User interface for managing access to credentials used in operations

Abstract

The present disclosure relates to a user interface for managing access to credentials used in an operation. The present disclosure as a whole relates to the management of access to credentials. In some examples, an electronic device authorizes the release of credentials used in an operation requiring authorization. In some examples, an electronic device causes a display of one or more steps to be taken to enable an input device for user input. In some examples, an electronic device disambiguates between a command for changing the account actively logged into the device and a command for causing the release of credentials from the security element.

Description

[0001] This application is a divisional application of invention patent application No. 201780069966.2, filed on October 25, 2017, and entitled “User interface for managing access to credentials used in operations”.

[0002] CROSS-REFERENCE TO RELATED APPLICATIONS

[0003] This application claims priority to U.S. Provisional Application Serial No. 62 / 412,819, filed on October 25, 2016, entitled “USER INTERFACE FOR MANAGING ACCESS TO CREDENTIALS FOR USE IN AN OPERATION,” and U.S. Provisional Application Serial No. 62 / 413,300, filed on October 26, 2016, entitled “USER INTERFACE FOR MANAGING ACCESS TO CREDENTIALS FOR USE IN AN OPERATION,” the contents of which are hereby incorporated by reference in their entirety.

[0004] This application is also related to U.S. Patent Application No. 15 / 256,959, filed on September 6, 2016, entitled “DATA VERIFICATION VIA INDEPENDENT PROCESSORS OF A DEVICE,” which is hereby incorporated by reference in its entirety and is included herein in its entirety as Appendix A. This application is also related to U.S. Provisional Patent No. 62 / 368,988, filed on July 29, 2016, entitled “SYSTEMS, DEVICES, AND METHODS FOR DYNAMICALLY PROVIDING USER INTERFACECONTROLS AT A TOUCH-SENSITIVE SECONDARY DISPLAY,” which is hereby incorporated by reference in its entirety and FIGS. 1A to 2D, 17A to 17G, and paragraphs

[00233] to

[00252] , and paragraphs

[00454] to

[00455] of the patent are included herein as Appendix B. This application also relates to U.S. Provisional Patent No. 62 / 338,994, entitled “REMOTE AUTHORIZATION TO PROCEED WITH AN ACTION,” filed on May 19, 2016, U.S. Provisional Patent No. 62 / 347,852, entitled “REMOTE AUTHORIZATION TO PROCEED WITH ANACTION,” filed on June 9, 2016, and U.S. Patent Application No. 15 / 269,801, entitled “USER INTERFACEFOR A DEVICE REQUESTING REMOTE AUTHORIZATION,” filed on September 19, 2016, portions of which are included as Appendix C, the contents of each of which are hereby incorporated by reference in their entirety. Technical Field

[0005] The present disclosure relates generally to computer user interfaces and, more particularly, to techniques for managing access to credentials used in operations requiring authorization. Background Art

[0006] The use of electronic devices for storing and accessing credentials has increased significantly in recent years. Typically, a user provides authorization to access stored credentials by entering a password at a keyboard of the device. Although the user entering the password expects that the input device (e.g., keyboard) and the software receiving the password will not misappropriate the password, the user cannot ensure that this will not occur. For example, pop-up windows of unethical websites can mimic legitimate websites to trick users into entering password information or other sensitive information that the user does not intend to share with the unethical website. Summary of the invention

[0007] However, some techniques for managing access to credentials used in operations using electronic devices are often cumbersome and inefficient. For example, some prior art techniques use complex and time-consuming user interfaces that may include multiple key presses or keystrokes. Prior art techniques may not be as secure as expected and often require more time than necessary, thereby wasting user time and device energy. This latter consideration is particularly important in battery-powered devices.

[0008] Therefore, the present technology and electronic device provide faster, safer and more efficient methods and interfaces for managing access to credentials used in operations requiring authorization. These methods and interfaces optionally supplement or replace other methods for managing access to certificates used in operations requiring authorization. Such methods and interfaces reduce the cognitive burden caused to the user and produce a more efficient man-machine interface. For battery-driven computing devices, such methods and interfaces save power and increase the time interval between battery charges. In addition, these methods and interfaces reduce the number of inputs required for authorizing the release of credentials used in operations requiring authorization at electronic devices (such as laptop computers). In addition, these methods and interfaces provide enhanced security for operations performed at electronic devices, where the operations involve the use of user credentials, such as personal data, account data and / or other private information.

[0009] According to some embodiments, a method is described for execution at an electronic device having a first display, a second display, one or more input devices, and a security element. The method includes: receiving a request for a credential for an operation requiring authorization; in response to receiving the request for the credential: displaying a parameter interface for the operation requiring authorization on the first display; while displaying the parameter interface, displaying a visual indication of one or more steps to be taken for the authorization operation on the second display; using one or more input devices to receive input corresponding to the visual indication of the one or more steps; and in response to receiving the input, according to determining that the input is consistent with the authorization criteria, causing the credential to be issued from the security element for use in the operation.

[0010] According to some embodiments, a non-transitory computer-readable storage medium is described. The non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device having a first display, a second display, one or more input devices, and a security element, the one or more programs including instructions for performing the following operations: receiving a request for a credential for an operation requiring authorization; in response to receiving the request for the credential: displaying a parameter interface for the operation requiring authorization on the first display; while displaying the parameter interface, displaying a visual indication of one or more steps to be taken for the authorization operation on the second display; using one or more input devices to receive input corresponding to the visual indication of the one or more steps; and in response to receiving the input, according to determining that the input is consistent with the authorization criteria, issuing the credential from the security element for use in the operation.

[0011] According to some embodiments, a transient computer-readable storage medium is described. The transient computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device having a first display, a second display, one or more input devices, and a security element, the one or more programs including instructions for performing the following operations: receiving a request for a credential for an operation requiring authorization; in response to receiving the request for the credential: displaying a parameter interface for the operation requiring authorization on the first display; while displaying the parameter interface, displaying a visual indication of one or more steps to be taken for the authorization operation on the second display; using one or more input devices to receive input corresponding to the visual indication of the one or more steps; and in response to receiving the input, based on determining that the input is consistent with the authorization criteria, causing the credential to be issued from the security element for use in the operation.

[0012] According to some embodiments, an electronic device is described. The electronic device includes: a first display; a second display; one or more input devices; a security element; one or more processors; and a memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for performing the following operations: receiving a request for a credential for an operation requiring authorization; in response to receiving the request for the credential: displaying a parameter interface for the operation requiring authorization on the first display; while displaying the parameter interface, displaying a visual indication of one or more steps to be taken for the authorization operation on the second display; using one or more input devices to receive input corresponding to the visual indication of the one or more steps; and in response to receiving the input, according to determining that the input is consistent with the authorization criteria, causing the credential to be issued from the security element for use in the operation.

[0013] According to some embodiments, an electronic device is described. The electronic device includes: a first display; a second display; one or more input devices; a security element; a device for the following operations: receiving a request for a credential for an operation requiring authorization; a device for the following operations: in response to receiving the request for the credential, displaying a parameter interface for the operation requiring authorization on the first display; while displaying the parameter interface, displaying a visual indication of one or more steps to be taken for the authorization operation on the second display; a device for the following operations: using one or more input devices to receive input corresponding to the visual indication of the one or more steps; and a device for the following operations: in response to receiving the input, based on determining that the input is consistent with the authorization criteria, causing the credential to be issued from the security element for use in the operation.

[0014] According to some embodiments, a method performed at an electronic device having an input device for authorizing access to a credential is described. The method includes: causing a user interface generated by the device to be displayed on a display; while causing the user interface generated by the device to be displayed on the display, receiving a request for the credential; and in response to receiving the request for the credential: causing a visual indication of one or more steps to be taken to enable the input device for user input to be displayed on the display based on determining that a first set of one or more criteria are satisfied, the first set of one or more criteria including an input disabling criterion that is satisfied when the input device is not enabled for user input.

[0015] According to some embodiments, a non-transitory computer-readable storage medium is described. The non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device having an input device for authorizing access to a credential, the one or more programs including instructions for performing the following operations: causing a user interface generated by the device to be displayed on a display; while causing the user interface generated by the device to be displayed on the display, receiving a request for the credential; and in response to receiving the request for the credential: causing a visual indication of one or more steps to be taken to enable the input device for user input to be displayed on the display based on determining that a first set of one or more criteria are satisfied, the first set of one or more criteria including an input disabling criterion that is satisfied when the input device is not enabled for user input.

[0016] According to some embodiments, a transient computer-readable storage medium is described. The transient computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device having an input device for authorizing access to a credential, the one or more programs including instructions for performing the following operations: causing a user interface generated by the device to be displayed on a display; while causing the user interface generated by the device to be displayed on the display, receiving a request for the credential; and in response to receiving the request for the credential: causing a visual indication of one or more steps to be taken to enable the input device for user input to be displayed on the display based on determining that a first set of one or more criteria are satisfied, the first set of one or more criteria including an input disabling criterion that is satisfied when the input device is not enabled for user input.

[0017] According to some embodiments, an electronic device is described. The electronic device includes: an input device for authorizing access to a credential; one or more processors; and a memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for performing the following operations: causing a user interface generated by the device to be displayed on a display; while causing the user interface generated by the device to be displayed on the display, receiving a request for the credential; and in response to receiving the request for the credential: causing a visual indication of one or more steps to be taken to enable the input device for user input to be displayed on the display based on determining that a first set of one or more criteria are satisfied, the first set of one or more criteria including an input disabling criterion that is satisfied when the input device is not enabled for user input.

[0018] According to some embodiments, an electronic device is described. The electronic device includes: an input device for authorizing access to a credential; means for causing a user interface generated by the device to be displayed on a display; means for causing a request for the credential to be received while causing the user interface generated by the device to be displayed on the display; and means for causing, in response to receiving the request for the credential, to cause a visual indication to be displayed on the display of one or more steps to be taken to enable the input device for user input based on determining that a first set of one or more criteria are satisfied, the first set of one or more criteria including an input disabling criterion that is satisfied when the input device is not enabled for user input.

[0019] According to some embodiments, a method performed at an electronic device with an integrated fingerprint sensor and a security element is described. The method includes: when a first account actively logs into the electronic device, using a fingerprint sensor to detect a corresponding fingerprint; based on determining that a first set of one or more criteria are satisfied, converting the electronic device so that the first account is no longer actively logged into the electronic device and the second account is actively logged into the electronic device; wherein the first set of one or more criteria include: a first mode standard satisfied when the electronic device is in a first mode, and a different account fingerprint standard satisfied when the corresponding fingerprint corresponds to a second account of the electronic device; based on determining that a second set of one or more criteria are satisfied, issuing a credential from the security element for use in an operation; and wherein the second set of one or more criteria include: a second mode standard satisfied when the electronic device is in a second mode, and a current account fingerprint standard satisfied when the corresponding fingerprint corresponds to a first account of the electronic device.

[0020] According to some embodiments, a non-transitory computer-readable storage medium is described. The non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device having an integrated fingerprint sensor and a security element, the one or more programs including instructions for performing the following operations: when a first account actively logs into the electronic device: using a fingerprint sensor to detect a corresponding fingerprint; based on determining that a first set of one or more criteria are satisfied, converting the electronic device so that the first account is no longer actively logged into the electronic device and a second account is actively logged into the electronic device; wherein the first set of one or more criteria include: a first mode standard satisfied when the electronic device is in a first mode, and a different account fingerprint standard satisfied when the corresponding fingerprint corresponds to a second account of the electronic device; based on determining that a second set of one or more criteria are satisfied, issuing a credential from the security element for use in an operation; and wherein the second set of one or more criteria include: a second mode standard satisfied when the electronic device is in a second mode, and a current account fingerprint standard satisfied when the corresponding fingerprint corresponds to a first account of the electronic device.

[0021] According to some embodiments, a transient computer-readable storage medium is described. The transient computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device having an integrated fingerprint sensor and a security element, the one or more programs including instructions for performing the following operations: when a first account actively logs into the electronic device: using a fingerprint sensor to detect a corresponding fingerprint; based on determining that a first set of one or more criteria are satisfied, converting the electronic device so that the first account is no longer actively logged into the electronic device and a second account is actively logged into the electronic device; wherein the first set of one or more criteria include: a first mode standard satisfied when the electronic device is in a first mode, and a different account fingerprint standard satisfied when the corresponding fingerprint corresponds to a second account of the electronic device; based on determining that a second set of one or more criteria are satisfied, issuing a credential from the security element for use in an operation; and wherein the second set of one or more criteria include: a second mode standard satisfied when the electronic device is in a second mode, and a current account fingerprint standard satisfied when the corresponding fingerprint corresponds to a first account of the electronic device.

[0022] According to some embodiments, an electronic device is described. The electronic device includes: an integrated fingerprint sensor; a security element; one or more processors; and a memory storing one or more programs configured to be executed by one or more processors, the one or more programs including instructions for performing the following operations: when a first account actively logs into the electronic device: using a fingerprint sensor to detect a corresponding fingerprint; based on determining that a first set of one or more criteria are satisfied, converting the electronic device so that the first account is no longer actively logged into the electronic device and a second account is actively logged into the electronic device; wherein the first set of one or more criteria include: a first mode standard satisfied when the electronic device is in a first mode, and a different account fingerprint standard satisfied when the corresponding fingerprint corresponds to a second account of the electronic device; based on determining that a second set of one or more criteria are satisfied, issuing a credential from the security element for use in an operation; and wherein the second set of one or more criteria include: a second mode standard satisfied when the electronic device is in a second mode, and a current account fingerprint standard satisfied when the corresponding fingerprint corresponds to a first account of the electronic device.

[0023] According to some embodiments, an electronic device is described. The electronic device includes: an integrated fingerprint sensor; a security element; a device for the following operations: when a first account actively logs into the electronic device, using the fingerprint sensor to detect a corresponding fingerprint; a device for the following operations: based on determining that a first set of one or more criteria are satisfied, converting the electronic device so that the first account is no longer actively logged into the electronic device and a second account is actively logged into the electronic device; wherein the first set of one or more criteria include: a first mode standard satisfied when the electronic device is in a first mode, and a different account fingerprint standard satisfied when the corresponding fingerprint corresponds to a second account of the electronic device; a device for the following operations: based on determining that a second set of one or more criteria are satisfied, issuing a credential from the security element for use in an operation; and wherein the second set of one or more criteria include: a second mode standard satisfied when the electronic device is in a second mode, and a current account fingerprint standard satisfied when the corresponding fingerprint corresponds to a first account of the electronic device.

[0024] According to some embodiments, an electronic device is described. The electronic device includes: a first display unit; a second display unit; one or more input device units; a security element unit; and a processing unit, the processing unit is coupled to the first display unit, the second display unit, the one or more input device units and the security element unit, and the processing unit is configured to: receive a request for a credential for an operation requiring authorization; in response to receiving the request for the credential: enable display of a parameter interface for an operation requiring authorization on the first display unit; while displaying the parameter interface, enable display of a visual indication of one or more steps to be taken for the authorization operation on the second display unit; use one or more input device units to receive input corresponding to the visual indication of the one or more steps; and in response to receiving the input, based on determining that the input is consistent with the authorization criteria, release the credential from the security element unit for use in the operation.

[0025] According to some embodiments, an electronic device is described. The electronic device includes: an input device unit for authorizing access to a credential; and a processing unit coupled to the input device unit, the processing unit being configured to: cause a user interface generated by the device to be displayed on a display unit; while causing the user interface generated by the device to be displayed on the display unit, receive a request for the credential; and in response to receiving the request for the credential: cause a visual indication of one or more steps to be taken to enable the input device unit for user input to be displayed on the display unit based on determining that a first set of one or more criteria are satisfied, the first set of one or more criteria including an input disabling criterion that is satisfied when the input device unit is not enabled for user input.

[0026] According to some embodiments, an electronic device is described. The electronic device includes: an integrated fingerprint sensor unit; a security element unit; and a processing unit coupled to the integrated fingerprint sensor unit and the security element unit, the processing unit being configured to: when a first account actively logs into the electronic device: use the fingerprint sensor unit to detect a corresponding fingerprint; based on determining that a first set of one or more criteria are satisfied, convert the electronic device so that the first account is no longer actively logged into the electronic device and a second account is actively logged into the electronic device; wherein the first set of one or more criteria include: a first mode standard satisfied when the electronic device is in a first mode, and a different account fingerprint standard satisfied when the corresponding fingerprint corresponds to a second account of the electronic device; based on determining that a second set of one or more criteria are satisfied, a credential is issued from the security element unit for use in an operation; and wherein the second set of one or more criteria include: a second mode standard satisfied when the electronic device is in a second mode, and a current account fingerprint standard satisfied when the corresponding fingerprint corresponds to a first account of the electronic device.

[0027] Executable instructions for performing these functions are optionally included in a non-transitory computer-readable storage medium or other computer program product configured for execution by one or more processors. Executable instructions for performing these functions are optionally included in a transient computer-readable storage medium or other computer program product configured for execution by one or more processors.

[0028] Thus, a faster, more efficient, and more secure method and interface is provided for devices for managing access to credentials used in operation, thereby improving the effectiveness, efficiency, and user satisfaction of such devices. Such methods and interfaces may supplement or replace other methods for managing access to credentials. BRIEF DESCRIPTION OF THE DRAWINGS

[0029] For a better understanding of the various described embodiments, reference should be made to the following detailed description taken in conjunction with the following drawings, wherein like reference numerals designate corresponding parts throughout the several views.

[0030] Figure 1A is a block diagram showing a portable multifunction device with a touch-sensitive display according to some embodiments.

[0031] Figure 1B is a block diagram illustrating example components for event processing according to some embodiments.

[0032] Figure 2 shows a portable multifunction device with a touch screen according to some embodiments.

[0033] Figure 3 is a block diagram of an exemplary multifunction device with a display and a touch-sensitive surface according to some embodiments.

[0034] Figure 4A shows an exemplary user interface for a menu of applications on a portable multifunction device according to some embodiments.

[0035] Figure 4B shows an exemplary user interface for a multifunction device with a touch-sensitive surface that is separate from the display according to some embodiments.

[0036] Figure 5A illustrates a personal electronic device according to some embodiments.

[0037] Figure 5B is a block diagram showing a personal electronic device according to some embodiments.

[0038] Figures 5C-5D illustrate exemplary components of a personal electronic device with a touch-sensitive display and an intensity sensor according to some embodiments.

[0039] Figures 5E-5H illustrate exemplary components and user interfaces of a personal electronic device according to some embodiments.

[0040] Figures 5I to 5N illustrate exemplary user interfaces for updating dynamic input and output devices according to some embodiments.

[0041] FIG. 6 illustrates example devices connected via one or more communication channels according to some embodiments.

[0042] Figures 7A to 7D-10 illustrate exemplary devices and user interfaces for using an electronic device to authorize the issuance of credentials for use in operations requiring authorization according to some embodiments.

[0043] Figures 8A-8B are flowcharts according to some embodiments, which illustrate a method for using an electronic device to authorize the issuance of credentials used in operations requiring authorization.

[0044] Figures 9A-1 to 9E-4 illustrate exemplary devices and user interfaces for using an electronic device to display one or more steps to be taken to enable an input device for user input according to some embodiments.

[0045] Figures 10A to 10D are flowcharts according to some embodiments, which illustrate a method for using an electronic device to display one or more steps to be taken to enable an input device for user input.

[0046] Figures 11A through 11M-4 illustrate exemplary devices and user interfaces for disambiguating between commands for changing an account actively logged into a device and commands for causing credentials to be released from a secure element, according to some embodiments.

[0047] Figures 12A-12B are flowcharts according to some embodiments, which illustrate a method for disambiguating between commands for changing an account actively logged into a device and commands for causing credentials to be released from a secure element.

[0048] 13-15 illustrate functional block diagrams according to some embodiments. DETAILED DESCRIPTION

[0049] The following description sets forth exemplary methods, parameters, etc. However, it should be appreciated that such description is not intended to limit the scope of the present disclosure, but is provided as a description of exemplary embodiments.

[0050] An electronic device that provides an effective method and interface for managing access to credentials used in operations is needed. For example, an effective method and interface for securely accessing credentials used in operations that require authorization is needed. As another example, an effective method and interface for securely authenticating and enabling the release of credentials for operations that require authorization is needed. As another example, when an input device for detecting authentication is unavailable, an effective method and interface for communicating with an external device to securely authorize the release of credentials is needed. As another example, an effective method and interface for securely converting an active login account to a different account is needed. Such technology can reduce the cognitive burden of users who need to access credentials used in operations that require authorization, thereby improving productivity. In addition, such technology can also reduce processor power usage and battery power that would otherwise be wasted on redundant user input.

[0051] In the following, Figures 1A to 1B, Figure 2, Figure 3, Figures 4A to 4B, and Figures 5A to 5M provide a description of an exemplary device for performing a technique for managing access to credentials used in an operation. Figure 6 shows an exemplary device connected via one or more communication channels according to some embodiments. Figures 7A to 7D-10 show an exemplary device and user interface for authorizing the release of credentials used in an operation requiring authorization. Figures 8A to 8B are flowcharts showing a method for authorizing the release of credentials used in an operation requiring authorization. The user interface in Figures 7A to 7D-10 is used to illustrate the process described below, including the process in Figures 8A to 8B. Figures 9A-1 to 9E-4 show an exemplary device and user interface for enabling the display of one or more steps to be taken by an input device for user input. Figures 10A to 10D are flowcharts according to some embodiments, which show a method for enabling the display of one or more steps to be taken by an input device for user input. The user interface in Figures 9A-1 to 9E-4 is used to illustrate the process described below, including the process in Figures 10A to 10D. Figures 11A to 11M-4 illustrate exemplary user interfaces for disambiguating between a command for changing an account actively logged into a device and a command for causing a credential to be issued from a secure element. Figures 12A to 12B are flow diagrams illustrating a method for disambiguating between a command for changing an account actively logged into a device and a command for causing a credential to be issued from a secure element. The user interfaces in Figures 11A to 11M-4 are used to illustrate the processes described below, including the processes in Figures 12A to 12B.

[0052] Although the following description uses the terms "first", "second", etc. to describe various elements, these elements should not be limited by the terms. These terms are only used to distinguish one element from another element. For example, a first touch can be named a second touch and similarly a second touch can be named a first touch without departing from the scope of the various described embodiments. Both the first touch and the second touch are touches, but they are not the same touch.

[0053] The terms used in the description of various described embodiments herein are only for the purpose of describing specific embodiments, and are not intended to be limited. As used in the description of various described embodiments and in the appended claims, the singular forms "one" and "the" are intended to also include plural forms, unless the context clearly indicates otherwise. It will also be understood that the term "and / or" used herein refers to and encompasses any and all possible combinations of one or more items in the associated listed items. It will also be understood that the term "includes", "including", "comprises" and / or "comprising" when used in this specification specifies the presence of stated features, integers, steps, operations, elements and / or parts, but does not exclude the presence or addition of one or more other features, integers, steps, operations, elements, parts and / or their grouping.

[0054] The term "if" is optionally interpreted to mean "when," "upon," or "in response to determining," or "in response to detecting," depending on the context. Similarly, the phrases "if it is determined that ..." or "if [a stated condition or event] is detected" are optionally interpreted to mean "upon determining that ..." or "in response to determining that ..." or "upon detecting [a stated condition or event]," or "in response to detecting [a stated condition or event]," depending on the context.

[0055] Embodiments of electronic devices, user interfaces for such devices, and associated processes for using such devices are described herein. In some embodiments, the device is a portable communication device, such as a mobile phone, that also includes other functions, such as a PDA and / or a music player function. Exemplary embodiments of portable multifunction devices include, but are not limited to, the Apple iPod from Apple Inc. (Cupertino, California). Devices, iPod Equipment, and Device. Other portable electronic devices, such as laptops or tablet computers with touch-sensitive surfaces (e.g., touch screen displays and / or touch pads) are optionally used. It should also be understood that in some embodiments, the device is not a portable communication device, but a desktop computer with a touch-sensitive surface (e.g., touch screen displays and / or touch pads).

[0056] In the following discussion, an electronic device including a display and a touch-sensitive surface is described. However, it should be understood that the electronic device optionally includes one or more other physical user interface devices, such as a physical keyboard, mouse and / or joystick.

[0057] The device typically supports a variety of applications, such as one or more of the following: a drawing application, a presentation application, a word processing application, a website creation application, a disk editing application, a spreadsheet application, a gaming application, a telephony application, a video conferencing application, an email application, an instant messaging application, a fitness support application, a photo management application, a digital camera application, a digital video camera application, a web browsing application, a digital music player application, and / or a digital video player application.

[0058] Various applications executed on the 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 corresponding information displayed on the device are optionally adjusted and / or varied for different applications, and / or adjusted and / or varied within the respective applications. In this way, the common physical architecture of the device (such as a touch-sensitive surface) optionally supports a variety of applications with a user interface that is intuitive and clear to the user.

[0059] Attention is now directed to embodiments of portable devices with touch-sensitive displays. FIG. 1A is a block diagram illustrating a portable multifunction device 100 with a touch-sensitive display system 112 according to some embodiments. The touch-sensitive display 112 is sometimes referred to as a "touch screen" for convenience, and is sometimes referred to as or referred to as a "touch-sensitive display system." The device 100 includes a memory 102 (which optionally includes 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 control devices 116, and an external port 124. The device 100 optionally includes one or more optical sensors 164. The device 100 optionally includes one or more contact force sensors 165 for detecting the intensity of contact on the device 100 (e.g., a touch-sensitive surface, such as the touch-sensitive display system 112 of the 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 touch-sensitive display system 112 of device 100 or touch pad 355 of device 300). These components optionally communicate via one or more communication buses or signal lines 103.

[0060] As used in this specification and claims, the term "intensity" of a contact on a touch-sensitive surface refers to the force or pressure (force per unit area) of a contact (e.g., a finger contact) on the touch-sensitive surface, or to a surrogate (surrogate) of the force or pressure of a contact on the touch-sensitive surface. The intensity of a contact has a range of values ​​that includes at least four different values ​​and more typically includes hundreds of different values ​​(e.g., at least 256). The intensity of a contact is optionally determined (or measured) using various methods and various sensors or combinations of sensors. For example, one or more force sensors below or adjacent to the touch-sensitive surface are optionally used to measure the force at different points on the touch-sensitive surface. In some implementations, force measurements from multiple force sensors are combined (e.g., weighted averaged) to determine an estimated contact force. 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 of the contact area detected on the touch-sensitive surface and / or its change, the capacitance of the touch-sensitive surface near the contact and / or its change, and / or the resistance of the touch-sensitive surface near the contact and / or its change are optionally used as a substitute for the force or pressure of the contact on the touch-sensitive surface. In some embodiments, the substitute measurement of the contact force or pressure is used directly to determine whether the intensity threshold has been exceeded (e.g., the intensity threshold is described in units corresponding to the substitute measurement). In some embodiments, the substitute measurement of the contact force or pressure is converted into an estimated force or pressure, and the estimated force or pressure is used to determine whether the intensity threshold has been exceeded (e.g., the intensity threshold is a pressure threshold measured in units of pressure). Using the intensity of the contact as an attribute of the user input allows the user to access additional device functions that would otherwise be inaccessible to the user on a smaller device with limited real estate, which is used to display an enable indication (e.g., on a touch-sensitive display) and / or receive user input (e.g., via a touch-sensitive display, a touch-sensitive surface, or a physical control / mechanical control, such as a knob or button).

[0061] As used in this specification and the claims, the term "haptic output" refers to a physical displacement of a device relative to a previous position of the device detected by a user using the user's sense of touch, a physical displacement of a component of the device (e.g., a touch-sensitive surface) relative to another component of the device (e.g., the housing), or a displacement of a component relative to the center of mass of the device. For example, in the case of contact between the device or a component of the device and a surface that is sensitive to touch by the user (e.g., a finger, palm, or other part of the user's hand), a haptic output generated by the physical displacement will be interpreted by the user as a sense of touch that corresponds to a perceived change in a physical characteristic of the device or a component of the device. For example, movement of a touch-sensitive surface (e.g., a touch-sensitive display or a touchpad) is optionally interpreted by the user as a "press click" or "release click" of a physical actuation button. In some cases, the user will feel a sense of touch, such as a "press click" or "release click," even when the physical actuation button associated with the touch-sensitive surface that is physically depressed (e.g., displaced) by the user's movement does not move. As another example, movement of a touch-sensitive surface will optionally be interpreted or sensed by the user as "roughness" of the touch-sensitive surface even when there is no change in the smoothness of the touch-sensitive surface. Although such interpretations of touch by the user will be limited by the user's individual sensory perception, many sensory perceptions of touch are common to most users. Thus, when a haptic output is described as corresponding to a particular sensory perception of the user (e.g., "press click," "release click," "roughness"), unless otherwise stated, the generated haptic output corresponds to a physical displacement of the device or a component thereof that would generate the stated sensory perception of a typical (or average) user.

