Device, method, and graphical user interface for operating a user interface based on unlock input.

Abstract

To provide an electronic device and a method for use in operation of a user interface based on a finger print sensor input.SOLUTION: The present invention is directed to a method of registering a fingerprint using an electronic device having a display and a fingerprint sensor. The method has steps of displaying a fingerprint registration interface 602, detecting a plurality of finger gestures executed by a finger on the fingerprint sensor 604, and collecting fingerprint information from the plurality of finger gestures executed by the corresponding finger 606. The method further has the steps of, after collection of the fingerprint information, determining whether the collected fingerprint information is sufficient for registration of a fingerprint of the finger, and registering the fingerprint of the finger in accordance with the determination that the fingerprint information collected for the finger is sufficient for registration of the fingerprint of the finger using the device.SELECTED DRAWING: Figure 6A

Description

Technical Field

[0001] Related Applications This application claims priority to U.S. Provisional Patent Application No. 61 / 875,669, filed on September 9, 2013, and U.S. Non-Provisional Patent Application No. 14 / 480,183, filed on September 8, 2014, the entire disclosures of each of which are hereby incorporated by reference in their entirety.

[0002] This application generally relates to electronic devices having a fingerprint sensor, including but not limited to, an electronic device having a fingerprint sensor for detecting an input for operating a user interface.

Background Art

[0003] The use of touch-sensitive surfaces as input devices for computers and other electronic computing devices has increased significantly in recent years. Exemplary touch-sensitive surfaces include touch pads and touch screen displays. Such surfaces are widely used to operate user interfaces on displays. Additionally, some electronic devices include fingerprint sensors for authenticating users.

[0004] Examples of operations include adjusting the position and / or size of one or more user interface objects, activating a button, opening a file / application represented by a user interface object, associating metadata with one or more user interface objects, or otherwise manipulating the user interface. Examples of user interface objects include digital images, videos, text, icons, control elements such as buttons, and other graphics. In several situations, users need to perform such operations on user interface objects in file management programs (e.g., Finder from Apple Inc., Cupertino, California), image management applications (e.g., Aperture® or iPhoto® from Apple Inc., Cupertino, California), digital content (e.g., video and music) management applications (e.g., iTunes® from Apple Inc., Cupertino, California), drawing applications, presentation applications (e.g., Keynote® from Apple Inc., Cupertino, California), document creation applications (e.g., Pages® from Apple Inc., Cupertino, California), website creation applications (e.g., iWeb® from Apple Inc., Cupertino, California), disc authoring applications (e.g., iDVD® from Apple Inc., Cupertino, California), or spreadsheet applications (e.g., Numbers® from Apple Inc., Cupertino, California).

[0005] However, the methods for performing these operations are cumbersome and inefficient. In addition, these methods are unnecessarily time-consuming, thereby wasting energy. This latter consideration is particularly important in battery-powered devices. [Overview of the project]

[0006] Therefore, there is a need for electronic devices that have faster and more efficient methods and interfaces for operating the user interface. Such methods and interfaces optionally complement or replace conventional methods for operating the user interface. Such methods and interfaces reduce the cognitive burden on the user and create a more efficient human-machine interface. In the case of battery-operated devices, such methods and interfaces conserve power and increase the time between battery charges.

[0007] The defects and other problems described above associated with user interfaces for electronic devices having touch-sensitive surfaces are mitigated or eliminated by the disclosed device. In some embodiments, the device is a desktop computer. In some embodiments, the device is portable (e.g., a notebook computer, tablet computer, or handheld device). In some embodiments, the device has a touchpad. In some embodiments, the device has a touch-sensitive display (also known as a “touchscreen” or “touchscreen display”). In some embodiments, the device has a fingerprint sensor. In some embodiments, the device has a graphical user interface (GUI), one or more processors, memory, and one or more modules, programs, or instruction sets stored in memory to perform multiple functions. In some embodiments, the user interacts with the GUI primarily through finger touch and gestures on the touch-sensitive surface and / or fingerprint sensor. In some embodiments, the functions optionally include image editing, drawing, presentation, word processing, website creation, disk authoring, spreadsheet creation, gameplay, making phone calls, video conferencing, sending emails, instant messaging, training support, digital photography, digital videography, web browsing, digital music playback, and / or digital video playback. Executable instructions for performing these functions may optionally be included in a non-temporary computer-readable storage medium or in other computer program products configured to run by one or more processors.

[0008] There is a need for electronic devices with faster and more efficient methods and interfaces for registering fingerprints using the device. Such methods and interfaces can complement or replace conventional methods for registering fingerprints using the device. Such methods and interfaces reduce the cognitive burden on the user and create a more efficient human-machine interface. In the case of battery-operated devices, such methods and interfaces save power and increase the time between battery charges.

[0009] Methods according to some embodiments are performed on an electronic device comprising a display and a fingerprint sensor. The method includes displaying a fingerprint registration interface, detecting a plurality of individual and distinct static finger gestures performed on the fingerprint sensor with a corresponding finger, and collecting fingerprint information from the plurality of individual and distinct static finger gestures performed on the corresponding finger. After collecting the fingerprint information, the method includes determining, based on the fingerprint information collected for the corresponding finger, whether the collected fingerprint information is sufficient to register the fingerprint of that corresponding finger using the device. In accordance with the determination that the collected fingerprint information for the corresponding finger is sufficient to register the fingerprint of that corresponding finger, the method includes registering the fingerprint of the corresponding finger using the device. In accordance with the determination that the collected fingerprint information for the corresponding finger is insufficient to register the fingerprint of that corresponding finger, the method includes displaying a message on the fingerprint registration interface prompting the user to perform one or more further static finger gestures with that corresponding finger on the fingerprint sensor.

[0010] According to some embodiments, the electronic device comprises a display unit configured to display a fingerprint registration interface, a fingerprint sensor unit, and a processing unit connected to the display unit and the fingerprint sensor unit. The processing unit is configured to detect a plurality of individual and distinct static finger gestures performed with a corresponding finger on the fingerprint sensor unit and to collect fingerprint information from the plurality of individual and distinct static finger gestures performed with the corresponding finger. After collecting the fingerprint information, the processing unit is also configured to determine, based on the fingerprint information collected for that corresponding finger, whether the collected fingerprint information is sufficient to register the fingerprint of that finger using the device. In accordance with the determination that the collected fingerprint information for a corresponding finger is sufficient to register the fingerprint of that finger, the processing unit is configured to register the fingerprint of that finger using the device. In accordance with the determination that the collected fingerprint information for a corresponding finger is insufficient to register the fingerprint of that finger, the processing unit is configured to enable the display of a message on the fingerprint registration interface prompting the user to perform one or more further static finger gestures with that finger on the fingerprint sensor.

[0011] Thus, electronic devices equipped with a display and a fingerprint sensor have faster and more efficient methods and interfaces for registering fingerprints using the device, thereby enhancing the effectiveness, efficiency, and user satisfaction of such devices. Such methods and interfaces can complement or replace conventional methods for registering fingerprints using the device.

[0012] There is a need for electronic devices with faster and more efficient methods and interfaces for performing fingerprint-based actions. Such methods and interfaces can complement or replace conventional methods for performing actions. Such methods and interfaces reduce the cognitive burden on the user and create a more efficient human-machine interface. In the case of battery-operated devices, such methods and interfaces save power and increase the time between battery charges.

[0013] According to some embodiments, the method is performed in an electronic device equipped with a fingerprint sensor. The method includes detecting a first input using the fingerprint sensor. The method also includes determining whether the first input contains a fingerprint in response to the detection of the first input. The method further includes performing a first action based on the presence of a fingerprint, regardless of the fingerprint identification information, in accordance with the determination that the first input contains a fingerprint, and conditionally performing a second action based on a registered fingerprint in accordance with the determination that the fingerprint of the first input matches a registered fingerprint.

[0014] According to some embodiments, the electronic device includes a fingerprint sensor unit configured to detect a first input and a processing unit connected to the fingerprint sensor unit. The processing unit is configured to determine whether the first input contains a fingerprint in response to detecting the first input. The processing unit is also configured to perform a first action based on the presence of a fingerprint, regardless of the fingerprint identification information, in accordance with the determination that the first input contains a fingerprint. The processing unit is further configured to conditionally perform a second action based on a registered fingerprint in accordance with the determination that the fingerprint of the first input matches a registered fingerprint.

[0015] Thus, electronic devices equipped with fingerprint sensors have faster and more efficient methods and interfaces for performing fingerprint-based actions, thereby increasing the effectiveness, efficiency, and user satisfaction of such devices. Such methods and interfaces can complement or replace conventional methods for performing fingerprint-based actions.

[0016] There is a need for electronic devices with faster and more efficient methods and interfaces for adding data to credential fields, such as passwords and credit card numbers, and for retrieving organized credentials. Such methods and interfaces can complement or replace conventional methods for adding data to credential fields and retrieving organized credentials. Such methods and interfaces reduce the cognitive burden on the user and create a more efficient human-machine interface. In the case of battery-operated devices, such methods and interfaces save power and increase the time between battery charges.

[0017] Methods according to some embodiments are performed on an electronic device comprising a display and a fingerprint sensor. The method includes: storing one or more sets of credentials; displaying a form having fields corresponding to one or more credentials of the set of credentials; receiving a request including a finger input on a fingerprint sensor to automatically fill in the form with one or more credentials of the set of credentials; filling in the form with one or more credentials in response to receiving a request to automatically fill in the form, according to a determination that the finger input includes a fingerprint associated with a user authorized to use the set of credentials; and ceasing to fill in the form with one or more credentials in response to a determination that the finger input includes a fingerprint not associated with a user authorized to use the set of credentials.

[0018] According to some embodiments, the electronic device comprises a display unit configured to display a form having fields corresponding to one or more credentials of one or more sets of credentials; a credential storage unit configured to store one or more sets of credentials; a fingerprint sensor unit; and a processing unit connected to the display unit, the credential storage unit, and the fingerprint sensor unit. The processing unit is configured to receive a request including a finger input on the fingerprint sensor for automatically filling out a form with one or more credentials of one or more sets of credentials, and to fill out the form with one or more credentials if it determines that the finger input includes a fingerprint associated with a user authorized to use one or more sets of credentials, and to stop filling out the form with one or more credentials if it determines that the finger input includes a fingerprint not associated with a user authorized to use one or more sets of credentials.

[0019] Methods according to some embodiments are performed on an electronic device comprising a display and a fingerprint sensor. The method includes storing one or more sets of credentials; receiving a request to display one or more sets of credentials; displaying an organized version of one or more sets of credentials in response to receiving a request to display one or more sets of credentials; detecting a fingerprint on the fingerprint sensor while displaying the organized version of one or more sets of credentials; and displaying an unorganized version of one or more sets of credentials in response to the detection of a fingerprint and in accordance with the determination that the fingerprint is associated with a user authorized to reveal one or more sets of credentials.

[0020] According to some embodiments, the electronic device comprises a display unit, a fingerprint sensor unit, a display unit, a credential storage unit, and a processing unit connected to the fingerprint sensor unit. The processing unit is configured to receive a request to display one or more sets of credentials, to enable the display of an organized version of the set of credentials in response to receiving a request to display one or more sets of credentials, and to enable the display of an unorganized version of the set of credentials in response to a fingerprint being detected on the fingerprint sensor while the organized version of the set of credentials is being displayed, and in accordance with a determination that the fingerprint is associated with a user authorized to reveal the set of credentials.

[0021] Thus, electronic devices equipped with a display and a fingerprint sensor have faster and more efficient methods and interfaces for automatically adding data to credential fields and revealing organized credentials, thereby enhancing the effectiveness, efficiency, and user satisfaction of such devices. Such methods and interfaces can complement or replace conventional methods for adding data to credential fields and revealing organized credentials.

[0022] There is a need for electronic devices with more efficient and secure methods and interfaces for managing the automated use of stored credentials. Such methods and interfaces can complement or replace conventional methods for managing the automated use of stored credentials.

[0023] Methods according to some embodiments are performed on an electronic device comprising a display and a fingerprint sensor. The method includes storing the corresponding credentials of a user of the device on the device, and, while running a software application, (1) receiving a fingerprint at the device's fingerprint sensor, and (2) automatically using the user's corresponding credentials in the software application in response to receiving a fingerprint and in accordance with a determination that credential usage criteria are met, including a determination that the received fingerprint matches at least one of a set of registered fingerprints. The method also includes receiving a request to register additional fingerprints using the device after automatically using the user's corresponding credentials in response to receiving a fingerprint, adding additional fingerprints to the set of registered fingerprints in response to a request to register additional fingerprints using the device, and preventing the registered fingerprints from being used to authorize the automatic use of the corresponding credentials in response to adding additional fingerprints to the set of registered fingerprints.

[0024] According to some embodiments, an electronic device includes a storage unit configured to store corresponding credentials of a user of the device on the device, and a processing unit coupled to the storage unit. The processing unit is configured to, while executing a software application, (1) receive a fingerprint at a fingerprint sensor of the device, and (2) automatically use the corresponding credentials of the user in the software application according to a determination that the fingerprint has been received and according to a determination that a credential usage criterion is satisfied, the determination including that the received fingerprint matches at least one of a set of registered fingerprints. After automatically using the corresponding credentials of the user in response to receiving the fingerprint, the processing unit receives a request to register a further fingerprint using the device, and in response to the request to register a further fingerprint using the device, adds the further fingerprint to the set of registered fingerprints, and is further configured to prevent the registered fingerprint from being used to permit automatic use of the corresponding credentials.

[0025] Thus, an electronic device including a display and a fingerprint sensor has a more efficient and secure method and interface for managing automatic use of credentials, enhancing the effectiveness, efficiency, and user satisfaction of such a device. Such a method and interface can complement or replace conventional methods for managing automatic use of credentials.

[0026] There is a need for an electronic device with a faster and more efficient method and interface for revealing organized information. Such a method and interface can complement or replace conventional methods of displaying information on a device. Such a method and interface reduces the cognitive burden on the user and creates a more efficient human-machine interface. In the case of a battery-operated device, such a method and interface saves power and increases the time between battery charges.

[0027] The method according to some embodiments is executed on an electronic device comprising a display and a fingerprint sensor. The method includes displaying a redacted version of first information on the display and detecting a finger input on the fingerprint sensor while the redacted version of the first information is being displayed on the display. The method further includes, in response to detecting the finger input on the fingerprint sensor, replacing the display of the redacted version of the first information with the unredacted version of the first information according to a determination that the finger input includes a fingerprint that matches a registered fingerprint that is permitted to reveal the first information, and maintaining the display of the redacted version of the first information on the display according to a determination that the finger input does not include a fingerprint that matches a previously registered fingerprint that is permitted to reveal the first information.

[0028] According to some embodiments, an electronic device comprises a display unit configured to display a redacted version of first information on the display, a fingerprint sensor unit, and a processing unit coupled to the display unit and the fingerprint sensor unit. The processing unit is configured to detect a finger input on the fingerprint sensor while enabling the display of the redacted version of the first information on the display unit. The processing unit is further configured, in response to detecting the finger input on the fingerprint sensor, to replace the display of the redacted version of the first information with the unredacted version of the first information according to a determination that the finger input includes a fingerprint that matches a registered fingerprint that is permitted to reveal the first information, and to maintain the display of the redacted version of the first information on the display according to a determination that the finger input does not include a fingerprint that matches a previously registered fingerprint that is permitted to reveal the first information.

[0029] Thus, electronic devices equipped with displays and fingerprint sensors have faster and more efficient methods and interfaces for revealing organized information, thereby enhancing the effectiveness, efficiency, and user satisfaction of such devices. Such methods and interfaces can complement or replace conventional methods of displaying information on devices.

[0030] There is a need for electronic devices with faster, more efficient methods and interfaces to provide various unlocking modes. Such methods and interfaces can complement or replace conventional methods for providing various unlocking modes. Such methods and interfaces reduce the cognitive burden on the user and create a more efficient human-machine interface. In the case of battery-operated devices, such methods and interfaces save power and increase the time between battery charges.

[0031] According to some embodiments, the method is performed on an electronic device comprising a fingerprint sensor and a display. While the operating mode of the device is in a locked mode in which access to the corresponding set of functions of the electronic device is locked, the method includes detecting a first input on the fingerprint sensor that corresponds to a request to initiate unlocking of the device. In response to detecting the first input on the fingerprint sensor, the method further includes determining whether the first input satisfies one of an unlock criterion, a first unlock failure criterion, or a second unlock failure criterion. In accordance with the determination that the first input satisfies an unlock criterion, the method includes transitioning the device from the locked mode to an unlocked mode in which the corresponding set of functions of the electronic device is unlocked. In accordance with the determination that a first input satisfies a first unlock failure criterion, the method includes: keeping the device in locked mode and adjusting the unlock settings so that the device can be unlocked via an unlock operation in a first set of one or more unlock operations; and, in accordance with the determination that a first input satisfies a second unlock failure criterion, keeping the device in locked mode and adjusting the unlock settings so that the device can be unlocked via an unlock operation in a second set of one or more unlock operations different from the first set of unlock operations.

[0032] According to some embodiments, the electronic device comprises a display unit configured to display a graphical user interface, a fingerprint sensor unit, and a processing unit connected to the display unit and the fingerprint sensor unit. When the operating mode of the device is in a locked mode in which access to the corresponding set of functions of the electronic device is locked, the fingerprint sensor unit detects a first input corresponding to a request to initiate unlocking of the device. In response to the detection of the first input by the fingerprint sensor unit, the processing unit is configured to determine whether the first input satisfies one of an unlock criterion, a first unlock failure criterion, or a second unlock failure criterion. The processing unit is further configured to move the device from the locked mode to an unlocked mode in which the corresponding set of functions of the electronic device is unlocked, according to the determination that the first input satisfies the first unlock failure criterion. The processing unit is further configured to keep the device in the locked mode and adjust the unlock settings so that the device can be unlocked via an unlock operation in a first set of one or more unlock operations. The processing unit is further configured to maintain the device in locked mode upon determination that the first input satisfies the second unlock failure criterion, and to adjust the unlock settings so that the device enables unlocking via unlocking operations in a second set of one or more unlocking operations different from the first set of unlocking operations.

[0033] Thus, electronic devices equipped with a display and a fingerprint sensor have faster and more efficient methods for providing various unlocking modes, thereby increasing the effectiveness, efficiency, and user satisfaction of such devices. Such methods and interfaces can complement or replace conventional methods for providing various unlocking modes.

[0034] Electronic devices require more efficient and secure methods and interfaces for controlling access to device information and functions and for unlocking the device. Such methods and interfaces may complement or replace conventional methods for controlling access to device information and functions and for unlocking the device. Such methods and interfaces reduce the cognitive burden on the user and create a more efficient human-machine interface. In the case of battery-operated devices, such methods and interfaces conserve power and increase battery charging time.

[0035] Methods according to some embodiments are performed on an electronic device comprising a display and a fingerprint sensor. The method includes: detecting a first input by displaying a first user interface on the display while the device is in a locked mode in which access to the corresponding function set of the electronic device is locked; displaying a second user interface on the display in a limited access mode in which access is restricted according to a restriction criterion, in response to the detection of the first input; detecting a first fingerprint on the fingerprint sensor while the second user interface is displayed in limited access mode; displaying the second user interface in full access mode in which access is not restricted according to a restriction criterion, in accordance with the determination that the first fingerprint is one of a plurality of registered fingerprints registered using the device, and moving the device from a locked mode to an unlocked mode in which the corresponding function set of the electronic device is unlocked; and maintaining the display of the second user interface in limited access mode and keeping the device in locked mode, in accordance with the determination that the first fingerprint is not one of a plurality of registered fingerprints.

[0036] According to some embodiments, the electronic device includes a display unit, a fingerprint sensor unit, and a processing unit connected to the display unit and the fingerprint sensor unit. The processing unit is configured to detect a first input by enabling the display of a first user interface on the display unit while the device is in a locked mode in which access to the corresponding set of features of the electronic device is locked; to enable the display of a second user interface on the display unit in a limited access mode in which access is restricted according to a restriction criterion, in response to the detection of the first input; to detect a first fingerprint on the fingerprint sensor while the display of the second user interface is enabled in limited access mode; to enable the display of the second user interface in a full access mode in which access to the second user interface is not restricted according to the restriction criterion, in accordance with the determination that the first fingerprint is one of a plurality of registered fingerprints registered using the device; to transition the device from the locked mode to an unlocked mode in which the corresponding set of features of the electronic device is unlocked; and to maintain the display of the second user interface in limited access mode and maintain the device in locked mode, in accordance with the determination that the first fingerprint is not one of a plurality of registered fingerprints.

[0037] Thus, electronic devices equipped with a display and a fingerprint sensor have more efficient and secure methods and interfaces for controlling access to device information and functions and unlocking the device, thereby enhancing the effectiveness, efficiency, and user satisfaction of such devices. Such methods and interfaces may complement or replace conventional methods for controlling access to device information and functions and unlocking the device.

[0038] There is a need for electronic devices with more efficient methods and interfaces for unlocking applications or devices in a context-dependent manner. Such methods and interfaces can complement or replace conventional methods of unlocking. Such methods and interfaces reduce the cognitive burden on the user and create a more efficient human-machine interface. In the case of battery-operated devices, such methods and interfaces conserve power and increase the time between battery charges.

[0039] Methods according to some embodiments are performed on an electronic device comprising a display and a fingerprint sensor. The method includes, while the electronic device is in a locked mode in which access to functions of multiple different applications on the electronic device is prevented, displaying on the display a first user interface which is one type of locked device user interface for the electronic device, and a limited-access user interface for the corresponding application in multiple different applications, and detecting a first input corresponding to a request to initiate the unlocking of one or more functions of the device using the fingerprint sensor. The method further includes, in response to the detection of the first input corresponding to a request to initiate the unlocking of one or more functions of the device using the fingerprint sensor, transitioning the device from the locked mode to a multi-application unlocked mode in which functions of multiple different applications are unlocked, according to the determination that the first user interface is a locked device user interface for the electronic device. The method also includes, according to the determination that the first user interface is a limited-access user interface for the corresponding application, transitioning the device from the locked mode to a single-application unlocked mode in which one or more previously locked functions of the corresponding application are unlocked, and continuing to prevent access to one or more previously locked functions of other applications in multiple different applications.

[0040] According to some embodiments, the electronic device comprises a display unit configured to display a first user interface, a fingerprint sensor unit, and a processing unit connected to the display unit and the fingerprint sensor unit. The processing unit is configured to enable the display on the display unit of a first user interface, which is one of the locked device user interfaces for the electronic device, and the limited access user interfaces for corresponding applications in the various applications, while the electronic device is in a locked mode in which access to the functions of multiple different applications on the electronic device is prevented, and to detect a first input using the fingerprint sensor that corresponds to a request to initiate the unlocking of one or more functions of the device. The processing unit is further configured to, in response to the detection of a first input using the fingerprint sensor that corresponds to a request to initiate the unlocking of one or more functions of the device, to determine that the first user interface is the locked device user interface of the electronic device, to transition the device from a locked mode to a multi-application unlocked mode in which the functions of multiple different applications are unlocked. The processing unit is also configured to, upon determining that the first user interface is a limited-access user interface for the corresponding application, transition the device from locked mode to single-application unlocked mode, where one or more previously locked features of the corresponding application are unlocked, while continuing to prevent access to one or more previously locked features of other applications in multiple different applications.

[0041] Thus, electronic devices equipped with a display and a fingerprint sensor have efficient methods and interfaces for unlocking applications or devices in a context-dependent manner, thereby enhancing the effectiveness, efficiency, and user satisfaction of such devices. Such methods and interfaces can complement or replace conventional methods of unlocking.

[0042] In some embodiments, the electronic device includes a fingerprint sensor, a display and / or a touch-sensitive surface, one or more processors, memory, and one or more programs, the one or more programs being stored in memory and configured to be executed by the one or more processors, and the one or more programs including instructions for performing any of the methods described above. According to some embodiments, a graphical user interface on an electronic device having a fingerprint sensor, a display, optionally a touch-sensitive surface, memory, and one or more processors that execute one or more programs stored in memory includes one or more elements displayed in any of the methods described above, and these elements are updated in response to input as described in any of the methods described above. A computer-readable storage medium according to some embodiments stores instructions that, when executed by an electronic device having a fingerprint sensor and optionally a display and / or a touch-sensitive surface, cause the electronic device to perform any of the methods described above. An electronic device according to some embodiments includes a fingerprint sensor, optionally a display and / or one or more touch-sensitive surfaces, and means for performing any of the methods described above. An information processing device for use in an electronic device having a fingerprint sensor and optionally a display and / or a touch-sensing surface, according to some embodiments, includes means for performing any of the operations described above.

[0043] Thus, electronic devices equipped with a display and a fingerprint sensor have faster and more efficient methods and interfaces for changing beamforming parameters based on fingerprint orientation, thereby enhancing the effectiveness, efficiency, and user satisfaction of such devices. Such methods and interfaces can complement or replace conventional methods for changing beamforming parameters. [Brief explanation of the drawing]

[0044] For a better understanding of the various embodiments described, please refer to the following “Description of Embodiments” in conjunction with the following drawings, where similar reference numbers refer to corresponding parts throughout those drawings.

[0045] [Figure 1A] This is a block diagram showing a portable multifunctional device comprising a touch-sensitive display and a fingerprint sensor, according to several embodiments.

[0046] [Figure 1B] This is a block diagram showing exemplary components for event handling according to several embodiments.

[0047] [Figure 2] Several embodiments of a portable multifunctional device having a touchscreen and a fingerprint sensor are shown.

[0048] [Figure 3] This is a block diagram of an exemplary multifunctional device having a display, a plurality of sensors including a fingerprint sensor, and optionally a touch-sensing surface, according to several embodiments.

[0049] [Figure 4A] This document illustrates an exemplary user interface for an application menu in a portable multifunction device according to several embodiments.

[0050] [Figure 4B] This document describes exemplary user interfaces for a multifunctional device having a touch-sensitive surface separate from a fingerprint sensor and display, according to several embodiments.

[0051] [Figure 4C] A schematic diagram of two hands associated with fingerprints, according to several embodiments, is shown.

[0052] [Figure 4D]Several embodiments illustrate various types of fingerprint rotation on a fingerprint sensor.

[0053] [Figure 5A] The following are exemplary user interfaces for registering fingerprints using a device, according to several embodiments. [Figure 5B] The following are exemplary user interfaces for registering fingerprints using a device, according to several embodiments. [Figure 5C] The following are exemplary user interfaces for registering fingerprints using a device, according to several embodiments. [Figure 5D] The following are exemplary user interfaces for registering fingerprints using a device, according to several embodiments. [Figure 5E] The following are exemplary user interfaces for registering fingerprints using a device, according to several embodiments. [Figure 5F] The following are exemplary user interfaces for registering fingerprints using a device, according to several embodiments. [Figure 5G] The following are exemplary user interfaces for registering fingerprints using a device, according to several embodiments. [Figure 5H] The following are exemplary user interfaces for registering fingerprints using a device, according to several embodiments. [Figure 5I] The following are exemplary user interfaces for registering fingerprints using a device, according to several embodiments. [Figure 5J] The following are exemplary user interfaces for registering fingerprints using a device, according to several embodiments. [Figure 5K] The following are exemplary user interfaces for registering fingerprints using a device, according to several embodiments. [Figure 5L] The following are exemplary user interfaces for registering fingerprints using a device, according to several embodiments. [Figure 5M]The following are exemplary user interfaces for registering fingerprints using a device, according to several embodiments. [Figure 5N] The following are exemplary user interfaces for registering fingerprints using a device, according to several embodiments. [Figure 5O] The following are exemplary user interfaces for registering fingerprints using a device, according to several embodiments. [Figure 5P] The following are exemplary user interfaces for registering fingerprints using a device, according to several embodiments. [Figure 5Q] The following are exemplary user interfaces for registering fingerprints using a device, according to several embodiments. [Figure 5R] The following are exemplary user interfaces for registering fingerprints using a device, according to several embodiments. [Figure 5S] The following are exemplary user interfaces for registering fingerprints using a device, according to several embodiments. [Figure 5T] The following are exemplary user interfaces for registering fingerprints using a device, according to several embodiments. [Figure 5U] The following are exemplary user interfaces for registering fingerprints using a device, according to several embodiments. [Figure 5V] The following are exemplary user interfaces for registering fingerprints using a device, according to several embodiments. [Figure 5W] The following are exemplary user interfaces for registering fingerprints using a device, according to several embodiments. [Figure 5X] The following are exemplary user interfaces for registering fingerprints using a device, according to several embodiments. [Figure 5Y] The following are exemplary user interfaces for registering fingerprints using a device, according to several embodiments. [Figure 5Z]The following are exemplary user interfaces for registering fingerprints using a device, according to several embodiments. [Figure 5AA] The following are exemplary user interfaces for registering fingerprints using a device, according to several embodiments. [Figure 5BB] The following are exemplary user interfaces for registering fingerprints using a device, according to several embodiments. [Figure 5CC] The following are exemplary user interfaces for registering fingerprints using a device, according to several embodiments. [Figure 5DD] The following are exemplary user interfaces for registering fingerprints using a device, according to several embodiments. [Figure 5EE] The following are exemplary user interfaces for registering fingerprints using a device, according to several embodiments.

