User Interface for Transfer Account
The method and interface optimize transfer account management on electronic devices by adapting to device contexts, reducing inputs and conserving power, thereby enhancing user convenience and efficiency.
Patent Information
- Application Number
- JP2024025558
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Priority Date
- 2019-05-24
- Filing Date
- 2024-02-22
- Publication Date
- 2025-07-28
- Estimated Expiration
- 2039-05-31
Smart Images

Figure 0007714068000001 
Figure 0007714068000002 
Figure 0007714068000003
Abstract
Description
Technical Field
[0001] (Cross - Reference to Related Applications) This application claims priority to U.S. Provisional Patent Application No. 62 / 679,865, entitled "USER INTERFACES FOR TRANSFER ACCOUNTS" (filed Jun. 3, 2018) and U.S. Provisional Patent Application No. 62 / 852,590, entitled "USER INTERFACES FOR TRANSFER ACCOUNTS" (filed May 24, 2019), the contents of which are hereby incorporated by reference in their entirety.
[0002] The present disclosure generally relates to computer user interfaces, and more particularly to techniques for managing the use of transfer accounts using an electronic device.
Background Art
[0003] The use of an electronic device to perform transfer operations such as commercial transactions (transactions) by a second electronic device such as a contactless terminal has increased significantly in recent years. Exemplary contactless terminals include near - field communication (NFC) - enabled terminals, Bluetooth® - enabled terminals, and barcode scanner - enabled terminals. The electronic device can be used with these exemplary terminals to enable a user of the electronic device to perform transfer operations using transfer accounts available for use via the electronic device.
Summary of the Invention
[0004] However, some techniques for managing the use of transfer accounts using an electronic device are generally cumbersome and inefficient. For example, in some existing techniques, complex and time - consuming user interfaces are used that may involve multiple key presses or keystrokes. Existing techniques take more time than necessary and waste the user's time and the device's energy. The latter problem is particularly significant in battery - operated devices.
[0005] Accordingly, the present technology provides an electronic device with a faster, more secure, and more efficient method and interface for managing the use of a transfer account. Such a method and interface optionally complement or replace other methods for managing the use of a transfer account. Such a method and interface reduce the cognitive burden on the user and create a more efficient human-machine interface. In the case of a battery-operated computing device, such a method and interface conserve power and increase the battery charging interval. Further, such a method and interface reduce the number of inputs required in an electronic device, and such smartphones and / or smartwatches perform transfer operations using a transfer account (e.g., credentials associated therewith). Further, such a method and interface enable improved user convenience when using a transfer account (e.g., credentials associated therewith) in a transfer operation.
[0006] According to some embodiments, a method for execution on an electronic device comprising a display is described. The method includes displaying, on the display, a start user interface including affordances for adding secure credentials to the electronic device; receiving a request for adding secure credentials to the electronic device, the request corresponding to the affordances for adding secure credentials; in response to receiving the request for adding secure credentials to the electronic device, starting a first process for inputting information regarding the secure credentials into the electronic device according to a determination that the device was operating in a first context when the request for adding secure credentials was received; and starting a second process different from the first process for inputting information regarding the secure credentials into the electronic device according to a determination that the device was operating in a second context different from the first context when the request for adding secure credentials was received.
[0007] According to some embodiments, a non-transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of an electronic device including a display is described. The one or more programs cause the display to display a start user interface including affordances for adding secure credentials to the electronic device, receive a request for adding secure credentials to the electronic device, where the request corresponds to an affordance for adding secure credentials, and in response to receiving the request for adding secure credentials to the electronic device, start a first process for inputting information regarding the secure credentials into the electronic device according to a determination that the device was operating in a first context when the request for adding secure credentials was received, and start a second process different from the first process for inputting information regarding the secure credentials into the electronic device according to a determination that the device was operating in a second context different from the first context when the request for adding secure credentials was received.
[0008] According to some embodiments, a non-transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of an electronic device including a display is described. The one or more programs cause the display to display a start user interface including affordances for adding secure credentials to the electronic device, receive a request to add secure credentials to the electronic device, where the request received corresponds to an affordance for adding secure credentials, and in response to receiving the request to add secure credentials to the electronic device, start a first process for inputting information regarding the secure credentials into the electronic device according to a determination that the device was operating in a first context when the request to add secure credentials was received, and start a second process different from the first process for inputting information regarding the secure credentials into the electronic device according to a determination that the device was operating in a second context different from the first context when the request to add secure credentials was received.
[0009] According to some embodiments, an electronic device is described as including a display, 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 are to display, on the display, a start user interface including affordances for adding secure credentials to the electronic device, receive a request for adding secure credentials to the electronic device, where the request corresponds to an affordance for adding secure credentials, and, in response to receiving the request for adding secure credentials to the electronic device, start a first process for inputting information regarding the secure credentials into the electronic device according to a determination that the device was operating in a first context when the request for adding secure credentials was received, and start a second process different from the first process for inputting information regarding the secure credentials into the electronic device according to a determination that the device was operating in a second context different from the first context when the request for adding secure credentials was received.
[0010] According to some embodiments, an electronic device is described. The electronic device includes a display, means for displaying a start user interface on the display that includes an affordance for adding secure credentials to the electronic device, means for receiving a request for adding secure credentials to the electronic device, the means for receiving a request corresponding to the affordance for adding secure credentials, means for starting a first process for inputting information regarding the secure credentials into the electronic device in response to receiving a request for adding secure credentials to the electronic device, according to a determination that the device was operating in a first context when the request for adding secure credentials was received, and means for starting a second process different from the first process for inputting information regarding the secure credentials into the electronic device according to a determination that the device was operating in a second context different from the first context when the request for adding secure credentials to the device was received.
[0011] According to some embodiments, a method is described for being executed on an electronic device that includes a display and one or more input devices. The method includes detecting a request to power on the electronic device while the electronic device is operating on stored power, and in response to detecting the request to power on the electronic device, displaying a wake screen user interface on the display according to a determination that the electronic device has available power that exceeds a threshold amount, and simultaneously displaying on the display an indication that the electronic device has available power that is less than the threshold amount and an indication that a first type of credentials are available for use via the electronic device according to a determination that the electronic device has available power that is less than the threshold amount and that the first type of credentials are provisioned on the electronic device, and displaying on the display an indication that the electronic device has available power that is less than the threshold amount without displaying an indication that the credentials are available for use via the electronic device according to a determination that the electronic device has available power that is less than the threshold amount and that the first type of credentials are not available for use via the electronic device.
[0012] According to some embodiments, a non-transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of an electronic device comprising a display and one or more input devices is described. The one or more programs, while the electronic device is operating on stored power, detect a request to start the electronic device, and in response to detecting the request to start the electronic device, display a wake screen user interface on the display according to a determination that the electronic device has available power exceeding a threshold amount, display on the display, according to a determination that the electronic device has available power less than the threshold amount and that a first type of credentials is provisioned on the electronic device, an indication that the electronic device has available power less than the threshold amount and an indication that the first type of credentials is available for use via the electronic device simultaneously, and display on the display, according to a determination that the electronic device has available power less than the threshold amount and that the first type of credentials is not available for use via the electronic device, an indication that the electronic device has available power less than the threshold amount without displaying an indication that the credentials are available for use via the electronic device, including instructions.
[0013] According to some embodiments, a non-transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of an electronic device including a display and one or more input devices is described. The one or more programs, while the electronic device is operating on stored power, detect a request to boot the electronic device, and in response to detecting the request to boot the electronic device, display a wake screen user interface on the display according to a determination that the electronic device has available power exceeding a threshold amount, display on the display, simultaneously, an indication that the electronic device has available power less than the threshold amount and an indication that a first type of credentials are available for use via the electronic device according to a determination that the electronic device has available power less than the threshold amount and the first type of credentials are provisioned on the electronic device, and display an indication that the electronic device has available power less than the threshold amount without displaying an indication that the credentials are available for use via the electronic device according to a determination that the electronic device has available power less than the threshold amount and the first type of credentials are not available for use via the electronic device, including instructions.
[0014] According to some embodiments, an electronic device is described as including a display, one or more input devices, 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, while the electronic device is operating on stored power, detect a request to start the electronic device, and in response to detecting the request to start the electronic device, display a wake screen user interface on the display according to a determination that the electronic device has available power exceeding a threshold amount, display on the display, simultaneously, an indication that the electronic device has available power less than the threshold amount and an indication that a first type of credentials are available for use via the electronic device according to a determination that the electronic device has available power less than the threshold amount and the first type of credentials are provisioned on the electronic device, and display an indication that the electronic device has available power less than the threshold amount without displaying an indication that the credentials are available for use via the electronic device according to a determination that the electronic device has available power less than the threshold amount and the first type of credentials are not available for use via the electronic device.
[0015] According to some embodiments, an electronic device is described. The electronic device includes a display, one or more input devices, means for detecting a request to activate the electronic device while the electronic device is operating on stored power, and in response to detecting a request to activate the electronic device, according to a determination that the electronic device has available power exceeding a threshold amount, displaying a wake screen user interface on the display, and according to a determination that the electronic device has available power less than the threshold amount and that a first type of credential is provisioned on the electronic device, simultaneously displaying on the display an indication that the electronic device has available power less than the threshold amount and an indication that the first type of credential is available for use via the electronic device, and according to a determination that the electronic device has available power less than the threshold amount and that the first type of credential is not available for use via the electronic device, displaying on the display an indication that the electronic device has available power less than the threshold amount without displaying an indication that the credential is available for use via the electronic device, and means for doing so.
[0016] According to some embodiments, a method is described that is executed in an electronic device comprising a display and a wireless communication radio. The method includes receiving, via the wireless communication radio, information indicating a request for credentials from a second electronic device, and in response to receiving the information indicating a request for credentials from the second electronic device, according to a determination that the information indicating the request for credentials is of a first type, displaying on the display a request for authentication to proceed with a transfer operation using a transfer account associated with the electronic device, and according to a determination that the information indicating the request for credentials is of a second type, transmitting, via the wireless communication radio, a second type of credential associated with the transfer account without requesting authentication.
[0017] According to some embodiments, a non-transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of an electronic device including a display and a wireless communication radio is described. The one or more programs are to receive, via the wireless communication radio, information indicating a request for credentials from a second electronic device, and in response to receiving the information indicating the request for credentials from the second electronic device, display, on the display, a request for authentication to proceed with a transfer operation using a transfer account associated with the electronic device according to a determination that the information indicating the request for credentials is of a first type, and transmit, via the wireless communication radio, a second type of credentials associated with the transfer account without requesting authentication according to a determination that the information indicating the request for credentials is of a second type.
[0018] According to some embodiments, a transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of an electronic device including a display and a wireless communication radio is described. The one or more programs are to receive, via the wireless communication radio, information indicating a request for credentials from a second electronic device, and in response to receiving the information indicating the request for credentials from the second electronic device, display, on the display, a request for authentication to proceed with a transfer operation using a transfer account associated with the electronic device according to a determination that the information indicating the request for credentials is of a first type, and transmit, via the wireless communication radio, a second type of credentials associated with the transfer account without requesting authentication according to a determination that the information indicating the request for credentials is of a second type.
[0019] According to some embodiments, an electronic device is described as including a display, a wireless communication radio, 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 are configured to receive, via the wireless communication radio, information indicating a request for credentials from a second electronic device, and in response to receiving the information indicating a request for credentials from the second electronic device, display, on the display, a request for authentication to proceed with a transfer operation using a transfer account associated with the electronic device according to a determination that the information indicating the request for credentials is of a first type, and transmit, via the wireless communication radio, a second type of credentials associated with the transfer account without requesting authentication according to a determination that the information indicating the request for credentials is of a second type.
[0020] According to some embodiments, an electronic device is described. The electronic device includes a display, a wireless communication radio, means for receiving, via the wireless communication radio, information indicating a request for credentials from a second electronic device, and means for displaying, on the display, a request for authentication to proceed with a transfer operation using a transfer account associated with the electronic device according to a determination that the information indicating the request for credentials is of a first type in response to receiving the information indicating a request for credentials from the second electronic device, and means for transmitting, via the wireless communication radio, a second type of credentials associated with the transfer account without requesting authentication according to a determination that the information indicating the request for credentials is of a second type.
[0021] According to some embodiments, a method is described that is executed in an electronic device comprising one or more wireless communication radios and storing information regarding a first account. The method includes receiving, from a communication terminal via one or more wireless communication radios, a credentials request; in response to receiving the credentials request, transmitting, via one or more wireless communication radios, the credentials of the first account without requesting authentication, according to a determination that authentication for the first account has been provided; the first account has not been authenticated, the first account is set in the electronic device to provide credentials without requesting authentication, and according to a determination that authentication is requested by the communication terminal, requesting authentication in the electronic device without transmitting the credentials of the first account; the first account has not been authenticated, the first account is set in the electronic device to provide credentials without requesting authentication, and according to a determination that authentication is not requested by the communication terminal, transmitting, via one or more wireless communication radios, the credentials of the first account without requesting authentication in the electronic device.
[0022] 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 comprising one or more wireless communication radios and storing information regarding a first account. The one or more programs receive a credential request from a communication terminal via the one or more wireless communication radios, and in response to receiving the credential request, transmit the credentials of the first account via the one or more wireless communication radios without requesting authentication according to a determination that authentication for the first account has been provided, the first account is not set up in the electronic device to provide credentials without requesting authentication and authentication has not been provided for the first account, request authentication in the electronic device without transmitting the credentials of the first account according to a determination that authentication is requested by the communication terminal, the first account is not set up in the electronic device to provide credentials without requesting authentication and authentication has not been provided for the first account, and transmit the credentials of the first account via the one or more wireless communication radios without requesting authentication in the electronic device according to a determination that authentication is not requested by the communication terminal.
[0023] According to some embodiments, a temporary computer-readable storage medium is described. The temporary computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device comprising one or more wireless communication radios and storing information regarding a first account. The one or more programs receive a credential request from a communication terminal via the one or more wireless communication radios, and in response to receiving the credential request, transmit the credentials of the first account via the one or more wireless communication radios without requesting authentication according to a determination that authentication for the first account has been provided, the first account has not been authenticated, and the first account is set in the electronic device to provide credentials without requesting authentication, request authentication in the electronic device without transmitting the credentials of the first account according to a determination that authentication is requested by the communication terminal, the first account has not been authenticated such that the electronic device is not in an authentication-provided state for the first account, and the first account is set in the electronic device to provide credentials without requesting authentication, and transmit the credentials of the first account via the one or more wireless communication radios without requesting authentication in the electronic device according to a determination that authentication is not requested by the communication terminal, including instructions.
[0024] According to some embodiments, an electronic device is described. The electronic device includes one or more wireless communication radios, one or more processors, and a memory storing one or more programs configured to be executed by the one or more processors. The electronic device stores information regarding a first account. The one or more programs receive a credential request from a communication terminal via the one or more wireless communication radios, and in response to receiving the credential request, transmit the credentials of the first account via the one or more wireless communication radios without requesting authentication according to a determination that authentication for the first account has been provided. If authentication for the first account has not been provided and the first account is set in the electronic device to provide credentials without requesting authentication, request authentication in the electronic device without transmitting the credentials of the first account according to a determination that authentication is requested by the communication terminal. If authentication for the first account has not been provided and the first account is set in the electronic device to provide credentials without requesting authentication, and if it is determined that authentication is not requested by the communication terminal, transmit the credentials of the first account in the electronic device without requesting authentication via the one or more wireless communication radios, including instructions.
[0025] According to some embodiments, an electronic device is described. The electronic device includes one or more wireless communication radios that store information regarding a first account, means for receiving a credential request from a communication terminal via the one or more wireless communication radios, and in response to receiving the credential request, transmitting the credentials of the first account via the one or more wireless communication radios without requesting authentication according to a determination that authentication for the first account has been provided, and if authentication for the first account has not been provided and the first account is set in the electronic device to provide credentials without requesting authentication, requesting authentication in the electronic device without transmitting the credentials of the first account according to a determination that authentication is requested by the communication terminal, and if authentication for the first account has not been provided and the first account is set in the electronic device to provide credentials without requesting authentication, and if it is determined that authentication is not requested by the communication terminal, transmitting the credentials of the first account in the electronic device without requesting authentication via the one or more wireless communication radios, including instructions.
[0026] The executable instructions for performing these functions are optionally included within a non-transitory computer-readable storage medium or other computer program product configured to be executed by one or more processors. The executable instructions for performing these functions are optionally included within a temporary computer-readable storage medium or other computer program product configured to be executed by one or more processors.
[0027] Thus, a faster and more efficient method and interface for managing a transfer account are provided to the device, thereby increasing the effectiveness, efficiency, and user satisfaction of such a device. Such a method and interface can complement or replace other methods for managing a transfer account.
Brief Description of the Drawings
[0028] To better understand the various embodiments described, the following "Modes for Carrying Out the Invention" should be referred to in conjunction with the following drawings, and like reference numerals refer to corresponding parts throughout the following figures.
[0029]
Figure 1A
[0030]
Figure 1B
[0031]
Figure 2
[0032]
Figure 3
[0033]
Figure 4A
[0034]
Figure 4B
[0035]
Figure 5A
[0036]
Figure 5B
[0037]
Figure 6
[0038]
Figure 7A
Figure 7B
Figure 7C
Figure 7D
Figure 7E
Figure 7F
Figure 7G
Figure 7H
Figure 7I
Figure 7J
Figure 7K
Figure 7L
Figure 7M
Figure 7N
Figure 7O
[0039]
Figure 8A
Figure 8B
Figure 8C
[0040]
Figure 9A
Figure 9B
Figure 9C
Figure 9D
Figure 9E
Figure 9F
Figure 9G
Figure 9H
Figure 9I
Figure 9J
[0041]
Figure 10A
Figure 10B
Figure 10C
[0042]
Figure 11A
Figure 11B
Figure 11C
Figure 11D
Figure 11E
Figure 11F
Figure 11G
Figure 11H
Figure 11I
Figure 11J
Figure 11K
Figure 11L
Figure 11M
Figure 11N
Figure 11O
Figure 11P
Figure 11Q
Figure 11R
Figure 11S
Figure 11T
Figure 11U
Figure 11V
[0043]
Figure 12A
Figure 12B
Figure 12C
[0044]
Figure 13A
Figure 13B
Figure 13C
Figure 13D
Figure 13E
Figure 13F
Figure 13G
Figure 13H
Figure 13I
Figure 13J
Figure 13K
Figure 13L
Figure 13M
Figure 13N
Figure 13O
Figure 13P
Figure 13Q
Figure 13R
Figure 13S
Figure 13T
Figure 13U
Figure 13V
Figure 13W
[0045]
Figure 14
[0046] The following description sets forth exemplary methods, parameters, and the like. However, such description is not intended as a limitation on the scope of the present disclosure, and it should be recognized that instead it is provided as a description of exemplary embodiments.
[0047] There is a need for an electronic device that provides an efficient method and interface for using a transfer account using the electronic device. For example, there is a need for an electronic device that provides an efficient method and interface for provisioning a transfer account on the electronic device (or adding secure credentials to the electronic device). In another example, there is a need for an electronic device that provides an efficient method and interface for using a transfer account (e.g., a particular type of transfer account) via the electronic device for transfer operations while the electronic device is operating in a low-power state. In another example, there is a need for an electronic device that provides an efficient method and interface for using a transfer account linked to a plurality of different sub-accounts and / or a specific account via the electronic device. Such techniques can reduce the cognitive burden on a user accessing a transfer account using an electronic device, thereby improving productivity. Further, such techniques can reduce processor and battery power that would otherwise be wasted on redundant user input.
[0048] In the following, FIGS. 1A - 1B, 2, 3, 4A - 4B, 5A - 5B, and 6 provide an illustration of exemplary devices for implementing techniques for managing transfer accounts. FIG. 6 shows an exemplary device connected via one or more communication channels according to some embodiments. FIGS. 7A - 7O show exemplary user interfaces for entering information regarding secure credentials into an electronic device according to some embodiments. FIGS. 8A - 8C are flow diagrams illustrating methods for entering information regarding secure credentials into an electronic device according to some embodiments. The user interfaces of FIGS. 7A - 7O are used to illustrate processes described later, including the processes of FIGS. 8A - 8C. FIGS. 9A - 9J show exemplary user interfaces for managing the use of credentials provisioned on an electronic device operating on stored power. FIGS. 10A - 10C are flow diagrams illustrating methods for managing the use of credentials provisioned on an electronic device operating on stored power according to some embodiments. The user interfaces of FIGS. 9A - 9J are used to illustrate processes described later, including the processes of FIGS. 10A - 10C. FIGS. 11A - 11V show exemplary user interfaces for managing the use of transfer accounts associated with different credentials on an electronic device. FIGS. 12A - 12C are flow diagrams illustrating methods for managing the use of transfer accounts associated with different credentials on an electronic device according to some embodiments. The user interfaces of FIGS. 11A - 11V are used to illustrate processes described later, including the processes of FIGS. 12A - 12C. FIGS. 13A - 13W show exemplary techniques and exemplary user interfaces for managing the use of credentials according to some embodiments. FIG. 14 is a flow diagram illustrating a method for managing the use of credentials according to some embodiments. The user interfaces of FIGS. 13A - 13W are used to illustrate processes described later, including the process of FIG. 14.
[0049] In the following description, terms such as "first", "second", etc. are used to describe various elements, but these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, without departing from the scope of the various embodiments described, the first touch can also be called the second touch, and similarly, the second touch can also be called the first touch. The first touch and the second touch are both touches, but they are not the same touch.
[0050] The terms used in the description of the various embodiments described herein are for the purpose of describing only specific embodiments and are not intended to be limiting. In the description of the various embodiments described and the appended claims, the singular forms "a", "an", and "the" are intended to include the plural as well, unless the context clearly dictates otherwise. Also, as used herein, the term "and / or" refers to any and all combinations of one or more of the associated listed items and is to be understood to include the same. The terms "includes", "including", "comprises", and / or "comprising", when used herein, specify the presence of the stated features, integers, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.
[0051] The term "if" optionally, depending on the context, is interpreted to mean "when" or "upon", or "in response to determining" or "in response to detecting". Similarly, the phrases "if it is determined" or "if [a stated condition or event] is detected" optionally, depending on the context, are interpreted to mean "upon determining" or "in response to determining", or "upon detecting [the stated condition or event]" or "in response to detecting [the stated condition or event]".
[0052] Embodiments of an electronic device, a user interface for such a device, and related processes for using such a device are described. In some embodiments, the device is a portable communication device such as a cellular phone that also includes other functions such as PDA functionality and / or music player functionality. Exemplary embodiments of portable multifunction devices include, but are not limited to, devices such as the iPhone®, iPod Touch®, and iPad® from Apple Inc. of Cupertino, California. Optionally, other portable electronic devices such as laptop or tablet computers having a touch-sensitive surface (e.g., a touch screen display and / or a touch pad) are also used. Also, in some embodiments, it should be understood that the device is not a portable communication device but a desktop computer having a touch-sensitive surface (e.g., a touch screen display and / or a touch pad).
[0053] 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, a mouse, and / or a joystick.
[0054] The device typically corresponds to various applications such as one or more of a drawing application, a presentation application, a word processing application, a website creation application, a disk authoring application, a spreadsheet application, a game application, a telephone application, a video conferencing application, an email application, an instant messaging application, a training 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.
[0055] 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, as well as the corresponding information displayed on the device, are optionally adjusted and / or changed for each application and / or within each respective application. Thus, the common physical architecture of the device (such as a touch-sensitive surface) optionally supports various applications with a user interface that is intuitive and transparent to the user.
[0056] Attention is now directed to an embodiment of a portable device having a touch-sensitive display. FIG. 1A is a block diagram showing a portable multifunctional device 100 having a touch-sensitive display system 112 according to some embodiments. The touch-sensitive display 112 may be referred to herein as a "touch screen" for convenience, and may be known or referred to as a "touch-sensitive display system." Device 100 includes a memory 102 (optionally including one or more computer-readable storage media), a memory controller 122, one or more processing units (CPUs) 120, a peripheral 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. Device 100 optionally includes one or more light sensors 164. Device 100 optionally includes one or more contact intensity sensors 165 (such as a touch-sensitive surface, such as the touch-sensitive display system 112 of device 100) for detecting the intensity of contact on device 100. Device 100 optionally includes one or more haptic output generators 167 for generating haptic output on device 100 (such as generating haptic output on a touch-sensitive surface, such as the touch-sensitive display system 112 of device 100 or the touch pad 355 of device 300). These components optionally communicate via one or more communication buses or signal lines 103.
[0057] As used in this specification and the claims, the term "intensity" of a contact on a touch-sensing surface refers to the force or pressure (force per unit area) of the contact (e.g., finger contact) on the touch-sensing surface, or a proxy for the force or pressure of the contact on the touch-sensing surface. The intensity of the contact has a range of values that includes at least four distinct values, and more typically, hundreds (e.g., at least 256) of distinct values. The intensity of the contact is optionally determined (or measured) using a variety of techniques and a variety of sensors or combinations of sensors. For example, one or more force sensors under or adjacent to the touch-sensing surface are optionally used to measure the force at various points on the touch-sensing surface. In some implementations, force measurements from multiple force sensors are combined (e.g., weighted average) to determine the estimated force of the contact. Similarly, a pressure-sensitive tip of a stylus is optionally used to determine the pressure of the stylus on the touch-sensing surface. Alternatively, the size and / or change of the contact area detected on the touch-sensing surface, the capacitance and / or change of the touch-sensing surface in proximity to the contact, and / or the resistance and / or change of the touch-sensing surface in proximity to the contact are optionally used as surrogates for the force or pressure of the contact on the touch-sensing surface. In some implementations, the alternative measurements for the force or pressure of the contact are used directly to determine whether they exceed an intensity threshold (e.g., the intensity threshold is described in units corresponding to the alternative measurements). In some implementations, the proxy measurement for the contact force or pressure is converted to an estimated force or pressure, and the estimated force or pressure is used to determine whether it exceeds an intensity threshold (e.g., the intensity threshold is a pressure threshold measured in units of pressure). By using the intensity of the contact as an attribute of user input, a user can access additional device functions that would normally be inaccessible to the user on a device of reduced size with a limited area for displaying affordances (e.g., on a touch-sensing display) and / or receiving user input (e.g., via a touch-sensing display, a touch-sensing surface, or a physical / mechanical control such as a knob or button).
[0058] As used in this specification and the claims, the term "haptic output" refers to a physical displacement of the device relative to its previous position, a physical displacement of a component of the device (e.g., a touch-sensing 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, that would be detected by a user's sense of touch. For example, in a situation where the device or a component of the device is in contact with a user's surface sensitive to touch (e.g., a finger, palm, or other part of the user's hand), the haptic output generated by the physical displacement will be interpreted by the user as a tactile sensation corresponding to a perceived change in the physical characteristics of the device or component thereof. For example, movement of a touch-sensing surface (e.g., a touch-sensing display or a trackpad) may optionally be interpreted by the user as a "down click" or "up click" of a physical actuator button. In some cases, the user may feel a tactile sensation such as a "down click" or "up click" even when there is no movement of the physical actuator button associated with the touch-sensing surface physically pressed (e.g., displaced) by the user's action. As another example, movement of a touch-sensing surface may optionally be interpreted or perceived by the user as "roughness" of the touch-sensing surface, even when there is no change in the smoothness of the touch-sensing surface. Such interpretation of touch by the user depends on the user's individual sensory perception, but there are many sensory perceptions of touch that are common to a majority of users. Thus, when a haptic output is described as corresponding to a particular sensory perception of the user (e.g., "up click", "down click", "roughness"), unless otherwise stated, the generated haptic output corresponds to a physical displacement of a device, or a component of the device, that generates the described sensory perception of a typical (or average) user.
[0059] Device 100 is merely an example of a portable multifunctional device, and it should be understood that device 100 may optionally have more or fewer components than those shown, may optionally combine two or more components, or may optionally have different configurations or arrangements of those components. The various components shown in FIG. 1A are implemented in a combination of hardware, software, or both hardware and software, including one or more signal processing circuits and / or application specific integrated circuits.
[0060] Memory 102 optionally includes high-speed random access memory and also optionally includes non-volatile memory such as one or more magnetic 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.
[0061] Peripheral interface 118 can be used to couple the input and output peripheral devices of the device to CPU 120 and memory 102. One or more processors 120 operate or execute various software programs and / or instruction sets stored in memory 102 to perform various functions for device 100 and process data. In some embodiments, peripheral interface 118, CPU 120, and memory controller 122 are optionally implemented on a single chip such as chip 104. In some other embodiments, they are optionally implemented on separate chips.
[0062] The RF (radio frequency) circuit 108 transmits and receives RF signals, also called electromagnetic signals. The RF circuit 108 converts electrical signals into electromagnetic signals or vice versa and communicates with a communication network and other communication devices via electromagnetic signals. The RF circuit 108 optionally includes well-known circuits for performing these functions, such as, but not limited to, an antenna system, an RF transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a CODEC chipset, a subscriber identity module (SIM) card, a memory, and the like. The RF circuit 108 optionally communicates wirelessly with a network such as the Internet, also called the World Wide Web (WWW), an intranet, and / or a wireless network such as a cellular telephone network, a wireless local area network (LAN) and / or a metropolitan area network (MAN), and with other devices. The RF circuit 108 optionally includes well-known circuits for detecting a near field Communication (NFC) field by, for example, a short-range communication radio. Wireless communication optionally includes, but is not limited to only, Global System for Mobile Communications (GSM) for mobile communication, 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 Termevolution, LTE), Near Field Communication (NFC), Wideband Code Division Multiple Access (W-CDMA), Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Bluetooth (registered trademark), Bluetooth Low Energy (BTLE (registered trademark)), Wireless Fidelity (Wi-Fi (registered trademark)) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11n, and / or IEEE 802.11ac), Voice over Internet Protocol (VoIP), Wi-MAX (registered trademark), protocols for email (e.g., Internet Message Access Protocol (IMAP) and / or Post Office Protocol (POP)), instant messaging (e.g., Extensible Messaging and Presence Protocol (XMPP), Session Initiation Protocol for Instant Messaging and Presence Leveraging Extensions (SIMPLE), Instant Messaging and Presence Service (IMPS)), and / or Short Message Service (SMS), or any other suitable communication protocol including communication protocols not yet developed as of the filing date of this specification.
[0063] The audio circuit 110, speaker 111, and microphone 113 provide an audio interface between the user and the device 100. The audio circuit 110 receives audio data from the peripheral device interface 118, converts this audio data into an electrical signal, and transmits this electrical signal to the speaker 111. The speaker 111 converts the electrical signal into human audible sound waves. Also, the audio circuit 110 receives the electrical signal converted from sound waves by the microphone 113. The audio circuit 110 converts the electrical signal into audio data and transmits this audio data to the peripheral device interface 118 for processing. The audio data is optionally obtained 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 of FIG. 2). The headset jack provides an interface between the audio circuit 110 and a detachable audio input / output peripheral device such as an output-only headset or a headset with both output (e.g., mono or stereo headphones) and input (e.g., microphone).
[0064] The I / O subsystem 106 couples input / output peripheral devices on the device 100, such as the touch screen 112 and other input control devices 116, to the peripheral device interface 118. The I / O subsystem 106 optionally includes a display controller 156, a light sensor controller 158, a depth camera controller 169, an intensity sensor controller 159, a haptic feedback controller 161, and one or more input controllers 160 for other input devices or control devices. The one or more input controllers 160 receive electrical signals from and transmit electrical signals to the other input control devices 116. The other input control devices 116 optionally include physical buttons (e.g., push buttons, rocker buttons, etc.), dials, slider switches, joysticks, click wheels, and the like. In some alternative embodiments, the input controller(s) 160 are optionally coupled to (or not coupled to any of) a keyboard, an infrared port, a USB port, and pointer devices such as a mouse. One or more buttons (e.g., 208 of FIG. 2) optionally include up and down buttons for volume control of the speaker 111 and / or the microphone 113. One or more buttons optionally include push buttons (e.g., 206 of FIG. 2).
[0065] As described in U.S. Patent Application No. 11 / 322,549, filed December 23, 2005, "Unlocking a Device by Performing Gestures on an Unlock Image", and U.S. Patent No. 7,657,849, which are hereby incorporated by reference in their entirety, a quick press of a push button optionally engages or disengages the lock of the touch screen 112, or optionally initiates a process of unlocking the device using gestures on the touch screen. A longer press of the push button (e.g., 206) optionally turns the power to the device 100 on or off. The functionality of one or more of the buttons is optionally customizable by the user. The touch screen 112 is used to implement virtual or soft buttons and one or more soft keyboards.
[0066] 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 transmits electrical signals to the touch screen 112. The touch screen 112 displays a visual output to the user. This visual output optionally includes graphics, text, icons, video, 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.
[0067] The touch screen 112 has a touch sensing surface, sensor, or set of sensors that accepts input from a user based on tactile and / or haptic contact. The touch screen 112 and the display controller 156 (along with any associated modules and / or instruction sets in the memory 102) detect contacts (and any movement or interruption of the contacts) on the touch screen 112 and convert the detected contacts into an interaction with user interface objects (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.
[0068] The touch screen 112 optionally uses LCD (liquid crystal display) technology, LPD (light emitting polymer display) technology, or LED (light emitting diode) technology, although in other embodiments other display technologies are also used. The touch screen 112 and the display controller 156 optionally use any of a plurality of currently known or later developed touch sensing technologies, 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 contacts and any movement or interruption thereof. In an exemplary embodiment, a projected mutual capacitance sensing technology such as that found in the iPhone (registered trademark) and iPod Touch (registered trademark) from Apple Inc. of Cupertino, California, is used.
[0069] The touch-sensing display in some embodiments of touch screen 112 is optionally similar to a multi-touch sensing touch pad as described in U.S. Patent Nos. 6,323,846 (Westerman et al.), 6,570,557 (Westerman et al.), and / or 6,677,932 (Westerman), and / or U.S. Patent Publication No. 2002 / 0015024A1, each of which is hereby incorporated by reference in its entirety. However, touch screen 112 displays visual output from device 100, whereas a touch-sensing touch pad does not provide visual output.
[0070] Touch sensing displays in some embodiments of touch screen 112 are described in (1) U.S. Patent Application No. 11 / 381,313, filed May 2, 2006, "Multipoint Touch Surface Controller"; (2) U.S. Patent Application No. 10 / 840,862, filed May 6, 2004, "Multipoint Touchscreen"; (3) U.S. Patent Application No. 10 / 903,964, filed Jul. 30, 2004, "Gestures For Touch Sensitive Input Devices"; (4) U.S. Patent Application No. 11 / 048,264, filed Jan. 31, 2005, "Gestures For Touch Sensitive Input Devices"; (5) U.S. Patent Application No. 11 / 038,590, filed Jan. 18, 2005, "Mode-Based Graphical User Interfaces For Touch Sensitive Input Devices"; (6) U.S. Patent Application No. 11 / 228,758, filed Sep. 16, 2005, "Virtual Input Device Placement On A Touch Screen User Interface"; (7) U.S. Patent Application No. 11 / 228,700, filed Sep. 16, 2005, "Operation Of A Computer With A Touch Screen Interface"; (8) U.S. Patent Application No. 11 / 228,737, filed Sep. 16, 2005, "Activating Virtual Keys Of A Touch-Screen Virtual Keyboard"; and (9) U.S. Patent Application No. 11 / 367,749, filed Mar. 3, 2006, "Multi-Functional Hand-Held Device". All of these applications are hereby incorporated by reference in their entirety.
[0071] The touch screen 112 optionally has a video resolution greater than 100 dpi. In some embodiments, the touch screen has a video resolution of about 160 dpi. The user optionally touches the touch screen 112 using any suitable object or appendage such as a stylus, finger, etc. In some embodiments, the user interface is designed to primarily handle finger contact and gestures, although this may be less precise than stylus-based input due to the larger contact area of the finger on the touch screen. In some embodiments, the device converts rough input by the finger into an accurate pointer / cursor position or command for performing the action desired by the user.
[0072] In some embodiments, in addition to the touch screen, the device 100 optionally includes a touch pad for activating or deactivating certain functions. In some embodiments, the touch pad, unlike the touch screen, is a touch-sensitive area of the device that does not display a visual output. The touch pad is optionally a touch-sensitive surface separate from the touch screen 112 or an extension of the touch-sensitive surface formed by the touch screen.
[0073] The device 100 also includes a power system 162 that supplies power to various components. The power system 162 optionally includes a power management system, one or more power sources (e.g., battery, alternating current (AC)), a recharge system, a power outage detection circuit, a power converter or inverter, a power status indicator (e.g., light-emitting diode (LED)), and any other components associated with the generation, management, and distribution of power within a portable device.
[0074] Device 100 also optionally includes one or more light sensors 164. FIG. 1A shows a light sensor coupled to a light sensor controller 158 within I / O subsystem 106. The light sensor 164 optionally includes a charge-coupled device (CCD) or a complementary metal-oxide semiconductor (CMOS) phototransistor. The light sensor 164 receives light from the environment projected through one or more lenses and converts the light into data representing an image. The light sensor 164, in cooperation with imaging module 143 (also referred to as a camera module), optionally captures a still image or video. In some embodiments, the light sensor is located on the back surface of device 100 opposite touch screen display 112 on the front surface of the device, and thus the touch screen display can be effectively used as a viewfinder for acquiring still and / or video images. In some embodiments, the light sensor is disposed on the front surface of the device, and thus an image of the user can optionally be obtained for a video conference, and the user can view other video conference participants on the touch screen display. In some embodiments, the position of the light sensor 164 can be changed by the user (e.g., by rotating the lens and sensor within the device housing), and thus a single light sensor 164 can be used for both video conferencing and for acquiring still and / or video images in conjunction with the touch screen display.
[0075] Device 100 also optionally includes one or more depth camera sensors 175. FIG. 1A shows a depth camera sensor coupled to a depth camera controller 169 within the I / O subsystem 106. The depth camera sensor 175 receives data from the environment and creates a three-dimensional model of an object (e.g., a face) within the scene from the perspective (e.g., the depth camera sensor). In some embodiments, in cooperation with the imaging module 143 (also referred to as the camera module), the depth camera sensor 175 is optionally used to determine depth maps for various portions of an image captured by the imaging module 143. In some embodiments, while a user is viewing other video conference participants on a touch screen display, an image of the user with depth information is optionally acquired for the video conference and a self-portrait image with depth map data is captured, a depth camera sensor is disposed on the front surface of the device 100. In some embodiments, the depth camera sensor 175 is disposed on the back surface of the device, or on both the back and front surfaces of the device 100. In some embodiments, the position of the depth camera sensor 175 can be changed by the user (e.g., by rotating the lens and sensor within the device housing), and thus the depth camera sensor 175 is used for video conferencing as well as for acquiring still and / or video images with the touch screen display.
[0076] Device 100 also optionally includes one or more contact intensity sensors 165. FIG. 1A shows a contact intensity sensor coupled to an intensity sensor controller 159 within I / O subsystem 106. The contact intensity sensor 165 optionally includes one or more piezoresistive strain gauges, capacitive force sensors, electrokinetic sensors, piezoelectric force sensors, optical force sensors, capacitive touch sensing surfaces, or other intensity sensors (e.g., sensors used to measure the force (or pressure) of contact on a touch sensing surface). The contact intensity sensor 165 receives contact intensity information (e.g., pressure information, or a proxy for pressure information) from the environment. In some embodiments, at least one contact intensity sensor is juxtaposed with, or proximate to, a touch sensing surface (e.g., touch sensing display system 112). In some embodiments, at least one contact intensity sensor is disposed on the back of device 100, opposite a touch screen display 112 disposed on the front of device 100.
[0077] Device 100 also optionally includes one or more proximity sensors 166. FIG. 1A shows a proximity sensor 166 coupled to the peripheral device interface 118. Alternatively, the proximity sensor 166 is optionally coupled to the input controller 160 within the I / O subsystem 106. The proximity sensor 166 functions as described in U.S. Patent Application Nos. 11 / 241,839, "Proximity Detector In Handheld Device", 11 / 240,788, "Proximity Detector In Handheld Device", 11 / 620,702, "Using Ambient Light Sensor To Augment Proximity Sensor Output", 11 / 586,862, "Automated Response To And Sensing Of User Activity In Portable Devices", and 11 / 638,251, "Methods And Systems For Automatic Configuration Of Peripherals", which are hereby incorporated by reference in their entirety. In some embodiments, when a multifunctional device is placed near the user's ear (e.g., when the user is on a phone call), the proximity sensor turns off and disables the touch screen 112.
[0078] Device 100 also optionally includes one or more haptic output generators 167. FIG. 1A shows a haptic output generator coupled to a haptic feedback controller 161 within I / O subsystem 106. The haptic output generator 167 optionally includes one or more electroacoustic devices such as speakers or other audio components, and / or electromechanical devices that convert energy, such as motors, solenoids, electroactive polymers, piezoelectric actuators, electrostatic actuators, or other haptic output generating components (e.g., components that convert an electrical signal into a haptic output on the device), into linear movement. The contact intensity sensor 165 receives haptic feedback generation instructions from the haptic feedback module 133 and generates a haptic output on device 100 that can be sensed by a user of device 100. In some embodiments, at least one haptic output generator is juxtaposed with, or proximate to, a touch sensing surface (e.g., touch sensing display system 112), and optionally generates a haptic output by moving the touch sensing surface in a vertical direction (e.g., in / out of the surface of device 100) or a horizontal direction (e.g., back and forth within the same plane as the surface of device 100). In some embodiments, at least one haptic output generator sensor is disposed on the back of device 100, which is opposite the touch screen display 112 disposed on the front of device 100.
[0079] In addition, device 100 optionally 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 within the I / O subsystem 106. The accelerometer 168 functions as described, for example, in U.S. Patent Publication No. 20050170059, "Acceleration-based Theft Detection System for Portable Electronic Devices," and U.S. Patent Publication No. 20060017692, "Methods And Apparatuses For Operating A Portable Device Based On An Accelerometer," both of which are hereby incorporated by reference in their entireties. In some embodiments, information is displayed on the touch screen display in portrait or landscape view based on analysis of data received from one or more accelerometers. In addition to the accelerometer 168, device 100 optionally includes a magnetometer and a GPS (or GLONASS or other global navigation system) receiver for obtaining information regarding the location and orientation (e.g., vertical or horizontal) of the device 100.
[0080] In some embodiments, the software components stored in memory 102 include an operating system 126, a communication module (or instruction set) 128, a touch / 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. Further, in some embodiments, memory 102 (FIG. 1A) or 370 (FIG. 3) stores a device / global internal state 157 as shown in FIGS. 1A and 3. The device / global internal state 157 includes, when there is a currently active application, an active application state indicating which application is active, a display state indicating which application, view, or other information occupies various regions 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 regarding the position and / or orientation of the device, among one or more of them.
[0081] The operating system 126 (e.g., an embedded operating system such as Darwin (registered trademark), RTXC (registered trademark), LINUX (registered trademark), UNIX (registered trademark), OS X (registered trademark), iOS (registered trademark), WINDOWS (registered trademark), or VxWorks (registered trademark)) includes various software components and / or drivers that control and manage general system tasks (e.g., memory management, control of storage devices, power management, etc.) and facilitate communication between various hardware components and software components.
[0082] The communication module 128 facilitates communication with other devices via 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 ports 124 (e.g., Universal Serial Bus (USB), FIREWIRE (registered trademark), etc.) are adapted to couple to other devices either directly or indirectly via a network (e.g., the Internet, a wireless LAN, etc.). In some embodiments, the external port is a multi-pin (e.g., 30-pin) connector that is the same as or similar to and / or compatible with the 30-pin connector used on iPod (registered trademark) devices (a trademark of Apple Inc.).
[0083] The contact / motion module 130 optionally detects contact with the touch screen 112 (in cooperation with the display controller 156) and other touch sensing devices (e.g., a touch pad or a physical click wheel). The contact / motion module 130 performs various operations related to the detection of contact, such as determining whether contact has occurred (e.g., detecting an event of a finger being lowered), determining the intensity of the contact (e.g., the force or pressure of the contact, or an alternative to the force or pressure of the contact), determining whether there is movement of the contact, tracking movement across the touch sensing surface (e.g., detecting one or more events of a finger being dragged), and determining whether the contact has stopped (e.g., detecting an event of a finger being raised or an interruption of the contact), including various software components for performing these operations. The contact / motion module 130 receives contact data from the touch sensing surface. Determining the movement of the contact point, represented by a series of contact data, optionally includes determining the speed (magnitude), velocity (magnitude and direction), and / or acceleration (change in magnitude and / or direction) of the contact point. These operations are optionally applied to a single contact (e.g., the contact of one finger) or multiple simultaneous contacts (e.g., "multi-touch" / contact of multiple fingers). In some embodiments, the contact / motion module 130 and the display controller 156 detect contact on the touch pad.
[0084] In some embodiments, the contact / motion module 130 uses a set of one or more intensity thresholds to determine whether an action has been performed by the user (e.g., to determine whether the user has "clicked" on an icon). In some embodiments, at least one subset of the intensity thresholds is determined according to software parameters (e.g., the intensity thresholds can be adjusted without changing the physical hardware of the device 100, rather than being determined by the activation thresholds of specific physical actuators). For example, the mouse "click" threshold for a trackpad or touchscreen display can be set to any of a wide range of default thresholds without changing the trackpad or touchscreen display hardware. Additionally, in some implementations, the user of the device is provided with software settings for adjusting one or more of the set of intensity thresholds (e.g., by adjusting individual intensity thresholds and / or adjusting multiple intensity thresholds at once with a system-level click "intensity" parameter).
[0085] The contact / motion module 130 optionally detects gesture inputs by the user. Different gestures on the touch-sensing surface have different contact patterns (e.g., the detected movement, timing, and / or intensity of the contact is different). Thus, gestures are optionally detected by detecting a specific contact pattern. For example, detecting a finger tap gesture includes detecting a finger down event followed by a finger up (lift off) event at the same position (or substantially the same position) as the finger down event (e.g., the position of an icon). As another example, detecting a finger swipe gesture on the touch-sensing surface includes detecting a finger down event followed by one or more finger drag events followed by a finger up (lift off) event.
[0086] The graphic module 132 includes various known software components for rendering and displaying graphics on the touch screen 112 or other display, including components that vary the visual impact of the displayed graphics (e.g., brightness, transparency, saturation, contrast, or other visual characteristics). As used herein, the term "graphic" includes, but is not limited to, any object that can be displayed to a user, including letters, web pages, icons (such as user interface objects including soft keys), digital images, videos, animations, and the like.
[0087] In some embodiments, the graphic module 132 stores data representing the graphics that will be used. Each graphic is optionally assigned a corresponding code. The graphic module 132 receives from an application, as needed, one or more codes that specify the graphic to be displayed, along with coordinate data and other graphic characteristic data, and then generates the image data for the screen to be output to the display controller 156.
[0088] The haptic feedback module 133 includes various software components for generating instructions to be used by the haptic output generator(s) 167 to generate haptic output at one or more locations on the device 100 in response to user interaction with the device 100.
[0089] The text input module 134 is optionally a component of the graphic module 132 and provides a soft keyboard for entering text in various applications (e.g., contacts 137, email 140, IM 141, browser 147, and any other application that requires text input).
[0090] 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 location-based dialing, to the camera 143 as metadata for photos / videos, and to applications that provide location-based services such as a weather widget, a local yellow pages widget, and a map / navigation widget).
[0091] The application 136 optionally includes the following modules (or sets of instructions) or subsets or supersets thereof. ● A contacts module 137 (sometimes referred to as an address book or contacts list), ● A phone module 138, ● A video conferencing module 139, ● An email client module 140, ● An instant messaging (IM) module 141, ● A training support module 142, ● A camera module 143 for still and / or video images, ● An image management module 144, ● A video player module, ● A music player module, ● A browser module 147, ● A calendar module 148, ● A widget module 149 that optionally includes one or more of a weather widget 149-1, a stock widget 149-2, a calculator widget 149-3, an alarm clock widget 149-4, a dictionary widget 149-5, and other widgets obtained by the user, as well as a user-created widget 149-6, ● A widget creation module 150 for creating the user-created widget 149-6, ● A search module 151, ● A video and music player module 152 that integrates the video player module and the music player module ● Memo module 153, ● Map module 154, and / or, ● Online video module 155.
[0092] Examples of other applications 136 optionally stored in the memory 102 include other word processing applications, other image editing applications, drawing applications, presentation applications, JAVA (registered trademark)-compatible applications, encryption, digital rights management, speech recognition, and speech reproduction.
[0093] In cooperation with the touch screen 112, the display controller 156, the contact / motion module 130, the graphic module 132, and the text input module 134, the contact module 137 optionally adds a name(s) to the address book, deletes a name(s) from the address book, associates a phone number(s), an email address(es), a physical address(es), or other information with a name, associates an image with a name, classifies and sorts names, provides a phone number or email address to initiate and / or facilitate communication by phone 138, the video conferencing module 139, email 140, or IM 141, etc., and is used to manage the address book or contact list (e.g., stored in the internal application state 192 of the contact module 137 in the memory 102 or the memory 370).
[0094] In cooperation with the RF circuit 108, the audio circuit 110, the speaker 111, the microphone 113, the touch screen 112, the display controller 156, the contact / motion module 130, the graphic module 132, and the text input module 134, the telephone module 138 is optionally used for input of a character sequence corresponding to a telephone number, access to one or more telephone numbers in the contact module 137, modification of the input telephone number, dialing of each telephone number, conducting a conversation, and call stop or hang-up when the conversation ends. As described above, the wireless communication optionally uses any of a plurality of communication standards, protocols, and technologies.
[0095] In cooperation 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 graphic module 132, the text input module 134, the contact module 137, and the telephone module 138, the videoconference module 139 includes executable instructions for starting, executing, and ending a videoconference between the user and one or more other participants according to a user instruction.
[0096] In cooperation with the RF circuit 108, the touch screen 112, the display controller 156, the contact / motion module 130, the graphic module 132, and the text input module 134, the email client module 140 includes executable instructions for creating, sending, receiving, and managing emails according to a user instruction. In cooperation with the image management module 144, the email client module 140 makes it very easy to create and send emails with still images or video images captured by the camera module 143.
[0097] In cooperation with the RF circuit 108, touch screen 112, display controller 156, contact / motion module 130, graphic module 132, and text input module 134, the instant messaging module 141 includes executable instructions for inputting a character sequence corresponding to an instant message, modifying previously input characters, transmitting each instant message (e.g., using the Short Message Service (SMS) or Multimedia Message Service (MMS) protocol for phone communication-based instant messages, or XMPP, SIMPLE, or IMPS for Internet-based instant messages), receiving instant messages, and viewing received instant messages. In some embodiments, the instant messages transmitted and / or received optionally include graphics, photos, audio files, video files, and / or other attached files supported by MMS and / or Enhanced Messaging Service (EMS). As used herein, "instant messaging" refers to both phone communication-based messages (e.g., messages transmitted using SMS or MMS) and Internet-based messages (e.g., messages transmitted using XMPP, SIMPLE, or IMPS).
[0098] In cooperation with the RF circuit 108, touch screen 112, display controller 156, contact / motion module 130, graphic module 132, text input module 134, GPS module 135, map module 154, and music player module, the training support module 142 creates training (e.g., having time, distance, and / or calorie burn goals), communicates with a training sensor (sports device), receives training sensor data, calibrates sensors used to monitor the training, selects and plays music for the training, and includes executable instructions for displaying, storing, and transmitting training data.
[0099] In cooperation with the touch screen 112, display controller 156, light sensor(s) 164, light sensor controller 158, contact / motion module 130, graphic module 132, and image management module 144, the camera module 143 includes executable instructions for capturing a still image or video (including a video stream) and storing it in the memory 102, modifying the characteristics of a still image or video, or deleting a still image or video from the memory 102.
[0100] In cooperation with the touch screen 112, display controller 156, contact / motion module 130, graphic module 132, text input module 134, and camera module 143, the image management module 144 includes executable instructions for arranging, modifying (e.g., editing), or otherwise operating on still images and / or video images, labeling, deleting, presenting (e.g., in a digital slide show or album), and storing them.
[0101] In cooperation with the RF circuit 108, touch screen 112, display controller 156, contact / motion module 130, graphic module 132, and text input module 134, the browser module 147 includes executable instructions for browsing the Internet according to user commands, including searching for, linking to, receiving, and displaying a web page or a portion thereof, as well as attached files and other files linked to the web page.
[0102] In cooperation with the RF circuit 108, touch screen 112, display controller 156, contact / motion module 130, graphic module 132, text input module 134, email client module 140, and browser module 147, the calendar module 148 includes executable instructions for creating, displaying, modifying, and storing a calendar and data associated with the calendar (e.g., calendar items, to do lists, etc.) according to user instructions.
[0103] In cooperation with the RF circuit 108, touch screen 112, display controller 156, contact / motion module 130, graphic module 132, text input module 134, and browser module 147, the widget module 149 is a mini-application (e.g., weather widget 149-1, stock widget 149-2, calculator widget 149-3, alarm clock widget 149-4, and dictionary widget 149-5) that is optionally downloaded and used by the user, or a mini-application (e.g., user-created widget 149-6) created by the user. In some embodiments, the widget includes an HTML (Hypertext Markup Language) file, a CSS (Cascading Style Sheets) file, and a JavaScript file. In some embodiments, the widget includes an XML (Extensible Markup Language) file and a JavaScript file (e.g., Yahoo! widget).
[0104] In cooperation with the RF circuit 108, touch screen 112, display controller 156, contact / motion module 130, graphic module 132, text input module 134, and browser module 147, the widget creator module 150 is optionally used by the user to create a widget (e.g., turn a user-specified portion of a web page into a widget).
[0105] In cooperation with the touch screen 112, display controller 156, contact / motion module 130, graphic module 132, and text input module 134, the search module 151 includes executable instructions for searching for characters, music, sound, images, video, and / or other files in the memory 102 that match one or more search criteria (e.g., one or more user-specified search terms) according to a user command.
[0106] In cooperation with touch screen 112, display controller 156, contact / motion module 130, graphic module 132, audio circuit 110, speaker 111, RF circuit 108, and browser module 147, video and music player module 152 includes executable instructions that enable a user to download and play 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 videos (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.).
[0107] In cooperation with touch screen 112, display controller 156, contact / motion module 130, graphic module 132, and text input module 134, memo module 153 includes executable instructions for creating and managing memos, to do lists, etc. according to user instructions.
[0108] In cooperation with RF circuit 108, touch screen 112, display controller 156, contact / motion module 130, graphic module 132, text input module 134, GPS module 135, and browser module 147, map module 154 is optionally used to receive, display, modify, and store maps and map-related data (e.g., driving directions, data regarding stores and other target locations near or at a particular location, and other location-based data) according to user instructions.
[0109] In cooperation with touch screen 112, display controller 156, contact / motion module 130, graphic 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 that enable a user to access a particular online video, browse a particular online video, receive (e.g., by streaming and / or downloading), play (e.g., on the touch screen or on an external display connected via external port 124), send an email having a link to a particular online video, and perform other management of online videos in one or more file formats such as H.264. In some embodiments, an instant messaging module 141 is used instead of email client module 140 to send a link to a particular online video. Additional explanation of the online video application can be found in U.S. Provisional Patent Application No. 60 / 936,562, filed Jun. 20, 2007, "Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos", and U.S. Patent Application No. 11 / 968,067, filed Dec. 31, 2007, "Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos", the contents of which are hereby incorporated by reference in their entirety.
[0110] The modules and applications identified above each correspond to a set of executable instructions that perform one or more of the functions described above and the methods described in this application (e.g., the computer-implemented methods and other information processing methods described herein). These modules (e.g., instruction sets) need not be implemented as separate software programs, procedures, or modules, and thus, in various embodiments, various subsets of these modules may optionally be combined or otherwise reconfigured. For example, the video player module may optionally be combined with the music player module to form a single module (e.g., the video and music player module 152 of FIG. 1A). In some embodiments, the memory 102 optionally stores a subset of the modules and data structures identified above. Further, the memory 102 optionally stores additional modules and data structures not described above.
[0111] In some embodiments, the device 100 is a device in which the operation of a set of default functions in the device is performed only via a touch screen and / or a touch pad. By using the touch screen and / or the touch pad as the main input control device for the device 100 to operate, the number of physical input control devices (push buttons, dials, etc.) on the device 100 is optionally reduced.
[0112] The set of default functions that are performed only through the touch screen and / or the touch pad optionally includes navigation between user interfaces. In some embodiments, the touch pad navigates the device 100 from any user interface displayed on the device 100 to the main menu, home menu, or root menu when touched by the user. In such embodiments, the "menu button" is implemented using the touch pad. In some other embodiments, the menu button is a physical push button or other physical input control device rather than the touch pad.
[0113] FIG. 1B is a block diagram showing exemplary components for event processing according to some embodiments. In some embodiments, memory 102 (FIG. 1A) or 370 (FIG. 3) includes an event sorter 170 (e.g., within operating system 126) and respective applications 136-1 (e.g., any of the aforementioned applications 137-151, 155, 380-390).
[0114] The event sorter 170 receives event information and determines the application 136-1 to which the event information is to be delivered and the application view 191 of the application 136-1. The event sorter 170 includes an event monitor 171 and an event dispatcher module 174. In some embodiments, the application 136-1 includes an application internal state 192 that indicates the current application view(s) displayed on the touch-sensitive display 112 when the application is active or running. In some embodiments, the device / global internal state 157 is used by the event sorter 170 to determine which application(s) is / are currently active, and the application internal state 192 is used by the event sorter 170 to determine the application view 191 to which the event information is to be delivered.
[0115] In some embodiments, the application internal state 192 includes additional information such as resume information to be used when the application 136-1 resumes execution, user interface state information indicating or ready to display the information being displayed by the application 136-1, a state queue that enables the user to return to the previous state or view of the application 136-1, and a redo / undo queue of previous actions performed by the user.
[0116] The event monitor 171 receives event information from the peripheral device interface 118. The event information includes information regarding sub-events (e.g., a user touch on the touch-sensing display 112 as part of a multi-touch gesture). The peripheral device interface 118 transmits information received from the I / O subsystem 106, or sensors such as the proximity sensor 166, the accelerometer(s) 168, and / or the microphone 113 (via the audio circuit 110). The information that the peripheral device interface 118 receives from the I / O subsystem 106 includes information from the touch-sensing display 112 or the touch-sensing surface.
[0117] In some embodiments, the event monitor 171 transmits requests to the peripheral device interface 118 at predetermined intervals. In response, the peripheral device interface 118 transmits event information. In other embodiments, the peripheral device interface 118 transmits event information only when there is a significant event (e.g., receipt of an input that exceeds a predetermined noise threshold and / or exceeds a predetermined duration).
[0118] In some embodiments, the event sorter 170 also includes a hit view determination module 172 and / or an active event recognition unit determination module 173.
[0119] The hit view determination module 172 provides a software procedure for determining where within one or more views a sub-event has occurred when the touch-sensing display 112 displays two or more views. A view is composed of control devices and other elements that a user can view on the display.
[0120] Another aspect of the user interface associated with an application is a set of views, sometimes referred to herein as application views or user interface windows, in which information is displayed and touch-based gestures occur. The application views (for each respective application) where touches are detected optionally correspond to a program level within the program hierarchy or view hierarchy of the application. For example, the lowest-level view where a touch is detected is optionally referred to as the hit view, and the set of events recognized as appropriate input is optionally determined based at least in part on the hit view of the initial touch that initiates the touch-based gesture.
[0121] The hit view determination module 172 receives information related to sub-events of touch-based gestures. When the application has a plurality of hierarchically structured views, the hit view determination module 172 identifies the hit view as the lowest-level view within the hierarchy in which the sub-events are to be processed. In most situations, the hit view is the lowest-level view where the start sub-event (e.g., the first sub-event within a sequence of sub-events that form an event or potential event) occurs. Once the hit view is identified by the hit view determination module 172, this hit view typically receives all sub-events related to the same touch or input source that was identified as the hit view.
[0122] The active event recognition unit determination module 173 determines which view(s) within the view hierarchy should receive a particular sequence of sub-events. In some embodiments, the active event recognition unit determination module 173 determines that only the hit view should receive a particular sequence of sub-events. In other embodiments, the active event recognition unit determination module 173 determines that all views including the physical location of the sub-event are views that are actively involved, and thus, determines that all views that are actively involved should receive a particular sequence of sub-events. In other embodiments, even if a touch sub-event is completely limited to an area associated with one particular view, the upper-level views within the hierarchy continue to be views that are actively involved.
[0123] The event dispatcher module 174 dispatches event information to an event recognition unit (e.g., event recognition unit 180). In embodiments including the active event recognition unit determination module 173, the event dispatcher module 174 distributes event information to the event recognition unit determined by the active event recognition unit determination module 173. In some embodiments, the event dispatcher module 174 stores the event information obtained by each event receiver 182 in an event queue.
[0124] In some embodiments, the operating system 126 includes an event sorter 170. Alternatively, the application 136-1 includes an event sorter 170. In still other embodiments, the event sorter 170 is a stand-alone module or a part of another module stored in the memory 102 such as the touch / motion module 130.
[0125] In some embodiments, Application 136-1 includes a plurality of event processing units 190 and one or more application views 191, each including instructions for processing touch events that occur within respective views of the user interface of the application. Each application view 191 of Application 136-1 includes one or more event recognition units 180. Typically, each application view 191 includes a plurality of event recognition units 180. In other embodiments, one or more of the event recognition units 180 are part of a separate module, such as a user interface kit or a higher-level object from which Application 136-1 inherits methods and other attributes. In some embodiments, each event processing unit 190 includes one or more of event data 179 received from data update unit 176, object update unit 177, GUI update unit 178, and / or event sorter 170. The event processing unit 190 optionally utilizes or invokes the data update unit 176, object update unit 177, or GUI update unit 178 to update the internal state 192 of the application. Alternatively, one or more of the application views 191 include one or more respective event processing units 190. Also, in some embodiments, one or more of the data update unit 176, object update unit 177, and GUI update unit 178 are included in respective application views 191.
[0126] Each event recognition unit 180 receives event information (e.g., event data 179) from event sorter 170 and identifies an event from this event information. The event recognition unit 180 includes an event receiving unit 182 and an event comparing unit 184. In some embodiments, the event recognition unit 180 also includes at least a subset of metadata 183 and event distribution instructions 188 (optionally including sub-event distribution instructions).
[0127] The event receiving unit 182 receives event information from the event sorter 170. The event information includes sub-events, for example, information about a touch or a movement of a touch. Depending on the sub-event, the event information also includes additional information such as the position of the sub-event. When the sub-event is related to the movement of a touch, the event information also optionally includes the speed and direction of the sub-event. In some embodiments, the event includes a rotation of the device from one orientation to another (e.g., from portrait to landscape or vice versa), and the event information includes corresponding information about the current orientation of the device (also referred to as the posture of the device).
[0128] The event comparison unit 184 compares the event information with the definition of a defined event or sub-event, and based on the comparison, determines an event or sub-event, or determines or updates the state of an event or sub-event. In some embodiments, the event comparison unit 184 includes an event definition 186. The event definition 186 includes definitions of events (e.g., a sequence of predefined sub-events) such as event 1 (187-1) and event 2 (187-2). In some embodiments, the sub-events within an event (187) include, for example, a touch start, a touch end, a touch movement, a touch cancellation, and multiple touches. In one example, the definition of event 1 (187-1) is a double-tap on a displayed object. The double-tap includes, for example, a first touch (touch start) on the displayed object for a predetermined stage, a first lift-off (touch end) for the predetermined stage, a second touch (touch start) on the displayed object for the predetermined stage, and a second lift-off (touch end) for the predetermined stage. In another example, the definition of event 2 (187-2) is a drag on a displayed object. The drag includes, for example, a touch (or contact) on the displayed object for a predetermined stage, a movement of the touch across the touch-sensitive display 112, and a lift-off of the touch (touch end). In some embodiments, the event also includes information about one or more associated event processing units 190.
[0129] In some embodiments, event definition 187 includes the definition of events for each user interface object. In some embodiments, event comparison unit 184 performs a hit test to determine which user interface object is associated with the sub - event. For example, within an application view where three user interface objects are displayed on touch - sensitive display 112, when a touch is detected on touch - sensitive display 112, event comparison unit 184 performs a hit test to determine which of the three user interface objects is associated with the touch (sub - event). If each of the displayed objects is associated with a respective event processing unit 190, the event comparison unit determines which event processing unit 190 should be activated using the result of the hit test. For example, event comparison unit 184 selects the event processing unit associated with the sub - event and object that triggered the hit test.
[0130] In some embodiments, the definition of each event 187 also includes a delay action that delays the delivery of event information until it is determined whether the sequence of sub - events corresponds to the event type of the event recognition unit.
[0131] If each event recognition unit 180 determines that a series of sub - events does not match any of the events of event definition 186, each event recognition unit 180 enters a state of event impossible, event failure, or event end, and then ignores the next sub - event of the touch - based gesture. In this situation, if there are other event recognition units that remain active for the hit view, that event recognition unit continues to track and process the sub - events of the ongoing touch - based gesture.
[0132] In some embodiments, each event recognition unit 180 includes metadata 183 having configurable properties, flags, and / or lists indicating how the event delivery system should actively participate in event recognition units that perform sub-event delivery. In some embodiments, the metadata 183 includes configurable properties, flags, and / or lists indicating how the event recognition units interact with each other or how they can interact with each other. In some embodiments, the metadata 183 includes configurable properties, flags, and / or lists indicating whether sub-events are delivered to various levels in the view hierarchy or program hierarchy.
[0133] In some embodiments, each event recognition unit 180 activates the event processing unit 190 associated with the event when one or more specific sub-events of the event are recognized. In some embodiments, each event recognition unit 180 distributes event information associated with the event to the event processing unit 190. Activating the event processing unit 190 is separate from sending (and deferring sending) sub-events to each hit view. In some embodiments, the event recognition unit 180 sets a flag associated with the recognized event, and the event processing unit 190 associated with the flag catches the flag and executes a predefined process.
[0134] In some embodiments, the event delivery command 188 includes a sub-event delivery command that distributes event information about sub-events without activating the event processing unit. Instead, the sub-event delivery command distributes event information to an event processing unit associated with a series of sub-events or to a view actively involved, and the event processing unit associated with the series of sub-events or the actively involved view receives the event information and performs predetermined processing.
[0135] In some embodiments, data update unit 176 creates and updates data used in application 136-1. For example, data update unit 176 updates the phone numbers used in contact module 137 or stores video files used in the video player module. In some embodiments, object update unit 177 creates and updates objects used in application 136-1. For example, object update unit 177 creates a new user interface object or updates the position of a user interface object. GUI update unit 178 updates the GUI. For example, GUI update unit 178 prepares display information and sends the display information to graphic module 132 for display on the touch-sensitive display.
[0136] In some embodiments, event processing unit(s) 190 includes or has access to data update unit 176, object update unit 177, and GUI update unit 178. In some embodiments, data update unit 176, object update unit 177, and GUI update unit 178 are included in a single module of their respective application 136-1 or application view 191. In other embodiments, they are included in two or more software modules.
[0137] It should be understood that the foregoing description regarding event processing of a user's touch on the touch-sensitive display also applies to other forms of user input for operating multifunctional device 100 using an input device, although not all of them are initiated on the touch screen. For example, movement of a mouse and pressing of a mouse button, movement of a contact such as a tap, drag, or scroll on a touch pad, pen stylus input, movement of the device, verbal commands, detected eye movements, biometric input, and / or any combination thereof, optionally in association with a single or multiple presses or holds of a keyboard, are used as input corresponding to sub-events that define events to be optionally recognized.
[0138] Figure 2 shows a portable multifunctional device 100 having 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, as well as in other embodiments described below, the user can select one or more of those graphics by performing gestures on the graphics using, for example, one or more fingers 202 (not drawn to scale in the figure) or one or more styli 203 (not drawn to scale in the figure). In some embodiments, the selection of one or more graphics is performed when the user interrupts contact with the one or more graphics. In some embodiments, the gestures optionally include one or more taps, one or more swipes (from left to right, from right to left, upward and / or downward), and / or rolling of a finger in contact with the device 100 (from right to left, from left to right, upward and / or downward). In some implementations or situations, an accidental contact with a graphic does not select that graphic. For example, if the gesture corresponding to selection is a tap, a swipe gesture that sweeps over an application icon does not optionally select the corresponding application.
[0139] The device 100 also optionally includes one or more physical buttons, such as a "home" button or a menu button 204. As described above, the menu button 204 is optionally used to navigate to any application 136 within a set of applications optionally running on the device 100. Alternatively, in some embodiments, the menu button is implemented as a soft key within a GUI displayed on the touch screen 112.
[0140] In some embodiments, device 100 includes a touch screen 112, a menu button 204, a push button 206 for turning the device on / off and locking the device, volume adjustment buttons 208, a subscriber identity module (SIM) card slot 210, a headset 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 holding it down for a predefined period, lock the device by pressing the button and releasing it before a predefined time has elapsed, and / or unlock the device or initiate an unlock process. In alternative embodiments, device 100 also accepts verbal input via a microphone 113 to activate or deactivate some functions. Device 100 also optionally includes one or more contact intensity sensors 165 for detecting the intensity of contact on the touch screen 112 and / or one or more haptic output generators 167 for generating haptic output to the user of device 100.
[0141] FIG. 3 is a block diagram of an exemplary multi-functional device having a display and a touch sensing surface, in accordance with some embodiments. Device 300 need not be portable. In some embodiments, device 300 is a laptop computer, a desktop computer, a tablet computer, a multimedia player device, a navigation device, an educational device (such as a child's learning toy), a gaming system, or a control device (e.g., a home or industrial controller). Device 300 typically includes one or more processing units (CPUs) 310, one or more networks or other communication interfaces 360, memory 370, and one or more communication buses 320 interconnecting these components. Communication bus 320 optionally includes circuitry (sometimes called a chipset) that interconnects and controls communications between system components. Device 300 includes an input / output (I / O) interface 330 that includes a display 340, which is typically a touch screen display. I / O interface 330 also optionally includes a keyboard and / or mouse (or other pointing device) 350, a touch pad 355, a haptic output generator 357 that generates haptic output on device 300 (e.g., similar to haptic output generator 167 described above with reference to FIG. 1A), and a sensor 359 (e.g., a light, acceleration, proximity, touch sensing, and / or contact intensity sensor similar to contact intensity sensor 165 described above with reference to FIG. 1A). Memory 370 includes high-speed random access memory such as DRAM, SRAM, DDR RAM, or other random access solid state memory devices, and optionally includes non-volatile memory such as one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid state storage devices. Memory 370 optionally includes one or more storage devices remotely located from the CPU(s) 310.In some embodiments, the memory 370 stores programs, modules, and data structures similar to, or a subset of, the programs, modules, and data structures stored in the memory 102 of the portable multifunctional device 100 (FIG. 1A). Further, the memory 370 optionally stores additional programs, modules, and data structures that do not exist in the memory 102 of the portable multifunctional device 100. For example, the memory 370 of the device 300 optionally stores a drawing module 380, a presentation module 382, a word processing module 384, a website creation module 386, a disk authoring module 388, and / or a spreadsheet module 390, whereas the memory 102 of the portable multifunctional device 100 (FIG. 1A) optionally does not store these modules.
[0142] Each of the elements identified above in FIG. 3 is optionally stored in one or more of the memory devices described above. Each of the modules identified above corresponds to a set of instructions for performing the functions described above. The modules or programs (e.g., sets of instructions) identified above need not be implemented as separate software programs, procedures, or modules, and thus in various embodiments, various subsets of these modules are optionally combined or otherwise reconfigured. In some embodiments, the memory 370 optionally stores a subset of the modules and data structures identified above. Further, the memory 370 optionally stores additional modules and data structures not described above.
[0143] Next, attention is optionally directed to embodiments of a user interface, for example, implemented on the portable multifunctional device 100.
[0144] Figure 4A shows an exemplary user interface of a menu of applications on a portable multifunctional device 100 according to some embodiments. A similar user interface is optionally implemented on device 300. In some embodiments, the user interface 400 includes the following elements, or a subset or superset thereof. ● One or more signal strength indicators (s) 402 for wireless communication (s), such as cellular signal and Wi-Fi (registered trademark) signal, ● Time 404, ● Bluetooth (registered trademark) indicator 405, ● Battery status indicator 406, ● A tray 408 having icons of frequently used applications, such as: ○ An icon 416 of the phone module 138 labeled "Phone", optionally including an indicator 414 of the number of missed calls or voice mail messages, ○ An icon 418 of the email client module 140 labeled "Mail", optionally including an indicator 410 of the number of unread emails, ○ An icon 420 of the browser module 147 labeled "Browser", and ○ An icon 422 of the video and music player module 152, also referred to as the iPod (trademark of Apple Inc.) module 152, labeled "iPod", and ● Icons of other applications, such as: ○ An icon 424 of the IM module 141 labeled "Message", ○ An icon 426 of the calendar module 148 labeled "Calendar", ○ An icon 428 of the image management module 144 labeled "Photos", ○ An icon 430 of the camera module 143 labeled "Camera", ○ An icon 432 of the online video module 155 labeled "Online Video", ○ The icon 434 of the stock widget 149-2 labeled with "Stock". ○ The icon 436 of the map module 154 labeled with "Map". ○ The icon 438 of the weather widget 149-1 labeled with "Weather". ○ The icon 440 of the alarm clock widget 149-4 labeled with "Clock". ○ The icon 442 of the training support module 142 labeled with "Training Support". ○ The icon 444 of the memo module 153 labeled with "Memo", and ○ The icon 446 of the settings application or module labeled with "Settings" that provides access to the settings for the device 100 and its various applications 136.
[0145] Note that the icon labels shown in Figure 4A are merely illustrative. For example, the icon 422 for the video and music player module 152 is displayed as "Music" or "Music Player". Other labels may optionally be used for the various application icons. In some embodiments, the label for each application icon includes the name of the application corresponding to that application icon. In some embodiments, the label for a particular application icon is different from the name of the application corresponding to that particular application icon.
[0146] Figure 4B shows an exemplary user interface on a device (e.g., device 300 of FIG. 3) having a touch sensing surface 451 (e.g., tablet or touch pad 355 of FIG. 3) separate from the display 450 (e.g., touch screen display 112). The device 300 also optionally includes one or more contact intensity sensors (e.g., one or more of sensors 359) that detect the intensity of contact on the touch sensing surface 451, and / or one or more haptic output generators 357 that generate haptic output to the user of the device 300.
[0147] Some of the following examples are given with reference to inputs on the touch screen display 112 (where the touch sensing surface and the display are combined), but in some embodiments, the device detects inputs on a touch sensing surface separate from the display shown in FIG. 4B. In some embodiments, the touch sensing surface (e.g., 451 of FIG. 4B) has a primary axis (e.g., 452 of FIG. 4B) corresponding to the primary axis (e.g., 453 of FIG. 4B) on the display (e.g., 450). According to these embodiments, the device detects contact (e.g., 460 and 462 of FIG. 4B) with the touch sensing surface 451 at locations (e.g., in FIG. 4B, 460 corresponds to 468 and 462 corresponds to 470) corresponding to each location on the display. In this way, user input (e.g., contacts 460 and 462 and their movements) detected by the device on the touch sensing surface (e.g., 451 of FIG. 4B) is used by the device to operate the user interface on the display (e.g., 450 of FIG. 4B) of the multifunctional device when the touch sensing surface is separate from the display. It should be understood that a similar method is optionally used for other user interfaces described herein.
[0148] In addition, the following examples are given mainly with reference to finger inputs (e.g., finger contact, finger tap gesture, finger swipe gesture), but it should be understood that in some embodiments, one or more of the finger inputs may be replaced by inputs from another input device (e.g., mouse-based input or stylus input). For example, a swipe gesture may optionally be replaced by the movement of a cursor along a swipe path following a mouse click (e.g., instead of contact movement). As another example, a tap gesture may optionally be replaced by a mouse click while the cursor is positioned over the location of the tap gesture (e.g., instead of detecting contact and subsequently stopping the detection of the contact). Similarly, when multiple user inputs are detected simultaneously, it should be understood that multiple computer mice may optionally be used simultaneously, or mouse and finger contacts may optionally be used simultaneously.
[0149] FIG. 5A shows an exemplary personal electronic device 500. The device 500 includes a body 502. In some embodiments, the device 500 can include some or all of the features described with respect to devices 100 and 300 (e.g., FIGS. 1A - 4B). In some embodiments, the device 500 has a touch-sensitive display screen 504, hereinafter referred to as the touch screen 504. Alternatively, or in addition to the touch screen 504, the device 500 has a display and a touch-sensitive surface. Similar to devices 100 and 300, in some embodiments, the touch screen 504 (or touch-sensitive surface) optionally includes one or more intensity sensors that detect the intensity of an applied contact (e.g., a touch). One or more intensity sensors of the touch screen 504 (or touch-sensitive surface) can provide output data representing the intensity of the touch. The user interface of the device 500 can respond to a touch based on the intensity of the touch, which means that touches of different intensities can call different user interface operations on the device 500.
[0150] Exemplary techniques for detecting and processing touch intensity can be found, for example, in International Patent Application No. PCT / US2013 / 040061, filed on May 8, 2013, published as International Patent No. WO / 2013 / 169849, "Device, Method, and Graphical User Interface for Displaying User Interface Objects Corresponding to an Application", and International Patent Application No. PCT / US2013 / 069483, filed on November 11, 2013, published as International Patent No. WO / 2014 / 105276, "Device, Method, and Graphical User Interface for Transitioning Between Touch Input to Display Output Relationships", each of which is hereby incorporated by reference in its entirety.
[0151] In some embodiments, device 500 has one or more input mechanisms 506 and 508. The input mechanisms 506 and 508, if included, can be physical mechanisms. Examples of physical input mechanisms include push buttons and rotatable mechanisms. In some embodiments, device 500 has one or more attachment mechanisms. Such attachment mechanisms, if included, can enable device 500 to be attached, for example, to hats, eyewear, earrings, necklaces, shirts, jackets, bracelets, watch bands, chains, pants, belts, shoes, wallets, backpacks, etc. These attachment mechanisms enable the user to wear device 500.
[0152] FIG. 5B shows an exemplary personal electronic device 500. In some embodiments, device 500 can include some or all of the components described with respect to FIGS. 1A, 1B, and 3. Device 500 has a bus 512 that operably couples an I / O section 514 to one or more computer processors 516 and a memory 518. The I / O section 514 can be connected to a display 504, which can have a touch sensing component 522 and optionally an intensity sensor 524 (e.g., a contact intensity sensor). Additionally, the I / O section 514 can be connected to a communication unit 530 that receives application and operating system data using Wi-Fi, Bluetooth®, near field communication (NFC), cellular, and / or other wireless communication techniques. The device 500 can include an input mechanism 506 and / or 508. The input mechanism 506 can optionally be, for example, a rotatable input device or a depressible and rotatable input device. In some embodiments, the input mechanism 508 can optionally be a button.
[0153] In some embodiments, the input mechanism 508 can optionally be a microphone. The personal electronic device 500 can optionally include various sensors such as a GPS sensor 532, an accelerometer 534, a direction sensor 540 (e.g., a compass), a gyroscope 536, a motion sensor 538, and / or combinations thereof, all of which can be operably connected to the I / O section 514.
[0154] The memory 518 of the personal electronic device 500 can 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, can cause the computer processor to execute, for example, the techniques described below, including process 800 (Figs. 8A-8C), process 1000 (Figs. 10A-10C), process 1200 (Figs. 12A-12C), and process 1400 (Fig. 14). A computer-readable storage media can be any media that tangibly contains or stores computer-executable instructions for use by or in connection with an instruction execution system, apparatus, or device. In some embodiments, the storage media is a transitory computer-readable storage media. In some embodiments, the storage media is a non-transitory computer-readable storage media. Non-transitory computer-readable storage media can include, but is not limited to, magnetic, optical, and / or semiconductor storage devices. Examples of such storage devices include magnetic disks, CDs, DVDs, or optical disks based on Blu-ray (registered trademark) technology, as well as resident solid-state memories such as flash, solid-state drives, and the like. The personal electronic device 500 is not limited to the components and configuration of Fig. 5B and can include other or additional components in multiple configurations.
[0155] As used herein, the term "affordance" refers to user interaction graphical user interface objects that are optionally displayed on the display screen of devices 100, 300, and / or 500 (Figs. 1A, 3, and 5A-5B). For example, images (e.g., icons), buttons, and text (e.g., hyperlinks) each optionally constitute an affordance.
[0156] As used herein, the term "focus selector" refers to an input element that indicates the current part of the user interface with which the user is interacting. In some implementations that include a cursor or other location marker, the cursor acts as the "focus selector," and thus while the cursor is positioned over a particular user interface element (e.g., a button, window, slider, or other user interface element), when an input (e.g., a press input) is detected on a touch-sensitive surface (e.g., the touchpad 355 of FIG. 3 or the touch-sensitive surface 451 of FIG. 4B), the particular user interface element is adjusted according to the detected input. In some implementations that include a touch screen display (e.g., the touch-sensitive display system 112 of FIG. 1A or the touch screen 112 of FIG. 4A) that enables direct interaction with user interface elements on the touch screen display, the detected contact on the touch screen acts as the "focus selector," and thus when an input (e.g., a press input by 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 according to the detected input. In some implementations, the focus is moved from one area of the user interface to another area of the user interface without movement of a corresponding cursor or movement of the contact on the touch screen display (e.g., by using the tab key or arrow keys to move the focus from one button to another), and in these implementations, the focus selector moves according to the movement of the focus between different areas of the user interface. Regardless of the particular form the focus selector takes, the focus selector is generally a user interface element (or a contact on the touch screen display) that is controlled by the user (e.g., by indicating to the device the element of the user interface with which the user intends to interact) so as to communicate the user's intended interaction to the user interface.For example, while a press input is detected on a touch sensing surface (e.g., a touch pad or a touch screen), the position of a focus selector (e.g., a cursor, a contact, or a selection box) over the corresponding button indicates that the user intends to activate that corresponding button (as opposed to other user interface elements shown on the device's display).
[0157] As used in this specification and the claims, the term "characteristic strength" of a contact refers to the characteristics of that contact based on one or more strengths of the contact. In some embodiments, the characteristic strength is based on a plurality of strength samples. The characteristic strength is optionally based on a set number of strength samples, i.e., a set period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10 seconds) associated with a given event (e.g., after detecting the contact, before detecting the lift-off of the contact, before or after detecting the start of movement of the contact, before detecting the end of the contact, before or after detecting an increase in the strength of the contact, and / or before or after detecting a decrease in the strength of the contact) during which the strength samples are collected. The characteristic strength of a contact is optionally based on one or more of the maximum value of the strength of the contact, the mean value of the strength of the contact, the average value of the strength of the contact, the top 10 percentile value of the strength of the contact, the median value of the strength of the contact, the top 90 percent value of the strength of the contact, etc. In some embodiments, the duration of the contact is used when determining the characteristic strength (e.g., when the characteristic strength is the average of the strength of the contact over time). In some embodiments, the characteristic strength is compared to a set of one or more strength thresholds to determine whether an action has been performed by the user. For example, a set of one or more strength thresholds optionally includes a first strength threshold and a second strength threshold. In this example, a contact having a characteristic strength that does not exceed the first threshold results in a first action, a contact having a characteristic strength that exceeds the first threshold but does not exceed the second threshold results in a second action, and a contact having a characteristic strength that exceeds the second threshold results in a third action. In some embodiments, the comparison between the characteristic strength and one or more thresholds is not used to determine whether to perform a first action or a second action, but rather is used to determine whether to perform one or more actions (e.g., whether to perform each action or whether to refrain from performing each action).
[0158] In some embodiments, for the purpose of determining the characteristic intensity, a portion of the gesture is identified. For example, the touch sensing surface optionally receives a continuous swipe contact that transitions from a starting location to reach an ending location, at which point the intensity of the contact increases. In this example, the characteristic intensity of the contact at the ending location is optionally based on only a portion of the continuous swipe contact (e.g., only the portion of the swipe contact at the ending location) rather than the entire swipe contact. In some embodiments, optionally, a smoothing algorithm is applied to the intensity of the swipe contact before determining the characteristic intensity of the contact. For example, the smoothing algorithm optionally includes one or more of a non - weighted moving average smoothing algorithm, a triangular smoothing algorithm, a median filter smoothing algorithm, and / or an exponential smoothing algorithm. In some situations, these smoothing algorithms eliminate minor increases or decreases in the intensity of the swipe contact for the purpose of determining the characteristic intensity.
[0159] The intensity of a contact on the touch sensing 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 typically corresponds to the intensity at which the device performs an operation associated with clicking a button of a physical mouse or a trackpad. In some embodiments, the deep press intensity threshold typically corresponds to the intensity at which the device performs an operation different from the operation associated with clicking a button of a physical mouse or a trackpad. In some embodiments, when a contact having a characteristic intensity below the light press intensity threshold (e.g., above a nominal contact detection intensity threshold below which the contact is not detected) is detected, the device moves the focus selector in accordance with the movement of the contact on the touch sensing surface without performing an operation associated with the light press intensity threshold or the deep press intensity threshold. Generally, unless otherwise specified, these intensity thresholds are consistent across various sets of user interface figures.
[0160] An increase in the characteristic intensity of a contact from an intensity below a light pressing intensity threshold to an intensity between the light pressing intensity threshold and a deep pressing intensity threshold may be referred to as an input of "light pressing". An increase in the characteristic intensity of a contact from an intensity below a deep pressing intensity threshold to an intensity above the deep pressing intensity threshold may be referred to as an input of "deep pressing". An increase in the characteristic intensity of a contact from an intensity below a contact detection intensity threshold to an intensity between the contact detection intensity threshold and the light pressing intensity threshold may be referred to as a detection of a contact on the touch surface. A decrease in the characteristic intensity of a contact from an intensity above the contact detection intensity threshold to an intensity below the contact detection intensity threshold may be referred to as a detection of a lift-off of the contact 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.
[0161] In some embodiments described herein, in response to detecting a gesture including each pressing input, or in response to detecting each pressing input performed by each contact (or contacts), one or more operations are performed, and each pressing input is detected based at least in part on detecting an increase in the intensity of a contact (or contacts) above a pressing input intensity threshold. In some embodiments, each operation is performed in response to detecting an increase in the intensity of each contact above the pressing input intensity threshold (e.g., the "downstroke" of each pressing input). In some embodiments, the pressing input includes an increase in the intensity of each contact above the pressing input intensity threshold and a subsequent decrease in the intensity of the contact below the pressing input intensity threshold, and each operation is performed in response to detecting a subsequent decrease in the intensity of each contact below the pressing input threshold (e.g., the "upstroke" of each pressing input).
[0162] In some embodiments, the device employs intensity hysteresis to avoid spurious inputs that may be referred to as "jitter," and the device defines or selects a hysteresis intensity threshold having a predetermined relationship to the pressing input intensity threshold (e.g., the hysteresis intensity threshold is X intensity units lower than the pressing input intensity threshold, or the hysteresis intensity threshold is 75%, 90%, or some reasonable percentage of the pressing input intensity threshold). Thus, in some embodiments, a pressing input includes an increase in the intensity of each contact that exceeds the pressing input intensity threshold, and a subsequent decrease in the intensity of the contact that falls below the hysteresis intensity threshold corresponding to the pressing input intensity threshold, and each operation is performed in response to detecting a subsequent decrease in the intensity of each contact that falls below the hysteresis intensity threshold (e.g., the "upstroke" of each pressing input). Similarly, in some embodiments, a pressing input is detected only when the device detects an increase in the intensity of a contact from an intensity below the hysteresis intensity threshold to an intensity above the pressing input intensity threshold, and optionally, a subsequent decrease in the intensity of the contact to an intensity below the hysteresis intensity, and each operation is performed in response to detecting the pressing input (e.g., depending on the situation, an increase in the intensity of the contact or a decrease in the intensity of the contact).
[0163] For ease of explanation, the description of an operation performed in response to a pressing input associated with a pressing input intensity threshold, or a gesture including a pressing input, is optionally triggered in response to detecting any of an increase in the intensity of a contact that exceeds the pressing input intensity threshold, an increase in the intensity of a contact from an intensity below the hysteresis intensity threshold to an intensity above the pressing input intensity threshold, a decrease in the intensity of a contact that falls below the pressing input intensity threshold, and / or a decrease in the intensity of a contact that falls below the hysteresis intensity threshold corresponding to the pressing input intensity threshold. Further, in examples where an operation is described as being performed in response to detecting a decrease in the intensity of a contact that falls below the pressing input intensity threshold, the operation is optionally performed in response to detecting a decrease in the intensity of a contact that corresponds to and falls below a hysteresis intensity threshold lower than the pressing input intensity threshold.
[0164] FIG. 6 shows an exemplary device connected via one or more communication channels for participating in a commercial transaction according to some embodiments. One or more exemplary electronic devices (e.g., devices 100, 300, and 500) are configured to optionally detect an input (e.g., a specific user input, an NFC field) and optionally transmit payment information (e.g., using NFC). One or more electronic devices optionally include NFC hardware and are configured to be NFC-enabled.
[0165] Electronic devices (e.g., devices 100, 300, and 500) are optionally configured to store payment account information associated with each of one or more payment accounts. Payment account information includes, for example, one or more of a personal or company name, a billing address, a login, 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, payment account information includes an image such as a photograph of a payment card (e.g., captured and / or received by the device). In some embodiments, the electronic device receives a user input including at least some payment account information (e.g., receives a credit, debit, account, or gift card number and expiration date entered by the user). In some embodiments, the electronic device detects at least some payment account information from an image (e.g., a payment card captured by the device's camera sensor). 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 a service (e.g., an app for renting or selling audio and / or video files) for which the user or user device or an account for the specified payment account data has previously made a purchase.
[0166] In some embodiments, a payment account is added to an electronic device (e.g., devices 100, 300, and 500), whereby the payment account information is securely stored on the electronic device. In some embodiments, after the user initiates such a process, the electronic device transmits information about the payment account to a commerce coordination server, which then communicates with a server (e.g., a payment server) operating on the payment network for the account to ensure the validity of the information. The electronic device is optionally configured to receive from the server a script that enables the electronic device to program payment information for the account onto a secure element.
[0167] In some embodiments, communication between electronic devices 100, 300, and 500 facilitates commerce (e.g., general or specific commerce). For example, a first electronic device (e.g., 100) can act as a providing or managing device and send a notification of new or updated payment account data (e.g., information for a new account, updated information for an existing account, and / or an alert regarding an existing account) to a second electronic device (e.g., 500). In another example, a first electronic device (e.g., 100) can send data to a second electronic device, the data reflecting information regarding a payment commerce facilitated by the first electronic device. The information optionally includes one or more of a payment amount, the account used, a purchase time, and whether a default account has been changed. The second device (e.g., 500) optionally uses such information to update a default payment account (e.g., based on a learning algorithm or explicit user input).
[0168] Electronic devices (e.g., 100, 300, 500) are configured to communicate with each other via any one of various networks. For example, the devices communicate using a Bluetooth connection 608 (e.g., including a conventional Bluetooth connection or a Bluetooth low energy connection) or a WiFi network 606. Communication between user devices is optionally adjusted to reduce the possibility of inappropriate sharing of information between the devices. For example, communication related to payment information requires that the communication devices be paired (e.g., associated with each other via an explicit user interaction) or associated with the same user account.
[0169] In some embodiments, an electronic device (e.g., 100, 300, 500) is optionally used to communicate with a point-of-sale (POS) payment terminal 600 that is NFC-enabled. This communication is optionally performed using various communication channels and / or technologies. In some embodiments, an electronic device (e.g., 100, 300, 500) communicates with the payment terminal 600 using an NFC channel 610. In some embodiments, the payment terminal 600 communicates with the electronic device (e.g., 100, 300, 500) using a peer-to-peer NFC mode. An electronic device (e.g., 100, 300, 500) is optionally configured to transmit a signal including payment information for a payment account (e.g., a default account or an account selected for a particular commercial transaction) to the payment terminal 600.
[0170] In some embodiments, advancing a commercial transaction includes transmitting a signal that includes payment information for an account, such as a payment account. In some embodiments, advancing a commercial transaction includes reconfiguring an electronic device (e.g., 100, 300, 500) to act as a contactless payment card, such as an NFC-enabled contactless payment card, and then transmitting account credentials to a payment terminal 600 or the like via NFC. In some embodiments, after transmitting account credentials via NFC, the electronic device is reconfigured not to act as a contactless payment card (e.g., requires permission before reconfiguring again to act as a contactless payment card via NFC).
[0171] In some embodiments, the generation and / or transmission of the signal is controlled by a secure element within the electronic device (e.g., 100, 300, 500). The secure element optionally requires a specific user input before disclosing payment information. For example, the secure element optionally requires detection of the electronic device being worn, detection of a button press, detection of a passcode entry, detection of a touch, detection of one or more option selections (e.g., received during an interaction with an application), detection of a fingerprint signature, detection of a voice or voice command, and / or detection of a gesture or movement (e.g., rotation or acceleration). In some embodiments, if a communication channel (e.g., an NFC communication channel) with another device (e.g., the payment terminal 600) is established within a time period defined from the detection of the input, the secure element discloses the payment information to be transmitted to the other device (e.g., the payment terminal 600). In some embodiments, the secure element is a hardware component that controls the disclosure of secure information. In some embodiments, the secure element is a software component that controls the disclosure of secure information.
[0172] In some embodiments, the protocol related to the involvement in commercial transactions depends on, for example, the device type. For example, the state of 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, the state of generating and / or transmitting for a wearable device includes detecting that a button has been pressed (e.g., after security verification), and the corresponding state for a phone does not require a button press but instead requires detecting a specific interaction with an application. In some embodiments, the state of transmitting and / or disclosing payment information includes receiving a specific input at each of a plurality of devices. For example, the disclosure of payment information optionally requires detecting a fingerprint and / or password on a device (e.g., device 100) and detecting a mechanical input (e.g., button press) on another device (e.g., device 500).
[0173] The payment terminal 600 optionally generates a signal that is transmitted to the payment server 604 to determine whether payment is permitted using the payment information. The payment server 604 optionally includes any device or system configured to receive payment information associated with a payment account and determine whether a proposed purchase is permitted. In some embodiments, the payment server 604 includes a server of an issuing bank. The payment terminal 600 communicates with the payment server 604 directly or indirectly via one or more other devices or systems (e.g., a server of an acquiring bank and / or a server of a card network).
[0174] Payment server 604 optionally identifies a user account from among databases of user accounts (e.g., 602) using at least some of the payment information. For example, each user account includes payment information. The account is optionally located by locating an account having specific payment information that matches the payment information from the POS communication. In some embodiments, when the provided payment information is inconsistent (e.g., the expiration date does not correspond to the credit, debit, or gift card number), or when there is no account that includes payment information matching the payment information from the POS communication, the payment is rejected.
[0175] In some embodiments, data for the user account further specifies one or more limits (e.g., credit limit), current or previous balance, previous transaction date, location, and / or amount, 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 the payment. For example, when adding the purchase amount to the current balance would exceed the account limit, when the account is frozen, when the previous business transaction amount exceeds a threshold, or when the previous number or frequency of business transactions exceeds a threshold, the payment server rejects the payment.
[0176] In some embodiments, payment server 604 responds to the POS payment terminal 600 with a notification as to whether the proposed purchase was approved or rejected. In some embodiments, the POS payment terminal 600 sends a signal for identifying the result to an electronic device (e.g., 100, 300, 500). For example, when the purchase is approved, the POS payment terminal 600 sends a receipt to the electronic device (e.g., 100, 300, 500) (e.g., via a business transaction coordination server that manages the business transaction app on the user device). In some cases, the POS payment terminal 600 presents an output indicating the result (e.g., visual or audio output). The payment can be sent to the retailer as part of the approval process or can be sent later.
[0177] In some embodiments, an electronic device (e.g., 100, 300, 500) participates in a commercial transaction that is completed without the intervention of a POS payment terminal 600. For example, when it is detected that a mechanical input has been received, a secure element within the electronic device (e.g., 100, 300, 500) discloses payment information, enabling an application on the electronic device to access the information (e.g., sending the information to a server associated with the application).
[0178] In some embodiments, an electronic device (e.g., 100, 300, 500) is in a locked or unlocked state. In the locked state, the electronic device is powered on and operational, but is prevented from performing a predetermined set of operations in response to user input. The predetermined set of operations may include navigation between user interfaces, activation or deactivation of a predetermined set of functions, and activation or deactivation of specific applications. The locked state may be used to prevent unintentional or unauthorized use of some functionality of the electronic device, or activation or deactivation of some functions on the electronic device. In the unlocked state, the electronic device 100 is powered on and operational, and is not prevented from performing at least a portion of a predetermined set of operations that cannot be performed in the locked state.
[0179] When the device is in the locked state, the device is considered to be locked. In some embodiments, a locked device may respond to a limited set of user inputs, including an input corresponding to an attempt to transition the device from the locked state to the unlocked state, or an input corresponding to turning off the power of the device.
[0180] In some embodiments, the secure element is a hardware component (e.g., a secure microcontroller chip) configured to securely store data or algorithms. In some embodiments, the secure element provides (or discloses) payment information (e.g., account numbers and / or dynamic security codes specific to a commercial transaction). In some embodiments, the secure element provides (or discloses) payment information in response to the device receiving a permission such as user authentication (e.g., fingerprint authentication, password authentication, when the device is unlocked, and optionally, after the device is unlocked by providing authentication credentials to the device and the device is continuously on the user's wrist, detecting a double press of a hardware button. The device being continuously on the user's wrist is determined by periodically checking that the device is in contact with the user's skin). For example, the device detects a fingerprint with a fingerprint sensor of the device (e.g., a fingerprint sensor incorporated in a button). The device determines whether this fingerprint is consistent with the registered fingerprint. In accordance with the determination that the fingerprint is consistent with the registered fingerprint, the secure element provides (or discloses) payment information. In accordance with the determination that the fingerprint is not consistent with the registered fingerprint, the secure element discontinues the provision (or disclosure) of payment information.
[0181] Next, attention is directed to embodiments of a user interface (「UI」) and associated processes implemented on an electronic device such as the portable multifunctional device 100, the device 300, or the device 500.
[0182] Figures 7A - 7O illustrate an exemplary user interface for entering information related to secure credentials into an electronic device 700, according to some embodiments. The user interfaces in these figures are used to illustrate the processes described below, including the processes in Figures 8A - 8C. In some embodiments, the electronic device 700 includes some or all of the features of device 100, device 300, or device 500. In some embodiments, the electronic device 700 includes a display 702, one or more input devices (e.g., a touch - sensing surface of the display 702, a mechanical input device 701 such as a power button, a camera 703, a microphone, a camera sensor (e.g., a light sensor 164) located on the back of the device 700), one or more output devices (e.g., speakers), and one or more sensors (e.g., biometric sensors 704 such as depth sensors, fingerprint sensors). In some embodiments, one or more sensors (e.g., biometric sensors such as fingerprint sensors) of the electronic device 700 are integrated within different components / elements of the device (e.g., the fingerprint sensor is integrated with the display 702).
[0183] In Figure 7A, the user attempts to enter information related to secure credentials. Specifically, the user attempts to enter account information of a payment card (e.g., a credit card, a debit card) to add a secure credential (e.g., a token stored in a secure element of the electronic device 700, a token corresponding to an account number or a device - specific number corresponding to an account number)) to the electronic device 700. In some embodiments, the secure credential is linked to the account information of the payment card (e.g., linked by the issuer of the payment card). Thus, in some embodiments, information related to the payment card is also information related to the secure credential, and vice versa. Using the secure credential, the electronic device 700 can participate in a commercial transaction using the account linked to the payment card (e.g., authenticate the payment for goods or services).
[0184] The electronic device 700 can input information associated with a payment card by using the camera sensor of the electronic device 700. For example, the electronic device 700 uses the camera sensor to capture an image of the visible account information located on the payment card. Then, the electronic device 700 performs optical character recognition on the image to extract the information associated with the payment card. However, some payment cards do not have visible account information (e.g., credit card number, debit card number, expiration date, security code), and it is necessary (e.g., for security reasons) to add secure credentials to the electronic device via a specific process (e.g., a process using an application provided by the issuer of the payment card). Payment cards without visible account information tend to be issued by banks operating in a particular country. Therefore, if the electronic device 700 is located in one of these countries, there is a high possibility that the payment card does not have visible account information that can be captured via the camera sensor, so an alternative process for receiving information associated with the payment card needs to be implemented.
[0185] As shown in FIG. 7A, the electronic device 700 displays a wallet user interface (UI) 706. While the wallet UI 706 is being displayed, the electronic device 700 receives an input 708 (e.g., a tap gesture) at an additional credential affordance 710.
[0186] In FIG. 7B, in response to receiving the input 708 at the additional credential affordance 710, the electronic device 700 continues to use an affordance 714 to display an introduction UI 712 (e.g., replacing the display of the wallet UI 706). The introduction UI 712 includes text that explains to the user the purpose of the process the user is currently involved in. To continue adding secure credentials to the electronic device 700, the user selects a continue affordance 714.
[0187] In FIG. 7C, while displaying the introductory UI 712, the electronic device 700 receives an input 716 at the continuous affordance 714. In response to receiving the input 716 at the continuous affordance 714, the electronic device 700 determines whether the geographical location of the electronic device 700 (e.g., a location defined by GPS coordinates (e.g., a location determined by the GPS module 135)) is located in one of the countries within a list of predetermined countries. Each country within the list of predetermined countries has one or more issuers (e.g., banks) operating therein that issue payment cards without visible account information. The electronic device 700 determines that the geographical location of the electronic device 700 is in one of the countries within the list of predetermined countries.
[0188] When it is determined that the geographical location of the electronic device 700 is located in one of the countries within the list of predetermined countries, the electronic device 700 determines whether the number of potential issuers of payment cards is less than a predetermined (or default) number (e.g., 5, 10, 15, 20). Potential issuers are issuers of payment cards without visible account information (or payment cards that require a specific process for adding secure credentials) operating in the country where the electronic device 700 is currently located. Following or simultaneously with the determination of the geographical location, the electronic device 700 determines that the number of potential issuers is equal to or greater than the default number (e.g., 10 or more).
[0189] In FIG. 7D, when it is determined that the potential number of issuers is equal to or greater than a predetermined number, the electronic device 700 displays an issuer search UI 718 (e.g., replacing the display of the introduction UI 712). The issuer search UI 718 enables the user to search for the issuer of a payment card. The issuer search UI 718 includes a virtual keyboard 720 used to input the name of the issuer of the payment card. The issuer search UI also includes a text input field 722 that displays one or more characters input via the virtual keyboard 720. When the user inputs one or more characters via the virtual keyboard 720, the electronic device 700 displays the results in real time, and only the issuers that match or correspond to the one or more input characters are displayed.
[0190] In FIG. 7E, while the issuer search UI 718 is being displayed, the electronic device 700 receives input via the virtual keyboard 720. In response to receiving input via the virtual keyboard 720, the electronic device 700 displays the input characters ("B" and "A") within the text input field 722. Further, in response to receiving input via the virtual keyboard 720, the electronic device 700 displays issuer affordances 724a - d that include the name of the issuer and the account type (e.g., credit, debit). The issuer affordances 724a - d are selected for display based on the name of the issuer associated with the issuer affordance. For example, since the name of the issuer (i.e., Baz Bank) corresponds to the input characters (e.g., the name of the issuer includes one or more of the input characters), the issuer affordances 724a - d are displayed. Further, in response to receiving input via the virtual keyboard 720, the electronic device 700 displays an alternative card affordance 726 that, when activated, results in the start of a process to capture information regarding secure credentials using the camera sensor of the electronic device 700. In some embodiments, the electronic device 700 displays the alternative card affordance 726 within the issuer search UI 718 of FIG. 7D.
[0191] In FIG. 7F, while the issuer search UI 718 is being displayed, the electronic device 700 receives an additional input ("Z") via the virtual keyboard 720 and, in response, updates the search results for the issuer of the payment card. That is, in response to receiving the additional input via the virtual keyboard 720, the electronic device 700 stops displaying the issuer affordances 724a - d. Further, in response to receiving the additional input via the virtual keyboard 720, the electronic device 700 displays the issuer affordances 724e - f.
[0192] The user attempts to enter information regarding a payment card (e.g., a debit card issued by Baz Bank). To do so, the user taps the issuer affordance 724e. While the issuer search UI 718 is being displayed, the electronic device receives an input 728 (e.g., a tap gesture) at the issuer affordance 724e. In response to receiving the input 728 at the issuer affordance 724e, the electronic device 700 determines whether an application corresponding to the issuer associated with the issuer affordance 724e (e.g., the Baz Bank application) is already installed on the electronic device 700 (e.g., after an initial determination that the payment account associated with the affordance 724e has no visible information or is an account associated with a payment card that requires emulation via a specific application). The electronic device 700 determines that the Baz Bank application is not installed on the electronic device 700.
[0193] In FIG. 7G, upon determining that the Baz Bank application is not installed on the electronic device 700, the electronic device 700 displays an app request UI 730 having an app store affordance 732 (e.g., replacing the display of the issuer search UI 718). The app request UI 730 prompts the user to continue adding secure credentials to the electronic device 700 using the Baz Bank application.
[0194] In FIG. 7H, since the user is attempting to download the Baz Bank application, the user taps on the app store affordance 732. While the app request UI 730 is being displayed, the electronic device 700 receives an input 736 at the app store affordance 732.
[0195] In FIG. 7I, in response to receiving the input 736 at the app store affordance 732, the electronic device 700 displays the app store UI 738 (e.g., replaces the display of the app request UI 730). The app store UI 738 includes the landing page of the Baz Bank application with a download affordance 740. To enter information regarding secure credentials, the user downloads the application. While the app store UI 738 is being displayed, the electronic device 700 receives an input (e.g., a tap gesture) at the download affordance 740. In response to receiving the input at the download affordance 740, the electronic device 700 initiates the process of downloading the Baz Bank application. This process can require user authentication before downloading the Baz Bank application. After downloading the application, the electronic device 700 receives an input to launch (or open) the Baz Bank application. After launching the Baz Bank application, the electronic device 700 receives an input regarding secure credentials (e.g., user account information (e.g., username, password), billing address). The electronic device 700 uses this input to add the secure credentials to the electronic device 700, thereby enabling the electronic device 700 to use the secure credentials in future commercial transactions.
[0196] Figure 7J shows different processes for entering information regarding secure credentials using the camera sensor of the electronic device 700. Using the camera capture UI, the electronic device 700 can receive information regarding secure credentials by capturing an image of the visible account information located on the payment card. As shown in Figure 7J, a portion of the payment card is positioned within the field of view of the rear-facing camera of the electronic device 700. After the card is properly positioned, the electronic device 700 then performs optical character recognition on the image (e.g., the captured image) to extract information associated with the payment card. The electronic device 700 then enters the information to add the secure credentials to the electronic device. As described above, Figure 7C shows that while displaying the introduction UI 712, the electronic device 700 receives an input 716 at the continuous affordance 714. In response to receiving the input 716 at the continuous affordance 714, the electronic device 700 determines whether the geographical location of the electronic device 700 (e.g., the location defined by GPS coordinates) is located in one of the countries within a predetermined list of countries. In some embodiments, if it is determined that the geographical location of the electronic device 700 is not in one of the countries within the predetermined list of countries, the electronic device 700 displays a camera capture UI 742 as shown in Figure 7J (instead of the issuer search UI 718 shown in Figure 7D and the issuer selection UI 744 shown in Figure 7K).
[0197] As described above, Figures 7E - 7F and 7K - 7L show user interfaces including alternative card affordances 726. In some embodiments, upon activation of the alternative card affordance 726, the electronic device 700 displays a camera capture UI 742 as shown in Figure 7J (e.g., replaces the display of the user interface including the alternative card affordance 726 with the camera capture UI 742).
[0198] As described above, FIGS. 7E-7F and 7L show user interfaces including affordances having account types (e.g., debit, credit). In some embodiments, upon activation of an affordance having a credit account type (e.g., 724b, 724d, 724f, and 752b), the electronic device 700 displays a camera capture UI 742, as shown in FIG. 7J (e.g., replaces the display of the user interface including the affordance having a credit account type with the camera capture UI 742).
[0199] FIG. 7K shows a different process for finding the issuer of a payment card. As described above with respect to FIG. 7C, when it is determined that the geographical location of the electronic device 700 is in one of the countries within a list of predetermined countries, the electronic device 700 determines whether the number of potential issuers of the payment card is less than some predetermined number (e.g., 5, 10, 15, 20). In some embodiments, when it is determined that the number of potential issuers of the payment card is less than the predetermined number, the electronic device 700 displays an issuer selection UI 744, as shown in FIG. 7K (instead of the issuer search UI 718 shown in FIG. 7D). The issuer selection UI 744 includes issuer affordances 746a-c that include the names of potential issuers operating at the geographical location of the electronic device 700. In some embodiments, the issuer selection UI 744 includes an alternative card affordance 726.
[0200] In FIG. 7K, the user attempts to select Bank Baz as the issuer of the payment card and taps on issuer affordance 746a. In some embodiments, while the issuer selection UI 744 is being displayed, the electronic device 700 receives an input 748 at the issuer affordance 746a.
[0201] In FIG. 7L, in response to receiving an input 748 at the issuer affordance 746a, the electronic device 700 displays a type selection UI 751 having type affordances 752a - b indicating different account types (e.g., debit, credit) of cards issued by Baz Bank (e.g., replacing the display of the issuer selection UI 744). In some embodiments, the type selection UI 751 includes an alternative card affordance 726. The user attempts to input information regarding a debit card issued by Baz Bank, so the user taps on the type affordance 752a. Accordingly, the electronic device 700 receives an input 750 at the type affordance 752a. In response to receiving the input 750 at the type affordance 752a, the electronic device 700 determines whether an application corresponding to the type affordance 752a (i.e., the Baz Bank application) is already installed on the electronic device 700. In some embodiments, the electronic device 700 determines that the Baz Bank application is not installed and, in response, displays an app request UI 730 having an app store affordance 732 as shown in FIG. 7G. In some embodiments, the electronic device 700 determines that the Baz Bank application is already installed on the electronic device 700.
[0202] In FIG. 7M, when it is determined that the Baz Bank application is already installed on the electronic device 700, the electronic device 700 displays an app request UI 730 having a launch affordance 754 (e.g., replacing the display of the type selection UI 751). When an input is received at the launch affordance 754, it causes the electronic device 700 to launch (or open) the Baz Bank application. After launching the Baz Bank application, the electronic device 700 receives an input regarding secure credentials (e.g., user account information (e.g., username, password), billing address). The electronic device 700 uses this input to add secure credentials to the electronic device 700, thereby enabling the electronic device 700 to be used in commercial transactions.
[0203] In some embodiments, the user interface of FIG. 7M is displayed in response to input 728 while the user interface of FIG. 7F is being displayed after the electronic device 700 determines that the related application is already installed on the electronic device 700.
[0204] Returning to FIG. 7L, the electronic device 700 can display a user interface other than the interface of FIG. 7M in response to receiving an input 750 corresponding to the selection of an account type. In some embodiments, in response to the input 750, after determining that the Baz Bank application is not installed on the electronic device, the electronic device 700 displays an interface similar to those of FIGS. 7G through 7I.
[0205] FIG. 7N shows a user interface 762 of an application for managing and configuring a pair of electronic devices (e.g., a smartwatch (e.g., electronic device 500)) that is wirelessly connected by being paired with an electronic device 700. The user interface 762 includes an affordance 766 that can be used to initiate a process for entering information regarding secure credentials (e.g., credentials also entered into the electronic device 700 or secure credentials not entered into device 700) into the pair of devices. While the user interface 762 is being displayed, the electronic device 700 receives an input 764 at the affordance 766. In some embodiments, in response to receiving the input 764 at the affordance 766, the electronic device 700 initiates a process for adding secure credentials to the pair of devices (e.g., the process includes some or all of the features and user interfaces described in FIGS. 7A-7M). In some embodiments, the process and the user interface associated with the process are generated by an application for managing and configuring the pair of electronic devices rather than a separate application such as the wallet application of FIG. 7A.
[0206] During the process of adding a secure credential, the user identifies the issuer and / or type (e.g., credit, debit) associated with the payment card. As shown in FIG. 7O, upon receiving an identification (e.g., selection) of the issuer and / or type associated with the payment card (e.g., using an interface similar or identical to that of FIG. 7F or FIG. 7L), the electronic device displays an app request UI 756 that prompts the user to download an application associated with the issuer (e.g., the Baz Bank application) at a later time to input information regarding the secure credential. Sometimes, it is preferable to require the user to manually close the application dedicated to the paired electronic device before downloading the application to ensure that the user is aware of whether the application is already downloaded to the electronic device 700 or the paired device. In some embodiments, after displaying the app request UI 756, when the electronic device 700 is activated, it outputs a prompt (e.g., a notification) that includes an affordance to display a landing page for the application associated with the issuer (e.g., a page similar to that of FIG. 7I) (e.g., output after a predetermined time has elapsed without the user downloading the application associated with the issuer).
[0207] FIGS. 8A-8C are flow diagrams illustrating a method 800 for inputting information regarding a secure credential using an electronic device, according to some embodiments. The method 800 is executed on a device having a display (e.g., 100, 300, 500). Some of the operations of the method 800 are optionally combined, the order of some operations is optionally changed, and some operations are optionally omitted.
[0208] As described below, method 800 provides an intuitive way to enter information about secure credentials using an electronic device. This method reduces the cognitive burden on the user of entering information about secure credentials using the electronic device, thereby creating a more efficient human-machine interface. In the case of a battery-operated computing device, power is conserved and the battery charging interval is increased by enabling the user to enter information about secure credentials using the electronic device faster and more efficiently.
[0209] The electronic device (e.g., 700) displays (802) a start user interface (e.g., 712) on a display (e.g., 702) that includes an affordance (e.g., 714) for adding a secure credential (e.g., a credit card, a debit card, a security token) to the electronic device (e.g., for entering information about the secure credential). In some embodiments, the start user interface is an interface of a first-party application (in some embodiments, the start user interface is an interface corresponding to a first-party application (e.g., an interface of a different first-party application (e.g., the start user interface and the first-party application used to perform one or more steps of a first process are both developed and / or released by a manufacturer of the electronic device or by a developer of an operating system of the electronic device))).
[0210] The electronic device receives (804) a request (e.g., 716) to add a secure credential to the electronic device (e.g., enter information regarding the secure credential), and the request corresponds to an affordance for adding the secure credential (in some embodiments, receiving the request includes receiving an input (e.g., a tap) at a location corresponding to the affordance) (in some embodiments, receiving the request includes receiving oral user input to select the affordance).
[0211] In response to receiving a request (e.g., 716) to add information regarding secure credentials to the electronic device (804), the electronic device initiates a first process (806) for entering information regarding secure credentials into the electronic device according to a determination that the electronic device is operating in a first context when the request to add secure credentials is received (in some embodiments, the first context includes the electronic device being at a first location (e.g., a geographical location, a country, a predetermined location from a list of predetermined locations)). (In some embodiments, initiating the first process for entering information regarding secure credentials into the electronic device includes displaying a user interface (e.g., 718, 744) for identifying an issuer of information associated with the secure credentials (e.g., a security token number, a credit card number, a debit card number, an expiration date of a credit card or debit card)). Determining that the electronic device is operating in the first context and then initiating the first process (e.g., a process in place of a second process) provides the user with a specific process for adding secure credentials to the electronic device, and this specific process is configured for a type of secure credential that highly correlates with the first context. Initiating the first process when a set of conditions are met without requiring an explicit request to execute the process improves the operability of the device, makes the user-device interface more efficient (e.g., by assisting the user in providing appropriate inputs when operating / interacting with the device and reducing user errors), and in addition, reduces power usage and improves the battery life of the device by enabling the user to use the device more quickly and efficiently.
[0212] In some embodiments, a secure credential is associated with an issuer of information associated with the secure credential (e.g., an administrator, regulator, or monitor of an activity associated with the secure credential), and (e.g., a third-party application is developed and / or released by an issuer of information associated with the secure credential (e.g., an entity (e.g., a university) that issues an identification card having information associated with the secure credential, a bank that issues a bank card having information associated with the secure credential)), starting a first process for entering information regarding the secure credential into an electronic device includes the electronic device receiving (808) an input (e.g., 728, 748) corresponding to the identification of the issuer of information associated with the secure credential (e.g., receiving a direct entry of the name of the issuer (e.g., via a keyboard) or receiving a selection of the issuer from a list of potential issuers).
[0213] In some embodiments, starting a first process for entering information regarding a secure credential into an electronic device, in response to receiving an input corresponding to the identification of the issuer of information associated with the secure credential, the electronic device displays (810) a plurality of types of information (e.g., 724a - f, 752a - b) issued by the issuer of the information, including at least a first type of information (e.g., credit account information) (e.g., 724f, 752b) and a second type of information different from the first type of information (e.g., debit account information) (e.g., 724, 752a). In some embodiments, the electronic device displays the first type of information within a user interface (e.g., 718, 751) for selecting the type of information.
[0214] In some embodiments, while displaying multiple types of information, the electronic device displays an alternative input affordance (e.g., 726). In some embodiments, the electronic device receives an input corresponding to a selection of the alternative input affordance (e.g., an option to initiate a second process). In some embodiments, in response to receiving a selection of the alternative input affordance, the electronic device displays, on the display, a capture user interface (e.g., 742) for capturing information regarding secure credentials using one or more camera sensors of the electronic device (e.g., capturing information from a card represented secure credentials or from displayed content associated with secure credentials) (in some embodiments, the capture user interface is different from the start user interface (e.g., 712)) (in some embodiments, the capture user interface includes a live preview of an image acquired by one or more camera sensors) (in some embodiments, the capture user interface includes a manual input affordance that, when selected, triggers the display of one or more text input fields and a virtual keyboard) (in some embodiments, displaying multiple types of information includes stopping the display of the start user interface) (in some embodiments, the second process is executed as part of the first process when the first process proceeds to a selection of the first type of information). In some embodiments, while displaying the capture user interface, the electronic device receives information regarding secure credentials using one or more camera sensors of the electronic device.In some embodiments, after receiving information regarding a secure credential, the electronic device inputs information regarding the secure credential (e.g., information received via one or more camera sensors, information determined based on information received via one or more camera sensors) into the electronic device (in some embodiments, the information regarding the secure credential is used to generate (or issue) a secure credential stored in a secure element of the electronic device) (in some embodiments, the secure credential stored in the secure element is released only after appropriate authentication is provided) (in some embodiments, the information received via one or more camera sensors is extracted from an image acquired by the one or more camera sensors using optical character recognition).
[0215] In some embodiments, while displaying multiple types of information, the electronic device receives an input corresponding to the selection of a first type of information (e.g., credit account information). In some embodiments, in response to receiving the selection of the first type of information, the electronic device displays, on the display, a capture user interface (e.g., 742) for capturing information regarding secure credentials (e.g., capturing information from a card represented or displayed content associated with the secure credentials) using one or more camera sensors of the electronic device (in some embodiments, the capture user interface is different from the starting user interface (e.g., 712)) (in some embodiments, the capture user interface includes a live preview of an image acquired by one or more camera sensors) (in some embodiments, the capture user interface includes a manual input affordance that, when selected, triggers the display of one or more text input fields and a virtual keyboard) (in some embodiments, displaying multiple types of information includes stopping the display of the starting user interface) (in some embodiments, the second process is executed as part of the first process when the first process proceeds to the selection of the first type of information).
[0216] In some embodiments, while displaying a capture user interface, the electronic device receives information regarding secure credentials using one or more camera sensors of the electronic device. In some embodiments, after receiving information regarding secure credentials, the electronic device inputs information regarding secure credentials (e.g., information received via one or more camera sensors, information determined based on information received via one or more camera sensors) into the electronic device (in some embodiments, the information regarding secure credentials is used to generate (or issue) secure credentials stored in a secure element of the electronic device) (in some embodiments, the secure credentials stored in the secure element are released only thereafter when appropriate authentication is provided).
[0217] In response to receiving a request (e.g., 716) to add a secure credential to the electronic device (804), the electronic device operates in a second context different from the first context. In some embodiments, the second context includes the electronic device being at a second location different from the first location (e.g., a location that does not match a location in a predetermined list of locations). When a request to add a secure credential to the device is received, the electronic device starts a second process (812) for entering information regarding the secure credential into the electronic device, and the second process is different from the first process. In some embodiments, starting the second process for entering information regarding the secure credential into the electronic device includes displaying a user interface (e.g., 742) for capturing information associated with the secure credential (e.g., a security token number, a credit card number, a debit card number, an expiration date of a credit or debit card) via one or more camera sensors. In some embodiments, the first context includes the electronic device being at a first location (e.g., a geographical location, a country, a predetermined location in a predetermined list of locations). In some embodiments, the electronic device is in the first context (e.g., the device is in a first mode) according to (based on) a determination (e.g., based on GPS data) that the electronic device is at a first location highly correlated with the information associated with the secure credential corresponding to the first process (e.g., the location corresponding to the first process for entering information).In some embodiments, the second context includes the electronic device being in a second location different from the first location (e.g., a location that does not match a list of predetermined locations). (In some embodiments, the electronic device is determined (e.g., based on GPS data) to be in a second location (e.g., highly correlated with information associated with secure credentials for a second process for inputting information) where the electronic device does not correspond to the first process (e.g., the second process is the default process) or corresponds to the second process (e.g., specifically corresponds).) When it is determined that the electronic device is operating in the second context, starting the second process (e.g., the default process) provides the user with a specific process for adding secure credentials to the electronic device, and this specific process is configured for the type of secure credentials that is highly correlated with the second context. Starting the second process when a set of conditions is met without requiring an explicit request to execute the process improves the operability of the device, (e.g., by assisting the user to provide appropriate input when operating / interacting with the device and reducing user errors) making the user-device interface more efficient, and in addition, reducing power consumption and improving the battery life of the device by enabling the user to use the device more quickly and efficiently.
[0218] In some embodiments, starting the second process includes the electronic device displaying (814) a capture user interface (e.g., 742) on the display for capturing information regarding secure credentials using one or more camera sensors of the electronic device (e.g., capturing information from a card represented on or a displayed content associated with the secure credential) (in some embodiments, the capture user interface is different from the start user interface (e.g., 712)) (in some embodiments, the capture user interface includes a live preview of an image acquired by one or more camera sensors) (in some embodiments, the capture user interface includes a manual input affordance that, when selected, triggers the display of one or more text input fields and a virtual keyboard) (in some embodiments, starting the second process includes stopping the display of a start user interface that includes an affordance for adding a secure credential to the electronic device).
[0219] In some embodiments, starting the second process further includes receiving (816) information regarding secure credentials using one or more camera sensors of the electronic device.
[0220] In some embodiments, starting the second process further includes the electronic device receiving information regarding secure credentials and then inputting into the electronic device information regarding secure credentials (e.g., information received via one or more camera sensors, information determined based on information received via one or more camera sensors) (818) (in some embodiments, the information regarding secure credentials is used to generate (or issue) secure credentials stored in a secure element of the electronic device) (in some embodiments, the secure credentials stored in the secure element are released only after appropriate authentication has been provided).
[0221] In some embodiments, the second process includes performing one or more operations using a first-party application (e.g., an application developed and / or released by a manufacturer of the electronic device or an application developed and / or released by a developer of the operating system of the electronic device) of the electronic device (e.g., corresponding to 742). In some embodiments, the first process includes a third-party application of the electronic device (e.g., an application not developed and / or released by a manufacturer of the electronic device or an application not developed and / or released by a developer of the operating system of the electronic device), an application developed and / or released by an entity other than the manufacturer of the device and / or the operating system, different from the first-party application), a third-party application corresponding to an issuer of information associated with secure credentials (e.g., an administrator, regulator, or monitor of an activity associated with secure credentials) (e.g., the third-party application is developed and / or released by an issuer of information associated with secure credentials (e.g., an entity (e.g., a university) that issues an identification card having information associated with secure credentials, a bank that issues a bank card having information associated with secure credentials)) to perform one or more operations. Performing the second process using a first-party application improves the security of the device by ensuring that information regarding secure credentials is securely transmitted and / or stored.
[0222] In some embodiments, a secure credential is associated with an issuer of information associated with the secure credential (e.g., an administrator, regulator, or monitor of an activity associated with the secure credential), and (e.g., a third - party application is developed and / or released by an issuer of information associated with the secure credential (e.g., an entity (e.g., a university) that issues an identification card with information associated with the secure credential, a bank that issues a bank card with information associated with the secure credential)). Initiating a first process for entering information regarding the secure credential into an electronic device includes the electronic device displaying a list of candidate issuers (e.g., as a plurality of affordances (e.g., 746a - c)) according to a determination that the total number of candidate issuers of information associated with the secure credential is less than a predetermined threshold (e.g., 5, 10, 20). In some embodiments, according to a determination that the total number of candidate issuers of information associated with the secure credential is greater than or equal to a predetermined threshold, the electronic device simultaneously displays one or more text input fields (e.g., 722) and a virtual keyboard (e.g., 720) having a plurality of character keys for entering characters into the one or more text input fields (in some embodiments, the text input fields and the virtual keyboard are displayed without displaying a list of candidate issuers). Determining that the number of potential issuers of a payment card is less than a given number, displaying a list of candidate issuers provides the user with an efficient way to select an issuer associated with the secure credential.Displaying a list of candidate issuers when a set of conditions is met without a clear requirement to display the list improves the operability of the device, makes the user-device interface more efficient (e.g., by assisting the user in providing appropriate input when operating / interacting with the device and reducing user errors), and in addition, reduces power consumption and improves the battery life of the device by enabling the user to use the device more quickly and efficiently. For example, when the number of candidate issuers is small, it may be more efficient for the user to select a candidate issuer from the list rather than using a virtual keyboard to search for the issuer. When it is determined that the number of potential issuers of a payment card is greater than a predetermined number, displaying a user interface for refining the issuer provides the user with an efficient way to select an issuer associated with secure credentials. Displaying a user interface for searching for an issuer when a set of conditions is met without a clear requirement to display the user interface for that purpose improves the operability of the device, makes the user-device interface more efficient (e.g., by assisting the user in providing appropriate input when operating / interacting with the device and reducing user errors), and in addition, reduces power consumption and improves the battery life of the device by enabling the user to use the device more quickly and efficiently. For example, when the number of candidate issuers is large, it may be more efficient for the user to use a virtual keyboard to search for the issuer rather than scrolling through the list to find the desired issuer.
[0223] In some embodiments, while displaying multiple types of information, the electronic device receives (820) an input (e.g., 728, 750) corresponding to a selection of a second type of information (e.g., debit account information) (e.g., 724e).
[0224] In some embodiments, in response to receiving a selection of a second type of information, the electronic device initiates a process (822) for entering information regarding a secure credential into the electronic device that includes performing one or more operations using an application corresponding to the issuer of the second type of information (e.g., an administrator, regulator, monitor of an activity associated with the secure credential), (e.g., the third-party application is developed and / or released by an issuer of information associated with the secure credential (e.g., an entity (e.g., a university) that issues an identification card having information associated with the secure credential, a bank that issues a bank card having information associated with the secure credential)) that includes performing one or more operations. In some embodiments, the process for entering information regarding a secure credential includes performing one or more operations using an application provided by the issuer of the information associated with the secure credential when the information associated with the secure credential is of a second (e.g., specific (e.g., debit)) type of information. In such embodiments, the information regarding the secure credential is provided directly to the electronic device by the application provided by the issuer.
[0225] In some embodiments, starting a process of inputting information regarding secure credentials into an electronic device, which includes performing one or more operations using an application corresponding to the issuer of the second type of information, is according to a determination that the application corresponding to the issuer of the second type of information is installed (e.g., already installed) on the electronic device. The electronic device either starts the application corresponding to the issuer of the second type of information or, when selected, displays an affordance (e.g., 754) to start the application corresponding to the issuer of the second type of information (in some embodiments, starting the application includes launching the application). In some embodiments, according to a determination that the application corresponding to the issuer of the second type of information is not installed (e.g., not currently installed) on the electronic device, the electronic device starts a process of downloading the application corresponding to the issuer of the second type of information or displays an affordance (e.g., 732) (e.g., a user interface (e.g., 730)) to start a process of downloading the application corresponding to the issuer of the second type of information when selected (e.g., a user interface (e.g., 738) for downloading the application (e.g., an affordance (e.g., 740) to start downloading the application) of an application store or application library having an affordance (e.g., 732) to display it) (in some embodiments, starting the application is different from starting a process of downloading the application). Displaying an affordance to start the application corresponding to the issuer of the second type of information prompts the user to continue the process of adding secure credentials to the electronic device.Prompting the user improves the device's operability and (for example, by assisting the user in making appropriate inputs and reducing user errors when operating the device / interacting with the device) makes the user-device interface more efficient, which in turn reduces the device's power consumption and improves battery life by enabling the user to use the device more quickly and efficiently. Similarly, displaying an affordance to initiate the download of an application corresponding to the source of the second type of information prompts the user to continue the process of adding secure credentials to the electronic device. Prompting the user improves the device's operability and (for example, by assisting the user in making appropriate inputs and reducing user errors when operating the device / interacting with the device) makes the user-device interface more efficient, which in turn reduces the device's power consumption and improves battery life by enabling the user to use the device more quickly and efficiently.
[0226] In some embodiments, while an application corresponding to the source of the second type of information is active, the electronic device inputs (824) information regarding secure credentials into the electronic device. In some embodiments, the information regarding secure credentials is used to generate (or issue) secure credentials stored in a secure element of the electronic device. In some embodiments, the secure credentials stored within the secure element are released only when appropriate authentication is provided.
[0227] In some embodiments, following the input of information regarding secure credentials into the electronic device, the electronic device uses the information regarding secure credentials to complete a commercial transaction (826) by transmitting (for example, in an encrypted secure form) the information regarding secure credentials to an electronic device (such as a terminal, a server).
[0228] Note that the details of the process described above with respect to method 800 (e.g., FIGS. 8A-8C) apply equally to the methods described later. For example, method 800 optionally includes one or more of the characteristics of the various methods described later with reference to method 1000. For example, the provisioning process of method 800 can be used to input information regarding secure credentials (e.g., the first credentials described in method 1000) onto an electronic device. In another example, method 800 optionally includes one or more of the characteristics of the various methods described later with reference to method 1200. For example, the provisioning process of method 800 can be used to input information regarding secure credentials (e.g., the credentials described in method 1200) onto an electronic device. For the sake of brevity, these details are not repeated below.
[0229] FIGS. 9A-9J illustrate exemplary user interfaces for managing the use of provisioned credentials on an electronic device operating on stored power, according to some embodiments. The user interfaces in these figures are used to illustrate the processes described below, including the processes in FIGS. 10A-10C.
[0230] FIG. 9A shows an electronic device 700 (e.g., a smartphone, a mobile device) similar to the electronic device 700 described above with reference to FIGS. 7A-7O and the electronic devices 700 and 700B described below with reference to FIGS. 11A-11V. In some embodiments, the electronic device 700 includes a display 702, one or more input devices (e.g., a touch-sensing surface of the display 702, a mechanical input device 701 such as a power button, a camera 703, a microphone), one or more output devices (e.g., a speaker), and one or more sensors (e.g., a biometric sensor 704 such as a depth sensor, a fingerprint sensor). In some embodiments, one or more sensors of the electronic device 700 (e.g., a biometric sensor such as a fingerprint sensor) are integrated within different components / elements of the device (e.g., the fingerprint sensor is integrated with the display 702).
[0231] In some embodiments, the electronic device 700 operates on stored (electrical) power, such as power stored in one or more (rechargeable) batteries, one or more capacitors, and / or other types of power storage devices. In some embodiments, when the electronic device 700 has less than (or equal to) a threshold amount of stored power remaining as the power stored by the device (e.g., less than 1% of the maximum power capacity, less than 3% of the maximum power capacity, less than 5% of the maximum power capacity), the electronic device 700 is in a low power state (e.g., a low battery state), and when the device has more than (or equal to) the threshold amount of stored power remaining as the power stored by the device, it is in a normal power state (e.g., a non-low battery state).
[0232] In FIG. 9A, the display 702 of the electronic device 700 is in an off state (however, the device itself is in an on state). In FIG. 9B, while the display 702 is in the off state, the electronic device 700 receives an activation 901 of the mechanical input device 701 (e.g., a single click / press input, a double click / press input). Alternatively, in other embodiments, the electronic device 700 receives an activation (e.g., a single touch input, a double touch input) on the display 702 (instead of the activation 901 of the mechanical input device 701).
[0233] In some embodiments, when the electronic device 700 receives the activation 901 of the mechanical input button 701, the device is in the normal power state (e.g., non-low battery state). As shown in FIG. 9C, in response to detecting the activation 901 while the electronic device 700 is in the normal power state, according to the determination that the activation 901 is a first type of activation input (e.g., a single press click / input), the electronic device 700 displays a lock screen user interface 910 on the display 702. In some embodiments, the lock screen user interface 910 includes an indication 910A that the electronic device 700 is currently in the user interface locked state and an indication 910B of the current time and / or date.
[0234] In some embodiments, when the electronic device 700 receives an activation 901 of the mechanical input button 701, it is in a normal power state (e.g., a non-low battery state). In some embodiments, in response to detecting an activation 901 while the electronic device 700 is in a normal power state, according to a determination that the activation 901 is a second type of activation input (e.g., a double-click / input) different from a first type of activation input (e.g., a single-click / input), the electronic device 700, as shown in FIG. 9D, displays, on the display 702, a transfer application user interface 912 of a transfer application (e.g., a first electronic wallet application controlled by the device's operating system). The transfer application user interface 912 includes a representation 914 of a transfer account (e.g., a payment account, a point account, a transportation account, a store value account, a credit card account) corresponding to the transfer account currently selected for use in a transfer operation (e.g., a commercial transaction such as a payment transaction), and a stack 916 of one or more partially visible representations of transfer accounts corresponding to other transfer accounts not currently selected for use in the transfer operation. The transfer application user interface 912 also includes an instruction 918 requesting authentication (e.g., biometric authentication such as face recognition authentication, fingerprint authentication, or iris / retinal scan authentication, password or passphrase authentication) to provide authentication for proceeding with the transfer operation.
[0235] In some embodiments, when the electronic device 700 receives the activation 901 of the mechanical input button 701, the device is in a low-power state (e.g., a low-battery state). In some embodiments, in response to detecting the activation 901 while the electronic device 700 is in the low-power state, the electronic device 700 displays a low-power user interface 920 on the display 702, as shown in FIG. 9E. In some embodiments, the low-power user interface 920 is only displayed by the electronic device 700 when the device is in the low-power state (since it has less than a threshold amount of power remaining as stored power). The low-power user interface 920 includes an indication 922A that the electronic device 700 is currently in the low-power state (visually indicating the low-power state, such as a low-battery graphic / animation). The low-power user interface 920 also includes an indication 922B that the electronic device 700 can still perform one or more operations while in the low-power state (e.g., describing that "you can continue to use the express mode pass without a battery"). The low-power user interface 920 further includes an indication 922C that the electronic device 700 needs to be charged (for the device to return to the normal power state, where the device can only operate in the normal power state and perform operations that are not in the low-battery state, such as authentication operations).
[0236] FIG. 9F shows an electronic device 700 held by a user of the device while the user enters a transportation gateway 924 of a transportation station (e.g., subway station, railway station, bus station, airport) and while the device is in a low power state. In some embodiments, one or more transfer accounts (e.g., payment account, stored value account, transportation account, secure access card) provisioned on the electronic device 700 are in an "express mode". In some embodiments, an account set to express mode can be used by a payment transaction terminal (e.g., a merchant transaction terminal 926 of the transportation gateway 924) to perform a transfer operation via the electronic device 700 without receiving authentication from the user (e.g., biometric authentication such as face recognition authentication, fingerprint authentication, or iris / retinal scan authentication, password or password authentication) to authenticate the transfer operation. In some embodiments, an account not set to express mode or not available for use in express mode requires authentication from the user (e.g., biometric authentication such as face recognition authentication, fingerprint authentication, or iris / retinal scan authentication, password or password authentication) to authenticate the transfer operation. In some embodiments, a first type of transfer account (e.g., stored value account, secure access card, stored value account) can be used / set to express mode. In some embodiments, a second type of transfer account (e.g., credit card account) cannot be used / set to express mode.
[0237] As shown in FIG. 9F, the merchant transaction terminal 926 of the transportation gateway 924 of the transportation station generates a field 928 (e.g., a near field communication (NFC)-based field). In FIG. 9F, the electronic device 700 is not held within the range of the field 928 of the merchant transaction terminal 926 by the user. Accordingly, the electronic device 700 does not detect the presence of the field 928 (e.g., via the wireless communication radio of the device).
[0238] In FIG. 9G, the transfer accounts (e.g., transportation accounts) available (and set) in the express mode are provisioned on the electronic device 700. While the device is in the low power state, the device detects the presence of a field 928 generated by a commerce terminal 926 of a transportation gateway 924 (e.g., via the wireless communication radio of the device). In response to detecting the field 928 (and in accordance with the determination that the transfer account set in the express mode is available for use via the device), the electronic device 700 transmits credentials (e.g., of a provisioned transportation card, of a provisioned transportation pass) associated with the transfer account to the commerce terminal 926 of the transportation gateway 924 for use in a commerce transaction (e.g., payment or a pass to enter a transportation authority). In some embodiments, in accordance with the determination that a plurality of transfer accounts (set in the express mode) are available for use, the electronic device 700 automatically selects a compatible transfer account for use in a commerce transaction by the commerce terminal 926 (e.g., based on an identifier or tag detected based on the field 928).
[0239] In some embodiments, when the transfer operation between the electronic device 700 and the commerce terminal 926 includes a payment commerce transaction (e.g., transportation fees), the transfer account associated with the transmitted credentials is a stored value account associated with funds (e.g., a payment account) (and the funds from the transfer account in the amount of the transportation fees are used for the transfer operation). In some embodiments, when the transfer operation between the electronic device 700 and the commerce terminal 926 includes a transportation pass (not transportation fees), the transfer account associated with the transmitted credentials is a transportation pass account having a valid transportation pass (e.g., a one-day transportation pass, a monthly transportation pass).
[0240] In some embodiments, when a field 928 is detected and credentials are transmitted to the commerce terminal 926, the electronic device 700 displays a low-power user interface 920 on the display 702. In some embodiments, the electronic device 700 discontinues detection of the field 928 generated by the commerce terminal 926 if the display 702 is in an off state (and thus the device does not transmit credentials associated with the transfer account to the commerce terminal 926).
[0241] As shown in FIG. 9G, transmitting credentials (e.g., of a provisioned transit card, of a provisioned transit pass) to the commerce terminal 926 of the transit gateway 924 opens the gateway and thus enables the user of the electronic device 700 to enter the transit station.
[0242] In FIG. 9H, transfer accounts available for express use are provisioned on the electronic device 700, but when not set to express mode (or when none of the transfer accounts provisioned on the device can be used in express mode), the device detects the presence of a field 928 generated by the commerce terminal 926 of the transit gateway 924 (e.g., via the wireless communication radio of the device). In response to detecting the field 928, the electronic device 700 discontinues transmitting credentials associated with the transfer accounts provisioned on the device to the commerce terminal 926 (because no express mode transfer account is available on the device). Thus, as shown in FIG. 9H, the electronic device 700 does not open the transit gateway 924 and thus does not enable the user of the device to enter the transit station.
[0243] In some embodiments, when the electronic device 700 is in the normal power state, the device transmits the credentials associated with the compatible transfer account to the commercial transaction terminal 926 of the transportation gateway 924 without receiving authentication if the compatible transfer account is not set to the express mode (or is not available to be set to the express mode), or after receiving successful authentication (e.g., biometric authentication such as face recognition authentication, fingerprint authentication, or iris / retinal scan authentication, password or passcode authentication) when the compatible transfer account is set to the express mode.
[0244] FIG. 9I shows the electronic device 700 held by a user of the device near a secure access terminal 930 associated with a secure location (e.g., a secure entrance to a secure location such as a locked door to a secure room or building) while in the low power state. In some embodiments, the electronic device 700 displays a low power user interface 920 on the display 702. In some embodiments, the display 702 is in the off state (thus not displaying the low power user interface 920).
[0245] In FIG. 9I, the electronic device 700 detects the presence of a field 932 generated by a secure access terminal 930 (e.g., via the device's wireless communication radio). In some embodiments, the secure access terminal 930 is configured to control access to a secure location (e.g., a room, a building) by locking / unlocking a secure door 934. In response to (or subsequent to) detecting the presence of the field 932 generated by the secure access terminal 930, the electronic device 700 transmits (e.g., via the device's wireless communication radio) to the secure access terminal 930 the credentials of a transfer account (e.g., a secure access account), where the transfer account is a secure access account that has been pre-configured to be compatible with the secure access terminal 930. As shown in FIG. 9I, transmitting the credentials of the transfer account to the secure access terminal 930 causes the secure door 934 to open, thus enabling the user to enter the secure location. In some embodiments, as described in more detail below with reference to FIGS. 11M - 11N, the electronic device 700 can also transmit the credentials of the transfer account to the secure access terminal 930 while in the normal power state.
[0246] In some embodiments, if the transfer account is a secure access account that is not configured to be compatible with the secure access terminal 930, transmitting the credentials of the transfer account to the secure access terminal 930 does not cause the secure door 934 to open so that a valid (compatible) secure access account is not presented to the secure access terminal 930.
[0247] Figures 10A-10C are flow diagrams showing a method for managing the use of credentials provisioned on an electronic device operating on stored power, according to some embodiments. Method 1000 is executed on an electronic device (e.g., 100, 300, 500, 700, 700B) having a display (e.g., 702) and one or more input devices (e.g., a touch-sensing surface of the display, a mechanical input device (e.g., 701), a mechanical home button, a mechanical power button). In some embodiments, the electronic device also includes one or more sensors (e.g., a camera, a biometric sensor, a depth sensor, a fingerprint sensor). Some operations of method 1000 are optionally combined, the order of some operations is optionally changed, and some operations are optionally omitted.
[0248] As described below, method 1000 provides an intuitive way to manage the use of credentials provisioned on an electronic device operating on stored power. This method reduces the cognitive burden on the user when managing the use of credentials provisioned on an electronic device operating on stored power, thereby creating a more efficient human-machine interface. In the case of a battery-operated computing device, it saves power and increases the battery charging interval by enabling the user to more quickly and efficiently manage the use of credentials provisioned on an electronic device operating on stored power.
[0249] While the electronic device (e.g., 700) is operating on stored power (e.g., battery power, power stored in a capacitor, or other types of stored power), the electronic device detects (1002) a request to wake up the electronic device (e.g., 901) (e.g., activation of a mechanical input element such as a raise to a wake-up gesture, a tap on the touch-sensing surface of the display, a voice trigger, a button press on a mechanical input device).
[0250] In response to detecting (1004) a request (e.g., 901) for an electronic device (e.g., 700) to wake up, according to a determination (1006) that the electronic device has available power (e.g., stored power such as battery power, power stored in a capacitor, or other types of stored power) that exceeds a threshold amount, the electronic device displays (1008) a wake screen user interface (e.g., 910, lock screen or notification screen) on a display (e.g., 702). Displaying a wake screen user interface in response to detecting a request to wake up the device according to a determination that the device has available power that exceeds a threshold amount provides feedback regarding the current state of the device - the device is operating beyond a threshold amount of available power. By providing improved visual feedback to the user, the operability of the device is enhanced, (e.g., assisting the user to provide appropriate input when operating / interacting with the device and reducing user errors), making the user-device interface more efficient, and in addition, reducing power usage and improving the battery life of the device by enabling the user to use the device more quickly and efficiently.
[0251] In some embodiments, in accordance with a determination (1006) that the electronic device (e.g., 700) has exceeded a threshold amount of available power (e.g., after displaying a wake screen user interface), the electronic device displays (1010) on a display (e.g., 702) a representation of a first credential (e.g., 914, either of a first type or a second type) and a representation of a second credential (e.g., either of a first type or a second type). Displaying the representation of the first credential and the representation of the second credential enables a user to quickly and easily select between two different types of credentials. By providing additional control of the device, the operability of the device is improved, the user device interface is made more efficient (e.g., by assisting the user to provide appropriate input when operating / interacting with the device and reducing user errors), and in addition, the power consumption of the device is reduced by enabling the user to use the device more quickly and efficiently, improving battery life. In some embodiments, the representation of the first credential (e.g., 914) and the representation of the second credential are displayed within the user interface of a payment application, such as an electronic wallet application. In some embodiments, the electronic device detects (1012) a selection of the representation of the first credential via one or more input devices (e.g., the touch-sensitive surface of the display). In some embodiments, in response to detecting a selection of the representation of the first credential, the electronic device sets (1014) the first credential for use in a commercial transaction.
[0252] In some embodiments, more than a threshold amount of power available to the electronic device (e.g., 700) and a first credential not of the second type (e.g., not associated with a credit card or debit card) are provisioned on the electronic device, and an express mode setting associated with the first credential (e.g., represented by an express mode affordance such as a toggle that is either in an “on” mode or an “off” mode, and when in the off mode (and thus non-express mode), the electronic device requires authentication such as biometric authentication for the first type of credential to be available for use via the electronic device, and when in the on mode (and thus express mode), the electronic device does not require authentication of the first type of credential to be available via the electronic device) is not activated (e.g., is in non-express mode), the electronic device detects an input (e.g., a user input such as a touch input on the displayed express mode affordance) (1018) and activates the express mode setting (e.g., is in express mode).
[0253] In some embodiments, in response to detecting the force to activate the express mode setting, the electronic device displays (1020) on a display (e.g., 702) an indication (e.g., an alert, a notification, a prompt) that a first credential may be available for use via the electronic device while the electronic device has less than a threshold amount of available power. Displaying an indication that a first credential may be available for use via the electronic device when the electronic device has less than a threshold amount of available power in response to detecting an input to activate the express mode setting enables the user to quickly and easily recognize that the first credential may be available for use even while the electronic device has less than a threshold amount of available power, thereby improving feedback. By providing improved visual feedback to the user, the operability of the device is improved, (e.g., by assisting the user in providing appropriate input when operating / interacting with the device and reducing user errors), making the user-device interface more efficient, and in addition, reducing power usage and improving the battery life of the device by enabling the user to use the device more quickly and efficiently. In some embodiments, the indication indicates that the first credential is available for use via the electronic device when the electronic device has less than a threshold amount of available power but no available power at all (e.g., when the electronic device has no available power when the stored power has been completely / discharged). In some embodiments, the indication indicates that the first credential is not available for use via the electronic device while the electronic device has no available power. In some embodiments, the indication indicates that the first credential is available for use via the electronic device while the electronic device has more than a threshold amount of available power.
[0254] In response to detecting a request (e.g., 901) to start an electronic device (e.g., 700) (1004), and in accordance with a determination (1022) that the electronic device has less than a threshold amount of available power (e.g., the device is in a low battery state) and that a first type of credential (e.g., an express transit card, an express stored value account, an ID card, a card that does not require authentication) is provisioned on the electronic device, the electronic device simultaneously displays (1024) on a display (e.g., 702) an indication (e.g., 922A, low battery graphic) that the electronic device has less than a threshold amount of available power and an indication (e.g., 922B) that the first type of credential is available for use via the electronic device (e.g., for a commercial transaction, for payment). Displaying an indication that the electronic device has less than a threshold amount of available power in response to detecting a request to start the electronic device improves feedback by enabling the user to quickly and easily recognize that the device has and is operating with less than a threshold amount of available power. By providing improved visual feedback to the user, the operability of the device is enhanced, the user-device interface is made more efficient (e.g., by assisting the user to provide appropriate input when operating / interacting with the device and reducing user errors), and in addition, the power consumption is reduced and the battery life of the device is improved by enabling the user to use the device more quickly and efficiently.Displaying an indication that a first type of credential is available via an electronic device while the device has less than a threshold amount of available power enables the user to recognize that access to certain functions of the device remains available even while the device has less than the threshold amount of available power, thereby improving feedback and enhancing the operability of the device, and thus making the user-device interface more efficient (e.g., by assisting the user in providing appropriate input and reducing user errors when operating the device / interacting with the device), and in addition, reducing the power consumption of the device and improving battery life by enabling the user to use the device more quickly and efficiently.
[0255] In some embodiments, an electronic device (e.g., 700) includes a wireless communication radio (e.g., for NFC connection). In some embodiments, after displaying an indication (e.g., 922B) that a first type of credential is available for use via the electronic device (e.g., while the electronic device has less than a threshold amount of available power), the electronic device transmits (1026) the first type of credential to a second electronic device (e.g., 926, 930, a commerce terminal, a payment terminal, a secure access terminal) for use by the second electronic device in an operation (e.g., a payment transaction, a secure access authentication) via the wireless communication radio (e.g., via an NFC connection). Transmitting the first type of credential to the second electronic device (automatically), without requiring user selection of the credential, enables the user to proceed with the operation quickly and easily. By performing optimized operations when a set of conditions is met without requiring further user input, the operability of the device is improved, the user-device interface is made more efficient (e.g., by assisting the user to provide appropriate input when operating / interacting with the device and reducing user errors), and in addition, the power consumption is reduced and the battery life of the device is improved by enabling the user to use the device more quickly and efficiently.
[0256] In some embodiments, a first type of credential (e.g., an express transit card, an express store value account, an ID card, a card that does not require authentication) is provisioned (1028) onto an electronic device (e.g., 700) while (e.g., while having less than a threshold amount of power available to the device), and the electronic device detects (1030) the presence of a field (e.g., 928, 932, an NFC field) generated by a second electronic device (e.g., 926, 930, a commercial transaction terminal such as a wireless badge reader for determining whether to provide access to a secure resource / location (e.g., unlocking a door, unlocking a computer terminal, or the like), a transit terminal, a secure access terminal) that reads wireless identification information based on identification information and provides an indication (e.g., 922B) that the first type of credential is available for use via the electronic device (e.g., via the wireless communication radio of the device). In some embodiments, the field generated by the second electronic device encodes a request for the credential.
[0257] In some embodiments, in response to detecting the presence of a field generated by a second electronic device, the electronic device transmits (1032) a first type of credential to the second electronic device (e.g., via the wireless communication radio of the device) without first requiring authentication from the user (e.g., biometric authentication or passcode / password authentication). Transmitting the first type of credential to the second electronic device (automatically) without requiring user selection of the credential enables the user to proceed with the operation quickly and easily. By performing optimized operations when a set of conditions is met without requiring further user input, the operability of the device is improved, the user-device interface is made more efficient (e.g., by assisting the user in providing appropriate input when operating / interacting with the device and reducing user errors), and in addition, the power consumption is reduced and the battery life of the device is improved by enabling the user to use the device more quickly and efficiently. In some embodiments, the electronic device ceases to generate feedback (e.g., visual feedback, tactile feedback, audio feedback) when transmitting the first type of credential to the second electronic device while the device has less than a threshold amount of available power. In some embodiments, the electronic device generates feedback when transmitting the credential while the device has more than a threshold amount of available power. Ceasing to generate feedback while the device has less than a threshold amount of available power and generating feedback while the device has more than a threshold amount of available power improves the operability of the device by more efficiently utilizing the available power of the device, thereby reducing the power consumption and improving the battery life of the device.
[0258] In some embodiments, displaying an indication (922B) that a first type of credential is available for use via an electronic device (e.g., 700) includes displaying an indication that the first type of credential is available for use via the electronic device in accordance with a determination that an express mode setting (associated with the first type of credential) of the electronic device is on. In some embodiments, in accordance with a determination that the express mode setting is off, the electronic device stops displaying an indication that the first type of credential is available for use via the electronic device even when the device determines that it has less than a threshold amount of available power (e.g., the device is in a low battery state). In some embodiments, the electronic device applies the same express mode setting to all first type credentials provisioned on the electronic device. In some embodiments, each first type credential provisioned on the electronic device is associated with its own express mode setting. In some embodiments, the express mode setting can be adjusted (to “on” or “off”) by a user of the electronic device, either globally for all provisioned credentials of the first type or individually for each provisioned credential of the first type. Enabling the user to adjust the express mode setting provides the user with more control of the device, enables the user to use specific credentials in express mode (and thus without requiring authentication), and enables the user to use specific credentials in non-express mode (and thus requiring authentication), thereby improving the security of the device.By providing additional control of the device, the operability of the device is improved, the user-device interface is made more efficient (e.g., by assisting the user to provide appropriate input when operating / interacting with the device and reducing user errors), and in addition, the power consumption of the device is reduced and the battery life is improved by enabling the user to use the device more quickly and efficiently.
[0259] In response to detecting a request (e.g., 901) to wake an electronic device (e.g., 700) (1004), and according to a determination (1034) that the electronic device has less than a threshold amount of available power and that a first type of credential is not available for use via the electronic device, the electronic device displays an indication (e.g., 922A) on a display (e.g., 702) that the electronic device has less than the threshold amount of available power without displaying an indication that the electronic device is available for use via the electronic device. Displaying an indication that the electronic device has less than the threshold amount of available power without displaying an indication that the electronic device is available for use via the electronic device improves feedback by enabling the user to quickly and easily recognize that the device is operating with less than the threshold amount of available power and that the credential is not available for use via the device while the device is operating with less than the threshold amount of available power. By providing improved visual feedback to the user, the operability of the device is enhanced, the user-device interface is made more efficient (e.g., by assisting the user to provide appropriate input when operating / interacting with the device and reducing user errors), and in addition, the power consumption is reduced and the battery life of the device is improved by enabling the user to use the device more quickly and efficiently.
[0260] In some embodiments, a first type of credential is available for use via an electronic device (e.g., 700) while the electronic device has less than a threshold amount of available power (e.g., the device is in a low battery state), and a second type of credential, different from the first type, is not available for use via the electronic device while the electronic device has less than a threshold amount of available power. In some embodiments, the second type of credential requires authentication (e.g., biometric authentication such as face recognition authentication, fingerprint authentication, or iris / retinal scan authentication, passcode or password authentication) for use via the electronic device (e.g., for a commercial transaction such as a payment transaction). In some embodiments, the electronic device cannot perform authentication while the device has less than a threshold amount of available power. Thus, in some embodiments, since the second type of credential requires authentication for use via the electronic device, when the electronic device has less than a threshold amount of available power, the second type of credential cannot be used via the electronic device (e.g., for a commercial transaction such as a payment transaction), and the second type of credential can only be used via the electronic device when the electronic device has an amount of available power that is at least a threshold amount.
[0261] In some embodiments, a first type of credential does not require authentication (e.g., biometric authentication such as face recognition authentication, fingerprint authentication, or iris / retinal scan authentication, passcode or password authentication) for use via an electronic device (e.g., 700) (e.g., for a commercial transaction or payment), and a second type of credential, different from the first type, requires authentication for use via the electronic device.
[0262] In some embodiments, an electronic device (e.g., 700) enables an authentication operation (e.g., for authenticating provisioned credentials for use via the electronic device in a commercial transaction, payment, or secure access request) while the electronic device has more than a threshold amount of available power, and the electronic device disables the authentication operation while the electronic device has less than the threshold amount of available power. Enabling the authentication operation while the electronic device has available power above the threshold amount and disabling the authentication operation while the electronic device has less than the threshold amount of available power improves the device's operability by allowing the device to use its resources in a more efficient manner, thereby reducing power consumption and improving the device's battery life. In some embodiments, the authentication operation includes biometric authentication (e.g., facial recognition authentication, fingerprint authentication, iris / retinal scan authentication). In some embodiments, the authentication operation includes passcode or password authentication.
[0263] In some embodiments, an electronic device (e.g., 700) operates on stored power and has less than a threshold amount of available power (e.g., while the device's display is off) (1038). The electronic device detects the presence of a field (e.g., 928, 932, NFC field) generated by a second electronic device (e.g., 926, 930, commerce terminal, payment terminal, secure access terminal) (e.g., via the device's wireless communication radio) (1040). In some embodiments, in response to detecting the presence of a field generated by the second electronic device (e.g., corresponding to a request to perform a commerce transaction or a request for credentials) (1042), the electronic device determines that no authentication operation is required (e.g., based on information obtained from the second electronic device) and transmits a first type of credential to the second electronic device (e.g., for use in a payment commerce transaction or secure access authentication) (e.g., via the device's wireless communication radio) (1044). In some embodiments, in response to detecting the presence of a field generated by the second electronic device (e.g., corresponding to a request to perform a commerce transaction or a request for credentials) (1042), the electronic device discontinues transmitting a first type of credential to the second electronic device according to a determination that an authentication operation is necessary (1046).
[0264] In some embodiments, while an electronic device (e.g., 700) has less than a threshold amount of available power (e.g., the device is in a low battery state), the electronic device stops displaying a user interface different from a user interface associated with an indication that the electronic device has less than a threshold amount of available power (e.g., 922A, low battery graphic). Thus, in some embodiments, the electronic device can display only a user interface (e.g., 922) associated with an indication that the device has less than a threshold amount of available power while the device is in a low battery state. In some embodiments, while the device is in a low battery state, displaying a user interface different from a user interface associated with an indication that the device has less than a threshold amount of available power is disabled. Displaying only a user interface associated with an indication that the device has less than a threshold amount of available power while the device has less than a threshold amount of available power improves feedback by allowing the user to quickly and easily recognize that the device is operating and has less than a threshold amount of battery power. By providing improved visual feedback to the user, the operability of the device is enhanced, (e.g., assisting the user to provide appropriate input when operating / interacting with the device and reducing user errors), making the user-device interface more efficient, and in addition, reducing power usage and improving the battery life of the device by enabling the user to use the device more quickly and efficiently.
[0265] In some embodiments, the first type of credentials corresponds to a transportation account that is available (e.g., for transportation payments) for use via an electronic device (e.g., 700) at a transportation terminal (e.g., 928, subway station, railway station, bus, taxi business transaction terminal). In some embodiments, the transportation account is set with a business transaction limit or usage limit (e.g., a maximum amount per day, or $100 per day or $20 per business transaction). In some embodiments, the transportation account is a commuting plan (e.g., a monthly pass, a 10-day pass, a ride pass, etc.) or includes it. In some embodiments, while the electronic device has less than a threshold amount of available power, the electronic device detects the presence of a field (e.g., 928) generated by a transportation terminal (e.g., 926) and, based on information obtained from the transportation terminal, automatically selects credentials corresponding to the commuting plan if the transportation terminal is configured to accept the commuting plan. Automatically selecting credentials corresponding to the commuting plan when the transportation terminal is configured to accept the commuting plan allows the user to quickly and easily use a transportation terminal with minimal interaction with the device. By automatically performing an operation when a set of conditions is met without requiring further user input, the operability of the device is enhanced, the user-device interface is made more efficient (e.g., by assisting the user to provide appropriate input when operating / interacting with the device and reducing user errors), and in addition, the power consumption of the device is reduced and the battery life is improved by allowing the user to use the device more quickly and efficiently.
[0266] In some embodiments, the electronic device includes a first type of multiple credentials corresponding to different types of transportation agencies (e.g., the transportation account of a subway station, the transportation account of a bus). In some embodiments, while the electronic device has less than a threshold amount of available power, the electronic device detects the presence of a field (e.g., 928) generated by a transportation terminal (e.g., 926) and, based on the information obtained from the transportation terminal, automatically selects a credential corresponding to a related type of transportation account (e.g., the transportation account of a subway station or the transportation account of a bus) for use via the electronic device at that transportation terminal. Automatically selecting a credential corresponding to a related type of transportation account for use via the electronic device at that transportation terminal allows the user to quickly and easily use a device that is permitted to pass through the transportation terminal with minimal interaction with the device. By automatically performing an operation when a set of conditions is met without requiring further user input, the operability of the device is enhanced, the user-device interface is made more efficient (e.g., by assisting the user to provide appropriate input when operating / interacting with the device and reducing user errors), and in addition, the power consumption of the device is reduced and the battery life is improved by enabling the user to use the device more quickly and efficiently.
[0267] In some embodiments, the first type of credential corresponds to an identification account that is available for use via an electronic device (e.g., 700) at a secure access terminal (e.g., 930 for access to a secure area within a building such as a secure building or a particular room in a building). In some embodiments, the secure access terminal permits access to enter a secure building such as an office building or a dormitory building (e.g., via a secure door 934). In some embodiments, while the electronic device has less than a threshold amount of available power, the electronic device detects the presence of a field (e.g., 932) generated by the secure access terminal. In some embodiments, in response to detecting the presence of the field generated by the secure access terminal, the electronic device transmits the credential corresponding to the identification account to the secure access terminal, but ceases to display the representation of the identification account on a display. Transmitting (automatically) the credential corresponding to the identification account to the secure access terminal in response to detecting the presence of the field generated by the secure access terminal enables a device that permits a user to access a secure location via a secure access terminal with minimal interaction with the device to be used quickly and easily. By performing an operation when a set of conditions is met without requiring further user input, the operability of the device is enhanced, the user-device interface is made more efficient (e.g., by assisting the user to provide appropriate input when operating / interacting with the device and reducing user errors), and in addition, the power consumption of the device is reduced and the battery life is improved by enabling the user to use the device more quickly and efficiently.
[0268] Note that the details of the processes described above with respect to method 1000 (e.g., FIGS. 10A - 10C) are also applicable in a similar manner to the methods described above and below. For example, method 800 optionally includes one or more of the various method characteristics described above with reference to method 1000. For example, the provisioning process of method 800 can be used to provision a transfer account associated with credentials onto an electronic device. In another example, method 1200 optionally includes one or more of the various method characteristics described above with respect to method 1000. For example, the process described in method 1200 can be used to use credentials via an electronic device in a normal power state (in addition to a low - power state). For the sake of brevity, these details are not repeated below.
[0269] FIGS. 11A - 11V show exemplary user interfaces for managing the use of transfer accounts associated with different credentials on an electronic device, according to some embodiments. The user interfaces in these figures are used to illustrate the processes described below, including the processes in FIGS. 12A - 12C.
[0270] FIG. 11A shows an electronic device 700 described above with reference to FIGS. 7A-7O and an electronic device 700 similar to the electronic device 700 described above with reference to FIGS. 9A-9J (e.g., a smartphone, a mobile device). The electronic device 700 includes a display 702 and a wireless communication radio (e.g., for near-field communication (NFC), Bluetooth, WiFi, LTE connection). In some embodiments, the electronic device 700 includes one or more input devices (e.g., a touch-sensing surface of the display 702, a mechanical input device 701 such as a power button, a camera 703, a microphone), one or more output devices (e.g., a speaker), and one or more sensors (e.g., a depth sensor, a biometric sensor 704 such as a fingerprint sensor). In some embodiments, one or more sensors (e.g., a biometric sensor such as a fingerprint sensor) of the electronic device 700 are integrated within different components / elements of the device (e.g., the fingerprint sensor is integrated with the display 702).
[0271] In FIG. 11, the electronic device 700 displays a transfer application user interface 1110 of a transfer application (e.g., a first electronic wallet application controlled by the device's operating system) on the display 702. The transfer application user interface 1110 includes a representation 1112 of a transfer account (e.g., a payment account, a point account, a transportation account, a store value account, a credit card account) corresponding to the transfer account currently selected for use in a transfer operation (e.g., a commercial transaction such as a payment transaction, a secure access request) and a stack 1114 of (visible) representations of transfer accounts corresponding to other transfer accounts not currently selected for use in the transfer operation.
[0272] In some embodiments, a transfer identification account (e.g., an identification account such as a student ID card associated with one or more sub-accounts associated with funds, points, and / or credit) is provisioned on the electronic device 700. In some embodiments, the transfer identification account is provisioned on the electronic device 700 via the provisioning process described above with reference to FIGS. 7A - 7O and method 800. In some embodiments, the transfer identification account is a student identification account / card and is controlled / composed by a related institution such as a related university (e.g., Appleton University). In some embodiments, the transfer identification account is a student identification account / card that is also associated or linked with one or more sub-transfer accounts (e.g., a point account such as a stored value account, a debit account, a meal point account, a credit account such as a printer credit account).
[0273] As shown in FIG. 11A, the electronic device 700 displays a (partial) representation 1116 of the transfer identification account within the stack 1114 of the transfer application user interface 1110. Alternatively, in some embodiments, as shown in FIG. 11B, the electronic device 700 displays a (partial) representation 1116 of the transfer identification account and a region display representation 1112 corresponding to the currently selected transfer account within a region of the transfer application user interface 1110 separate from the region display stack 1114.
[0274] In FIG. 11B, while the transfer application user interface 1110 including the (partial) representation 1116 of the transfer identification account is displayed on the display 702, the electronic device 700 detects an activation 1101 (e.g., a touch input) of the (partial) representation 1116 of the transfer identification account (e.g., via the touch-sensitive surface of the display 702), thus setting the transfer identification account as the currently selected transfer account.
[0275] In FIG. 11C, in response to detecting the activation 1101 of the (partial) representation 1116 of the transfer identification account, the electronic device 700 displays the complete representation 1116 of the transfer identification account on the transfer application user interface 1110 (e.g., by replacing the display of the representation 1112 corresponding to the currently selected transfer account).
[0276] As shown in FIG. 11C, the representation 1116 of the transfer identification account includes an instruction 1118 and an image 1120 of an institution (e.g., a university) associated with the account. The representation 1116 of the transfer identification account also includes an image 1122, a name 1124 (Theo Appleseed), and a status 1126 (e.g., student, undergraduate, graduate, professor, staff) associated with the account owner (e.g., Theo Appleseed), and the account owner is associated with an institution (e.g., Appleton University) associated with the account. In this example, the account owner Theo Appleseed is a student at the institution Appleton University.
[0277] As shown in FIG. 11C, the representation 1116 of the transfer identification account includes at least a portion of a plurality of sub-account balance information 1128 associated with, linked / connected to, the transfer identification account, including first sub-account balance information 1128A (e.g., meal point balance), second sub-account balance information 1128B (e.g., laundry credit balance), and third sub-account balance information 1128C (e.g., parking credit balance). In some embodiments, the transfer identification account is associated with one or more sub-accounts where the sub-account balance information is not shown in the representation 1116 of the transfer identification account shown on the transfer application user interface 1110.
[0278] The representation 1116 of the transfer identification account further includes an information affordance 1130 for viewing a detailed description page associated with the transfer identification account, as will be described in more detail below with reference to FIG. 11P.
[0279] In FIG. 11D, while displaying the display 1116 of the transfer identification account within the currently selected area of the transfer application user interface 1110 on the display 702 (thereby indicating that the transfer identification account is currently selected for use in a transfer operation such as a commercial transaction or a secure access request), the electronic device 700 receives an input 1103 (e.g., a double click / press) on the mechanical input device 701.
[0280] In FIG. 11E, in response to detecting the input 1103 on the mechanical input device 701 while displaying the representation 1116 of the transfer identification account within the currently selected area of the transfer application user interface 1110, the electronic device 700 displays an authentication request 1132 (e.g., a visual indication or an animation) that requests authentication (e.g., biometric authentication such as face recognition authentication, fingerprint authentication, or iris / retinal scan authentication, password or passcode authentication) to the transfer application user interface 1110, and thus proceeds to a transfer operation (e.g., a commercial transaction or a secure access request) using the transfer identification account.
[0281] In FIG. 11F, in response to (or subsequent to, and then) displaying the authentication request 1132, while displaying the representation 1116 of the transfer identification account, the electronic device 700 receives / detects biometric information (e.g., the user's face feature information, the user's fingerprint information, the user's iris / retinal scan information) via (e.g., one or more input devices and / or one or more sensors such as the camera 703 and / or the biometric sensor 704 (e.g., a depth sensor), or a fingerprint sensor). As shown in FIG. 11F, while receiving / detecting the user's biometric information, the electronic device 700 displays a processing instruction 1134 (e.g., a visual indication such as a double-ring circular-shaped graphical animation) to the transfer application user interface 1110 indicating that the user's biometric information is being received / detected (e.g., replacing the display of the authentication request 1132). In some embodiments, in addition to or instead of biometric information, the electronic device 700 receives a password or passcode authentication to authenticate that the device proceeds to a transfer operation using the transfer identification account.
[0282] In FIG. 11G, in response to successful authentication, while displaying the representation 1116 of the transfer identification account, the electronic device 700 displays a success indication 1136 (e.g., a visual indication such as a smiling face graphic object) indicating that the authentication has been successful (thus, the device has been authenticated to proceed with the transfer operation using the transfer identification account) on the transfer application user interface 1110 (e.g., replacing the display of the processing instruction 1134).
[0283] In some embodiments, authentication is successful when the received or detected authentication information (e.g., received or detected biometric authentication information, received passcode / password authentication information) matches the authentication information (e.g., recorded biometric authentication information or registered passcode / password) already registered or recorded on the electronic device 700.
[0284] In some embodiments, in accordance with the determination that the authentication has failed (e.g., because the received / detected biometric authentication information does not match the registered biometric authentication information), the electronic device 700 revokes the permission for the transfer operation (thus, the device is not permitted to continue the transfer operation using the transfer identification account).
[0285] In FIG. 11H, after displaying the success indication 1136 (e.g., after a predetermined amount of time such as 0.5 seconds, 1 second, or 3 seconds), and while displaying the representation 1116 of the transfer identification account, the electronic device 700 displays a terminal proximity holding requirement 1138 (including, for example, a visual indication such as a graphical animation of the moving device and / or a text indication describing "hold near the reader") on the transfer application user interface 1110 (replacing the display of the success indication 1136), which requires the device to be placed near a terminal (e.g., a contactless payment merchant terminal, a transportation terminal, a secure access terminal) so that the device can detect a field (e.g., a near field communication (NFC)-based field) generated by the terminal (e.g., via the wireless communication radio of the device).
[0286] In FIG. 11H, after receiving a successful authentication (and thus while the near-terminal holding request 1138 is being displayed), while displaying the representation 1116 of the transfer identification account within the transfer application user interface 1110, the electronic device 700 detects the presence of the field 1142 generated by the washing machine commercial transaction terminal 1140 (e.g., via the wireless communication radio of the device). In some embodiments, the washing machine commercial transaction terminal 1140 is associated with / controlled by an institution associated with the transfer identification account (e.g., the University of Appleton).
[0287] In FIG. 11J, in response to (or subsequent to) detecting the presence of the field 1142 generated by the washing machine commercial transaction terminal 1140, the electronic device 700 transmits (e.g., via the wireless communication radio of the device) to the commercial transaction terminal 1140 the credentials of a second secondary account (e.g., a washing credit account) for use by the commercial transaction terminal 1140 in a transfer operation (e.g., payment of a washing credit for using the washing machine). In some embodiments, prior to transmitting the credentials of the second secondary account, the electronic device 700 automatically selects the second secondary account from a plurality of secondary accounts associated with / linked to the transfer identification account for use in the transfer operation (e.g., based on an identifier or tag detected based on the field 1142 of the commercial transaction terminal 1140).
[0288] As shown in FIG. 11J, in response to (or subsequent to) transmitting the credentials of the second sub-account to the commercial transaction terminal 1140, the electronic device 700 updates the display of the second sub-account balance information 1128B (e.g., a laundry credit account) to reflect the remaining balance of the second sub-account after the transfer operation (e.g., a $3 payment from the laundry credit account for laundry - thus, the remaining balance of the laundry credit decreases from $268.10 to $265.10). The electronic device 1100 also displays a success indicator 1144 (e.g., describing "Payment completed") in the transfer application user interface 1110 indicating that the transfer operation (e.g., including the use of laundry credit) has been successfully completed.
[0289] FIG. 11K shows the electronic device 700 that displays the transfer identification representation 1116 (as the currently selected account) and the near-terminal holding request 1138 (after successfully authenticating to authorize the device to continue the transfer operation using the transfer identification account) in the transfer application user interface 1110.
[0290] In FIG. 11K, after receiving a successful authentication with the transfer identification account as the currently selected account and while the transfer application user interface 1110 is being displayed, the electronic device 700 detects the presence of a field 1148 generated by a commercial transaction terminal 1146 associated with the university cafeteria (e.g., the cafeteria of the University of Appleton) (e.g., via the wireless communication radio of the device).
[0291] In FIG. 11L, in response to (or subsequent to) detecting the presence of field 1148 generated by cafeteria commerce terminal 1146, electronic device 700 transmits (e.g., via the device's wireless communication radio) to cafeteria commerce terminal 1146 the credentials of a first secondary account (e.g., a meal point account) for use in a transfer operation (e.g., transfer / inference of meal points from user Theo AppleSeed's meal point account). In some embodiments, prior to transmitting the credentials of the first secondary account, electronic device 700 automatically selects the first secondary account from a plurality of secondary accounts associated with / linked to a transfer identification account for use in the transfer operation (e.g., based on an identifier or tag detected based on field 1148 of cafeteria commerce terminal 1146).
[0292] As shown in FIG. 11L, in response to (or subsequent to) transmitting the credentials of the first secondary account to cafeteria commerce terminal 1146, electronic device 700 updates the display of first secondary account balance information 1128A to reflect the remaining balance of the first secondary account (e.g., a meal point account) (e.g., use of 1 meal point for a meal in the cafeteria - thus, the remaining meal point balance decreases from 4 to 3). Electronic device 1100 also displays in transfer application user interface 1110 a success indication 1150 (e.g., describing "meal exchange") indicating that the transfer operation (e.g., including use of meal points) has been successfully completed.
[0293] FIG. 11M shows an electronic device 700 held by a user of the device near a secure access terminal 1152 associated with a secure location (e.g., a secure entrance to a secure room or building, such as a locked door to a secure room or building). In FIG. 11M, the electronic device 700 is displaying a transfer application user interface 1110 having a transfer identification account currently selected for use in a transfer operation (as indicated by the representation 1116 of the transfer identification account). Alternatively, in some embodiments, the display 702 of the electronic device 700 is in an off state (and thus the device is not displaying the transfer application user interface 1110).
[0294] In FIG. 11M, the electronic device 700 detects the presence of a field 1154 generated by the secure access terminal 1152 (e.g., via the wireless communication radio of the device). In some embodiments, the secure access terminal 1152 is configured to control access to a secure location (e.g., a room, a building) by locking / unlocking a secure door 1156. In some embodiments, prior to detecting the presence of the field 1154 generated by the secure access terminal 1152, the electronic device 700 receives a successful authentication (e.g., biometric authentication such as face recognition authentication, fingerprint authentication, or iris / retinal scan authentication, password or passcode authentication) and authenticates the use of the transfer identification account in the secure access request. In some embodiments, the electronic device 700 does not receive authentication prior to detecting the presence of the field 1154 because the transfer identification account is an explicit account and / or is in express mode and thus no authentication is required to authorize the account for use in the transfer operation.
[0295] In some embodiments, in response to (or subsequent to) the detection of the presence of field 1154 generated by secure access terminal 1152, electronic device 700 transmits (e.g., via the device's wireless communication radio) access credentials for the transfer identification account to secure access terminal 1152, and the transfer identification account is preconfigured to be compatible with secure access terminal 1154. As shown in FIG. 11N, transmitting access credentials for the transfer identification account to secure access terminal 1152 causes secure door 1156 to open, thus enabling the user to enter the secure location.
[0296] In some embodiments, if the transfer identification account is not preconfigured to be compatible with secure access terminal 1152, transmitting access credentials for the transfer identification account to secure access terminal 1152 does not cause secure door 1156 to open so that a valid (compatible) secure access account is not presented to secure access terminal 1152.
[0297] In some embodiments (e.g., if the transfer identification account is not in explicit mode), authentication is required for the use of the transfer identification account in a secure access request having secure access terminal 1152, and thus, in some embodiments, transmitting access credentials for the transfer identification account to secure access terminal 1152 without receiving a successful authentication does not cause secure door 1156 to open even if the transfer identification account is compatible with secure access terminal 1152.
[0298] FIG. 11O shows an electronic device 700 that redisplay on the display 702 the transfer application user interface 1110 using the transfer identification account currently selected for use in a transfer operation (as indicated by the representation 1116 of the transfer identification account displayed within the current account area of the user interface). In FIG. 11O, while displaying the representation 1116 of the transfer identification account, the electronic device 700 detects an activation 1105 (e.g., a touch input) of the information affordance 1130 (e.g., via the touch-sensitive surface of the display 702).
[0299] As shown in FIG. 11P, in response to detecting the activation 1105 of the information affordance 1130, the electronic device 700 displays on the display an account details page 1158 that includes a plurality of information items and / or options associated with the transfer identification account. In some embodiments, the account details page 1158 includes an express mode affordance (e.g., a toggle having on and off states) that enables (in the on state) or disables (in the off state) the express mode setting of the transfer identification account. As described above, when the express mode is enabled, authentication (e.g., biometric authentication such as face recognition authentication, fingerprint authentication, or iris / retinal scan authentication, a passcode or passcode authentication) is not required to permit the transfer identification account for use in a transfer operation (e.g., using a secondary account associated with / linked to the transfer identification account) or to permit a secure access request (e.g., using access credentials associated with the transfer identification account). When the express mode is disabled, authentication (e.g., biometric authentication such as face recognition authentication, fingerprint authentication, or iris / retinal scan authentication, a passcode or passcode authentication) is required to permit the transfer identification account for use in a transfer operation (e.g., using a secondary account associated with / linked to the transfer identification account) or to permit a secure access request (e.g., using access credentials associated with the transfer identification account).
[0300] As shown in FIG. 11P, the account details page 1158 includes an account owner information area 1162 that contains the name 1162A of the account owner (e.g., Theo Appleseed) and the institutional identification number 1162B of the account owner (e.g., student ID number). The account details page 1158 also includes a sub - account balance area 1164 that shows the sub - accounts associated with / linked to the transfer - identifying account and the balance associated with each sub - account. In some embodiments, the transfer - identifying account is associated with / linked to four sub - accounts, but the representation 1116 of the transfer - identifying shown in the transfer application user interface 1110 includes a display of a maximum set number (e.g., 3) of sub - accounts. Thus, in some embodiments, the associated / linked sub - accounts are displayed in the representation 1116, while the sub - account balance area 1164 (e.g., the first sub - account balance 1164A corresponding to the meal point account, the second sub - account balance 1164B corresponding to the laundry credit account, the third sub - account balance 1164C corresponding to the parking credit account, and the fourth sub - account balance 1164D corresponding to the flexible spending account) is displayed.
[0301] In FIG. 11P, the account details page 1158 also includes a contact affordance 1166 for starting (wireless) communication (e.g., phone call, text message, email, chat) with the representation of the institution associated with the transfer - identifying account (e.g., Appleton University). The account details page 1158 further includes a removal affordance for de - provisioning / delinking the transfer - identifying account from the electronic device 700.
[0302] FIG. 11Q shows an electronic device 700B (e.g., a smartwatch, a device having one or more features of device 500) that includes, for example, a display 702B and a wireless communication radio (e.g., for NFC, Bluetooth, WiFi, LTE connection) and that displays a time user interface 1176 (which may also be a lock screen, for example) on the display 702B. The electronic device 700B includes one or more input devices (e.g., a touch sensing surface of the display 702B, a rotatable input device 703B, a mechanical input device 701B, a microphone) and one or more output devices (e.g., a tactile generator, a speaker).
[0303] In FIG. 11Q, while the time user interface 1176 is displayed on the display 702B, the electronic device 700B receives an input 1107 (e.g., a double click / press) on the mechanical input button 701B.
[0304] In response to receiving the input 1107 on the mechanical input button 701B, as shown in FIG. 11R, the electronic device 1100 displays a transfer application user interface 1178 (associated with / related to the transfer application user interface 1110 displayed on the electronic device 700) of a transfer application (e.g., a first party electronic wallet application controlled by / directly associated with the device's operating system) on the display 702B. In FIG. 11R, the electronic device 700B displays a representation 1180 of a transfer identification account (associated with / related to the representation 1116 of the transfer identification account displayed on the electronic device 700) within the transfer application user interface 1178.
[0305] The representation 1180 of the transfer identification account includes an image 1182, a name 1184 (e.g., Theo Appleseed), and a status 1186 (e.g., student, undergraduate, graduate student, professor, staff) associated with the account owner (e.g., Theo Appleseed), in the same manner as how these information are shown in the representation 1116 of the transfer identification account displayed on the electronic device 700. The representation 1180 of the transfer identification account also includes first sub-account balance information 1188A (e.g., corresponding to the meal point account) - in some embodiments, more sub-account balance information is shown in the representation 1116 of the transfer identification account displayed on the electronic device 700 than in the representation 1180 of the transfer identification account displayed on the electronic device 700B.
[0306] In some embodiments, the transfer application user interface 1178 includes one or more display elements 1190 corresponding to the number of accounts (including the transfer identification account) accessible by the electronic device 700B and indicating the currently displayed account (transfer identification account).
[0307] Figures 11R - 11T show the electronic device 700B that receives an input 1109 (e.g., a rotational input) on the rotatable input device 703B (e.g., in a clockwise direction) while displaying the transfer application user interface 1178 showing the representation 1180 of the transfer identification account, thereby scrolling the representation 1180 of the transfer identification. In response to detecting the input 1109 (alternatively, a touch scroll gesture on the touch-sensitive surface of the display 702B), the electronic device 700B displays additional information items in the representation 1180 of the transfer identification account (e.g., the first sub-account balance 1188A, the second sub-account balance 1188B, the third sub-account balance 1188C, and the fourth sub-account balance 1188D corresponding to the first sub-account balance 1164A, the second sub-account balance 1164B, the third sub-account balance 1164C, and the fourth sub-account balance 1164D shown in Figure 11P, respectively) that were not displayed before receiving the input 1109 (e.g., due to the limited display space of the electronic device 700B).
[0308] In FIG. 11U, while displaying a transfer application user interface 1178 that shows a representation 1180 of a transfer application account, the electronic device 1100 detects an input 1111 (e.g., a horizontal swipe on display 702B) (e.g., via the touch-sensing surface of display 702B). As shown in FIG. 11V, in response to detecting the input 1111, the electronic device 1100 displays a representation 1192 of a transfer account different from the transfer identification account (e.g., a payment account, a stored value account) in the transfer application user interface 1178 (e.g., replaces the display of the representation 1180 of the transfer identification account). In some embodiments, further in response to detecting the input 1111 (and thus replacing the display of the representation 1180 of the transfer identification account with the display of a representation 1192 of a different transfer account), the electronic device 1100 updates the display of the display element 1190 to indicate that a representation of a different transfer account is currently being displayed (and is currently selected for use in a transfer operation).
[0309] FIGS. 12A-12C are flow diagrams showing a method for managing the use of transfer accounts associated with different credentials on an electronic device, according to some embodiments. The method 1200 is executed on a device (e.g., 100, 300, 500, 700, 700B) having a display (e.g., 702, 702B) and a wireless communication radio (e.g., for NFC, Bluetooth, LTE, and / or WiFi connections). Some operations of the method 1200 are optionally combined, the order of some operations is optionally changed, and some operations are optionally omitted.
[0310] As described below, method 1200 provides an intuitive way to manage the use of transfer accounts associated with different credentials on an electronic device. This method reduces the user's cognitive burden when managing the use of transfer accounts associated with different credentials on an electronic device, thereby creating a more efficient human-machine interface. In the case of a battery-operated computing device, power is conserved and the battery charging interval is lengthened by enabling the user to more quickly and efficiently manage the use of transfer accounts associated with different credentials.
[0311] An electronic device (e.g., 700, 700B) receives (1202), via a wireless communication radio (e.g., for NFC connection), information indicating a request for credentials (e.g., a commercial transaction type identifier associated with a transfer of an item, such as a point, credit, resource, or funds transfer, or an access type identifier associated with authorization for access / entry to a specific secure location, such as a secure room or building, that is not associated with a transfer of an item and is received from a second electronic device (e.g., 1140, 1146, 1152, a secure access terminal such as a commercial transaction terminal, a building access terminal, a card reader)) while displaying a user interface (e.g., 1110, 1178) of a transfer application (e.g., an electronic wallet application).
[0312] In response to receiving information indicating a request for credentials from a second electronic device (e.g., 1140, 1146, 1152) (1204), if the information indicating the request for credentials is determined to be of a first type (e.g., a transfer type such as a commercial transaction type, a payment type, points, credit, or fund transfer) (1206), the electronic device (e.g., 700, 700B) displays on a display (e.g., 702, 702B) a request for authentication (e.g., 1132) (1208) for proceeding with a transfer operation (e.g., a fund transfer such as points, credit, resources, or payment) using a transfer account (associated with the first type of credentials associated with the electronic device, including a plurality of different balances such as funds, meal points, laundry credit, printer credit, etc., associated with / linked to an identification card / account). By displaying a request for authentication for proceeding with a transfer operation using a transfer account in response to receiving information indicating a request for credentials from a second electronic device, the user can quickly and easily recognize that the authentication required to authorize the device to proceed with the transfer operation is requested. By providing improved visual feedback to the user, the operability of the device is improved, (e.g., by assisting the user to provide appropriate input when operating / interacting with the device and reducing user errors), making the user-device interface more efficient, and in addition, reducing power consumption and improving the battery life of the device by enabling the user to use the device more quickly and efficiently. Requiring authentication for proceeding with a transfer operation using a transfer account also enhances the security of the device by preventing unauthorized use of the device and performing unauthorized transfer operations using the transfer account.
[0313] In some embodiments, the transfer account corresponds to the student identification account. In some embodiments, the student identification card is provisioned / linked onto an electronic device (e.g., 700, 700B) using the provisioning process described above with reference to FIGS. 7A - 7O.
[0314] In some embodiments, following (and during) the display of an authentication request to continue a transfer operation using a transfer account, an electronic device (e.g., 700, 700B) receives (1210) authentication information (biometric authentication information such as the user's face features or fingerprints, passcode or password authentication) via one or more input devices and / or sensors of the device (e.g., a camera, a biometric sensor (e.g., a depth sensor), and / or a fingerprint sensor). In some embodiments, in response to receiving the authentication information (1212), according to a determination that the received authentication information corresponds to registered authentication information (e.g., the user's registered biometric information such as registered face features or fingerprints, a registered passcode or password), the electronic device proceeds (1214) with a transfer operation (e.g., transferring points, credits, resources, or funds such as a payment) using the transfer account (e.g., using the balance associated with the transfer account). In some embodiments, in response to receiving the authentication information (1212), according to a determination that the received authentication information does not correspond to the registered authentication information, the electronic device proceeds (1216) with the transfer operation using the transfer account. In some embodiments, in addition to halting the progress of the transfer operation, the electronic device displays an indication that the authentication was unsuccessful. In some embodiments, the electronic device further displays an indication for the user to retry the authentication. Displaying an indication that the authentication was unsuccessful and / or displaying an indication for the user to retry the authentication improves feedback by enabling the user to quickly and easily recognize that further action (e.g., retrying the authentication) is required for the device to permit the authentication to be unsuccessful and proceed with the transfer operation using the transfer account. By providing the user with improved visual feedback, the operability of the device is improved, the user-device interface is made more efficient (e.g., by assisting the user to provide appropriate input when operating / interacting with the device and reducing user errors), and in addition, the power consumption is reduced and the battery life of the device is improved by enabling the user to use the device more quickly and efficiently.
[0315] In response to receiving information indicating a request for credentials from a second electronic device (e.g., 1140, 1146, 1152) (1204), in accordance with a determination (1218) that the information indicating a request for credentials is of a second type (e.g., an access type such as access to a secure location), the electronic device (e.g., 700, 700B) transmits (to the second electronic device) a second type of credentials associated with the transfer account via a wireless communication radio without requesting authentication (1220). Without further user input, transmitting the second type of credentials without requesting authentication in accordance with the determination that the information indicating a request for credentials is of a second type enables the user to use the device quickly and easily for transfer operations with minimal input. By reducing the number of inputs required to perform an operation, the device's operability is enhanced, the user-device interface is made more efficient (e.g., by assisting the user to provide appropriate inputs when operating / interacting with the device and reducing user errors), and in addition, by enabling the user to use the device more quickly and efficiently, the device's power consumption is reduced and the battery life is improved.
[0316] In some embodiments, an electronic device (e.g., 700, 700B) requests authentication before sending credentials to a second electronic device. Requiring authentication before sending credentials to a second electronic device enhances the security of the device by preventing unauthorized use of the device and preventing unauthorized transfer operations from being performed using the transfer account. Thus, in some embodiments, in accordance with a determination that the information indicating the request for credentials is of a second type (e.g., related to secure access permission), the electronic device requests authentication (e.g., biometric authentication such as face recognition authentication, fingerprint authentication, password or passcode authentication) (e.g., 1132) to proceed with sending the credentials to the second electronic device (e.g., to a user interface of a transfer operation such as an electronic wallet application). In some embodiments, in response to performing a successful authentication, the electronic device sends the credentials to the second electronic device.
[0317] In some embodiments, in accordance with a determination (1218) that information indicating a credential request is of a second type (e.g., an access type such as access to a secure location), an electronic device (e.g., 700, 700B) displays (1222) on a display (e.g., 702, 702B) a representation of a transfer account (e.g., 1116, 1180) (e.g., an ID card account such as a student ID card account) within a user interface (e.g., 1110, 1178) of a transfer application (e.g., an electronic wallet application) (e.g., within the electronic wallet application that is controlled / directly associated by the device's operating system) (in addition to sending the second type of credential to a second electronic device). Displaying a representation of a transfer account in accordance with a determination that information indicating a credential request is of a second type enables the user to quickly and easily recognize that the credential requested (by the second electronic device) is of the second type (and not of the first type), thereby improving feedback. By providing the user with improved visual feedback, the operability of the device is enhanced, (e.g., by assisting the user to provide appropriate input when operating / interacting with the device and reducing user errors), making the user-device interface more efficient, and in addition, reducing power consumption and improving the battery life of the device by enabling the user to use the device more quickly and efficiently.
[0318] In some embodiments, the information indicating a credential request is of a second type, and a second electronic device (e.g., 1152) is configured to control access to a secure location (e.g., configured to permit access to a secure location upon receiving a transmission of credentials that satisfy a set of access criteria (e.g., the credentials are authorized credentials), such as by unlocking a secure door 1156).
[0319] In some embodiments, before receiving information indicating a credential request, an electronic device (e.g., 700, 700B) displays (1224) on a display (e.g., 702, 702B) a representation of a transfer account (e.g., an ID card account such as a student ID card account) within, for example, a user interface (e.g., 1110, 1178 of a transfer application such as an electronic wallet application, where the electronic wallet application is controlled / directly associated by the device's operating system), and the representation of the transfer account (e.g., 1116, 1180) includes the sub-account balances associated with a plurality of sub-accounts (e.g., meal point account, laundry credit account, printer credit account) associated with (e.g., linked to) the transfer account. By displaying the sub-account balances associated with the plurality of sub-accounts associated with the transfer account in the representation of the transfer, the user can quickly and easily recognize the available balance of the sub-accounts associated with the transfer account, thereby improving the operability of the device, making the user-device interface more efficient (e.g., by assisting the user in providing appropriate input when operating / interacting with the device and reducing user errors), and in addition, reducing the power consumption of the device and improving battery life by enabling the user to use the device more quickly and efficiently. In some embodiments, the representation of the transfer account also includes the name of the person (e.g., student) associated with the account. In some embodiments, the representation of the transfer account also includes an image (e.g., a photo) of the person associated with the account.
[0320] In some embodiments, while displaying a request for authentication to proceed with the transfer operation, the electronic device (e.g., 700, 700B) receives (1226) an authentication (e.g., biometric authentication such as face recognition authentication, fingerprint authentication, iris / retinal scan authentication, password authentication) to proceed with the transfer operation via one or more input devices such as a camera, a biometric sensor (e.g., depth sensor), or a fingerprint sensor. In some embodiments, after receiving (e.g., responding to) a (successful) authentication to proceed with the transfer operation using the transfer account, the electronic device automatically selects (1228) a first sub-account (e.g., meal point account, laundry credit account, printer credit account) among a plurality of sub-accounts associated with the transfer account (e.g., corresponding to balances 1164A - 1164D) based on information received from a second electronic device (e.g., a commercial transaction terminal, a payment terminal). In some embodiments, after automatically selecting the first sub-account (e.g., in response to receiving a (successful) authentication and proceeding with the transfer operation using the transfer account), the electronic device proceeds with the transfer operation using the selected first sub-account (1230).
[0321] In some embodiments, the first sub-account is selected from the group consisting of a cash account, a meal point account, a laundry credit, and a printer credit.
[0322] In some embodiments, in response to receiving information indicating a request for credentials from a second electronic device (e.g., 1152) (1204), in accordance with a determination (1218) that the information indicating the request for credentials is of a second type (e.g., related to secure access authentication) (e.g., after displaying a request for authentication and receiving a successful authentication), the electronic device (e.g., 700, 700B) transmits (1232) the second type of credentials (to the second electronic device) via a wireless communication radio without causing a change to the secondary account balance (if any) of a plurality of secondary accounts associated with the transfer account. For example, the second electronic device is a secure access terminal (e.g., 1152) to a secure location (e.g., a secure building secured by a secure door 1156), and the credentials transmitted to the secure access terminal permit access to the secure location (e.g., by unlocking the door) without affecting any of the secondary account balances associated with the transfer account. By automatically transmitting the second type of credentials to the secure access terminal without affecting any of the secondary account balances associated with the transfer account, the user is enabled to obtain access to the secure location using the electronic device with minimal input. By reducing the number of inputs required to perform an operation, the operability of the device is improved, (e.g., by assisting the user in providing appropriate inputs when operating / interacting with the device and reducing user errors), the user-device interface is made more efficient, and in addition, power usage is reduced and the battery life of the device is improved by enabling the user to use the device more quickly and efficiently.
[0323] In some embodiments, while displaying a transfer account representation (e.g., 1116, 1180), an electronic device (e.g., 700, 700B) detects (1234) the activation (e.g., 1105, touch input) of an information affordance (e.g., 1130) of the transfer account representation (e.g., via the touch-sensing surface of the display). In some embodiments, in response to detecting the activation of the transfer account, the electronic device displays (1236) an information page (e.g., 1158 associated with the transfer account, the information page includes detailed information about the transfer account (e.g., different types of information (e.g., information not displayed as part of the transfer account representation) and options regarding the account, such as balance information, account number, account usage history, contact buttons to contact / call the account administrator)) on a display (e.g., 702, 702B).
[0324] In some embodiments, the information page includes a contact affordance (e.g., 1166) to contact (e.g., call) the administrator of the transfer account. By providing a contact affordance to contact the administrator of the transfer account within the information page associated with the transfer account, the user is enabled to quickly and easily contact the administrator as needed, thus improving the operability of the device and making the user-device interface more efficient (e.g., by assisting in reducing user errors when the user provides appropriate inputs and operates / interacts with the device), and in addition, reducing the power consumption of the device and improving battery life by enabling the user to use the device more quickly and efficien...
Claims
1. In an electronic device having a display, displaying, on the display, a start user interface including an affordance for adding secure credentials to the electronic device; receiving a request to add the secure credentials to the electronic device, the request corresponding to the affordance for adding the secure credentials; in response to receiving the request to add the secure credentials to the electronic device, starting, according to a determination that the electronic device was operating in a first context when the request to add the secure credentials was received, where the first context includes the electronic device being in a first location, starting a first process for inputting information regarding the secure credentials into the electronic device; starting, according to a determination that the electronic device was operating in a second context different from the first context when the request to add the secure credentials was received, where the second context includes the electronic device being in a second location different from the first location, starting a second process different from the first process for inputting information regarding the secure credentials into the electronic device. A method comprising the above.
2. The method according to claim 1, wherein the second process includes performing one or more operations using a first-party application of the electronic device, and the first process includes performing one or more operations using a third-party application of the electronic device different from the first-party application, and the third-party application corresponds to an issuer of information associated with the secure credentials.
3. The method according to claim 2, wherein the start user interface is an interface of the first-party application.
4. Starting the second process includes: displaying, on the display, a capture user interface for capturing the information regarding the secure credentials using one or more camera sensors of the electronic device. Receiving the information regarding the secure credential using the one or more camera sensors of the electronic device; After receiving the information regarding the secure credential, inputting the information regarding the secure credential into the electronic device, the method according to any one of claims 1 to 3.
5. The secure credential is associated with an issuer of information associated with the secure credential, and starting the first process for inputting the information regarding the secure credential into the electronic device can be Displaying a list of candidate issuers according to a determination that the total number of candidate issuers of the information associated with the secure credential is less than a predetermined threshold; According to a determination that the total number of the candidate issuers of the information associated with the secure credential is greater than or equal to the predetermined threshold, simultaneously displaying one or more text input fields and a virtual keyboard having a plurality of character keys for inputting characters into the one or more text input fields, the method according to any one of claims 1 to 4.
6. The secure credential is associated with an issuer of information associated with the secure credential, and starting the first process for inputting the information regarding the secure credential into the electronic device can be Receiving an input corresponding to the identification information of the issuer of the information associated with the secure credential; In response to receiving the input corresponding to the identification information of the issuer of the information associated with the secure credential, displaying a plurality of types of information issued by the issuer of the information, the plurality of types of information including at least a first type of information and a second type of information different from the first type of information, the method according to any one of claims 1 to 4.
7. Displaying an alternative input affordance while displaying the plurality of types of information; Receiving an input corresponding to the selection of the alternative input affordance; In response to receiving the input corresponding to the selection of the alternative input affordance, display, on the display, a capture user interface for capturing the information regarding the secure credential using one or more camera sensors of the electronic device. While the capture user interface is being displayed, receive the information regarding the secure credential using the one or more camera sensors of the electronic device. After receiving the information regarding the secure credential, further include inputting the information regarding the secure credential into the electronic device. The method according to claim 6.
8. While displaying the plurality of types of information, receive an input corresponding to the selection of the first type of information. In response to receiving the input corresponding to the selection of the first type of information, display, on the display, a capture user interface for capturing the information regarding the secure credential using one or more camera sensors of the electronic device. While the capture user interface is being displayed, receive the information regarding the secure credential using the one or more camera sensors of the electronic device. After receiving the information regarding the secure credential, further include inputting the information regarding the secure credential into the electronic device. The method according to claim 6.
9. While displaying the plurality of types of information, receive an input corresponding to the selection of the second type of information. In response to receiving the input corresponding to the selection of the second type of information, start a process of inputting the information regarding the secure credential into the electronic device, including performing one or more operations using an application corresponding to the issuer of the second type of information. The method according to claim 6.
10. Starting the process of inputting the information regarding the secure credential into the electronic device, including performing one or more operations using an application corresponding to the issuer of the second type of information. In accordance with a determination that the application corresponding to the issuer of the information of the second type is installed in the electronic device, starting the application corresponding to the issuer of the information of the second type, or, when selected, displaying an affordance for starting the application corresponding to the issuer of the information of the second type; In accordance with a determination that the application corresponding to the issuer of the information of the second type is not installed in the electronic device, starting a process for downloading the application corresponding to the issuer of the information of the second type, or, when selected, displaying an affordance for starting a process for downloading the application corresponding to the issuer of the information of the second type, the method according to claim 9.
11. The method according to claim 9 or 10, further comprising inputting the information regarding the secure credential into the electronic device while the application corresponding to the issuer of the information of the second type is active.
12. The method according to any one of claims 4, 7, 8, and 11, further comprising completing a commercial transaction using the information regarding the secure credential by transmitting the information regarding the secure credential to an external electronic device subsequent to inputting the information regarding the secure credential into the electronic device.
13. A computer program for causing a computer to execute the method according to any one of claims 1 to 12.
14. An electronic device, a memory storing the computer program according to claim 13, one or more processors capable of executing the computer program stored in the memory, and the electronic device is configured to communicate with a display, the electronic device.
15. An electronic device configured to communicate with a display, the electronic device having means for executing the method according to any one of claims 1 to 12.
Citation Information
Patent Citations
System for supporting integrated electronic payments and the method thereof
KR1020160016125A
Smartphone application enabling instant activation or deactivation of credit cards with the touch of a button
US20150170137A1
Classifying open-loop and closed-loop payment cards based on optical character recognition
US20160019529A1
Facilitating sending and receiving of peer-to-peer payments
US20160117666A1
Securely Accessing Secure Elements
US20160150410A1