[0062] It should be understood that device 100 is merely one example of a portable multifunctional device, and device 100 optionally has more or fewer components than those shown, optionally combines two or more components, or optionally has a different configuration or arrangement of these components. The various components shown in FIG. 1A are implemented in hardware, software, or a combination of hardware and software, including one or more signal processing and / or application specific integrated circuits.

[0063] Memory 102 optionally includes high-speed random access memory and also optionally includes non-volatile memory, such as one or more disk storage devices, flash memory devices, or other non-volatile solid state memory devices. Memory controller 122 optionally controls access to memory 102 by other components of device 100.

[0064] The peripheral device interface 118 can be used to couple the input peripheral devices and output peripheral devices of the device to the CPU 120 and the memory 102. The one or more processors 120 run or execute various software programs and / or instruction sets stored in the memory 102 to perform various functions of the device 100 and process data. In some embodiments, the peripheral device interface 118, the CPU 120, and the memory controller 122 are optionally implemented on a single chip such as the chip 104. In some other embodiments, they are optionally implemented on separate chips.

[0065] RF (radio frequency) circuit 108 receives and sends RF signals, also referred to as electromagnetic signals. RF circuit 108 converts electrical signals into / converts electromagnetic signals into electrical signals, and communicates with communication networks and other communication devices via electromagnetic signals. RF circuit 108 optionally includes well-known circuits for performing these functions, including but not limited to antenna systems, RF transceivers, one or more amplifiers, tuners, one or more oscillators, digital signal processors, codec chipsets, user identity modules (SIM) cards, memory, and the like. RF circuit 108 optionally communicates with networks and other devices through wireless communications, such as the Internet (also referred to as the World Wide Web (WWW)), intranets, and / or wireless networks (such as cellular telephone networks, wireless local area networks (LANs), and / or metropolitan area networks (MANs)). RF circuit 108 optionally includes well-known circuits for detecting near field communication (NFC) fields, such as by detecting through a short-range communication radio component. Wireless communication optionally uses any of a variety of communication standards, protocols and technologies, including, but not limited to, 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), Near Field Communication (NFC), Wideband Code Division Multiple Access (W-CDMA), Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Bluetooth, Bluetooth Low Energy (BTLE), Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE802.11n and / or IEEE 802.11ac), Voice over Internet Protocol (VoIP), Wi-MAX, email protocols (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 Utilizing Extensions (SIMPLE), Instant Messaging and Presence Service (IMPS)), and / or Short Message Service (SMS), or any other suitable communications protocol including communications protocols that have not been developed as of the filing date of this document.

[0066] The audio circuit 110, the speaker 111, and the microphone 113 provide an audio interface between the user and the device 100. The audio circuit 110 receives audio data from the peripheral device interface 118, converts the audio data into electrical signals, and transmits the electrical signals to the speaker 111. The speaker 111 converts the electrical signals into sound waves audible to humans. The audio circuit 110 also receives electrical signals converted from sound waves by the microphone 113. The audio circuit 110 converts the electrical signals into audio data, and transmits the audio data to the peripheral device interface 118 for processing. The audio data is optionally retrieved from and / or transmitted to the memory 102 and / or the RF circuit 108 by the peripheral device interface 118. In some embodiments, the audio circuit 110 also includes a headset jack (e.g., 212 in FIG. 2). The headset jack provides an interface between audio circuitry 110 and a removable audio input / output peripheral device, such as an output-only headset or a headset having both output (e.g., single or dual ear headphones) and input (e.g., a microphone).

[0067] The I / O subsystem 106 couples input / output peripherals on the device 100, such as the touch screen 112 and other input control devices 116, to a peripherals interface 118. The I / O subsystem 106 optionally includes a display controller 156, an optical sensor controller 158, an intensity sensor controller 159, a tactile feedback controller 161, and one or more input controllers 160 for other input or control devices. The one or more input controllers 160 receive / send electrical signals from / to other input control devices 116. Other input control devices 116 optionally include physical buttons (e.g., push buttons, rocker buttons, etc.), dials, slide switches, joysticks, click wheels, etc. In some alternative embodiments, the input controllers 160 are optionally coupled to any (or none) of the following: a keyboard, an infrared port, a USB port, and a pointing device such as a mouse. The one or more buttons (eg, 208 in FIG. 2 ) optionally include an up / down button for volume control of the speaker 111 and / or microphone 113. The one or more buttons optionally include a push button (eg, 206 in FIG. 2 ).

[0068] A quick press of the push button optionally disengages the lock of the touch screen 112 or optionally begins the process of unlocking the device using gestures on the touch screen, as described in U.S. Patent Application 11 / 322,549, filed on December 23, 2005, entitled "Unlocking a Device by Performing Gestures on an Unlock Image" (i.e., U.S. Patent No. 7,657,849), which is hereby incorporated by reference in its entirety. A long press of the push button (e.g., 206) optionally turns the device 100 on or off. The functions of one or more buttons are optionally user-customizable. The touch screen 112 is used to implement virtual buttons or soft buttons and one or more soft keyboards.

[0069] The touch-sensitive display 112 provides an input interface and an output interface between the device and the user. The display controller 156 receives electrical signals from the touch screen 112 and / or sends electrical signals to the touch screen 112. The touch screen 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 optionally corresponds to user interface objects.

[0070] The touch screen 112 has a touch-sensitive surface, sensor, or sensor group that accepts input from a user based on tactile and / or haptic contact. The touch screen 112 and display controller 156 (together with any associated modules and / or instruction sets in memory 102) detect contact (and any movement or interruption of the contact) on the touch screen 112 and convert the detected contact into interaction with a user interface object (e.g., one or more soft keys, icons, web pages, or images) displayed on the touch screen 112. In an exemplary embodiment, the point of contact between the touch screen 112 and the user corresponds to the user's finger.

[0071] The touch screen 112 optionally uses LCD (liquid crystal display) technology, LPD (light emitting polymer display) technology, or LED (light emitting diode) technology, although other display technologies are used in other embodiments. The touch screen 112 and display controller 156 optionally use any of a variety of touch sensing technologies now known or later developed, including but not limited to capacitive, resistive, infrared, and surface acoustic wave technologies, as well as other proximity sensor arrays or other elements for determining one or more points of contact with the touch screen 112 to detect contact and any movement or interruption thereof. In an exemplary embodiment, projected mutual capacitance sensing technology is used, such as in the Apple ® from Apple Inc. (Cupertino, California). and iPod The technology used in.

[0072] The touch-sensitive display in some embodiments of the touch screen 112 is optionally similar to the multi-touch-sensitive trackpad described in the following U.S. Patents: 6,323,846 (Westerman et al.), 6,570,557 (Westerman et al.), and / or 6,677,932 (Westerman et al.), and / or U.S. Patent Publication 2002 / 0015024A1, each of which is hereby incorporated by reference in its entirety. However, the touch screen 112 displays visual output from the device 100, while the touch-sensitive touchpad does not provide visual output.

[0073] In some embodiments, the touch-sensitive display of the touch screen 112 is as described in the following patent applications: (1) U.S. patent application 11 / 381,313, entitled “Multipoint Touch Surface Controller,” filed on May 2, 2006; (2) U.S. patent application No. 10 / 840,862, entitled “Multipoint Touchscreen,” filed on May 6, 2004; (3) U.S. patent application No. 10 / 903,964, entitled “Gestures For Touch Sensitive Input Devices,” filed on July 30, 2004; (4) U.S. patent application 11 / 048,264, entitled “Gestures For Touch Sensitive Input Devices,” filed on January 31, 2005; (5) U.S. patent application 11 / 086, entitled “Mode-Based Graphical User Interfaces For Touch Sensitive and (9) U.S. patent application No. 11 / 367,749, filed on March 3, 2006, entitled “Multi-Functional Hand-Held Device.” All of these applications are hereby incorporated by reference in their entirety.

[0074] The touch screen 112 optionally has a video resolution of more than 100 dpi. In some embodiments, the touch screen has a video resolution of about 160 dpi. The user optionally uses any suitable object or attachment such as a stylus, finger, etc. to contact the touch screen 112. In some embodiments, the user interface is designed to work primarily through finger-based contacts and gestures, which may not be as precise as stylus-based input due to the larger contact area of ​​the finger on the touch screen. In some embodiments, the device converts rough finger-based input into precise pointer / cursor positions or commands for performing the actions desired by the user.

[0075] In some embodiments, in addition to the touch screen, 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 touch screen, does not display visual output. The touchpad is optionally a touch-sensitive surface that is separate from the touch screen 112 or an extension of the touch-sensitive surface formed by the touch screen.

[0076] The device 100 also includes a power system 162 for powering the various components. The power system 162 optionally includes a power management system, one or more power sources (e.g., batteries, alternating current (AC)), a recharging system, a power fault 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 in a portable device.

[0077] The device 100 optionally also includes one or more optical sensors 164. FIG. 1A shows an optical sensor coupled to an optical sensor controller 158 in the I / O subsystem 106. The optical sensor 164 optionally includes a charge coupled device (CCD) or a complementary metal oxide semiconductor (CMOS) phototransistor. The optical sensor 164 receives light projected through one or more lenses from the environment and converts the light into data representing an image. In conjunction with the imaging module 143 (also called a camera module), the optical sensor 164 optionally captures a static image or video. In some embodiments, the optical sensor is located on the rear of the device 100, opposite to the touch screen display 112 on the front of the device, so that the touch screen display can be used as a viewfinder for static image and / or video image acquisition. In some embodiments, the optical sensor is located on the front of the device so that the user's image is optionally obtained for video conferencing while the user views other video conference participants on the touch screen display. In some embodiments, the position of optical sensor 164 can be changed by a user (e.g., by rotating the lens and sensor in the device housing) so that a single optical sensor 164 is used with the touch screen display for both video conferencing and still image and / or video image capture.

[0078] The device 100 optionally also includes one or more contact force sensors 165. Figure 1A shows a contact force sensor coupled to a force sensor controller 159 in the I / O subsystem 106. The contact force sensor 165 optionally includes one or more piezoresistive strain gauges, capacitive force sensors, electrical force sensors, piezoelectric force sensors, optical force sensors, capacitive touch-sensitive surfaces, or other force sensors (e.g., sensors for measuring the force (or pressure) of contact on a touch-sensitive surface). The contact force sensor 165 receives contact force information (e.g., pressure information or a substitute for pressure information) from the environment. In some embodiments, at least one contact force sensor is arranged in juxtaposition or proximity to a touch-sensitive surface (e.g., touch-sensitive display system 112). In some embodiments, at least one contact force sensor is located on the rear of the device 100, opposite to the touch screen display 112 located on the front of the device 100.

[0079] Device 100 optionally also includes one or more proximity sensors 166. FIG. 1A shows proximity sensor 166 coupled to peripherals interface 118. Alternatively, proximity sensor 166 is optionally coupled to input controller 160 in I / O subsystem 106. The proximity sensor 166 is optionally implemented as described in the following U.S. patent applications: No. 11 / 241,839, entitled "Proximity Detector In Handheld Device"; No. 11 / 240,788, entitled "Proximity Detector In Handheld Device"; No. 11 / 620,702, entitled "Using Ambient Light Sensor To Augment Proximity Sensor Output"; No. 11 / 586,862, entitled "Automated Response To And Sensing Of User Activity In Portable Devices"; and No. 11 / 638,251, entitled "Methods And Systems For Automatic Configuration Of Peripherals", which are hereby incorporated by reference in their entirety. In some embodiments, when the multifunction device is placed near the user's ear (e.g., when the user is making a phone call), the proximity sensor is turned off and the touch screen 112 is disabled.

[0080] Device 100 optionally also includes one or more tactile output generators 167. FIG. 1A shows a tactile output generator coupled to a tactile feedback controller 161 in I / O subsystem 106. Tactile output generator 167 optionally includes one or more electroacoustic devices, such as a speaker or other audio component; and / or an electromechanical device that converts energy into linear motion, such as a motor, solenoid, electroactive polymer, piezoelectric actuator, electrostatic actuator, or other tactile output generating component (e.g., a component that converts an electrical signal into a tactile output on the device). Contact intensity sensor 165 receives tactile feedback generation instructions from tactile feedback module 133 and generates tactile output on device 100 that can be felt by a user of device 100. In some embodiments, at least one tactile output generator is juxtaposed with or adjacent to a touch-sensitive surface (e.g., touch-sensitive display system 112), and optionally generates tactile output by moving the touch-sensitive surface vertically (e.g., inward / outward toward the surface of device 100) or laterally (e.g., back and forward in the same plane as the surface of device 100). In some embodiments, at least one tactile output generator sensor is located on the back of device 100, opposite to touch screen display 112 located on the front of device 100.

[0081] The device 100 optionally also includes one or more accelerometers 168. FIG. 1A shows an accelerometer 168 coupled to the peripheral device interface 118. Alternatively, the accelerometer 168 is optionally coupled to the input controller 160 in the I / O subsystem 106. The accelerometer 168 is optionally implemented as described in the following U.S. Patent Publication: U.S. Patent Publication 20050190059, entitled "Acceleration-based Theft Detection System for Portable Electronic Devices" and U.S. Patent Publication 20060017692, entitled "Methods And Apparatuses For Operating A Portable Device Based On An Accelerometer", both of which are incorporated herein by reference in their entirety. In some embodiments, information is displayed in a portrait view or a landscape view on a touch screen display based on analysis of data received from one or more accelerometers. Device 100 optionally includes a magnetometer (not shown) and a GPS (or GLONASS or other global navigation system) receiver (not shown) in addition to accelerometer 168 for obtaining information about the position and orientation (eg, portrait or landscape) of device 100 .

[0082] In some embodiments, the software components stored in the memory 102 include an operating system 126, a communication module (or instruction set) 128, a contact / motion module (or instruction set) 130, 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. In addition, in some embodiments, the memory 102 (Figure 1A) or 370 (Figure 3) stores a device / global internal state 157, as shown in Figures 1A and 3. The device / global internal state 157 includes one or more of the following: an active application state, which indicates which applications (if any) are currently active; a display state, which indicates what applications, views, or other information occupy various areas of the touch screen display 112; a sensor state, including information obtained from various sensors and input control devices 116 of the device; and position information about the position and / or posture of the device.

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

[0084] The communication module 128 facilitates communication with other devices through one or more external ports 124 and also includes various software components for processing data received by the RF circuit 108 and / or the external port 124. The external port 124 (e.g., Universal Serial Bus (USB), FireWire, etc.) is suitable for coupling directly to other devices or indirectly via a network (e.g., the Internet, wireless LAN, etc.). In some embodiments, the external port is connected to (trademark of Apple Inc.) devices.

[0085] The contact / motion module 130 optionally detects contact with the touch screen 112 (in conjunction with the display controller 156) and 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 press event), determining the contact strength (e.g., the force or pressure of the contact, or a substitute for the force or pressure of the contact), determining whether there is movement of the contact and tracking the movement on the touch-sensitive surface (e.g., detecting one or more finger drag events), and determining whether the contact has stopped (e.g., detecting a finger lift event or contact disconnection). The contact / motion module 130 receives contact data from the touch-sensitive surface. Determining the movement of the contact point optionally includes determining the rate (magnitude), velocity (magnitude and direction), and / or acceleration (change in magnitude and / or direction) of the contact point, the movement of the contact point being represented by a series of contact data. These operations are optionally applied to a single point of contact (e.g., a single finger contact) or multiple points of simultaneous contact (e.g., "multi-touch" / multiple finger contacts). In some embodiments, the contact / motion module 130 and display controller 156 detect contact on the touch pad.

[0086] In some embodiments, the contact / motion module 130 uses a set of one or more intensity thresholds to determine whether an operation has been performed by a user (e.g., to determine whether a user has "clicked" an icon). In some embodiments, at least a subset of the intensity thresholds are determined based on software parameters (e.g., the intensity thresholds are not determined by the activation thresholds of specific physical actuators and can be adjusted without changing the physical hardware of the device 100). For example, without changing the touchpad or touchscreen display hardware, the mouse "click" threshold of a touchpad or touchscreen can be set to any one of a large range of predefined thresholds. In addition, in some specific implementations, a software setting is provided to the user of the device for adjusting one or more intensity thresholds in a set of intensity thresholds (e.g., by adjusting individual intensity thresholds and / or by utilizing a system-level click on an "intensity" parameter to adjust multiple intensity thresholds at once).

[0087] The contact / motion module 130 optionally detects gesture input by the user. Different gestures on the touch-sensitive surface have different contact patterns (e.g., different motions, timings, and / or intensities of the detected contacts). Therefore, gestures are optionally detected by detecting specific contact patterns. For example, detecting a finger tap gesture includes detecting a finger press event, and then detecting a finger lift (lift-off) event at the same location (or substantially the same location) as the finger press event (e.g., at the location of an icon). As another example, detecting a finger swipe gesture on the touch-sensitive surface includes detecting a finger press event, then detecting one or more finger drag events, and then detecting a finger lift (lift-off) event.

[0088] The graphics module 132 includes various known software components for rendering and displaying graphics on the touch screen 112 or other display, including components for changing the visual impact (e.g., brightness, transparency, saturation, contrast, or other visual characteristics) of the displayed graphics. As used herein, the term "graphics" includes any object that can be displayed to a user, including, but not limited to, text, web pages, icons (such as user interface objects including soft keys), digital images, videos, animations, etc.

[0089] In some embodiments, the graphics module 132 stores data representing graphics to be used. Each graphic is optionally assigned a corresponding code. The graphics module 132 receives one or more codes for specifying the graphics to be displayed from an application program, etc., and also receives coordinate data and other graphic attribute data together if necessary, and then generates screen image data to be output to the display controller 156.

[0090] Haptic feedback module 133 includes various software components for generating instructions used by tactile output generator 167 to produce tactile output at one or more locations on device 100 in response to user interaction with device 100 .

[0091] Text input module 134, which is optionally a component of graphics module 132, provides a soft keyboard for entering text in various applications (e.g., contacts 137, email 140, IM 141, browser 147, and any other application requiring text input).

[0092] The GPS module 135 determines the location of the device and provides this information for use in various applications (e.g., to the phone 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 the Weather widget, the Local Pages widget, and the Maps / Navigation widget).

[0093] The application 136 optionally includes the following modules (or instruction sets) or a subset or superset thereof:

[0094] Contacts module 137 (sometimes called address book or contact list);

[0095] Telephone module 138;

[0096] Video conferencing module 139;

[0097] Email client module 140;

[0098] Instant messaging (IM) module 141;

[0099] Fitness support module 142;

[0100] A camera module 143 for still images and / or video images;

[0101] Image management module 144;

[0102] Video player module;

[0103] Music player module;

[0104] Browser module 147;

[0105] Calendar module 148;

[0106] A widget module 149, which optionally includes one or more of the following: a weather widget 149-1, a stock widget 149-2, a calculator widget 149-3, an alarm widget 149-4, a dictionary widget 149-5, and other widgets acquired by the user, and a user-created widget 149-6;

[0107] A widget creator module 150 for forming a user-created widget 149-6;

[0108] Search module 151;

[0109] Video and music player module 152, which merges the video player module and the music player module;

[0110] Notepad module 153;

[0111] Map module 154; and / or

[0112] Online video module 155.

[0113] Examples of other applications 136 optionally stored in memory 102 include other word processing applications, other image editing applications, drawing applications, rendering applications, JAVA-enabled applications, encryption, digital rights management, voice recognition, and voice replication.

[0114] In conjunction with the touch screen 112, display controller 156, touch / motion 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 (e.g., stored in the application internal state 192 of the contact module 137 in memory 102 or memory 370), including: adding one or more names to the address book; deleting names from the address book; associating telephone numbers, email addresses, physical addresses, or other information with names; associating images with names; categorizing and classifying names; providing telephone numbers or email addresses to initiate and / or facilitate communications via telephone 138, video conferencing module 139, email 140, or IM 141; and the like.

[0115] In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch screen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134, phone module 138 is optionally used to enter a sequence of characters corresponding to a phone number, access one or more phone numbers in contact module 137, modify an entered phone number, dial a corresponding phone number, conduct a conversation, and disconnect or hang up when the conversation is complete. As described above, wireless communication optionally uses any of a variety of communication standards, protocols, and technologies.

[0116] In combination with the RF circuit 108, the audio circuit 110, the speaker 111, the microphone 113, the touch screen 112, the display controller 156, the optical sensor 164, the optical sensor controller 158, the contact / motion module 130, the graphics module 132, the text input module 134, the contact module 137 and the telephone module 138, the video conferencing module 139 includes executable instructions for initiating, conducting and terminating a video conference between a user and one or more other participants in accordance with user instructions.

[0117] In conjunction with RF circuit 108, touch screen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134, email client module 140 includes executable instructions for creating, sending, receiving, and managing emails in response to user instructions. In conjunction with image management module 144, email client module 140 makes it very easy to create and send emails with still images or video images captured by camera module 143.

[0118] In conjunction with RF circuit 108, touch screen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134, instant messaging module 141 includes executable instructions for the following operations: inputting a character sequence corresponding to an instant message, modifying previously input characters, transmitting a corresponding instant message (e.g., using a short message service (SMS) or multimedia message service (MMS) protocol for phone-based instant messaging or using XMPP, SIMPLE, or IMPS for Internet-based instant messaging), receiving instant messages, and viewing received instant messages. In some embodiments, the transmitted and / or received instant messages optionally include graphics, photos, audio files, video files, and / or other attachments supported in MMS and / or enhanced messaging services (EMS). As used herein, "instant messaging" refers to both phone-based messages (e.g., messages sent using SMS or MMS) and Internet-based messages (e.g., messages sent using XMPP, SIMPLE, or IMPS).

[0119] In combination with the RF circuit 108, the touch screen 112, the display controller 156, the contact / motion module 130, the graphics module 132, the text input module 134, the GPS module 135, the map module 154 and the music player module, the fitness support module 142 includes executable instructions for creating a fitness (e.g., with time, distance and / or calorie burn goals); communicating with fitness sensors (sports equipment); receiving fitness sensor data; calibrating sensors for monitoring fitness; selecting and playing music for fitness; and displaying, storing and transmitting fitness data.

[0120] In conjunction with the touch screen 112, display controller 156, optical sensor 164, optical sensor controller 158, contact / motion module 130, graphics module 132 and image management module 144, the camera module 143 includes executable instructions for the following operations: capturing still images or videos (including video streams) and storing them in the memory 102, modifying the characteristics of the still images or videos, or deleting the still images or videos from the memory 102.

[0121] In conjunction with touch screen 112, display controller 156, touch / motion module 130, graphics module 132, text input module 134, and camera module 143, image management module 144 includes executable instructions for arranging, modifying (e.g., editing), or otherwise manipulating, labeling, deleting, presenting (e.g., in a digital slideshow or album), and storing still images and / or video images.

[0122] In combination with the RF circuit 108, the touch screen 112, the display controller 156, the touch / motion module 130, the graphics module 132 and the text input module 134, the browser module 147 includes executable instructions for browsing the Internet in accordance with user instructions, including searching, linking to, receiving and displaying web pages or portions thereof, as well as attachments and other files linked to web pages.

[0123] In combination with the RF circuit 108, the touch screen 112, the display controller 156, the touch / motion module 130, the graphics module 132, the text input module 134, the email client module 140 and the browser module 147, the calendar module 148 includes executable instructions for creating, displaying, modifying and storing calendars and data associated with the calendar (e.g., calendar entries, to-do items, etc.) in accordance with user instructions.

[0124] In conjunction with the RF circuit 108, the touch screen 112, the display controller 156, the contact / motion module 130, the graphics module 132, the text input module 134, and the browser module 147, the desktop widget module 149 is a mini-application that is optionally downloaded and used by the user (e.g., the weather desktop widget 149-1, the stock desktop widget 149-2, the calculator desktop widget 149-3, the alarm desktop widget 149-4, and the dictionary desktop widget 149-5) or a mini-application created by the user (e.g., the user-created desktop widget 149-6). In some embodiments, the desktop widget includes an HTML (Hypertext Markup Language) file, a CSS (Cascading Style Sheets) file, and a JavaScript file. In some embodiments, the desktop widget includes an XML (Extensible Markup Language) file and a JavaScript file (e.g., the Yahoo! desktop widget).

[0125] In combination with the RF circuit 108, touch screen 112, display controller 156, touch / motion module 130, graphics module 132, text input module 134 and browser module 147, the desktop widget creator module 150 is optionally used by a user to create a desktop widget (e.g., converting a user-specified portion of a web page into a desktop widget).

[0126] In combination with the touch screen 112, display controller 156, contact / motion module 130, graphics module 132 and text input module 134, the search module 151 includes executable instructions for searching the memory 102 for text, music, sound, images, videos and / or other files that match one or more search criteria (e.g., one or more user-specified search terms) in accordance with user instructions.

[0127] In conjunction with touch screen 112, display controller 156, contact / motion module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, and browser module 147, video and music player module 152 includes executable instructions that allow a user to download and play back recorded music and 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 back video (e.g., on touch screen 112 or on an external display connected via external port 124). In some embodiments, device 100 optionally includes the functionality of an MP3 player, such as an iPod (trademark of Apple Inc.).

[0128] In conjunction with the touch screen 112, display controller 156, contact / motion module 130, graphics module 132 and text input module 134, the notepad module 153 includes executable instructions for creating and managing notes, to-do lists, etc. according to user instructions.

[0129] In combination with the RF circuit 108, the touch screen 112, the display controller 156, the touch / motion module 130, the graphics module 132, the text input module 134, the GPS module 135 and the 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 relating to stores and other points of interest at or near a particular location, and other location-based data) in accordance with user instructions.

[0130] In conjunction with touch screen 112, display controller 156, contact / motion 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, online video module 155 includes instructions for performing the following operations: allowing a user to access, browse, receive (e.g., by streaming and / or downloading), playback (e.g., on the touch screen or on an external display connected via external port 124), send an email with a link to a specific online video, and otherwise manage online videos in one or more file formats such as H.264. In some embodiments, instant messaging module 141 is used instead of email client module 140 to send a link to a specific online video. Additional descriptions of online video applications can be found in U.S. Provisional Patent Application No. 60 / 936,562, filed on June 20, 2007, entitled “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos,” and U.S. Patent Application No. 11 / 968,067, filed on December 31, 2007, entitled “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos,” the contents of which are hereby incorporated by reference in their entirety.

[0131] Each of the above modules and applications corresponds to an executable instruction set for performing one or more of the above functions and the methods described in this patent application (e.g., computer-implemented methods and other information processing methods described herein). These modules (e.g., instruction sets) need not be implemented with independent software programs, processes or modules, so various subsets of these modules are optionally combined or otherwise rearranged in various embodiments. For example, a video player module is optionally combined with a music player module into a single module (e.g., video and music player modules 152 in Fig. 1A). In some embodiments, memory 102 optionally stores a subset of the above modules and data structures. In addition, memory 102 optionally stores other modules and data structures not described above.