[0054] [Figure 6A] This flowchart illustrates a method for registering fingerprints using a device according to several embodiments. [Figure 6B] This flowchart illustrates a method for registering fingerprints using a device according to several embodiments. [Figure 6C] This flowchart illustrates a method for registering fingerprints using a device according to several embodiments. [Figure 6D] This flowchart illustrates a method for registering fingerprints using a device according to several embodiments.

[0055] [Figure 7] This is a functional block diagram of an electronic device according to several embodiments.

[0056] [Figure 8A] The following are exemplary user interfaces for performing fingerprint-based operations according to several embodiments. [Figure 8B]The following are exemplary user interfaces for performing fingerprint-based operations according to several embodiments. [Figure 8C] The following are exemplary user interfaces for performing fingerprint-based operations according to several embodiments. [Figure 8D] The following are exemplary user interfaces for performing fingerprint-based operations according to several embodiments. [Figure 8E] The following are exemplary user interfaces for performing fingerprint-based operations according to several embodiments. [Figure 8F] The following are exemplary user interfaces for performing fingerprint-based operations according to several embodiments. [Figure 8G] The following are exemplary user interfaces for performing fingerprint-based operations according to several embodiments. [Figure 8H] The following are exemplary user interfaces for performing fingerprint-based operations according to several embodiments. [Figure 8I] The following are exemplary user interfaces for performing fingerprint-based operations according to several embodiments. [Figure 8J] The following are exemplary user interfaces for performing fingerprint-based operations according to several embodiments. [Figure 8K] The following are exemplary user interfaces for performing fingerprint-based operations according to several embodiments. [Figure 8L] The following are exemplary user interfaces for performing fingerprint-based operations according to several embodiments. [Figure 8M] The following are exemplary user interfaces for performing fingerprint-based operations according to several embodiments. [Figure 8N] The following are exemplary user interfaces for performing fingerprint-based operations according to several embodiments. [Figure 8O] The following are exemplary user interfaces for performing fingerprint-based operations according to several embodiments. [Figure 8P] The following are exemplary user interfaces for performing fingerprint-based operations according to several embodiments. [Figure 8Q] The following are exemplary user interfaces for performing fingerprint-based operations according to several embodiments. [Figure 8R] The following are exemplary user interfaces for performing fingerprint-based operations according to several embodiments. [Figure 8S] The following are exemplary user interfaces for performing fingerprint-based operations according to several embodiments. [Figure 8T] The following are exemplary user interfaces for performing fingerprint-based operations according to several embodiments. [Figure 8U] The following are exemplary user interfaces for performing fingerprint-based operations according to several embodiments. [Figure 8V] The following are exemplary user interfaces for performing fingerprint-based operations according to several embodiments. [Figure 8W] The following are exemplary user interfaces for performing fingerprint-based operations according to several embodiments.

[0057] [Figure 9A] This flowchart illustrates a method for performing fingerprint-based operations according to several embodiments. [Figure 9B] This flowchart illustrates a method for performing fingerprint-based operations according to several embodiments.

[0058] [Figure 10] This is a functional block diagram of an electronic device according to several embodiments.

[0059] [Figure 11A]The following are exemplary user interfaces for adding credentials to a credential field and displaying an unorganized version of the credentials in response to fingerprint-based user authentication, according to several embodiments. [Figure 11B] The following are exemplary user interfaces for adding credentials to a credential field and displaying an unorganized version of the credentials in response to fingerprint-based user authentication, according to several embodiments. [Figure 11C] The following are exemplary user interfaces for adding credentials to a credential field and displaying an unorganized version of the credentials in response to fingerprint-based user authentication, according to several embodiments. [Figure 11D] The following are exemplary user interfaces for adding credentials to a credential field and displaying an unorganized version of the credentials in response to fingerprint-based user authentication, according to several embodiments.

[0060] [Figure 12A] The following flowcharts illustrate several embodiments of allowing automatic data addition to credential fields using fingerprint-based user authentication and enabling the display of an unorganized version of the credentials. [Figure 12B] The following flowcharts illustrate several embodiments of allowing automatic data addition to credential fields using fingerprint-based user authentication and enabling the display of an unorganized version of the credentials.

[0061] [Figure 13] This is a functional block diagram of an electronic device according to some embodiments.

[0062] [Figure 14A] The following are exemplary user interfaces for displaying an unorganized version of credentials in response to fingerprint-based user authentication, according to several embodiments. [Figure 14B]The following are exemplary user interfaces for displaying an unorganized version of credentials in response to fingerprint-based user authentication, according to several embodiments. [Figure 14C] The following are exemplary user interfaces for displaying an unorganized version of credentials in response to fingerprint-based user authentication, according to several embodiments.

[0063] [Figure 15A] This flowchart illustrates a method, according to several embodiments, for allowing the display of an unorganized version of credentials using fingerprint-based user authentication. [Figure 15B] This flowchart illustrates a method, according to several embodiments, for allowing the display of an unorganized version of credentials using fingerprint-based user authentication.

[0064] [Figure 16] This is a functional block diagram of an electronic device according to several embodiments.

[0065] [Figure 17A] The following are exemplary user interfaces for managing the automated use of credentials stored through registered fingerprints, according to several embodiments. [Figure 17B] The following are exemplary user interfaces for managing the automated use of credentials stored through registered fingerprints, according to several embodiments. [Figure 17C] The following are exemplary user interfaces for managing the automated use of credentials stored through registered fingerprints, according to several embodiments. [Figure 17D] The following are exemplary user interfaces for managing the automated use of credentials stored through registered fingerprints, according to several embodiments. [Figure 17E] The following are exemplary user interfaces for managing the automated use of credentials stored through registered fingerprints, according to several embodiments. [Figure 17F] The following are exemplary user interfaces for managing the automated use of credentials stored through registered fingerprints, according to several embodiments. [Figure 17G] The following are exemplary user interfaces for managing the automated use of credentials stored through registered fingerprints, according to several embodiments. [Figure 17H] The following are exemplary user interfaces for managing the automated use of credentials stored through registered fingerprints, according to several embodiments. [Figure 17I] The following are exemplary user interfaces for managing the automated use of credentials stored through registered fingerprints, according to several embodiments. [Figure 17J] The following are exemplary user interfaces for managing the automated use of credentials stored through registered fingerprints, according to several embodiments.

[0066] [Figure 18A] This flowchart illustrates a method for managing the automated use of credentials stored through registered fingerprints, according to several embodiments. [Figure 18B] This flowchart illustrates a method for managing the automated use of credentials stored through registered fingerprints, according to several embodiments. [Figure 18C] This flowchart illustrates a method for managing the automated use of credentials stored through registered fingerprints, according to several embodiments.

[0067] [Figure 19] This is a functional block diagram of an electronic device according to several embodiments.

[0068] [Figure 20A] The following are exemplary user interfaces for revealing organized information according to several embodiments. [Figure 20B]The following are exemplary user interfaces for revealing organized information according to several embodiments. [Figure 20C] The following are exemplary user interfaces for revealing organized information according to several embodiments. [Figure 20D] The following are exemplary user interfaces for revealing organized information according to several embodiments. [Figure 20E] The following are exemplary user interfaces for revealing organized information according to several embodiments. [Figure 20F] The following are exemplary user interfaces for revealing organized information according to several embodiments. [Figure 20G] The following are exemplary user interfaces for revealing organized information according to several embodiments. [Figure 20H] The following are exemplary user interfaces for revealing organized information according to several embodiments. [Figure 20I] The following are exemplary user interfaces for revealing organized information according to several embodiments. [Figure 20J] The following are exemplary user interfaces for revealing organized information according to several embodiments. [Figure 20K] The following are exemplary user interfaces for revealing organized information according to several embodiments. [Figure 20L] The following are exemplary user interfaces for revealing organized information according to several embodiments. [Figure 20M] The following are exemplary user interfaces for revealing organized information according to several embodiments. [Figure 20N] The following are exemplary user interfaces for revealing organized information according to several embodiments. [Figure 20O]The following are exemplary user interfaces for revealing organized information according to several embodiments. [Figure 20P] The following are exemplary user interfaces for revealing organized information according to several embodiments. [Figure 20Q] The following are exemplary user interfaces for revealing organized information according to several embodiments. [Figure 20R] The following are exemplary user interfaces for revealing organized information according to several embodiments. [Figure 20S] The following are exemplary user interfaces for revealing organized information according to several embodiments. [Figure 20T] The following are exemplary user interfaces for revealing organized information according to several embodiments.

[0069] [Figure 21A] This flowchart illustrates a method for revealing organized information according to several embodiments. [Figure 21B] This flowchart illustrates a method for revealing organized information according to several embodiments. [Figure 21C] This flowchart illustrates a method for revealing organized information according to several embodiments.

[0070] [Figure 22] This is a functional block diagram of an electronic device according to several embodiments.

[0071] [Figure 23A] An exemplary user interface for providing various unlocking modes according to several embodiments is shown. [Figure 23B] An exemplary user interface for providing various unlocking modes according to several embodiments is shown. [Figure 23C]An exemplary user interface for providing various unlocking modes according to several embodiments is shown. [Figure 23D] An exemplary user interface for providing various unlocking modes according to several embodiments is shown. [Figure 23E] An exemplary user interface for providing various unlocking modes according to several embodiments is shown. [Figure 23F] An exemplary user interface for providing various unlocking modes according to several embodiments is shown. [Figure 23G] An exemplary user interface for providing various unlocking modes according to several embodiments is shown. [Figure 23H] An exemplary user interface for providing various unlocking modes according to several embodiments is shown. [Figure 23I] An exemplary user interface for providing various unlocking modes according to several embodiments is shown. [Figure 23J] An exemplary user interface for providing various unlocking modes according to several embodiments is shown. [Figure 23K] An exemplary user interface for providing various unlocking modes according to several embodiments is shown. [Figure 23L] An exemplary user interface for providing various unlocking modes according to several embodiments is shown. [Figure 23M] An exemplary user interface for providing various unlocking modes according to several embodiments is shown. [Figure 23N] An exemplary user interface for providing various unlocking modes according to several embodiments is shown. [Figure 23O] An exemplary user interface for providing various unlocking modes according to several embodiments is shown. [Figure 23P]An exemplary user interface for providing various unlocking modes according to several embodiments is shown. [Figure 23Q] An exemplary user interface for providing various unlocking modes according to several embodiments is shown. [Figure 23R] An exemplary user interface for providing various unlocking modes according to several embodiments is shown. [Figure 23S] An exemplary user interface for providing various unlocking modes according to several embodiments is shown. [Figure 23T] An exemplary user interface for providing various unlocking modes according to several embodiments is shown. [Figure 23U] An exemplary user interface for providing various unlocking modes according to several embodiments is shown. [Figure 23V] An exemplary user interface for providing various unlocking modes according to several embodiments is shown. [Figure 23W] An exemplary user interface for providing various unlocking modes according to several embodiments is shown. [Figure 23X] An exemplary user interface for providing various unlocking modes according to several embodiments is shown. [Figure 23Y] An exemplary user interface for providing various unlocking modes according to several embodiments is shown. [Figure 23Z] An exemplary user interface for providing various unlocking modes according to several embodiments is shown. [Figure 23AA] An exemplary user interface for providing various unlocking modes according to several embodiments is shown. [Figure 23BB] An exemplary user interface for providing various unlocking modes according to several embodiments is shown. [Figure 23CC]An exemplary user interface for providing various unlocking modes according to several embodiments is shown. [Figure 23DD] An exemplary user interface for providing various unlocking modes according to several embodiments is shown. [Figure 23EE] An exemplary user interface for providing various unlocking modes according to several embodiments is shown. [Figure 23FF] An exemplary user interface for providing various unlocking modes according to several embodiments is shown.

[0072] [Figure 24A] This flowchart illustrates a method for providing various unlocking modes according to several embodiments. [Figure 24B] This flowchart illustrates a method for providing various unlocking modes according to several embodiments. [Figure 24C] This flowchart illustrates a method for providing various unlocking modes according to several embodiments. [Figure 24D] This flowchart illustrates a method for providing various unlocking modes according to several embodiments.

[0073] [Figure 25] This is a functional block diagram of an electronic device according to several embodiments.

[0074] [Figure 26A] The following are exemplary user interfaces for controlling access to device information and functions and for unlocking the device, according to several embodiments. [Figure 26B] The following are exemplary user interfaces for controlling access to device information and functions and for unlocking the device, according to several embodiments. [Figure 26C]The following are exemplary user interfaces for controlling access to device information and functions and for unlocking the device, according to several embodiments. [Figure 26D] The following are exemplary user interfaces for controlling access to device information and functions and for unlocking the device, according to several embodiments. [Figure 26E] The following are exemplary user interfaces for controlling access to device information and functions and for unlocking the device, according to several embodiments. [Figure 26F] The following are exemplary user interfaces for controlling access to device information and functions and for unlocking the device, according to several embodiments. [Figure 26G] The following are exemplary user interfaces for controlling access to device information and functions and for unlocking the device, according to several embodiments. [Figure 26H] The following are exemplary user interfaces for controlling access to device information and functions and for unlocking the device, according to several embodiments. [Figure 26I] The following are exemplary user interfaces for controlling access to device information and functions and for unlocking the device, according to several embodiments. [Figure 26J] The following are exemplary user interfaces for controlling access to device information and functions and for unlocking the device, according to several embodiments. [Figure 26K] The following are exemplary user interfaces for controlling access to device information and functions and for unlocking the device, according to several embodiments. [Figure 26L] The following are exemplary user interfaces for controlling access to device information and functions and for unlocking the device, according to several embodiments. [Figure 26M]The following are exemplary user interfaces for controlling access to device information and functions and for unlocking the device, according to several embodiments. [Figure 26N] The following are exemplary user interfaces for controlling access to device information and functions and for unlocking the device, according to several embodiments. [Figure 26O] The following are exemplary user interfaces for controlling access to device information and functions and for unlocking the device, according to several embodiments. [Figure 26P] The following are exemplary user interfaces for controlling access to device information and functions and for unlocking the device, according to several embodiments. [Figure 26Q] The following are exemplary user interfaces for controlling access to device information and functions and for unlocking the device, according to several embodiments. [Figure 26R] The following are exemplary user interfaces for controlling access to device information and functions and for unlocking the device, according to several embodiments. [Figure 26S] The following are exemplary user interfaces for controlling access to device information and functions and for unlocking the device, according to several embodiments. [Figure 26T] The following are exemplary user interfaces for controlling access to device information and functions and for unlocking the device, according to several embodiments. [Figure 26U] The following are exemplary user interfaces for controlling access to device information and functions and for unlocking the device, according to several embodiments. [Figure 26V] The following are exemplary user interfaces for controlling access to device information and functions and for unlocking the device, according to several embodiments. [Figure 26W]The following are exemplary user interfaces for controlling access to device information and functions and for unlocking the device, according to several embodiments. [Figure 26X] The following are exemplary user interfaces for controlling access to device information and functions and for unlocking the device, according to several embodiments.

[0075] [Figure 27A] This flowchart illustrates a method for controlling access to device information and functions and unlocking a device, according to several embodiments. [Figure 27B] This flowchart illustrates a method for controlling access to device information and functions and unlocking a device, according to several embodiments. [Figure 27C] This flowchart illustrates a method for controlling access to device information and functions and unlocking a device, according to several embodiments. [Figure 27D] This flowchart illustrates a method for controlling access to device information and functions and unlocking a device, according to several embodiments.

[0076] [Figure 28] This is a functional block diagram of an electronic device according to several embodiments.

[0077] [Figure 29A] The following are exemplary user interfaces for context-dependently unlocking an application or device, according to several embodiments. [Figure 29B] The following are exemplary user interfaces for context-dependently unlocking an application or device, according to several embodiments. [Figure 29C] The following are exemplary user interfaces for context-dependently unlocking an application or device, according to several embodiments. [Figure 29D]The following are exemplary user interfaces for context-dependently unlocking an application or device, according to several embodiments. [Figure 29E] The following are exemplary user interfaces for context-dependently unlocking an application or device, according to several embodiments. [Figure 29F] The following are exemplary user interfaces for context-dependently unlocking an application or device, according to several embodiments. [Figure 29G] The following are exemplary user interfaces for context-dependently unlocking an application or device, according to several embodiments. [Figure 29H] The following are exemplary user interfaces for context-dependently unlocking an application or device, according to several embodiments. [Figure 29I] The following are exemplary user interfaces for context-dependently unlocking an application or device, according to several embodiments. [Figure 29J] The following are exemplary user interfaces for context-dependently unlocking an application or device, according to several embodiments. [Figure 29K] The following are exemplary user interfaces for context-dependently unlocking an application or device, according to several embodiments. [Figure 29L] The following are exemplary user interfaces for context-dependently unlocking an application or device, according to several embodiments. [Figure 29M] The following are exemplary user interfaces for context-dependently unlocking an application or device, according to several embodiments. [Figure 29N]The following are exemplary user interfaces for context-dependently unlocking an application or device, according to several embodiments. [Figure 29O] The following are exemplary user interfaces for context-dependently unlocking an application or device, according to several embodiments. [Figure 29P] The following are exemplary user interfaces for context-dependently unlocking an application or device, according to several embodiments. [Figure 29Q] The following are exemplary user interfaces for context-dependently unlocking an application or device, according to several embodiments. [Figure 29R] The following are exemplary user interfaces for context-dependently unlocking an application or device, according to several embodiments. [Figure 29S] The following are exemplary user interfaces for context-dependently unlocking an application or device, according to several embodiments. [Figure 29T] The following are exemplary user interfaces for context-dependently unlocking an application or device, according to several embodiments. [Figure 29U] The following are exemplary user interfaces for context-dependently unlocking an application or device, according to several embodiments. [Figure 29V] The following are exemplary user interfaces for context-dependently unlocking an application or device, according to several embodiments. [Figure 29W] The following are exemplary user interfaces for context-dependently unlocking an application or device, according to several embodiments. [Figure 29X]The following are exemplary user interfaces for context-dependently unlocking an application or device, according to several embodiments. [Figure 29Y] The following are exemplary user interfaces for context-dependently unlocking an application or device, according to several embodiments.

[0078] [Figure 30A] This flowchart illustrates a context-dependent method for unlocking an application or device, according to several embodiments. [Figure 30B] This flowchart illustrates a context-dependent method for unlocking an application or device, according to several embodiments. [Figure 30C] This flowchart illustrates a context-dependent method for unlocking an application or device, according to several embodiments. [Figure 30D] This flowchart illustrates a context-dependent method for unlocking an application or device, according to several embodiments.

[0079] [Figure 31] This is a functional block diagram of an electronic device according to several embodiments. Description of the Embodiment

[0080] The methods, devices, and GUIs described herein respond to input on a fingerprint sensor in place of, or in addition to, input on a touch-sensitive surface or other input device. In some implementations, a touch-sensitive surface having a spatial resolution of sufficient height to detect the features of a fingerprint formed by individual fingerprint ridges is used as the fingerprint sensor. When a fingerprint sensor without a separate touch-sensitive surface is used, the fingerprint sensor can perform many of the functions of a touch-sensitive surface in a much smaller form factor, as it can detect the movement of contact on the fingerprint sensor even when the area of ​​the fingerprint is larger than the area of ​​the fingerprint sensor. When a fingerprint sensor is used in addition to a separate touch-sensitive surface, the fingerprint sensor can augment the touch-sensitive surface by accurately detecting twisting motion of contact, identifying different fingerprints of the fingers used when performing gestures on the fingerprint sensor, and identifying the current user of the device. In addition, when a fingerprint sensor is used in addition to a separate touchscreen display, the fingerprint sensor can detect touch input in situations where it is preferable not to have a finger covering part of the display (e.g., while viewing a map, video, or game). When a touch-sensitive surface is used as a fingerprint sensor, the touch-sensitive surface optionally has a spatial resolution setting that can be optionally defined to automatically switch the touch-sensitive surface (or an area of ​​the touch-sensitive surface) between a low-resolution mode and a high-resolution mode without user intervention. In many situations, the low-resolution mode consumes less power than the high-resolution mode. The benefit of operating the touch-sensitive surface in low-resolution mode when fingerprint detection is not required, and switching the touch-sensitive surface or an area of ​​the touch-sensitive surface to high-resolution mode as needed, is to save power while enhancing the user experience of using the device by sensing fingerprint features at high resolution when necessary. In implementations where a touch-sensitive surface is used as a fingerprint sensor, the term "fingerprint sensor" refers to the touch-sensitive surface or an area of ​​the touch-sensitive surface that is currently in high-resolution mode.

[0081] Many different methods are described below for providing an intuitive user interface in which input from one or more fingerprint sensors is used to operate the user interface of an electronic device. Using one or more of these methods (optionally and in combination with each other) helps to provide a user interface that intuitively provides the user with additional information or functionality, thus reducing the cognitive burden on the user and enhancing the human-machine interface. Such improvements to the human-machine interface enable the user to use the device faster and more efficiently. With respect to battery-operated devices, these improvements result in power savings and increased intervals between battery charging. For the sake of simplicity, some exemplary embodiments of these methods, including systems, methods, and user interfaces, are described below. Figures 5A to 5EE below show exemplary user interfaces for registering fingerprints using the device. Figures 6A to 6D are flowcharts illustrating how to register fingerprints using the device. The user interfaces in Figures 5A to 5EE are used to illustrate the processes in Figures 6A to 6D. Figures 8A to 8W show exemplary user interfaces for performing fingerprint-based actions. Figures 9A to 9B are flowcharts illustrating how to perform fingerprint-based actions. The processes shown in Figures 9A to 9B are illustrated using the user interfaces of Figures 8A to 8W. ●Figures 11A-11D and 14A-14C below show exemplary user interfaces for adding credentials to a credentials field and displaying an unorganized version of the credentials, based on authentication using the user's fingerprint.Figures 12A-12B and 15A-15B are flowcharts showing how to allow automatic addition of credentials to a credentials field and / or display of unorganized credentials using authentication based on the user's fingerprint. The processes in Figures 12A-12B and 15A-15B are illustrated using the user interfaces in Figures 11A-11D and 14A-14C. ●Figures 17A to 17J below show exemplary user interfaces for managing the automatic use of credentials stored on an electronic device (e.g., device 100 or 300). Figures 18A to 18C are flowcharts illustrating how to manage the automatic use of credentials stored on an electronic device (e.g., device 100 or 300). The processes in Figures 18A to 18C are illustrated using the user interfaces in Figures 17A to 17J. ●Figures 20A to 20T below show exemplary user interfaces for revealing organized information. Figures 21A to 21C are flowcharts illustrating how to reveal organized information. The processes in Figures 21A to 21C are illustrated using the user interfaces in Figures 20A to 20T. ●Figures 23A to 23FF below show exemplary user interfaces for providing various unlocking modes on an electronic device. Figures 24A to 24D are flowcharts illustrating how to provide various unlocking modes on an electronic device. The processes in Figures 24A to 24D are illustrated using the user interfaces in Figures 23A to 23FF. ●Figures 26A to 26X below show exemplary user interfaces for controlling access to device information and functions, and for unlocking the device. Figures 27A to 27D are flowcharts showing how to unlock access to the device and its functions. The processes in Figures 27A to 27D are illustrated using the user interfaces in Figures 26A to 26X. ●Figures 29A to 29Y below show exemplary user interfaces for unlocking an application or device in a context-dependent manner. Figures 30A to 30D are flowcharts illustrating how to unlock an application or device in a context-dependent manner. The user interfaces in Figures 29A to 29Y are used to illustrate the processes in Figures 30A to 30D. Example device

[0082] Here, embodiments shown in the accompanying drawings will be referred to in detail. The following detailed description includes numerous specific details to provide a complete understanding of the various embodiments described. However, it will be apparent to those skilled in the art that the various embodiments described can be practiced without these specific details. In other examples, well-known methods, procedures, components, circuits, and networks are not described in detail so as not to unnecessarily obscure the aspects of the embodiments.

[0083] In this specification, terms such as "first," "second," etc., are used to describe various elements in some embodiments, but it will be understood that these elements should not be limited by those terms. These terms are used solely to distinguish one element from another. For example, without departing from the scope of the various embodiments described, a first contact may be referred to as a second contact, and similarly, a second contact may be referred to as a first contact. Both the first and second contacts are contacts, but they are not the same contact.

[0084] The terminology used in the description of the various embodiments described herein is intended solely to describe specific embodiments and not to limit them. Where used in the various described embodiments and in the appended claims, the singular forms “a,” “an,” and “the” are intended to also include the plural form unless the context otherwise explicitly indicates. Where used herein, the term “and / or” should also be understood to refer to and include all possible combinations of one or more of the related enumerated items. Furthermore, where used herein, the terms “includes,” “comprises,” and / or “comprising” specify the presence of a described feature, integer, step, operation, element, and / or component, but should not be understood to exclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.

[0085] As used herein, the term "if" is interpreted, at its discretion and in context, to mean "when," "upon," "in response to determining," or "in response to detecting." Similarly, the phrases "if it is determined" or "if (a stated condition or event) is detected" are interpreted, at its discretion and in context, to mean "upon determining," "in response to determining," "upon detecting (the stated condition or event)," or "in response to detecting (the stated condition or event)."

[0086] Embodiments of electronic devices, user interfaces for such devices, and related processes for using such devices are described. In some embodiments, the device is a portable communication device, such as a mobile phone, which also includes other functions, such as PDA functionality and / or music playback functionality. Exemplary embodiments of portable multifunction devices include, without limitation, the iPhone®, iPod Touch®, and iPad® devices of Apple Inc., Cupertino, California. Other portable electronic devices, such as laptop or tablet computers with touch-sensitive surfaces (e.g., touchscreen displays and / or touchpads), may also be used optionally. It should also be understood that in some embodiments, the device is not a portable communication device but a desktop computer with touch-sensitive surfaces (e.g., touchscreen displays and / or touchpads).

[0087] The following discussion describes an electronic device comprising a display and a touch-sensitive surface. However, please understand that this electronic device may optionally include one or more other physical user interface devices such as a physical keyboard, mouse, and / or joystick.

[0088] The device generally supports a variety of applications, including drawing applications, presentation applications, word processing applications, website creation applications, disk authoring applications, spreadsheet applications, game applications, telephone applications, video conferencing applications, email applications, instant messaging applications, training support applications, photo management applications, digital camera applications, digital video camera applications, web browsing applications, digital music playback applications, and / or digital video playback applications.

[0089] Various applications running on this device optionally use at least one common physical user interface device, such as a touch-sensitive surface. One or more functions of the touch-sensitive surface and the corresponding information displayed on the device are optionally adjusted and / or modified from one application to the next, and / or within the corresponding applications. In this manner, the device's common physical architecture (such as the touch-sensitive surface) optionally supports various applications that have an intuitive and transparent user interface for the user.