[0132] In some embodiments, the device 100 is a device where the operation of a predefined set of functions on the device is performed exclusively through a touch screen and / or a touch pad. By using a touch screen and / or a touch pad as the primary input control device for operating the device 100, the number of physical input control devices (e.g., push buttons, dials, etc.) on the device 100 is optionally reduced.

[0133] A predefined set of functions that are performed exclusively through the touch screen and / or trackpad optionally includes navigation between user interfaces. In some embodiments, the touchpad, when touched by the user, navigates the device 100 to a main menu, a home menu, or a root menu from any user interface displayed on the device 100. In such embodiments, a "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, rather than a touchpad.

[0134] Fig. 1B is a block diagram showing exemplary components for event processing according to some embodiments. In some embodiments, memory 102 (Fig. 1A) or memory 370 (Fig. 3) includes event classifier 170 (e.g., in operating system 126) and corresponding application 136-1 (e.g., any one of the aforementioned applications 137 to 151, 155, 380 to 390).

[0135] Event classifier 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 to be delivered. Event classifier 170 includes event monitor 171 and event distributor module 174. In some embodiments, application 136-1 includes application internal state 192, which indicates one or more current application views displayed on touch-sensitive display 112 when the application is active or executing. In some embodiments, device / global internal state 157 is used by event classifier 170 to determine which application(s) is currently active, and application internal state 192 is used by event classifier 170 to determine the application view 191 to which the event information is to be delivered.

[0136] In some embodiments, the application internal state 192 includes additional information, such as one or more of the following: resumption information to be used when the application 136-1 resumes execution, user interface state information indicating that information is being displayed or is ready to be displayed by the application 136-1, a state queue for enabling a user to return to a previous state or view of the application 136-1, and a repeat / undo queue of previous actions taken by the user.

[0137] Event monitor 171 receives event information from peripherals interface 118. Event information includes information about sub-events (e.g., user touches on touch-sensitive display 112 as part of a multi-touch gesture). Peripherals interface 118 transmits information it receives from I / O subsystem 106 or sensors such as proximity sensor 166, one or more accelerometers 168, and / or microphone 113 (through audio circuit 110). The information that peripherals interface 118 receives from I / O subsystem 106 includes information from touch-sensitive display 112 or a touch-sensitive surface.

[0138] In some embodiments, event monitor 171 sends requests to peripheral device interface 118 at predetermined intervals. In response, peripheral device interface 118 transmits event information. In other embodiments, peripheral device interface 118 transmits event information only when there is a significant event (e.g., receiving an input above a predetermined noise threshold and / or receiving an input for more than a predetermined duration).

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

[0140] When the touch-sensitive display 112 displays more than one view, the hit view determination module 172 provides software procedures for determining where within one or more views a sub-event has occurred. A view consists of controls and other elements that a user can see on the display.

[0141] Another aspect of the user interface associated with an application is a set of views, sometimes also referred to herein as application views or user interface windows, in which information is displayed and touch-based gestures occur. The application views (of the respective application) in which a touch is detected optionally correspond to a programmatic level within the programmatic or view hierarchy of the application. For example, the lowest level view in which a touch is detected is optionally referred to as a hit view, and the set of events recognized as correct input is optionally determined at least in part based on the hit view of the initial touch that started the touch-based gesture.

[0142] Hit view determination module 172 receives information related to sub-events of touch-based gestures. When an application has multiple views organized in a hierarchy, hit view determination module 172 identifies the hit view as the lowest view in the hierarchy where the sub-events should be processed. In most cases, the hit view is the lowest level view in which the initiating sub-event (e.g., 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 hit view determination module 172, the hit view typically receives all sub-events related to the same touch or input source for which it was identified as the hit view.

[0143] Active event recognizer determination module 173 determines which view or views within the view hierarchy should receive a particular sequence of sub-events. In some embodiments, active event recognizer determination module 173 determines that only the hit view should receive a particular sequence of sub-events. In other embodiments, active event recognizer determination module 173 determines that all views that include the physical location of the sub-event are actively participating views, and therefore determines that all actively participating views should receive a particular sequence of sub-events. In other embodiments, even if a touch sub-event is completely confined to an area associated with one particular view, higher views in the hierarchy will still remain as actively participating views.

[0144] Event distributor module 174 distributes event information to event recognizers (e.g., event recognizers 180). In embodiments including active event recognizer determination module 173, event distributor module 174 delivers the event information to the event recognizers determined by active event recognizer determination module 173. In some embodiments, event distributor module 174 stores the event information in an event queue, which is retrieved by corresponding event receivers 182.

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

[0146] In some embodiments, application 136-1 includes multiple event handlers 190 and one or more application views 191, each of which includes instructions for handling touch events occurring in a corresponding view of the user interface of the application. Each application view 191 of application 136-1 includes one or more event recognizers 180. Typically, the corresponding application view 191 includes multiple event recognizers 180. In other embodiments, one or more event recognizers in event recognizers 180 are part of an independent module, which is a higher-level object such as a user interface toolkit (not shown) or application 136-1 from which methods and other properties are inherited. In some embodiments, the corresponding event handler 190 includes one or more of the following: data updater 176, object updater 177, GUI updater 178, and / or event data 179 received from event classifier 170. Event handler 190 optionally utilizes or calls data updater 176, object updater 177 or GUI updater 178 to update application internal state 192. Alternatively, one or more of the application views in the application views 191 include one or more corresponding event handlers 190. In addition, in some embodiments, one or more of the data updater 176, the object updater 177, and the GUI updater 178 are included in the corresponding application view 191.

[0147] A corresponding event identifier 180 receives event information (e.g., event data 179) from event classifier 170 and identifies an event from the event information. Event identifier 180 includes an event receiver 182 and an event comparator 184. In some embodiments, event identifier 180 also includes metadata 183 and at least a subset of event delivery instructions 188 (which optionally include sub-event delivery instructions).

[0148] Event receiver 182 receives event information from event classifier 170. Event information includes information about sub-events such as touch or touch movement. Depending on the sub-event, the event information also includes additional information, such as the location of the sub-event. When the sub-event involves the movement of the touch, the event information optionally also includes the speed and direction of the sub-event. In some embodiments, the event includes the device rotating from one orientation to another orientation (e.g., from a longitudinal orientation to a transverse orientation, or vice versa), and the event information includes corresponding information about the current orientation of the device (also referred to as the device posture).

[0149] Event comparator 184 compares event information with predefined event or sub-event definitions, and determines an event or sub-event based on the comparison, or determines or updates the state of an event or sub-event. In some embodiments, event comparator 184 includes event definition 186. Event definition 186 includes the definition of an event (e.g., a predefined sequence of sub-events), such as event 1 (187-1), event 2 (187-2), and others. In some embodiments, sub-events in event (187) include, for example, touch start, touch end, touch move, touch cancel, and multi-touch. In one example, the definition of event 1 (187-1) is a double-click on a displayed object. For example, a double-click includes a first touch (touch start) of a predetermined duration on a displayed object, a first lift-off (touch end) of a predetermined duration, a second touch (touch start) of a predetermined duration on a displayed object, and a second lift-off (touch end) of a predetermined duration. In another example, the definition of event 2 (187-2) is a drag on a displayed object. For example, dragging includes a touch (or contact) of a predetermined duration on a displayed object, movement of the touch on the touch-sensitive display 112, and lifting of the touch (touch end). In some embodiments, the event also includes information for one or more associated event handlers 190.

[0150] In some embodiments, event definition 187 includes definitions of events for corresponding user interface objects. In some embodiments, event comparator 184 performs a hit test to determine which user interface object is associated with a sub-event. For example, in an application view displaying three user interface objects on touch-sensitive display 112, when a touch is detected on touch-sensitive display 112, event comparator 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 comparator uses the result of the hit test to determine which event handler 190 should be activated. For example, event comparator 184 selects an event handler associated with a sub-event and the object that triggered the hit test.

[0151] In some embodiments, the definition of the corresponding event (187) also includes a delay action that delays the delivery of the event information until it has been determined that the sub-event sequence does or does not correspond to the event type of the event identifier.

[0152] When a corresponding event recognizer 180 determines that a sequence of sub-events does not match any event in event definition 186, the corresponding event recognizer 180 enters an event impossible, event failed, or event ended state, after which subsequent sub-events of the touch-based gesture are ignored. In this case, other event recognizers (if any) that remain active for the hit view continue to track and process sub-events of the ongoing touch-based gesture.

[0153] In some embodiments, the corresponding event recognizers 180 include metadata 183 with configurable properties, flags, and / or lists that indicate how the event delivery system should perform sub-event delivery to actively participating event recognizers. In some embodiments, metadata 183 includes configurable properties, flags, and / or lists that indicate how event recognizers interact or can interact with each other. In some embodiments, metadata 183 includes configurable properties, flags, and / or lists that indicate whether sub-events are delivered to different levels in a view or programmatic hierarchy.

[0154] In some embodiments, when one or more specific sub-events of an event are identified, the corresponding event recognizer 180 activates an event handler 190 associated with the event. In some embodiments, the corresponding event recognizer 180 delivers event information associated with the event to the event handler 190. Activating the event handler 190 is different from sending (and deferred sending) the sub-events to the corresponding hit view. In some embodiments, the event recognizer 180 throws a tag associated with the identified event, and the event handler 190 associated with the tag obtains the tag and performs a predefined process.

[0155] In some embodiments, the event delivery instructions 188 include a sub-event delivery instruction that delivers event information about a sub-event without activating an event handler. Instead, the sub-event delivery instruction delivers the event information to an event handler associated with a sub-event sequence or to an actively participating view. The event handler associated with the sub-event sequence or with an actively participating view receives the event information and performs a predetermined process.

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

[0157] In some embodiments, event handler 190 includes or has access to data updater 176, object updater 177, and GUI updater 178. In some embodiments, data updater 176, object updater 177, and GUI updater 178 are included in a single module of the corresponding application 136-1 or application view 191. In other embodiments, they are included in two or more software modules.

[0158] It should be understood that the above discussion of event processing of user touches on a touch-sensitive display also applies to other forms of user input that utilize input devices to operate the multifunction device 100, and not all user input is initiated on the touch screen. For example, mouse movement and mouse button presses, optionally in conjunction with single or multiple keyboard presses or hold; contact movement on a touch pad, such as tapping, dragging, scrolling, etc.; stylus input; movement of the device; verbal commands; detected eye movement; biometric input; and / or any combination thereof are optionally used as input corresponding to sub-events defining the event to be recognized.

[0159] FIG. 2 shows a portable multifunction device 100 with a touch screen 112 according to some embodiments. The touch screen optionally displays one or more graphics within a user interface (UI) 200. In this embodiment and other embodiments described below, a user can select one or more of these graphics by, for example, making gestures on the graphics using one or more fingers 202 (not drawn to scale in the figure) or one or more styluses 203 (not drawn to scale in the figure). In some embodiments, when the user interrupts contact with one or more graphics, selection of one or more graphics will occur. In some embodiments, gestures optionally include one or more taps, one or more swipes (from left to right, from right to left, up and / or down) and / or rolling of fingers that have been in contact with the device 100 (from right to left, from left to right, up and / or down). In some specific implementations or in some cases, inadvertent contact with a graphic will not select the graphic. For example, when the gesture corresponding to the selection is a tap, a swipe gesture that sweeps over an application icon optionally does not select the corresponding application.

[0160] The device 100 optionally also includes one or more physical buttons, such as a "home" or menu button 204. As previously described, the menu button 204 is optionally used to navigate to any application 136 in a set of applications that are optionally executed on the device 100. Alternatively, in some embodiments, the menu button is implemented as a soft key in a GUI displayed on the touch screen 112.

[0161] In some embodiments, the device 100 includes a touch screen 112, a menu button 204, a push button 206 for turning the device on / off and for locking the device, one or more volume adjustment buttons 208, a user identity module (SIM) card slot 210, an earphone jack 212, and a docking / charging external port 124. The push button 206 is optionally used to turn the device on / off by pressing the button and keeping the button in a pressed state for a predefined time interval; lock the device by pressing the button and releasing the button before the predefined time interval passes; and / or unlock the device or initiate an unlocking process. In an alternative embodiment, the device 100 also accepts voice input for activating or deactivating certain functions through a microphone 113. The device 100 also optionally includes one or more contact strength sensors 165 for detecting the strength of contact on the touch screen 112, and / or one or more tactile output generators 167 for generating tactile output for a user of the device 100.

[0162] Fig. 3 is a block diagram of an exemplary multifunctional device with a display and a touch-sensitive surface according to some embodiments. Device 300 need not be portable. In some embodiments, device 300 is a laptop, 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 controller or an industrial controller). Device 300 typically includes one or more processing units (CPUs) 310, one or more networks or other communication interfaces 360, a memory 370 and one or more communication buses 320 for interconnecting these components. Communication bus 320 optionally includes a circuit (sometimes referred to as a chipset) that interconnects system components and controls the communication between system components. Device 300 includes an input / output (I / O) interface 330 with a display 340, which is typically a touch screen display. The I / O interface 330 also optionally includes a keyboard and / or mouse (or other pointing device) 350 and a touch pad 355, a tactile output generator 357 for generating tactile output on the device 300 (e.g., similar to the one or more tactile output generators 167 described above with reference to FIG. 1A ), and a sensor 359 (e.g., an optical sensor, an acceleration sensor, a proximity sensor, a touch sensor, and / or a contact force sensor (similar to the one or more contact force sensors 165 described above with reference to FIG. 1A )). The memory 370 includes a high-speed random access memory, such as DRAM, SRAM, DDR RAM, or other random access solid-state memory devices; and optionally includes a 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. The memory 370 optionally includes one or more storage devices located away from the CPU 310. In some embodiments, the memory 370 stores programs, modules, and data structures similar to those stored in the memory 102 of the portable multifunction device 100 ( FIG. 1A ), or a subset thereof. In addition, memory 370 optionally stores additional programs, modules, and data structures not present in memory 102 of portable multifunction device 100. For example, memory 370 of device 300 optionally stores a drawing module 380, a presentation module 382, ​​a word processing module 384, a website creation module 386, a disk editing module 388, and / or a spreadsheet module 390, while memory 102 of portable multifunction device 100 ( FIG. 1A ) optionally does not store these modules.

[0163] Each element in the above-mentioned elements in Fig. 3 is optionally stored in one or more memory devices of the previously mentioned memory device.Each module in the above-mentioned modules corresponds to the instruction set for performing the above-mentioned functions.The above-mentioned modules or programs (e.g., instruction sets) need not be implemented as independent software programs, processes or modules, and therefore the various subsets of these modules are optionally combined or otherwise rearranged in various embodiments.In some embodiments, memory 370 optionally stores the subset of the above-mentioned modules and data structures.In addition, memory 370 optionally stores other modules and data structures not described above.

[0164] Attention is now turned to an embodiment of a user interface that is optionally implemented on, for example, portable multifunction device 100.

[0165] 4A illustrates an exemplary user interface for an application menu on portable multifunction device 100 according to some embodiments. A similar user interface is optionally implemented on device 300. In some embodiments, user interface 400 includes the following elements, or a subset or superset thereof:

[0166] One or more signal strength indicators 402 of one or more wireless communications such as cellular signals and Wi-Fi signals;

[0167] Time 404;

[0168] Bluetooth indicator 405;

[0169] Battery status indicator 406;

[0170] A tray 408 with icons for commonly used applications, such as:

[0171] o an icon 416 of the phone module 138 labeled “Phone”, the icon 416 optionally including an indicator 414 of the number of missed calls or voice messages;

[0172] o an icon 418 of the email client module 140 labeled “Mail”, the icon 418 optionally including an indicator 410 of the number of unread emails;

[0173] o an icon 420 labeled "Browser" of the browser module 147; and

[0174] o an icon 422 labeled “iPod” of a video and music player module 152 (also referred to as an iPod (trademark of Apple Inc.) module 152); and

[0175] Icons for other apps, such as:

[0176] o Icon 424 labeled “Messages” of IM module 141;

[0177] o Icon 426 labeled “Calendar” of calendar module 148;

[0178] o Icon 428 labeled “Photos” of the image management module 144;

[0179] o Icon 430 labeled “Camera” of camera module 143;

[0180] o Icon 432 labeled “Online Video” of the online video module 155;

[0181] o Icon 434 labeled “Stock Market” of the Stock Market widget 149-2;

[0182] o an icon 436 labeled “MAP” of the map module 154;

[0183] o Icon 438 labeled “Weather” of the Weather widget 149-1;

[0184] o Icon 440 labeled “Clock” of the alarm clock widget 149-4;

[0185] o an icon 442 labeled “Fitness Support” of the fitness support module 142;

[0186] o Icon 444 labeled "Notepad" of the Notepad module 153; and

[0187] o An icon 446 of a settings application or module labeled “Settings” that provides access to settings for the device 100 and its various applications 136 .

[0188] It should be noted that the icon labels shown in FIG. 4A are exemplary only. For example, icon 422 of video and music player module 152 is labeled "Music" or "Music Player". Other labels are optionally used for various application icons. In some embodiments, the label of a corresponding application icon includes the name of the application corresponding to the corresponding application icon. In some embodiments, the label of a particular application icon is different from the name of the application corresponding to the particular application icon.

[0189] 4B shows an exemplary user interface on a device (e.g., device 300 of FIG. 3 ) having a touch-sensitive surface 451 (e.g., tablet or touchpad 355 of FIG. 3 ) that is separate from a display 450 (e.g., touch screen display 112 ). Device 300 also optionally includes one or more contact intensity sensors (e.g., one or more of sensors 359 ) for detecting the intensity of contacts on touch-sensitive surface 451 and / or one or more tactile output generators 357 for generating tactile outputs for a user of device 300.

[0190] Although some of the examples below will be given with reference to input on a touch screen display 112 (in which a touch-sensitive surface and a display are combined), in some embodiments, the device detects input on a touch-sensitive surface that is separate from the display, as shown in FIG. 4B. In some embodiments, the touch-sensitive surface (e.g., 451 in FIG. 4B) has a main axis (e.g., 452 in FIG. 4B) corresponding to a main axis (e.g., 453 in FIG. 4B) on a display (e.g., 450). According to these embodiments, the device detects contact (e.g., 460 and 462 in FIG. 4B) with the touch-sensitive surface 451 at a position corresponding to a corresponding position on the display (e.g., in FIG. 4B, 460 corresponds to 468 and 462 corresponds to 470). In this way, when the touch-sensitive surface (e.g., 451 in FIG. 4B) is separated from the display (450 in FIG. 4B) of the multifunction device, the user input detected by the device on the touch-sensitive surface (e.g., contacts 460 and 462 and their movement) is used by the device to manipulate the user interface on the display. It should be understood that similar methods are optionally used for other user interfaces described herein.

[0191] In addition, although the following examples are primarily given with reference to finger inputs (e.g., finger contacts, single-finger tap gestures, finger swipe gestures), it should be understood that in some embodiments, one or more of these finger inputs are replaced by input from another input device (e.g., mouse-based input or stylus input). For example, a swipe gesture is optionally replaced by a mouse click (e.g., instead of contact), followed by movement of the cursor along the path of the swipe (e.g., instead of movement of the contact). As another example, a tap gesture is optionally replaced by a mouse click when the cursor is over the location of the tap gesture (e.g., instead of detecting contact, followed by ceasing to detect contact). Similarly, when multiple user inputs are detected simultaneously, it should be understood that multiple computer mice are optionally used simultaneously, or a mouse and finger contact are optionally used simultaneously.

[0192] FIG. 5A shows an exemplary personal electronic device 500. The device 500 includes a body 502. In some embodiments, the device 500 may include some or all of the features described with respect to the devices 100 and 300 (e.g., FIG. 1A to FIG. 4B). In some embodiments, the device 500 has a touch-sensitive display screen 504, referred to as a touch screen 504 hereinafter. As an alternative or supplement to the touch screen 504, the device 500 has a display and a touch-sensitive surface. As in the case of the devices 100 and 300, in some embodiments, the touch screen 504 (or touch-sensitive surface) optionally includes one or more intensity sensors for detecting the intensity of the contact (e.g., touch) applied. One or more intensity sensors of the touch screen 504 (or touch-sensitive surface) may provide output data representing the intensity of the touch. The user interface of the device 500 may respond to the touch based on the intensity of the touch, which means that different intensities of touch may invoke different user interface operations on the device 500.

[0193] Exemplary techniques for detecting and processing touch intensity are found, for example, in the following related patent applications: International patent application serial number PCT / US2013 / 040061, entitled “Device, Method, and Graphical User Interface for Displaying User Interface Objects Corresponding to an Application,” filed on May 8, 2013, published as WIPO patent publication number WO / 2013 / 169849; and International patent application serial number PCT / US2013 / 069483, entitled “Device, Method, and Graphical User Interface for Transitioning Between Touch Input to Display Output Relationships,” filed on November 11, 2013, published as WIPO patent publication number WO / 2014 / 105276, each of which is hereby incorporated by reference in its entirety.

[0194] In some embodiments, the device 500 has one or more input mechanisms 506 and 508. The input mechanisms 506 and 508 (if included) can be physical. Examples of physical input mechanisms include push buttons and rotatable mechanisms. In some embodiments, the device 500 has one or more attachment mechanisms. Such attachment mechanisms (if included) can allow the device 500 to be attached to, for example, hats, glasses, earrings, necklaces, shirts, jackets, bracelets, watchbands, bracelets, pants, belts, shoes, wallets, backpacks, etc. These attachment mechanisms allow the user to wear the device 500.

[0195] FIG. 5B shows an exemplary personal electronic device 500. In some embodiments, the device 500 may include some or all of the components described with reference to FIG. 1A, FIG. 1B, and FIG. 3. The device 500 has a bus 512 that operatively couples an I / O portion 514 to one or more computer processors 516 and a memory 518. The I / O portion 514 may be connected to a display 504 that may have a touch-sensitive component 522 and optionally an intensity sensor 524 (e.g., a contact intensity sensor). In addition, the I / O portion 514 may be connected to a communication unit 530 for receiving application and operating system data using Wi-Fi, Bluetooth, near field communication (NFC), cellular, and / or other wireless communication technologies. The device 500 may include an input mechanism 506 and / or 508. For example, the input mechanism 506 may be optionally a rotatable input device or a depressible input device and a rotatable input device. In some examples, the input mechanism 508 may be optionally a button.

[0196] In some examples, input mechanism 508 is optionally a microphone. Personal electronic device 500 optionally includes various sensors, such as GPS sensor 532, accelerometer 534, orientation sensor 540 (e.g., compass), gyroscope 536, motion sensor 538, and / or combinations thereof, all of which are operably connected to I / O portion 514.

[0197] The memory 518 of the personal electronic device 500 may include one or more non-transitory computer-readable storage media for storing computer-executable instructions, which, when executed by one or more computer processors 516, may, for example, cause the computer processor to perform the techniques described below, including process 800 (FIG. 8A to 8B), process 1000 (FIG. 10A to 10D), and process 1200 (FIG. 12A to 12B). A computer-readable storage medium may be any medium that can tangibly contain or store computer-executable instructions for use by or in conjunction with an instruction execution system, apparatus, and device. In some embodiments, the storage medium is a transient computer-readable storage medium. In some embodiments, the storage medium is a non-transitory computer-readable storage medium. Non-transitory computer-readable storage media may include, but are not limited to, magnetic storage devices, optical storage devices, and / or semiconductor storage devices. Examples of such storage devices include magnetic disks, optical disks based on CD, DVD, or Blu-ray technology, and persistent solid-state memory such as flash memory, solid-state drives, and the like. The personal electronic device 500 is not limited to the components and configurations of FIG. 5B, but may include other components or additional components in a variety of configurations.

[0198] As used herein, the term "affordance" refers to a user-interactive graphical user interface object that is optionally displayed on a display screen of device 100, 300, and / or 500 (FIGS. 1, 3, and 5). For example, an image (e.g., an icon), a button, and text (e.g., a hyperlink) optionally each constitute an affordance.

[0199] As used herein, the term "focus selector" refers to an input element used to indicate the current portion of a user interface with which a user is interacting. In some implementations that include a cursor or other position marker, the cursor acts as a "focus selector" such that when an input (e.g., a press input) is detected on a touch-sensitive surface (e.g., touchpad 355 in FIG. 3 or touch-sensitive surface 451 in FIG. 4B ) while the cursor is over a particular user interface element (e.g., a button, window, slider, or other user interface element), the particular user interface element is adjusted in accordance with the detected input. In some implementations that include a touch screen display that enables direct interaction with user interface elements on a touch screen display (e.g., touch-sensitive display system 112 in FIG. 1A or touch screen 112 in FIG. 4A ), a contact detected on the touch screen acts as a "focus selector" such that when an input (e.g., a press input by a contact) is detected at the location of a particular user interface element (e.g., a button, window, slider, or other user interface element) on the touch screen display, the particular user interface element is adjusted in accordance with the detected input. In some implementations, focus moves from one area of ​​a user interface to another area of ​​the user interface without corresponding movement of a cursor or movement of a contact on a touch screen display (e.g., by using a tab key or arrow keys to move focus from one button to another); in these implementations, a 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 is typically a user interface element (or contact on a touch screen display) that is controlled by a user to deliver the user's intended interaction with the user interface (e.g., by indicating to the device the element of the user interface with which the user desires to interact). For example, when a press input is detected on a touch-sensitive surface (e.g., a touchpad or touch screen), the position of a focus selector (e.g., a cursor, contact, or selection box) over a corresponding button will indicate that the user desires to activate the corresponding button (rather than other user interface elements shown on the device display).

[0200] As used in the specification and claims, the term "characteristic intensity" of a contact refers to a characteristic of a contact based on one or more intensities of the contact. In some embodiments, the characteristic intensity is based on multiple intensity samples. The characteristic intensity is optionally based on a predefined number of intensity samples or a set of intensity samples collected during a predetermined time period (e.g., 0.05 seconds, 0.1 seconds, 0.2 seconds, 0.5 seconds, 1 second, 2 seconds, 5 seconds, 10 seconds) relative to a predefined event (e.g., after contact is detected, before contact is detected to be lifted off, before or after contact starts to move, before contact ends, before or after contact intensity is detected to increase, and / or before or after contact intensity is detected to decrease). The characteristic intensity of a contact is optionally based on one or more of the following: the maximum value of the intensity of the contact, the mean value of the intensity of the contact, the average value of the intensity of the contact, the value at the top 10% of the intensity of the contact, the half-maximum value of the intensity of the contact, the 90% maximum value of the intensity of the contact, etc. In some embodiments, the duration of the contact is used when determining the characteristic intensity (e.g., when the characteristic intensity is the average value of the intensity of the contact over time). In some embodiments, the feature strength is compared to a set of one or more strength thresholds to determine whether the user has performed an operation. For example, the set of one or more strength thresholds optionally includes a first strength threshold and a second strength threshold. In this example, a contact whose feature strength does not exceed the first threshold results in a first operation, a contact whose feature strength exceeds the first strength threshold but does not exceed the second strength threshold results in a second operation, and a contact whose feature strength exceeds the second threshold results in a third operation. In some embodiments, a comparison between the feature strength and one or more thresholds is used to determine whether to perform one or more operations (e.g., whether to perform the corresponding operation or to abandon the corresponding operation) rather than to determine whether to perform the first operation or the second operation.

[0201] FIG. 5C shows multiple contacts 552A-552E on a touch-sensitive display screen 504 detected using multiple intensity sensors 524A-524D. FIG. 5C also includes an intensity graph, which shows the current intensity measurements of intensity sensors 524A-524D relative to intensity units. In this embodiment, the intensity measurements of intensity sensors 524A and 524D are both 9 intensity units, and the intensity measurements of intensity sensors 524B and 524C are both 7 intensity units. In some specific implementations, the cumulative intensity is the sum of the intensity measurements of multiple intensity sensors 524A-524D, which is 32 intensity units in this embodiment. In some embodiments, each contact is assigned a corresponding intensity, i.e., a portion of the cumulative intensity. FIG. 5D shows the cumulative intensity assigned to contacts 552A-552E based on their distance from the center of force 554. In this embodiment, each of contacts 552A, 552B, and 552E is assigned a contact strength of 8 strength units of the cumulative strength, and each of contacts 552C and 552D is assigned a contact strength of 4 strength units of the cumulative strength. More generally, in some embodiments, each contact j is assigned a corresponding strength Ij, which is a portion of the cumulative strength A, according to a predefined mathematical function Ij=A·(Dj / ΣDi), where Dj is the distance of the corresponding contact j from the force center, and ΣDi is the sum of the distances of all corresponding contacts (e.g., i=1 to the last) from the force center. The operations described with reference to Figures 5C-5D can be performed using an electronic device similar to or equivalent to device 100, 300, or 500. In some embodiments, the characteristic strength of a contact is based on one or more strengths of the contact. In some embodiments, an intensity sensor is used to determine a single characteristic strength (e.g., a single characteristic strength of a single contact). It should be noted that the intensity map is not part of the displayed user interface, but is included in Figures 5C-5D to assist the reader.

[0202] In some embodiments, a portion of a gesture is identified for determining characteristic strength. For example, the touch-sensitive surface optionally receives a continuous swipe contact that transitions from a starting position and reaches an end position, where the contact strength increases. In this example, the characteristic strength of the contact at the end position is optionally based only on a portion of the continuous swipe contact, rather than the entire swipe contact (e.g., only the portion of the swipe contact at the end position). In some embodiments, a smoothing algorithm is optionally applied to the strength of the swipe contact before determining the characteristic strength of the contact. For example, a smoothing algorithm optionally includes one or more of the following: an unweighted sliding average smoothing algorithm, a triangular smoothing algorithm, a median filter smoothing algorithm, and / or an exponential smoothing algorithm. In some cases, these smoothing algorithms eliminate narrow peaks or depressions in the strength of the swipe contact to achieve the purpose of determining the characteristic strength.

[0203] The intensity of contact on the touch-sensitive surface is optionally characterized relative to one or more intensity thresholds such as a contact detection intensity threshold, a light press intensity threshold, a deep press intensity threshold, and / or one or more other intensity thresholds. In some embodiments, the light press intensity threshold corresponds to an intensity at which the device will perform an operation typically associated with clicking a button of a physical mouse or touchpad. In some embodiments, the deep press intensity threshold corresponds to an intensity at which the device will perform an operation different from the operation typically associated with clicking a button of a physical mouse or touchpad. In some embodiments, when a contact having a characteristic intensity lower than the light press intensity threshold (e.g., and higher than a nominal contact detection intensity threshold, contacts lower than the nominal contact detection intensity threshold are no longer detected) is detected, the device will move the focus selector according to the movement of the contact on the touch-sensitive surface without performing an operation associated with the light press intensity threshold or the deep press intensity threshold. Generally speaking, unless otherwise stated, these intensity thresholds are consistent between different groups of user interface illustrations.

[0204] An increase in contact feature intensity from an intensity below a light press intensity threshold to an intensity between the light press intensity threshold and the deep press intensity threshold is sometimes referred to as a "light press" input. An increase in contact feature intensity from an intensity below a deep press intensity threshold to an intensity above the deep press intensity threshold is sometimes referred to as a "deep press" input. An increase in contact feature intensity from an intensity below a contact detection intensity threshold to an intensity between the contact detection intensity threshold and the light press intensity threshold is sometimes referred to as detecting contact on the touch surface. A decrease in contact feature intensity from an intensity above the contact detection intensity threshold to an intensity below the contact detection intensity threshold is sometimes referred to as detecting contact lifted from the touch surface. In some embodiments, the contact detection intensity threshold is zero. In some embodiments, the contact detection intensity threshold is greater than zero.

[0205] In some embodiments described herein, one or more operations are performed in response to detecting a gesture that includes a corresponding press input or in response to detecting a corresponding press input performed using a corresponding contact (or multiple contacts), wherein the corresponding press input is detected at least in part based on detecting that the strength of the contact (or multiple contacts) increases to above a press input strength threshold. In some embodiments, the corresponding operation is performed in response to detecting that the strength of the corresponding contact increases to above the press input strength threshold (e.g., a "down stroke" of the corresponding press input). In some embodiments, the press input includes an increase in the strength of the corresponding contact to above the press input strength threshold and the strength of the contact subsequently decreases to below the press input strength threshold, and the corresponding operation is performed in response to detecting that the strength of the corresponding contact subsequently decreases to below the press input threshold (e.g., an "up stroke" of the corresponding press input).

[0206] 5E-5H illustrate detection of a gesture that includes contact 562 moving from an intensity below the light press intensity threshold (eg, “IT L ”) to a level above the deep press intensity threshold in FIG. 5H (e.g., “IT D ”). On the displayed user interface 570 including application icons 572A-572D displayed in the predefined area 574, when the cursor 576 is displayed above the application icon 572B corresponding to application 2, a gesture performed using contact 562 is detected on the touch-sensitive surface 560. In some embodiments, the gesture is detected on the touch-sensitive display 504. The intensity sensor detects the intensity of the contact on the touch-sensitive surface 560. The device determines whether the intensity of the contact 562 is within the deep press intensity threshold (for example, “IT D ”) reaches a peak above. Contact 562 is maintained on touch-sensitive surface 560. In response to detecting the gesture, and according to the intensity increasing to a deep press intensity threshold (e.g., “IT D ”) above contact 562, scaled representations 578A-578C (e.g., thumbnails) of documents most recently opened for application 2 are displayed, as shown in Figures 5F-5H. In some embodiments, the intensity is a characteristic intensity of the contact compared to one or more intensity thresholds. It should be noted that the intensity map for contact 562 is not part of the displayed user interface, but is included in Figures 5E-5H to assist the reader.

[0207] In some embodiments, the display of representations 578A-578C includes animation. For example, representation 578A is initially displayed near application icon 572B, as shown in FIG5F . As the animation progresses, representation 578A moves upward, and representation 578B is displayed near application icon 572B, as shown in FIG5G . Then, representation 578A moves upward, 578B moves upward toward representation 578A, and representation 578C is displayed near application icon 572B, as shown in FIG5H . Representations 578A-578C form an array above icon 572B. In some embodiments, the animation progresses according to the intensity of contact 562, as shown in FIG5F-FIG5G , where representations 578A-578C appear and move as the intensity of contact 562 moves toward a deep press intensity threshold (e.g., “IT D ”) increases and moves upward. In some embodiments, the intensity on which the animation progresses is the characteristic intensity of the contact. The operations described in reference Figures 5E-5H can be performed using an electronic device similar to or equivalent to device 100, 300 or 500.

[0208] In some embodiments, the device employs intensity hysteresis to avoid unexpected inputs sometimes referred to as "jitter," where the device defines or selects a hysteresis intensity threshold that has a predefined relationship to a press input intensity threshold (e.g., the hysteresis intensity threshold is X intensity units lower than the press input intensity threshold, or the hysteresis intensity threshold is 75%, 90%, or some reasonable proportion of the press input intensity threshold). Thus, in some embodiments, a press input includes an increase in the intensity of the corresponding contact to above the press input intensity threshold and a subsequent decrease in the intensity of the contact to below the hysteresis intensity threshold corresponding to the press input intensity threshold, and a corresponding operation is performed in response to detecting that the intensity of the corresponding contact subsequently decreases to below the hysteresis intensity threshold (e.g., an "upward stroke" of the corresponding press input). Similarly, in some embodiments, a press input is detected only when the device detects that the contact intensity increases from an intensity equal to or below the hysteresis intensity threshold to an intensity equal to or above the press input intensity threshold and, optionally, that the contact intensity subsequently decreases to an intensity equal to or below the hysteresis intensity, and a corresponding operation is performed in response to detecting the press input (e.g., an increase in contact intensity or a decrease in contact intensity, depending on the circumstances).

[0209] For ease of explanation, optionally, a description of an operation performed in response to a press input associated with a press input intensity threshold or in response to a gesture including a press input is triggered in response to detecting any of the following: contact intensity increasing to above the press input intensity threshold, contact intensity increasing from an intensity below a hysteresis intensity threshold to an intensity above the press input intensity threshold, contact intensity decreasing to below the press input intensity threshold, and / or contact intensity decreasing to below a hysteresis intensity threshold corresponding to the press input intensity threshold. Additionally, in examples where an operation is described as being performed in response to detecting that the intensity of the contact decreases below the press input intensity threshold, the operation is optionally performed in response to detecting that the intensity of the contact decreases below a hysteresis intensity threshold that corresponds to and is less than the press input intensity threshold.

[0210] As used herein, an "installed application" refers to a software application that has been downloaded to an electronic device (e.g., device 100, 300, and / or 500) and is ready to be launched (e.g., become open) on the device. In some embodiments, a downloaded application becomes an installed application using an installer that extracts program portions from a downloaded software package and integrates the extracted portions with the operating system of a computer system.

[0211] As used herein, the term "open application" or "executing application" refers to a software application that has retained state information (e.g., as part of device / global internal state 157 and / or application internal state 192). An open or executing application is optionally any of the following types of applications:

[0212] The active application currently displayed on the display of the device on which the application is being used;

[0213] Background applications (or background processes), which are not currently displayed but one or more processes of the application are being processed by one or more processors; and

[0214] - A suspended or dormant application that is not running but has state information stored in memory (volatile and non-volatile, respectively) and can be used to resume execution of the application.

[0215] As used herein, the term "closed application" refers to a software application that does not have retained state information (e.g., the state information of a closed application is not stored in the memory of the device). Therefore, closing an application includes stopping and / or removing the application process of the application and removing the state information of the application from the memory of the device. Generally speaking, when in a first application, opening a second application does not close the first application. When the second application is displayed and the first application stops being displayed, the first application becomes a background application.

[0216] Figures 5I to 5N show exemplary user interfaces for displaying application-specific affordances on a dynamically updated touch screen display according to some embodiments. These embodiments of the user interface ("UI") and associated processes can be implemented by a portable computing system (e.g., the portable computing system 100 shown in Figures 1A to 1B of the cross-referenced U.S. Provisional Patent Application Serial No. 62 / 368,988, a portion of which is included in Appendix B) or a desktop computing system (e.g., the desktop computing system 200 shown in Figures 2A to 2D of the cross-referenced U.S. Provisional Patent Application Serial No. 62 / 368,988, a portion of which is included in Appendix B). Those of ordinary skill in the art will understand that the following user interfaces are merely examples. In addition, those of ordinary skill in the art will understand that additional affordances and / or user interface elements may be used in practice, or that fewer affordances and / or user interface elements may be used in practice.

[0217] FIG. 5I shows a main display 5000, which displays a status tray 5014A indicating that the system (i.e., operating system) is currently in focus and an application (app) tray 5014B with multiple executable / selectable application icons, wherein the multiple executable / selectable application icons include: mail application icon 5006, web browser application icon 5008, media player application icon 5010, application icon 5012, and photo application icon 5015. In some embodiments, the status tray 5014A indicates the application currently running in the foreground and also includes multiple menus (e.g., File, Edit, View, Go, Window, and Help menus in FIG. 5I), each menu including a set of corresponding controls for the application. FIG. 5I also shows the main display 5000 displaying a cursor 5004 at a position corresponding to the application icon 5012.

[0218] FIG5I also shows a dynamic function row 5002 (e.g., a touch-sensitive display) that displays multiple affordances based on the current focus of the primary display 5000 (i.e., the operating system, because no application windows are open). For example, in FIG5I , the system / operating system is currently in focus on the primary display 5000. In FIG5I , the dynamic function row 5002 includes persistent controls implemented as physical keys and / or soft keys, including: an escape affordance 5016 that, when activated (e.g., via a tap contact), invokes a corresponding function (e.g., exits an application currently in focus on the primary display 5000 or pauses a game); and a power control 5034 that, when activated (e.g., via a tap contact), causes a modal alert to be displayed on the dynamic function row 5002 and / or the primary display 5000 for exiting, restarting, or shutting down the system.

[0219] In FIG. 5I , the dynamic function row 5002 also includes a plurality of system-level enable indications, including: a brightness enable indication 5018 for adjusting the brightness of the main display 5000; a brightness enable indication 5020 for adjusting the brightness of a set of physical keys 106 (when applicable) and / or the brightness of the dynamic function row 5002; an exposure enable indication 5022, which, when activated (e.g., via a tap contact), causes a preview window of the active application to be displayed on the main display 5000; a search enable indication 5024 for performing a local search (e.g., for electronic documents) and / or an Internet search; and an enable indication 5025 for enabling a user to search the main display 5000. Dynamic display row 5002 includes a display of default or user-selected widgets and tools on main display 5000 when activated (e.g., via a tap contact); a notification display 5028, which, when activated (e.g., via a tap contact), displays a notification center on main display 5000 that includes recent messages, notifications, calendar events, etc.; a play / pause display 5030 for initiating or pausing playback of a media item (e.g., a song, a podcast, a video, etc.); and a volume control display 5032 for adjusting the volume of a media item being played. For example, when a tap is detected on brightness display 5020, dynamic function row 5002 displays a brightness slider for adjusting the brightness of a set of physical keys and / or the brightness of dynamic function row 5002. In some embodiments, the multiple system-level enable indicators also include a settings enable indicator (not shown) for accessing adjustment settings associated with the dynamic function row 5002, such as symbol / icon size, touch detection sensitivity, tactile feedback, auditory feedback, animation for changing focus, power mode, etc.

[0220] FIG5J shows primary display 5000 displaying window 5224 for a web browser application in response to detecting that web browser application icon 5008 has been selected with cursor 5004. In FIG5J , window 5224 includes controls for the web browser application, including navigation controls (e.g., previous web page, next web page, refresh, and add to favorites), an address bar, a search bar, a show all bookmarks affordance (e.g., similar to an open book), a show all open tabs affordance (e.g., a grid of six squares), and affordances for specific bookmarks A, B, and C. In FIG5J , window 5224 shows a home interface for the web browser application, including a plurality of affordances 5227 linking to favorite or most frequently visited websites A through H. In FIG5J , window 5224 for application A is in focus on primary display 5000. In Figure 5J, status tray 5014A indicates that the web browser application is running in the foreground, and app tray 5014B also indicates that the web browser application is running in the foreground based on the shadow behind web browser application icon 5008.

[0221] FIG5J also shows dynamic function row 5002 displaying affordance 5226 in addition to persistent controls (i.e., affordances 5016 and 5034) and multiple system-level affordances (i.e., affordances 5018, 5020, 5022, 5024, 5026, 5028, 5030, and 5032) in response to detecting that web browser application icon 5008 has been selected with cursor 5004 in FIG5I. When activated (e.g., via a tap contact), affordance 5226 causes dynamic function row 5002 to display a set of controls for the web browser application (e.g., affordances 5230, 5232, and 5238, and address bar 5234, as shown in FIG5K). FIG5J also shows dynamic function row 5002 receiving and detecting contact 5228 (e.g., a tap contact) at a location corresponding to affordance 5226.

[0222] FIG. 5K shows a dynamic function row 5002 that displays a set of controls for a web browser application in response to detecting a selection of affordance 5226 in FIG. 5J. In FIG. 5K, the set of controls for the web browser application includes affordance 5230 for displaying a web page visited before the web page currently displayed by the web browser application in window 5224; affordance 5232 for displaying a web page visited after the web page currently displayed by the web browser application in window 5224; affordance 5238 for adding the web page currently displayed by the web browser application to a favorites list or a bookmark folder; and address bar 5234 for displaying the URL of the web page currently displayed by the web browser application. In FIG. 5K, address bar 5234 also includes refresh affordance 5236 for refreshing the web page currently displayed by the web browser application. FIG. 5K also shows main display 5000 displaying cursor 5004 at a position corresponding to affordance 5227-A linked to website A.

[0223] FIG5L shows primary display 5000 displaying an interface for tab A within window 5224 after detecting that affordance 5227-A corresponding to website A has been selected with cursor 5004 in FIG5K. In FIG5L, the interface for tab A is in focus on primary display 5000, as indicated by the bold line around tab A and the bold text for tab A. In FIG5L, the interface for tab A displays a checkout web page for website A (e.g., a page associated with URL: www.website_A.com / checkout). The checkout web page corresponds to a user's virtual shopping cart, which includes items A and B to be purchased. FIG5L also shows primary display 5000 displaying cursor 5004 at a location corresponding to the purchase affordance within window 5224. FIG5K also shows dynamic functionality row 5002 displaying the URL for the checkout web page for website A in address bar 5234 (e.g., www.website_A.com / checkout).

[0224] FIG. 5M shows a main display 5000 displaying a modal alert 5240 on window 5224 in response to detecting that a purchase affordance is selected with cursor 5004 in FIG. 5L. In FIG. 5M, modal alert 5240 displayed on main display 5000 prompts the user to provide their fingerprint on dynamic function row 5002, and also includes a cancel affordance 5242 that, when activated (e.g., via selection of cursor 5004), causes the purchase to be canceled. For example, modal alert 5240 is displayed based on the security settings (e.g., default or user-specified security settings) that require fingerprints to verify purchases initiated by the system. For example, in some embodiments, when a password is entered to access an application or website, when a password is entered to decrypt system-stored data, when a folder and / or data is deleted from the system, when other destructive actions are taken, etc., main display 5000 and / or dynamic function row 5002 display a modal alert to prompt the user to provide their fingerprint on dynamic function row 5002 when logging into the system.

[0225] FIG. 5M also shows a dynamic function row 5002 that displays a modal alert 5240 in response to detecting that a purchase enable indication has been selected with the cursor 5004 in FIG. 5L. In FIG. 5M, the modal alert 5240 displayed on the dynamic function row 5002 prompts the user to provide their fingerprint in the fingerprint area 5244 of the dynamic function row 5002, and also includes a cancel enable indication 5242, which cancels the enable indication when activated (e.g., via a tap contact) to cancel the purchase. In some embodiments, the dynamic function row 5002 is configured to detect a fingerprint within the fingerprint area 5244 of the dynamic function row 5002, which also corresponds to the power control 5034. In some embodiments, the dynamic function row 5002 is configured to detect a fingerprint at any position within its touch-sensitive area. FIG. 5M also shows a dynamic function row 5002 that receives and detects a contact 5246 (e.g., a press and hold gesture) within the fingerprint area 5244.

[0226] Figure 5N shows main display 5000 displaying an interface for tab A within window 5224 after contact 5246 is detected within fingerprint area 5244 in Figure 5M. In Figure 5N, the interface for tab A displays a receipt web page for website A (e.g., a page associated with URL: www.website_A.com / reciept), indicating that the purchase was completed after verification of the fingerprint provided by the user.

[0227] In some examples, the techniques and features described above with reference to Figures 5I to 5N are combined with the techniques described below with reference to Figures 7A to 7D-10, Figures 9A-1 to 9E-4, and Figures 11A to 11M-4. In some examples, the main display (e.g., 5000) described above corresponds to the first display (e.g., 702, 902, 1102) described below. In some examples, the dynamic function row (e.g., 5002) described above corresponds to the second display (e.g., 704, 904, 1104) described below. In some examples, the fingerprint area (e.g., 5244) of the dynamic function row (e.g., 5002) corresponds to the fingerprint sensor (e.g., 710, 910, 1120) described below.

[0228] FIG6 illustrates an exemplary device connected via one or more communication channels to participate in a transaction according to some embodiments. One or more exemplary electronic devices (e.g., devices 100, 300, and 500) are configured to optionally detect input (e.g., specific user input, NFC field), and optionally transmit payment information (e.g., using NFC). The one or more electronic devices optionally include NFC hardware and are configured to support NFC.

[0229] The electronic device (e.g., devices 100, 300, and 500) is optionally configured to store payment account information associated with each of one or more payment accounts. The payment account information includes, for example, one or more of the following: a person's name or company name, a billing address, a login name, a password, an account number, an expiration date, a security code, a phone number, a bank associated with the payment account (e.g., an issuing bank), and a card network identifier. In some embodiments, the payment account information includes an image, such as a photo of a payment card (e.g., a photo taken by the device and / or received by the device). In some embodiments, the electronic device receives user input including at least some payment account information (e.g., receiving a credit card number, a debit card number, an account number or a shopping card number and an expiration date entered by the user). In some embodiments, the electronic device detects at least some payment account information from an image (e.g., of a payment card captured by a camera sensor of the device). In some embodiments, the electronic device receives at least some payment account information from another device (e.g., another user device or a server). In some embodiments, the electronic device receives payment account information from a server associated with another service (e.g., an application for renting or selling audio files and / or video files) for which the user or user device's account has previously made a purchase or for which payment account data has been identified.

[0230] In some embodiments, a payment account is added to an electronic device (e.g., devices 100, 300, and 500) so that the payment account information is securely stored on the electronic device. In some embodiments, after a user initiates such a process, the electronic device transmits the payment account information to a transaction coordination server, which then communicates with a server operated by the account's payment network (e.g., a payment server) to ensure the validity of the information. The electronic device is optionally configured to receive a script from the server that allows the electronic device to program the account's payment information onto a secure element.

[0231] In some embodiments, communication between devices 100, 300, and 500 facilitates transactions (e.g., general transactions or specific transactions). For example, a first electronic device (e.g., 100) may be used as a configuration device or a management device, and may send new or updated payment account data (e.g., information about a new account, updated information about an existing account, and / or a warning about an existing account) to a second electronic device (e.g., 500). As another example, a first electronic device (e.g., 100) may send data to a second electronic device, wherein the data reflects information about a payment transaction facilitated at the first electronic device. The information optionally includes one or more of the following: the payment amount, the account used, the time of purchase, and whether to change the default account. The second device (e.g., 500) optionally uses such information to update the default payment account (e.g., based on a learning algorithm or explicit user input).

[0232] Electronic devices (e.g., 100, 300, 500) are configured to communicate with each other via any of a variety of networks. For example, the devices communicate using a Bluetooth connection 608 (e.g., including a traditional Bluetooth connection or a Bluetooth low energy connection) or using a WiFi network 606. Communications between user devices are optionally adjusted to reduce the possibility of improper sharing of information between devices. For example, communication regarding payment information requires that the communicating devices be paired (e.g., associated with each other via explicit user interaction) or associated with the same user account.

[0233] In some embodiments, an electronic device (e.g., 100, 300, 500) is used to communicate with a point of sale (POS) payment terminal 600, which optionally supports NFC. The communication is optionally carried out using various communication channels and / or technologies. In some examples, an electronic device (e.g., 100, 300, 500) uses an NFC channel 610 to communicate with a payment terminal 600. In some embodiments, the payment terminal 600 uses a peer-to-peer NFC mode to communicate with an electronic device (e.g., 100, 300, 500). An electronic device (e.g., 100, 300, 500) is optionally configured to transmit a signal to the payment terminal 600, the signal including payment information of a payment account (e.g., a default account or an account selected for a specific transaction).

[0234] In some embodiments, continuing the transaction includes transmitting a signal including payment information of an account (such as a payment account). In some embodiments, continuing the transaction includes reconfiguring the electronic device (e.g., 100, 300, 500) to respond as a contactless payment card (such as an NFC-enabled contactless payment card) and then transmitting the credentials of the account via NFC to, for example, a payment terminal 600. In some embodiments, after transmitting the credentials of the account via NFC, the electronic device is reconfigured not to respond as a contactless payment card (e.g., authorization is required before being reconfigured again to respond as a contactless payment card via NFC).

[0235] In some embodiments, the generation and / or transmission of the signal is controlled by a security element in an electronic device (e.g., 100, 300, 500). Before issuing payment information, the security element optionally requires specific user input. For example, the security element optionally requires: detecting the electronic device being worn, detecting button presses, detecting password input, detecting touch, detecting one or more option selections (e.g., option selections received when interacting with an application), detecting fingerprint signatures, detecting voice or voice commands, and / or detecting gestures or movements (e.g., rotation or acceleration). In some embodiments, if a communication channel (e.g., NFC communication channel) with another device (e.g., payment terminal 600) is established within a defined time period from when the input is detected, the security element issues payment information so that it is transmitted to another device (e.g., payment terminal 600). In some embodiments, the security element is a hardware component that controls the release of security information. In some embodiments, the security element is a software component that controls the release of security information.

[0236] In some embodiments, the protocol associated with transaction participation depends on, for example, the device type. For example, the conditions for generating and / or transmitting payment information may be different for a wearable device (e.g., device 500) and a phone (e.g., device 100). For example, a generation condition and / or a transmission condition for a wearable device includes detecting that a button has been pressed (e.g., after security verification), while a corresponding condition for a phone does not require a button press, but requires detection of a specific interaction with an application. In some embodiments, conditions for transmitting and / or publishing payment information include receiving specific input on each of a plurality of devices. For example, the release of payment information optionally requires detection of a fingerprint and / or password at a device (e.g., device 100), as well as detection of a mechanical input (e.g., a button press) on another device (e.g., device 500).

[0237] The payment terminal 600 optionally uses the payment information to generate a signal for transmission to the payment server 604 to determine whether the payment is authorized. The payment server 604 optionally includes any device or system configured to receive the payment information associated with the payment account and determine whether the proposed purchase is authorized. In some embodiments, the payment server 604 includes a server of the issuing bank. The payment terminal 600 communicates directly with the payment server 604 or indirectly via one or more other devices or systems (e.g., a server of the acquiring bank and / or a server of the card network).

[0238] Payment server 604 optionally uses at least some of the payment information to identify the user account from a database of user accounts (e.g., 602). For example, each user account includes payment information. The account is optionally located by locating an account with specific payment information that matches the information from the POS communication. In some embodiments, payment is rejected when the provided payment information is inconsistent (e.g., the expiration date does not correspond to the credit card number, the debit card number, or the shopping card number does not correspond) or when no account includes payment information that matches the information from the POS communication.

[0239] In some embodiments, the user account data further identifies one or more constraints (e.g., credit limit); current or previous balances; previous transaction dates, locations, and / or amounts; account status (e.g., active or frozen), and / or authorization instructions. In some embodiments, the payment server (e.g., 604) uses such data to determine whether to authorize a payment. For example, the payment server denies payment when the purchase amount added to the current balance would cause the account limit to be exceeded, when the account is frozen, when the previous transaction amount exceeds a threshold, or when the number or frequency of previous transactions exceeds a threshold.

[0240] In some embodiments, the payment server 604 responds to the POS payment terminal 600 with an indication of whether the proposed purchase is authorized or rejected. In some embodiments, the POS payment terminal 600 transmits a signal to the electronic device (e.g., 100, 300, 500) to identify the result. For example, when the purchase is authorized (e.g., via a transaction coordination server that manages a transaction application on a user device), the POS payment terminal 600 sends a receipt to the electronic device (e.g., 100, 300, 500). In some cases, the POS payment terminal 600 presents an output (e.g., a visual output or an audio output) indicating the result. The payment may be transmitted to the merchant as part of the authorization process, or may be transmitted later.

[0241] In some embodiments, the electronic device (e.g., 100, 300, 500) participates in a transaction that is completed without involving the POS payment terminal 600. For example, upon detecting that the mechanical input has been received, the secure element in the electronic device (e.g., 100, 300, 500) releases the payment information to allow an application on the electronic device to access the information (e.g., and transmit the information to a server associated with the application).

[0242] In some embodiments, the electronic device (e.g., 100, 300, 500) is in a locked state or an unlocked state. In the locked state, the electronic device is powered on and is operable, but it is blocked from performing a predefined set of operations in response to user input. The predefined set of operations may include navigating between user interfaces, activating or deactivating a predefined set of functions, and activating or deactivating certain applications. The locked state can be used to prevent unconscious or unauthorized use of some functions of the electronic device, or to activate or deactivate some functions on the electronic device. In the unlocked state, the electronic device 100 is powered on and is operable, and is not blocked from performing at least a portion of a predefined set of operations that cannot be performed when in the locked state.