[0090] Here, we turn our attention to embodiments of portable devices equipped with a touch-sensitive display. Figure 1A is a block diagram of a portable multifunction device 100 equipped with a touch-sensitive display 112 according to several embodiments. The touch-sensitive display 112 is sometimes referred to for convenience as a “touchscreen” and is known or referred to as a “touch-sensitive display system.” Device 100 includes a memory 102 (optionally including one or more computer-readable storage media), a memory controller 122, one or more processing units (CPUs) 120, a peripheral device interface 118, an RF circuit 108, an audio circuit 110, a speaker 111, a microphone 113, an input / output (I / O) subsystem 106, other input or control devices 116, and an external port 124. Device 100 optionally includes one or more optical sensors 164. Device 100 optionally includes one or more intensity sensors 165 for detecting the intensity of contact on Device 100 (e.g., a touch-sensitive surface such as the touch-sensitive display system 112 of Device 100). Device 100 optionally includes one or more tactile output generators 167 for generating tactile output on Device 100 (e.g., generating tactile output on a touch-sensitive surface such as the touch-sensitive display system 112 of Device 100 or the touchpad 355 of Device 300). These components optionally communicate via one or more communication buses or signal lines 103.

[0091] As used herein and in the claims, the term “strength” of contact on a touch-sensitive surface refers to the force or pressure (force per unit area) of contact (e.g., finger contact) on the touch-sensitive surface, or a substitute for the force or pressure of contact on the touch-sensitive surface. The strength of contact has a numerical range, including at least four different numerical values, and more typically including hundreds or more different numerical values ​​(e.g., at least 256). The strength of contact is determined (or measured) optionally using various methods and various sensors, or combinations of sensors. For example, one or more sensors placed below or adjacent to the touch-sensitive surface are optionally used to measure the force at various points on the touch-sensitive surface. In some implementations, force measurements from multiple force sensors are combined (e.g., weighted average) to determine the estimated force of contact. Similarly, the pressure-sensitive tip of a stylus is optionally used to determine the pressure of the stylus on the touch-sensitive surface. Alternatively, the size and / or change in the contact area detected on the touch-sensitive surface, the capacitance and / or change in the touch-sensitive surface adjacent to the contact, and / or the resistance and / or change in the touch-sensitive surface adjacent to the contact may be optionally used as a substitute for the force or pressure of the contact on the touch-sensitive surface. In some implementations, the substitute measurement of the force or pressure of the contact is used directly to determine whether an intensity threshold is exceeded (e.g., the intensity threshold is described in units corresponding to the substitute measurement). In some implementations, the substitute measurement of the force or pressure of the contact is converted to an estimated force or pressure, and this estimated force or pressure is used to determine whether an intensity threshold is exceeded (e.g., the intensity threshold is a pressure threshold measured in units of pressure).

[0092] As used herein and in the claims, the term “tactile output” means a physical displacement of the device relative to its previous position, a physical displacement of a component of the device (e.g., a touch-sensitive surface) relative to another component of the device (e.g., a housing), or a displacement of a component relative to the center of mass of the device, which will be detected by the user through the user’s sense of touch. For example, in a situation where the device or a component of the device is in contact with the touch-sensitive surface of the user (e.g., the user’s fingers, palm, or other part of their hand), the tactile output generated by the physical displacement will be interpreted by the user as a tactile sensation corresponding to a perceived change in the physical properties of the device or a component of the device. For example, movement of a touch-sensitive surface (e.g., a touch-sensitive display or trackpad) may be optionally interpreted by the user as a “down-click” or “up-click” of a physical actuator button. In some cases, the user may feel a tactile sensation such as a “down-click” or “up-click” even when there is no movement of a physical actuator button associated with a touch-sensitive surface that is physically pressed (e.g., displaced) by the user’s movement. As another example, movement of a touch-sensitive surface can be optionally interpreted or perceived by the user as "roughness" of the touch-sensitive surface, even when there is no change in the smoothness of the touch-sensitive surface. Such user interpretations of touch depend on the individual user's sensory perception, but there are many touch sensory perceptions common to the majority of users. Therefore, when a tactile output is described as corresponding to a user's specific sensory perception (e.g., "up-click," "down-click," "roughness"), unless otherwise stated, the generated tactile output corresponds to the physical displacement of the device or its components that produce the described sensory perception of a typical (or average) user.

[0093] Device 100 is merely one embodiment of a portable multifunction device, and it should be understood that Device 100 may optionally have more or fewer components than those shown, or may optionally have two or more components in any combination, or may optionally have different configurations or arrangements of components. The various components shown in Figure 1A may be implemented in hardware, software, or a combination of both hardware and software, including one or more signal processing and / or application-specific integrated circuits.

[0094] Memory 102 optionally includes high-speed random-access memory and optionally includes non-volatile memory such as one or more magnetic disk storage devices, flash memory devices, or other non-volatile semiconductor memory devices. Access to memory 102 by other components of device 100, such as the CPU 120 and peripheral interface 118, is optionally controlled by the memory controller 122.

[0095] The input and output peripherals of this device can be connected to the CPU 120 and memory 102 using the peripheral interface 118. One or more processors 120 run or execute various software programs and / or instruction sets stored in memory 102 in order to perform various functions for device 100 and to perform data processing.

[0096] In some embodiments, the peripheral interface 118, CPU 120, and memory controller 122 are optionally implemented on a single chip, such as chip 104. In some other embodiments, they are optionally implemented on separate chips.

[0097] The RF (radio frequency) circuit 108 transmits and receives RF signals, also known as electromagnetic signals. The RF circuit 108 converts electrical signals to electromagnetic signals, or electromagnetic signals to electrical signals, and communicates with communication networks and other communication devices via electromagnetic signals. The RF circuit 108 optionally includes, but is not limited to, an antenna system, an RF transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a CODEC chipset, a subscriber identification module (SIM) card, memory, and other well-known circuits for performing the above functions. The RF circuit 108 optionally communicates wirelessly with networks such as the Internet, also known as the Internet of Things (WWW), intranets such as cellular telephone networks and / or wireless networks, wireless local area networks (LANs) and / or metropolitan area networks (MANs), and other devices. Wireless communication technologies include Global System for Mobile Communications (GSM®), Enhanced Data GSM Environment (EDGE®), High-Speed ​​Downlink Packet Access (HSDPA), High-Speed ​​Uplink Packet Access (HSUPA), Evolution, Data-Only (EV-DO), HSPA, HSPA+, Dual-Cell HSPA (DC-HSPDA), Long-Term Evolution (LTE®), Short-Range Wireless Communication (NEC), Wideband Code Division Multiple Access (W-CDMA), Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), and Bluetooth. (Registered trademark)The present application may optionally use any of several communication standards, protocols, and technologies, including, but not limited to, Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, and / or IEEE 802.11n), Voice over Internet Protocol (VoIP), Wi-MAX®, protocols for email (e.g., Internet Message Access Protocol (IMAP) and / or Post Office Protocol (POP)), instant messaging (e.g., extensible messaging and presence protocol (XMPP), Session Initiation Protocol for Instant Messaging and Presence Leveraging Extensions (SIMPLE), Instant Messaging and Presence Service (IMPS)), and / or Short Message Service (SMS), or any other suitable communication protocols, including communication protocols not yet developed as of the filing date of this application.

[0098] The audio circuit 110, speaker 111, and microphone 113 provide an audio interface between the user and the device 100. The audio circuit 110 receives audio data from the peripheral interface 118, converts the audio data into an electrical signal, and transmits the electrical signal to the speaker 111. The speaker 111 converts the electrical signal into human audible sound waves. The audio circuit 110 also receives the electrical signal converted from the sound waves by the microphone 113. The audio circuit 110 converts the electrical signal into audio data and sends the audio data to the peripheral interface 118 for processing. The audio data is optionally taken in by the peripheral interface 118 from memory 102 and / or RF circuit 108, and / or sent back to memory 102 and / or RF circuit 108. In some embodiments, the audio circuit mechanism 110 further includes a headset jack (e.g., 212 in Figure 2). The headset jack provides an interface between the audio circuit 110 and a detachable audio input / output peripheral, such as output-only headphones or a headset that has both output (e.g., headphones for one or both ears) and input (e.g., a microphone).

[0099] The I / O subsystem 106 connects the input / output peripherals of device 100, such as the touchscreen 112 and other input control devices 116, to the peripheral interface 118. The I / O subsystem 106 optionally includes a display controller 156, an optical sensor controller 158, an intensity sensor controller 159, a haptic feedback controller 161, and one or more input controllers 160 for other input or control devices. One or more input controllers 160 receive / transmit electrical signals to / from the other input or control devices 116. The other input control devices 116 optionally include physical buttons (e.g., push buttons, rocker buttons), dials, slider switches, joysticks, click wheels, etc. In some alternative embodiments, one or more input controllers 160 are optionally connected to (or not connected to) any of the following: a keyboard, an infrared port, a USB port, and a pointer device such as a mouse. One or more buttons (e.g., 208 in Figure 2) optionally include up / down buttons for adjusting the volume of speaker 111 and / or microphone 113. One or more buttons optionally include push buttons (e.g., 206 in Figure 2).

[0100] The touch-sensitive display 112 provides input and output interfaces between the device and the user. The display controller 156 receives and / or transmits electrical signals to and from the touchscreen 112. The touchscreen 112 displays visual output to the user. The visual output optionally includes graphics, text, icons, videos, and any combination thereof (collectively referred to as “graphics”). In some embodiments, some or all of the visual output corresponds to user interface objects.

[0101] The touchscreen 112 has a touch-sensing surface, sensor, or set of sensors that accept user input based on tactile and / or tactile contact. The touchscreen 112 and the display controller 156 (along with any associated modules and / or instruction sets in memory 102) detect contact (and any action or interruption of contact) on the touchscreen 112 and translate the detected contact into interaction with user interface objects displayed on the touchscreen 112 (e.g., one or more soft keys, icons, web pages, or images). In one exemplary embodiment, the contact between the touchscreen 112 and the user corresponds to the user's finger.

[0102] The touchscreen 112 optionally uses LCD (liquid crystal display) technology, LPD (polymer light-emitting display) technology, or LED (light-emitting diode) technology, but other display technologies are used in other embodiments. The touchscreen 112 and display controller 156 optionally detect touch and any movement or interruption using any of several currently known or future-developed touch sensing technologies, including but not limited to capacitive technology, resistive technology, infrared technology, and surface ultrasonic technology, as well as other proximity sensor arrays or other elements for determining one or more contact points with the touchscreen 112. In one exemplary embodiment, projected mutual capacitance sensing technology is used, as seen in iPhone®, iPod Touch®, and iPad® from Apple Inc. of Cupertino, California.

[0103] The touchscreen 112 optionally has a video resolution greater than 100 dpi. In some embodiments, the touchscreen has a video resolution of approximately 160 dpi. The user optionally touches the touchscreen 112 using any suitable object or accessory, such as a stylus or finger. In some embodiments, the user interface is designed to function primarily with finger-based touch and gestures, which may be less precise than stylus-based input due to the larger contact area of ​​the finger on the touchscreen. In some embodiments, the device translates rough finger-based input into precise pointer / cursor positions or commands to perform user-desired actions.

[0104] In some embodiments, in addition to the touchscreen, the device 100 optionally includes a touchpad (not shown) for activating or deactivating specific functions. In some embodiments, the touchpad is a touch-sensitive area of ​​the device that, unlike the touchscreen, does not display a visual output. The touchpad is optionally a touch-sensitive surface separate from the touchscreen 112, or an extension of the touch-sensitive surface formed by the touchscreen.

[0105] Device 100 also includes a power system 162 for supplying power to various components. The power system 162 optionally includes a power management system, one or more power sources (e.g., a battery, alternating current (AC)), a recharge system, a power failure detection circuit, a power converter or inverter, a power status indicator (e.g., a light-emitting diode (LED)), and any other components associated with the generation, management, and distribution of power within the portable device.

[0106] Device 100 also optionally includes one or more optical sensors 164. Figure IA shows the optical sensors coupled to an optical sensor controller 158 in the I / O subsystem 106. The optical sensors 164 optionally include a charge-coupled device (CCD) or a complementary metal-oxide-semiconductor (CMOS) phototransistor. The optical sensors 164 receive light from the environment projected through one or more lenses and convert that light into data representing an image. In use with an imaging module 143 (also referred to as a camera module), the optical sensors 164 optionally capture still images or video. In some embodiments, the optical sensors are located on the back of device 100, opposite the touchscreen display 112 on the front of the device, so that the touchscreen display can be enabled as a viewfinder for acquiring still images and / or video. In some embodiments, another optical sensor is located on the front of the device so that the user's image is optionally acquired for video conferencing while the user views other video conference participants on the touchscreen display.

[0107] Device 100 also optionally includes one or more contact strength sensors 165. Figure 1A shows the contact strength sensors coupled to a strength sensor controller 159 in the I / O subsystem 106. The contact strength sensors 165 optionally include one or more piezoresistive strain gauges, capacitive force sensors, electric force sensors, pressure-power sensors, optical force sensors, capacitive touch-sensing surfaces, or other strength sensors (e.g., sensors used to measure the force (or pressure) of contact on a touch-sensing surface). The contact strength sensors 165 receive contact strength information (e.g., pressure information or a proxy for pressure information) from the environment. In some embodiments, at least one contact strength sensor is located juxtaposed with or in close proximity to a touch-sensing surface (e.g., a touch-sensing display system 112). In some embodiments, at least one contact strength sensor is located on the back of Device 100, opposite the touchscreen display 112 located on the front of Device 100.

[0108] Device 100 also optionally includes one or more proximity sensors 166. Figure 1A shows the proximity sensor 166 connected to the peripheral interface 118. Alternatively, the proximity sensor 166 is connected to the input controller 160 in the I / O subsystem 106. In some embodiments, if the multifunction device is positioned near the user's ear (for example, when the user is making a phone call), the proximity sensor turns off and disables the touchscreen 112.

[0109] Device 100 also optionally includes one or more tactile output generators 167. Figure 1A shows a tactile output generator connected to a tactile feedback controller 161 in the I / O subsystem 106. The tactile output generator 167 optionally includes one or more electroacoustic devices such as a speaker or other sound component, and / or electromechanical devices that convert energy into linear motion, such as a motor, solenoid, electroactive polymer, piezoelectric actuator, electrostatic actuator, or other tactile output component (e.g., a component that converts an electrical signal into a tactile output on the device). The contact intensity sensor 165 receives a tactile feedback generation command from the tactile feedback module 133 and generates a tactile output on device 100 that can be sensed by the user of device 100. In some embodiments, at least one tactile output generator is positioned juxtaposed with or adjacent to a touch-sensing surface (e.g., a touch-sensing display system 112) and optionally generates a tactile output by moving the touch-sensing surface vertically (e.g., inward / outward from the surface of device 100) or laterally (e.g., in the forward / backward direction on the same plane as the surface of device 100). In some embodiments, at least one tactile output generator sensor is positioned on the back of device 100, opposite the touchscreen display 112 which is positioned on the front of device 100.

[0110] Device 100 also optionally includes one or more accelerometers 168. Figure 1A shows the accelerometer 168 connected to a peripheral interface 118. Alternatively, the accelerometer 168 may optionally be connected to an input controller 160 in the I / O subsystem 106. In some embodiments, information is displayed on the touchscreen display in portrait or landscape view based on an analysis of data received from one or more accelerometers. Device 100 may optionally include, in addition to the accelerometer(s) 168, a magnetometer (not shown) and a GPS (or GLONASS or other global navigation system) receiver (not shown) for obtaining information about the location and orientation of Device 100 (e.g., portrait or landscape).

[0111] In some embodiments, device 100 also includes (or communicates with) one or more fingerprint sensors 169. Figure 1A shows a fingerprint sensor 169 connected to a peripheral interface 118. Alternatively, the fingerprint sensor 169 is optionally connected to an input controller 160 in the I / O subsystem 106. However, in one common embodiment, the fingerprint identification operation is performed using protected, dedicated hardware (e.g., one or more processors, memory and / or communication buses) with additional security features to enhance the security of the fingerprint information determined by the fingerprint sensor. The fingerprint sensors used herein are sensors capable of distinguishing fingerprint features in the ridges and valleys of the skin, such as those found on the fingers and toes of humans (also referred to as “minuscia features”). The fingerprint sensor may distinguish fingerprint features using any of a variety of techniques, including but not limited to visual fingerprint imaging, ultrasonic fingerprint imaging, active capacitive fingerprint imaging, and passive capacitive fingerprint imaging. In addition to distinguishing fingerprint features in a fingerprint, in some embodiments, the fingerprint sensor 169 can track the movement of fingerprint features over time, thereby determining / characterizing the movement of a fingerprint over time on the fingerprint sensor. Although the fingerprint sensor (e.g., fingerprint sensor 169) in Figure 1A is shown separately from the touch-sensing surface (e.g., touch-sensing display system 112), in some implementations, the touch-sensing surface (e.g., touch-sensing display system 112) will be understood to have a spatial resolution with sufficient height to detect fingerprint features formed by individual fingerprint ridges and will be used as a fingerprint sensor in place of, or in addition to, a separate fingerprint sensor (e.g., fingerprint sensor 169). In some embodiments, the device 100 includes a set of one or more orientation sensors used to determine the orientation of a finger or hand (e.g., the orientation of a finger on the fingerprint sensor 169) on or near the device.In addition, in some embodiments, a set of one or more orientation sensors is used in addition to, or instead of, a fingerprint sensor to detect the rotation of a contact interacting with the device (for example, in one or more of the methods described below, instead of using a fingerprint sensor to detect the rotation of a fingerprint / contact, a set of one or more orientation sensors is used to detect the rotation of a contact containing a fingerprint, with or without detection of fingerprint features).

[0112] In some embodiments, the comparison of fingerprint features with those of a detected fingerprint and those of a stored fingerprint is performed by protected, dedicated hardware (e.g., one or more processors, memory, and / or communication buses) separate from the processor 120 to enhance the security of the fingerprint data generated, stored, and processed by the fingerprint sensor 169. In some embodiments, the comparison of fingerprint features with those of a registered fingerprint and those of a stored fingerprint is performed by the processor 120 using a fingerprint analysis module 131.

[0113] In some embodiments, during the registration process, the device (e.g., a separate secure module 146 connected to a fingerprint analysis module 131 or one or more fingerprint sensors 169) collects biometric information about one or more of the user's fingerprints (e.g., identifying the relative positions of multiple minisure points in the user's fingerprint). After the registration process is complete, the biometric information is stored in the device (e.g., in the secure fingerprint module 146) for later use when authenticating the detected fingerprint. In some embodiments, the biometric information stored in the device excludes fingerprint images and information that could potentially reconstruct the fingerprint image, so that fingerprint images are not inadvertently made available if the device's security is compromised. In some embodiments, during the authentication process, the device (e.g., a fingerprint analysis module 131 or a separate secure model 146 communicating with one or more fingerprint sensors 169) determines whether the finger input detected by the fingerprint sensor includes a fingerprint that matches a registered fingerprint by collecting biometric information about the fingerprint detected on the fingerprint sensor (e.g., identifying the relative positions of multiple minisure points in the fingerprint detected on the fingerprint sensor) and comparing the biometric information corresponding to the detected fingerprint with the biometric information corresponding to one or more registered fingerprints. In some embodiments, comparing the biometric information corresponding to the detected fingerprint with the biometric information corresponding to one or more registered fingerprints includes comparing the types and positions of minisure points in the biometric information corresponding to the detected fingerprint with the types and positions of minisure points in the biometric information corresponding to the registered fingerprints. However, the determination of whether the finger input includes a fingerprint that matches a previously registered fingerprint that has been registered using the device is optionally performed using one of several well-known fingerprint authentication methods for determining whether the detected fingerprint matches a registered fingerprint.

[0114] In some embodiments, the software components stored in memory 102 include an operating system 126, a communication module (or instruction set), a contact / motion module (or instruction set) 130, a fingerprint analysis module 131, a graphics module (or instruction set) 132, a text input module (or instruction set) 134, a Global Positioning System (GPS) module (or instruction set) 135, and an application (or instruction set) 136. Furthermore, in some embodiments, as shown in Figures 1A and 3, memory 102 stores device / global internal state 157. The device / global internal state 157 includes one or more of the following: active application state, indicating which application is active, if any applications are currently active; display state, indicating which applications, views, or other information occupy various areas of the touchscreen display 112; sensor state, including information obtained from various sensors and input control devices 116 of the device; and location information relating to the location and / or orientation of the device.

[0115] In some embodiments, credential information is stored as secure credential information 145. The secure credential information optionally includes credentials for a user account (e.g., username and password, billing information, address information). In some embodiments, credential information for one or more different applications is stored in a secure central location on the device so that the credential information is accessible from various applications. In some embodiments, credential information associated with a particular application (e.g., username and password or billing information entered within a particular application) is stored together with that particular application (e.g., username and password for authorizing purchases in a store application are stored together with the store application to facilitate access by the store application). In some embodiments, other security information (e.g., decryption keys for decrypting encrypted content stored on the device) is stored together with the secure credential information 145 or in another secure location on the device.

[0116] An operating system 126 (for example, an embedded operating system such as Darwin®, RTXC®, LINUX®, UNIX®, OS X®, WINDOWS®, or VxWorks®) includes various software components and / or drivers for controlling and managing common system tasks (e.g., memory management, storage device control, power management, etc.) and facilitates communication between various hardware and software components.

[0117] The communication module 128 facilitates communication with other devices via one or more external ports 124 and includes various software components for processing data received by the RE circuit 108 and / or external ports 124. The external ports 124 (e.g., Universal Serial Bus (USB), FireWire®, etc.) are adapted to connect to other devices directly or indirectly via a network (e.g., the Internet, Wi-Fi, etc.). In some embodiments, the external ports are multi-pin (e.g., 30-pin) connectors identical to, or similar to, and / or compatible with, the 30-pin connector used on iPod (trademark of Apple Inc.) devices.

[0118] The contact / motion module 130 optionally detects contact with the touchscreen 112 (in conjunction with the display controller 156) and contact with other touch-sensitive devices (e.g., a touchpad or physical click wheel). The contact / motion module 130 includes various software components for performing various operations related to contact detection, such as determining whether contact has occurred (e.g., detecting a finger-down event), determining the intensity of the contact (e.g., the force or pressure of the contact, or a substitute for the force or pressure of the contact), determining whether there is contact movement and tracking of movement across the touch-sensitive surface (e.g., detecting one or more finger-drag events), and determining whether contact has been terminated (e.g., detecting a finger-up event or interruption of contact). The contact / motion module 130 receives contact data from the touch-sensitive surface. Determining the movement of the contact point represented by a series of contact data optionally includes determining the speed (magnitude), velocity (magnitude and direction), and / or acceleration (change in magnitude and / or direction) of the contact point. These actions can be optionally applied to a single contact (e.g., a single finger contact) or multiple simultaneous contacts (e.g., "multi-touch" / multiple finger contacts). In some embodiments, the contact / movement module 130 and the display controller 156 detect contact on the touchpad.

[0119] In some embodiments, the contact / movement module 130 uses a set of one or more intensity thresholds to determine whether an action has been performed by the user (for example, whether the user has "clicked" on an icon). In some embodiments, at least a subset of the intensity thresholds is determined according to software parameters (for example, the intensity thresholds are not determined by activation thresholds of a particular physical actuator and can be adjusted without changing the physical hardware of device 100). For example, the mouse "click" threshold for a trackpad or touchscreen display can be set to one of a wide range of default thresholds without changing the trackpad or touchscreen display hardware. In addition, in some implementations, the user of the device is provided with software settings to adjust one or more of the set of intensity thresholds (for example, by adjusting individual intensity thresholds and / or by adjusting multiple intensity thresholds immediately after a system-level click of the "intensity" parameter).