[0243] When the device is in the locked state, the device is said to be locked. In some embodiments, the device in the locked state can respond to a restricted set of user inputs, including inputs corresponding to attempts to convert the device to the unlocked state or inputs corresponding to shutting down the device.

[0244] In some embodiments, the security element is a hardware component (e.g., a secure microcontroller chip) configured to securely store data or algorithms. In some embodiments, the security element provides (or publishes) payment information (e.g., account number and / or transaction-specific dynamic security code). In some embodiments, the security element provides (or publishes) payment information in response to receiving authorization, such as user authentication (e.g., fingerprint authentication; password authentication; when the device is in an unlocked state, and optionally when the device has been continuously on the user's wrist since the device was unlocked by providing authentication credentials to the device, a double press of the hardware button is detected, wherein the device is determined to be continuously present on the user's wrist by periodically checking that the device is in contact with the user's skin). For example, the device detects a fingerprint at the device's fingerprint sensor (e.g., a fingerprint sensor integrated into a button). The device determines whether the fingerprint is consistent with the registered fingerprint. Based on determining that the fingerprint is consistent with the registered fingerprint, the security element provides (or publishes) payment information. Based on determining that the fingerprint is inconsistent with the registered fingerprint, the security element abandons providing (or publishing) payment information.

[0245] Attention now turns to these embodiments of user interfaces (“UIs”) and associated processes that are implemented on an electronic device such as portable multifunction device 100; device 300; or device 500; or the portable computing system 100 shown in FIGS. 1A through 1B of cross-referenced U.S. provisional patent application serial number 62 / 368,988, a portion of which is included in Appendix B; or the desktop computing system 200 shown in FIGS. 2A through 2D of cross-referenced U.S. provisional patent application serial number 62 / 368,988, a portion of which is included in Appendix B.

[0246] Figures 7A to 7D-10 illustrate exemplary user interfaces for managing access to credentials used in operation using an electronic device 700. In some embodiments, the electronic device 700 is a portable multifunction device 100; a device 300; a device 500; or a portable computing system 100 (e.g., a laptop computer) shown in Figures 1A to 1B of the cross-referenced U.S. Provisional Patent Application Serial No. 62 / 368,988 described above, a portion of which is included in Appendix B. In some embodiments, the electronic device 700 is a desktop computing system 200 shown in Figures 2A to 2D of the cross-referenced U.S. Provisional Patent Application Serial No. 62 / 368,988 described above, a portion of which is included in Appendix B. The electronic device 700 has a first display 702, a second display 704 (different from the first display), one or more input devices (e.g., a touch-sensitive surface), and a security element (e.g., a security element for securely storing credentials such as transaction credentials). The exemplary user interfaces depicted in these figures are used to illustrate the processes described below, including the processes in Figures 8A to 8B.

[0247] In some embodiments, the first display 702 of the electronic device 700 is the main display of the device. The second display 704 of the electronic device 700 is a dynamic function row, such as the dynamic function row 5002 described with reference to Figures 5I to 5N. In some embodiments, the second display 704 of the electronic device 700 (e.g., the dynamic function row) is separate from the physical keyboard 706A of the device (e.g., the second display 704 is included as part of a peripheral input mechanism). In some embodiments, the second display 704 is integrated with another input device such as a touchpad 706B.

[0248] The electronic device 700 includes a security element that stores credentials (e.g., transaction credentials) for an associated account registered on the device (e.g., a user account of a user of the device), wherein the account is enabled to authorize the security element to store and issue the credentials. In some examples, the credentials include payment information (e.g., credit card information, such as a credit card number and / or expiration date) stored in the security element of the electronic device 700. In some examples, authorization information (e.g., a registered fingerprint) is used to cause the security element to issue the credentials.

[0249] In some embodiments, the second display 704 (e.g., a dynamic function row) is paired with a security element, and therefore, the second display 704 is able and / or authorized to cause the security element to publish credentials stored in the security element. For example, the security element and the second display 704 are paired during the manufacturing process of the electronic device 700. When the second display 704 is paired with the security element, replacing the second display 704 or the security element in the electronic device 700 requires re-pairing the components to enable the security element to store and publish credentials (e.g., transaction credentials) again. In some embodiments, the second display 704 is paired with the security element, and the first display 702 is not paired with the security element, and therefore, the second display 704 is able and / or authorized to cause the security element to publish credentials stored in the security element, while the first display 702 is not able and is not authorized to publish credentials stored in the security element.

[0250] The electronic device 700 includes a fingerprint sensor 710. In some embodiments, the fingerprint sensor 710 is positioned adjacent to the second display 704, as depicted in FIG. 7A. In some embodiments, the fingerprint sensor 710 is a capacitive fingerprint reader. In some embodiments, the fingerprint sensor 710 is integrated into the hardware input element 708. In some embodiments, the hardware input element 708 is an input element used as a power button (e.g., for powering on and off the electronic device 700) and a fingerprint sensor (as described below with reference to FIG. 11A to FIG. 11M-4 and FIG. 12A to 12B). In some examples, the hardware input element 708 is an input element that is sensitive to changes in input intensity and is activated when pressed. In some examples, the hardware input element 708 is an intensity-sensitive button with an integrated intensity sensor, and when the intensity of the input on the intensity-sensitive button (e.g., characteristic intensity) exceeds the activation threshold, the intensity-sensitive button is activated. In some embodiments, the hardware input element 708 forms a continuous touch-sensitive area with the second display 704.

[0251] 7A to 7B illustrate a user interface 712 of an electronic device 700 when a user is attempting to perform an operation that requires authorization (e.g., a payment transaction). In FIG. 7A , the electronic device 700 displays a browser application 714 on the foreground of the user interface 712 displayed on the first display 702. In some examples, the user interface 712 includes an indication 712A of an account that is actively logged into the electronic device 700 (e.g., the name of the user associated with the account, in this example, the name is “J.Appleseed”). For example, a user (e.g., “J.Appleseed”) is browsing the Internet using a browser application 714 to purchase an item 714B (T-shirt) from an online store 714A. In this example, the active login account (e.g., the account of “J.Appleseed”) is an account that is enabled to authorize a secure element to issue credentials.

[0252] The electronic device 700 displays a payment enable indication 716 in the browser application 714 that is being used to perform an operation (e.g., perform a payment transaction). For example, as shown in FIG. 7A , the electronic device 700 displays a payment enable indication 716 (e.g., a “buy now” enable indication) corresponding to the operation (e.g., payment transaction) on the browser application 714. When the electronic device 700 detects the selection of the payment enable indication 716, it continues to perform the operation (e.g., continues to perform a payment transaction involving the purchase of the product 714B). In some embodiments, the payment enable indication 716 is part of and controlled by the application used to perform the operation (in this example, the browser application). In some embodiments, the payment enable indication 716 is controlled by the operating system of the electronic device 700 and is controlled separately from the application used to perform the operation.

[0253] FIG. 7B shows the electronic device 700 when the user selects the payment enable representation 716 to proceed with the operation (e.g., to continue to purchase goods 714B online). Therefore, the electronic device 700 receives a request for a voucher (e.g., a transaction voucher), which requires user authorization. In some examples, receiving the request for the voucher includes detecting activation of the payment enable representation 716 corresponding to the operation by one or more input devices (e.g., a computer mouse, touch input) (e.g., using a mouse cursor 718A). In some examples, the electronic device 700 receives a request for the voucher from a remote server. In some examples, the electronic device 700 receives the request from an application executed locally on the electronic device 700.

[0254] In some embodiments, in response to receiving a request for a credential (e.g., a transaction credential), the electronic device 700 determines whether the credential is stored in a security element. If the electronic device 700 determines that the credential is not stored in the security element, the electronic device instructs the user to register the credential on the electronic device (e.g., providing a payment account such as a credit card account to the electronic device 700), as described below with reference to Figures 9E-1 to 9E-4. In response to determining that the certificate is stored in the security element, the electronic device 700 determines whether to enable an account that actively logs into the electronic device (e.g., the "J.Appleseed" account indicated by indication 712A) to authorize operations that require authorization (e.g., payment transactions), such as by using fingerprint authorization or different types of authorization (e.g., password authorization, facial recognition authorization).

[0255] Figures 7C-1 to 7C-6 illustrate exemplary embodiments for authorizing operations when an account is configured for fingerprint authorization. Alternatively (or additionally), Figures 7D-1 to 7D-10 illustrate exemplary embodiments for authorizing operations when an account is not configured for fingerprint authorization.

[0256] Figures 7C-1 to 7C-6 show exemplary embodiments for authorizing an operation (e.g., a payment transaction) when an account (e.g., an actively logged-in account, such as a "J.Appleseed" account) is configured for fingerprint authorization. In response to receiving a request for a credential, the electronic device 700 determines whether the electronic device is configured to use one or more registered fingerprints to authorize the operation. In some embodiments, based on determining that the electronic device 700 is configured to use one or more registered fingerprints to authorize the operation, the electronic device requests fingerprint input to authorize the operation that requires authorization. In some examples, the electronic device 700 displays a visual indication 704A of one or more steps to be taken for the authorization operation on the second display 704. For example, the visual indication 704A includes an indication (e.g., text instructions and / or graphic instructions, pictorial instructions, and / or symbolic instructions) for the user to provide fingerprint input (e.g., "Touch to pay for an online store"), as shown in Figure 7C-1. In some examples, the visual indication 704A replaces content, such as content specific to the application being run (e.g., a browser application). For example, visual indication 704A replaces a "back" affordance, a "forward" affordance, a URL affordance, and a "favorites" affordance displayed on the second display.

[0257] In some embodiments, as shown in Figures 7C-1 to 7C-2, in response to receiving a request for a credential (e.g., a transaction credential), the electronic device 700 displays a parameter interface 720 (e.g., a payment slip) for an authorization operation (e.g., a payment transaction) on the first display 702. In some embodiments, the parameter interface 720 prompts the user to provide a fingerprint input for the authorization operation. In some examples, as shown by the transition of the parameter interface 720 in Figures 7C-1 to 7C-2, in response to receiving a request for a credential (e.g., a transaction credential), the parameter interface 720 slides into view on the first display 702 (e.g., from the edge of the first display). In some examples, the parameter interface 720 at least partially obscures a web page (e.g., an online store 714A) including a payment enable representation 716 displayed on the browser application 714. In some examples, the parameter interface 720 at least partially obscures the application that initiated the request for the credential.

[0258] 7C-2 shows a parameter interface 720 (e.g., a payment slip) that is fully visible on the first display 702. While the parameter interface 720 is displayed on the first display 702 (and / or in conjunction with displaying the parameter interface on the first display), the electronic device 700 displays on the second display 704 (e.g., simultaneously with displaying the parameter interface 720 on the first display 702) a visual indication 704A of one or more steps to be taken to authorize an operation (e.g., authorize a payment transaction).

[0259] In some examples, the parameter interface 720 (e.g., payment slip) is a user interface element controlled by the operating system of the electronic device 700, rather than an element controlled by an application (e.g., browser application 714) associated with the operation (e.g., payment transaction). In some examples, the parameter interface 720 is part of a first-party application provided by a provider of the operating system of the requesting device or a provider / manufacturer of the electronic device 700, where the first-party application is different from the application (e.g., browser application 714) associated with the operation. In some examples, the parameter interface 720 includes user-selectable options for modifying various aspects of the operation (e.g., modifying characteristics of the payment transaction), such as payment account options, shipping address options, shipping method options, and / or contact information options.

[0260] In some embodiments, as shown in FIG. 7C-2, the parameter interface 720 includes a first cancel enable indication 720C. In response to detecting the activation of the first cancel enable indication 720C, the electronic device 700 stops displaying the visual indication 704A of one or more steps to be taken for the authorization operation on the second display 704, and stops displaying the text indication 720B of one or more steps to be taken (e.g., without causing the release of credentials from the security element for use in the operation). Still as shown in FIG. 7C-2, in some examples, in response to receiving a request for a credential (e.g., a transaction credential), the electronic device 700 displays (e.g., simultaneously with the first cancel enable indication 720C) a second cancel enable indication 704C on the second display 704. In some examples, in response to detecting the activation of the second cancel enable indication 704C, the electronic device 700 stops displaying the visual indication 704A of one or more steps to be taken for the authorization operation on the second display 704, and stops displaying the text indication 720B of one or more steps to be taken (e.g., without causing the release of credentials from the security element for use in the operation).

[0261] In some embodiments, when the parameter interface 720 is displayed (and / or in conjunction with displaying the parameter interface), the electronic device 700 abandons the execution of any task in response to receiving a touch input at one or more locations on the touch-sensitive surface corresponding to the second display 704 that do not correspond to the second cancellation indication 704C or the fingerprint sensor 710 at the touch-sensitive surface corresponding to the second display 704. In some examples (e.g., when fingerprint authorization is enabled), the electronic device 700 disables touch input at one or more locations that do not correspond to the second cancellation indication 704C by abandoning the execution of any task in response to detecting a touch input at a location that does not correspond to the second cancellation indication 704C.

[0262] In some embodiments, while displaying the parameter interface 720 (and / or in conjunction with displaying the parameter interface), the electronic device 700 abandons performing any task upon detecting activation (e.g., pressing, pressing exceeding a strength threshold) of the hardware input element 708. For example, the electronic device 700 maintains an account (e.g., a "J.Appleseed" account) as an account actively logged into the electronic device 700, and abandons converting the active account state of the electronic device 700 to a second account (different from the first account) as an account actively logged into the electronic device 700 upon detecting activation (e.g., pressing) of the hardware input element, regardless of whether authorization (e.g., fingerprint authorization) has been received, as described in detail with respect to Figures 11A to 11M-4 and Figures 12A to 12B. In some examples, activation (e.g., pressing) (or merely activating) the hardware input element 708 does not cause any changes to the content displayed by the user interface 712 on the first display 702 or on the second display 704. In some examples, activation (eg, pressing) of hardware input element 708 does not cause electronic device 700 to shut down or power off, regardless of the duration of activation (eg, pressing) of hardware input element 708.

[0263] In some examples, the visual indication 704A on the second display 704 includes text instructions instructing the user to provide an authorized fingerprint by using the fingerprint sensor 710 (e.g., the visual indication 704A displays "Touch to pay to the online store", as shown in Figures 7C-1 to 7C-2). In some examples, the text instructions identify the merchant involved in the transaction (e.g., "online store"). In some examples, the visual indication 704A includes an animation 704B indicating the position of the fingerprint sensor 710 on the electronic device 700. For example, the animation 704B moves toward the fingerprint sensor 710 on the electronic device 700, such as an arrow pointing in the direction of the fingerprint sensor 710 and dynamically moving or extending linearly on an axis corresponding to the alignment of the arrow toward the position of the fingerprint sensor 710, as shown in the transition from Figure 7C-1 to Figure 7C-2. In some examples, the parameter interface 720 (e.g., a payment slip) on the first display 702 also provides a graphical non-textual indication 720A (e.g., a graphical depiction of a fingerprint) and a textual indication 720B (e.g., “Pay with fingerprint”) of one or more steps to be taken to authorize an operation (e.g., a payment transaction).

[0264] In some embodiments, the visual indication 704A displayed on the second display 704 is displayed at a secure location on the second display 704, where the first application (e.g., a browser application, an application requesting credentials) cannot affect the displayed content, and at the secure location, the second application (e.g., an operating system of the electronic device) can cause the display. In some examples, the first application (e.g., a browser application, an application requesting credentials) can cause the display at one or more locations other than the secure location on the second display 704. In some examples, the content that can be displayed at the secure location on the second display 704 is controlled by one or more processes of the operating system of the electronic device 700. In some examples, a third-party application (e.g., an application not provided by the manufacturer of the electronic device 700) cannot cause content to be displayed at a secure location on the second display 704. In some examples, the secure location on the second display 704 is secure, while one or more (or all) other locations on the second display 704 are unsafe. In some examples, the secure location is adjacent to the fingerprint sensor 710, without any unsafe intermediate display location.

[0265] FIG. 7C-3 illustrates a user 700A (e.g., “J.Appleseed”) associated with an account actively logged into the electronic device 700. In this example, the account of the J.Appleseed user is enabled to authorize the release of credentials from the secure element by providing input corresponding to a visual indication 704A of one or more steps to be taken to authorize an operation (e.g., a payment transaction). In some embodiments, as shown in FIG. 7C-3, receiving input corresponding to the visual indication 704A (e.g., a fingerprint input) includes detecting a fingerprint of the user by a fingerprint sensor 710.

[0266] In response to receiving a fingerprint input from user 700A, electronic device 700 determines whether the detected fingerprint input is consistent with authorization criteria. Based on determining that the detected fingerprint input is consistent with the authorization criteria, electronic device 700 causes a credential to be issued from the security element for use in an operation (e.g., payment information used in a payment transaction). In some embodiments, the authorization criteria include a criterion that is satisfied when the detected fingerprint is consistent with a registered fingerprint stored in the security element that is authorized to issue credentials from the security element.

[0267] In some examples, as shown in FIG. 7C-4 , before causing the credential to be issued from the secure element for use in an operation (e.g., a payment transaction), the electronic device 700 displays a visual indication 704A (e.g., “Processing”) on the second display 704 that notifies the user 700A that authorization is being processed (e.g., the electronic device is determining whether the detected fingerprint is consistent with the registered fingerprint). In some examples, the parameter interface 720 (e.g., a payment slip) displayed on the first display 702 also provides a graphical indication 720A and a text indication 720B (e.g., “Processing”) that notifies the user 700A that authorization is being processed (e.g., the electronic device 700 is determining whether the detected fingerprint is consistent with the registered fingerprint).

[0268] Based on determining that the detected fingerprint input from user 700A is consistent with the authorization criteria, the electronic device 700 causes the credential to be issued from the security element for use in the operation, and optionally, the credential is transmitted to the remote server for use in the operation. In some examples, in response to determining that the authorization (or operation) has been completed, the electronic device 700 notifies the user of the completion of the authorization by displaying a visual indication 704A (e.g., "end", "complete") on the second display 704 as shown in Figure 7C-5. In some examples, the electronic device 700 also displays (e.g., simultaneously displays) a graphical indication 702A and a text indication 702B (e.g., "end", "complete") on the first display 702 to notify the user 700A that the authorization is complete.

[0269] In some embodiments, as shown in FIG. 7C-6, based on determining that the detected fingerprint is inconsistent with the registered fingerprint (e.g., the detected input is inconsistent with the authorization criteria), the electronic device 700 abandons the issuance of credentials from the security element for use in the operation (e.g., abandons the completion of the payment transaction, abandons the transmission of payment information for use in the operation). In some examples, the electronic device 700 also displays a visual indication 704A (e.g., "Try again") on the second display 704, which visual indication requests the user 700A to provide input again (e.g., fingerprint input, as depicted in FIG. D-3 to FIG. 7C-4). In some examples, the parameter interface 720 (e.g., a payment slip) also provides a graphical indication 720A and a text indication 720B (e.g., "Try again") (e.g., displayed simultaneously), which requests the user 700A to try again. In some examples, the indications 720A and 720B are not the same or the same. In some examples, if the new attempt is successful, the electronic device 700 displays a visual indication 704A (e.g., “End,” “Complete”) on the second display 704 that notifies the user that the authorization is complete, as shown in FIG. 7C-5 and described with reference to FIG. 7C-5.

[0270] Figures 7D-1 to 7D-10 show exemplary embodiments for authorizing operations that require authorization (e.g., payment transactions) when an account (e.g., an actively logged-in account) is not configured for fingerprint authorization. In response to receiving a request for a credential, the electronic device 700 determines whether the electronic device is configured to use one or more registered fingerprints to authorize the operation (e.g., whether the device is configured for fingerprint authorization). In some embodiments, based on determining that the electronic device 700 is not configured for fingerprint authorization, the electronic device requests a password input to authorize the operation (e.g., the device is in password authorization mode). Therefore, in some examples, the electronic device 700 displays a visual indication 704A on the second display 704, which includes an indication (e.g., text and / or graphic / illustrative / symbolic instruction) prompting the user to activate the authorization indication 704D displayed on the second display 704, as shown in Figure 7D-1. In some examples, the electronic device displays a corresponding indication on the first display. In some examples, the indication on the first display is different or the same as the indication 704A on the second display.

[0271] In the password authorization mode, the authorization criteria include: criteria that are satisfied when activation of the authorization enable indication 704D is detected (e.g., at a secure location on the second display 704); and criteria that are satisfied when a received sequence of one or more characters (e.g., a password entered by a user) is consistent with a registered password (e.g., a password stored on the electronic device) that is authorized to issue credentials from the secure element of the electronic device 700. In some examples, the authorization criteria include additional criteria that are satisfied when activation of the authorization enable indication 704D is detected before the character sequence is received. For example, because the fingerprint has not yet been registered in the electronic device 700, or because the user of the device has prohibited the use of fingerprint input for transaction authorization, the authorization criteria are satisfied when activation of the authorization enable indication 704D is detected before the character sequence is received. In some examples, the electronic device displays an indication or arrow (e.g., an animation) pointing to the authorization enable indication.

[0272] In some embodiments, one or more input devices of the electronic device 700 include a keyboard that is not paired with a secure element (e.g., the keyboard is an external keyboard such as connected to the device via USB and is therefore not capable of and authorized to release credentials stored in the secure element). In some examples, a received character sequence (e.g., a password input) is passed from a first processor associated with the keyboard 706A to a second processor associated with the secure element and the second display 704. Additional details related to the technology are described throughout the cross-referenced U.S. patent application Ser. No. 15 / 256,959 included in Appendix A, particularly in FIG. 3 and in paragraphs

[0047] to

[0048] ,

[0080] , and

[0094] .

[0273] In some embodiments, as shown in Figures 7D-1 to 7D-2, in response to receiving a request for a credential (e.g., a transaction credential), the electronic device 700 displays a parameter interface 720 (e.g., a payment slip) for completing an operation (e.g., a payment transaction) on the first display 702, and the parameter interface prompts the user to provide a password input to authorize the operation. In some embodiments, as shown by the transition of the parameter interface 720 in Figures 7D-1 to 7D-2, in response to receiving a request for a credential (e.g., a transaction credential), the parameter interface 720 slides into view on the first display 702 (e.g., from the edge of the first display). In some examples, the parameter interface 720 at least partially obscures a web page (e.g., an online store 714A) displayed on the browser application 714 that includes a payment enabling representation 720.

[0274] 7D-2 shows a parameter interface 720 (e.g., a payment slip) that is fully visible on the first display 702. While the parameter interface 720 is displayed on the first display 702 (and / or in conjunction with displaying the parameter interface on the first display), the electronic device 700 displays a visual indication 704A on the second display 704 of one or more steps to be taken to authorize an operation (e.g., a payment transaction).

[0275] In some embodiments, the parameter interface 720 (e.g., a payment form) is a user interface element controlled by the operating system, rather than an element of an application (e.g., browser application 714) associated with the operation (e.g., a payment transaction). In some examples, the parameter interface 720 is part of a first-party application provided by a provider of the operating system of the requesting device (e.g., a provider of the electronic device 700), where the first-party application is different from the application (e.g., browser application 714) associated with the operation. In some examples, the parameter interface 720 includes user-selectable options for modifying various aspects of the operation (e.g., modifying characteristics of the payment transaction), such as payment account options, shipping address options, shipping method options, and / or contact information options.

[0276] In some embodiments, as shown in FIG. 7D-2, the parameter interface 720 includes a first cancel enable indication 720C, which, when activated, causes the electronic device 700 to stop displaying a visual indication 704A of one or more steps to be taken for the authorization operation on the second display 704 (e.g., without causing the release of credentials from the security element for use in the operation). Therefore, if the electronic device 700 detects activation of the first cancel enable indication 720C via one or more input devices, the electronic device stops displaying a visual indication 704A of one or more steps to be taken for the authorization operation on the second display 704 (e.g., without causing the release of credentials from the security element for use in the operation).

[0277] Still as shown in FIG. 7D-2, in some examples, in response to receiving a request for a credential (e.g., a transaction credential), the electronic device 700 displays (e.g., simultaneously with the first cancel enable indication 720C) a second cancel enable indication 704C on the second display 704. In some examples, activation of the second cancel enable indication 704C causes the electronic device 700 to stop displaying a visual indication 704A of one or more steps to be taken for the authorization operation on the second display 704 (e.g., without causing the credential to be released from the security element for use in the operation). Therefore, if the electronic device 700 detects activation of the second cancel enable indication 704C via one or more input devices, the electronic device stops displaying a visual indication 704A of one or more steps to be taken for the authorization operation (e.g., without causing the credential to be released from the security element for use in the operation). In some examples, in response to detecting activation of the first cancel enable indication 720C or the second cancel enable indication 704C, the electronic device stops displaying the indication 720B on the first display or stops displaying the visual indication 704A on the second display.

[0278] In some embodiments, when the parameter interface 720 is displayed (and / or in conjunction with displaying the parameter interface), the electronic device 700 abandons the execution of any task in response to receiving a touch input at one or more locations on the touch-sensitive surface corresponding to the second display 704 that do not correspond to the second cancellation indication 704C or the fingerprint sensor 710 at the touch-sensitive surface corresponding to the second display 704. In some examples, the electronic device 700 disables the touch input at one or more locations that do not correspond to the second cancellation indication 704C by abandoning the execution of any task in response to detecting the touch input at a location that does not correspond to the second cancellation indication 704C. In some examples (e.g., when fingerprint authorization is not enabled), disabling the touch input at one or more locations that do not correspond to the second cancellation indication 704C includes abandoning any task in response to detecting the touch input at a location that does not correspond to the second cancellation indication 704C and the authorization indication 704D, which is displayed at a secure location on the second display 704. In some examples (eg, when fingerprint authorization is not enabled), electronic device 700 prohibits processing touch input at a location that does not correspond to second cancel-indication 704C or authorization-indication 704D.

[0279] In some examples, visual indication 704A includes text instructions that prompt the user to activate authorization enable indication 704D to proceed with the operation. In some examples, visual indication 704A includes an animation indicating the location of authorization enable indication 704D on electronic device 700. For example, the animation moves toward authorization enable indication 704D on electronic device 700, such as an arrow pointing in the direction of authorization enable indication 704D and moving dynamically and linearly on an axis corresponding to the alignment of the arrow toward the location of authorization enable indication 704D. In some examples, parameter interface 720 (e.g., payment slip) on first display 702 also provides graphical indication 720A and text indication 720B of one or more steps to be taken for authorization operation (e.g., payment transaction).

[0280] In some embodiments, the visual indication 704A is displayed at a secure location on the second display 704, where the first application (e.g., the application requesting the credential) cannot cause a display, but where the second application (e.g., the operating system of the electronic device 700) can cause a display. In some examples, the first application (e.g., the application requesting the credential) can cause a display at one or more locations on the second display 704 other than the secure location. In some examples, the content that can be displayed at the secure location on the second display 704 is controlled by one or more processes of the operating system of the electronic device 700. In some examples, a third-party application (e.g., an application not provided by the manufacturer of the electronic device 700) cannot cause content to be displayed at the secure location on the second display 704. In some examples, the secure location on the second display 704 is secure, while one or more (or all) other locations on the second display 704 are unsecure.

[0281] 7D-2 shows a parameter interface 720 (e.g., a payment slip) that is fully visible on the first display 702. While displaying the parameter interface 720 (and / or in conjunction with displaying the parameter interface), the electronic device 700 displays on the second display 704 (e.g., simultaneously with displaying the parameter interface 720 on the first display) a visual indication 704A of one or more steps to be taken to authorize an operation (e.g., a payment transaction).

[0282] Figure 7D-3 shows that user 700A (e.g., "J.Appleseed") provides input corresponding to visual indication 704A of one or more steps (e.g., activates authorization enable indication 704D). In some embodiments, as shown in Figure 7D-3, receiving input corresponding to visual indication 704A of one or more steps to be taken to authorize an operation (e.g., a payment transaction) includes detecting activation of authorization enable indication 704D by user 700A. In some examples, as shown in Figures 7D-4 to 7D-5, after detecting activation of authorization enable indication 704D by user 700A, parameter interface 720 shrinks to display less information and displays prompt 720D requesting the user to provide a password. In some examples, after detecting activation of the authorization enable indication, the electronic device abandons providing options for changing operation details (such as the payment account to be used, shipping address, shipping method, etc.). In some examples, after detecting activation of authorization affordance 704D by user 700A, visual indication 704A requests the user to provide a password (e.g., visual indication 704A displays “Enter password to complete purchase”). In some examples, visual indication 704A for providing a password is displayed on second display 704 in a secure location.

[0283] As shown in Figure 7D-6, receiving input corresponding to visual indication 704A includes receiving a character sequence representing a password by one or more input devices (e.g., keyboard 706A or an external keyboard connected to the electronic device). For example, the character sequence is a sequence of alphanumeric characters and / or symbol characters representing the password. In some examples, the character sequence is received via typing input on keyboard 706A of electronic device 700. In some examples, the keyboard is a hardware keyboard (e.g., a mechanical keyboard) separated from the first display 702 and the second display 704. In some examples, the keyboard is a soft keyboard displayed on a portion of the first display 702 or a portion of the second display 704.

[0284] In some examples, the parameter interface 720 includes a completion enable indication 720E. As shown in Figures 7D-7, once the user completes entering a character sequence (e.g., a password) on one or more input devices (e.g., a keyboard) of the electronic device, the electronic device 700 detects the user's activation 718B of the completion enable indication 720E. In response to detecting that the user 700A activates the completion enable indication 720E for an authorization operation (e.g., a payment transaction), the electronic device 700 determines whether the detected character sequence (e.g., the entered password) is consistent with the authorization criteria. Based on determining that the detected character sequence (e.g., the entered password) is consistent with the authorization criteria, the electronic device 700 causes the release of credentials from the security element for use in the operation (e.g., payment information used in a payment transaction). In some embodiments, the authorization criteria include a standard that is met when the detected character sequence (e.g., the entered password) is consistent with a registered character sequence (e.g., a registered password) stored in the security element that is authorized to release credentials from the security element.

[0285] In some examples, as shown in Figures 7D-8, before causing the credential to be issued from the security element for use in an operation (e.g., a payment transaction), the electronic device 700 displays a visual indication 704A (e.g., "Processing") on the second display 704, which notifies the user 700A that the authorization is being processed (e.g., the electronic device is determining through the security element whether the entered password is consistent with the registered password). In some examples, the parameter interface 720 (e.g., a payment slip) displayed on the first display 702 also provides a graphical non-textual indication 720A and a textual indication 720B (e.g., "Processing"), which notifies the user 700A that the authorization is being processed (e.g., the electronic device is determining whether the entered password is consistent with the registered password).

[0286] If the electronic device 700 determines that the character sequence (e.g., the input password) input by the user 700A is consistent with the authorization standard (e.g., the registered password), the authorization is completed. In some examples, as shown in Figures 7D-9, in response to determining that the authorization is completed, the electronic device 700 displays a visual indication 704A (e.g., "end", "complete") on the second display 704, and the visual indication notifies the user that the authorization is completed. In some examples, the electronic device 700 also displays a graphic indication 720A and a text indication 720B (e.g., "end", "complete") on the first display 702, and the graphic indication and text indication notify the user 700A that the authorization is completed. Based on determining that the detected character sequence (e.g., the detected password) is consistent with the authorization standard (e.g., the registered password), the electronic device 700 causes the credential to be issued from the security element for use in an operation (e.g., a payment transaction).

[0287] In some embodiments, as shown in FIG. 7D-10, based on determining that the entered character sequence (e.g., a password provided by user 700A, as depicted in FIG. 7D-4 to FIG. 7D-7) is inconsistent with the registered password, the electronic device 700 abandons causing the credential to be issued from the security element for use in the operation (e.g., abandons completing the payment transaction). In some examples, the electronic device 700 also displays a visual indication 704A (e.g., "Try Again") on the second display 704, which notifies the user 700A that the authorization was unsuccessful and therefore enters the character sequence (e.g., password) again. In some examples, the parameter interface 720 (e.g., a payment slip) provides a cleared password field, which instructs the user 700A to enter the character sequence (e.g., password) again. In some examples, if after repeated attempts, the electronic device 700 determines that the entered character sequence (e.g., the detected password) is consistent with the registered character sequence (e.g., the registered password), the electronic device displays a visual indication 704A (e.g., "End", "Complete") on the second display 704, which notifies the user that the authorization is complete, as shown in FIG. 7D-9.

[0288] In some embodiments, one or more input devices of the electronic device 700 include one or more cameras. In some embodiments, the one or more cameras include one or more cameras with depth sensing capabilities. In some embodiments, the one or more cameras include one or more camera sensors. In some embodiments, the one or more cameras include multiple cameras capable of generating depth maps using parallax effects.

[0289] In some embodiments, after receiving a request for a credential (e.g., as shown in FIG. 7B ), the electronic device 700 requests a biometric identifier to authorize an operation that requires authorization. In some embodiments, after receiving a request for a credential (e.g., as shown in FIG. 7B ), and based on determining that the electronic device 700 is not configured to use one or more registered fingerprints to authorize an operation (e.g., a payment transaction), the electronic device 700 requests a biometric identifier to authorize an operation. In some embodiments, after receiving a request for a credential (e.g., as shown in FIG. 7B ), and based on determining that the electronic device 700 is configured to use one or more registered fingerprints to authorize an operation (e.g., a payment transaction), the electronic device 700 requests a biometric identifier (as a supplement or alternative to requesting fingerprint input) to authorize an operation. In some embodiments, the electronic device 700 is configured to use a biometric identifier to authorize an operation (e.g., a payment transaction), and the method is the primary authorization method. In some examples, the biometric identifier is a facial identifier or an eye-based identifier (such as iris recognition or retinal scanning) detected using one or more sensors or cameras of the electronic device 700.

[0290] In some embodiments, if the electronic device 700 requests biometrics to authorize an operation, the visual indication of one or more steps to be taken to authorize the operation includes an indication of requesting a biometric identifier (e.g., a facial identifier, and / or an eye-based identifier, such as an iris recognition or a retinal scan). The electronic device 700 receives a biometric identifier corresponding to the visual indication of the one or more steps by detecting the biometric identifier (e.g., a biometric identifier of a user) using one or more cameras. In some examples, the biometric identifier is one or more images captured using one or more cameras (e.g., a camera sensor). In some examples, the electronic device 700 uses one or more captured images to generate a depth map (or multiple depth maps) corresponding to one or more physical features of the user (such as, facial features of the user).

[0291] In some embodiments, if the electronic device 700 requests a biometric identification to authorize an operation (e.g., a payment transaction), the authorization criteria include criteria that are satisfied when the detected biometric identification (e.g., the user's biometric identification) is consistent with a registered biometric identification authorized to issue credentials from the secure element. In some examples, the authorization criteria include criteria that are satisfied when a depth map generated corresponding to one or more physical features of the user (e.g., facial structure or other features) is consistent with registered biometric depth map information authorized to issue credentials from the secure element (e.g., a registered depth map corresponding to a registered user).

[0292] Figures 8A to 8B are flowcharts according to some embodiments, which illustrate a method for using an electronic device (e.g., device 700) to authorize the release of credentials used in an operation requiring authorization. In some embodiments, method 800 is performed at a device (e.g., 100; 300; 500; cross-referenced U.S. Provisional Patent Application Serial No. 62 / 368,988 portable computing system 100, a portion of which is included in Appendix B; cross-referenced U.S. Provisional Patent Application Serial No. 62 / 368,988 desktop computing system 200, a portion of which is included in Appendix B) having a first display, a second display (different from the first display), a security element, and one or more input devices, wherein one or more input devices optionally include a touch-sensitive surface, a fingerprint sensor, a keyboard, and / or one or more cameras. Some operations in method 800 are optionally combined, the order of some operations is optionally changed, and some operations are optionally omitted.

[0293] As described below, method 800 provides an intuitive way to authorize the release of credentials used in operations requiring authorization. The method reduces the cognitive burden on users when managing access to credentials used in operations requiring authorization, thereby creating a more efficient human-computer interface. For battery-powered computing devices, users are enabled to manage access to credentials used in operations more quickly and efficiently, which saves power and increases the time interval between battery charges.

[0294] In some embodiments, method 800 is performed on a device having a second display (e.g., display 704) paired with a security element. For example, the security element and the second display (e.g., 704) have been paired during the manufacturing process, so that replacing the security element or the second display (e.g., 704) requires re-pairing of the remaining and replaced components to meet the criteria of the authorization criteria. In some embodiments, the first display (e.g., 702) of the electronic device is not paired with the security element and is therefore unable and unauthorized to release credentials stored in the security element.

[0295] In some embodiments, prior to receiving the request for the credential, the electronic device (e.g., 700) displays (802) on the first display (e.g., 702) a payment enablement representation (e.g., 716) corresponding to the operation requiring authorization (e.g., a "Buy Now" enablement representation). In some examples, the payment enablement representation (e.g., 716) is displayed by a first application (e.g., a browser application).

[0296] An electronic device (e.g., 700) receives (806) a request for credentials (e.g., transaction credentials) for an operation requiring authorization. In some examples, the request is received from a remote server. In some examples, the request is received from a locally executed application. In some embodiments, receiving the request for the credentials includes detecting (804) activation of a payment enablement representation (e.g., 716) corresponding to the operation requiring authorization by one or more input devices (e.g., a computer mouse, touch input).

[0297] In some embodiments, the credential includes payment information stored in the security element. In some examples, the credential includes authorization information (e.g., an authorization fingerprint is used to cause the security element to issue the credential from the security element of the electronic device (e.g., 700)).

[0298] In response to receiving a request for credentials (e.g., transaction credentials): the electronic device (e.g., 700) displays (808) on a first display (e.g., 702) a parameter interface (e.g., 720) for an operation requiring authorization. In some examples, the parameter interface (e.g., 720) is a payment slip. In some examples, the payment slip is a user interface of an operating system, not a first application. In some examples, the payment slip is part of a first-party application provided by a provider of an operating system of the requesting device, where the first-party application is different from the first application. In some examples, the payment slip includes user-selectable options for a payment transaction, such as a payment account option, a shipping address option, a shipping method option, and a contact information option. In some examples, in response to activation of a payment-enabling representation (e.g., 716), the payment slip slides into the display (e.g., slides into a view on one or more displays). In some examples, the payment slip at least partially obscures a webpage including the payment-enabling representation. Thus, the electronic device prompts the user to take action to approve the operation by displaying the parameter interface.

[0299] In some embodiments, a parameter interface (e.g., 720) for an operation requiring authorization includes a first cancel-enabling indication (e.g., 720C) that, when activated, causes the electronic device (e.g., 700) to stop displaying visual indications (e.g., 704A) of one or more steps to be taken to authorize the operation on a second display (e.g., 704) (e.g., without causing credentials to be released from a secure element for use in the operation). In some examples, based on detecting activation of the first cancel-enabling indication (e.g., 720C) via one or more input devices, the electronic device (e.g., 700) stops displaying visual indications (e.g., 704A) of one or more steps to be taken to authorize the operation (e.g., without causing credentials to be released from a secure element for use in the operation).

[0300] In some embodiments, in response to receiving a request for a credential (e.g., a transaction credential), the electronic device displays on a second display (e.g., 704) (e.g., simultaneously with a first cancel-enable indication (e.g., 720C)) a second cancel-enable indication (e.g., 704C), which, when activated, causes the electronic device (e.g., 700) to stop displaying on the second display (e.g., 704) visual indications (e.g., 704A) of one or more steps to be taken to authorize an operation (e.g., without causing the credential to be released from the secure element for use in the operation). In some examples, based on detecting activation of the second cancel-enable indication (e.g., 704C) via one or more input devices, the electronic device (e.g., 700) stops displaying visual indications (e.g., 704A) of one or more steps to be taken to authorize an operation (e.g., without causing the credential to be released from the secure element for use in the operation).

[0301] In some embodiments, the second display (e.g., 704) and the touch-sensitive surface form a touch-sensitive display, and when a parameter interface (e.g., 720) for an operation requiring authorization is displayed (and / or in combination with displaying the parameter interface), the electronic device (e.g., 700) responds to receiving a touch input at one or more locations on the touch-sensitive surface corresponding to the second display (e.g., 704) that do not correspond to the second cancellation indication (e.g., 704C) at the touch-sensitive surface corresponding to the second display (e.g., 704), and abandons the execution of any function. By reducing the locations where the received input acts, the electronic device reduces the possibility of receiving unintentional and unexpected input (thereby reducing the possibility that the electronic device performs unnecessary operations), and thereby improves the human-computer interface. In some examples (e.g., when fingerprint authorization is enabled), the electronic device (e.g., 700) disables the touch input at one or more locations that do not correspond to the second cancellation indication (e.g., 704C of Figure 7C-2) by abandoning the execution of any function in response to detecting a touch input at a location that does not correspond to the second cancellation indication (e.g., 704C of Figure 7C-2). In some examples (e.g., when fingerprint authorization is not enabled), the electronic device (e.g., 700) disables touch input at one or more locations that do not correspond to the second cancel-enable indication (e.g., 704C of FIG. 7D-2), including giving up executing any function in response to detecting a touch input at a location that does not correspond to the second cancel-enable indication (e.g., 704C of FIG. 7D-2) and the authorization enable indication (704D of FIG. 7D-2). In some examples, the electronic device (e.g., 700) disables processing of touch input at locations that do not correspond to the second cancel-enable indication (e.g., 704C) and the authorization enable indication. By reducing the locations where received input acts, the electronic device reduces the likelihood of receiving unintentional and unexpected input (thereby reducing the likelihood that the electronic device performs unnecessary operations), and thereby improves the human-computer interface.

[0302] While displaying the parameter interface (e.g., 720) (and / or in conjunction with displaying the parameter interface), the electronic device (e.g., 700) displays (810) on the second display (e.g., 704) (e.g., simultaneously with displaying the parameter interface (e.g., 720) on the first display (e.g., 702)) a visual indication (e.g., 704A) of one or more steps to be taken for the authorization operation. By simultaneously seeing the parameter interface displayed on the first display and the visual indication displayed on the second display, the user gains additional confidence that the parameter interface is authentic (e.g., responsive to a request for credentials) and that the parameter interface is therefore secure (e.g., securely displayed by the device's operating system, rather than by a rogue process), thereby improving the human-computer interface. In some examples, the visual indication of one or more steps (e.g., 704A of FIG. 7C-2 ) instructs the user to provide an authorization fingerprint by using the fingerprint sensor (e.g., 710). In some examples, the visual indication is animated (e.g., 704B). In some examples, the visual indication points (e.g., 704B) in the direction of the fingerprint sensor (e.g., 710). Thus, the electronic device indicates to the user the status of the device and the input (eg, the type of input) required to proceed with the operation by displaying visual indications of one or more steps.

[0303] In some embodiments, a visual indication (e.g., 704A) of one or more steps to be taken for the authorization operation displayed on the second display (e.g., 704) is displayed at a secure location on the second display (e.g., 704) where the first application (e.g., the application requesting the credential) cannot cause the display and where the second application (e.g., the operating system of (e.g., electronic device 700)) can cause the display. By displaying the visual indication at a secure location on the second display, the user gains additional confidence that the initiation of the display is a genuine request for the credential (e.g., in response to a genuine request for the credential) and that the corresponding parameter interface is therefore secure (e.g., securely displayed by the device's operating system, not by a rogue process), thereby improving the human-machine interface. In some examples, the first application (e.g., the application requesting the credential) can cause the display at one or more locations on the second display (e.g., 704) other than the secure location. In some examples, at the secure location, only the second application can cause the display and the content display is controlled by one or more processes of the operating system of the electronic device (e.g., 700). In some examples, third-party applications (e.g., applications not provided by the manufacturer of electronic device 700) are unable to cause content to be displayed at a secure location on the second display (e.g., 704). In some examples, the secure location on the second display (e.g., 704) is secure, while one or more (or all) other locations of the second display (e.g., 704) are unsecure.

[0304] In some embodiments, the electronic device determines whether the electronic device (e.g., 700) is configured to use one or more registered fingerprints to authorize an operation.

[0305] In some embodiments, based on determining (812) that the electronic device (e.g., 700) is configured to use one or more registered fingerprints to authorize an operation, a visual indication of one or more steps to be taken for the authorization operation (e.g., 704A of FIG. 7C-2 ) includes instructions (e.g., text and / or graphic / illustrative / symbolic instructions) for the user to provide fingerprint input. Thus, the electronic device notifies the user of the current configuration of the device and prompts the user to provide appropriate input by checking the current confirmation and displaying the fingerprint input indication.

[0306] In some embodiments, based on determining (816) that the electronic device (e.g., 700) is not configured to use one or more registered fingerprints (and / or biometric information) to authorize an operation, a visual indication of one or more steps to be taken for the authorization operation (e.g., 704A of FIG. 7D-2 ) includes an indication for the user to activate an authorization enable indication (e.g., 704D of FIG. 7D-2 ) for initiating a process of receiving a password. Thus, the electronic device informs the user of the current configuration of the device and prompts the user to provide appropriate input by checking the current confirmation and displaying an indication of a password input.

[0307] In some embodiments, one or more input devices include a fingerprint sensor (e.g., 710, a capacitive fingerprint reader, a button that functions as a power button and a fingerprint sensor, as described with reference to Figures 11A to 11M-4), and the visual indication (e.g., 704A of Figure 7C-2) includes an indication requesting fingerprint input. In some embodiments, the electronic device (e.g., 700) receives input corresponding to the visual indication of one or more steps (e.g., 704A of Figure 7C-2) including detecting (814) a fingerprint by the fingerprint sensor (e.g., 710), and the authorization criteria include a criterion that is satisfied when the detected fingerprint is consistent with a registered fingerprint that is authorized to issue credentials from the security element. By including a criterion that is satisfied when the detected fingerprint is consistent with a registered fingerprint, the electronic device provides additional security that helps prevent unauthorized users from authorizing operations, thereby making the system more secure.

[0308] In some embodiments, the visual indication (e.g., 704A of FIG. 7C-2 ) includes an animation (e.g., 704B of FIG. 7C-2 ) indicating the location of the fingerprint sensor (e.g., 710) on the electronic device 700. For example, the visual indication is an animation (e.g., 704B of FIG. 7C-2 ) moving toward the fingerprint sensor (e.g., 710) on the device, such as an arrow (e.g., 704B of FIG. 7C-2 ) pointing in the direction of the fingerprint sensor (e.g., 710) and moving linearly on an axis corresponding to the alignment of the arrow (e.g., 704B of FIG. 7C-2 ). Thus, in the case where the device includes multiple input devices, by displaying an animation indicating the location of the device configured to receive input, the electronic device prompts the user to provide input using a particular input device (e.g., fingerprint sensor).

[0309] In some embodiments, the authorization criteria include: criteria that are satisfied when activation of an authorization enable indication (e.g., 704D of FIG. 7D-2 ) displayed on a second display (e.g., 704, at a secure location on the second display) is detected; and criteria that are satisfied when a sequence of one or more characters received is consistent with a password authorized to issue credentials from a secure element (e.g., a password stored on the device). By displaying the authorization enable indication on the second display, the user gains additional confidence that the display of the enable indication is caused by a genuine request for credentials (e.g., in response to a genuine request for credentials) and that the corresponding parameter interface is therefore secure (e.g., securely displayed by the device's operating system, rather than by a rogue process), thereby improving the human-machine interface. In addition, when the authorization enable indication is displayed at a secure location on the second display, an additional level of security is achieved, which provides the user with additional confidence that the request for credentials is genuine. In some examples, (e.g., because the fingerprint has not been enrolled on the device or because the user has disabled use of fingerprint for transaction authorization) the authorization criteria include additional criteria that are met when activation of the authorization enable indication (e.g., 704D of FIG. 7D-2) is detected before the character sequence is received.

[0310] In some embodiments, an electronic device (e.g., 700) displays (e.g., simultaneously with visual indications of one or more steps (e.g., 704A of FIG. 7D-2)) an authorization indication (e.g., 704D of FIG. 7D-2) on a second display (e.g., 704). The simultaneous display of one or more steps with the authorization indication allows a user to quickly understand the required steps and the location where the required steps should be performed, thereby improving the human-computer interface. For example, the authorization indication (e.g., 704D of FIG. 7D-2) is displayed at a secure location on the display, as described below. In some embodiments, the visual indication of one or more steps (e.g., 704A of FIG. 7D-2) includes an indication requesting activation of the authorization indication (e.g., 704D of FIG. 7D-2) displayed on the second display (e.g., 704).

[0311] The electronic device (eg, 700 ) receives ( 822 ) input corresponding to the visual indication (eg, 704A) of the one or more steps using one or more input devices.

[0312] In some embodiments, the electronic device (e.g., 700) receives input corresponding to a visual indication of one or more steps (e.g., 704A of FIG. 7D-2) including detecting (818) activation of an authorization enable representation (e.g., 704D of FIG. 7D-2). In some examples, after detecting activation of an authorization enable representation (e.g., 704D of FIG. 7D-2) displayed on a second display (e.g., 704), the electronic device (e.g., 700) prompts the user to provide a password. In some examples, the prompt for providing a password is displayed simultaneously on the first display (e.g., 702) and the second display (e.g., 704). In some examples, the prompt for providing a password is displayed on the second display (e.g., 704) at a secure location. Therefore, by displaying the prompt at a secure location, the electronic device confirms to the user that the request is credible and the proposed operation is safe.

[0313] In some embodiments, the electronic device (e.g., 700) receiving input corresponding to the visual indication (e.g., 704A) of one or more steps also includes receiving (820) a character sequence (e.g., a sequence of alphanumeric characters and / or symbol characters) by one or more input devices (e.g., a keyboard) (e.g., after detecting activation of the authorization enable representation (e.g., 704D), after prompting the user to provide a password). By first detecting activation of the authorization enable representation before prompting (and receiving) the character sequence (e.g., a password), the electronic device reduces the risk of the user providing the character sequence when the prompt for the character sequence is performed by an unethical process (such as a process intended to steal the user's password). In some examples, the electronic device (e.g., 700) includes a keyboard (e.g., 706A), and the character sequence is received via typing input on the keyboard (e.g., 706A) of the device. In some examples, the keyboard (e.g., 706A) is a hardware keyboard separate from the first display (e.g., 702) and the second display (e.g., 704). In some examples, the keyboard is a soft keyboard displayed on a portion of the first display (e.g., 702) or a portion of the second display (e.g., 704).

[0314] In some embodiments, one or more input devices include a keyboard (e.g., 706A) that is not paired with a secure element (e.g., the keyboard is an external keyboard attached to the device and is therefore not capable of and authorized to issue credentials stored in the secure element), and the received character sequence is passed from a first processor associated with the keyboard to a second processor associated with the secure element and a second display (e.g., 704). Additional details related to this technology are described throughout cross-referenced U.S. patent application Ser. No. 15 / 256,959 (included herein as Appendix A), particularly in FIG. 3 and paragraphs

[0047] to

[0048] ,

[0080] , and

[0094] .

[0315] In some embodiments, a fingerprint sensor (e.g., 710) is integrated into a hardware input element (e.g., 708) of an electronic device (e.g., 700). In some examples, the input element is sensitive to changes in intensity and is activated when pressed. In some examples, the input element is an intensity-sensitive button with an integrated intensity sensor, which is interpreted as being activated when the intensity of the input on the intensity-sensitive button reaches an activation threshold. In some examples, such as by forming a touch-sensitive display, the hardware input element (e.g., 708) corresponds to the second display (e.g., 704), and the hardware input element (e.g., 708) is in a secure position on the second display (e.g., 704). In some embodiments, when a parameter interface (e.g., 720) for an operation requiring authorization is displayed, the electronic device (e.g., 700) abandons the execution of any function in response to detecting the activation of the hardware input element (e.g., 708). In some examples, the electronic device (e.g., 700) maintains the first account as the account actively logged into the device, and abandons the state of converting the device, so that regardless of authorization (e.g., fingerprint authorization) or not, when the activation (e.g., pressing) of the hardware input element (e.g., 708) is detected, the second account (different from the first account) is actively logged into the device. In some examples, activating the hardware input element (e.g., 708) does not cause the electronic device (e.g., 700) to perform a task, activating the hardware input element (e.g., 708) does not cause any changes to the content displayed on the first display (e.g., 702) or the second display (e.g., 704), and / or activating the hardware input element (e.g., 708, no matter how long the hardware input element is pressed) does not cause the electronic device (e.g., 700) to shut down or power off. By not performing a task when the activation of the hardware input element is detected when the parameter interface is displayed, the electronic device avoids changing the user actively logged in at the electronic device during an ongoing operation (such as a payment transaction), thereby creating a better and more effective human-computer interface.

[0316] In response to receiving the input, based on determining that the input is consistent with authorization criteria (and / or the authorization criteria are satisfied), credentials are issued (824) from the secure element for use in the operation (e.g., payment information for use in a payment transaction).

[0317] In some embodiments, based on determining that the input is inconsistent with the authorization criteria, the electronic device (e.g., 700) abandons (826) causing the credential to be issued from the security element for use in an operation (e.g., a payment transaction). In some embodiments, after receiving the character sequence, and based on determining that the received character sequence is inconsistent with the registered password, the electronic device (e.g., 700) abandons causing the credential to be issued from the security element for use in an operation (e.g., a payment transaction). In some examples, after determining that the received character sequence is inconsistent with the registered password, the electronic device (e.g., 700) simultaneously displays a prompt on the first display (e.g., 702) and / or the second display (e.g., 704) indicating that the user re-enters the password. In some examples, the registered password is a user login password of the electronic device (e.g., a password for an account actively logged into the device).

[0318] In some embodiments, one or more input devices of the electronic device (e.g., 700) include one or more cameras (e.g., a camera with depth sensing capabilities, multiple cameras for generating depth maps using parallax effects, one or more camera sensors). In some embodiments, the visual indication (e.g., 704A) includes an indication of requesting a biometric identification (e.g., a facial identification, an eye-based identification, such as iris recognition or a retinal scan). By providing a display requesting a biometric identification, the electronic device notifies the user of the state of the device (requesting biometric authentication) and prompts the user to provide the requested input, thereby improving the human-computer interface. In some embodiments, the electronic device (e.g., 700) receives input corresponding to the visual indication (e.g., 704A) of one or more steps, including detecting a biometric identification (e.g., a user's biometric identification) by one or more cameras. In some examples, the biometric identification is one or more images captured using one or more cameras (e.g., a camera sensor). In some examples, the electronic device (e.g., 700) uses one or more captured images to generate a depth map (or multiple depth maps) corresponding to one or more (or more) physical features of the user (such as, the user's facial features). In some embodiments, the authorization criteria include criteria that are satisfied when the detected biometric identifier is consistent with an enrolled biometric identifier that is authorized to issue credentials from the secure element. In some examples, the authorization criteria include criteria that are satisfied when a generated depth map corresponding to one or more physical features of the user is consistent with enrolled biometric depth map information that is authorized to issue credentials from the secure element (e.g., an enrolled depth map corresponding to a registered user).

[0319] It should be noted that the details of the process described above with respect to method 800 (e.g., Figures 8A to 8B) also apply in a similar manner to the methods described below. For example, methods 1000 and 1200 optionally include one or more features of the various methods described above with reference to method 800. In some examples, electronic devices 700, 900, and 1100 are the same electronic device. In some examples, the first display and the second display described with reference to methods 800, 1000, and 1200 are similar. For the sake of simplicity, these details are not repeated below.

[0320] Figures 9A-1 to 9E-4 illustrate exemplary devices and user interfaces for using an electronic device 900 (e.g., a laptop computer) with an input device (e.g., a fingerprint sensor and / or a touch-sensitive display associated with a security element) to display one or more steps to be taken to enable the input device for user input according to some embodiments. The exemplary user interfaces depicted in these figures are used to illustrate the processes described below, including the processes in Figures 10A to 10D.

[0321] FIG. 9A-1 shows an electronic device 900 according to some embodiments. In some examples, the electronic device 900 is the same as the electronic device 700. The electronic device 900 has an input device for authorizing access to the credential. For example, the electronic device 900 has a fingerprint sensor 910 and / or a touch-sensitive display 904 associated with a security element (e.g., for securely storing credentials, such as transaction credentials). In some embodiments, the electronic device 900 has a main display 902 (e.g., a first display). In some embodiments, the electronic device 900 causes a user interface 912 to be displayed at an external display 950. The exemplary user interfaces depicted in these figures are used to illustrate the processes described below, including the processes in FIG. 10A to FIG. 10D.

[0322] In some embodiments, in response to receiving a request for a credential, the electronic device determines whether multiple sets of criteria are met. Based on these determinations, the electronic device performs various functions. For example, the following table summarizes multiple sets of criteria and the corresponding functions performed. Each row in the table corresponds to a set of one or more criteria and the generated functions. The "result" column indicates the function performed when the set of one or more criteria in the row is met. For example, "yes" indicates that when the title condition of the corresponding column is true, one of the one or more criteria in the set is met; "no" indicates that when the title condition of the corresponding column is not true, one of the one or more criteria in the set is met; "NA" indicates that the set of one or more conditions of the corresponding row is independent of (or does not include) the conditions of the corresponding column. As described below, this set of criteria (corresponding to rows) optionally includes various criteria (corresponding to columns). In some examples, even if one or more criteria are identified as "yes" or "no" in the following table, the one or more criteria can be excluded from the corresponding standard group.

[0323]

[0324]

[0325] In some embodiments, the second display 904 of the electronic device 900 is a dynamic function row, such as the dynamic function row 5002 described with reference to Figures 5I to 5N. In some embodiments, the second display 904 of the electronic device 900 (e.g., the dynamic function row) is separate from the physical keyboard 906A of the device (e.g., the second display 904 is included as part of a peripheral input mechanism). In some embodiments, the second display 904 is integrated with another input device such as a touchpad 906B.

[0326] The electronic device 900 includes a security element that stores credentials (e.g., transaction credentials) of an associated account (e.g., an account of a user of the electronic device) registered on the electronic device, wherein the account is enabled to authorize the security element to store and release the credentials. In some examples, the credentials include payment information stored in the security element of the electronic device 900. In some examples, the credentials include authorization information (e.g., a registered fingerprint for user authorization (to cause the security element to release the credentials from the security element)) that can be released from the security element for use in an operation (e.g., a payment transaction).

[0327] In some embodiments, the second display 904 (e.g., a dynamic function row) is paired with a security element, and therefore, the second display 904 is able and / or authorized to publish credentials stored in the security element. For example, the security element and the second display 904 are paired during the manufacturing process of the electronic device 900. When the second display 904 is paired with the security element, replacing the second display 904 or the security element in the electronic device 900 requires re-pairing the components to enable the security element to store and publish credentials (e.g., transaction credentials) again. In some embodiments, the second display 904 is paired with the security element, and the first display 902 is not paired with the security element, and therefore, the second display 904 is able and / or authorized to publish credentials stored in the security element, while the first display 902 is not able and is not authorized to publish credentials stored in the security element.

[0328] The electronic device 900 includes a fingerprint sensor 910. In some embodiments, the fingerprint sensor 910 is positioned adjacent to the second display 904. In some embodiments, the fingerprint sensor 910 is a capacitive fingerprint reader. In some embodiments, the fingerprint sensor 910 is integrated into the hardware input element 908. In some embodiments, the hardware input element 908 is an input element used as a power button (e.g., for powering on and off the electronic device 900) and a fingerprint sensor (as described below with reference to Figures 11A to 11M-4 and Figures 12A to 12B). In some examples, the hardware input element 908 is an input element that is sensitive to changes in input intensity. In some examples, the hardware input element 908 is an intensity-sensitive button with an integrated intensity sensor, and when the intensity of the input on the intensity-sensitive button (e.g., characteristic intensity) exceeds the activation threshold, the intensity-sensitive button is activated. In some embodiments, the hardware input element 908 forms a continuous touch-sensitive area with the second display 904.

[0329] Figures 9A-1 to 9A-6 show exemplary devices and user interfaces for indicating that a user stores credentials at an electronic device. Figure 9A-1 shows a user interface 912 of an electronic device 900 when a user is trying to perform an operation that requires authorization (e.g., a payment transaction). The electronic device 900 displays a user interface 912 generated by the device on a display (e.g., a first display 902), wherein the user interface 912 displays a browser application 914 in the foreground of the user interface. In some examples, the user interface 912 includes an indication 912A (e.g., the name of the user associated with the account, in this example, the name is "J.Appleseed") of actively logging into an account of the electronic device 900. For example, a user (e.g., "J.Appleseed") is browsing the Internet using a browser application 914 to purchase a product 914B from an online store 914A. In this example, the active login account (e.g., the account indicated by 912A, the account of "J.Appleseed") is an account that is enabled to authorize a secure element to issue credentials.

[0330] Electronic device 900 displays payment enable indication 916 on an application for performing an operation requiring authorization (e.g., performing a payment transaction). For example, as shown in FIG. 9A-1 , online store 914A displayed on browser application 914 includes payment enable indication 916 (e.g., “Buy Now” enable indication) corresponding to the operation.

[0331] Figure 9A-2 shows an electronic device 900 that receives a request for a credential (e.g., a transaction credential) to authorize an operation that requires authorization. In some examples, receiving a request for a credential includes detecting activation of a payment enable representation 916 corresponding to the operation by one or more input devices (e.g., a computer mouse, touch input) (e.g., using a mouse cursor 918A). In some embodiments, the payment enable representation 916 is part of and controlled by an application (e.g., a browser application) used to perform the operation. In some embodiments, the payment enable representation 916 is controlled by the operating system of the electronic device and is controlled separately from the application used to perform the operation. In some examples, the electronic device 900 receives a request for a credential from a remote server. In some examples, the electronic device 900 receives a request from an application executed locally on the electronic device.

[0332] In some embodiments, in response to receiving a request for credentials, and based on determining that a second set of one or more criteria are satisfied, the electronic device causes a visual indication of one or more steps to be taken to store credentials using the secure element (e.g., steps to provide the electronic device with a payment account such as a credit card account) to be displayed on a display (e.g., on a display of the electronic device, or on an external display different from the display of the electronic device and different from the touch-sensitive display), the second set of one or more criteria including a non-stored credential standard that is satisfied when the secure element does not store credentials (e.g., payment credentials). In some examples, the non-stored credential standard is satisfied when it is determined that the secure element does not store payment credentials that can be used for payment transactions. In some examples, the electronic device provides a request to provide the electronic device with a payment account stored at a remote server. In some examples, the electronic device displays a user input request for payment account information (such as a credit card number and expiration date). In some examples, visual indication 904A replaces content, such as content specific to a running application (e.g., a browser application). For example, visual indication 904A replaces a "back" affordance, a "forward" affordance, a URL affordance, and a "favorites" affordance displayed on the second display.

[0333] For example, as shown in FIGS. 9A-3 to 9A-4, in response to determining that the stored credentials criteria are not met, the electronic device 900 displays a parameter interface 920 with an indication 920H (e.g., “Set up laptop payment”) of one or more steps to be taken using the secure element to store the credentials on a display (e.g., the first display 902), and also displays a visual indication 904A (e.g., “Set up laptop payment”) of one or more steps to be taken using the secure element to store the credentials on a different display (e.g., the second display 904). In some examples, the parameter interface 920 also includes a completion enable representation 920E, which, when activated, causes the electronic device 900 to store the input credentials in the secure element. In some examples, as shown by the transition from FIG. 9A-3 to FIG. 9A-4, the electronic device 900 causes the parameter interface 920 to appear in the field of view (e.g., by sliding down from the edge of the display).

[0334] In some examples, parameter interface 920 is a payment slip. In some examples, the payment slip is a user interface of an operating system, not a first application. In some examples, the payment slip is part of a first-party application provided by a provider of an operating system of a requesting device, wherein the first-party application is different from the first application. In some examples, the payment slip includes user-selectable options for payment transactions, such as payment account options, shipping address options, shipping method options, and contact information options. In some examples, in response to activation of a payment affordance, the payment slip slides into a display (e.g., slides into a view on one or more displays). In some examples, the payment slip at least partially obscures a web page including a payment affordance. In some examples, after displaying a parameter interface identifying one or more devices different from the electronic device, the electronic device receives information indicating whether authorization is provided at one of the one or more devices in response to a request for a credential, and in response, the electronic device provides an indication of whether authorization is provided at one of the one or more devices in response to a request for a credential.

[0335] In some examples, as shown in Figures 9A-5, the parameter interface 920 receives information related to the credentials to be stored in the security element of the electronic device 900. In some examples, the user enters the information using a keyboard, camera sensor, or other input device. In some examples, the relevant information includes a user name 920F (e.g., "J.Appleseed") enabled to authorize operations on the electronic device (e.g., payment transactions), an account number 920G (e.g., a credit card number) for operations on the electronic device (e.g., payment transactions), a billing address and a shipping address associated with the user (e.g., "J.Appleseed"), and / or contact information (e.g., a phone number, an email address) associated with the user (e.g., "J.Appleseed").

[0336] 9A-6 illustrates electronic device 900 detecting activation 918B of completion enable representation 920E. For example, when the user completely enters all information requested by parameter interface 920 to complete the registration of user credentials on the secure element of electronic device 900, the user activates (e.g., by selecting completion enable representation 920E using a mouse, trackpad, or touch input) completion enable representation 920E. In response to detecting activation of completion enable representation 920E (and, in response to determining that there are no errors associated with the entries provided by the user), electronic device 900 displays parameter interface 920 on first display 902 for continuing the operation (e.g., payment transaction), for example, as described with reference to FIGS. 7A to 7D-10.

[0337] In some examples, the electronic device enables the user to use the second electronic device to authorize the operation regardless of whether the stored credential criteria are met. For example, if the electronic device determines that the proximity device criteria (e.g., criteria that are met when the electronic device is communicating with the second electronic device, the second electronic device is close to the electronic device, and the second electronic device is enabled to respond to the request for the credential) are met, the electronic device enables the user to use the second electronic device to authorize the operation. Additional details related to the technology are described in the entirety of cross-referenced U.S. patent application serial number 15 / 269,801, a portion of which is included herein as Appendix C.

[0338] Figure 9B-1 to Figure 9B-5 show exemplary devices and user interfaces for indicating that a user enables an input device of an electronic device. As shown in Figure 9B-1, an electronic device 900 is in a clamshell mode. In some examples, in a clamshell mode, an electronic device 900 (e.g., via Thunderbolt, HDMI, DVI, VGA, etc.) is connected to an external display 950, and the electronic device 900 causes a user interface 912 to be displayed on the external display 950. An integrated display (e.g., a main display, a first display 902 of an electronic device) optionally does not display a user interface. For example, the electronic device 900 is a laptop computer, and when the integrated display of the laptop computer is closed, the laptop computer is in a clamshell mode, which makes a touch-sensitive display (e.g., a second display 904) and / or an electronic device 900 fingerprint sensor inaccessible. The laptop computer is connected to an external display, which makes it possible to disable the input device (e.g., a touch-sensitive display and / or a fingerprint sensor) of the electronic device 900 for user input. In some examples, in the clamshell mode, the electronic device 900 is also connected to an external keyboard 906C, which is connected to the electronic device 900 via a cable and is separate from the integrated keyboard 906A of the electronic device. In some examples, in the clamshell mode, the electronic device 900 is also connected to an external mouse 906D (or external touchpad) that is separate from the integrated touchpad 906B of the electronic device.

[0339] 9B-1 to 9B-2 illustrate a user interface 912 of an electronic device 900 displayed on an external display 950 when a user attempts to perform an operation that requires authorization (e.g., a payment transaction). FIG. 9B-1 illustrates an electronic device 900 causing a user interface 912 to be displayed on an external display 950, the user interface displaying a browser application 914 on the foreground of the interface. In some examples, the user interface includes an indication 912A of an account actively logged into the electronic device 900 (e.g., the name of a user associated with the account, in this example, the name is "J.Appleseed"). For example, a user (e.g., "J.Appleseed") is browsing the Internet using a browser application 914 to purchase an item 914B from an online store 914A.

[0340] An application for performing an operation requiring authorization (e.g., performing a payment transaction) includes a payment enable indication 916. For example, as shown in FIG. 9B-1, the website of an online store 914A displayed on a browser application 914 includes a payment enable indication 916 corresponding to the operation (e.g., a "buy now" enable indication). Activating the payment enable indication 916 allows the user to continue to perform the operation (e.g., continue to purchase item 914B). In some embodiments, the payment enable indication 916 is part of and controlled by the application for performing the operation (e.g., a browser application). In some embodiments, the payment enable indication 916 is controlled by the operating system of the electronic device and is controlled separately from the application for performing the operation.

[0341] Figure 9B-2 shows an electronic device 900, when a user selects a payment enable representation 916 to proceed with an operation (e.g., to proceed with an online purchase of goods 914B), the electronic device receives a request for a credential (e.g., a transaction credential) for authorizing an operation that requires authorization. In some examples, receiving a request for a credential includes detecting activation 918A of a payment enable representation 916 corresponding to an operation by one or more input devices (e.g., a computer mouse, touch input). Thus, when a user interface generated by the electronic device 900 is displayed on an external display 950, the electronic device receives a request for a credential (e.g., a payment credential). In some examples, a request for a credential is received from a remote server. In some examples, a request is received from a locally executed application.

[0342] In some embodiments, as shown in FIG. 9B-2 , a user is browsing the Internet using a browser application 914 displayed on an external display 950 to purchase a product 914B from an online store 914A. The online store 914A displayed on the browser application includes a payment enable indication 916 (e.g., a “buy now” enable indication) corresponding to an operation that requires authorization. For example, activating the payment enable indication 916 allows the user to proceed with the purchase of the product 914B. In some examples, the payment enable indication 916 is displayed by a first application (e.g., a browser application). In some examples, the operation that requires authorization is a payment transaction.

[0343] The electronic device 900 stores a first set of one or more criteria. The first set of one or more criteria includes input disabling criteria that are met when an input device (e.g., a fingerprint sensor of the electronic device 900, and / or a touch-sensitive display associated with a security element of the electronic device 900 (e.g., the second display 904)) is not enabled for user input. For example, when the device is a laptop computer and the laptop computer is "closed" (e.g., in a clamshell mode), the electronic device 900 is not enabled for user input. In the clamshell mode, the built-in integrated display of the laptop computer is closed, so that the user cannot access the touch-sensitive display of the electronic device 900 (e.g., the second display 904).

[0344] As shown in Figures 9B-3 to 9B-4, based on determining that the first set of one or more criteria are met, the electronic device 900 causes a visual indication 920D of one or more steps to be taken to enable the input device for user input to be displayed on a display (e.g., on an external display different from the display of the electronic device), wherein the first set of one or more criteria includes an input disabling standard that is met when the input device is not enabled for user input. In some examples, the visual indication 920D is displayed as part of a parameter interface 920 that prompts the user to open the electronic device 900. In some examples, the parameter interface 920 that prompts the user to open the electronic device slides into view from an area (e.g., an edge) of the display, as shown in the transitions in Figures 9B-3 to 9B-4. In some examples, the parameter interface 920 includes a graphical indication 920D that prompts the user to open and directly use the electronic device 900 to provide authorization for an operation (e.g., a payment transaction). In some examples, parameter interface 920 includes a textual indication 920D (eg, “Open laptop for payment authorization”) prompting the user to open and directly use electronic device 900 to provide authorization for the operation.

[0345] In some embodiments, the first set of one or more criteria stored in the electronic device 900 also includes a stored credential criterion that is satisfied when the security element of the electronic device has stored credentials (e.g., payment credentials). In some examples, the stored credential criterion is satisfied when it is determined that the security element of the electronic device 900 has been configured to store (and is storing) payment credentials that can be used in a payment transaction.

[0346] In some embodiments, the first group of one or more standards stored in the electronic device 900 also includes an authorized account standard that is met when enabling an account that actively logs into the electronic device 900 to authorize the security element to issue a credential (e.g., a payment credential). In some examples, the electronic device 900 is configured to be used with multiple accounts. In some examples, one account in multiple accounts is enabled to authorize the security element to issue a credential (e.g., a payment credential), and other accounts in multiple accounts are not enabled to authorize the security element to issue a credential. In some examples, one account in multiple accounts is enabled to authorize payment using the security element of the electronic device 900. In some examples, the security element includes credentials for various payment accounts, which can be selected by the user for use in operation.

[0347] In some embodiments, the first set of one or more criteria stored in the electronic device 900 also includes a proximity device criterion that is satisfied when the electronic device is communicating with a second electronic device, the second electronic device is in proximity to the electronic device, and the second electronic device is enabled to respond to the request for the credential. Additional details related to the technology (e.g., "handoff" operation) are described in the entirety of cross-referenced U.S. patent application Ser. No. 15 / 269,801, particularly in FIGS. 8A to 8M and paragraphs

[0203] to

[0232] , a portion of which is included in Appendix C.

[0348] In some embodiments, as shown in FIG. 9B-5, once the user enables the electronic device to enable the input device, such as by opening the electronic device 900 (e.g., opening a laptop computer) so that the device is no longer in the clamshell mode, the electronic device 900 causes the user interface 912 to be displayed on the integrated display of the electronic device (e.g., the first display 902). In some examples, the electronic device 900 continues to cause the external display 950 to simultaneously display (e.g., copy) the user interface 912, as shown in FIG. 9B-5. In some examples, once the electronic device is "opened", the electronic device 900 stops causing the external display 950 to display the user interface 912.

[0349] Based on the input device being enabled, the electronic device 900 proceeds with the operation requiring authorization (e.g., a payment transaction), as described above with reference to FIGS. 7A to 7D-10 (e.g., using fingerprint authorization, password authorization, or different types of authorization). For example, the electronic device receives (e.g., at the input device) user input for authorizing the transfer of credentials for use in an operation associated with the request for credentials, and in response to receiving the input for authorizing the transfer of credentials and based on determining that the input is consistent with the authorization criteria, causes the credentials to be released from the secure element for use in the operation.

[0350] In some embodiments, as shown in Figures 9C-1 to 9C-7, when one or more criteria of the third group are met, the electronic device instructs the user to provide authorization at the second electronic device.

[0351] In response to detecting activation of payment enable indication 916, and based on determining that one or more criteria of a third set are satisfied, electronic device 900 causes a parameter interface 920 (e.g., a payment slip) for continuing an operation (e.g., a payment transaction) to be displayed on external display 950, the third set of one or more criteria including a stored credential standard that is satisfied when the security element has stored credentials. In some examples, as described in the transition from FIG. 9C-3 to FIG. 9C-4, parameter interface 920 slides into view on the display (e.g., from the edge of the display). In some examples, parameter interface 920 includes a graphical indication 920A (e.g., a graphical image of second electronic device 900B) and / or a textual indication 920B (e.g., "Use phone for payment authorization") that notifies the user to continue the operation (e.g., payment transaction) using second electronic device 900B (e.g., notifying the user to use "Switch").

[0352] In some embodiments, parameter interface 920 is a payment slip. In some examples, the payment slip is a user interface of an operating system, not a first application. In some examples, the payment slip is part of a first-party application provided by a provider of an operating system of a requesting device, wherein the first-party application is different from the first application. In some examples, the payment slip includes user-selectable options for payment transactions, such as payment account options, shipping address options, shipping method options, and contact information options. In some examples, in response to activation of a payment affordance, the payment slip slides into a display (e.g., slides into a view on one or more displays). In some examples, the payment slip at least partially obscures a web page including a payment affordance. In some examples, after displaying a parameter interface identifying one or more devices different from an electronic device, the electronic device receives information indicating whether authorization is provided at one of the one or more devices in response to a request for a credential, and in response, the electronic device provides an indication of whether authorization is provided at one of the one or more devices in response to a request for a credential.

[0353] In some embodiments, the third group of one or more standards includes an unauthorized account standard that is met when an account that actively logs into the electronic device is not enabled to authorize the security element to issue a credential (e.g., a payment credential). In some examples, the electronic device is configured to be used with multiple accounts. In some examples, a login account in multiple accounts is not enabled to authorize the security element to issue a credential (e.g., a payment credential). In some examples, a login account in multiple accounts is enabled to authorize payment using the security element of the electronic device.

[0354] In some embodiments, as shown in Figures 9C-4 to 9C-7, in response to detecting the activation of the payment enabling representation 916, the electronic device sends a request to the second electronic device 900B to receive authorization for an operation (e.g., a payment transaction). In some embodiments, at Figure 9C-4, the second electronic device 900B displays transaction information and requests authentication information from the user. At Figure 9C-5, the second electronic device 900B receives authentication information (e.g., fingerprint information, password information) from the user. At Figure 9C-6, when processing the authorization of the operation (e.g., a payment transaction), the display of the second electronic device 900B includes information also included in the parameter interface 920 displayed on the display by the electronic device 900. If the authorization at the second electronic device 900B is successful, the second electronic device 900B causes the security element of the second electronic device 900B to issue a certificate, which is transmitted to the remote server by the second electronic device 900B for use in the operation. The certificate is a payment account specified by the electronic device 900 and optionally selected at the electronic device. At Figure 9C-7, electronic device 900 and second electronic device 900B cause their respective displays to display an indication of whether the operation was successful (e.g., whether the payment was authorized). Additional details related to the technology (e.g., the "switching" operation) are described in the entirety of cross-referenced U.S. patent application Ser. No. 15 / 269,801, particularly in Figures 8A to 8M and paragraphs

[0203] to

[0232] , a portion of which is included in Appendix C.

[0355] Figures 9D-1 to 9D-7 show an electronic device that performs operations (e.g., payment transactions) according to some embodiments, and the electronic device has multiple accounts (e.g., multiple user accounts). The first account in the multiple accounts (e.g., the account of "J.Appleseed") is an account (e.g., a unique account) that is enabled to authorize the security element of the electronic device 900 to issue credentials. The second account (e.g., the account of "A.Appleseed") that is not enabled to authorize the security element of the electronic device 900 to issue credentials actively logs in to the electronic device 900. The electronic device 900 stores one or more standards of the third group. In some embodiments, the input device of the electronic device 900 is not enabled (e.g., the device is in clamshell mode). In some embodiments, the input device of the electronic device is enabled (e.g., the device is not in clamshell mode).

[0356] In some examples, the electronic device 900 causes an indication 912B to be displayed on a display (e.g., an external monitor or an integrated display, such as the first display 902) that a second account (e.g., an account associated with “A.Appleseed”) is actively logged into the electronic device.

[0357] In the example shown in FIG9D-1 , a second user (e.g., “A.Appleseed”) is browsing the Internet using browser application 914 to purchase item 914C from online store 914A. The website of online store 914A displayed on browser application 914 includes a payment affordance 916 (e.g., a “Buy Now” affordance) corresponding to an operation requiring authorization (e.g., for authorizing a payment transaction). For example, the operation requiring authorization is purchasing item 914C online.

[0358] Figure 9D-2 shows a second user activating payment enable representation 916 to proceed with an operation requiring authorization (e.g., payment information used in a payment transaction). In response to the second user selecting payment enable representation 916, electronic device 900 receives a request for credentials (e.g., transaction credentials) for an operation requiring authorization. In some examples, receiving the request for the credentials includes detecting activation of payment enable representation 916 corresponding to the operation by one or more input devices (e.g., a computer mouse, touch input). In some examples, electronic device 900 receives the request for the credentials from a remote server. In some examples, the request is received from an application executed locally on electronic device 900.

[0359] In some embodiments, as shown in Figure 9D-3, in response to receiving a request for credentials, and based on determining that one or more criteria of a third set are satisfied, the electronic device 900 causes a parameter interface 920 corresponding to the request for credentials to be displayed on a display (e.g., on a first display of the electronic device, or on an external display that is different from the display of the electronic device and different from the touch-sensitive display), and the third set of one or more criteria includes a storage credential standard that is satisfied when the security element has stored credentials (e.g., payment credentials). Parameter interface 920 identifies (e.g., via 920A) one or more devices different from the electronic device in response to the request for credentials. In some examples, the storage credential standard is satisfied when it is determined that the security element has been configured to store (and is storing) payment credentials (e.g., that can be used in a payment transaction).

[0360] In some embodiments, the third group of one or more criteria include unauthorized account criteria that are met when an account that actively logs into the electronic device is not enabled to authorize the security element to issue credentials (e.g., payment credentials). For example, in some examples, the electronic device is configured to be used with multiple accounts. In some examples, a login account in multiple accounts is not enabled to authorize the security element to issue credentials (e.g., payment credentials). In some examples, a login account in multiple accounts is enabled to authorize payment using the security element of the electronic device.

[0361] In some examples, the third set of one or more criteria includes proximity device criteria that are met when the electronic device 900 communicates with a second electronic device 900B, the second electronic device is proximate to the electronic device 900, and the second electronic device is enabled to respond to the request for the credential.

[0362] In some embodiments, as shown in Figures 9D-4 to 9D-7, in response to detecting the activation of the payment enabling indication 916, the electronic device sends a request to the second electronic device 900B to receive authorization for the operation (e.g., payment transaction). In some examples, the electronic device 900 transmits the request to the second electronic device that identifies the operation to be authorized (e.g., payment operation). In some embodiments, at Figure 9D-4, the second electronic device 900B displays transaction information and requests authentication information from the user. At Figure 9D-5, the second electronic device 900B receives authentication information (e.g., fingerprint information, password information) from the user. At Figure 9D-6, when processing the authorization of the operation (e.g., payment transaction), the display of the second electronic device 900B includes information also included in the parameter interface 920 displayed on the display by the electronic device 900. If the authorization at the second electronic device 900B is successful, the second electronic device 900B causes the security element of the second electronic device 900B to issue a credential, which is transmitted to the remote server by the second electronic device 900B for use in the operation. The credential is with the payment account specified by the electronic device 900 and optionally selected at the electronic device. At Figure 9D-7, the electronic device 900 and the second electronic device 900B cause their corresponding displays to display an indication of whether the operation is successful (e.g., whether the payment is authorized). In some examples, the electronic device 900 receives information indicating whether authorization is received at the second electronic device from the second electronic device 900B (and optionally displays a corresponding indication). In some examples, the electronic device receives information indicating whether the operation is successful from the second electronic device 900, and optionally displays a corresponding indication. In some examples, in response to receiving information from the second electronic device, the electronic device displays an indication of whether the authorization is successful and / or whether the operation is successful. Therefore, the electronic device 900 uses the second electronic device 900B, which is a remote device (e.g., a phone, a watch), to authorize the operation, such as by using fingerprint authorization at the second electronic device 900B. Additional details regarding the technology (e.g., “switching” operations) are described throughout cross-referenced U.S. patent application Ser. No. 15 / 269,801, particularly in FIGS. 8A to 8M and paragraphs

[0203] to

[0232] , a portion of which is included in Appendix C.

[0363] In some examples, parameter interface 920 is a payment slip. In some examples, the payment slip is a user interface of an operating system, not a first application. In some examples, the payment slip is part of a first-party application provided by a provider of an operating system of a requesting device, wherein the first-party application is different from the first application. In some examples, the payment slip includes user-selectable options for payment transactions, such as payment account options, shipping address options, shipping method options, and contact information options. In some examples, in response to activation of a payment affordance, the payment slip slides into a display (e.g., slides into a view on one or more displays). In some examples, the payment slip at least partially obscures a web page including a payment affordance. In some examples, after displaying a parameter interface identifying one or more devices different from the electronic device, the electronic device receives information indicating whether authorization is provided at one of the one or more devices in response to a request for a credential, and in response, the electronic device provides an indication of whether authorization is provided at one of the one or more devices in response to a request for a credential.

[0364] In some embodiments, as shown in Figures 9E-1 to 9E-4, the electronic device 900 prompts the user to provide authorization at the electronic device. The electronic device 900 stores a fifth set of one or more criteria. At Figure 9E-1, the electronic device displays a web browser application, which is similar to the description above.

[0365] Figure 9E-2 shows a user activating a payment enable indication 916 to proceed with an operation requiring authorization (e.g., payment information used in a payment transaction). In response to the user activating the payment enable indication 916, the electronic device 900 receives a request for credentials (e.g., transaction credentials) for the operation requiring authorization. In some examples, receiving the request for the credentials includes detecting activation of the payment enable indication 916 corresponding to the operation by one or more input devices (e.g., a computer mouse, touch input). In some examples, the electronic device 900 receives the request for the credentials from a remote server. In some examples, the request is received from an application executed locally on the electronic device 900.

[0366] As shown in Figures 9E-3 to 9E-4, in some embodiments, in response to receiving a request for a credential, and based on determining that one or more criteria of the fifth group are satisfied, the electronic device causes a parameter interface 920 corresponding to the request for the credential to be displayed on a display (e.g., on a display of the electronic device, or on an external display different from the display of the electronic device and different from the touch-sensitive display), the parameter interface requests authorization in response to the request for the credential, and the fifth group of one or more criteria includes a storage credential standard that is satisfied when the security element has stored the credential (e.g., a payment credential). In some examples, the storage credential standard is satisfied when it is determined that the security element has been configured to store (and is storing) payment credentials that can be used in a payment transaction. In some examples, the electronic device receives authorization (e.g., a fingerprint authorization or a password authorization that is consistent with a registered fingerprint or password, respectively), and in response, causes the security element to issue the credential for use in a transaction corresponding to the request for the credential. In some examples, the issued credential is transmitted to a remote server for use in a transaction. The process of receiving authorization (e.g., via a password, fingerprint, biometrics) is described in more detail with respect to Figures 7A to 7D-10 and Figures 8A to 8B. In some examples, the parameter interface is a payment slip. In some examples, the payment slip is a user interface of an operating system, not a first application. In some examples, the payment slip is part of a first-party application provided by a provider of an operating system of the requesting device, where the first-party application is different from the first application. In some examples, the payment slip includes user-selectable options for payment transactions, such as payment account options, shipping address options, shipping method options, contact information options. In some examples, in response to activation of a payment enabling representation, the payment slip slides into a display (e.g., slides into a view on one or more displays). In some examples, the payment slip at least partially obscures the web page including the payment enabling representation.

[0367] In some embodiments, the fifth group of one or more standards includes an authorized account standard that is met when enabling an account that actively logs into an electronic device to authorize a security element to issue a voucher (e.g., a payment voucher). In some examples, the electronic device is configured to be used with multiple accounts. In some examples, one account in multiple accounts is enabled to authorize a security element to issue a voucher (e.g., a payment voucher), and other accounts in multiple accounts are not enabled to authorize a security element to issue a voucher. In some examples, one account in multiple accounts is enabled to authorize payment using the security element of the electronic device.

[0368] In some embodiments, the fifth set of one or more criteria includes an input enable mode criterion that is satisfied when an input device of the electronic device is enabled for user input. In some examples, the electronic device is a laptop computer, and the input device is enabled for user input when the laptop computer is not in clamshell mode. In some examples, the input device is enabled for user input when the electronic device is a laptop computer that is not connected to an external display and when the laptop computer is open and booted.

[0369] In some embodiments, as discussed above, multiple sets of one or more criteria optionally exclude specific criteria. Thus, to satisfy a set of one or more criteria, a specific criterion need not be satisfied. For example, multiple sets of one or more criteria may optionally be independent of (e.g., exclude) one or more of the following: whether the input enabled mode criterion or the input not enabled mode criterion is satisfied; whether the stored credentials criterion or the unstored credentials criterion is satisfied; whether the stored credentials criterion or the unstored credentials criterion is satisfied; whether the authorized account criterion or the unauthorized account criterion is satisfied; whether the proximity device criterion or the non-proximity device criterion is satisfied.

[0370] Figures 10A to 10D are flowcharts according to some embodiments, which illustrate a method for managing access to credentials used in an operation using an electronic device (e.g., 900). In some embodiments, method 1000 is performed at a device (e.g., 100; 300; 500; cross-referenced U.S. Provisional Patent Application Serial No. 62 / 368,988, a portion of which is included in Appendix B; cross-referenced U.S. Provisional Patent Application Serial No. 62 / 368,988, a portion of which is included in Appendix B) having an input device (e.g., a fingerprint sensor and / or a touch-sensitive display associated with a security element) for authorizing access to the credentials (e.g., an input device integrated into the housing of the electronic device). Some operations in method 1000 are optionally combined, the order of some operations is optionally changed, and some operations are optionally omitted.

[0371] As described below, method 1000 provides an intuitive way to enable display of one or more steps to be taken to enable an input device for user input. The method reduces the cognitive burden on the user when managing access to credentials used in operations requiring authorization, thereby creating a more efficient human-computer interface. For battery-powered computing devices, users are enabled to more quickly and efficiently manage access to credentials used in operations, which saves power and increases the time interval between battery charges.

[0372] In some embodiments, method 1000 is performed on a device connected to an external display (e.g., 950) and causing display at the external display. In some embodiments, method 1000 is performed on a device having a primary display (e.g., 902).

[0373] An electronic device (e.g., 900) causes a user interface (e.g., 912) generated by the device to be displayed (1002) on a display (e.g., 950, an external display connected to the device). In some embodiments, the display is an external display (e.g., connected to the electronic device via a cable). In some embodiments, the display is a main display of the electronic device (e.g., an integral part of the electronic device, a display integrated into the electronic device).

[0374] While causing a user interface (e.g., 912) generated by the electronic device (e.g., 900) to be displayed on a display, the electronic device (e.g., 900) receives (1004) a request for credentials (e.g., payment credentials). In some examples, the request is received from a remote server. In some examples, the request is received from an application executed locally.

[0375] In response to receiving a request for credentials (1006), and based on determining that a first set of one or more criteria are satisfied, the electronic device (e.g., 900) causes a visual indication (e.g., 920A, 920D) of one or more steps to be taken to enable an input device for user input (e.g., steps to convert the device from a clamshell mode to an unclamshell mode) to be displayed (1008) on a display (e.g., 902, 950), wherein the first set of one or more criteria includes an input disabling standard that is satisfied when the input device is not enabled for user input. By displaying a visual indication of one or more steps in response to determining that the input disabling standard is satisfied, the electronic device notifies a user of an internal state of the machine that caused the error and prompts the user to take action to correct the error. For example, the electronic device (e.g., 900) is a laptop computer, and when the built-in display of the laptop computer is closed, the laptop computer is in a clamshell mode, which makes the touch-sensitive display of the device inaccessible. In some embodiments, the laptop computer is connected to an external display (e.g., 950), which disables the touch-sensitive display for user input. Thus, the electronic device notifies the user of the state of the electronic device (e.g., the input device is disabled) and prompts the user to take action by displaying a visual indication of one or more steps. After causing the display of a visual indication of one or more steps to be taken to enable the input device for user input (e.g., 920D), the electronic device (e.g., 900) detects a request to enable the input device for user input (e.g., detecting that the laptop is turned on), and in response, enables the user input device for user input. The electronic device (e.g., 900) receives user input at the input device authorizing the release of credentials from the device's secure element, and in response, releases the credentials from the secure element, which are then transmitted to the remote server for use in a transaction corresponding to the request for the credentials.

[0376] In some embodiments, the electronic device (e.g., 900) includes a security element, and the first set of one or more criteria includes (1008-1) a stored credentials criterion that is satisfied when the security element has stored credentials (e.g., payment credentials). In some examples, the stored credentials criterion is satisfied when it is determined that the security element has been configured to store (and is storing) payment credentials that can be used in a payment transaction.

[0377] In some embodiments, the first group of one or more standards includes (1008-2) an authorized account standard that is met when an account that actively logs into an electronic device (e.g., 900) is enabled to authorize a secure element to issue a credential (e.g., a payment credential). By including the authorized account standard in the first group of one or more standards, the electronic device recognizes that the active login account can authorize the release of the credential and prompts the user to take action to enable the device to execute the release of the credential (e.g., in response to user authorization). In some examples, the electronic device (e.g., 900) is configured to be used with multiple accounts. In some examples, one of the multiple accounts is enabled to authorize the secure element to issue a credential (e.g., a payment credential), and other accounts in the multiple accounts are not enabled to authorize the secure element to issue a credential. In some examples, one of the multiple accounts is enabled to authorize payment using the secure element of the electronic device (e.g., 900).

[0378] In some embodiments, the first group of one or more criteria includes an input non-enabled mode criterion that is satisfied when an input device of the electronic device (e.g., 900) is not enabled for user input. In some examples, the electronic device (e.g., 900) is a laptop computer, and when the laptop computer is in a clamshell mode (e.g., where the built-in integrated display of the laptop computer is closed, which makes the touch-sensitive display of the electronic device inaccessible), the input device is not enabled for user input. The electronic device determines the state of the device and performs appropriate actions accordingly. In some examples, when the electronic device (e.g., 900) is a laptop computer connected to an external display (e.g., 950), the input device is not enabled for user input, which disables the touch-sensitive display for user input. In some examples, when the electronic device (e.g., 900) is a laptop computer and the laptop computer is closed, the input non-enabled mode criterion is satisfied.

[0379] In some embodiments, the first set of one or more criteria includes (1008-3) a non-proximity device criterion that is satisfied when the electronic device (e.g., 900) is not communicating with a second electronic device (e.g., 900B), the second electronic device is proximate to the electronic device, and the second electronic device is enabled to respond to a request for a credential. By including the non-proximity device criterion, the electronic device determines the state of the device and performs appropriate actions accordingly. Additional details related to the technology (e.g., a "switching" operation) are described throughout the cross-referenced U.S. patent application Ser. No. 15 / 269,801, particularly in FIGS. 8A to 8M and paragraphs

[0203] to

[0232] , a portion of which is included in Appendix C.

[0380] In some embodiments, the electronic device (e.g., 900) includes a security element, and the second set of one or more standards includes a non-stored credential standard that is satisfied when the security element does not store credentials (e.g., payment credentials). In some embodiments, in response to receiving a request for credentials, and according to determining that the second set of one or more standards are satisfied, the electronic device (e.g., 900) causes a visual indication (e.g., 904A) of one or more steps to be taken using the security element to store credentials (e.g., steps to provide a payment account such as a credit card account for an electronic device) to be displayed (1010) on a display (e.g., 902, 950). The electronic device determines the state of the device and performs appropriate actions accordingly, thereby improving the human-machine interface. In some examples, when it is determined that the security element does not store payment credentials that can be used for payment transactions, the non-stored credential standard is satisfied. In some examples, the electronic device (e.g., 900) provides a request to provide the electronic device with a payment account stored at a remote server. In some examples, the electronic device (e.g., 900) displays a user input request for payment account information (such as, credit card number and expiration date). Thus, by displaying visual indications of one or more steps, the electronic device informs the user of the status of the device (eg, no credentials stored) and prompts the user to take action before proceeding.

[0381] In some embodiments, the electronic device (e.g., 900) includes a security element, and in response to receiving a request for a credential, and based on determining that a third set of one or more criteria are satisfied, the electronic device (e.g., 900) causes a parameter interface (e.g., 920) corresponding to the request for the credential to be displayed (1012) on a display (e.g., 902, 950), the parameter interface identifying one or more devices different from the electronic device for responding to the request for the credential, the third set of one or more criteria including a stored credential standard that is satisfied when the security element has stored the credential (e.g., payment credential). The electronic device determines the state of the device (which is capable of requesting authorization through a different device) and accordingly enables the user to perform operations using the different devices, thereby creating an effective human-machine interface. In some examples, the stored credential standard is satisfied when it is determined that the security element has been configured to store (and is storing) payment credentials that can be used in a payment transaction. Therefore, by displaying one or more different devices, the electronic device notifies the user to take action using one of the one or more different devices in order to proceed with the operation. In the absence of such an indication, the user may not view other devices, and therefore, the process will stop.

[0382] In some examples, the parameter interface (e.g., 920) is a payment slip. In some examples, the payment slip is a user interface of the operating system, not the first application. By causing the operating system to display the parameter interface, the user gains confidence that the parameter interface is secure. In some examples, the payment slip is part of a first-party application provided by a provider of the operating system of the requesting device, wherein the first-party application is different from the first application. In some examples, the payment slip includes user-selectable options for payment transactions, such as payment account options, shipping address options, shipping method options, and / or contact information options. In some examples, in response to activation of the payment affordance 916, the payment slip slides into the display (e.g., slides into a view on one or more displays). In some examples, the payment slip at least partially obscures the web page including the payment affordance. Other details related to the technology (e.g., "switching" operation) are described in the entirety of the cross-referenced U.S. patent application serial number 15 / 269,801, particularly in Figures 8A to 8M and paragraphs

[0203] to

[0232] , a portion of which is included in Appendix C. In some examples, after displaying a parameter interface 920 identifying one or more devices different from the electronic device (e.g., 900), the electronic device receives information indicating whether to provide authorization at one of the one or more devices (e.g., 900B) in response to a request for credentials, and in response, the electronic device provides an indication of whether to provide authorization at one of the one or more devices (e.g., 900B) in response to the request for credentials.

[0383] In some embodiments, the third set of one or more criteria includes (1014-1) an unauthorized account standard that is met when an account that actively logs into the electronic device (e.g., 900) is not enabled to authorize the security element to issue credentials (e.g., payment credentials). In some examples, the electronic device (e.g., 900) is configured to be used with multiple accounts. In some examples, a login account in the multiple accounts is not enabled to authorize the security element to issue credentials (e.g., payment credentials). In some examples, a login account in the multiple accounts is enabled to use the security element of the electronic device (e.g., 900) to authorize payment.

[0384] In some embodiments, the third set of one or more criteria includes (1014-2) a proximity device criterion that is satisfied when the electronic device (e.g., 900) communicates with a second electronic device (e.g., 900B), the second electronic device is close to the electronic device (e.g., 900), and the second electronic device is enabled to respond to a request for a credential. In some examples, the electronic device (e.g., 900) transmits a request to a second electronic device (e.g., 900B) that identifies an operation to be authorized (e.g., a payment operation). In some examples, the electronic device (e.g., 900) receives information from the second electronic device (e.g., 900B) indicating whether authorization is received at the second electronic device. In some examples, the electronic device (e.g., 900) receives information from the second electronic device (e.g., 900B) indicating whether the operation is successful. In some examples, in response to receiving information from the second electronic device (e.g., 900B), the electronic device (e.g., 900) displays an indication of whether the authorization is successful and / or whether the operation is successful. Thus, the electronic device (e.g., 900) uses a second electronic device (e.g., 900B) that is a remote device (e.g., a phone, a watch) to authorize the operation, such as by using fingerprint authorization at the second electronic device 900B. Additional details related to this technology (e.g., "handoff" operation) are described in the entirety of cross-referenced U.S. patent application Ser. No. 15 / 269,801, particularly in FIGS. 8A to 8M and paragraphs

[0203] to

[0232] , a portion of which is included in Appendix C.

[0385] In some embodiments, the electronic device (e.g., 900) includes a security element, and in response to receiving a request for a credential, based on determining that a fourth set of one or more criteria are satisfied, the electronic device (e.g., 900) causes a parameter interface (e.g., 920) corresponding to the request for the credential to be displayed (1016) on a display (e.g., 902, 950), the parameter interface identifying one or more devices different from the electronic device for responding to the request for the credential, the fourth set of one or more criteria including a stored credential standard that is satisfied when the security element has stored the credential (e.g., a payment credential). Thus, the electronic device determines the state of the device based on the standard (e.g., the security element of the electronic device has stored) (and other standards), and if the set of standards is satisfied, displays a parameter interface that notifies the user of the device state and enables the user to perform operations using a different device. Additional details related to the technology (e.g., "switch" operations) are described throughout the cross-referenced U.S. patent application Ser. No. 15 / 269,801, particularly in FIGS. 8A to 8M and paragraphs

[0203] to

[0232] , a portion of which is included in Appendix C. In some examples, the stored credentials criterion is satisfied when it is determined that the secure element has been configured to store (and is storing) payment credentials that can be used in a payment transaction.

[0386] In some examples, the parameter interface (e.g., 920) is a payment slip. In some examples, the payment slip is a user interface of an operating system, not a first application. In some examples, the payment slip is part of a first-party application provided by a provider of an operating system of a requesting device, wherein the first-party application is different from the first application. Therefore, by causing the payment slip to be displayed as part of a user interface of an operating system (or a provided first-party application), the electronic device signals the user that the display of the payment slip is caused by a request for a credential (e.g., in response to a real request for a credential) and the corresponding parameter interface is therefore secure (e.g., securely displayed by the operating system of the device, rather than displayed by a rogue process), thereby giving the user confidence in the operation and improving the human-machine interface. In some examples, the payment slip includes user-selectable options for a payment transaction, such as a payment account option, a shipping address option, a shipping method option, and / or a contact information option. In some examples, in response to activation of a payment-enabling representation, the payment slip slides into a display (e.g., slides into a view on one or more displays). In some examples, the payment slip at least partially obscures a web page including a payment-enabling representation (e.g., 916). In some examples, after displaying a parameter interface (e.g., 920) that identifies one or more devices different from the electronic device (e.g., 900), the electronic device receives information indicating whether to provide authorization at one of the one or more devices (e.g., 900B) in response to a request for credentials, and in res...

Claims

1. A method, include: At electronic devices with integrated fingerprint sensors and secure elements: While the first account is actively logged into the electronic device: Detecting a corresponding fingerprint using the fingerprint sensor; based on determining that a first set of one or more criteria are satisfied, switching the electronic device so that the first account is no longer actively logged into the electronic device and so that a second account is actively logged into the electronic device; Wherein the first set of one or more criteria includes: a first mode criterion satisfied when the electronic device is in the first mode, and a different account fingerprint criterion satisfied when the corresponding fingerprint corresponds to the second account of the electronic device; Based on determining that a second set of one or more criteria are satisfied, causing a credential to be issued from the secure element for use in the operation; and Wherein the second set of one or more criteria includes: a second mode criterion satisfied when the electronic device is in the second mode, and A current account fingerprint criterion is satisfied when the corresponding fingerprint corresponds to the first account of the electronic device.

2. The method according to claim 1, further comprising: include: After causing the credential to be issued from the secure element for use in the operation, the credential is transmitted to a remote server.

3. The method of any one of claims 1 to 2, wherein the fingerprint sensor is integrated with a hardware input element, and wherein the first set of one or more criteria comprises criteria that are satisfied when activation of the hardware input element is detected.

4. The method according to any one of claims 1 to 2, further comprising: include: Based on determining that the first set of one or more criteria are not met, the first account is maintained as actively logged into the electronic device.

5. The method according to any one of claims 1 to 2, further comprising: include: Based on determining that the second set of one or more criteria are not met, causing a credential to be issued from the secure element for use in the operation is abandoned.

6. The method of any one of claims 1 to 2, wherein the first mode and the second mode are mutually exclusive.

7. The method according to any one of claims 1 to 2, in, The electronic device also includes one or more displays, and wherein, during the second mode, a parameter interface is displayed on one of the one or more displays.

8. The method according to claim 7, in, The electronic device also includes one or more displays, and wherein, during the first mode, the parameter interface is not displayed on the one or more displays.

9. The method according to claim 3, in, Detecting activation of the hardware input element includes detecting a press of the hardware input element for a duration not exceeding a first threshold duration.

10. The method according to any one of claims 1 to 2, in, The electronic device further comprises one or more displays, and wherein the fingerprint sensor is integrated with a hardware input element of the electronic device, the method further comprising: Based on determining that one or more criteria of a third group are met, display a prompt to turn off the electronic device on one of the one or more displays; and wherein the one or more criteria of the third group include: A shutdown press criterion that is met when an activation of the hardware input element is detected for a duration exceeding a first threshold duration and not exceeding a second threshold duration.

11. The method according to any one of claims 1 to 2, wherein, The fingerprint sensor is integrated with a hardware input element of the electronic device, and the method further includes: Based on determining that one or more criteria of a fourth group are met, power off the electronic device without turning it off; and wherein the one or more criteria of the fourth group include: A power-off press criterion that is met when an activation of the hardware input element is detected for a duration exceeding the second threshold duration.

12. The method according to any one of claims 1 to 2, wherein, Enable the first account of the electronic device to authorize the security element to issue a credential.

13. A computer-readable storage medium storing one or more programs configured to be executed by one or more processors of an electronic device having an integrated fingerprint sensor and a security element, the one or more programs including instructions for: While a first account is actively logged in to the electronic device: Use the fingerprint sensor to detect a corresponding fingerprint; Based on determining that one or more criteria of a first group are met, transform the electronic device such that the first account is no longer actively logged in to the electronic device and a second account is actively logged in to the electronic device; wherein the one or more criteria of the first group include: A first mode criterion that is met when the electronic device is in a first mode, and A different account fingerprint criterion that is met when the corresponding fingerprint corresponds to the second account of the electronic device; Based on determining that one or more criteria of a second group are met, cause a credential to be issued from the security element for use in an operation; and wherein the one or more criteria of the second group include: A second mode criterion that is met when the electronic device is in a second mode, and A current account fingerprint criterion that is met when the corresponding fingerprint corresponds to the first account of the electronic device.

14. The computer-readable storage medium according to claim 13, the one or more programs further including instructions for: After causing the credential to be issued from the security element for use in the operation, transmit the credential to a remote server.

15. The computer-readable storage medium according to any one of claims 13 to 14, wherein the fingerprint sensor is integrated with a hardware input element, and wherein the one or more criteria of the first group include criteria that are met when an activation of the hardware input element is detected.

16. The computer-readable storage medium according to any one of claims 13 to 14, the one or more programs further including instructions for: Based on determining that the first set of one or more criteria are not met, the first account is maintained as actively logged into the electronic device.

17. The computer-readable storage medium of any one of claims 13 to 14, wherein the one or more programs further comprise instructions for: Based on determining that the second set of one or more criteria are not met, causing a credential to be issued from the secure element for use in the operation is abandoned.

18. The computer-readable storage medium of any one of claims 13 to 14, wherein the first mode and the second mode are mutually exclusive.

19. The computer-readable storage medium according to any one of claims 13 to 14, in, The electronic device also includes one or more displays, and wherein, during the second mode, a parameter interface is displayed on one of the one or more displays.

20. The computer-readable storage medium of claim 19, in, The electronic device also includes one or more displays, and wherein, during the first mode, the parameter interface is not displayed on the one or more displays.

21. The computer-readable storage medium of claim 15, in, Detecting activation of the hardware input element includes detecting a press of the hardware input element for a duration not exceeding a first threshold duration.

22. The computer-readable storage medium according to any one of claims 13 to 14, in, The electronic device further comprises one or more displays, and wherein the fingerprint sensor is integrated with a hardware input element of the electronic device, and the one or more programs further comprise instructions for: Based on determining that a third set of one or more criteria are satisfied, displaying a prompt on one of the one or more displays to turn off the electronic device; and The third set of one or more criteria includes: A close press criterion is satisfied when activation of the hardware input element is detected for a duration exceeding a first threshold duration and not exceeding a second threshold duration.

23. The computer-readable storage medium according to any one of claims 13 to 14, in, The fingerprint sensor is integrated with a hardware input element of the electronic device, and the one or more programs further include instructions for: upon determining that a fourth set of one or more criteria are satisfied, powering off the electronic device without shutting down the electronic device; and The fourth set of one or more criteria includes: A power-off press criterion is satisfied when activation of the hardware input element is detected for a duration exceeding a second threshold duration.

24. The computer-readable storage medium according to any one of claims 13 to 14, in, The first account of the electronic device is enabled to authorize the secure element to issue credentials.

25. An electronic device, include: Integrated fingerprint sensor; Safety elements; one or more processors; and A memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for: While the first account is actively logged into the electronic device: Detecting a corresponding fingerprint using the fingerprint sensor; based on determining that a first set of one or more criteria are satisfied, switching the electronic device so that the first account is no longer actively logged into the electronic device and so that a second account is actively logged into the electronic device; Wherein the first set of one or more criteria includes: a first mode criterion satisfied when the electronic device is in the first mode, and a different account fingerprint criterion satisfied when the corresponding fingerprint corresponds to the second account of the electronic device; Based on determining that a second set of one or more criteria are satisfied, causing a credential to be issued from the secure element for use in the operation; and Wherein the second set of one or more criteria includes: a second mode criterion satisfied when the electronic device is in the second mode, and A current account fingerprint criterion is satisfied when the corresponding fingerprint corresponds to the first account of the electronic device.

26. The electronic device of claim 25, wherein the one or more programs further comprise instructions for: After causing the credential to be issued from the secure element for use in the operation, the credential is transmitted to a remote server.

27. The electronic device of any one of claims 25 to 26, wherein the fingerprint sensor is integrated with a hardware input element, and wherein the first set of one or more criteria includes criteria that are satisfied when activation of the hardware input element is detected.

28. The electronic device according to any one of claims 25 to 26, wherein the one or more programs further comprise instructions for: Based on determining that the first set of one or more criteria are not met, the first account is maintained as actively logged into the electronic device.

29. The electronic device according to any one of claims 25 to 26, wherein the one or more programs further comprise instructions for: Based on determining that the second set of one or more criteria are not met, causing a credential to be issued from the secure element for use in the operation is abandoned.

30. The electronic device of any one of claims 25 to 26, wherein the first mode and the second mode are mutually exclusive.

31. The electronic device according to any one of claims 25 to 26, in, The electronic device also includes one or more displays, and wherein, during the second mode, a parameter interface is displayed on one of the one or more displays.

32. The electronic device according to claim 31, in, The electronic device also includes one or more displays, and wherein, during the first mode, the parameter interface is not displayed on the one or more displays.

33. The electronic device according to claim 27, in, Detecting activation of the hardware input element includes detecting a press of the hardware input element for a duration not exceeding a first threshold duration.

34. The electronic device according to any one of claims 25 to 26, in, The electronic device further comprises one or more displays, and wherein the fingerprint sensor is integrated with a hardware input element of the electronic device, and the one or more programs further comprise instructions for: Based on determining that a third set of one or more criteria are satisfied, displaying a prompt on one of the one or more displays to turn off the electronic device; and The third set of one or more criteria includes: A close press criterion is satisfied when activation of the hardware input element is detected for a duration exceeding a first threshold duration and not exceeding a second threshold duration.

35. The electronic device according to any one of claims 25 to 26, in, The fingerprint sensor is integrated with a hardware input element of the electronic device, and the one or more programs further include instructions for: upon determining that a fourth set of one or more criteria are satisfied, powering off the electronic device without shutting down the electronic device; and The fourth set of one or more criteria includes: A power-off press criterion is satisfied when activation of the hardware input element is detected for a duration exceeding a second threshold duration.

36. The electronic device according to any one of claims 25 to 26, in, The first account of the electronic device is enabled to authorize the secure element to issue credentials.

37. An electronic device, include: Integrated fingerprint sensor; Safety elements; and Apparatus for performing the method according to any one of claims 1 to 12.

38. A computer program product comprising program code portions for performing the method according to any one of claims 1 to 12 when the computer program product is run on one or more computing devices.

Images