[0120] The contact / movement module 130 optionally detects gesture input from the user. Different gestures on the touch-sensitive surface have different contact patterns (e.g., different movement, timing, and / or intensity of detected contact). Therefore, gestures are optionally detected by detecting a specific contact pattern. For example, detecting a finger tap gesture involves detecting a finger-down event, followed by a finger-lift-off event at the same location (or substantially the same location) as the finger-down event (e.g., at the icon's position). In another embodiment, detecting a finger-swipe gesture on the touch-sensitive surface involves detecting a finger-down event, followed by one or more finger-drag events, and then a finger-up (lift-off) event.

[0121] The fingerprint analysis module 131 optionally detects user finger input on the fingerprint sensor, determines whether the finger input includes a fingerprint corresponding to a registered fingerprint registered using the device, and / or detects the movement of the fingerprint corresponding to a finger gesture. In some embodiments, fingerprint registration and comparison of the detected fingerprint with a registered fingerprint are performed by a secure fingerprint analysis module 146 communicating with one or more fingerprint sensors 169, and the secure fingerprint analysis module 146 provides the fingerprint analysis module 131 with information indicating whether the detected fingerprint matches a registered fingerprint without providing the fingerprint analysis module 131 with biometric information about the detected or registered fingerprint (for example, to maintain the security of biometric information about the detected and registered fingerprints). In some embodiments, information about the movement of the fingerprint during finger input and the number of finger-up or finger-down events is also provided to the fingerprint analysis module 131 by the secure fingerprint analysis module 146. In some embodiments, information about finger input is used by the fingerprint analysis module 131 to respond to the finger input (for example, by unlocking the device, unlocking a device function, displaying previously organized information, or performing an action based on the behavior of the fingerprint on the fingerprint sensor).

[0122] The graphics module 132 includes various known software components for rendering and displaying graphics on the touchscreen 112 or other display, including components for modifying the visual effects of the displayed graphics (e.g., brightness, transparency, saturation, contrast, or other visual properties). As used herein, the term “graphics” includes, but is not limited to, any objects that can be displayed to a user, such as text, web pages, icons (including user interface objects such as soft keys), digital images, videos, and animations.

[0123] In some embodiments, the graphics module 132 stores data representing the graphics to be used. Each graphic is optionally assigned a corresponding code. The graphics module 132 receives one or more codes specifying the graphics to be displayed, along with coordinate data and other graphic property data, from an application or the like as needed, and generates screen image data to be output to the display controller 156.

[0124] The haptic feedback module 133 includes various software components for generating instructions used by a haptic output generator(s) 167 to generate haptic outputs at one or more locations on the device 100 in response to user interaction with the device 100.

[0125] The text input module 134 is optionally a component of the graphics module 132 and provides a soft keyboard for entering text in various applications (e.g., contacts 137, email 140, IM 141, browser 147, and any other applications that require text input).

[0126] The GPS module 135 determines the device's location and provides this information for use in various applications (for example, to the telephone 138 for use in location-based dialing, to the camera 143 as picture / video metadata, and to applications that provide location-based services such as weather widgets, local yellow pages widgets, and map / navigation widgets).

[0127] Application 136 optionally includes the following modules (or sets of instructions), or subsets or supersets thereof: ●Contact module 137 (also called address book or contact list), ●Telephone module 138, ●Video conferencing module 139, ● Email client module 140, ● Instant messaging (IM) module 141, ●Training support module 142, ● Camera module 143 for still images and / or video images, ●Image management module 144, ● Browser module 147, ●Calendar module 148, ● A widget module 149 that optionally includes one or more of the following: weather widget 149-1, stock widget 149-2, calculator widget 149-3, alarm clock widget 149-4, dictionary widget 149-5, other widgets acquired by the user, and user-created widgets 149-6. ●Widget creation module 150 for creating user-created widget 149-6, ● Search module 151, ● A video and music playback module 152, which is optionally composed of a video playback module and a music playback module. ●Memo Module 153, ●Map module 154 and / or ● Online video module 155.

[0128] Examples of other applications 136 that may be optionally stored in memory 102 include other word processing applications, other image editing applications, drawing applications, presentation applications, Java®-enabled applications, encryption, digital rights management, speech recognition, and speech duplication.

[0129] Together with the touchscreen 112, display controller 156, contact module 130, graphics module 132, and text input module 134, the contact module 137 is optionally used to manage an address book or contact list (stored, for example, in the application internal state 192 of the contact module 137 in memory 102 or memory 370), which includes adding or removing names from the address book, associating telephone numbers, email addresses, addresses, or other information with names, associating images with names, categorizing and sorting names, and providing telephone numbers or email addresses to initiate and / or facilitate communication by telephone 138, video conferencing 139, email 140, or IM 141.

[0130] Together with the RF circuit 108, audio circuit 110, speaker 111, microphone 113, touchscreen 112, display controller 156, contact module 130, graphics module 132, and text input module 134, the telephone module 138 is optionally used to input a telephone number and a corresponding set of characters, access one or more telephone numbers in the address book 137, modify an entered telephone number, dial a corresponding telephone number, conduct a conversation, and disconnect or hang up when the conversation is complete. As described above, wireless communication optionally uses one of several communication standards, protocols, and technologies.

[0131] Together with the RF circuit 108, audio circuit 110, speaker 111, microphone 113, touchscreen 112, display controller 156, light sensor 164, light sensor controller 158, contact module 130, graphics module 132, text input module 134, contact list 137, and telephone module 138, the video conferencing module 139 includes executable commands for starting, conducting, and ending video conferences between the user and one or more other participants, according to user instructions.

[0132] Together with the RF circuit 108, touchscreen 112, display controller 156, contact module 130, graphics module 132, and text input module 134, the email client module 140 includes executable commands for creating, sending, receiving, and managing emails in response to user instructions. Together with the image management module 144, the email client module 140 makes it very easy to create still images or videos captured by the camera module 143 and send them via email.

[0133] Together with the RF circuit 108, touchscreen 112, display controller 156, contact module 130, graphics module 132, and text input module 134, the instant messaging module 141 includes executable instructions for entering instant messages and corresponding strings, modifying entered characters, sending corresponding instant messages (e.g., using the Short Message Service (SMS) or Multimedia Messaging Service (MMS) protocol for telephone-based instant messaging, or using XMPP, SIMPLE, or IMPS for internet-based instant messaging), and receiving and displaying instant messages. In some embodiments, transmitted and / or received instant messages optionally include graphics, photographs, audio files, video files, and / or other attachments, as supported by MMS and / or Enhanced Messaging Services (EMS). As used herein, “instant messaging” refers to both telephone-based messages (e.g., messages sent using SMS or MMS) and internet-based messages (e.g., messages sent using XMPP, SIMPLE, or IMPS).

[0134] Together with the RF circuit 108, touchscreen 112, display controller 156, contact module 130, graphics module 132, text input module 134, GPS module 135, map module 154, and music playback module 146, the training support module 142 includes executable commands for generating training (e.g., having time, distance, and / or calorie consumption targets), communicating with training sensors (sports devices), receiving training sensor data, measuring sensors used to monitor training, selecting and playing music for training, and displaying, storing, and transmitting training data.

[0135] Together with the touchscreen 112, display controller 156, light sensor(s) 164, light sensor controller 158, contact module 130, graphics module 132, and image management module 144, the camera module 143 includes executable instructions for capturing still images or videos (including video streams) and storing them in memory 102, modifying the characteristics of still images or videos, or deleting still images or videos from memory 102.

[0136] Together with the touchscreen 112, display controller 156, contact module 130, graphics module 132, text input module 134, and camera module 143, the image management module 144 includes executable commands for arranging, modifying (e.g., editing), and otherwise manipulating, labeling, deleting, presenting (e.g., in a digital slideshow or album), and storing still images and / or videos.

[0137] Together with the RF circuit 108, touchscreen 112, display system controller 156, contact module 130, graphics module 132, and text input module 134, the browser module 147 includes executable instructions for browsing the Internet in accordance with user instructions, including searching for, linking, receiving, and displaying web pages or parts thereof, as well as attachments and other files linked to web pages.

[0138] Together with the RF circuit 108, touchscreen 112, display system controller 156, contact module 130, graphics module 132, text input module 134, email client module 140, and browser module 147, the calendar module 148 includes executable instructions for creating, displaying, modifying, and storing calendars and data associated with calendars (e.g., calendar entries, to-do lists, etc.) in accordance with user instructions.

[0139] In connection with RF circuit 108, touch screen 112, display system controller 156, touch module 130, graphic module 132, text input module 134, and browser module 147, widget module 149 is a mini-application (e.g., weather widget 149-1, stock price widget 149-2, calculator widget 149-3, alarm clock widget 149-4, and dictionary widget 149-5) that is optionally downloaded and used by a user, or a mini-application created by the user (e.g., user-created widget 149-6). In some embodiments, the widget includes HTML (HyperText Markup Language) files, CSS (Cascading Style Sheets) files, and JavaScript files. In some embodiments, the widget includes XML (Extensible Markup Language) files and JavaScript® files (e.g., Yahoo!® widgets).

[0140] In combination with RF circuit 108, touch screen 112, display system controller 156, touch module 130, graphic module 132, text input module 134, and browser module 147, widget creation module 150 is optionally used by a user to create a widget (e.g., change a user-specified location on a web page to a widget).

[0141] In combination with touch screen 112, display system controller 156, touch module 130, graphic module 132, and text input module 134, search module 151 includes executable instructions for searching, in accordance with a user's instructions, for text, music, sounds, images, videos, and / or other files in memory 102 that match one or more search criteria (e.g., one or more user-specified search terms).

[0142] In combination with the touch screen 112, display system controller 156, contact module 130, graphic module 132, audio circuit 110, speaker 111, RF circuit 108, and browser module 147, the video and music playback module 152 includes executable instructions that enable a user to download and play recorded music or other sound files stored in one or more file formats such as MP3 or AAC files, and executable instructions for displaying, presenting, or otherwise playing videos (on the touch screen ......

[0143] In combination with the touch screen 112, display controller 156, contact module 130, graphic module 132, and text input module 134, the memo module 153 includes executable instructions for creating and managing memos, ToDo lists, etc. according to user instructions.

[0144] In combination with the RF circuit 108, touch screen 112, display system controller 156, contact module 130, graphic module 132, text input module 134, GPS module 135, and browser module 147, the map module 154 is optionally used to receive, display, modify, and store maps and data associated with the maps (e.g., driving directions, data about stores and other points of interest near a particular location or its vicinity, and other location-based data) according to user instructions.

[0145] Together with the touchscreen 112, display system controller 156, contact module 130, graphics module 132, audio circuit 110, speaker 111, RF circuit 108, text input module 134, email client module 140, and browser module 147, the online video module 155 includes instructions that enable the user to access, browse, receive (e.g., by streaming and / or downloading), play (e.g., on the touchscreen or on an external display connected via external port 124), send emails containing links to specific online videos, and manage them in other ways. In some embodiments, an instant messaging module 141, rather than the email client module 140, is used to send links to specific online videos.

[0146] Each of the modules and applications identified above corresponds to an executable instruction set and the method of this application (e.g., a method performed by a computer and other information processing methods described herein) for performing one or more of the above functions. These modules (i.e., instruction sets) do not need to be implemented as separate software programs, procedures, or modules, and therefore various subsets of these modules can be optionally combined or rearranged in various embodiments. In some embodiments, memory 102 optionally stores a subset of the identified modules and data structures described above. Furthermore, memory 102 optionally stores additional modules and data structures not described above.

[0147] In some embodiments, device 100 is a device in which the operation of a default set of functions on the device is performed exclusively via a touchscreen and / or touchpad. By using a touchscreen and / or touchpad as the primary input control device for the operation of device 100, the number of physical input control devices on device 100 (such as push buttons, dials, and similar devices) is optionally reduced.

[0148] A default set of functions, performed exclusively via the touchscreen and / or touchpad, optionally includes navigation between user interfaces. In some embodiments, the touchpad, when touched by the user, navigates the device 100 from any user interface displayed on the device 100 to the main menu, home menu, or root menu. In such embodiments, the “menu button” is implemented using the touchpad. In some other embodiments, the menu button is a physical push button or other physical input control device instead of a touchpad.

[0149] Figure 1B is a block diagram showing exemplary components for event processing according to several embodiments. In some embodiments, memory 102 (in Figure 1A) or 370 (in Figure 3) includes an event sorter 170 (e.g., in operating system 126) and corresponding applications 136-1 (e.g., any of the applications 137-13, 155, and 380-390 described above).

[0150] The event sorter 170 receives event information and determines the application 136-1 and the application view 191 of application 136-1 to which the event information is distributed. The event sorter 170 includes an event monitor 171 and an event dispatcher module 174. In some embodiments, application 136-1 includes an application internal state 192 that indicates the current application view(s) displayed on the touch-sensitive display 112 when the application is active or running. In some embodiments, the event sorter 170 uses a device / overall internal state 157 to determine the currently active application(s), and the event sorter 170 uses the application internal state 192 to determine the application view(s) to which the event information is distributed.

[0151] In some embodiments, the application internal state 192 includes additional information such as resume information used when the application 136-1 resumes execution, user interface state information indicating that information is displayed or ready to be displayed by the application 136-1, state queues to allow the user to return to a previous state or view of the application 136-1, and redo / undo queues for actions previously performed by the user.

[0152] The event monitor 171 receives event information from the peripheral interface 118, or optionally from the fingerprint analysis module 131. The event information includes information about sub-events (e.g., user touch on the touch-sensitive display 112 as part of a multi-touch gesture or finger input on the fingerprint sensor 169). The peripheral interface 118 transmits information received from the I / O subsystem 106 or from sensors such as the proximity sensor 166, one or more accelerometers 168, the fingerprint sensor 169, and / or the microphone 113 (via the audio circuit 110). The information received by the peripheral interface 118 from the I / O subsystem 106 includes information from the touch-sensitive display 112 or the touch-sensitive surface.

[0153] In some embodiments, the event monitor 171 sends a request to the peripheral interface 118 at predetermined intervals. In response, the peripheral interface 118 transmits event information. In other embodiments, the peripheral interface 118 transmits event information only when there is a significant event (e.g., exceeding a predetermined noise threshold and / or receiving input for longer than a predetermined time).

[0154] In some embodiments, the event sorter 170 also includes a hit view determination module 172 and / or an active event recognition determination module 173.

[0155] The hit view determination module 172 provides software procedures for determining where a sub-event occurred within one or more views when the touch-sensitive display 112 displays one or more views. A view consists of a control unit and other elements that the user can see on the display.

[0156] Another aspect of the user interface associated with an application is a set of views, which may be referred to herein as application views or user interface windows, in which information is displayed and touch-based gestures are performed. The application view (of the corresponding application) in which a touch is detected optionally corresponds to the program level within the application's program hierarchy or view hierarchy. For example, the lowest level view in which a touch is detected is optionally called a hit view, and the set of events recognized as appropriate input is optionally determined, at least in part, based on the hit view of the initial touch that initiates a touch-based gesture.

[0157] The hit view determination module 172 receives information associated with sub-events of touch-based gestures. If the application has multiple views organized hierarchically, the hit view determination module 172 identifies the hit view as the lowest-level view in the hierarchy that should process the sub-events. In most situations, the hit view is the lowest-level view where the first sub-event (i.e., the first sub-event in a sequence of sub-events that form an event or potential event) occurs. Once a hit view is identified by the hit view determination module, the hit view typically receives all sub-events associated with the same touch or input source that identified it as a hit view.

[0158] The active event recognition unit determination module 173 determines which view(s) in the view hierarchy should receive a particular sequence of sub-events. In some embodiments, the active event recognition unit determination module 173 determines that only the hit view should receive a particular sequence of sub-events. In other embodiments, the active event recognition unit determination module 173 determines that all views, including the physical location of the sub-event, are actively involved views, and therefore all actively involved views should receive a particular sequence of sub-events. In other embodiments, even if the touch sub-event is entirely confined to a region associated with a particular view, higher-level views in the hierarchy will remain actively involved views.

[0159] The event dispatcher module 174 transmits event information to an event recognition unit (e.g., an event recognition unit 180). In embodiments including an active event recognition unit determination module 173, the event dispatcher module 174 distributes the event information to the event recognition unit determined by the active event recognition unit determination module 173. In some embodiments, the event dispatcher module 174 stores the event information acquired by the corresponding event receiver module 182 in an event queue.

[0160] In some embodiments, the operating system 126 includes an event sorter 170. Alternatively, application 136-1 includes an event sorter 170. In yet another embodiment, the event sorter 170 is a standalone module or part of another module stored in memory 102, such as a contact / movement module 130.

[0161] In some embodiments, application 136-1 includes a plurality of event handlers 190 and one or more application views 191, each containing instructions for handling touch events occurring within each view of the application's user interface. Each application view 191 of application 136-1 includes one or more event recognition units 180. Typically, a corresponding application view 191 includes a plurality of event recognition units 180. In other embodiments, one or more event recognition units 180 are part of a separate module, such as a user interface kit (not shown) or a higher-level object from which application 136-1 inherits methods and other properties. In some embodiments, each event handler 190 includes one or more event data 179 received from a data updater 176, an object updater 177, a GUI updater 178, and / or an event sorter 170. The event handler 190 optionally uses or calls the data updater 176, object updater 177, or GUI updater 178 to update the application's internal state 192. Alternatively, one or more of the application views 191 include one or more respective event handlers 190. In some embodiments, one or more of the data updater 176, object updater 177, and GUI updater 178 are included within the corresponding application view 191.

[0162] The corresponding event recognition unit 180 receives event information (e.g., event data 179) from the event sorter 170 and identifies an event from that event information. The event recognition unit 180 includes an event receiving unit 182 and an event comparison unit 184. In some embodiments, the event recognition unit 180 further includes metadata 183 and at least a subset of event distribution instructions 188 (optionally including sub-event distribution instructions).

[0163] The event receiving unit 182 receives event information from the event sorter 170. The event information includes information about sub-events, such as touches or touch movements, or finger input or fingerprint movements. Depending on the sub-event, the event information may also include additional information, such as the location of the sub-event. When the sub-event involves touch movement, the event information may optionally further include the velocity and direction of the sub-event. In some embodiments, an event includes a rotation of the device from one direction to another (e.g., from portrait to landscape, or vice versa), and the event information includes corresponding information about the current orientation of the device (also called the device orientation).

[0164] The event comparison unit 184 compares event information with the definitions of predetermined events or sub-events, and based on this comparison, determines an event or sub-event, or determines or updates the state of an event or sub-event. In some embodiments, the event comparison unit 184 includes an event definition 186. The event definition 186 includes, for example, definitions of events such as event 1 (187-1), event 2 (187-2), etc. (e.g., a predetermined sequence of sub-events). In some embodiments, the sub-events in event 187 include, for example, touch start, touch end, touch move, touch cancel, multiple touches, fingerprint start, fingerprint end, fingerprint move, fingerprint authentication, and fingerprint authentication failure. In one example, the definition of event 1 (187-1) is a double-tap on a displayed object. The double-tap includes, for example, a first touch (touch start) at a predetermined stage on the displayed object, a first lift-off (touch end) at a predetermined stage, a second touch (touch start) at a predetermined stage on the displayed object, and a second lift-off (touch end) at a predetermined stage. In another embodiment, the definition of event 2 (187-2) is dragging a displayed object. Dragging includes, for example, a touch (or contact) at a predetermined stage on the displayed object, movement of the touch across the touch-sensitive display 112, and lift-off of the touch (touch end). In some embodiments, an event also includes information about one or more associated event handlers 190.

[0165] In some embodiments, the event definition 187 includes an event definition for each user interface object. In some embodiments, the event comparison unit 184 performs a hit test to determine which user interface object is associated with a sub-event. For example, in an application view where three user interface objects are displayed on a touch-sensitive display 112, when a touch is detected on the touch-sensitive display 112, the event comparison unit 184 performs a hit test to determine which of the three user interface objects is associated with the touch (sub-event). If each displayed object is associated with a corresponding event handler 190, the event comparison unit uses the results of the hit test to determine which event handler 190 needs to be activated. For example, the event comparison unit 184 selects an event handler associated with the object that triggers the sub-event and the hit test.

[0166] In some embodiments, the definition of each event 187 also includes a delay effect that delays the transmission of event information until it is determined whether the sequence of sub-events corresponds to the event type of the event recognition unit.

[0167] If the corresponding event recognition unit 180 determines that a series of sub-events does not match any of the events in the event definition 186, the corresponding event recognition unit 180 enters an event impossible, event failed, or event terminated state and thereafter ignores subsequent sub-events of the touch-based gesture. In this situation, any other event recognition units that remain active for the hit view continue to track and process the sub-events of the ongoing touch-based gesture.

[0168] In some embodiments, the corresponding event recognition unit 180 includes metadata 183 having configurable properties, flags, and / or lists that indicate how the event distribution system performs sub-event distribution to the event recognition unit in which it is actively involved. In some embodiments, the metadata 183 includes configurable properties, flags, and / or lists that indicate how the event recognition units may interact with each other. In some embodiments, the metadata 183 includes configurable properties, flags, and / or lists that indicate whether sub-events are distributed to various levels within the view hierarchy or program hierarchy.

[0169] In some embodiments, the corresponding event recognition unit 180 activates an event handler 190 associated with an event when one or more specific sub-events of an event are recognized. In some embodiments, the corresponding event recognition unit 180 distributes event information associated with the event to the event handler 190. Activating the event handler 190 is distinct from sending (and delaying the sending of) the sub-events to the corresponding hit view. In some embodiments, the event recognition unit 180 throws a flag associated with the recognized event, and the event handler 190 associated with the flag catches the flag and performs default processing.

[0170] In some embodiments, the event distribution command 188 includes a sub-event distribution command that distributes event information about a sub-event without activating an event handler. Instead, the sub-event distribution command distributes the event information to an event handler or an actively involved view associated with a set of sub-events. The event handler associated with the set of sub-events or the actively involved view receives the event information and performs predetermined processing.

[0171] In some embodiments, the data updater 176 creates and updates data used in application 136-1. For example, the data updater 176 updates telephone numbers used in contact module 137 or stores video files used in video playback module 145. In some embodiments, the object updater 177 creates and updates objects used in application 136-1. For example, the object updater 176 creates new user interface objects or updates the positions of user interface objects. The GUI updater 178 updates the GUI. For example, the GUI updater 178 prepares display information and sends it to the graphics module 132 for display on the touch-sensitive display.

[0172] In some embodiments, one or more event handlers 190 include, or have access to, a data updater 176, an object updater 177, and a GUI updater 178. In some embodiments, the data updater 176, the object updater 177, and the GUI updater 178 are contained in a single module of the corresponding application 136-1 or application view 191. In other embodiments, they are contained in two or more software modules.

[0173] The aforementioned discussion of event processing for user touch on a touch-sensitive display also applies to other forms of user input for operating the multifunction device 100 using input devices, but it will be understood that not all of these begin on a touchscreen. For example, mouse movement and mouse button presses, touch movements on a touchpad such as taps, drags, and scrolls, pen stylus input, device movement, verbal commands, detected eye movements, biometric input, and / or any combination thereof may be used as inputs corresponding to sub-events that define the recognized event.

[0174] Figure 2 shows a portable multifunctional device 100 having a touchscreen 112 according to several embodiments. The touchscreen optionally displays one or more graphics within a user interface (UI) 200. In embodiments described later and in this embodiment, the user can select one or more graphics by making gestures on the graphics using, for example, one or more fingers 202 (not shown in the figure to an exact scale) or one or more styluses 203 (not shown in the figure to an exact scale). In some embodiments, the selection of one or more graphics occurs when the user discontinues contact with one or more graphics. In some embodiments, the gesture optionally includes one or more taps, one or more swipes (from left to right, right to left, upward, and / or downward), and / or rolling of a finger in contact with the device 100 (from right to left, left to right, upward, and / or downward). In some implementations or situations, accidental contact with a graphic does not select the graphic; for example, if the gesture corresponding to selection is a tap, a swipe gesture over an application icon does not arbitrarily select the corresponding application.

[0175] Device 100 also optionally includes one or more physical buttons, such as a "Home" or menu button 204. As previously stated, the menu button 204 is optionally used to navigate to any application 136 within a set of applications optionally run on Device 100. Alternatively, in some embodiments, the menu button is implemented as a soft key in a GUI displayed on the touchscreen 112. In some embodiments, button 204 includes an integrated fingerprint sensor 169-1 for identifying a fingerprint interacting with button 204 and / or for detecting the movement of a fingerprint on button 204. The device also optionally includes one or more other fingerprint sensors 169-2, separate from button 204, which are used instead of, or in conjunction with, the fingerprint sensor 169-1 built into button 204, for identifying a user interacting with the device and / or detecting fingerprint movement. In addition, one or more of the other fingerprint sensors 169-2 are optionally associated with a button (e.g., a pressure-sensitive area activated by detecting an input having an intensity exceeding an activation intensity threshold, or a physical actuator that moves in response to a force applied by the user). In implementations where the touch-sensing surface (e.g., touchscreen 112) has a spatial resolution of sufficient height to detect fingerprint features formed by individual fingerprint ridges, the touch-sensing surface (e.g., touchscreen 112) is optionally used as a substitute for or additional fingerprint sensor (e.g., fingerprint sensor 169-1 or 169-2). In some embodiments, device 100 includes a set of one or more orientation sensors used to determine the orientation of a hand on device 100.

[0176] In one embodiment, device 100 includes a touchscreen 112, a menu button 204, a push button 206 for turning the device on / off and locking the device, one or more volume buttons 208, a receiver identification module (SIM) card slot 210, a headset jack 212, and an external docking / charging port 124. The push button 206 is optionally used to turn the device on / off by pressing and holding the button for a predetermined time interval, to lock the device, and / or to unlock the device or initiate an unlocking process by pressing and releasing the button before the predetermined time interval has elapsed. In an alternative embodiment, device 100 also accepts verbal input through a microphone 113 to activate or deactivate certain functions. The device 100 also optionally includes one or more contact intensity sensors 165 for detecting the intensity of contact with the touchscreen 112 and / or one or more tactile output generators 167 for generating tactile output from the user of the device 100.

[0177] Figure 3 is a block diagram of an exemplary multifunctional device having a display and a touch-sensitive surface according to several embodiments. Device 300 may not be portable. In some embodiments, device 300 is a laptop computer, a desktop computer, a tablet computer, a multimedia player device, a navigation device, an educational device (such as a children's learning toy), a game system, or a control device (e.g., a home or commercial controller). Device 300 typically includes one or more processing units (CPUs) 310, one or more network or other communication interfaces 360, memory 370, and one or more communication buses 320 for interconnecting these components. The communication buses 320 optionally include circuitry (sometimes referred to as a chipset) for interconnecting and controlling communication between system components. Device 300 includes an input / output (I / O) interface 330 with a display 340, which is typically a touchscreen display. Furthermore, the I / O interface 330 optionally includes a keyboard and / or mouse (or other pointing device) 350 and a touchpad 355, a tactile output generator 357 (similar to, for example, one or more tactile output generators 167 described above in relation to Figure 1A) for generating tactile output on the device 300, and a sensor 359 (e.g., an optical sensor, an accelerometer, a proximity sensor, a touch sensor, and / or a touch intensity sensor similar to one or more contact intensity sensors 165 described above in relation to Figure 1A, and / or a fingerprint sensor similar to one or more fingerprint sensors 169 described above in relation to Figure 1A). In addition, in an implementation in which the touch-sensitive surface (e.g., the touchpad 355) has a spatial resolution of sufficient height to detect fingerprint features formed by individual fingerprint ridges, the touch-sensitive surface (e.g., the touchpad 355) may optionally be used as a substitute for or as an additional fingerprint sensor (e.g., one of the sensors 359).In some embodiments, the device 300 includes a set of one or more orientation sensors used to determine the orientation of a finger or hand on or near the device (e.g., the orientation of a finger on the fingerprint sensor 169). In addition, in some embodiments, the set of one or more orientation sensors is used in addition to or instead of the fingerprint sensor to detect the rotation of a contact interacting with the device. For example, in one or more of the methods described above, instead of using the fingerprint sensor to detect the rotation of a fingerprint / contact, a set of one or more orientation sensors is used to detect the rotation of a contact containing a fingerprint, with or without detection of fingerprint features.

[0178] Memory 370 includes high-speed random-access memory such as DRAM, SRAM, DDR RAM, or other random-access solid-state memory devices, and optionally includes non-volatile memory such as one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid-state storage devices. Memory 370 optionally includes one or more storage devices located remotely from the CPU(s) 310. In some embodiments, memory 370 stores programs, modules, and data structures similar to, or subsets thereof, stored in memory 102 of the portable multifunction device 100 (Figure 1A). Furthermore, memory 370 optionally stores additional programs, modules, and data structures that are not present in memory 102 of the portable multifunction device 100. For example, the memory 370 of device 300 optionally stores the drawing module 380, the presentation module 382, ​​the document creation module 384, the website creation module 386, the disk authoring module 388, and / or the spreadsheet module 390, but the memory 102 of the portable multifunction device 100 (Figure 1) does not optionally store these modules.

[0179] Each of the elements of Figure 3 identified above is optionally stored in one or more of the aforementioned memory devices. Each of the modules identified above corresponds to an instruction set for performing the function described above. The identified modules or programs (i.e., instruction sets) do not need to be implemented as separate software programs, procedures, or modules; therefore, in various embodiments, various subsets of these modules are optionally combined or rearranged in other ways. In some embodiments, memory 370 optionally stores subsets of the identified modules and data structures described above. Furthermore, memory 370 optionally stores additional modules and data structures not described above.

[0180] Here, we turn our attention to an embodiment of a user interface ("UI") that is optionally implemented on the portable multifunction device 100.

[0181] Figure 4A shows an exemplary user interface for an application menu on a portable multifunction device 100 according to several embodiments. A similar user interface may optionally be implemented on device 300. In some embodiments, the user interface 400 includes the following elements, or subsets or supersets thereof. ● Signal strength indicators (one or more) for wireless communication (one or more) such as cellular signals and Wi-Fi signals 402, ●Time 404, ●Bluetooth indicator 405, ●Battery status indicator 406, ●Tray 408 contains icons for frequently used applications, such as the following: ○Optionally including an indicator 414 of the number of missed calls or voicemail messages, an icon 416 for the telephone module 138 labeled "Telephone", ○Optionally including an indicator 410 of the number of unread emails, an icon 418 labeled "Mail" for the email client module 140, ○ Icon 420 for browser module 147, labeled as "Browser", and ○ Icon 422 for the video and music playback module 152, also known as the iPod (trademark of Apple Inc.) module 152, which is labeled "iPod," and ● Icons for other applications, such as those listed below. ○ Icon 424 for IM module 141, labeled as "Text" ○ Icon 426 for calendar module 148, labeled as "Calendar" ○ Icon 428 for image management module 144, labeled as "Photo" ○ Icon 430 for camera module 143, labeled "Camera" ○ Icon 432 for online video module 155, labeled "online video" ○ Icon 434 for stock widget 149-2, labeled "Stocks" ○ Icon 436 for map module 154, labeled as "Map" ○ Icon 438 for weather widget 149-1, labeled "Weather" ○ Icon 440 for alarm clock widget 149-4, labeled as "Clock" ○ Icon 442 for training support module 142, labeled "Training Support" ○ Icon 444 for memo module 153, which is labeled as "Memo", and ○ An icon 446 for a configuration application or module that provides access to settings related to device 100 and its various applications 136.

[0182] It will be understood that the icon labels shown in Figure 4A are merely illustrative. For example, the icon 422 for the video and music playback module 152 is labeled "Music" or "Music Player". Other labels are used optionally for various application icons. In some embodiments, the label for each application icon includes the name of the application corresponding to that application icon. In some embodiments, the label for a particular application icon is different from the name of the application corresponding to that particular application icon.

[0183] Figure 4B shows an exemplary user interface on a device (e.g., device 300 in Figure 3) having a touch-sensitive surface 451 (e.g., tablet or touchpad 355 in Figure 3) separate from a display 450 (e.g., touchscreen 112) having an integrated 359-1 (or separate 359-2) fingerprint sensor (e.g., one or more of the sensors 359 operating in a manner similar to the fingerprint sensor 169 in Figure 1A). In addition, in an implementation where the touch-sensitive surface 451 has a spatial resolution of sufficient height to detect fingerprint features formed by individual fingerprint ridges, the touch-sensitive surface 451 may be optionally used as a fingerprint sensor in place of or in addition to different fingerprint sensors (e.g., integrated fingerprint sensor 359-1, or separate fingerprint sensor 359-2). The device 300 also optionally includes one or more contact intensity sensors (e.g., one or more of sensors 359-3) for detecting the intensity of contact with the touch sensing surface 451 and / or one or more tactile output generators 357 for generating a user tactile output for the device 300.

[0184] Some of the following embodiments are described with reference to input on a touchscreen display 112 (when the touch-sensing surface and the display are combined), but in some embodiments, the device detects input on a touch-sensing surface separate from the display, as shown in Figure 4B. In some embodiments, the touch-sensing surface (e.g., 451 in Figure 4B) has a principal axis (e.g., 452 in Figure 4B) corresponding to a principal axis (e.g., 453 in Figure 4B) on the display (e.g., 450). According to these embodiments, the device detects contact (e.g., 460 and 462 in Figure 4B) with the touch-sensing surface 451 at positions corresponding to each of the positions on the display (e.g., 460 corresponds to 468 and 462 corresponds to 470 in Figure 4B). Thus, when the touch-sensitive surface is separate from the display, user input detected by the device on the touch-sensitive surface (e.g., 451 in Figure 4B) (e.g., touches 460 and 462, and their movement) is used by the device to operate the user interface on the display of the multifunction device (e.g., 450 in Figure 4B). It should be understood that a similar method may be optionally used for other user interfaces described herein.

[0185] Furthermore, while the following description primarily refers to finger input (e.g., finger touch, finger tap gesture, finger swipe gesture), it should be understood that in some embodiments, one or more of these finger inputs may be replaced by input from another input device (e.g., mouse-based input or stylus input). For example, a swipe gesture may optionally be replaced with a mouse click (e.g., instead of touch), followed by cursor movement along the swipe path (e.g., instead of touch movement). In another embodiment, a tap gesture may optionally be replaced with a mouse click (e.g., instead of stopping touch detection after touch detection) while the cursor is positioned over the tap gesture location. Similarly, when multiple user inputs are detected simultaneously, it should be understood that multiple computer mice may optionally be used simultaneously, or a mouse and finger touch may optionally be used simultaneously.

[0186] As used herein, the term “focus selector” refers to an input element that indicates the current portion of the user interface that the user is interacting with. In implementations including a cursor or other location marker, the cursor functions as a “focus selector” when input (e.g., press input) is detected on a touch-sensitive surface (e.g., touchpad 355 in Figure 3, or touch-sensitive surface 451 in Figure 4B) and the cursor is over a particular user interface element (e.g., a button, window, slider, or other user interface element), and the particular user interface element is adjusted according to the detected input. In some implementations including a touchscreen display (e.g., touch-sensitive display system 112 in Figure 1A, or touchscreen 112 in Figure 4A) that enables direct interaction with user interface elements on the touchscreen display, the contact detected on the touchscreen acts as a “focus selector” so that when input (e.g., press input by touch) is detected at the location of a particular user interface element (e.g., a button, window, slider, or other user interface element) on the touchscreen display, that particular user interface element is adjusted according to the detected input. In some implementations, focus is moved from one area of ​​the user interface to another without corresponding cursor movement or touch movement on the touchscreen (for example, by moving focus from one button to another using the tab key or arrow keys). In these implementations, the focus selector moves in accordance with the movement of focus between different areas of the user interface. Regardless of the specific form the focus selector takes, the focus selector as a whole is a user interface element (or touch on the touchscreen display) controlled by the user to convey the user's intended interaction with the user interface (for example, by instructing the device to interact with the user interface element the user wishes to interact with).For example, when a press input is detected on a touch-sensitive surface (e.g., a touchpad or touchscreen), the position of the focus selector (e.g., a cursor, touch, or selection box) above each button indicates (in contrast to other user interface elements displayed on the device's display) that the user is trying to activate that button.

[0187] Figure 4C shows schematic diagrams of two hands with associated fingerprints LP ("left little finger" fingerprint), LR ("left ring finger" fingerprint), LM ("left middle finger" fingerprint), LI ("left index finger" fingerprint), LT ("left thumb" fingerprint), RT ("right thumb" fingerprint), RI ("right index finger" fingerprint), RM ("right middle finger" fingerprint), RR ("right ring finger" fingerprint), and RP ("right little finger" fingerprint). These abbreviations are used to refer to other fingers illustrating examples of interaction with a fingerprint sensor. For some of the methods described herein, one or more fingerprints of a user are registered by collecting information about the fingerprints that enables fingerprint identification. These registered fingerprints, or pre-registered fingerprints, may also be referred to as registered fingerprints. In many of the situations described below, a fingerprint detected on a fingerprint sensor is compared to a previously registered fingerprint (e.g., a registered fingerprint).

[0188] Figure 4D illustrates two different types of rotation of a fingerprint on a fingerprint sensor (e.g., a fingerprint sensor 169 integrated into button 204). The left side of Figure 4D is an example of "swirl" of a fingerprint around the fingerprint sensor, where the center of gravity of the fingerprint moves in a swirl motion (e.g., circular motion) around the center of the fingerprint sensor. The right side of Figure 4D is an example of "twist" of a fingerprint on the fingerprint sensor, where the principal axis of the fingerprint changes its orientation relative to the fingerprint sensor. These terms (e.g., "swirl" and "twist") are used to describe the different directions of rotation of a fingerprint on a fingerprint sensor, with reference to other fingers illustrating examples of interaction with the fingerprint sensor.

[0189] As shown in Figure 4D, in some embodiments, the fingerprint sensor is smaller than or approximately the same size as an average fingerprint. Therefore, in some embodiments, the fingerprint sensor detects fingerprint movement (e.g., fingerprint gestures) by detecting the movement of fingerprint features instead of, or in addition to, detecting the movement of the edges of the fingerprint. In other words, in some implementations, the fingerprint sensor detects fingerprint movement not by determining the movement of the contour of the fingerprint (e.g., contact), but by detecting the movement of the ridges of the fingerprint on the fingerprint sensor (e.g., specific minisure points of the ridges). Regardless of whether the fingerprint sensor is larger or smaller than the fingerprint, detecting fingerprint movement (e.g., fingerprint gestures) based on the movement of fingerprint features instead of, or in addition to, the movement of the edges or contour of the fingerprint allows for tracking fingerprint movement in much greater detail, even if the fingerprint covers all or most of the fingerprint sensor. User interface and related processes Register your fingerprint using the device.

[0190] Many electronic devices provide methods for unlocking them. For example, users may need to enter a passcode or personal identification number (PIN), perform a swipe gesture with a predefined pattern, or slide an affordance to unlock the device and access personal user information and applications. However, with the proliferation of e-commerce and mobile purchases, stronger security is required to unlock devices. The device described below improves upon existing methods of registering fingerprints of each finger after collecting fingerprint information from multiple individual and distinct static finger gestures. In turn, the device performs a limited action (e.g., unlocking the device or mobile purchase) when the detected fingerprint matches a registered fingerprint.

[0191] The device displays a fingerprint registration interface and detects multiple individual and distinct static finger gestures performed with the corresponding finger on the fingerprint sensor. The device collects fingerprint information from the multiple individual and distinct static finger gestures performed with the corresponding finger. After collecting the fingerprint information, the device determines, based on the fingerprint information collected for that corresponding finger, whether the collected fingerprint information is sufficient to register the fingerprint of that finger using the device. If the device determines that the collected fingerprint information for that finger is sufficient to register the fingerprint of that finger, the device registers the fingerprint of that finger using the device. If the device determines that the collected fingerprint information for that finger is not sufficient to register the fingerprint of that finger, the device displays a message on the fingerprint registration interface prompting the user to perform one or more additional static finger gestures with that finger on the fingerprint sensor.

[0192] In some embodiments, the device is an electronic device comprising a separate display (e.g., display 450) and a separate touch-sensitive surface (e.g., touch-sensitive surface 451). In some embodiments, the device is a portable multifunction device 100, where the display is a touchscreen 112 and the touch-sensitive surface includes a tactile output generator 167 on the display (Figure 1A). The device described below with reference to Figures 5A-5EE and 6A-6D includes one or more fingerprint sensors 169. In some embodiments, the one or more fingerprint sensors include one or more integrated fingerprint sensors 359-1 (Figure 4B) that are integrated with a touch-sensitive surface (e.g., a separate touch-sensitive surface 451 or a touch-sensitive display system 112). In some embodiments, the one or more fingerprint sensors include a separate fingerprint sensor 359-2 (Figure 4B) that is separate from the touch-sensitive surface (e.g., a separate touch-sensitive surface 451 or a touch-sensitive display system 112). Unless otherwise specified, the fingerprint sensor 169 described below is optionally an integrated fingerprint sensor 359-1 or a separate fingerprint sensor 359-2, depending on the hardware and software configuration of the device including the fingerprint sensor 169. For convenience of explanation, the embodiments described with reference to Figures 5A to 5EE and 6A to 6D will be discussed with reference to a device having a touchscreen 112 and a separate touch-sensing surface 359-2, but similar operations are optionally performed on the device by the integrated fingerprint sensor 359-1 in response to detecting inputs described in Figures 5A to 5EE on the integrated fingerprint sensor 359-1 while the user interface shown in Figures 5A to 5EE is displayed on the display 450. Furthermore, similar operations are optionally performed on the separate touch-sensing surface 451 in devices having a display 450 and a separate touch-sensing surface 451 instead of a touchscreen 112, in response to the detection of contact shown in Figures 5A to 5EE on the fingerprint sensor 169 (e.g., integrated fingerprint sensor 359-1 or separate fingerprint sensor 359-2) and / or on the separate touch-sensing surface 451 while displaying the user interface shown in Figures 5A to 5EE on the display 450.In such embodiments, the contacts shown in Figures 5A to 5EE optionally represent both a focus selector corresponding to a position on the display 450 and a contact corresponding to a position of a contact or gesture made on a separate touch-sensing surface (e.g., touch-sensing surface 451), the focus selector optionally represents a corresponding contact, a representative point corresponding to a contact (e.g., the centroid of the corresponding contact, or a point associated with the corresponding contact), or the centroids of two or more contacts detected on the touchscreen 112, and optionally replaces with a displayed cursor.

[0193] Figures 5A to 5M show part of the device setup process in which a first fingerprint is registered using the portable multifunction device 100.

[0194] Figure 5A shows a portable multifunction device 100 (sometimes referred to as Device 100 herein) displaying a user interface 400 on a touchscreen 112. In Figure 5A, the user interface 400 includes a “Set Up Touch ID” interface that prompts the user to register a fingerprint to function as the user’s Touch ID. The registered fingerprint (e.g., Touch ID) can be used to unlock the device in place of a passcode or personal identification number (PIN), and optionally to purchase goods or services. In Figure 5A, the “Set Up Touch ID” interface is displayed during the device setup process. For example, the device setup process occurs when the user first powers on the device. For example, the device setup process includes at least an optional fingerprint registration process (e.g., shown in Figures 5B–5K and 5N–5T) and a passcode setup process (e.g., shown in Figure 5M). The "Set Up Touch ID" interface includes a "Set Up Now" box 502, which, when activated, initiates the fingerprint registration process on device 100, and a "Set Up Later" box 504, which, when activated, causes device 100 to skip the fingerprint registration process and display the passcode setting interface (for example, shown in Figure 5M). For example, the "Set Up Now" box 502 is activated when contact (e.g., touch input or tap gesture) is detected within or above the "Set Up Now" box 502, or when a fingerprint is detected on the fingerprint sensor 169. For example, the "Set Up Later" box 504 is activated when touch input is detected within or above the "Set Up Later" box 504. Figure 5A also shows device 100 detecting contact 506 (e.g., tap gesture) at a location on the touchscreen 112 corresponding to the "Set Up Now" box 502. Alternatively, Figure 5A shows a device 100 that detects a fingerprint 508 (for example, corresponding to the user's right index finger) on a fingerprint sensor 169 as part of a first finger gesture (for example, a first touch and placement gesture) and collects fingerprint information from the first finger gesture.

[0195] Figure 5B shows device 100 displaying a first fingerprint registration interface for the fingerprint registration process on the touchscreen 112 in response to the detection of contact 506 in Figure 5A. In some embodiments, the fingerprint registration process includes at least a first fingerprint registration interface (e.g., shown in Figures 5B-5G and 5O-5Q) and a second fingerprint registration interface (e.g., shown in Figures 5H-5J and 5R-5S). In Figure 5B, the first fingerprint registration interface includes commands on the fingerprint sensor 169 prompting the user to perform a number of separate and distinct stationary finger gestures with the corresponding fingers to register the fingerprints of the corresponding fingers. In Figure 5B, the first fingerprint registration interface also includes a progress indicator 510 in a first state 510-a. For example, in the first state 510-a, the progress indicator 510 is a simulated fingerprint with elongated ridges. The first state 510-a indicates that no fingerprint information has been collected. Figure 5B also shows a "back" affordance 509 that, when activated, causes device 100 to redisplay the "Set Up Touch ID" interface of Figure 5A. Figure 5B further shows device 100 detecting a fingerprint 512 (for example, corresponding to the user's right index finger) on the fingerprint sensor 169 as part of a first finger gesture and collecting fingerprint information from the first finger gesture.

[0196] Figure 5C shows device 100 changing the appearance of the progress indicator 510 in response to the detection of a first finger gesture. For example, the first finger gesture corresponds to fingerprint 508 in Figure 5A or fingerprint 512 in Figure 5B. In Figure 5C, device 100 displays the progress indicator 510 in a second state 510-b. In Figure 5C, at least part of the ridge of the progress indicator 510 is thicker (or darker) in the second state 510-b compared to the first state 510-a in Figure 5B. The second state 510-b of the progress indicator 510 indicates that some fingerprint information has been collected, but one or more further finger gestures are needed to register the first fingerprint (for example, a fingerprint corresponding to the user's right index finger). Figure 5C also shows that device 100 detects a fingerprint 514 (e.g., corresponding to the user's right index finger) on the fingerprint sensor 169 as part of a second finger gesture (e.g., a second touch and rest gesture) and collects fingerprint information from the second finger gesture.

[0197] Figure 5D shows device 100 displaying a message on the touchscreen 112 prompting the user to perform a subsequent finger gesture different from the second finger gesture detected in Figure 5C. In Figure 5D, in response to the detection of the second finger gesture in Figure 5C, device 100 displays message 516, the first registration interface (including a progress indicator 510 for the second state 510-b), on the touchscreen 112. In Figure 5D, message 516 includes instructions to the user to move each finger between each finger gesture to collect fingerprint information corresponding to the fingerprints of different areas of each finger. In some embodiments, message 516 is closed and the fingerprint registration process resumes when contact is detected at a location corresponding to the "OK" affordance in message 516, or when the next finger gesture is detected by the fingerprint sensor 169. Figure 5D also shows that device 100 detects a fingerprint 518 (e.g., corresponding to the user's right index finger) on the fingerprint sensor 169 as part of a third finger gesture (e.g., a third touch and rest gesture) and collects fingerprint information from the third finger gesture.

[0198] Figure 5E shows device 100 changing the appearance of the progress indicator 510 in response to the detection of a third finger gesture in Figure 5D. In Figure 5E, device 100 displays the progress indicator 510 in the third state 510-c. In Figure 5E, a greater amount of the ridge on the progress indicator 510 is thicker compared to the second state 510-b in Figure 5B. The third state 510-c of the progress indicator 510 indicates that more fingerprint information has been collected, but one or more further finger gestures are required to register the first fingerprint (e.g., corresponding to the user's right index finger). Figure 5E also shows device 100 detecting fingerprint 520 (e.g., corresponding to the user's right index finger) on the fingerprint sensor 169 as part of a fourth finger gesture (e.g., a fourth touch and rest gesture) and collecting fingerprint information from the fourth finger gesture.

[0199] Figure 5F shows device 100 displaying a message on the touchscreen 112 prompting the user to perform a subsequent finger gesture different from the fourth finger gesture detected in Figure 5E. In Figure 5F, in response to the detection of the fourth finger gesture in Figure 5E, device 100 displays message 522 on the touchscreen 112 above the first registration interface (including a progress indicator 510 for the third state 510-c). In Figure 5F, message 522 includes a command instructing the user to keep their finger on the fingerprint sensor 169 for a longer period of time so that fingerprint information can be collected. In some embodiments, message 522 includes a command indicating that the user should feel a vibration signaling when it is safe to lift the user's finger from the fingerprint sensor 169. In some embodiments, message 522 is closed and the fingerprint registration process resumes when contact is detected at a position corresponding to the "OK" affordance in message 522 or when the next finger gesture is detected by the fingerprint sensor 169. Figure 5F also shows that device 100 detects contact 524 at the location on touchscreen 112 corresponding to the "OK" affordance in message 522.

[0200] Figure 5G shows device 100 displaying a first fingerprint registration interface having a progress indicator 510 in a third state 510-c, in response to the detection of contact 524 in Figure 5F. Figure 5G also shows device 100 detecting a fingerprint 526 (e.g., corresponding to the user's right index finger) on the fingerprint sensor 169 as part of a fifth finger gesture (e.g., a fifth touch and rest gesture) and collecting fingerprint information from the fifth finger gesture.

[0201] Figure 5H shows device 100 displaying a second fingerprint registration interface on the touchscreen 112 for the fingerprint registration process and changing the appearance of the progress indicator 510 in response to the detection of a fifth finger gesture in Figure 5G. In Figure 5H, the second fingerprint registration interface includes instructions to prompt the user to perform one or more further individual and distinct stationary finger gestures on the fingerprint sensor 169 with the corresponding finger (e.g., the user's right index finger) to collect fingerprint information about the missing areas (e.g., edges) of the corresponding finger's fingerprint from previously collected fingerprint information and complete the registration of the first fingerprint (e.g., corresponding to the user's right index finger). In Figure 5H, device 100 displays the progress indicator 510 in the fourth state 510-d. In Figure 5H, the progress indicator 510 is magnified in the fourth state 510-d, showing a thinner ridge around a larger ellipse enclosing the internal region of the thickened ridge. In Figure 5H, the internal region of the progress indicator 510 corresponds to the unenlarged progress indicator 510 included in the first registration interface shown in Figures 5B to 5G. In this example, a larger amount of ridges in the internal region of the progress indicator 510 are thicker in the fourth state 510-d compared to the third state 510-c in Figure 5G. The fourth state 510-d of the progress indicator 510 indicates that more fingerprint information has been collected, but one or more further finger gestures are required to register the first fingerprint (e.g., the fingerprint corresponding to the user's right index finger). Figure 5H also shows that device 100 detects fingerprint 528 (e.g., corresponding to the user's right index finger) on the fingerprint sensor 169 as part of a sixth finger gesture (e.g., a sixth touch and rest gesture) and collects fingerprint information from the sixth finger gesture.

[0202] Figure 5I shows device 100 with a changed appearance of the progress indicator 510 in response to the detection of the sixth finger gesture in Figure 5H. In Figure 5H, device 100 displays the progress indicator 510 in the fifth state 510-e. In Figure 5I, a portion of the ridge on the outer edge of the progress indicator 510 is thicker in the fifth state 510-e compared to the fourth state 510-d in Figure 5H. The fifth state 510-e of the progress indicator 510 indicates that more fingerprint information has been collected, but one or more further finger gestures are required to register the first fingerprint (e.g., the fingerprint corresponding to the user's right index finger). Figure 5I also shows device 100 detecting the fingerprint 530 (e.g., corresponding to the user's right index finger) on the fingerprint sensor 169 as part of the seventh finger gesture (e.g., the fourth touch and rest gesture) and collecting fingerprint information from the seventh finger gesture.

[0203] Figure 5J shows device 100 changing the appearance of the progress indicator 510 in response to detecting the seventh finger gesture in Figure 5I. In Figure 5J, device 100 displays the progress indicator 510 in the sixth state 510-f. In Figure 5J, all the ridges on the outer edge of the progress indicator 510 are thickened in the fifth state 510-f. In this example, the sixth state 510-f of the progress indicator 510 indicates that no additional finger gestures are required to register the first fingerprint (for example, the fingerprint corresponding to the user's right index finger).

[0204] Figure 5K shows device 100 displaying a third fingerprint registration interface on the touchscreen 112 after changing the appearance of the progress indicator 510 in Figure 5J. In Figure 5K, the third fingerprint registration interface indicates that the first fingerprint (e.g., the fingerprint corresponding to the user's right index finger) has been successfully registered using device 100. In Figure 5K, the third fingerprint registration interface, once activated, includes a “Continue” box 534 that causes device 100 to display an interface for the next step in the device setup process. Figure 5K also shows that device 100 detects a contact 536 (e.g., a tap gesture) at the location on the touchscreen 112 corresponding to the “Continue” box 534.

[0205] Figure 5L shows device 100 displaying the "Set Up Touch ID for Purchase" interface on the touchscreen 112 in response to the detection of contact 536 in Figure 5K. The "Set Up Touch ID for Purchase" interface prompts the user to associate the fingerprint registered in Figures 5B-5K with purchase credentials (e.g., store login ID and password, credit card information, billing address, etc.). The "Set Up Touch ID for Purchase" interface includes a "Set Up Now" box 538, which, when activated, initiates a purchase setup process that associates purchase credentials with a previously registered fingerprint on device 100, and a "Set Up Later" box 540, which, when activated, causes device 100 to skip the purchase setup process and display the passcode setup interface. For example, the "Set Up Now" box 538 is activated when touch input is detected in or above the "Set Up Later" box 538, and the "Set Up Later" box 540 is activated when touch input is detected in or above the "Set Up Later" box 540. Figure 5L also shows that device 100 detects a contact 542 (e.g., a tap gesture) at the location on the touchscreen 112 corresponding to the “Set up later” box 540.

[0206] Figure 5M shows device 100 displaying a passcode setting interface on the touchscreen 112 in response to the detection of contact 542 in Figure 5L. In Figure 5M, the passcode setting interface includes several soft keys that allow setting a master passcode or PIN for the device.

[0207] Figures 5N to 5T show how to register a second fingerprint using the portable multifunction device 100 via the configuration interface.

[0208] Figure 5N shows a device 100 displaying a fingerprint setting interface on a touchscreen 112. In Figure 5N, the fingerprint setting interface includes a “back” affordance 544, which, when activated, causes device 100 to redisplay a previous setting interface different from the fingerprint setting interface, and an “edit” affordance 546, which, when activated, causes device 100 to change the appearance of the fingerprint setting interface, allowing the user to delete a registered fingerprint or edit its name. In Figure 5N, the fingerprint setting interface also includes a toggle switch 548 configured to turn on / off a passcode unlock function that allows the user to unlock the device using a registered fingerprint instead of a passcode, and a toggle switch 550 configured to turn on / off the ability to purchase goods and services with a registered fingerprint. In Figure 5N, the passcode unlock function is turned on, and the ability to purchase goods and services with a registered fingerprint is turned off.

[0209] In Figure 5N, the fingerprint setting interface also includes a list of registered fingerprints. In Figure 5N, the list of registered fingerprints includes a "Fingerprint 1" box 552, which, when activated, changes the appearance of the "Fingerprint 1" box 552, allowing the user to edit the name of a registered fingerprint, and also includes an "Add Fingerprint" box 554, which, when activated, causes the device 100 to start the fingerprint registration process. For example, the registered "Fingerprint 1" corresponds to the first fingerprint (e.g., the fingerprint corresponding to the user's right index finger) that is registered during the registration process shown in Figures 5B to 5K. Figure 5N also shows that the device 100 detects a contact 556 (e.g., a tap gesture) at the location on the touchscreen 112 corresponding to the "Add Fingerprint" box 554.

[0210] Figure 5O shows device 100 displaying a first fingerprint registration interface for the fingerprint registration process on the touchscreen 112 in response to the detection of contact 556 in Figure 5N. In Figure 5O, the first fingerprint registration interface includes commands that prompt the user to perform a number of individual and distinct stationary finger gestures with the corresponding fingers on the fingerprint sensor 169 to register the fingerprints of the corresponding fingers. In Figure 5O, the first fingerprint registration interface also includes a progress indicator 558 in a first state 558-a. For example, in the first state 558-a, the progress indicator 558 is a simulated fingerprint with an elongated ridge. The first state 558-a indicates that no fingerprint information has been collected. Figure 5O also shows a “back” affordance 557 that, when activated, causes device 100 to redisplay the fingerprint setting interface of Figure 5N. Figure 5O further shows that device 100 detects a fingerprint 560 (e.g., corresponding to the user's left index finger) on the fingerprint sensor 169 as part of a first finger gesture (e.g., a first touch and rest gesture) and collects fingerprint information from the first finger gesture.

[0211] Figure 5P shows device 100 changing the appearance of the progress indicator 558 in response to the detection of the first finger gesture in Figure 5O. In Figure 5P, device 100 displays the progress indicator 558 in a second state 558-b. In Figure 5P, at least some of the ridges of the progress indicator 558 are thicker (or darker) in the second state 558-b compared to the first state 558-a in Figure 5O. The second state 558-b of the progress indicator 558 indicates that some fingerprint information has been collected, but one or more further finger gestures are needed to register a second fingerprint (e.g., a fingerprint corresponding to the user's left index finger). Figure 5P also shows device 100 detecting a fingerprint 562 (e.g., corresponding to the user's left index finger) on the fingerprint sensor 169 as part of a second finger gesture (e.g., a second touch and rest gesture) and collecting fingerprint information from the second finger gesture.

[0212] Figure 5Q shows device 100 displaying a message on the touchscreen 112 prompting the user to perform a subsequent finger gesture different from the second finger gesture detected in Figure 5P. In Figure 5Q, in response to the detection of the second finger gesture in Figure 5P, device 100 displays message 564 on the touchscreen 112 above the first registration interface (including a progress indicator 558 for the second state 558-b). In Figure 5Q, message 564 includes an instruction to the user to place their finger on the fingerprint sensor 169 (e.g., integrated with the home button 204) without clicking / pressing the home button 204 until a vibration is felt, in order to collect fingerprint information. In some embodiments, message 564 is closed and the fingerprint registration process resumes when contact is detected at a position corresponding to the "OK" affordance in message 564 or when a subsequent finger gesture is detected by the fingerprint sensor 169. Figure 5Q also shows that device 100 detects a fingerprint 566 (e.g., corresponding to the user's left index finger) on the fingerprint sensor 169 as part of a third finger gesture (e.g., a third touch and rest gesture) and collects fingerprint information from the third finger gesture.

[0213] Figure 5R shows device 100 displaying a second fingerprint registration interface on the touchscreen 112 for the fingerprint registration process and changing the appearance of the progress indicator 558 in response to detecting the third finger gesture in Figure 5Q. In Figure 5R, the second fingerprint registration interface includes instructions to prompt the user to perform one or more further individual and distinct stationary finger gestures on the fingerprint sensor 169 with the corresponding finger (e.g., the user's left index finger) to collect fingerprint information about the missing areas of the corresponding finger's fingerprint (e.g., edges) from the previously collected fingerprint information and complete the registration of the second fingerprint (corresponding to the user's left index finger). In Figure 5R, device 100 displays the progress indicator 558 in the third state 558-c. For example, in the third state 558-c, the progress indicator 510 is magnified to show a thinner ridge around a larger ellipse enclosing the internal region of the thickened ridge. In Figure 5R, the internal region of the progress indicator 558 corresponds to the unenlarged progress indicator 558 included in the first registration interface shown in Figures 5O to 5Q. In this example, a larger amount of ridges in the internal region of the progress indicator 558 are thicker in the third state 558-c compared to the second state 510-b in Figure 5P. The third state 558-c of the progress indicator 558 indicates that more fingerprint information has been collected, but one or more further finger gestures are required to register a second fingerprint (e.g., a fingerprint corresponding to the user's left index finger). Figure 5R also shows that device 100 detects fingerprint 568 (e.g., corresponding to the user's left index finger) on the fingerprint sensor 169 as part of a fourth finger gesture (e.g., a fourth touch and rest gesture) and collects fingerprint information from the fourth finger gesture.

[0214] Figure 5S shows device 100 with a changed appearance of the progress indicator 558 in response to the detection of a fourth finger gesture in Figure 5R. In Figure 5S, device 100 displays the progress indicator 558 in the fourth state 510-d. In Figure 5S, a portion of the ridge on the outer edge of the progress indicator 558 is thicker in the fourth state 510-d compared to the third state 510-c in Figure 5R. The fourth state 510-d of the progress indicator 558 indicates that more fingerprint information has been collected, but one or more further finger gestures are required to register a second fingerprint (for example, a fingerprint corresponding to the user's left index finger). In other words, the fourth state 510-d of the progress indicator 558 is incomplete and does not indicate completion, and therefore one or more further finger gestures are required to register a second fingerprint. Figure 5S also shows that device 100 detects a fingerprint 569 (e.g., corresponding to the user's left index finger) on the fingerprint sensor 169 as part of a fifth finger gesture (e.g., a fifth touch and placement gesture) and collects fingerprint information from the fifth finger gesture.

[0215] Figure 5T shows device 100 displaying a third fingerprint registration interface on the touchscreen 112 in response to the detection of a fifth finger gesture in Figure 5S. In Figure 5T, the third fingerprint registration interface indicates that the registration of a second fingerprint (e.g., a fingerprint corresponding to the user's left index finger) to device 100 has been successful. In Figure 5T, the third fingerprint registration interface, when activated, includes a “Continue” box 570 that causes device 100 to redisplay the fingerprint setup interface. Figure 5T also shows that device 100 detects a contact 572 (e.g., a tap gesture) at the location on the touchscreen 112 corresponding to the “Continue” box 570.

[0216] Figures 5U to 5W show that when a registered fingerprint is detected, the registered fingerprint is highlighted in the fingerprint setting interface.

[0217] Figure 5U shows device 100 displaying a fingerprint setting interface on the touchscreen 112 in response to the detection of contact 570 in Figure 5T. In Figure 5U, the list of registered fingerprints includes a "Fingerprint 1" box 552, a "Fingerprint 2" box 574, and an "Add Fingerprint" box 554. When activated, the "Fingerprint 1" box 552 changes the appearance of the "Fingerprint 1" box 552, allowing the user to edit the name of a registered fingerprint. When activated, the "Fingerprint 2" box 574 changes the appearance of the "Fingerprint 2" box 574, allowing the user to edit the name of a registered fingerprint. When activated, the "Add Fingerprint" box 554 starts the fingerprint registration process for registering additional fingerprints on device 100. For example, registered "fingerprint 1" corresponds to the first fingerprint registered during the registration process shown in Figures 5B to 5K (for example, the fingerprint corresponding to the user's right index finger), and registered "fingerprint 2" corresponds to the second fingerprint registered during the registration process shown in Figures 5N to 5T (for example, the fingerprint corresponding to the user's left index finger).

[0218] Figure 5U also shows that device 100 detects fingerprint 576 (for example, corresponding to the user's left index finger) on fingerprint sensor 169. Upon detection of fingerprint 576, device 100 highlights the registered fingerprint corresponding to the detected fingerprint (if any) in the list of registered fingerprints. In Figure 5U, for example, device 100 informs the user that the detected fingerprint 576 corresponds to the registered "fingerprint 2" by increasing the thickness of the border of the "fingerprint 2" box 574.

[0219] Figure 5V shows a device 100 that detects a fingerprint 578 (for example, corresponding to the user's right index finger) on a fingerprint sensor 169. Upon detection of fingerprint 578, device 100 highlights the registered fingerprint corresponding to the detected fingerprint (if any) in the list of registered fingerprints. In Figure 5V, for example, device 100 informs the user that the detected fingerprint 578 corresponds to the registered "fingerprint 1" by increasing the thickness of the border of the "fingerprint 1" box 552.

[0220] Figure 5W shows a device 100 that detects a fingerprint 580 (for example, corresponding to the user's left thumb). Upon detecting a fingerprint 580, if device 100 determines that the detected fingerprint 580 does not correspond to any of the registered fingerprints, it does not highlight any of the registered fingerprints in the list of registered fingerprints. In Figure 5W, for example, device 100 indicates that the detected fingerprint 580 does not correspond to any of the registered fingerprints by maintaining the display of the fingerprint setting interface.

[0221] Figures 5X to 5AA show the limited operation performed when a registered fingerprint is detected.

[0222] Figure 5X shows device 100 displaying a lock screen on touchscreen 112. In Figure 5X, for example, device 100 is in a locked or restricted access mode. Figure 5X also shows device 100 detecting a fingerprint 582 (for example, corresponding to the user's right index finger) on fingerprint sensor 169.

[0223] Figure 5Y shows device 100 displaying the home screen on the touchscreen 112 in response to the detection of fingerprint 582 in Figure 5X and the determination that fingerprint 582 corresponds to a registered fingerprint. For example, fingerprint 582 corresponds to the user's right index finger registered as the first fingerprint in Figures 5B to 5K. In Figure 5Y, for example, device 100 is unlocked or in unrestricted access mode.

[0224] Figure 5Z shows device 100 displaying a lock screen on touchscreen 112. In Figure 5Z, for example, device 100 is in a locked or restricted access mode. Figure 5Z also shows device 100 detecting a fingerprint 584 (for example, corresponding to the user's right thumb) on fingerprint sensor 169.

[0225] Figure 5AA shows device 100 maintaining the display of the lock screen on the touchscreen 112 in response to the detection of fingerprint 584 in Figure 5Z and the determination that fingerprint 584 does not correspond to a registered fingerprint. In Figure 5AA, for example, device 100 is in a locked or restricted access mode.

[0226] Figures 5BB to 5EE show how the appearance of the progress indicator changes in response to a series of individual and distinct static finger gestures.

[0227] Figure 5BB shows the appearance of a progress indicator after several individual and distinct stationary finger gestures (e.g., touch and rest gestures). In Figure 5BB, the progress indicator is a simulated fingerprint with multiple ridges. In Figure 5BB, the ridges of the progress indicator become thicker (or darker) as fingerprint information is collected from the finger gestures. In some embodiments, the ridges of the progress indicator thicken according to a predetermined pattern. In Figure 5BB, for example, the appearance of the progress indicator after finger gesture 5 is the same as after finger gesture 4. This is because no fingerprint information was collected during finger gesture 5. In this embodiment, fingerprint information was not collected during finger gesture 5 because the user did not place their finger on the fingerprint sensor for a sufficient length (e.g., message 522 in Figure 5F), the user clicked the home button (e.g., message 564 in Figure 5Q), or the user failed to move their finger between finger gestures (message 516 in Figure 5D). In Figure 5BB, the progress indicator expands after finger gesture 7 to show that further fingerprint information needs to be collected about the edges of the fingerprint in order to register the fingerprint.

[0228] Figure 5CC shows the appearance of the progress indicator after several individual and distinct stationary finger gestures (e.g., touch and rest gestures). In Figure 5CC, the progress indicator includes several concentric circles (e.g., mimicking the center of a target). In Figure 5CC, the circles (or rings) of the progress indicator are filled in from the innermost circle as fingerprint information is collected from the finger gestures. In Figure 5CC, for example, the appearance of the progress indicator after finger gesture 5 is the same as after finger gesture 4. This is because no fingerprint information was collected during finger gesture 5. In this embodiment, fingerprint information was not collected during finger gesture 5 because the user did not place their finger on the fingerprint sensor for a sufficient length (e.g., message 522 in Figure 5F), the user clicked the home button (e.g., message 564 in Figure 5Q), or the user failed to move their finger between finger gestures (message 516 in Figure 5D). In Figure 5CC, the progress indicator expands after finger gesture 7 to indicate that further fingerprint information needs to be collected to register the fingerprint.

[0229] Figure 5DD shows the appearance of the progress indicator after several individual and distinct stationary finger gestures (e.g., touch and rest gestures). In Figure 5DD, the progress indicator includes multiple progress indicator portions (e.g., hexagonal geometric shapes in a honeycomb layout). In Figure 5DD, the progress indicator portions of the progress indicator (e.g., hexagons) are filled in relative to the locations of fingerprint information collected from previous finger gestures. In Figure 5DD, for example, after finger gesture 1 is performed, the progress indicator portion in the lower left region of the progress indicator is filled in, indicating that fingerprint information for the lower left region of the fingerprint has been collected from finger gesture 1. In Figure 5DD, the progress indicator is enlarged after finger gesture 6, indicating that further fingerprint information needs to be collected about the edges of the fingerprint in order to register the fingerprint. In Figure 5DD, for example, the appearance of the progress indicator after finger gesture 10 is the same as after finger gesture 9. This is because no fingerprint information was collected during finger gesture 10. In this embodiment, fingerprint information was not collected during the finger gesture 10 because the user did not place their finger on the fingerprint sensor for a sufficient length of time (e.g., message 522 in Figure 5F), because the user clicked the home button (e.g., message 564 in Figure 5Q), or because the user failed to move their finger between finger gestures (message 516 in Figure 5D).

[0230] Figure 5EE shows the appearance of the progress indicator after several individual and distinct stationary finger gestures (e.g., touch and rest gestures). In Figure 5EE, the progress indicator (e.g., a partially displayed sphere) includes multiple progress indicator portions (e.g., framed regions of the partially displayed sphere). In Figure 5EE, the progress indicator portions of the progress indicator (e.g., framed regions) are filled in with the locations of fingerprint information collected from previous finger gestures. In Figure 5EE, for example, after finger gesture 1 is performed, the progress indicator portion near the equatorial source of the progress indicator is filled in, indicating that fingerprint information about the center of the fingerprint has been collected from finger gesture 1. In Figure 5EE, for example, the appearance of the progress indicator after finger gesture 9 is the same as after finger gesture 8. This is because no fingerprint information was collected during finger gesture 9. In this embodiment, fingerprint information was not collected during the finger gesture 9 because the user did not place their finger on the fingerprint sensor for a sufficient length of time (e.g., message 522 in Figure 5F), because the user clicked the home button (e.g., message 564 in Figure 5Q), or because the user failed to move their finger between finger gestures (message 516 in Figure 5D).

[0231] Figures 6A to 6D are flowcharts illustrating a method 600 for registering fingerprints using a device, according to several embodiments. The method 600 is performed on an electronic device having a display and a touch-sensing surface (e.g., device 300 in Figure 3, or portable multifunction device 100 in Figure 1A). In some embodiments, the display is a touchscreen display, and the fingerprint sensor is on the display. In some embodiments, the display is separate from the fingerprint sensor. Some operations of the method 600 are optionally combined, and / or the order of some operations is optionally changed.

[0232] As described below, Method 600 provides an intuitive method for registering fingerprints using a device. This method reduces the cognitive burden on the user when registering fingerprints using a device, thereby creating a more efficient human-machine interface. In the case of battery-operated electronic devices, power is saved and the time interval between battery charges is extended by enabling the user to register fingerprints more quickly and efficiently using the device.

[0233] The device displays a fingerprint registration interface (602). In some embodiments, the fingerprint registration interface is displayed as part of the device setup process. For example, Figures 5A–5M show a device setup process that includes the fingerprint registration process in Figures 5B–5K, the setup process for purchase in Figure 5L, and the passcode setup process in Figure 5M. In Figures 5B–5K, the fingerprint registration process includes a first registration interface in Figures 5B–5G with a non-magnified progress indicator, a second registration in Figures 5H–5J with a magnified progress indicator, and a third registration interface in Figure 5K with text indicating that the fingerprint registration process was successful. In some embodiments, the fingerprint registration interface is displayed during the device setup process, before the passcode setup interface is displayed. For example, the fingerprint registration process shown in Figures 5B–5K occurs before the passcode setup interface in Figure 5M is displayed, in response to the detection of contact 506 at the location corresponding to the “Set Up Now” box 502 in Figure 5A.

[0234] In some embodiments, if the fingerprint registration interface is closed without registering a fingerprint, the passcode setting interface is displayed. For example, in response to contact being detected at the location corresponding to the "Set Later" box 504 in Figure 5A, the device displays the passcode setting interface in Figure 5M.

[0235] In some embodiments, the fingerprint registration interface is displayed as part of the device configuration user interface. For example, Figures 5O–5T show a fingerprint registration process initiated in response to the detection of a contact 556 at the location corresponding to the “Add Fingerprint” box 554 in the fingerprint configuration interface of Figure 5N. In Figures 5O–5T, the fingerprint registration process includes a first registration interface in Figures 5O–5Q with a non-magnified progress indicator, a second registration in Figures 5R–5S with a magnified progress indicator, and a third registration process in Figure 5T with text indicating that the fingerprint registration process was successful.

[0236] The device detects multiple individual and distinct stationary finger gestures performed on the fingerprint sensor with the corresponding finger (604). For example, multiple individual and distinct stationary finger gestures are gestures in which the corresponding finger does not move across the fingerprint sensor, such as tap and hold gestures on the fingerprint sensor. Thus, in some embodiments, the multiple finger gestures are not swipe gestures on the fingerprint sensor. For example, device 100 detects seven individual and distinct finger gestures (e.g., touch and rest gestures) on the fingerprint sensor 169 during the fingerprint registration process shown in Figures 5B to 5K. In another embodiment, device 100 detects five individual and distinct finger gestures (e.g., touch and rest gestures) on the fingerprint sensor 169 during the fingerprint registration process shown in Figures 5N to 5K.

[0237] The device collects fingerprint information from a number of separate and distinct stationary finger gestures performed with the corresponding finger (606). For example, device 100 collects (or attempts to collect) fingerprint information from a fingerprint detected on the fingerprint sensor 169 as part of each of seven separate and distinct finger gestures (e.g., touch and rest gestures) during the fingerprint registration process shown in Figures 5B to 5K. In another embodiment, device 100 collects (or attempts to collect) fingerprint information from a fingerprint detected on the fingerprint sensor 169 as part of each of seven separate and distinct finger gestures (e.g., touch and rest gestures) during the fingerprint registration process shown in Figures 5N to 5T.

[0238] In some embodiments, fingerprint information from multiple individual and distinct static finger gestures is collected for an area of ​​the corresponding finger's fingerprint that is at least twice as large as the area that can be captured by the fingerprint sensor during a single static finger gesture (608). For example, it is not possible to capture an entire fingerprint based on a single static finger gesture because the fingerprint sensor is substantially smaller than the relevant area of ​​the fingerprint. In some embodiments, the fingerprint information collected from multiple individual and distinct static finger gestures is for an area of ​​the corresponding finger's fingerprint that is 100 mm 2 While it can handle a larger area, the fingerprint sensor is 50mm. 2 or 25mm 2 It has a smaller sensor area, such as the following:

[0239] In some embodiments, while the corresponding finger is on the fingerprint sensor during a corresponding stationary gesture, the device collects fingerprint information (610), and after the fingerprint information has been collected, the device provides haptic feedback to indicate that the fingerprint information has been collected. For example, the device vibrates slightly to indicate to the user that fingerprint information for the current stationary finger gesture has been collected and that the next finger gesture can be performed. In some embodiments, the device requires some corresponding time to collect the fingerprint information, and the haptic feedback is given after the finger has been on the fingerprint sensor for at least that amount of time. For example, message 522 in Figure 5F indicates that the device 100 was unable to collect fingerprint information from the fourth finger gesture detected in Figure 5E because the user did not keep their finger on the fingerprint sensor 169 for long enough time for the fingerprint information to be collected. In some embodiments, message 522 includes a command instructing the user to keep their finger on the fingerprint sensor 169, which is integrated with the home button 204, until the user feels a slight vibration indicating that the fingerprint has been collected and the user may remove their finger from the fingerprint sensor 169. In some implementations, the corresponding time to collect fingerprint information from each fingerprint gesture is less than 1 second. In some implementations, the corresponding time to collect fingerprint information from each fingerprint gesture is less than 1 second and longer than 0.1 seconds. In some implementations, the corresponding time to collect fingerprint information from each fingerprint gesture is at least 0.25 seconds and less than 0.75 seconds.

[0240] In some embodiments, the fingerprint registration interface includes a progress indicator (612), and in response to the detection of a corresponding stationary finger gesture made with a corresponding finger on the fingerprint sensor, the device changes the appearance of the progress indicator to indicate that further fingerprint information has been collected from the corresponding stationary finger gesture. In Figures 5B–5K, the fingerprint registration process includes a first registration interface in Figures 5B–5G with a non-magnified progress indicator, and a second registration in Figures 5H–5J with a magnified progress indicator. In this example, the appearance of the progress indicator changes (e.g., the ridge becomes a thicker line) as fingerprint information is collected from multiple individual and distinct finger gestures (e.g., touch and rest gestures).

[0241] In some embodiments, the fingerprint registration interface also includes a message prompting the user to place their finger on the fingerprint sensor in a typical manner, and the progress indicator is a simulated / stock fingerprint. For example, the first registration interface in Figures 5B–5G includes a command instructing the user to perform multiple finger gestures (e.g., touch and place gestures) on the fingerprint sensor 169 integrated with the home button 204. In Figures 5B–5J, for example, the progress indicator 510 is a simulated fingerprint.

[0242] In some embodiments, changes in the appearance of the progress indicator indicate the amount of fingerprint information collected relative to the amount of fingerprint information required to register a fingerprint. Figures 5BB to 5EE show changes in the appearance of various progress indicators after several individual and distinct finger gestures (e.g., touch and rest gestures). Each of the progress indicators in Figures 5BB to 5EE shows the amount of fingerprint information collected in comparison to the amount of fingerprint information required to register a fingerprint. In Figure 5BB, for example, thick ridges indicate the amount of fingerprint information collected, and thin ridges indicate the amount of fingerprint information not collected. In Figure 5CC, for example, filled (or shaded) circles / rings indicate collected fingerprint information, and the total number of circles / rings indicates the total amount of fingerprint information required to register a fingerprint. In Figure 5DD, for example, filled (or shaded) hexagons indicate collected fingerprint information, and the total number of hexagons indicates the total amount of fingerprint information required to register a fingerprint. In Figure 5EE, for example, partially displayed spherical filled (or shaded) box areas represent collected fingerprint information, and the total number of partially displayed spherical box areas represents the total number of fingerprint information items required to register a fingerprint.

[0243] In some embodiments, as further fingerprint information is collected, portions of the progress indicator are filled in in a predetermined order, regardless of which fingerprint portion was detected. In Figures 5B to 5J, for example, the ridges of the progress indicator 510 thicken according to a predetermined pattern, regardless of which fingerprint portion was detected. In some embodiments, portions of the progress indicator are filled in based on the portion of the fingerprint from which fingerprint information has been collected. In Figure 5DD, for example, the progress indicator includes multiple progress indicator portions (e.g., a hexagonal geometric shape in a honeycomb layout). In Figure 5DD, the progress indicator portions of the progress indicator (e.g., hexagons) are filled in relative to the locations of fingerprint information collected from previous finger gestures. In Figure 5EE, the progress indicator (e.g., a partially displayed sphere) includes multiple progress indicator portions (e.g., a framed area of ​​a partially displayed sphere). In Figure 5EE, the progress indicator portions of the progress indicator (e.g., a framed area) are filled in relative to the locations of fingerprint information collected from previous finger gestures.

[0244] In some embodiments, the progress indicator includes a portion of the surface of a three-dimensional object (e.g., a sphere or other ellipse) (614). In Figure 5EE, the progress indicator mimics a sphere in which a portion of the surface of the sphere is displayed.

[0245] In some embodiments, the progress indicator takes the shape of a fingerprint (e.g., a stock or imitation fingerprint) (616) and includes lines representing the ridges of the fingerprint, and changing the appearance of the progress indicator includes coloring some of the ridges. In Figure 5BB, for example, the progress indicator is an imitation fingerprint with multiple ridges. In this example, the ridges of the progress indicator become thicker or colored as fingerprint information is collected from multiple finger gestures.

[0246] In some embodiments, the progress indicator includes multiple concentric circles (618), and changing the appearance of the progress indicator includes filling one of the multiple concentric circles with a default fill (e.g., a default color and / or pattern). In Figure 5CC, the progress indicator includes multiple concentric circles (e.g., mimicking the center of a target). In some embodiments, the concentric circles are filled with a default fill, starting from the innermost circle and ending with the outermost circle. In Figure 5CC, the circles (or rings) of the progress indicator are filled in from the innermost circle as fingerprint information is collected from the finger gesture. In some embodiments, the concentric circles are filled with a default fill, starting from the outermost circle and ending with the innermost circle.

[0247] In some embodiments, the progress indicator includes multiple progress indicator portions corresponding to the fingerprint portions of the corresponding fingerprint (620), and as fingerprint information is collected from the corresponding fingerprint portion, the device changes the appearance of the corresponding progress indicator portion to indicate that fingerprint information has been collected from that corresponding fingerprint portion. In some embodiments, the progress indicator portion is a depiction of fingerprint ridges. For example, after each finger gesture, the user's fingerprint corresponding to the fingerprint information collected from the previous finger gesture is presented in the progress indicator. In this example, the progress indicator mimics a typical image of the user's fingerprint constructed from multiple finger gestures (e.g., a patchwork of images or scans of the user's fingerprint). In this example, once a complete typical image of the user's fingerprint is presented, the user's fingerprint is registered using the device. In some embodiments, the typical image of the user's fingerprint is deleted from the device after the fingerprint has been registered. In some embodiments, the progress indicator portion is a geometric shape (e.g., a hexagon in a honeycomb layout). In Figure 5DD, the progress indicator mimics a honeycomb layout having multiple progress indicator portions, each progress indicator portion being a hexagonal geometric shape. In Figure 5DD, the hexagon of the progress indicator is filled in according to the location of the fingerprint information collected from the previous finger gesture. In Figure 5EE, the progress indicator mimics a partially displayed sphere having multiple progress indicator parts, each progress indicator part being a framed area of ​​the partially displayed sphere. In Figure 5EE, the framed areas of the progress indicator are filled in according to the location of the fingerprint information collected from the previous finger gesture.

[0248] After collecting fingerprint information, the device determines, based on the fingerprint information collected for the corresponding finger, whether the collected fingerprint information is sufficient to register the fingerprint of the corresponding finger using the device (622). In some embodiments, the maximum number of images captured from each finger gesture can be combined to generate the required fingerprint information. For example, in some implementations, up to 15 images from each of 15 finger gestures may be combined to generate the required fingerprint information.

[0249] In some embodiments, the collected fingerprint information is sufficient to register the fingerprint of the corresponding finger when the collected fingerprint information meets a predetermined criterion. In some embodiments, the predetermined criterion includes a threshold amount of fingerprint information (e.g., a threshold amount of surface area). In some embodiments, the threshold amount of fingerprint information is a predetermined minimum amount of non-overlapping fingerprint area. For example, 15 images collected from each of 15 finger gestures, 200 mm² 2 It is combined to generate a non-overlapping area of ​​fingerprints, 200mm 2 This is the default minimum area required to register a fingerprint. In some embodiments, the threshold amount of fingerprint information is a multiple of the surface area of ​​the fingerprint sensor. For example, if the fingerprint sensor is 25 mm 2 In this case, a sufficient amount of fingerprint information is the area of ​​non-overlapping fingerprints that is eight times the surface area of ​​the fingerprint sensor (for example, 200 mm²). 2 In some embodiments, the default criteria include the quality of a default image collected from multiple finger gestures. For example, if a user's fingerprint from a corresponding finger gesture is too dirty, too faint, or does not meet other default standards, the quality of the image collected from that finger gesture will not meet the quality criteria. In some embodiments, the default criteria require a default degree of correlation between images collected from multiple finger gestures. In some embodiments, the default criteria require that the fingerprint information is collected from the same finger.

[0250] If the device determines that the fingerprint information collected for a corresponding finger is sufficient to register the fingerprint of that finger, the device registers the fingerprint of that finger using the device (624). In Figure 5K, for example, device 100 determines that the first fingerprint (for example, the fingerprint corresponding to the user's right index finger) has been successfully registered using device 100 after the seventh finger gesture in Figure 5I. In Figure 5T, for example, device 100 determines that the second fingerprint (for example, the fingerprint corresponding to the user's left index finger) has been successfully registered using device 100 after detecting the fifth finger gesture in Figure 5S.

[0251] If the device determines that the fingerprint information collected for a corresponding finger is insufficient to register the fingerprint of that finger, it displays a message on the fingerprint registration interface (626) prompting the user to perform one or more additional static finger gestures on the fingerprint sensor with that finger. In Figures 5C to 5I, for example, device 100 determines that the fingerprint information collected for a corresponding finger is insufficient to register the fingerprint of that finger. In Figures 5C to 5G, for example, device 100 displays a command on the first fingerprint registration interface instructing the user to perform one or more additional finger gestures on the fingerprint sensor 169 integrated with the home button 204, and in Figures 5H to 5I, for example, device 100 displays a command on the second fingerprint registration interface instructing the user to adjust their grip to capture the edge of the fingerprint when performing one or more finger gestures on the fingerprint sensor 169 integrated with the home button 204.

[0252] In some embodiments, a message prompting the user to make one or more further finger gestures (628) includes a displayed instruction causing the user to make a subsequent finger gesture different from the corresponding finger gesture. In some embodiments, the device 100 displays one or more default messages or warning notifications prompting the user to make a subsequent finger gesture in a manner that allows for proper collection of fingerprint information.

[0253] In some embodiments, the display message (628) includes a displayed command on the fingerprint sensor to move the finger between each finger gesture to collect information from the fingerprint with fewer finger gestures (e.g., "Move your finger. Move your finger a little between scans."). For example, message 516 in Figure 5D indicates that device 100 was unable to collect fingerprint information from the second finger gesture detected in Figure 5C because the user did not move their finger a little compared to the position of the first finger gesture. In some embodiments, while displaying a command on the fingerprint sensor to move the user's finger more between each finger gesture, device 100 provides negative haptic feedback (e.g., two consecutive vibrations) to attract the user's attention and to inform the user that device 100 was unable to collect fingerprint information from the previous finger gesture.

[0254] In some embodiments, the message includes a displayed command to keep the finger on the fingerprint sensor for a longer period of time (e.g., "Keep your finger on the sensor"). For example, message 522 in Figure 5F indicates that the device 100 was unable to collect fingerprint information from the fourth finger gesture detected in Figure 5E because the user did not keep their finger on the fingerprint sensor 169 for long enough time to collect the fingerprint information. In some embodiments, while displaying a message that includes a displayed command to keep the user's finger on the fingerprint sensor 169 for a longer period of time, the device 100 provides negative haptic feedback (e.g., two consecutive vibrations) to attract the user's attention and inform the user that the device 100 was unable to collect fingerprint information from the previous finger gesture.

[0255] In some embodiments, the message includes a displayed instruction to apply less pressure on the fingerprint sensor (e.g., "Oops, you clicked. Place your finger on the home button until you feel a vibration without clicking"). For example, message 564 in Figure 5Q indicates that the device 100 was unable to collect fingerprint information from the second finger gesture detected in Figure 5P because the user clicked the home button 204 instead of placing their finger on the fingerprint sensor 169, which is integrated with the home button 204. In some embodiments, while displaying an instruction to apply less pressure on the fingerprint sensor 169, the device 100 provides negative haptic feedback (e.g., two consecutive vibrations) to attract the user's attention and inform the user that they need to place their finger on the fingerprint sensor 169 without clicking or pressing the home button 204.

[0256] In some embodiments where the fingerprint registration process is position-dependent, the message includes a displayed instruction to properly position the finger on the fingerprint sensor 169, which has a depiction of the correct finger placement. In some such embodiments, while displaying the instruction to properly position the finger on the fingerprint sensor 169, the device 100 provides negative tactile feedback (e.g., two consecutive vibrations). However, in some other embodiments, the registration process is not position-dependent.

[0257] In some embodiments, a message prompting the user to perform one or more further finger gestures includes instructions for one or more parts or locations of the corresponding fingerprint where the fingerprint information is insufficient or has not yet been collected (630) (for example, the message indicates that the edge of the fingerprint is missing from the collected fingerprint information). In some embodiments, the message includes displayed instructions to change the part of the fingerprint in contact with the fingerprint sensor so that the device can capture a specific part of the fingerprint (for example, an instruction to place the edge of the finger on the fingerprint sensor), and displayed instructions to allow the device to capture more types of fingerprint information (for example, an instruction to move the finger more between finger gestures). In Figures 5H to 5I and 5R to 5S, for example, device 100 displays instructions in a second fingerprint registration interface to the user to adjust their grip when performing one or more further finger gestures on the fingerprint sensor 169 integrated with the home button 204 so that the edge of the fingerprint can be captured. In some embodiments, the message includes a displayed instruction (e.g., an instruction to move the finger less between finger gestures) that causes the device to change the portion of the fingerprint that is in contact with the fingerprint sensor, so that it can better combine information from multiple stationary finger gestures.

[0258] In some embodiments, after changing the appearance of multiple progress indicator portions (for example, by coloring multiple progress indicator portions with corresponding colors), and in accordance with the determination that the fingerprint information collected for the corresponding finger is sufficient to register the fingerprint of the corresponding finger, the device changes the appearance of one or more unchanged progress indicator portions to match those of multiple progress indicator portions (for example, by coloring the entire shape of the fingerprint in the progress indicator with its corresponding color) (632). In Figure 5J, for example, device 100 darkens or thickens all the ridges of the progress indicator 510 (compared to Figure 5I) in accordance with the determination that the fingerprint information collected after detecting the seventh finger gesture in Figure 5I is sufficient to register the fingerprint. In Figure 5CC, for example, device 100 floods the progress indicator after detecting the finger gesture 12 in accordance with the determination that the fingerprint information collected after detecting the finger gesture 12 is sufficient to register the fingerprint.

[0259] In some embodiments, after registering the fingerprint of a corresponding finger using the device, the device receives a request to perform a restricted action (e.g., unlock the device, purchase content or applications for the device, or display personal information on the device) (634), and the device detects the fingerprint on the fingerprint sensor. In Figure 5X, for example, after registering a first fingerprint (e.g., corresponding to the user's right index finger) in Figures 5B to 5K and a second fingerprint (e.g., corresponding to the user's left index finger) in Figures 5N to 5T, the device 100 receives a request to perform a restricted action (e.g., unlock the device 100) while the lock screen is displayed on the touchscreen 112. In this example, the request to perform a restricted action includes a fingerprint 582 (e.g., corresponding to the user's right index finger) on the fingerprint sensor 169. In Figure 5Z, for example, after registering a first fingerprint (e.g., corresponding to the user's right index finger) in Figures 5B to 5K and a second fingerprint (e.g., corresponding to the user's left index finger) in Figures 5N to 5T, device 100 receives a request to perform a limited operation (e.g., unlock device 100) while the lock screen is displayed on the touchscreen 112. In this example, the request includes a fingerprint 584 (e.g., corresponding to the user's right thumb) on the fingerprint sensor 169.

[0260] In some embodiments, the device performs a restricted operation (638) in response to receiving a request to perform a restricted operation (636) and in accordance with the determination that a fingerprint has been registered using the device. In Figure 5Y, for example, in response to receiving a request to unlock the device 100 in Figure 5X and in accordance with the determination that the fingerprint 582 is a registered fingerprint, the device 100 is unlocked (e.g., from restricted operation) and a home screen with multiple application icons is displayed on the touchscreen 112.

[0261] In some embodiments, the device discontinues performing the restricted operation (640) in response to receiving a request to perform a restricted operation (636) and determining that the fingerprint has not been registered using the device. In Figure 5AA, for example, in response to receiving a request to unlock the device 100 in Figure 5Z and determining that the fingerprint 584 is not a registered fingerprint, the device 100 maintains the display of the lock screen on the touchscreen 112 and discontinues unlocking (e.g., the restricted operation).

[0262] In some embodiments, after registering the fingerprint of a corresponding finger using the device, the device displays a fingerprint setting interface (642) having multiple entries, including entries corresponding to each finger's fingerprint and one or more other entries corresponding to other registered fingerprints of fingers other than the corresponding finger; detects a second finger gesture corresponding to the fingerprint of a corresponding finger on the fingerprint sensor and, in response to the detection of the second finger gesture, highlights the fingerprint of the corresponding finger and the corresponding entry (e.g., displaying a frame around the entry, increasing the line thickness of the entry, changing the text or fill color of the entry, etc.). In Figures 5U to 5W, for example, device 100 displays a list of registered fingerprints on the fingerprint setting interface on the touchscreen 112. In this example, the list of registered fingerprints includes a "Fingerprint 1" box 552 associated with a first fingerprint (e.g., corresponding to the user's right index finger) registered in Figures 5N to 5T, and a "Fingerprint 2" box 574 associated with a second fingerprint (e.g., corresponding to the user's left index finger) registered in Figures 5B to 5K. In Figure 5U, for example, when the fingerprint sensor 169 detects a fingerprint 576 (e.g., corresponding to the user's left index finger), the device 100 increases the line thickness of the "Fingerprint 2" box 574 (or highlights it) to indicate that the detected fingerprint 576 corresponds to the registered "Fingerprint 2". In Figure 5V, for example, when the fingerprint sensor 169 detects a fingerprint 578 (e.g., corresponding to the user's right index finger), the device 100 increases the line thickness of the "Fingerprint 1" box 552 (or highlights it) to indicate that the detected fingerprint 578 corresponds to the registered "Fingerprint 1". In Figure 5W, for example, when fingerprint 580 (corresponding to, for example, the user's left thumb) is detected on the fingerprint sensor 169, the device 100 maintains the display of the fingerprint setting interface to indicate that the detected fingerprint 580 does not correspond to any of the registered fingerprints.

[0263] In some embodiments, a given entry can be renamed (for example, by typing a new name into the entry while the fingerprint setting interface is in edit mode) and / or deleted (for example, by swiping across the entry and selecting the delete affordance that appears when the swipe across the entry is detected). In Figure 5N, for example, device 100 displays a fingerprint setting interface with an "edit" affordance 546 on the touchscreen 112. When activated, the "edit" affordance 546 causes device 100 to change the appearance of the fingerprint setting interface (for example, displaying a delete affordance next to each registered fingerprint) and causes device 100 to enter edit mode, which allows the user to delete registered fingerprints or edit their names. In some embodiments, a limited number of fingerprints (e.g., 3, 5, 10, or other reasonable number) can be registered at one time. This is to limit the time required to determine whether a fingerprint detected on the fingerprint sensor matches a registered fingerprint. For example, in some implementations, the number of registered fingerprints is limited so that the determination of whether a fingerprint detected on the fingerprint sensor matches a registered fingerprint can be completed in 0.5 seconds.

[0264] It should be understood that the specific order of operations described in Figures 6A-6D is merely illustrative and is not intended to indicate that the described order is the only order in which the operations can be performed. Those skilled in the art will recognize various ways of rearranging the operations described herein. In addition, it should be noted that the methods described herein and other processing details described herein in relation to them (e.g., those described in paragraph

[0080] ) are applicable in a manner similar to Method 600 described above in relation to Figures 6A-6D. For example, the fingerprints and gestures described above with reference to Method 600 optionally have one or more of the fingerprint and gesture features described herein with reference to other methods described herein (e.g., the methods described in paragraph

[0080] ). For brevity, these details are not repeated here.

[0265] In some embodiments, Figure 7 shows a functional block diagram of an electronic device 700 configured according to the concepts of the various embodiments described. The functional blocks of the device are optionally performed by hardware, software, or a combination of hardware and software to implement the concepts of the various embodiments described. Those skilled in the art will understand that the functional blocks described in Figure 7 are optionally combined or separated into subblocks to implement the concepts of the various embodiments described. Accordingly, the description herein optionally supports any possible combinations or separations, or further definitions of the functional blocks described herein.

[0266] As shown in Figure 7, the electronic device 700 comprises a display unit 702 configured to display a fingerprint registration interface and a fingerprint sensor unit 704. In some embodiments, the electronic device 700 optionally comprises a touch-sensing surface unit 706 configured to receive one or more touch inputs and a haptic feedback unit configured to provide haptic feedback. The electronic device 700 also includes a processing unit 710, which is connected to the display unit 702 and the fingerprint sensor unit 704, and optionally connected to the touch-sensing surface unit 706 and the haptic feedback unit 708. In some embodiments, the processing unit 710 comprises a detection unit 712, a collection unit 714, a determination unit 716, a registration unit 718, a display activation unit 720, a receiving unit 722, an execution unit 724, a highlighting unit 726, and an appearance modification unit 728.

[0267] The processing unit 710 is configured to detect multiple individual and distinct stationary finger gestures performed with the corresponding finger on the fingerprint sensor unit 704 (for example, by the detection unit 712), and to collect fingerprint information from the multiple individual and distinct stationary finger gestures performed with the corresponding finger (for example, by the collection unit 714). After collecting the fingerprint information, the processing unit 710 is configured to determine (for example, by the determination unit 716) whether the collected fingerprint information is sufficient to register the fingerprint of the corresponding finger using the device, based on the fingerprint information collected for the corresponding finger. In accordance with the determination that the collected fingerprint information for the corresponding finger is sufficient to register the fingerprint of the corresponding finger, the processing unit 710 is configured to register the fingerprint of the corresponding finger using the electronic device 700 (for example, by the registration unit 718). If the fingerprint information collected for a corresponding finger is determined to be insufficient to register the fingerprint of that finger, the processing unit 710 is configured to enable the display of a message (for example, by the display enablement unit 720) on the fingerprint registration interface prompting the user to perform one or more further static finger gestures with that corresponding finger on the fingerprint sensor unit 704.

[0268] In some embodiments, fingerprint information from multiple individual and distinct stationary finger gestures is collected for the area of ​​the corresponding finger's fingerprint, which is at least twice the size of the area that can be captured by the fingerprint sensor unit 704.

[0269] In some embodiments, the processing unit 710 is configured to receive a request to perform a restricted operation (for example, by the receiving unit 722) and to detect a fingerprint on the fingerprint sensor 704 (for example, by the detection unit 712). Upon receiving a request to perform a restricted operation, the processing unit 710 performs the restricted operation (for example, by the execution unit 724) if it determines that the fingerprint has been registered using the device, and cancels the execution of the restricted operation if it determines that the fingerprint has not been registered using the device.

[0270] In some embodiments, a message prompting the user to make one or more additional finger gestures includes a displayed command causing the user to make a subsequent finger gesture different from the corresponding finger gesture.

[0271] In some embodiments, a message prompting the user to make one or more further finger gestures includes an indication of one or more parts or locations of a corresponding fingerprint for which fingerprint information is insufficient or has not been collected.

[0272] In some embodiments, the processing unit 710 is configured to collect fingerprint information (for example, in the collection unit 714) while the corresponding finger is on the fingerprint sensor unit 704 during the corresponding stationary gesture. The electronic device 700 includes a haptic feedback unit 708 configured to provide haptic feedback to indicate that the fingerprint information has been collected by the electronic device 700 after the fingerprint information has been collected.

[0273] In some embodiments, after registering the fingerprint of a corresponding finger with the electronic device 700, the processing unit 710 activates a fingerprint setting interface having multiple entries, including an entry corresponding to the fingerprint of the corresponding finger and one or more other entries corresponding to other registered fingerprints of other fingers other than the corresponding finger (for example, in the display activation unit 720), detects a second finger gesture corresponding to the fingerprint of the corresponding finger on the fingerprint sensor unit 704 (for example, in the detection unit 712), and highlights the entry corresponding to the fingerprint of the corresponding finger (for example, in the highlighting unit 726) in response to the detection of the second finger gesture.

[0274] In some embodiments, the fingerprint registration interface includes a progress indicator, and in response to detection on the fingerprint sensor 704, the processing unit 710 changes the appearance of the progress indicator (for example, by the appearance changing unit 728) to indicate that further fingerprint information has been collected from the corresponding stationary finger gesture.

[0275] In some embodiments, the progress indicator includes a portion of the surface of a three-dimensional object.

[0276] In some embodiments, the progress indicator takes the shape of a fingerprint and includes lines representing the ridges of the fingerprint, and changing the appearance of the progress indicator includes coloring some of the ridges (for example, in the appearance changing unit 728).

[0277] In some embodiments, the progress indicator includes multiple concentric circles, and changing the appearance of the progress indicator includes filling one of the multiple concentric circles with a default fill (for example, in the appearance change unit 728).

[0278] In some embodiments, the progress indicator includes a plurality of progress indicator portions corresponding to the fingerprint portion of the corresponding fingerprint, and when fingerprint information is collected from the corresponding fingerprint portion, the processing unit 710 is configured to change the appearance of the corresponding progress indicator portion (for example, by the appearance changing unit 728) to indicate that fingerprint information has been collected from the corresponding fingerprint portion.

[0279] In some embodiments, the processing unit 710 is configured to change the appearance of one or more unchanged progress indicator portions to match the appearance of the (already changed) progress indicator portions (for example, by the appearance changing unit 728) after changing the appearance of a plurality of progress indicator portions and determining that there is sufficient fingerprint information collected for the corresponding fingers to register the fingerprints of the corresponding fingers.

[0280] The operation of the information processing method described above is performed selectively by activating one or more functional modules within the information processing device, such as a general-purpose processor (for example, those described above in relation to Figures 1A and 3) or an application-specific chip.

[0281] The operations described above, with reference to Figures 6A to 6D, are optionally performed by the components shown in Figure 1A, Figure 1B, or Figure 7. For example, the detection operation 602, the collection operation 606, the determination operation 622, and the registration operation 624 are optionally performed by the event sorter 170, the event recognition unit 180, and the event handler 190. The event monitor 171 of the event sorter 170 detects contact on the touch-sensitive display 112, and the event dispatcher module 174 distributes the event information to application 136-1. Each event recognition unit 180 of application 136-1 compares the event information with its respective event definition 186 and determines whether the first contact at the first position on the touch-sensitive surface corresponds to a default event or sub-event, such as the selection of an object on the user interface. When a default event or sub-event is detected, the event recognition unit 180 activates the event handler 190 associated with the detection of the event or sub-event. The event handler 190 optionally uses or calls either the data updater 176 or the object updater 177 to update the application's internal state 192. In some embodiments, the event handler 190 accesses the corresponding GUI updater 178 to update what is displayed by the application. Similarly, it will be obvious to those skilled in the art how other processes are carried out based on the components shown in Figures 1A and 1B. Perform actions based on fingerprints

[0282] Many electronic devices are configured to perform various actions. Existing methods for performing actions typically require performing a corresponding action in response to a corresponding input. For example, in existing methods, the user typically provides an input to perform a single action. When the user wants to perform a different action, they need to navigate through a menu or provide a different input to perform the different action. In addition, certain secure actions involve personal information (e.g., credit card information, passwords, etc.) or restricted functionality. Such secure actions typically require user authentication (e.g., using a passcode). Therefore, performing multiple actions, including secure actions, is cumbersome and inefficient. In the embodiments described below, an improved method for performing actions is obtained by performing multiple actions in response to a single input. Non-secure actions (e.g., resetting a display dimming timer) are performed in response to a fingerprint input, regardless of the fingerprint's identification information (e.g., whether the fingerprint belongs to an authorized user), while secure actions (e.g., revealing personal information) are performed in response to a fingerprint input only when the fingerprint input matches a pre-registered (e.g., registered) fingerprint. This method streamlines the process of performing multiple actions in response to fingerprint input, thereby eliminating the need for additional and separate steps to perform those actions.

[0283] In some embodiments, the device is an electronic device comprising a separate display (e.g., display 450) and a separate touch-sensitive surface (e.g., touch-sensitive surface 451). In some embodiments, the device is a portable multifunction device 100, where the display is a touchscreen 112 and the touch-sensitive surface includes a tactile output generator 167 on the display (Figure 1A). The device described below with reference to Figures 8A-8W and 9A-9B includes one or more fingerprint sensors 169. In some embodiments, the one or more fingerprint sensors include one or more integrated fingerprint sensors 359-1 (Figure 4B) that are integrated with the touch-sensitive surface (e.g., a separate touch-sensitive surface 451 or a touch-sensitive display system 112). In some embodiments, the one or more fingerprint sensors include a separate fingerprint sensor 359-2 (Figure 4B) that is separate from the touch-sensitive surface (e.g., a separate touch-sensitive surface 451 or a touch-sensitive display system 112). Unless otherwise specified, the fingerprint sensor 169 described below is optionally an integrated fingerprint sensor 359-1 or a separate fingerprint sensor 359-2, depending on the hardware and software configuration of the device including the fingerprint sensor 169. For convenience of explanation, embodiments described with reference to Figures 8A-8W and 9A-9B will be discussed with reference to the display 450, a separate touch-sensing surface 451, and a separate fingerprint sensor 359-2, but similar operations are optionally performed on the device by the integrated fingerprint sensor 359-1 in response to detecting inputs described in Figures 8A-8W on the integrated fingerprint sensor 359-1 while the user interface shown in Figures 8A-8B is displayed on the display 450. Furthermore, similar operations are optionally performed on a device having a touchscreen 112 while displaying the user interface shown in Figures 8A to 8W on the touchscreen 112 in response to the detection of contact shown in Figures 8A to 8W on the fingerprint sensor 169 (e.g., integrated fingerprint sensor 359-1 or separate fingerprint sensor 359-2).

[0284] Figures 8A to 8W show exemplary user interfaces for performing fingerprint-based operations according to several embodiments.

[0285] Figure 8A shows an exemplary user interface for a shopping webpage. The exemplary user interface includes multiple input fields (e.g., 802-1 to 802-8) and representations of information in corresponding input fields (e.g., 804). Representations of information in corresponding input fields are distinguished from the information in the corresponding input fields. These representations are sometimes called organized representations, and the information in these input fields is sometimes called organized information. For example, as shown, an organized representation of information in a corresponding input field indicates that the corresponding input field contains information, but does not reveal the information in the corresponding input field. In Figure 8A, organized information in a corresponding input field is represented by black dots (e.g., a single black dot represents the corresponding character in the corresponding input field), but organized information in a corresponding input field may be represented by any other character, shape, or visual representation that does not directly convey the information in the corresponding input. In some implementations, one or more input fields in the corresponding user interface contain unorganized information, and these input fields represent the information within those fields, while other input fields contain organized information, represented by organized representations.

[0286] Figure 8A also shows the display dimming timer 896-1 and the credential authorization timer 898-1. In Figure 8A, the display dimming timer 896-1 and the credential authorization timer 898-1 are shown in their corresponding reset positions. In some embodiments, the display dimming timer 896-1 is a timer used to determine when to dim the display of device 100. In some embodiments, the credential authorization timer 898-1 is a timer used to determine when a registered fingerprint will no longer be authorized to authenticate the user of device 100. Although the display dimming timer 896-1 and the credential authorization timer 898-1 are shown in Figure 8A to illustrate specific operations of device 100, the display dimming timer 896-1 and the credential authorization timer 898-1 do not necessarily have to be shown on the touchscreen 112. In some embodiments, the display dimming timer 896-1 is shown on the touchscreen 112. In other embodiments, the display dimming timer 896-1 is not shown on the touchscreen 112. In some embodiments, the credential grant timer 898-1 is shown on the touchscreen 112. In other embodiments, the credential grant timer 898-1 is not shown on the touchscreen 112.

[0287] Figure 8B shows the display dimming timer 896-2 and the credential authorization timer 898-2, indicating the elapsed time. As shown in Figure 8B, in some embodiments, the display dimming timer 896-1 expires earlier than the credential authorization timer 898-1. For example, in some embodiments, the display dimming timer 896-1 expires in less than one minute, and the credential authorization timer 898-1 expires in 24 or 48 hours. In some implementations, the dimming timers have an expiration date that the user can select from one of a set of default dimming timer expiration dates, such as one minute, two minutes, five minutes, and ten minutes. In some embodiments, the credential authorization timer has a default expiration date (e.g., 48 hours) that can be overridden by the user or by a corporate policy that includes overriding one or more default settings. When overridden, the authorization timer expiration date is set to a shorter period than the default expiration date (e.g., 24 hours, 12 hours, 6 hours, 4 hours, or 2 hours).

[0288] Figure 8C shows that more time has passed and the display dimming timer 896-3 has expired. In accordance with the determination that the display dimming timer has expired, the touchscreen 112 is automatically dimmed (the brightness of the touchscreen 112 is reduced).

[0289] Figure 8C also shows that while the touchscreen 112 is dimmed, an input 812 (e.g., finger contact or contact using an object) is detected on the fingerprint sensor 169. In some embodiments, if it is determined that the input 812 does not contain a fingerprint (e.g., it is contact using an object such as a pen), the input 812 is ignored (e.g., no action is performed in response to the input 812). In some embodiments, if it is determined that the input 812 contains a fingerprint, one or more actions are performed.

[0290] Figures 8D to 8F show three corresponding sets of actions that may be performed in response to input 812, according to the determination that input 812 contains a fingerprint, according to some embodiments.

[0291] Figure 8D shows an exemplary set of operations performed according to an input 812 (Figure 8C) including a fingerprint, according to one of several embodiments. In Figure 8D, the display dimming timer 896-4 is reset and the touchscreen 112 ceases the dimming state (e.g., the brightness of the touchscreen 112 increases to the brightness of the touchscreen 112 before dimming). In Figure 8D, the credential grant timer 898-4 is not reset. In Figure 8D, the representation (e.g., 804) of information in the corresponding input fields (e.g., 802-1 to 802-8) remains on the touchscreen 112.

[0292] Figure 8E shows a set of alternative actions performed in response to an input 812 including a fingerprint (Figure 8C) according to several embodiments. In Figure 8E, the display dimming timer 896-5 is reset, and the touchscreen 112 stops dimming. In addition, the representation of information in the corresponding input fields (e.g., 802-1 to 802-8) (sometimes called an organized representation) (e.g., 804 in Figure 8C) is replaced with the information in the corresponding input fields (sometimes called an unorganized information). For example, in Figure 8E, the representation of information in the corresponding input fields is replaced with payment information (e.g., credit card number, expiration date, security code, cardholder name, billing address, etc.). In Figure 8F, the credential authorization timer 898-5 is not reset.

[0293] Figure 8F shows yet another set of alternative actions performed in response to an input 812 including a fingerprint (Figure 8C) according to some embodiments. In Figure 8F, the display dimming timers 896-6 are reset, and the touchscreen 112 stops dimming. In addition, the representation of information in the corresponding input fields (e.g., 802-1 to 802-8) (sometimes called the organized representation) (e.g., 804 in Figure 8C) is replaced with the information in the corresponding input fields (sometimes called the unorganized information). Furthermore, the credential authorization timer 898-6 is reset.

[0294] In some embodiments, the corresponding set of operations shown in Figures 8E to 8F is performed upon determination that the fingerprint in input 812 matches a registered fingerprint. However, in some embodiments, the operation shown in Figure 8D is performed regardless of whether the fingerprint in input 812 matches a registered fingerprint (for example, in some embodiments, the operation shown in Figure 8D is performed even when the fingerprint in input 812 does not match a registered fingerprint).

[0295] Figures 8G to 8H show operations performed while the touchscreen 112 is not dimmed, according to several embodiments.

[0296] Figure 8G shows a user interface similar to the one shown in Figure 8B. In Figure 8G, the display dimming timers 896-7 and the credential authorization timers 898-7 have not yet expired. Figure 8G also shows that input 814 has been detected on the fingerprint sensor 169. In some embodiments, input 814 is ignored (e.g., no action is performed in response to input 814) if it is determined that input 814 does not contain a fingerprint (e.g., it is a contact using an object such as a pen). In some embodiments, one or more actions are performed if it is determined that input 814 contains a fingerprint.

[0297] Figure 8H shows that the display dimming timers 896-8 are reset in response to input 814, which includes a fingerprint. In Figure 8H, the credential authorization timers 898-4 are not reset. Also in Figure 8H, the representation (e.g., 804) of the information in the corresponding input fields (e.g., 802-1 to 802-8) remains on the touchscreen 112.

[0298] Figures 8I to 8K show operations performed before the credential adjustment timer 898 expires, according to several embodiments.

[0299] Figure 8I shows the lock screen displayed on the touchscreen 112. In Figure 8I, the credential adjustment timers 898-9 have not yet expired. The display dimming timers (e.g., 896-8 in Figure 8G) are not shown in Figure 8I for brevity. However, those skilled in the art will understand that in some implementations, operations related to the display dimming timers 896 can be performed from the lock screen. For example, in some embodiments, upon determination that the display dimming timers 896 have expired while the touchscreen 112 is displaying the lock screen, the device 100 automatically dims the touchscreen 112 while displaying the lock screen. In some embodiments, upon determination that an input including a fingerprint has been detected on the fingerprint sensor 169, the display dimming timers 896 are reset.

[0300] In Figure 8I, input 816 is detected on the fingerprint sensor 169. In some embodiments, if it is determined that input 816 does not contain a fingerprint (e.g., it is a contact using an object such as a pen), input 816 is ignored (e.g., no action is performed in response to input 816). In some embodiments, if it is determined that input 816 contains a fingerprint, one or more actions are performed.

[0301] Figure 8J shows an exemplary user interface displayed in response to a determination that the fingerprint in input 816 does not match a registered fingerprint. Figure 8J also shows that a separate input 818 is detected on the fingerprint sensor 169. In some embodiments, if it is determined that input 818 does not contain a fingerprint (e.g., it is a contact using an object such as a pen), input 818 is ignored (e.g., no action is performed in response to input 818). In some embodiments, if it is determined that input 818 contains a fingerprint, one or more actions are performed.

[0302] Figure 8K shows that in some embodiments, device 100 is unlocked upon determination that the fingerprint in input 818 matches a registered fingerprint. In some embodiments, unlocking device 100 includes displaying the home screen.

[0303] Figures 8L to 8M show the operations performed while the credential authorization timer 898 is expiring.

[0304] Figure 8L shows the lock screen displayed on the touchscreen 112. In Figure 8L, the credential adjustment timers 898-9 have expired. Figure 8L also shows that input 820 has been detected on the fingerprint sensor 169. In some embodiments, if it is determined that input 820 does not contain a fingerprint (e.g., it is a contact using an object such as a pen), input 820 is ignored (e.g., no action is performed in response to input 820). In some embodiments, if it is determined that input 820 contains a fingerprint, one or more actions are performed.

[0305] Figure 8M shows that in some embodiments, a passcode screen (shown in Figure 8M) is displayed on the touchscreen 112 in response to input 820. In some embodiments, even if the fingerprint in input 820 (Figure 8L) matches a registered fingerprint, the passcode screen is displayed according to the determination that input 820 (Figure 8L) was received while the credential authorization timer 898 has expired.

[0306] In some embodiments, the passcode screen is displayed regardless of whether the fingerprint in the input matches a registered fingerprint, based on the determination that the input, including a fingerprint, was received while the credential authorization timer 898 has expired.

[0307] Figures 8N to 8O illustrate exemplary operations for providing access to restricted functions according to several embodiments.

[0308] Figure 8N shows a user interface that includes one or more selectable user interface objects (e.g., buttons labeled “Network Settings,” “Bluetooth,” and “Sound”). Compared to Figure 8O, one or more selectable user interface objects (e.g., the button labeled “Credential Manager” 806 in Figure 8O) are not displayed on the touchscreen 112. Figure 8N also shows that input 822 has been detected on the fingerprint sensor 169. In some embodiments, input 822 is ignored (e.g., no action is performed in response to input 822) upon determination that input 822 does not contain a fingerprint (e.g., it is a contact using an object such as a pen). In some embodiments, one or more actions are performed upon determination that input 822 contains a fingerprint.

[0309] Figure 8O shows that, following the determination that input 822 matches a registered fingerprint, a selectable user interface object 806 is displayed on the touchscreen 112. Figure 8O also shows that touch input 824 is detected on the touchscreen 112 at the position corresponding to the selectable user interface object 806.

[0310] Figure 8P shows an exemplary user interface (e.g., a credential manager user interface) that appears when a touch input 824 is detected at a location corresponding to a selectable user interface object 806. The exemplary user interface in Figure 8P includes multiple fields and representations of the information within the corresponding fields.

[0311] Figure 8P also shows an unauthorized attempt counter 894-1, which counts the number of unauthorized attempts to perform one or more default secure actions (e.g., revealing personal information or providing access to restricted features).

[0312] To illustrate the specific operation of device 100, the unauthorized trial counter 894-1 is shown in Figures 8P to 8V, although the unauthorized trial counter 894-1 is not necessarily shown on the touchscreen 112. In some embodiments, the unauthorized trial counter 894-1 is shown on the touchscreen 112. In other embodiments, the unauthorized trial counter 894-1 is not shown on the touchscreen 112.

[0313] Figure 8P shows that input 826 is detected on the fingerprint sensor 169. In some embodiments, input 826 is ignored (e.g., no action is performed in response to input 826) if it is determined that input 826 does not contain a fingerprint (e.g., contact with an object such as a pen). In some embodiments, one or more actions are performed if it is determined that input 826 contains a fingerprint. In some embodiments, no action is performed if it is determined that the fingerprint in input 826 does not match a registered fingerprint.

[0314] Figure 8Q shows that, in some embodiments, the number of unauthorized attempts in the unauthorized attempt counter 894-1 to perform one or more default secure actions increases (for example, from zero to one) according to the determination that the fingerprint of input 826 does not match a registered fingerprint. In some embodiments, as shown in Figure 8Q, the representation of information in the corresponding field (sometimes called the organized representation) remains on the touchscreen 112. Figure 8Q shows that input 826 (Figure 8P) is no longer detected on the fingerprint sensor 169. In some embodiments, the number of unauthorized attempts in the unauthorized attempt counter 894-1 to perform one or more default secure actions increases according to the detection of the lift-off of input 826 (Figure 8P) from the fingerprint sensor 169 and according to the determination that the fingerprint in input 826 (Figure 8P) does not match a registered fingerprint.

[0315] Figure 8R shows that input 828 is detected on the fingerprint sensor 169. In some embodiments, input 828 is ignored (e.g., no action is performed in response to input 828) if it is determined that input 828 does not contain a fingerprint (e.g., contact with an object such as a pen). In some embodiments, one or more actions are performed if it is determined that input 828 contains a fingerprint. In some embodiments, no action is performed if it is determined that the fingerprint in input 828 does not match a registered fingerprint.

[0316] Figure 8S shows that, in some embodiments, the number of unauthorized attempts in the unauthorized attempt counter 894-3 to perform one or more default secure actions increases (e.g., from 1 to 2) according to the determination that the fingerprint in input 828 does not match a registered fingerprint. In some embodiments, as shown in Figure 8S, the representation of the information in the corresponding field remains on the touchscreen 112. In Figures 8S to 8U, it is assumed that the number of unauthorized attempts in the unauthorized attempt counter 894-3 satisfies (e.g., matches or exceeds) a default number of unauthorized attempts (e.g., 2, 3, 4, or 5).

[0317] Figure 8S also shows that input 828 (Figure 8R) is no longer detected on the fingerprint sensor 169. In some embodiments, the number of unauthorized attempts to perform one or more default secure actions in the unauthorized attempt counter 894-3 increases in accordance with the detection of the liftoff of input 828 (Figure 8R) from the fingerprint sensor 169 and the determination that the fingerprint in input 828 (Figure 8R) does not match a registered fingerprint.

[0318] Figure 8T shows that input 830 is detected on the fingerprint sensor 169. In some embodiments, input 830 is ignored (e.g., no action is performed in response to input 830) if it is determined that input 830 does not contain a fingerprint (e.g., contact with an object such as a pen). In some embodiments, one or more actions are performed if it is determined that input 830 contains a fingerprint. In some embodiments, no action is performed if it is determined that the fingerprint in input 830 does not match a registered fingerprint.

[0319] Figure 8U shows that even if the fingerprint in input 830 matches a registered fingerprint, the representation of the information in the corresponding field (sometimes called the organized representation) remains on the touchscreen 112 (for example, the information in the corresponding field is not revealed). In some embodiments, the number of unauthorized attempts in the unauthorized attempt counter 894-3 does not increase once the number of unauthorized attempts in the unauthorized attempt counter 894-3 reaches a predetermined number of unauthorized attempts (e.g., 2), as shown in Figure 8U. In some embodiments, the number of unauthorized attempts in the unauthorized attempt counter 894-3 increases for fingerprints in the corresponding input that do not match a registered fingerprint, regardless of whether the number of unauthorized attempts in the unauthorized attempt counter 894-3 has reached a predetermined number of unauthorized attempts.

[0320] In some embodiments, once the number of unauthorized attempts in the unauthorized attempt counter 894-3 reaches a predetermined number of unauthorized attempts, the unauthorized attempt counter 894-3 is reset by providing the correct passcode on the passcode screen (for example, Figure 8M).

[0321] Figures 8V to 8W show the operations performed when the number of unauthorized attempts in the unauthorized attempt counter 894-3 does not reach the predetermined number of unauthorized attempts.

[0322] Figure 8V shows that input 832 has been detected on the fingerprint sensor 169. In some embodiments, input 832 is ignored (e.g., no action is performed in response to input 832) if it is determined that input 832 does not contain a fingerprint (e.g., it is a contact using an object such as a pen). In some embodiments, one or more actions are performed if it is determined that input 832 contains a fingerprint. In some embodiments, no action is performed if it is determined that the fingerprint in input 832 does not match a registered fingerprint.

[0323] Figure 8W shows that, upon determination that the fingerprint in input 832 matches a registered fingerprint, the representation of information in the corresponding field (sometimes called an organized representation) is replaced with information in the corresponding field (sometimes called unorganized or unorganized information). For example, as shown in Figure 8W, the representation of information in the corresponding field is replaced with one or more username and password sets (sometimes called unorganized or unorganized username and passwords). In some embodiments, the unauthorized attempt counter 894-4 (Figure 8V) is reset upon determination that the fingerprint in input 832 matches a registered fingerprint while the number of unauthorized attempts in the unauthorized attempt counter 894-4 (Figure 8V) is less than the default number of unauthorized attempts.

[0324] Figures 9A and 9B are flowcharts illustrating a method 900 for performing fingerprint-based operations according to several embodiments. The method 900 is performed in an electronic device having a display and a touch-sensitive surface (e.g., device 300 in Figure 3, or portable multifunction device 100 in Figure 1A). In some embodiments, the display is a touchscreen display, and the touch-sensitive surface is on the display. In some embodiments, the display is separate from the touch-sensitive surface. Some operations of the method 900 are optionally combined, and / or the order of some operations is optionally changed.

[0325] As described below, Method 900 provides an intuitive way to perform fingerprint-based actions. This method creates a more efficient human-machine interface by reducing the cognitive burden on the user when performing fingerprint-based actions. In the case of battery-operated electronic devices, power is saved and battery charging time is increased by enabling the user to perform fingerprint-based actions faster and more efficiently.

[0326] The device detects a first input using a fingerprint sensor (902). For example, as shown in Figure 8C, input 812 is detected on the fingerprint sensor 169.

[0327] Upon detecting the first input, the device determines whether the first input includes a fingerprint (904).

[0328] In accordance with the determination that the first input contains a fingerprint, the device performs a first action based on the presence of the fingerprint, regardless of the fingerprint identification information (906). In some embodiments, the first action includes resetting the display dimming timer. For example, as shown in Figure 8E, the display dimming timer 896-5 is reset in accordance with the determination that the first input contains a fingerprint. Typically, resetting the display dimming timer has the effect that the display brightness is not automatically dimmed because the dimming timer has not expired (is not in an expired state). Typically, the display brightness is not automatically dimmed as long as a fingerprint continues to be detected on the fingerprint sensor.

[0329] In some embodiments, the device includes a display (908). The device also includes a display dimming timer (e.g., 896-1 in Figure 8A) that starts from a dimming timer start value (e.g., 0 seconds). The device automatically dims the display upon determination that the display dimming timer has expired (e.g., the display dimming timer reaches a predetermined expiration value such as 60 seconds, 120 seconds, etc.). In some embodiments, the display dimming timer stores the time elapsed since the display dimming timer was reset. For example, when 1 second has elapsed since the display dimming timer was reset, the display dimming timer stores 1 second. When 2 seconds have elapsed since the display dimming timer was reset, the display dimming timer stores 2 seconds. In some embodiments, a first operation includes resetting the display dimming timer to the dimming timer start value. In another embodiment, the dimming timer is a countdown timer, the dimming timer expiration value is 0 seconds, and the dimming start value is a value such as 60 seconds, 120 seconds, 300 seconds, etc. In this embodiment, the display is not dimmed as long as the dimming timer is not zero.

[0330] In some embodiments, the device collects information about the fingerprint in contact with the fingerprint sensor at predetermined intervals shorter than the time required for the dimming timer to expire. As long as the fingerprint remains on the fingerprint sensor, the device repeatedly detects the fingerprint to reset the dimming timer, and consequently, in such cases, the display brightness is not automatically dimmed as long as a fingerprint continues to be detected on the fingerprint sensor.

[0331] In accordance with the determination that the fingerprint in the first input matches a registered fingerprint, the device conditionally performs a second action based on the registered fingerprint (910). For example, as shown in Figure 8E, the device reveals personal information (e.g., credit card information) in accordance with the determination that the fingerprint in input 812 (Figure 8C) matches a registered fingerprint. In some embodiments, conditionally performing the second action includes performing the second action in accordance with the determination that the second action is not prevented. In some embodiments, conditionally performing the second action includes canceling the second action in accordance with the determination that the second action is prevented. In some implementations, the second action is prevented in accordance with the determination that the credential authorization timer 898 has expired.

[0332] In some embodiments, the second operation includes one or more of the following: disclosing personal information (e.g., disclosing credit card information as shown in Figure 8E) and providing access to restricted functions (e.g., displaying a selectable user interface object 806 that, when selected, initiates the display of a user interface having restricted functions such as a credential manager function, as shown in Figure 8O) (912).

[0333] In some embodiments, upon detecting a first input, the device cancels the execution of a second operation according to the determination that the first input contains a fingerprint and that the fingerprint in the first input does not match a registered fingerprint (914). For example, as shown in Figures 8G to 8H, upon detecting input 814 (Figure 8G), and according to the determination that input 814 contains a fingerprint and that the fingerprint in input 814 does not match a registered fingerprint, the device cancels the execution of a second operation (for example, in Figure 8H, personal information such as credit card information is not revealed).

[0334] In some embodiments, upon detecting a first input, the device performs a first action without performing a second action (916) according to the determination that the first input contains a fingerprint and that the fingerprint in the first input does not match a registered fingerprint. For example, as shown in Figures 8G to 8H, upon detecting an input 814 (Figure 8G), and according to the determination that the input 814 contains a fingerprint and that the fingerprint in the input 814 does not match a registered fingerprint, the device performs a first action without performing a second action (for example, resetting the display dimming timer 896-8 in Figure 8H) (for example, in Figure 8H, no personal information such as credit card information is revealed).

[0335] In some embodiments, both the first and second operations are performed according to the determination that the first input contains a fingerprint that matches a registered fingerprint (918). For example, as shown in Figures 8C and 8E, both the first operation (e.g., resetting the display dimming timer 896-5) and the second operation (e.g., revealing personal information such as credit card information, as shown in Figure 8E) are performed according to the determination that input 812 (Figure 8C) contains a fingerprint that matches a registered fingerprint.

[0336] In some embodiments, upon determination that a first input contains a fingerprint matching a registered fingerprint, the device performs a third operation, separate from the second operation, based on the registered fingerprint (920). For example, as shown in Figures 8C and 8F, upon determination that input 812 (Figure 8C) contains a fingerprint matching a registered fingerprint, the device performs a third operation (for example, resetting the credential authorization timer 898-6 in Figure 8F).

[0337] In some embodiments, the device includes a credential authorization timer that starts from an authorization timer start value (e.g., zero) (for example, a timer that measures the amount of time that a registered fingerprint is authorized to use device unlock credentials such as a passcode, or purchase credentials such as a credit card number or a password for a store account linked to a credit card number or other payment source) (922). In some embodiments, the credential authorization timer stores the time elapsed since the credential authorization timer was reset. For example, when one hour has elapsed since the credential authorization timer was reset, the credential authorization timer stores one hour. When two hours have elapsed since the credential authorization timer was reset, the credential authorization timer stores two hours.

[0338] In some embodiments, the device prevents the device from being unlocked with a fingerprint (a fingerprint matching a registered fingerprint) after the credential authorization timer has expired (e.g., reached a predetermined expiration value such as 12, 24, or 48 hours). In another embodiment, the credential authorization timer is a countdown timer, the credential authorization timer expiration value is zero seconds, and the credential authorization timer start value is the authorization timer expiration (or a corresponding one), such as any authorization timer expiration described elsewhere in this specification. In this embodiment, the device does not prevent the device from being unlocked (using a fingerprint matching a registered fingerprint) as long as the credential authorization timer has a non-zero value.

[0339] In some embodiments, preventing the device from being unlocked using a fingerprint includes disabling fingerprint unlocking. For example, as shown in Figures 8L to 8M, upon determination that the credential authorization timer 898-12 (Figure 8L) has expired, the device prevents unlocking even if input 820 matches a registered fingerprint. In some embodiments, in response to input 820, the device displays a passcode screen (Figure 8M) instead of unlocking the device. In contrast, in some embodiments, as shown in Figures 8J to 8K, upon determination that the credential authorization timer 898-10 (Figure 8J) has not expired, the device unlocks in response to the fingerprint in input 818 that matches a registered fingerprint (for example, by ceasing to display the unlock screen shown in Figure 8J and instead displaying the home screen shown in Figure 8K).

[0340] In some embodiments, the third operation includes resetting the credential authorization timer to the authorization timer start value. For example, as shown in Figures 8C and 8F, the device performs the third operation (for example, resetting the credential authorization timer 898-5 in Figure 8F) upon determining that input 812 (Figure 8C) contains a fingerprint that matches a registered fingerprint.

[0341] In some embodiments, the first input includes a corresponding fingerprint on a fingerprint sensor (924). The device detects the lift-off of the corresponding fingerprint from the fingerprint sensor. In response to the detection of the lift-off of the fingerprint from the fingerprint sensor and the determination that the corresponding fingerprint does not match a registered fingerprint, the device increments the count of unauthorized attempts to perform a second action (e.g., unauthorized attempts to unlock the device). For example, as shown in Figures 8P and 8Q, in response to the detection of the lift-off of input 826 (Figure 8P) from fingerprint sensor 169 (Figure 8Q) and the determination that the fingerprint in input 826 does not match a registered fingerprint, the device increments the count of unauthorized attempts to perform a second action (e.g., the count of unauthorized attempt counter 894-2) from zero to one. In some embodiments, the count of unauthorized attempts is incremented only after detecting individual fingerprint gestures, including touch-downs and lift-offs of the fingerprint from the fingerprint sensor. Consequently, a long, continuous fingerprint gesture is counted only as a single attempt to perform a second action.

[0342] In some embodiments, after incrementing the count of unauthorized attempts to perform a second operation, the device determines whether a fingerprint invalidation criterion is met (926). The fingerprint invalidation criterion includes a criterion that is met when the count of unauthorized attempts to perform a second operation reaches a default number of unauthorized attempts to perform a second operation. In some embodiments, the count of unauthorized attempts performed in the second operation is considered met when the count of unauthorized attempts to perform a second operation matches the default number of unauthorized attempts to perform a second operation. For example, if the default number of unauthorized attempts to perform a second operation is set to 2, and the count of unauthorized attempts to perform a second operation in unauthorized attempt counter 894-3 (Figure 8T) is 2, then the count of unauthorized attempts reaches the default number of unauthorized attempts to perform a second operation. In some embodiments, the count of unauthorized attempts to perform a second operation is considered to satisfy the default number of unauthorized attempts to perform a second operation when the count of unauthorized attempts to perform a second operation exceeds the default number of unauthorized attempts to perform a second operation.

[0343] In some embodiments, upon determination that a fingerprint invalidation criterion has been met, the device prevents a second action from being performed based on the fingerprint (e.g., by disabling the fingerprint sensor or ignoring a fingerprint detected by the fingerprint sensor that matches a previously registered fingerprint). For example, as shown in Figures 8T to 8U, upon determination that a fingerprint invalidation criterion has been met (e.g., the count of unauthorized attempts to perform the second action has reached a predetermined number of unauthorized attempts to perform the second action), the device prevents a second action from being performed in response to a fingerprint in input 830 that matches a registered fingerprint (e.g., revealing personal information such as a username and password) (for example, in Figure 8U, the disclosure of personal information is maintained on the touchscreen 112, and in Figure 8U, the personal information is not displayed on the touchscreen 112).

[0344] In some embodiments, a first action is performed while detecting the presence of a fingerprint on the fingerprint sensor (928), and a second action is performed in response to detecting the lift-off of a fingerprint from the fingerprint sensor that matches a previously registered fingerprint. For example, in some embodiments, the first action (e.g., resetting the display dimming timer 896-3 in Figure 8C) is performed while detecting input 812 (Figure 8C) containing a fingerprint on the fingerprint sensor 169 (Figure 8C). In contrast, in some embodiments, the second action (e.g., revealing personal information such as credit card information) is performed only after detecting the lift-off of input 812 (Figure 8C) from the fingerprint sensor 169 (Figure 8E).

[0345] It should be understood that the specific order of operations described in Figures 9A-9B is merely illustrative and not intended to indicate that the described order is the only order in which the operations can be performed. Those skilled in the art will recognize various ways of rearranging the operations described herein. For example, in some embodiments, a device uses a fingerprint sensor to detect a first input. In response to detecting the first input, the device determines whether the first input contains a fingerprint, and, in accordance with the determination that the first input contains a fingerprint, performs a first operation based on the presence of a fingerprint, regardless of the fingerprint identification information, and, in accordance with the determination that the fingerprint in the first input matches a registered fingerprint, conditionally performs a second operation based on a registered fingerprint.

[0346] In addition, it should be noted that details of other processes described herein with respect to other methods described herein (e.g., those enumerated in paragraph

[0080] ) are applicable in a similar manner to Method 900 described above with respect to Figures 9A and 9B. For example, the inputs, actions, and credentials described above with reference to Method 900 optionally have one or more of the features of the inputs, actions, and credentials described herein with reference to other methods described herein (e.g., the methods described in paragraph

[0080] ). For brevity, these details are not repeated here.

[0347] In some embodiments, Figure 10 shows a functional block diagram of an electronic device 1000 configured according to the concepts of the various embodiments described. The functional blocks of the device are optionally performed by hardware, software, or a combination of hardware and software to implement the concepts of the various embodiments described. Those skilled in the art will understand that the functional blocks described in Figure 10 are optionally combined or separated into subblocks to implement the concepts of the various embodiments described. Accordingly, the description herein optionally supports any possible combinations or separations, or further definitions of the functional blocks described herein.

[0348] As shown in Figure 10, the electronic device 1000 includes a fingerprint sensor unit 1006 configured to detect a first input, and a processing unit 1008 connected to the fingerprint sensor unit 1006. In some embodiments, the electronic device 1000 includes a display unit 1002 connected to the processing unit 1008 and configured to display a graphical user interface. In some embodiments, the display unit 1002 is connected to the fingerprint sensor unit 1006. In some embodiments, the electronic device 1000 includes a touch-sensing surface unit 1004 connected to the processing unit 1008 and configured to receive touch input. In some embodiments, the processing unit 1008 includes a determination unit 1010, a first operation execution unit 1012, a second operation execution unit 1014, a third operation execution unit 1016, a credential authorization timer unit 1018, a prevention unit 1020, a reset unit 1022, a display dimming timer unit 1024, a dimming unit 1026, a personal information disclosure unit 1028, an access provision unit 1030, and an increment unit 1032.

[0349] The processing unit 1008 is configured to determine (for example, using the determination unit 1010) whether the first input contains a fingerprint in response to detecting the first input. The processing unit 1008 is also configured to perform a first action (for example, using the first action execution unit 1012) based on the presence of a fingerprint, regardless of the fingerprint identification information, in accordance with the determination that the first input contains a fingerprint. The processing unit 1008 is further configured to conditionally perform a second action (for example, using the second action execution unit 1014) based on a registered fingerprint in accordance with the determination (for example, using the determination unit 1010) that the fingerprint in the first input matches a registered fingerprint.

[0350] In some embodiments, the processing unit 1008 is configured to detect a first input and, upon determining that the first input contains a fingerprint and that the fingerprint in the first input does not match a registered fingerprint, to cancel the execution of a second operation (for example, using a prevention unit 1020).

[0351] In some embodiments, the processing unit 1008 is configured to detect a first input and, in response to a determination (for example, using a determination unit 1010) that the first input contains a fingerprint, and a determination that the fingerprint in the first input does not match a registered fingerprint, it performs a first operation (for example, using a first operation execution unit 1012) without performing a second operation.

[0352] In some embodiments, the first and second operations are performed (for example, using the first operation execution unit 1012 and the second operation execution unit 1014) in accordance with a determination (for example, using the determination unit 1010) that the first input contains a fingerprint that matches a registered fingerprint.

[0353] In some embodiments, the processing unit 1008 is configured to perform a third operation, separate from the second operation, based on the registered fingerprint (for example, using a third operation execution unit 1016), upon determining that the first input contains a fingerprint that matches a registered fingerprint.

[0354] In some embodiments, the device includes a credential authorization timer unit 1018 that starts from an authorization timer start value. The processing unit 1008 is configured to prevent the device from being unlocked with a fingerprint (e.g., using a prevention unit 1020) after the credential authorization timer unit 1018 has expired. A third operation includes resetting the credential authorization timer unit 1018 to the authorization timer start value (e.g., using a reset unit 1022).

[0355] In some embodiments, the device includes a display unit 1002 connected to a processing unit 1008. The device includes a display dimming timer unit 1024 that starts from a dimming timer start value. The processing unit 1008 is configured to automatically enable dimming of the display unit 1002 (for example, using a dimming unit 1026) upon determination (for example, using a determination unit 1010) that the display dimming timer unit 1024 has expired. A first operation includes resetting the display dimming timer unit 1024 to the dimming timer start value (for example, using a reset unit 1022).

[0356] In some embodiments, the second operation includes one or more of the following: disclosing personal information (e.g., using a personal information disclosure unit 1028) and providing access to restricted functions (e.g., using an access provision unit 1030).

[0357] In some embodiments, the first input includes a corresponding fingerprint on a fingerprint sensor unit 1006. The fingerprint sensor unit 1006 is configured to detect the lift-off of the corresponding fingerprint from the fingerprint sensor unit 1006, and the processing unit 1008 is configured to increment the count of unauthorized attempts to perform a second operation (e.g., using an increment unit 1032) in response to the detection of the lift-off of the fingerprint from the fingerprint sensor unit 1006 and to the determination (e.g., using a determination unit 1010) that the corresponding fingerprint does not match a registered fingerprint.

[0358] In some embodiments, the processing unit 1008 is configured to determine (e.g., using the determination unit 1010) whether a fingerprint invalidation criterion is met after incrementing the count of unauthorized attempts to perform the second operation. The fingerprint invalidation criterion includes a criterion that is met when the count of unauthorized attempts to perform the second operation reaches a predetermined number of unauthorized attempts to perform the second operation. In accordance with the determination (e.g., using the determination unit 1010) that the fingerprint invalidation criterion is met, the processing unit 1008 is configured to prevent the second operation from being performed based on the fingerprint (e.g., using the prevention unit 1020 and / or the second operation execution unit 1014).

[0359] In some embodiments, a first operation is performed while the presence of a fingerprint is detected on the fingerprint sensor unit 1006 (for example, using a first operation execution unit 1012), and a second operation is performed in response to the detection of a lift-off of a fingerprint from the fingerprint sensor unit 1006 that matches a previously registered fingerprint (for example, using a second operation execution unit 1014).

[0360] The operation of the information processing method described above is performed selectively by activating one or more functional modules within the information processing device, such as a general-purpose processor (for example, those described above in relation to Figures 1A and 3) or an application-specific chip.

[0361] The operations described above, with reference to Figures 9A and 9B, are optionally performed by the components shown in Figures 1A, 1B, or 10. For example, the detection operation 902, the first operation execution operation 906, and the second operation execution operation 910 are optionally performed by the event sorter 170, the event recognition unit 180, and the event handler 190. The event monitor 171 of the event sorter 170 detects contact on the touch-sensitive display 112, and the event dispatcher module 174 distributes the event information to application 136-1. Each event recognition unit 180 of application 136-1 compares the event information with its respective event definition 186 to determine whether the first contact at the first location on the touch-sensitive surface corresponds to a default event or sub-event, such as the selection of an object on the user interface. When a default event or sub-event is detected, the event recognition unit 180 activates the event handler 190 associated with the detection of the event or sub-event. The event handler 190 optionally uses or calls either the data updater 176 or the object updater 177 to update the application's internal state 192. In some embodiments, the event handler 190 accesses the corresponding GUI updater 178 to update what is displayed by the application. Similarly, it will be clear to those skilled in the art how other processes are performed based on the components shown in Figures 1A and 1B. Automatically add data to the credential field and reveal the organized credentials.

[0362] Many applications of modern electronic devices require users to provide credentials in order to access specific information and / or services. For example, e-commerce websites or applications often require users to enter credit card numbers, billing addresses, and shipping addresses in order to make payments. Another example is when users are often required to enter a user ID and / or password before accessing a secure service or other secure information is permitted (e.g., email websites or applications, social networks, etc.). Because users frequently need to provide credentials when using electronic devices, credentials can be stored in the device's memory so that they can be inserted into credential fields without the need for manual entry by the user. However, this presents several security and privacy risks. For example, an unauthorized user could pick up a device that does not belong to that user and make purchases using stored credit card information, or gain access to personal and / or confidential data, applications, websites, etc.

[0363] Furthermore, to protect the privacy and / or security of credentials, they may be displayed in an organized format so that they cannot be read or copied. However, this makes it difficult for users to verify that credentials are entered correctly, or to review and / or edit stored credentials that are typically only displayed in an organized format (for example, in a credential manager interface for users to enter, edit, and otherwise manage stored credentials on a device). ...

Claims

1. It is a method, In an electronic device having one or more processors, memory, and one or more sensors, The system receives one or more inputs corresponding to requests to proceed with individual operations requiring authentication via one or more sensors. In response to receiving one or more of the above inputs, The process of using biometric authentication to authenticate the individual operation is initiated based on the determination that the use of biometric authentication to authenticate the individual operation has been enabled and that the biometric registration in the electronic device has not been changed since the use of biometric authentication to authenticate the individual operation was approved. A method comprising: enabling the use of biometric authentication to authenticate the individual operations, and preventing the use of biometric authentication to authenticate the individual operations in accordance with a determination that the biometric registration in the electronic device has been changed since the use of biometric authentication to authenticate the individual operations was authorized.

2. A method according to claim 1, wherein initiating the process which uses biometric authentication to authenticate the individual operations includes outputting a prompt to provide biometric authentication.

3. The method according to claim 2, To provide biometric authentication, after outputting the prompt, biometric information is received using one or more sensors. A method comprising: performing the individual operations in response to receiving the biometric information using one or more sensors, and in accordance with the determination that the received biometric information matches at least one of the registered sets of biometric information.

4. The method according to claim 3, The aforementioned electronic device further includes a display, A method for performing the individual operations described above, which includes displaying a progress indicator via the display that shows the progress of performing the individual operations.

5. A method according to any one of claims 1 to 4, A method comprising outputting a prompt to re-authenticate the use of biometric authentication for the individual operation in response to the receipt of one or more of the aforementioned inputs, and in accordance with the determination that the use of biometric authentication for authenticating the individual operation has been enabled, and that the biometric registration in the electronic device has been changed since the use of biometric authentication for authenticating the individual operation was authorized.

6. A method according to any one of claims 1 to 5, wherein the biometric authentication is fingerprint authentication.

7. A method according to any one of claims 1 to 6, wherein the individual operations include using credentials.

8. A computer program that causes a computer to perform the method described in any one of claims 1 to 7.

9. It is an electronic device, A memory for storing the computer program described in claim 8, The electronic device includes one or more processors capable of executing the computer program stored in the memory, wherein the electronic device includes one or more processors, memory, and one or more sensors.

10. An electronic device having one or more processors, memory, and one or more sensors, An electronic device comprising means for performing the method described in any one of claims 1 to 7.

Images