User interface for loyalty and private label accounts on wearable devices
By simplifying the account linking and trading process on electronic devices, the complex and time-consuming user interface in the prior art is solved, and more efficient account management and battery life are achieved.
Patent Information
- Application Number
- CN202010830790.1
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Priority Date
- 2015-06-05
- Filing Date
- 2016-05-30
- Publication Date
- 2024-11-01
- Estimated Expiration
- 2036-05-30
AI Technical Summary
The prior art is complex and time-consuming when linking an account to an electronic device, selecting a trading account, and transmitting transaction information, resulting in wasting user time and device energy, especially in battery-driven devices.
Provides a faster and more efficient method and interface that reduces user input and processing power and saves battery life by receiving input on electronic devices, displaying visual indicators, enabling accounts, and participating in transactions through wireless communication components.
Simplifies account links and transaction processes, reduces user cognitive burden, reduces redundant inputs, improves user interface efficiency and device performance, and extends battery life.
Smart Images

Figure CN112085493B_ABST
Abstract
Description
[0001] CROSS-REFERENCE TO RELATED APPLICATIONS
[0002] This application is a divisional application of the invention patent application with Chinese national application number 201610371774.4, application date May 30, 2016, and invention name “User interface for loyalty accounts and private brand accounts for wearable devices”.
[0003] This patent application claims priority to U.S. Provisional Application Serial No. 62 / 230,430, filed on June 5, 2015, entitled “USER INTERFACE FOR LOYALTY ACCOUNTS AND PRIVATE LABEL ACCOUNTS FOR A WEARABLE DEVICE,” which is hereby incorporated by reference in its entirety for all purposes.
[0004] This patent application is related to the following provisional patent applications: U.S. patent application serial number 62 / 004,886, filed on May 29, 2014, entitled “USER INTERFACE FOR PAYMENTS” (reference number P22848USP1); U.S. patent application serial number 62 / 047,545, filed on September 8, 2014, entitled “USER INTERFACE FOR PAYMENTS” (reference number P22848USP2); U.S. patent application serial number 62 / 127,790, filed on March 3, 2015, entitled “USER INTERFACE FOR PAYMENTS” (reference number P22848USP3); and U.S. patent application serial number 62 / 136,930, filed on February 1, 2015, entitled “USER INTERFACE FOR No. 62 / 110,566, filed on December 6, 2013, entitled “PROVISIONING AND AUTHENTICATING CREDENTIALS ON AN ELECTRONIC DEVICE” (reference number P26049USP1); No. 61 / 912,727, filed on December 6, 2013, entitled “PROVISIONING OF CREDENTIALS ON AN ELECTRONIC DEVICE USING PASSWORDS COMMUNICATED OVER VERIFIED CHANNELS” (reference number P19950USP1); No. 61 / 909,717, filed on November 27, 2013, entitled “PROVISIONING OF CREDENTIALS ON AN ELECTRONIC DEVICE USING PASSWORDS COMMUNICATED OVER VERIFIED CHANNELS” (reference number P19950USP1); No. 61 / 912,727, filed on December 6 ... U.S. Patent Application Serial No. 62 / 004,182, filed on December 23, 2013, entitled “DELETION OF CREDENTIALS FROM AN ELECTRONIC DEVICE” (reference number P20450USP4); U.S. Patent Application Serial No. 61 / 920,029, filed on December 23, 2013, entitled “DELETION OF CREDENTIALS FROM AN ELECTRONIC DEVICE” (reference number P21084USP1); U.S. Patent Application Serial No. 61 / 899,737, filed on November 4, 2013, entitled “USING BIOAUTHENTICATION IN NEAR-FIELD-COMMUNICATION TRANSACTIONS” (reference number P21646USP1);U.S. Patent Application Serial No. 61 / 905,035, filed on November 15, 2013, entitled “GENERATING TRANSACTION IDENTIFIERS” (reference number P21714USP1); U.S. Patent Application Serial No. 61 / 905,042, filed on November 15, 2013, entitled “ELECTRONIC RECEIPTS FOR NFC-BASED FINANCIAL TRANSACTIONS” (reference number 21734USP1); U.S. Patent Application Serial No. 62 / 004,798, filed on May 29, 2014, entitled “FINANCIAL-TRANSACTION NOTIFICATIONS” (reference number P23211USP1); U.S. Patent Application Serial No. 62 / 004,798, filed on May 29, 2014, entitled “METHODS FOR MANAGING PAYMENT APPLETS ON A SECUREEMENT TO CONDUCT MOBILE PAYMENT TRANSACTIONS” (reference number P23215USP1); U.S. patent application serial number 62 / 004,840, filed on May 29, 2014, entitled “METHODS FOR OPERATING APORTABLE ELECTRONIC DEVICE TO CONDUCT MOBILE PAYMENT TRANSACTIONS” (reference number P23223USP1); U.S. patent application serial number 62 / 004,835, filed on May 29, 2014, entitled “METHODS FOR USING A PRIMARY USER DEVICE TO PROVISION CREDENTIALS ONTO A SECONDARYUSER DEVICE” (reference number P23224USP1); U.S. patent application serial number 62 / 004,835, filed on May 29, 2014, entitled “METHODS FOR USING A RANDOM AUTHORIZATION NUMBER TO PROVIDEENHANCED SECURITY FOR A SECURE ELEMENT” (reference number P23261USP1);U.S. Patent Application Serial No. 62 / 004,338, filed May 29, 2014, entitled “USER DEVICE SECURE PARTICIPATION INTRANSACTIONS VIA LOCAL SECURE ELEMENT DETECTION OF MECHANICAL INPUT” (reference number P22931USP1); and U.S. Utility Patent Application Serial No. 14 / 092,205, filed November 27, 2013, entitled “SECURE PROVISIONING OF CREDENTIALS ON AN ELECTRONIC DEVICE” (reference number P19545US1); each of which is hereby incorporated by reference in its entirety. ; Technical Field
[0005] The present disclosure relates generally to computer user interfaces, and more particularly to techniques for computer user interfaces for loyalty accounts and payment accounts. Background Art
[0006] In recent years, the use of electronic devices to make payments over the Internet at point-of-sale terminals has increased significantly. Exemplary point-of-sale terminals include near field communication (NFC) enabled terminals, Bluetooth enabled terminals, and barcode scanner enabled terminals. Electronic devices can be used in conjunction with these exemplary terminals to enable users of the electronic devices to make payments for the purchase of, for example, goods or services. Summary of the invention
[0007] However, some techniques for linking accounts to electronic devices, selecting accounts for transactions, and transmitting account information in transactions are often cumbersome and inefficient. For example, the prior art uses complex and time-consuming user interfaces that may include multiple keystrokes or keystrokes. The prior art requires more time than necessary, which results in wasted user time and device energy. This latter consideration is particularly important in battery-powered devices.
[0008] Therefore, the present invention provides a faster and more effective method and interface for electronic devices to link accounts to electronic devices, select accounts used in transactions, and transmit account information in transactions. Such methods and interfaces optionally supplement or replace other methods for performing similar tasks. Such methods and interfaces can reduce the cognitive burden caused to users and produce more effective man-machine interfaces. Such methods and interfaces can also reduce the number of unnecessary, redundant, repeated and / or redundant inputs, and can create faster and more effective user interface arrangements, which can reduce the number of required inputs, reduce processing power, and reduce the amount of time that the user interface needs to display in order to access and perform required functions. For battery-driven computing devices, such methods and interfaces save power and increase the time interval between two battery charges.
[0009] A method comprises: at an electronic device having a display, a touch-sensitive surface, and one or more wireless communication elements: receiving input for requesting that the device be enabled for a payment transaction; in response to receiving the input for requesting that the device be enabled for a payment transaction: displaying on the display a first visual indicator for identifying a first account; and enabling the electronic device to participate in transactions using the first account via the one or more wireless communication elements; receiving one or more swipe inputs in a first direction via the touch-sensitive surface; in response to receiving the one or more user swipe inputs: displaying on the display a second visual indicator for identifying a second account; and enabling the electronic device to participate in transactions using the second account via the one or more wireless communication elements; and wherein the first visual indicator is different from the second visual indicator.
[0010] A method comprising: at an electronic device having a display and a position sensor: detecting a current location using the position sensor; determining whether the current location is associated with a first account; displaying a visual indication of a default payment account on the display based on a failure to determine that the current location is associated with an account other than a default payment account; displaying a visual indication of the default payment account and a visual indication of the first account simultaneously on the display based on a determination that the current location is associated with the first account; and wherein the default payment account and the first account are linked to the electronic device, and the default payment account and the first account are different.
[0011] A method comprises: at an electronic device having a display and a position sensor: receiving input for requesting to enable the device to conduct a payment transaction; and in response to receiving the input: detecting a current location using the position sensor; determining whether a set of one or more payment criteria have been met, wherein the set of one or more payment criteria includes criteria that are met when the current location is associated with a first payment account; based on determining that the set of one or more payment criteria are not met, displaying a visual indication of a default payment account on the display, wherein the default payment account is different from the first payment account; and based on determining that the set of one or more payment criteria are met, displaying a visual indication of the first payment account on the display.
[0012] A method comprises: at an electronic device having a display and one or more wireless communication elements: receiving an input for requesting to enable the device to conduct a payment transaction; in response to receiving the input, displaying a payment indication on the display, the payment indication representing a plurality of payment accounts including a first payment account and a second payment account; receiving a request for account information corresponding to the payment transaction via the one or more wireless communication elements; in response to receiving the request for account information corresponding to the payment transaction: based on determining that payment criteria of the first payment account have been met, transmitting account information of the first payment account via the one or more wireless communication elements without transmitting account information of the second payment account; and based on determining that payment criteria of the second payment account have been met, transmitting account information of the second payment account via the one or more wireless communication elements without transmitting account information of the first payment account.
[0013] A method comprises: at an electronic device having a display, a touch-sensitive surface configured to detect intensity of contact, and one or more wireless communication elements: receiving a first input; in response to receiving the first input: displaying a first user interface on the display, wherein the first user interface comprises: a first visual indicator for identifying a payment card associated with multiple payment accounts, and a second visual indicator for identifying a first payment account among the multiple payment accounts of the payment card; enabling the electronic device to participate in a payment transaction using the first payment account via the one or more wireless communication elements; detecting a first contact on the touch-sensitive surface; determining whether a characteristic intensity of the first contact is above an intensity threshold; and based on determining that the characteristic intensity of the first contact is above the intensity threshold, displaying a second user interface on the display, wherein the second user interface enables selection between different payment accounts represented by the first visual indicator.
[0014] A method comprises: at a first electronic device having a display and one or more wireless communication elements: receiving a first request for linking a payment account associated with a payment card to the first electronic device; in response to receiving the first request, initiating a process for linking the payment account to the first electronic device; after successfully linking the payment account to the first electronic device, simultaneously displaying on the display: an indication that the payment account has been successfully linked to the first electronic device; and an optional enable indication for linking the payment account to a second electronic device different from the first electronic device; and receiving activation of the optional enable indication; and in response to receiving activation of the optional enable indication, initiating a process for linking the payment account to the second electronic device.
[0015] A method comprises: at a first electronic device having a display and one or more wireless communication elements: displaying on the display a payment account user interface of a second electronic device associated with the first electronic device, wherein displaying the payment account user interface comprises simultaneously displaying: a representation of a first payment account together with status information of the first payment account, the status information indicating that the first payment account is linked to the second electronic device and that the second electronic device is configured to enable payment using the first payment account; and a representation of a second payment account together with status information of the second payment account, the status information indicating that the second payment account is linked to the first electronic device but not linked to the second electronic device.
[0016] An electronic device comprises: a display; a touch-sensitive surface; and a device for receiving an input for requesting that the device be enabled for a payment transaction; a device for performing the following operations in response to receiving the input for requesting that the device be enabled for a payment transaction: displaying a first visual indicator for identifying a first account on the display; and enabling the electronic device to participate in transactions using the first account via the one or more wireless communication elements; a device for receiving one or more swipe inputs in a first direction via the touch-sensitive surface; a device for performing the following operations in response to receiving the one or more user swipe inputs: displaying a second visual indicator for identifying a second account on the display; and enabling the electronic device to participate in transactions using the second account via the one or more wireless communication elements; and wherein the first visual indicator is different from the second visual indicator.
[0017] An electronic device comprises: a display; a touch-sensitive surface; and a device for detecting a current location using the location sensor; a device for determining whether the current location is associated with a first account; a device for displaying a visual indication of a default payment account on the display based on a failure to determine that the current location is associated with an account other than a default payment account; a device for simultaneously displaying a visual indication of the default payment account and a visual indication of the first account on the display based on a determination that the current location is associated with the first account; and wherein the default payment account and the first account are linked to the electronic device, and the default payment account and the first account are different.
[0018] An electronic device comprises: a display; a touch-sensitive surface; and a device for receiving input for requesting to enable the device to conduct a payment transaction; and a device for performing the following operations in response to receiving the input: detecting a current location using the location sensor; determining whether a set of one or more payment criteria has been met, wherein the set of one or more payment criteria includes criteria that are met when the current location is associated with a first payment account; based on determining that the set of one or more payment criteria is not met, displaying a visual indication of a default payment account on the display, wherein the default payment account is different from the first payment account; and based on determining that the set of one or more payment criteria is met, displaying a visual indication of the first payment account on the display.
[0019] An electronic device comprises: a display; a touch-sensitive surface; and a device for receiving an input for requesting to enable the device to conduct a payment transaction; a device for displaying a payment indication on the display in response to receiving the input, the payment indication representing multiple payment accounts including a first payment account and a second payment account; a device for receiving a request for account information corresponding to a payment transaction via the one or more wireless communication elements; a device for performing the following operations in response to receiving the request for account information corresponding to the payment transaction: based on determining that the payment criteria of the first payment account have been met, transmitting the account information of the first payment account via the one or more wireless communication elements without transmitting the account information of the second payment account; and based on determining that the payment criteria of the second payment account have been met, transmitting the account information of the second payment account via the one or more wireless communication elements without transmitting the account information of the first payment account.
[0020] An electronic device comprises: a display; a touch-sensitive surface configured to detect the intensity of a contact; and a device for receiving a first input; a device for displaying a first user interface on the display in response to receiving the first input, wherein the first user interface comprises: a first visual indicator for identifying a payment card associated with multiple payment accounts, and a second visual indicator for identifying a first payment account among the multiple payment accounts of the payment card; a device for enabling the electronic device to participate in a payment transaction using the first payment account via the one or more wireless communication elements; a device for detecting a first contact on the touch-sensitive surface; a device for determining whether a characteristic intensity of the first contact is above an intensity threshold; and a device for displaying a second user interface on the display based on determining that the characteristic intensity of the first contact is above the intensity threshold, wherein the second user interface enables selection between different payment accounts represented by the first visual indicator.
[0021] An electronic device comprises: a display; a touch-sensitive surface; and a device for receiving a first request for linking a payment account associated with a payment card to the first electronic device; a device for initiating a process for linking the payment account to the first electronic device in response to receiving the first request; a device for simultaneously displaying the following items on the display after successfully linking the payment account to the first electronic device: an indication that the payment account has been successfully linked to the first electronic device; and an optional enable indication for linking the payment account to a second electronic device different from the first electronic device; and a device for receiving activation of the optional enable indication; and a device for initiating a process for linking the payment account to the second electronic device in response to receiving activation of the optional enable indication.
[0022] An electronic device comprises: a display; a touch-sensitive surface; and a device for displaying a payment account user interface of a second electronic device associated with the first electronic device on the display, wherein displaying the payment account user interface comprises simultaneously displaying: a representation of a first payment account together with status information of the first payment account, the status information indicating that the first payment account is linked to the second electronic device and that the second electronic device is configured to enable payments to be made using the first payment account; and a representation of a second payment account together with status information of the second payment account, the status information indicating that the second payment account is linked to the first electronic device but not linked to the second electronic device.
[0023] A non-transitory computer-readable storage medium, comprising one or more programs for execution by one or more processors of an electronic device having a display, a touch-sensitive surface, and one or more wireless communication elements, the one or more programs comprising instructions that, when executed by the one or more processors, cause the electronic device to: receive input requesting that the device be enabled for a payment transaction; in response to receiving input requesting that the device be enabled for a payment transaction: display a first visual indicator on the display for identifying a first account; and enable the electronic device to participate in transactions using the first account via the one or more wireless communication elements; receive one or more swipe inputs in a first direction via the touch-sensitive surface; in response to receiving the one or more user swipe inputs: display a second visual indicator on the display for identifying a second account; and enable the electronic device to participate in transactions using the second account via the one or more wireless communication elements; and wherein the first visual indicator is different from the second visual indicator.
[0024] An electronic device comprises: a display; a touch-sensitive surface; one or more wireless communication elements; one or more processors; a memory; and one or more programs stored in the memory, the one or more programs comprising instructions that, when executed by the one or more processors, cause the electronic device to: receive input requesting that the device be enabled for a payment transaction; in response to receiving input requesting that the device be enabled for a payment transaction: display a first visual indicator on the display for identifying a first account; and enable the electronic device to participate in transactions using the first account via the one or more wireless communication elements; receive one or more swipe inputs in a first direction via the touch-sensitive surface; in response to receiving the one or more user swipe inputs: display a second visual indicator on the display for identifying a second account; and enable the electronic device to participate in transactions using the second account via the one or more wireless communication elements; and wherein the first visual indicator is different from the second visual indicator.
[0025] A non-transitory computer-readable storage medium, comprising one or more programs for execution by one or more processors of an electronic device having a display and a position sensor, the one or more programs comprising instructions that, when executed by the one or more processors, cause the electronic device to: detect a current location using the position sensor; determine whether the current location is associated with a first account; based on failing to determine that the current location is associated with an account other than a default payment account, display a visual indication of the default payment account on the display; based on determining that the current location is associated with the first account, simultaneously display a visual indication of the default payment account and a visual indication of the first account on the display; and wherein the default payment account and the first account are linked to the electronic device, and the default payment account and the first account are different.
[0026] An electronic device comprises: a display; a position sensor; one or more processors; a memory; and one or more programs stored in the memory, wherein the one or more programs include instructions that, when executed by the one or more processors, cause the electronic device to: detect a current position using the position sensor; determine whether the current position is associated with a first account; based on failing to determine that the current position is associated with an account other than a default payment account, display a visual indication of the default payment account on the display; based on determining that the current position is associated with the first account, simultaneously display a visual indication of the default payment account and a visual indication of the first account on the display; and wherein the default payment account and the first account are linked to the electronic device, and the default payment account and the first account are different.
[0027] A non-transitory computer-readable storage medium comprises one or more programs for execution by one or more processors of an electronic device having a display and a position sensor, the one or more programs comprising instructions which, when executed by the one or more processors, cause the electronic device to: receive input for requesting that the device be enabled for a payment transaction; and in response to receiving the input: detect a current location using the position sensor; determine whether a set of one or more payment criteria has been met, wherein the set of one or more payment criteria includes criteria that are met when the current location is associated with a first payment account; based on a determination that the set of one or more payment criteria has not been met, display a visual indication of a default payment account on the display, wherein the default payment account is different from the first payment account; and based on a determination that the set of one or more payment criteria has been met, display a visual indication of the first payment account on the display.
[0028] An electronic device comprises: a display; a position sensor; one or more processors; a memory; and one or more programs stored in the memory, wherein the one or more programs include instructions that, when executed by the one or more processors, cause the electronic device to: receive input for requesting that the device be enabled for a payment transaction; and in response to receiving the input: detect a current location using the position sensor; determine whether a set of one or more payment criteria has been met, wherein the set of one or more payment criteria includes criteria that are met when the current location is associated with a first payment account; based on determining that the set of one or more payment criteria has not been met, display a visual indication of a default payment account on the display, wherein the default payment account is different from the first payment account; and based on determining that the set of one or more payment criteria has been met, display a visual indication of the first payment account on the display.
[0029] A non-transitory computer-readable storage medium comprises one or more programs for execution by one or more processors of an electronic device having a display and one or more wireless communication elements, the one or more programs comprising instructions which, when executed by the one or more processors, cause the electronic device to: receive input for requesting that the device be enabled for a payment transaction; in response to receiving the input, display a payment indication on the display, the payment indication representing a plurality of payment accounts including a first payment account and a second payment account; receive a request for account information corresponding to the payment transaction via the one or more wireless communication elements; in response to receiving the request for account information corresponding to the payment transaction: based on determining that payment criteria for the first payment account have been met, transmit account information for the first payment account via the one or more wireless communication elements without transmitting account information for the second payment account; and based on determining that payment criteria for the second payment account have been met, transmit account information for the second payment account via the one or more wireless communication elements without transmitting account information for the first payment account.
[0030] An electronic device comprises: a display; one or more wireless communication elements; one or more processors; a memory; and one or more programs stored in the memory, wherein the one or more programs include instructions that, when executed by the one or more processors, cause the electronic device to: receive an input for requesting that the device be enabled to perform a payment transaction; in response to receiving the input, display a payment indication on the display, wherein the payment indication represents a plurality of payment accounts including a first payment account and a second payment account; receive a request for account information corresponding to the payment transaction via the one or more wireless communication elements; in response to receiving the request for account information corresponding to the payment transaction: based on determining that the payment criteria of the first payment account have been met, transmit the account information of the first payment account via the one or more wireless communication elements without transmitting the account information of the second payment account; and based on determining that the payment criteria of the second payment account have been met, transmit the account information of the second payment account via the one or more wireless communication elements without transmitting the account information of the first payment account.
[0031] A non-transitory computer-readable storage medium comprising one or more programs for execution by one or more processors of an electronic device having a display, a touch-sensitive surface configured to detect intensity of contact, and one or more wireless communication elements, the one or more programs comprising instructions that, when executed by the one or more processors, cause the electronic device to: receive a first input; in response to receiving the first input: display a first user interface on the display, wherein the first user interface comprises: a first visual indicator for identifying a payment card associated with multiple payment accounts, and a second visual indicator for identifying a first payment account among the multiple payment accounts of the payment card; enable the electronic device to participate in a payment transaction using the first payment account via the one or more wireless communication elements; detect a first contact on the touch-sensitive surface; determine whether a characteristic intensity of the first contact is above an intensity threshold; and based on determining that the characteristic intensity of the first contact is above the intensity threshold, display a second user interface on the display, wherein the second user interface enables selection between different payment accounts represented by the first visual indicator.
[0032] An electronic device comprises: a display; a touch-sensitive surface configured to detect the intensity of a contact; one or more wireless communication elements; one or more processors; a memory; and one or more programs stored in the memory, the one or more programs comprising instructions that, when executed by the one or more processors, cause the electronic device to: receive a first input; in response to receiving the first input: display a first user interface on the display, wherein the first user interface comprises: a first visual indicator for identifying a payment card associated with a plurality of payment accounts, and a second visual indicator for identifying a first payment account among the plurality of payment accounts of the payment card; enable the electronic device to participate in a payment transaction using the first payment account via the one or more wireless communication elements; detect a first contact on the touch-sensitive surface; determine whether a characteristic intensity of the first contact is above an intensity threshold; and based on determining that the characteristic intensity of the first contact is above the intensity threshold, display a second user interface on the display, wherein the second user interface enables selection between different payment accounts represented by the first visual indicator.
[0033] A non-transitory computer-readable storage medium comprises one or more programs for execution by one or more processors of a first electronic device having a display and one or more wireless communication elements, the one or more programs comprising instructions which, when executed by the one or more processors, cause the first electronic device to: receive a first request for linking a payment account associated with a payment card to the first electronic device; in response to receiving the first request, initiate a process for linking the payment account to the first electronic device; after successfully linking the payment account to the first electronic device, simultaneously display on the display: an indication that the payment account has been successfully linked to the first electronic device; and an optional enable indication for linking the payment account to a second electronic device different from the first electronic device; and receive activation of the optional enable indication; and in response to receiving activation of the optional enable indication, initiate a process for linking the payment account to the second electronic device.
[0034] A first electronic device comprises: a display; one or more wireless communication elements; one or more processors; a memory; and one or more programs stored in the memory, wherein the one or more programs include instructions that, when executed by the one or more processors, cause the first electronic device to: receive a first request for linking a payment account associated with a payment card to the first electronic device; in response to receiving the first request, initiate a process for linking the payment account to the first electronic device; after successfully linking the payment account to the first electronic device, simultaneously display on the display: an indication that the payment account has been successfully linked to the first electronic device; and an optional enable indication for linking the payment account to a second electronic device different from the first electronic device; and receive activation of the optional enable indication; and in response to receiving activation of the optional enable indication, initiate a process for linking the payment account to the second electronic device.
[0035] A non-transitory computer-readable storage medium comprises one or more programs for execution by one or more processors of a first electronic device having a display and one or more wireless communication elements, the one or more programs comprising instructions which, when executed by the one or more processors, cause the first electronic device to: display on the display a payment account user interface of a second electronic device associated with the first electronic device, wherein displaying the payment account user interface comprises simultaneously displaying: a representation of a first payment account together with status information of the first payment account, the status information indicating that the first payment account is linked to the second electronic device and that the second electronic device is configured to enable payments to be made using the first payment account; and a representation of a second payment account together with status information of the second payment account, the status information indicating that the second payment account is linked to the first electronic device but not linked to the second electronic device.
[0036] A first electronic device, comprising: a display; one or more wireless communication elements; one or more processors; a memory; and one or more programs stored in the memory, the one or more programs comprising instructions that, when executed by the one or more processors, cause the first electronic device to: display on the display a payment account user interface of a second electronic device associated with the first electronic device, wherein displaying the payment account user interface comprises simultaneously displaying: a representation of a first payment account together with status information of the first payment account, the status information indicating that the first payment account is linked to the second electronic device and that the second electronic device is configured to enable payments to be made using the first payment account; and a representation of a second payment account together with status information of the second payment account, the status information indicating that the second payment account is linked to the first electronic device but not linked to the second electronic device.
[0037] An electronic device comprises: a touch-sensitive surface unit; a display unit; a wireless communication unit including one or more wireless communication elements; and a processing unit coupled to the display unit, the touch-sensitive surface unit and the wireless communication unit, the processing unit being configured to: receive an input for requesting to enable the device to perform a payment transaction; in response to receiving the input for requesting to enable the device to perform a payment transaction: enable display of a first visual indicator for identifying a first account on the display unit; and enable the electronic device to participate in transactions using the first account via the one or more wireless communication elements; receive one or more swipe inputs in a first direction via the touch-sensitive surface unit; in response to receiving the one or more user swipe inputs: enable display of a second visual indicator for identifying a second account on the display unit; and enable the electronic device to participate in transactions using the second account via the one or more wireless communication elements; and wherein the first visual indicator is different from the second visual indicator.
[0038] An electronic device comprises: a display unit; a position sensor unit; and a processing unit coupled to the display unit and the position sensor unit, the processing unit being configured to: detect a current position using the position sensor unit; determine whether the current position is associated with a first account; enable display of a visual indication of a default payment account on the display unit based on failure to determine that the current position is associated with an account other than a default payment account; enable simultaneous display of a visual indication of the default payment account and a visual indication of the first account on the display unit based on determination that the current position is associated with the first account; and wherein the default payment account and the first account are linked to the electronic device, and the default payment account and the first account are different.
[0039] An electronic device comprises: a display unit; a position sensor unit; and a processing unit coupled to the display unit and the position sensor unit, the processing unit being configured to: receive an input for requesting to enable the device to conduct a payment transaction; and in response to receiving the input: detect a current position using the position sensor unit; determine whether a set of one or more payment criteria has been met, wherein the set of one or more payment criteria includes criteria that are met when the current location is associated with a first payment account; based on determining that the set of one or more payment criteria has not been met, enable display of a visual indication of a default payment account on the display unit, wherein the default payment account is different from the first payment account; and based on determining that the set of one or more payment criteria has been met, enable display of a visual indication of the first payment account on the display unit.
[0040] An electronic device comprises: a display unit; a wireless communication unit comprising one or more wireless communication elements; and a processing unit coupled to the display unit and the wireless communication unit, the processing unit being configured to: receive an input for requesting to enable the device to perform a payment transaction; in response to receiving the input, enable display of a payment indication on the display unit, the payment indication representing a plurality of payment accounts including a first payment account and a second payment account; receive a request for account information corresponding to the payment transaction via the one or more wireless communication elements; in response to receiving the request for account information corresponding to the payment transaction: based on determining that the payment criteria of the first payment account have been met, transmit the account information of the first payment account via the one or more wireless communication elements without transmitting the account information of the second payment account; and based on determining that the payment criteria of the second payment account have been met, transmit the account information of the second payment account via the one or more wireless communication elements without transmitting the account information of the first payment account.
[0041] An electronic device comprises: a display unit; a touch-sensitive surface unit; a wireless communication unit comprising one or more wireless communication elements; and a processing unit coupled to the display unit and configured to detect the intensity of a contact, wherein the processing unit is configured to: receive a first input; in response to receiving the first input: enable display of a first user interface on the display unit, wherein the first user interface comprises: a first visual indicator for identifying a payment card associated with a plurality of payment accounts, and a second visual indicator for identifying a first payment account among the plurality of payment accounts of the payment card; enable the electronic device to participate in a payment transaction using the first payment account via the one or more wireless communication elements; detect a first contact on the touch-sensitive surface unit; determine whether a characteristic intensity of the first contact is higher than an intensity threshold; and based on determining that the characteristic intensity of the first contact is higher than the intensity threshold, enable display of a second user interface on the display unit, wherein the second user interface enables selection between different payment accounts represented by the first visual indicator.
[0042] A first electronic device comprises: a display unit; a wireless communication unit having one or more wireless communication elements; and a processing unit coupled to the display unit and the wireless communication unit, the processing unit being configured to: receive a first request for linking a payment account associated with a payment card to the first electronic device; in response to receiving the first request, initiate a process for linking the payment account to the first electronic device; after successfully linking the payment account to the first electronic device, enable simultaneous display on the display unit of: an indication that the payment account has been successfully linked to the first electronic device; and an optional enable indication for linking the payment account to a second electronic device different from the first electronic device; and receive activation of the optional enable indication; and in response to receiving activation of the optional enable indication, initiate a process for linking the payment account to the second electronic device.
[0043] A first electronic device comprises: a display unit; a wireless communication unit comprising one or more wireless communication elements; and a processing unit coupled to the display unit and the wireless communication unit, the processing unit being configured to: enable display of a payment account user interface of a second electronic device associated with the first electronic device on the display unit, wherein enabling display of the payment account user interface comprises enabling simultaneous display of: a representation of a first payment account together with status information of the first payment account, the status information indicating that the first payment account is linked to the second electronic device and that the second electronic device is configured to enable payment using the first payment account; and a representation of a second payment account together with status information of the second payment account, the status information indicating that the second payment account is linked to the first electronic device but not linked to the second electronic device.
[0044] A transient computer-readable storage medium includes one or more programs for execution by one or more processors of an electronic device having a display, a touch-sensitive surface, and one or more wireless communication elements, the one or more programs including instructions that, when executed by the one or more processors, cause the electronic device to: receive input requesting that the device be enabled for a payment transaction; in response to receiving input requesting that the device be enabled for a payment transaction: display a first visual indicator on the display for identifying a first account; and enable the electronic device to participate in transactions using the first account via the one or more wireless communication elements; receive one or more swipe inputs in a first direction via the touch-sensitive surface; in response to receiving the one or more user swipe inputs: display a second visual indicator on the display for identifying a second account; and enable the electronic device to participate in transactions using the second account via the one or more wireless communication elements; and wherein the first visual indicator is different from the second visual indicator.
[0045] A transient computer-readable storage medium includes one or more programs for execution by one or more processors of an electronic device having a display and a position sensor, the one or more programs including instructions that, when executed by the one or more processors, cause the electronic device to: detect a current location using the position sensor; determine whether the current location is associated with a first account; based on failing to determine that the current location is associated with an account other than a default payment account, display a visual indication of the default payment account on the display; based on determining that the current location is associated with the first account, display a visual indication of the default payment account and a visual indication of the first account on the display at the same time; and wherein the default payment account and the first account are linked to the electronic device, and the default payment account and the first account are different.
[0046] A transient computer-readable storage medium comprises one or more programs for execution by one or more processors of an electronic device having a display and a position sensor, the one or more programs comprising instructions which, when executed by the one or more processors, cause the electronic device to: receive input for requesting that the device be enabled for a payment transaction; and in response to receiving the input: detect a current location using the position sensor; determine whether a set of one or more payment criteria has been met, wherein the set of one or more payment criteria includes criteria that are met when the current location is associated with a first payment account; based on a determination that the set of one or more payment criteria has not been met, display a visual indication of a default payment account on the display, wherein the default payment account is different from the first payment account; and based on a determination that the set of one or more payment criteria has been met, display a visual indication of the first payment account on the display.
[0047] A transient computer-readable storage medium includes one or more programs for execution by one or more processors of an electronic device having a display and one or more wireless communication elements, the one or more programs including instructions that, when executed by the one or more processors, cause the electronic device to: receive input for requesting that the device be enabled for a payment transaction; in response to receiving the input, display a payment indication on the display, the payment indication representing multiple payment accounts including a first payment account and a second payment account; receive a request for account information corresponding to the payment transaction via the one or more wireless communication elements; in response to receiving the request for account information corresponding to the payment transaction: based on determining that the payment criteria of the first payment account have been met, transmit the account information of the first payment account via the one or more wireless communication elements without transmitting the account information of the second payment account; and based on determining that the payment criteria of the second payment account have been met, transmit the account information of the second payment account via the one or more wireless communication elements without transmitting the account information of the first payment account.
[0048] A transient computer-readable storage medium comprises one or more programs for execution by one or more processors of an electronic device having a display, a touch-sensitive surface configured to detect intensity of contact, and one or more wireless communication elements, the one or more programs comprising instructions that, when executed by the one or more processors, cause the electronic device to: receive a first input; in response to receiving the first input: display a first user interface on the display, wherein the first user interface comprises: a first visual indicator for identifying a payment card associated with multiple payment accounts, and a second visual indicator for identifying a first payment account among the multiple payment accounts of the payment card; enable the electronic device to participate in a payment transaction using the first payment account via the one or more wireless communication elements; detect a first contact on the touch-sensitive surface; determine whether a characteristic intensity of the first contact is above an intensity threshold; and based on determining that the characteristic intensity of the first contact is above the intensity threshold, display a second user interface on the display, wherein the second user interface enables selection between different payment accounts represented by the first visual indicator.
[0049] A transient computer-readable storage medium comprises one or more programs for execution by one or more processors of a first electronic device having a display and one or more wireless communication elements, the one or more programs comprising instructions which, when executed by the one or more processors, cause the first electronic device to: receive a first request for linking a payment account associated with a payment card to the first electronic device; in response to receiving the first request, initiate a process for linking the payment account to the first electronic device; after successfully linking the payment account to the first electronic device, simultaneously display on the display: an indication that the payment account has been successfully linked to the first electronic device; and an optional enable indication for linking the payment account to a second electronic device different from the first electronic device; and receive activation of the optional enable indication; and in response to receiving activation of the optional enable indication, initiate a process for linking the payment account to the second electronic device.
[0050] A transient computer-readable storage medium comprises one or more programs for execution by one or more processors of a first electronic device having a display and one or more wireless communication elements, the one or more programs comprising instructions which, when executed by the one or more processors, cause the first electronic device to: display on the display a payment account user interface of a second electronic device associated with the first electronic device, wherein displaying the payment account user interface comprises simultaneously displaying: a representation of a first payment account together with status information of the first payment account, the status information indicating that the first payment account is linked to the second electronic device and that the second electronic device is configured to enable payments to be made using the first payment account; and a representation of a second payment account together with status information of the second payment account, the status information indicating that the second payment account is linked to the first electronic device but not linked to the second electronic device.
[0051] Thus, a faster, more efficient method and interface is provided for devices for linking accounts to the devices, selecting accounts for transactions, and transmitting account information in transactions, thereby increasing the effectiveness, efficiency, and user satisfaction of such devices. Such methods and interfaces may supplement or replace other methods for performing similar tasks.
[0052] Executable instructions for performing these functions are optionally included in a non-transitory computer-readable storage medium or other computer program product configured for execution by one or more processors. Executable instructions for performing these functions are optionally included in a transient computer-readable storage medium or other computer program product configured for execution by one or more processors. BRIEF DESCRIPTION OF THE DRAWINGS
[0053] For a better understanding of the various described embodiments, reference should be made to the following detailed description taken in conjunction with the following drawings, wherein like reference numerals refer to corresponding parts throughout the drawings.
[0054] Figure 1A is a block diagram illustrating a portable multifunction device with a touch-sensitive display according to some embodiments.
[0055] Figure 1B is a block diagram illustrating example components for event processing according to some embodiments.
[0056] Figure 2 A portable multifunction device with a touch screen according to some embodiments is shown.
[0057] Figure 3 is a block diagram of an exemplary multifunction device with a display and a touch-sensitive surface according to some embodiments.
[0058] Figure 4A An exemplary user interface for an application menu on a portable multifunction device according to some embodiments is shown.
[0059] Figure 4B An exemplary user interface is shown for a multifunction device having a touch-sensitive surface separate from the display according to some embodiments.
[0060] Figure 5A A personal electronic device according to some embodiments is shown.
[0061] Figure 5B is a block diagram illustrating a personal electronic device according to some embodiments.
[0062] Figure 5C-5D Example components of a personal electronic device with a touch-sensitive display and an intensity sensor are shown according to some embodiments.
[0063] Figure 5E-5H Exemplary components and user interfaces of a personal electronic device according to some embodiments are shown.
[0064] Fig.5I Example devices connected via one or more communication channels to complete a payment transaction are shown in accordance with some embodiments.
[0065] Figures 6A-6G Exemplary techniques and exemplary user interfaces for receiving selections of accounts are shown according to some embodiments.
[0066] Figure 7 is a flowchart illustrating a method for receiving a selection of an account according to some embodiments.
[0067] Figures 8A-8D Exemplary techniques and exemplary user interfaces for selecting an account according to some embodiments are shown.
[0068] Fig. 9 is a flow chart illustrating a method for selecting an account according to some embodiments.
[0069] Figures 10A-10E Exemplary techniques and exemplary user interfaces for selecting an account according to some embodiments are shown.
[0070] Fig.11 is a flowchart illustrating a method for selecting an account according to some embodiments.
[0071] Figures 12A-12D Exemplary techniques and exemplary user interfaces for transferring account information for an account according to some embodiments are shown.
[0072] Fig.13 is a flowchart illustrating a method for transmitting account information of an account according to some embodiments.
[0073] Figures 14A-14E Exemplary techniques and exemplary user interfaces for receiving selections of accounts are shown according to some embodiments.
[0074] Fig.15 is a flowchart illustrating a method for receiving a selection of an account according to some embodiments.
[0075] FIG. 16A to FIG. 16G Exemplary methods and exemplary user interfaces for linking a payment account to one or more electronic devices are shown according to some embodiments.
[0076] Fig.17 is a flowchart illustrating a method for linking a payment account to one or more electronic devices according to some embodiments.
[0077] 18A to 18C An exemplary method and exemplary user interface for linking a payment account to an electronic device according to some embodiments are shown.
[0078] Fig.19 is a flow chart illustrating a method for linking a payment account to an electronic device according to some embodiments.
[0079] Figure 20-26 A functional block diagram according to some embodiments is shown. DETAILED DESCRIPTION
[0080] The following description sets forth exemplary methods, parameters, etc. However, it should be appreciated that such description is not intended to limit the scope of the present disclosure, but is provided as a description of exemplary embodiments.
[0081] There is a need for electronic devices that provide more efficient methods and interfaces for linking accounts to the electronic device, selecting accounts for transactions, and transmitting account information in transactions. Specifically, there is a need for efficient methods and interfaces for wearable devices such as smart watches. Such techniques can reduce the cognitive burden of users accessing event notifications, thereby improving productivity. In addition, such techniques can reduce processor power and battery power that would otherwise be wasted on redundant user input.
[0082] Hereinafter, 1A-1B, Figure 2 , Figure 3 , Figure 4A-4B and Figure 5A-5B A description of an exemplary apparatus is provided. Figures 6A-6G Example techniques and example user interfaces for receiving a selection of an account are shown. Figure 7is a flow chart illustrating a method for receiving a selection of an account. Figures 6A-6G The user interface in Figure 7 process. Figures 8A-8D Exemplary techniques and exemplary user interfaces for selecting an account are shown. Fig. 9 is a flow chart illustrating a method for selecting an account. Figures 8A-8D The user interface in Fig. 9 process. Figures 10A-10E Exemplary techniques and exemplary user interfaces for selecting an account are shown. Fig.11 is a flowchart illustrating a method for selecting an account according to some embodiments. Figures 10A-10E The user interface in Fig.11 process. Figures 12A-12D Exemplary techniques and exemplary user interfaces for transferring account information for an account are shown. Fig.13 is a flowchart illustrating a method for transmitting account information of an account according to some embodiments. Figures 12A-12D The user interface in Fig.13 process. Figures 14A-14E Example techniques and example user interfaces for receiving a selection of an account are shown. Fig.15 is a flow chart illustrating a method for receiving a selection of an account. Figures 14A-14E The user interface in Fig.15 process. Figures 16A-16G Exemplary techniques and exemplary user interfaces for linking a payment account to one or more electronic devices are shown. Fig.17 is a flow chart illustrating a method for linking a payment account to one or more electronic devices. Figures 16A-16G The user interface in Fig.17 process. 18A to 18C An exemplary method and exemplary user interface for linking a payment account to an electronic device according to some embodiments are shown. Fig.19 is a flow chart illustrating a method for linking a payment account to an electronic device. Figures 18A-18C The user interface in Fig.19 process.
[0083] Although the following description uses the terms "first", "second", etc. to describe various elements, these elements should not be limited by the terms. These terms are only used to distinguish one element from another element. For example, a first touch can be named a second touch and similarly a second touch can be named a first touch without departing from the scope of the various described embodiments. Both the first touch and the second touch are touches, but they are not the same touch.
[0084] The terms used in the description of the various embodiments described herein are only for the purpose of describing specific embodiments and are not intended to be limiting. As used in the description of the various embodiments described and in the appended claims, the singular forms "a", "an" and "the" are intended to also include plural forms unless the context clearly indicates otherwise. It will also be understood that the term "and / or" used herein refers to and encompasses any and all possible combinations of one or more items in the items listed in association. It will also be understood that the term "includes", "including", "comprises" and / or "comprising" when used in this specification specifies the presence of stated features, integers, steps, operations, elements and / or parts, but does not exclude the presence or addition of one or more other features, integers, steps, operations, elements, parts and / or their groupings.
[0085] Depending on the context, the term "if" may be interpreted to mean "when" or "upon" or "in response to determining" or "in response to detecting." Similarly, the phrases "if it is determined that ..." or "if [a stated condition or event] is detected" may be interpreted to mean "upon determining that ..." or "in response to determining that ..." or "upon detecting [a stated condition or event]" or "in response to detecting [a stated condition or event]," depending on the context.
[0086] Embodiments of electronic devices, user interfaces for such devices, and associated processes for using such devices are described herein. In some embodiments, the device is a portable communication device such as a mobile phone that also includes other functions such as a PDA and / or a music player function. Exemplary embodiments of portable multifunction devices include, but are not limited to, the Apple Watch from Apple Inc (Cupertino, California). iPod and Device. Other portable electronic devices, such as laptops or tablet computers with touch-sensitive surfaces (e.g., touch screen displays and / or touch pads) are optionally used. It should also be understood that in some embodiments, the device is not a portable communication device, but a desktop computer with a touch-sensitive surface (e.g., touch screen displays and / or touch pads).
[0087] In the following discussion, an electronic device including a display and a touch-sensitive surface is described. However, it should be understood that the electronic device optionally includes one or more other physical user interface devices, such as a physical keyboard, mouse and / or joystick.
[0088] The device may support a variety of applications, such as one or more of the following applications: a drawing application, a presentation application, a word processing application, a website creation application, a disk editing application, a spreadsheet application, a gaming application, a telephony application, a video conferencing application, an email application, an instant messaging application, a fitness support application, a photo management application, a digital camera application, a digital video camera application, a web browsing application, a digital music player application, and / or a digital video player application.
[0089] Various applications executing on the device optionally use at least one common physical user interface device such as a touch-sensitive surface. One or more functions of the touch-sensitive surface and corresponding information displayed on the device are optionally adjusted and / or varied from one application to the next and / or within a respective application. In this way, a common physical architecture of the device (such as a touch-sensitive surface) optionally supports a variety of applications with a user interface that is intuitive and clear to the user.
[0090] Attention is now directed to embodiments of portable devices having touch-sensitive displays. Figure 1A 1 is a block diagram illustrating a portable multifunction device 100 with a touch-sensitive display system 112 according to some embodiments. The touch-sensitive display 112 is sometimes referred to as a "touch screen" for convenience, and may sometimes be referred to as or referred to as a "touch-sensitive display system." The device 100 includes a memory 102 (which optionally includes one or more computer-readable storage media), a memory controller 122, one or more processing units (CPUs) 120, a peripheral device interface 118, an RF circuit 108, an audio circuit 110, a speaker 111, a microphone 113, an input / output (I / O) subsystem 106, other input control devices 116, and an external port 124. The device 100 optionally includes one or more optical sensors 164. The device 100 optionally includes one or more contact force sensors 165 for detecting the intensity of contact on the device 100 (e.g., a touch-sensitive surface, such as the touch-sensitive display system 112 of the device 100). Device 100 optionally includes one or more tactile output generators 167 for generating tactile output on device 100 (e.g., generating tactile output on a touch-sensitive surface such as touch-sensitive display system 112 of device 100 or touch pad 355 of device 300). These components optionally communicate via one or more communication buses or signal lines 103.
[0091] As used in this specification and claims, the term "intensity" of a contact on a touch-sensitive surface refers to the force or pressure (force per unit area) of a contact (e.g., a finger contact) on the touch-sensitive surface, or to a surrogate (surrogate) of the force or pressure of a contact on the touch-sensitive surface. The intensity of a contact has a range of values that includes at least four different values and more typically includes hundreds of different values (e.g., at least 256). The intensity of a contact is optionally determined (or measured) using various methods and various sensors or combinations of sensors. For example, one or more force sensors below or adjacent to the touch-sensitive surface are optionally used to measure the force at different points on the touch-sensitive surface. In some implementations, force measurements from multiple force sensors are combined (e.g., a weighted average) to determine an estimated contact force. Similarly, the pressure-sensitive tip of a stylus is optionally used to determine the pressure of the stylus on the touch-sensitive surface. Alternatively, the size of the contact area detected on the touch-sensitive surface and / or its change, the capacitance of the touch-sensitive surface adjacent to the contact and / or its change, and / or the resistance of the touch-sensitive surface adjacent to the contact and / or its change are optionally used as a substitute for the force or pressure of the contact on the touch-sensitive surface. In some embodiments, the substitute measurement of the contact force or pressure is used directly to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is described in units corresponding to the substitute measurement). In some embodiments, the substitute measurement of the contact force or pressure is converted into an estimated force or pressure, and the estimated force or pressure is used to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is a pressure threshold measured in units of pressure). Using the intensity of the contact as an attribute of the user input allows the user to access additional device functionality that would otherwise be inaccessible to the user on a smaller device with limited real estate, which is used to display an enable indication (e.g., on a touch-sensitive display) and / or receive user input (e.g., via a touch-sensitive display, touch-sensitive surface, or physical / mechanical controls such as knobs or buttons).
[0092] As used in this specification and claims, the term "tactile output" refers to a physical displacement of a device relative to a previous position of the device, a physical displacement of a component of the device (e.g., a touch-sensitive surface) relative to another component of the device (e.g., a housing), or a displacement of a component relative to the center of mass of the device, which will be detected by a user using the user's sense of touch. For example, in the case where a device or a component of the device is in contact with a user's touch-sensitive surface (e.g., a finger, palm, or other part of the user's hand), the tactile output generated by the physical displacement will be interpreted by the user as a tactile sensation corresponding to a perceived change in a physical characteristic of the device or component of the device. For example, movement of a touch-sensitive surface (e.g., a touch-sensitive display or trackpad) is optionally interpreted by the user as a "press click" or "release click" to a physical actuation button. In some cases, the user will feel a tactile sensation, such as a "press click" or "release click", even when the physical actuation button associated with the touch-sensitive surface that is physically pressed (e.g., displaced) by the user's movement does not move. As another example, movement of a touch-sensitive surface may optionally be interpreted or sensed by a user as "roughness" of the touch-sensitive surface even when there is no change in the smoothness of the touch-sensitive surface. While such interpretation of touch by a user will be limited by the user's individualized sensory perceptions, there are many sensory perceptions of touch that are common to most users. Thus, when a tactile output is described as corresponding to a particular sensory perception of a user (e.g., "press click," "release click," "roughness"), unless otherwise stated, the tactile output generated corresponds to a physical displacement of the device or a component thereof that would generate a sensory perception of a typical (or average) user.
[0093] It should be understood that device 100 is only one example of a portable multifunction device, and that device 100 optionally has more or fewer components than shown, optionally combines two or more components, or optionally has a different configuration or arrangement of the components. Figure 1A The various components shown in the EMBODIMENTS 2000 are implemented in hardware, software, or a combination of hardware and software, including one or more signal processing circuits and / or application specific integrated circuits.
[0094] Memory 102 optionally includes high-speed random access memory and also includes non-volatile memory, such as one or more disk storage devices, flash memory devices, or other non-volatile solid-state memory devices. Memory controller 122 can control other components of device 100 to access memory 102.
[0095] The peripheral device interface 118 can be used to couple the input peripheral devices and output peripheral devices of the device to the CPU 120 and the memory 102. The one or more processors 120 run or execute various software programs and / or instruction sets stored in the memory 102 to perform various functions of the device 100 and process data. In some embodiments, the peripheral device interface 118, the CPU 120, and the memory controller 122 can be implemented on a single chip such as the chip 104. In some other embodiments, they can be implemented on separate chips.
[0096] RF (radio frequency) circuit 108 receives and transmits RF signals, also called electromagnetic signals. RF circuit 108 converts electrical signals into / converts electromagnetic signals into electrical signals, and communicates with a communication network and other communication devices via electromagnetic signals. RF circuit 108 optionally includes well-known circuits for performing these functions, including 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 user identity module (SIM) card, a memory, and the like. RF circuit 108 optionally communicates with a network and other devices via wireless communication, such as the Internet (also known as 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)). RF circuit 108 optionally includes well-known circuits for detecting a near field communication (NFC) field, such as by a short-range communication radio component. Wireless communication optionally uses any of a variety of communication standards, protocols and techniques, including, but not limited to, Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), High Speed Downlink Packet Access (HSDPA), High Speed Uplink Packet Access (HSUPA), Evolution, Data-Only (EV-DO), HSPA, HSPA+, Dual Cell HSPA (DC-HSPDA), Long Term Evolution (LTE), Near Field Communication (NFC), Wideband Code Division Multiple Access (W-CDMA), Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Bluetooth, Bluetooth Low Energy, Wireless Fidelity (Wi-Fi) (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, email protocols (e.g., Internet Message Access Protocol (IMAP) and / or Post Office Protocol (POP)), instant messaging (e.g., Extensible Messaging and Presence Protocol (XMPP), Session Initiation Protocol for Instant Messaging and Presence Utilizing Extensions (SIMPLE), Instant Messaging and Presence Service (IMPS)), and / or Short Message Service (SMS), or any other suitable communications protocol including communications protocols that have not been developed as of the filing date of this document.
[0097] The audio circuit 110, the speaker 111, and the microphone 113 provide an audio interface between the user and the device 100. The audio circuit 110 receives audio data from the peripheral device interface 118, converts the audio data into electrical signals, and transmits the electrical signals to the speaker 111. The speaker 111 converts the electrical signals into sound waves audible to humans. The audio circuit 110 also receives electrical signals converted from sound waves by the microphone 113. The audio circuit 110 converts the electrical signals into audio data and transmits the audio data to the peripheral device interface 118 for processing. The audio data can be retrieved from the memory 102 and / or the RF circuit 108 by the peripheral device interface 118 and / or transmitted to the memory 102 and / or the RF circuit 108. In some embodiments, the audio circuit 110 also includes a headset interface (e.g., Figure 2 The headset interface provides an interface between the audio circuit 110 and a removable audio input / output peripheral device, such as an output-only headset or a headset with both output (e.g., a single-ear headset or a dual-ear headset) and input (e.g., a microphone).
[0098] The I / O subsystem 106 couples input / output peripherals on the device 100, such as a touch screen 112 and other input control devices 116, to a peripheral device interface 118. The I / O subsystem 106 optionally includes a display controller 156, an optical sensor controller 158, an intensity sensor controller 159, a tactile feedback controller 161, and one or more input controllers 160 for other input or control devices. The one or more input controllers 160 receive / send electrical signals from other input control devices 116. Other input control devices 116 optionally include physical buttons (e.g., push buttons, rocker buttons, etc.), dials, slide switches, joysticks, click wheels, and the like. In some alternative embodiments, one or more input controllers 160 are optionally coupled to any (or none) of the following: a keyboard, an infrared port, a USB port, and a pointer device such as a mouse. One or more buttons (e.g., Figure 2 208) optionally includes an up / down button for volume control of the speaker 111 and / or the microphone 113. The one or more buttons optionally include a push button (e.g., Figure 2 206).
[0099] A quick press of the push button may unlock the touch screen 112 or begin the process of unlocking the device using gestures on the touch screen, as described in U.S. Patent Application 11 / 322,549, filed on December 23, 2005, entitled "Unlocking a Device by Performing Gestures on an Unlock Image," and U.S. Patent Application No. 7,657,849. The above-mentioned U.S. Patent Applications are hereby incorporated by reference in their entirety. A longer press of the push button (e.g., 206) may turn the device 100 on or off. The user may customize the function of one or more buttons. The touch screen 112 is used to implement virtual buttons or soft buttons and one or more soft keyboards.
[0100] The touch-sensitive display 112 provides an input interface and an output interface between the device and the user. The display controller 156 receives electrical signals from the touch screen 112 and / or sends electrical signals to the touch screen 112. The touch screen 112 displays visual output to the user. The visual output may include graphics, text, icons, videos, and any combination thereof (collectively referred to as "graphics"). In some embodiments, some or all of the visual output may correspond to user interface objects.
[0101] The touch screen 112 has a touch-sensitive surface, sensor, or set of sensors that accepts input from a user based on tactile and / or haptic contact. The touch screen 112 and display controller 156 (together with any associated modules and / or instruction sets in memory 102) detect contact (and any movement or interruption of the contact) on the touch screen 112 and convert the detected contact into interaction with a user interface object (e.g., one or more soft keys, icons, web pages, or images) displayed on the touch screen 112. In an exemplary embodiment, the point of contact between the touch screen 112 and the user corresponds to a finger of the user.
[0102] The touch screen 112 may use LCD (liquid crystal display) technology, LPD (light emitting polymer display) technology, or LED (light emitting diode) technology, although other display technologies may be used in other embodiments. The touch screen 112 and display controller 156 may use any of a variety of touch sensing technologies now known or later developed, including but not limited to capacitive technology, resistive technology, infrared technology, and surface acoustic wave technology, as well as other proximity sensor arrays or other elements for determining one or more points of contact with the touch screen 112 to detect contact and any movement or interruption thereof. In an exemplary embodiment, projected mutual capacitance sensing technology is used, such as the Surface Mount 200 from Apple Inc. (Cupertino, California). and technology found on the iPod Touch.
[0103] The touch-sensitive display in some embodiments of the touch screen 112 can be similar to the multi-touch-sensitive touch pad described in the following U.S. Patents: 6,323,846 (Westerman et al.), 6,570,557 (Westerman et al.), and / or 6,677,932 (Westerman); and / or U.S. Patent Publication 2002 / 0015024A1, each of which is hereby incorporated by reference in its entirety. However, the touch screen 112 displays visual output from the device 100, while the touch-sensitive touch pad does not provide visual output.
[0104] The touch-sensitive display in some embodiments of the touch screen 112 may be described as in the following patent applications: (1) U.S. patent application No. 11 / 381,313, entitled “Multipoint Touch Surface Controller,” filed on May 2, 2006; (2) U.S. patent application No. 10 / 840,862, entitled “Multipoint Touchscreen,” filed on May 6, 2004; (3) U.S. patent application No. 10 / 903,964, entitled “Gestures For Touch Sensitive Input Devices,” filed on July 30, 2004; (4) U.S. patent application No. 11 / 048,264, entitled “Gestures For Touch Sensitive Input Devices,” filed on January 31, 2005; (5) U.S. patent application No. 11 / 086,964, entitled “Mode-Based Graphical User Interfaces For Touch Sensitive Input Devices,” filed on January 18, 2005 and (9) U.S. patent application No. 11 / 367,749, filed on March 3, 2006, entitled “Multi-Functional Hand-Held Device.” All of these patent applications are hereby incorporated by reference in their entirety.
[0105] The touch screen 112 may have a video resolution of more than 100 dpi. In some embodiments, the touch screen has a video resolution of about 160 dpi. The user may use any suitable object or appendage such as a stylus, finger, etc. to contact the touch screen 112. In some embodiments, the user interface is designed to work primarily with finger-based contacts and gestures, which may not be as precise as stylus-based input due to the larger contact area of a finger on the touch screen. In some embodiments, the device translates rough finger-based input into precise pointer / cursor positions or commands for performing the actions desired by the user.
[0106] In some embodiments, in addition to the touch screen, the device 100 may include a touch pad (not shown) for activating or deactivating specific functions. In some embodiments, the touch pad is a touch-sensitive area of the device that, unlike the touch screen, does not display visual output. The touch pad can be a touch-sensitive surface separate from the touch screen 112, or an extension of the touch-sensitive surface formed by the touch screen.
[0107] The device 100 also includes a power system 162 for powering the various components. The power system 162 may include a power management system, one or more power sources (e.g., batteries, alternating current (AC)), a recharging system, a power fault detection circuit, a power converter or inverter, a power status indicator (e.g., a light emitting diode (LED)), and any other components associated with the generation, management, and distribution of power in a portable device.
[0108] Device 100 may also include one or more optical sensors 164 . Figure 1A An optical sensor coupled to an optical sensor controller 158 in the I / O subsystem 106 is shown. The optical sensor 164 may include a charge coupled device (CCD) or a complementary metal oxide semiconductor (CMOS) phototransistor. The optical sensor 164 receives light projected through one or more lenses from the environment and converts the light into data representing an image. In conjunction with the imaging module 143 (also referred to as a camera module), the optical sensor 164 can capture static images or videos. In some embodiments, the optical sensor is located on the rear of the device 100 opposite to the touch screen display 112 on the front of the device, so that the touch screen display can be used as a viewfinder for static images and / or video image acquisition. In some embodiments, the optical sensor is located at the front of the device so that the image of the user can be obtained while the user is watching other video conference participants on the touch screen display for video conferencing. In some embodiments, the position of the optical sensor 164 can be changed by the user (e.g., by rotating the lens and sensor in the device housing) so that a single optical sensor 164 can be used with the touch screen display for both video conferencing and static image and / or video image acquisition.
[0109] Device 100 optionally also includes one or more contact intensity sensors 165 . Figure 1A A contact force sensor is shown coupled to a force sensor controller 159 in the I / O subsystem 106. Contact force sensor 165 optionally includes one or more piezoresistive strain gauges, capacitive force sensors, electrical force sensors, piezoelectric force sensors, optical force sensors, capacitive touch-sensitive surfaces, or other force sensors (e.g., sensors for measuring the force (or pressure) of contact on a touch-sensitive surface). Contact force sensor 165 receives contact force information (e.g., pressure information or a surrogate for pressure information) from the environment. In some embodiments, at least one contact force sensor is juxtaposed or adjacent to a touch-sensitive surface (e.g., touch-sensitive display system 112). In some embodiments, at least one contact force sensor is located on the rear of device 100 opposite to touch screen display 112 located on the front of device 100.
[0110] Device 100 may also include one or more proximity sensors 166 . Figure 1A A proximity sensor 166 is shown coupled to the peripherals interface 118. Alternatively, the proximity sensor 166 can be coupled to the input controller 160 in the I / O subsystem 106. The proximity sensor 166 can be implemented as described in the following U.S. patent applications: 11 / 241,839, entitled "Proximity Detector In Handheld Device"; 11 / 240,788, entitled "Proximity Detector In Handheld Device"; 11 / 620,702, entitled "Using Ambient Light Sensor To Augment Proximity Sensor Output"; 11 / 586,862, entitled "Automated Response To And Sensing Of User Activity In Portable Devices"; and 11 / 638,251, entitled "Methods And Systems For Automatic Configuration Of Peripherals", which are hereby incorporated by reference in their entirety. In some embodiments, when the multifunction device is placed near the user's ear (e.g., when the user is on a phone call), the proximity sensor turns off and disables the touch screen 112.
[0111] Device 100 optionally also includes one or more tactile output generators 167 . Figure 1AA tactile output generator is shown coupled to a tactile feedback controller 161 in the I / O subsystem 106. The tactile output generator 167 optionally includes one or more electroacoustic devices such as a speaker or other audio component; and / or an electromechanical device for converting energy into linear motion such as a motor, solenoid, electroactive polymer, piezoelectric actuator, electrostatic actuator, or other tactile output generating component (e.g., a component for converting an electrical signal into a tactile output on the device). The contact force sensor 165 receives tactile feedback generation instructions from the tactile feedback module 133 and generates a tactile output on the device 100 that can be felt by a user of the device 100. In some embodiments, at least one tactile output generator is arranged in parallel or adjacent to a touch-sensitive surface (e.g., a touch-sensitive display system 112) and optionally generates tactile output by moving the touch-sensitive surface vertically (e.g., inward / outward of the surface of the device 100) or laterally (e.g., backward and forward in the same plane as the surface of the device 100). In some embodiments, at least one tactile output generator sensor is located on a rear portion of the device 100 opposite the touch screen display 112 located on the front of the device 100.
[0112] Device 100 may also include one or more accelerometers 168 . Figure 1A An accelerometer 168 is shown coupled to the peripheral device interface 118. Alternatively, the accelerometer 168 may be coupled to the input controller 160 in the I / O subsystem 106. The accelerometer 168 may be implemented as described in the following U.S. Patent Publications: 20050190059, entitled "Acceleration-based Theft Detection System for Portable Electronic Devices" and 20060017692, entitled "Methods And Apparatuses For Operating A Portable Device Based On An Accelerometer", both of which are incorporated herein by reference in their entirety. In some embodiments, information is displayed in a portrait view or a landscape view on the touch screen display based on analysis of data received from the one or more accelerometers. The device 100 optionally includes a magnetometer (not shown) and a GPS (or GLONASS or other global navigation system) receiver (not shown) in addition to the one or more accelerometers 168 for obtaining information about the position and orientation (e.g., portrait or landscape) of the device 100.
[0113] In some embodiments, the software components stored in memory 102 include an operating system 126, a communication module (or instruction set) 128, a contact / motion module (or instruction set) 130, a graphics module (or instruction set) 132, a text input module (or instruction set) 134, a global positioning system (GPS) module (or instruction set) 135, and an application (or instruction set) 136. In addition, in some embodiments, memory 102 ( Figure 1A ) or 370( Figure 3 ) storage device / global internal state 157, such as Figure 1A and Figure 3 . The device / global internal state 157 includes one or more of the following: an active application state indicating which applications, if any, are currently active; a display state indicating what applications, views, or other information occupy various areas of the touch screen display 112; a sensor state including information obtained from the device's various sensors and input control devices 116; and position information regarding the device's position and / or posture.
[0114] The operating system 126 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, iOS, WINDOWS, or an embedded operating system such as VxWorks) includes various software components and / or drivers for controlling and managing general system tasks (e.g., memory management, storage device control, power management, etc.), and facilitating communication between various hardware components and software components.
[0115] The communication module 128 facilitates communication with other devices through one or more external ports 124 and also includes various software components for processing data received by the RF circuit 108 and / or the external port 124. The external port 124 (e.g., Universal Serial Bus (USB), FireWire, etc.) is suitable for coupling directly to other devices or indirectly through a network (e.g., the Internet, wireless LAN, etc.). In some embodiments, the external port is connected to (trademark of Apple Inc.) devices.
[0116] The contact / motion module 130 optionally detects contact with the touch screen 112 (in conjunction with the display controller 156) and other touch-sensitive devices (e.g., a touchpad or physical click wheel). The contact / motion module 130 includes various software components for performing various operations related to contact detection, such as determining whether contact has occurred (e.g., detecting a finger press event), determining the strength of the contact (e.g., the force or pressure of the contact, or a substitute for the force or pressure of the contact), determining whether there is movement of the contact and tracking the movement on the touch-sensitive surface (e.g., detecting one or more finger drag events), and determining whether the contact has stopped (e.g., detecting a finger lift event or contact disconnection). The contact / motion module 130 receives contact data from the touch-sensitive surface. Determining the movement of a contact point optionally includes determining a rate (magnitude), a velocity (magnitude and direction), and / or an acceleration (change in magnitude and / or direction) of the contact point, the movement of which is represented by a series of contact data. These operations are optionally applied to a single point of contact (e.g., a single finger contact) or multiple points of simultaneous contact (e.g., "multi-touch" / multi-finger contact). In some embodiments, the contact / motion module 130 and display controller 156 detect contact on the touch pad.
[0117] In some embodiments, the contact / motion module 130 uses a set of one or more intensity thresholds to determine whether an operation has been performed by a user (e.g., to determine whether a user has "clicked" an icon). In some embodiments, at least a subset of the intensity thresholds are determined based on software parameters (e.g., the intensity thresholds are not determined by the activation thresholds of specific physical actuators and can be adjusted without changing the physical hardware of the device 100). For example, without changing the touchpad or touchscreen display hardware, the mouse "click" threshold of a touchpad or touchscreen can be set to any one of a large range of predefined thresholds. In addition, in some specific implementations, a software setting is provided to the user of the device for adjusting one or more intensity thresholds in a set of intensity thresholds (e.g., by adjusting individual intensity thresholds and / or by utilizing a system-level click on an "intensity" parameter to adjust multiple intensity thresholds at once).
[0118] The contact / motion module 130 optionally detects gesture input by the user. Different gestures on the touch-sensitive surface have different contact patterns (e.g., different motions, timings, and / or intensities of the detected contacts). Therefore, gestures are optionally detected by detecting specific contact patterns. For example, detecting a finger tap gesture includes detecting a finger press event, and then detecting a finger lift (lift-off) event at the same location (or substantially the same location) as the finger press event (e.g., at the location of an icon). As another example, detecting a finger swipe gesture on the touch-sensitive surface includes detecting a finger press event, then detecting one or more finger drag events, and then detecting a finger lift (lift-off) event.
[0119] The graphics module 132 includes various known software components for rendering and displaying graphics on the touch screen 112 or other display, including components for changing the visual impact (e.g., brightness, transparency, saturation, contrast, or other visual characteristics) of the displayed graphics. As used herein, the term "graphics" includes any object that can be displayed to a user, including, without limitation, text, web pages, icons (such as user interface objects including soft keys), digital images, videos, animations, etc.
[0120] In some embodiments, the graphics module 132 stores data to be used to represent graphics. Each graphic is optionally assigned a corresponding code. The graphics module 132 receives one or more codes for specifying the graphics to be displayed from an application program, etc., and also receives coordinate data and other graphic attribute data together if necessary, and then generates screen image data to be output to the display controller 156.
[0121] Haptic feedback module 133 includes various software components for generating instructions used by one or more tactile output generators 167 to generate tactile output at one or more locations on device 100 in response to user interaction with device 100 .
[0122] The text input module 134, which may be a component of the graphics module 132, provides a soft keyboard for entering text in a variety of applications (eg, contacts 137, email 140, IM 141, browser 147, and any other application requiring text input).
[0123] The GPS module 135 determines the location of the device and provides such information for use in various applications (e.g., to the phone 138 for location-based dialing; to the camera 143 as picture / video metadata; and to applications that provide location-based services such as weather widgets, local yellow pages widgets, and maps / navigation widgets).
[0124] The application 136 may include the following modules (or instruction sets) or a subset or superset thereof:
[0125] Contacts module 137 (sometimes called an address book or contact list);
[0126] Telephone module 138;
[0127] Video conferencing module 139;
[0128] Email client module 140;
[0129] Instant messaging (IM) module 141;
[0130] Fitness support module 142;
[0131] A camera module 143 for still images and / or video images;
[0132] Image management module 144;
[0133] Video player module;
[0134] Music player module;
[0135] Browser module 147;
[0136] Calendar module 148;
[0137] A widget module 149, which may include one or more of the following: a weather widget 149-1, a stock widget 149-2, a calculator widget 149-3, an alarm widget 149-4, a dictionary widget 149-5, and other widgets acquired by the user and a widget 149-6 created by the user;
[0138] A widget creator module 150 for forming a user-created widget 149-6;
[0139] Search module 151;
[0140] Video and music player module 152, which merges the video player module and the music player module;
[0141] Notepad module 153;
[0142] Map module 154; and / or
[0143] Online video module 155.
[0144] Examples of other applications 136 that may be stored in memory 102 include other word processing applications, other image editing applications, drawing applications, rendering applications, JAVA-enabled applications, encryption, digital rights management, voice recognition, and voice replication.
[0145] In conjunction with the touch screen 112, display controller 156, touch / motion module 130, graphics module 132, and text input module 134, the contact module 137 can be used to manage an address book or contact list (e.g., stored in the application internal state 192 of the contact module 137 in memory 102 or memory 370), including: adding one or more names to the address book; deleting one or more names from the address book; associating one or more telephone numbers, one or more email addresses, one or more physical addresses, or other information with a name; associating an image with a name; categorizing and classifying names; providing a telephone number or email address to initiate and / or facilitate communications via telephone 138, video conferencing module 139, email 140, or IM 141; and the like.
[0146] In conjunction with RF circuit 108, audio circuit 110, speaker 111, microphone 113, touch screen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134, phone module 138 may be used to input a character sequence corresponding to a phone number, access one or more phone numbers in contact module 137, modify an inputted phone number, dial a corresponding phone number, conduct a conversation, and disconnect or hang up when the conversation is complete. As described above, wireless communication may use any of a number of communication standards, protocols, and technologies.
[0147] In combination with the RF circuit 108, the audio circuit 110, the speaker 111, the microphone 113, the touch screen 112, the display controller 156, the optical sensor 164, the optical sensor controller 158, the contact / motion module 130, the graphics module 132, the text input module 134, the contact module 137 and the telephone module 138, the video conferencing module 139 includes executable instructions for initiating, conducting and terminating a video conference between a user and one or more other participants in accordance with user instructions.
[0148] In conjunction with RF circuit 108, touch screen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134, email client module 140 includes executable instructions for creating, sending, receiving, and managing emails in response to user instructions. In conjunction with image management module 144, email client module 140 makes it very easy to create and send emails with still images or video images captured by camera module 143.
[0149] In conjunction with the RF circuit 108, the touch screen 112, the display controller 156, the contact / motion module 130, the graphics module 132, and the text input module 134, the instant messaging module 141 includes executable instructions for the following operations: inputting a character sequence corresponding to an instant message, modifying previously input characters, transmitting a corresponding instant message (e.g., using a short message service (SMS) or multimedia message service (MMS) protocol for phone-based instant messaging or using XMPP, SIMPLE, or IMPS for Internet-based instant messaging), receiving instant messages, and viewing received instant messages. In some embodiments, the transmitted and / or received instant messages may include graphics, photos, audio files, video files, and / or other attachments supported in MMS and / or enhanced messaging services (EMS). As used herein, "instant messaging" refers to both phone-based messages (e.g., messages transmitted using SMS or MMS) and Internet-based messages (e.g., messages transmitted using XMPP, SIMPLE, or IMPS).
[0150] In combination with the RF circuit 108, the touch screen 112, the display controller 156, the contact / motion module 130, the graphics module 132, the text input module 134, the GPS module 135, the map module 154, and the music player module, the fitness support module 142 includes executable instructions for: creating a fitness (e.g., with time, distance, and / or calorie burn goals); communicating with a fitness sensor (mobile device); receiving fitness sensor data; calibrating sensors for monitoring fitness; selecting fitness music and playing it; and displaying, storing, and transmitting fitness data.
[0151] In conjunction with the touch screen 112, display controller 156, one or more optical sensors 164, optical sensor controller 158, touch / motion module 130, graphics module 132, and image management module 144, the camera module 143 includes executable instructions for capturing still images or videos (including video streams) and storing them in memory 102, modifying characteristics of still images or videos, or deleting still images or videos from memory 102.
[0152] In conjunction with touch screen 112, display controller 156, touch / motion module 130, graphics module 132, text input module 134, and camera module 143, image management module 144 includes executable instructions for arranging, modifying (e.g., editing), or otherwise manipulating, labeling, deleting, presenting (e.g., in a digital slideshow or album), and storing still images and / or video images.
[0153] In combination with the RF circuit 108, the touch screen 112, the display controller 156, the touch / motion module 130, the graphics module 132 and the text input module 134, the browser module 147 includes executable instructions for browsing the Internet in accordance with user instructions (including searching, linking to, receiving, and displaying web pages or portions thereof, as well as attachments and other files linked to web pages).
[0154] In combination with the RF circuit system 108, the touch screen 112, the display controller 156, the touch / motion module 130, the graphics module 132, the text input module 134, the email client module 140 and the browser module 147, the calendar module 148 includes executable instructions for creating, displaying, modifying and storing calendars and data associated with the calendar (e.g., calendar entries, to-do items, etc.) in accordance with user instructions.
[0155] In conjunction with the RF circuit system 108, the touch screen 112, the display controller 156, the contact / motion module 130, the graphics module 132, the text input module 134, and the browser module 147, the desktop widget module 149 is a mini-application that can be downloaded and used by the user (e.g., the weather desktop widget 149-1, the stock desktop widget 149-2, the calculator desktop widget 149-3, the alarm desktop widget 149-4, and the dictionary desktop widget 149-5) or a mini-application created by the user (e.g., the user-created desktop widget 149-6). In some embodiments, the desktop widget includes an HTML (Hypertext Markup Language) file, a CSS (Cascading Style Sheets) file, and a JavaScript file. In some embodiments, the desktop widget includes an XML (Extensible Markup Language) file and a JavaScript file (e.g., the Yahoo! desktop widget).
[0156] In combination with the RF circuit 108, the touch screen 112, the display controller 156, the touch / motion module 130, the graphics module 132, the text input module 134, and the browser module 147, the desktop widget creator module 150 can be used by users to create desktop widgets (for example, to transfer a user-specified portion of a web page to a desktop widget).
[0157] In combination with the touch screen 112, display controller 156, contact / motion module 130, graphics module 132 and text input module 134, the search module 151 includes executable instructions for searching the memory 102 for text, music, sound, images, videos and / or other files that match one or more search conditions (e.g., one or more user-specified search terms) in accordance with user instructions.
[0158] In conjunction with touch screen 112, display controller 156, contact / motion module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, and browser module 147, video and music player module 152 includes executable instructions that allow a user to download and play back recorded music and other sound files stored in one or more file formats (such as MP3 or AAC files), as well as executable instructions for displaying, presenting, or otherwise playing back video (e.g., on touch screen 112 or on an external display connected via external port 124). In some embodiments, device 100 optionally includes the functionality of an MP3 player, such as an iPod (trademark of Apple Inc.).
[0159] In conjunction with the touch screen 112, display controller 156, contact / motion module 130, graphics module 132 and text input module 134, the notepad module 153 includes executable instructions for creating and managing notes, to-do lists, etc. according to user instructions.
[0160] In combination with RF circuitry 108, touch screen 112, display controller 156, touch / motion module 130, graphics module 132, text input module 134, GPS module 135, and browser module 147, map module 154 may be used to receive, display, modify, and store maps and data associated with the maps (e.g., driving directions, data relating to stores and other points of interest at or near a particular location, and other location-based data) in accordance with user instructions.
[0161] In conjunction with touch screen 112, display controller 156, contact / motion module 130, graphics module 132, audio circuit 110, speaker 111, RF circuit 108, text input module 134, email client module 140, and browser module 147, online video module 155 includes instructions that allow a user to access, browse, receive (e.g., by streaming and / or downloading), play back (e.g., on the touch screen or on an external display connected via external port 124), send an email with a link to a specific online video, and otherwise manage online videos in one or more file formats such as H.264. In some embodiments, instant messaging module 141 is used instead of email client module 140 to send a link to a specific online video. Additional description of the online video application can be found in U.S. Provisional Patent Application No. 60 / 936,562, filed on June 20, 2007, entitled “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos,” and U.S. Patent Application No. 11 / 968,067, filed on December 31, 2007, entitled “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos,” the contents of which are hereby incorporated by reference in their entirety.
[0162] Each of the modules and applications described above corresponds to an executable instruction set for performing one or more of the functions described above and the methods described in this patent application (e.g., the computer-implemented methods and other information processing methods described herein). These modules (e.g., instruction sets) do not have to be implemented as separate software programs, processes, or modules, and therefore various subsets of these modules may be combined or otherwise rearranged in various embodiments. For example, a video player module may be combined with a music player module into a single module (e.g., Figure 1A In some embodiments, the memory 102 may store a subset of the above modules and data structures. In addition, the memory 102 may store additional modules and data structures not described above.
[0163] In some embodiments, the device 100 is a device that performs operations of a predefined set of functions on the device solely through a touch screen and / or a touch pad. By using a touch screen and / or a touch pad as the primary input control device for the operation of the device 100, the number of physical input control devices (such as push buttons, dials, etc.) on the device 100 can be reduced.
[0164] The predefined set of functions performed exclusively through the touch screen and / or touchpad optionally includes navigating between user interfaces. In some embodiments, the touchpad, when touched by the user, navigates the device 100 from any user interface displayed on the device 100 to a main menu, a home menu, or a root menu. In such embodiments, a touchpad is used to implement a "menu button." In some other embodiments, the menu button is a physical push button or other physical input control device, rather than a touchpad.
[0165] Figure 1B 1 is a block diagram illustrating exemplary components for event processing according to some embodiments. In some embodiments, memory 102 ( Figure 1A ) or memory 370( Figure 3 ) includes an event classifier 170 (e.g., in the operating system 126) and a corresponding application 136-1 (e.g., any one of the aforementioned applications 137-151, 155, 380-390).
[0166] Event classifier 170 receives event information and determines the application 136-1 and the application view 191 of application 136-1 to which the event information is to be delivered. Event classifier 170 includes event monitor 171 and event distributor module 174. In some embodiments, application 136-1 includes application internal state 192, which indicates one or more current application views displayed on touch-sensitive display 112 when the application is active or executing. In some embodiments, device / global internal state 157 is used by event classifier 170 to determine which application(s) is currently active, and application internal state 192 is used by event classifier 170 to determine the application view 191 to which the event information is to be delivered.
[0167] In some embodiments, the application internal state 192 includes additional information, such as one or more of the following: resumption information to be used when the application 136-1 resumes execution, user interface state information indicating information being displayed by the application 136-1 or information ready to be displayed by the application 136-1, a state queue for enabling a user to return to a previous state or view of the application 136-1, and a repeat / undo queue of previous actions taken by the user.
[0168] Event monitor 171 receives event information from peripherals interface 118. Event information includes information about sub-events (e.g., a user touch on touch-sensitive display 112 as part of a multi-touch gesture). Peripherals interface 118 transmits information it receives from I / O subsystem 106 or sensors (such as proximity sensor 166), one or more accelerometers 168, and / or microphone 113 (through audio circuit 110). The information that peripherals interface 118 receives from I / O subsystem 106 includes information from touch-sensitive display 112 or a touch-sensitive surface.
[0169] In some embodiments, event monitor 171 sends requests to peripheral device interface 118 at predetermined intervals. In response, peripheral device interface 118 transmits event information. In other embodiments, peripheral device interface 118 transmits event information only when there is a significant event (e.g., receiving an input above a predetermined noise threshold and / or receiving an input for more than a predetermined duration).
[0170] In some embodiments, the event classifier 170 also includes a hit view determination module 172 and / or an active event identifier determination module 173.
[0171] When the touch-sensitive display 112 displays more than one view, the hit view determination module 172 provides software procedures for determining where within one or more views a sub-event has occurred. A view consists of controls and other elements that a user can see on the display.
[0172] 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 (of the respective application) in which a touch is detected may correspond to a programmatic hierarchy of the application or a programmatic level within the view hierarchy. For example, the lowest level view in which a touch is detected is optionally called a hit view, and the set of events recognized as correct input is determined at least in part based on the hit view of the initial touch that started the touch-based gesture.
[0173] Hit view determination module 172 receives information related to sub-events of touch-based gestures. When an application has multiple views organized in a hierarchy, hit view determination module 172 identifies the hit view as the lowest view in the hierarchy where the sub-events should be processed. In most cases, the hit view is the lowest level view in which the initiating sub-event (e.g., the first sub-event in a sequence of sub-events that form an event or potential event) occurs. Once a hit view is identified by hit view determination module 172, the hit view typically receives all sub-events related to the same touch or input source for which it was identified as the hit view.
[0174] Active event recognizer determination module 173 determines which view or views within the view hierarchy should receive a particular sequence of sub-events. In some embodiments, active event recognizer determination module 173 determines that only the hit view should receive a particular sequence of sub-events. In other embodiments, active event recognizer determination module 173 determines that all views that include the physical location of the sub-event are actively participating views, and therefore determines that all actively participating views should receive a particular sequence of sub-events. In other embodiments, even if a touch sub-event is completely confined to an area associated with one particular view, views higher in the hierarchy will still remain actively participating views.
[0175] Event distributor module 174 distributes event information to event recognizers (e.g., event recognizers 180). In embodiments including active event recognizer determination module 173, event distributor module 174 delivers the event information to the event recognizers determined by active event recognizer determination module 173. In some embodiments, event distributor module 174 stores the event information in an event queue, which is retrieved by corresponding event receivers 182.
[0176] In some embodiments, operating system 126 includes event classifier 170. Alternatively, application 136-1 includes event classifier 170. In another embodiment, event classifier 170 is a standalone module or a part of another module (such as contact / motion module 130) stored in memory 102.
[0177] In some embodiments, application 136-1 includes multiple event handlers 190 and one or more application views 191, each of which includes instructions for handling touch events occurring within a corresponding view of the user interface of the application. Each application view 191 of application 136-1 includes one or more event recognizers 180. Typically, the corresponding application view 191 includes multiple event recognizers 180. In other embodiments, one or more application views in event recognizer 180 are part of an independent module, such as a user interface toolkit (not shown) or a higher level object from which application 136-1 inherits methods and other properties. In some embodiments, the corresponding event handler 190 includes one or more of the following: data updater 176, object updater 177, GUI updater 178, and / or event data 179 received from event classifier 170. Event handler 190 can utilize or call data updater 176, object updater 177, or GUI updater 178 to update application internal state 192. Alternatively, one or more of the application views in application view 191 include one or more corresponding event handlers 190. Additionally, in some embodiments, one or more of data updater 176, object updater 177, and GUI updater 178 are included in the corresponding application view 191.
[0178] The corresponding event identifier 180 receives event information (e.g., event data 179) from the event classifier 170 and identifies the event from the event information. The event identifier 180 includes an event receiver 182 and an event comparator 184. In some embodiments, the event identifier 180 also includes at least a subset of the following: metadata 183, and event delivery instructions 188 (which may include sub-event delivery instructions).
[0179] Event receiver 182 receives event information from event classifier 170. Event information includes information about sub-events, such as touches or touch movements. Depending on the sub-event, the event information also includes additional information, such as the location of the sub-event. When the sub-event involves the movement of a touch, the event information may also include the rate and direction of the sub-event. In some embodiments, the event includes the device rotating from one orientation to another (e.g., from a portrait orientation to a landscape orientation, or vice versa), and the event information includes corresponding information about the current orientation of the device (also referred to as the device posture).
[0180] Event comparator 184 compares event information with predefined event or sub-event definitions, and determines an event or sub-event based on the comparison, or determines or updates the state of an event or sub-event. In some embodiments, event comparator 184 includes event definition 186. Event definition 186 includes the definition of an event (e.g., a predefined sequence of sub-events), such as event 1 (187-1), event 2 (187-2), and other events. In some embodiments, sub-events in event 187 include, for example, touch start, touch end, touch move, touch cancel, and multi-touch. In one example, the definition of event 1 (187-1) is a double-click on a displayed object. For example, a double-click includes a first touch (touch start) of a predetermined duration on a displayed object, a first lift (touch end) of a predetermined duration, a second touch (touch start) of a predetermined duration on a displayed object, and a second lift (touch end) of a predetermined duration. In another example, the definition of event 2 (187-2) is a drag on a displayed object. For example, dragging includes a touch (or contact) of a predetermined duration on a displayed object, movement of the touch on the touch-sensitive display 112, and lifting of the touch (end of touch). In some embodiments, the event also includes information for one or more associated event handlers 190.
[0181] In some embodiments, event definition 187 includes definitions of events for corresponding user interface objects. In some embodiments, event comparator 184 performs a hit test to determine which user interface object is associated with a sub-event. For example, in an application view displaying three user interface objects on touch display 112, when a touch is detected on touch-sensitive display 112, event comparator 184 performs a hit test to determine which of the three user interface objects is associated with the touch (sub-event). If each displayed object is associated with a corresponding event handler 190, the event comparator uses the result of the hit test to determine which event handler 190 should be activated. For example, event comparator 184 selects an event handler associated with a sub-event and the object that triggered the hit test.
[0182] In some embodiments, the definition of the corresponding event (187) also includes a delay action that delays delivery of the event information until it has been determined whether the sub-event sequence does or does not correspond to the event type of the event identifier.
[0183] When a corresponding event recognizer 180 determines that a sequence of sub-events does not match any event in event definition 186, the corresponding event recognizer 180 enters an event not possible, event failed, or event ended state, after which subsequent sub-events of the touch-based gesture are ignored. In this case, other event recognizers (if any) that remain active for the hit view continue to track and process sub-events of the ongoing touch-based gesture.
[0184] In some embodiments, the corresponding event identifier 180 includes metadata 183 with configurable properties, flags, and / or lists for indicating how the event delivery system should perform sub-event delivery to actively participating event identifiers. In some embodiments, metadata 183 includes configurable properties, flags, and / or lists for indicating how event identifiers interact or can interact with each other. In some embodiments, metadata 183 includes configurable properties, flags, and / or lists for indicating whether sub-events are delivered to different levels in a view or programmatic hierarchy.
[0185] In some embodiments, when one or more specific sub-events of an event are identified, the corresponding event recognizer 180 activates an event handler 190 associated with the event. In some embodiments, the corresponding event recognizer 180 delivers event information associated with the event to the event handler 190. Activating the event handler 190 is different from sending (and deferred sending) the sub-events to the corresponding hit view. In some embodiments, the event recognizer 180 throws a tag associated with the identified event, and the event handler 190 associated with the tag obtains the tag and performs a predefined process.
[0186] In some embodiments, event delivery instructions 188 include sub-event delivery instructions that deliver event information about a sub-event without activating an event handler. Instead, the sub-event delivery instructions deliver the event information to an event handler associated with a sub-event string or to an actively participating view. An event handler associated with a sub-event sequence or with an actively participating view receives the event information and executes a predetermined process.
[0187] In some embodiments, data updater 176 creates and updates data used in application 136-1. For example, data updater 176 updates phone numbers used in contact module 137 or stores video files used in video player module. In some embodiments, object updater 177 creates and updates objects used in application 136-1. For example, object updater 177 creates new user interface objects or updates the position of user interface objects. GUI updater 178 updates the GUI. For example, GUI updater 178 prepares display information and sends it to graphics module 132 for display on a touch-sensitive display.
[0188] In some embodiments, one or more event handlers 190 include or have access to data updater 176, object updater 177, and GUI updater 178. In some embodiments, data updater 176, object updater 177, and GUI updater 178 are included in a single module of the corresponding application 136-1 or application view 191. In other embodiments, they are included in two or more software modules.
[0189] It should be understood that the above discussion of event processing for user touches on a touch-sensitive display also applies to other forms of user input that utilize input devices to operate the multifunction device 100, not all of which are initiated on the touch screen. For example, mouse movement and mouse button presses, optionally combined with single or multiple keyboard presses or holds; contact movement on a touch pad, such as taps, drags, scrolls, etc.; stylus input; movement of the device; verbal commands; detected eye movement; biometric input; and / or any combination thereof as input corresponding to a sub-event to define an event to be recognized.
[0190] Figure 2A portable multifunction device 100 with a touch screen 112 according to some embodiments is shown. The touch screen optionally displays one or more graphics within a user interface (UI) 200. In this embodiment and in other embodiments described below, a user can select one or more of these graphics by, for example, making gestures on the graphics using one or more fingers 202 (not drawn to scale in the accompanying drawings) or using one or more styluses 203 (not drawn to scale in the accompanying drawings). In some embodiments, selection of one or more graphics will occur when the user interrupts contact with the one or more graphics. In some embodiments, gestures optionally include one or more taps, one or more swipes (from left to right, from right to left, up and / or down) and / or rolling of fingers that have been in contact with the device 100 (from right to left, from left to right, up and / or down). In some specific implementations or in some cases, inadvertent contact with a graphic will not select the graphic. For example, when the gesture corresponding to the selection is a tap, a swipe gesture that sweeps over an application icon optionally does not select the corresponding application.
[0191] The device 100 may also include one or more physical buttons, such as a "home" button or menu button 204. As previously described, the menu button 204 may be used to navigate to any application 136 in a set of applications executable on the device 100. Alternatively, in some embodiments, the menu button is implemented as a soft key in a GUI displayed on the touch screen 112.
[0192] In some embodiments, the device 100 includes a touch screen 112, a menu button 204, a push button 206 for turning the device on / off and for locking the device, one or more volume adjustment buttons 208, a user identity module (SIM) card slot 210, an earphone jack 212, and a docking / charging external port 124. The push button 206 is optionally used to: power on / off the device by pressing the button and keeping the button in a pressed state for a predetermined time interval; lock the device by pressing the button and releasing the button before a predetermined time interval passes; and / or unlock the device or initiate an unlocking process. In an alternative embodiment, the device 100 also accepts voice input for activating or deactivating certain functions through a microphone 113. The device 100 also optionally includes one or more contact strength sensors 165 for detecting the strength of contact on the touch screen 112, and / or one or more tactile output generators 167 for generating tactile output for a user of the device 100.
[0193] Figure 3300 is a block diagram of an exemplary multifunction device with a display and a touch-sensitive surface according to some embodiments. Device 300 does not have to be portable. In some embodiments, device 300 is a laptop computer, a desktop computer, a tablet computer, a multimedia player device, a navigation device, an educational device (such as a children's learning toy), a game system, or a control device (e.g., a home controller or an industrial controller). Device 300 typically includes one or more processing units (CPUs) 310, one or more network or other communication interfaces 360, a memory 370, and one or more communication buses 320 for interconnecting these components. The communication bus 320 optionally includes a circuit system (sometimes called a chipset) that interconnects system components and controls communication between system components. Device 300 includes an input / output (I / O) interface 330 with a display 340, which is typically a touch screen display. The I / O interface 330 also optionally includes a keyboard and / or a mouse (or other pointing device) 350 and a touchpad 355, a tactile output generator 357 for generating tactile output on the device 300 (e.g., similar to the above reference). Figure 1A The one or more tactile output generators 167 described above), sensors 359 (e.g., optical sensors, acceleration sensors, proximity sensors, touch sensors, and / or sensors similar to those described above) Figure 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 located remotely from one or more CPUs 310. In some embodiments, memory 370 stores data related to portable multifunction device 100 ( Figure 1A ) or a subset thereof. In addition, memory 370 optionally stores additional programs, modules, and data structures not present in memory 102 of portable multifunction device 100. For example, memory 370 of device 300 optionally stores a drawing module 380, a presentation module 382, a word processing module 384, a website creation module 386, a disk editing module 388, and / or a spreadsheet module 390, while portable multifunction device 100 ( Figure 1A )'s memory 102 optionally does not store these modules.
[0194] Figure 3Each of the above-mentioned elements in can be stored in one or more of the aforementioned memory devices. Each module in the above-mentioned modules corresponds to an instruction set for performing the above-mentioned functions. The above-mentioned modules or programs (e.g., instruction sets) do not have to be implemented as separate software programs, processes or modules, and therefore various subsets of these modules can be combined or otherwise rearranged in various embodiments. In some embodiments, memory 370 can store subsets of the above-mentioned modules and data structures. In addition, memory 370 can store additional modules and data structures not described above.
[0195] Attention is now turned to embodiments of a user interface that may be implemented on, for example, portable multifunction device 100 .
[0196] Figure 4A An exemplary user interface of an application menu on portable multifunction device 100 is shown according to some embodiments. A similar user interface can be implemented on device 300. In some embodiments, user interface 400 includes the following elements, or a subset or superset thereof:
[0197] One or more signal strength indicators 402 of one or more wireless communications such as cellular signals and Wi-Fi signals;
[0198] Time 404;
[0199] Bluetooth indicator 405;
[0200] Battery status indicator 406;
[0201] A tray 408 with icons of commonly used applications, such as:
[0202] o an icon 416 of the phone module 138 labeled “Phone”, the icon 416 optionally including an indicator 414 of the number of missed calls or voice messages;
[0203] o an icon 418 of the email client module 140 labeled “Mail,” which optionally includes an indicator 410 of the number of unread emails;
[0204] o An icon 420 of the browser module 147 labeled "Browser"; and
[0205] o an icon 422 labeled “iPod” of a video and music player module 152 (also referred to as an iPod (trademark of Apple Inc.) module 152); and
[0206] Icons of other applications, such as:
[0207] o Icon 424 of IM module 141 labeled “Message”;
[0208] o Icon 426 labeled “Calendar” of calendar module 148;
[0209] o Icon 428 labeled “Photos” of the image management module 144;
[0210] o An icon 430 labeled “Camera” of the camera module 143;
[0211] o Icon 432 labeled “Online Video” of the online video module 155;
[0212] o Icon 434 labeled "Stock Market" of the Stock Market widget 149-2;
[0213] o an icon 436 labeled “MAP” of the map module 154;
[0214] o Icon 438 labeled "Weather" of the Weather widget 149-1;
[0215] o Icon 440 labeled as “Clock” of the alarm clock widget 149-4;
[0216] o an icon 442 labeled “Fitness Support” of the fitness support module 142;
[0217] o An icon 444 of the notepad module 153 labeled "Notepad"; and
[0218] o An icon 446 labeled “Settings” for a settings application or module that provides access to settings for the device 100 and its various applications 136.
[0219] It should be pointed out that Figure 4A The icon labels shown in are exemplary only. For example, icon 422 of video and music player module 152 may optionally be labeled "Music" or "Music Player". Other labels are optionally used for various application icons. In some embodiments, the label of a respective application icon includes the name of the application corresponding to the respective application icon. In some embodiments, the label of a particular application icon is different from the name of the application corresponding to the particular application icon.
[0220] Figure 4B A touch-sensitive surface 451 (eg, touch screen display 112) is shown having a touch-sensitive surface 451 (eg, Figure 3 tablet computer or touch pad 355) device (e.g., Figure 3Device 300 also optionally includes one or more contact intensity sensors (e.g., one or more of sensors 357) for detecting intensity of contacts on touch-sensitive surface 451, and / or one or more tactile output generators 359 for generating tactile output for a user of device 300.
[0221] Although some of the examples that follow will be given with reference to input on a touch screen display 112 (where a touch-sensitive surface and a display are combined), in some embodiments, the device detects input on a touch-sensitive surface that is separate from the display, such as Figure 4B In some embodiments, the touch-sensitive surface (e.g., Figure 4B 451) has a main axis (e.g., Figure 4B 453) corresponding to the principal axis (for example, Figure 4B According to these embodiments, the device detects a position corresponding to a corresponding position on the display (e.g., Figure 4B 460 corresponds to 468 and 462 corresponds to 470) in contact with touch-sensitive surface 451 (e.g., Figure 4B 460 and 462 in FIG. 4 ). Thus, on a touch-sensitive surface (eg, Figure 4B 451) and the display of a multi-function device ( Figure 4B When the user input detected by the device on the touch-sensitive surface (e.g., contacts 460 and 462 and their movement) is separated, the device is used to manipulate the user interface on the display. It should be understood that similar methods are optionally used for other user interfaces described herein.
[0222] In addition, although the following examples are primarily given with reference to finger inputs (e.g., finger contacts, single-finger tap gestures, finger swipe gestures), it should be understood that in some embodiments, one or more of these finger inputs are replaced by input from another input device (e.g., mouse-based input or stylus input). For example, a swipe gesture is optionally replaced by a mouse click (e.g., instead of contact), followed by movement of the cursor along the path of the swipe (e.g., instead of movement of the contact). As another example, a tap gesture is optionally replaced by a mouse click when the cursor is over the location of the tap gesture (e.g., instead of detection of contact, followed by termination of detection of contact). Similarly, when multiple user inputs are detected simultaneously, it should be understood that multiple computer mice are optionally used simultaneously, or one mouse and multiple finger contacts are optionally used simultaneously.
[0223] Figure 5AAn exemplary personal electronic device 500 is shown. Device 500 includes a body 502. In some embodiments, device 500 may include a device 502 for devices 100 and 300 (e.g., Figures 1A-4B ) or some or all of the features described in the preceding claims. In some embodiments, device 500 has a touch-sensitive display screen 504, hereinafter referred to as touch screen 504. As an alternative or in addition to touch screen 504, device 500 has a display and a touch-sensitive surface. As with devices 100 and 300, in some embodiments, touch screen 504 (or touch-sensitive surface) may have one or more intensity sensors for detecting the intensity of an applied contact (e.g., a touch). One or more intensity sensors of touch screen 504 (or touch-sensitive surface) may provide output data representing the intensity of the touch. The user interface of device 500 may respond to touches based on the intensity of the touches, which means that touches of different intensities may invoke different user interface operations on device 500.
[0224] For example, technology for detecting and processing touch intensity can be found in the following related patent applications: International Patent Application No. PCT / US2013 / 040061, entitled “Device, Method, and Graphical User Interface for Displaying User Interface Objects Corresponding to an Application,” filed on May 8, 2013, and International Patent Application No. PCT / US2013 / 069483, entitled “Device, Method, and Graphical User Interface for Transitioning Between Touch Input to Display Output Relationships,” filed on November 11, 2013, each of which is hereby incorporated by reference in its entirety.
[0225] In some embodiments, the device 500 has one or more input mechanisms 506 and 508. The input mechanisms 506 and 508 (if included) can be physical. Examples of physical input mechanisms include push buttons and rotatable mechanisms. In some embodiments, the device 500 has one or more attachment mechanisms. Such attachment mechanisms (if included) can allow the device 500 to be attached to, for example, hats, glasses, earrings, necklaces, shirts, jackets, bracelets, watchbands, bracelets, pants, belts, shoes, wallets, backpacks, etc. These attachment mechanisms can allow the user to wear the device 500.
[0226] Figure 5BAn exemplary personal electronic device 500 is shown. In some embodiments, the device 500 may include a reference Figure 1A , Figure 1B and Figure 3 Some or all of the components described. Device 500 has a bus 512 that operatively couples an I / O portion 514 to one or more computer processors 516 and a memory 518. I / O portion 514 may be connected to a display 504, which may have a touch-sensitive component 522 and optionally also a touch-intensity sensitive component 524. In addition, I / O portion 514 may be connected to a communication unit 530 for receiving application and operating system data using Wi-Fi, Bluetooth, near field communication (NFC), cellular and / or other wireless communication technologies. Device 500 may include input mechanisms 506 and / or 508. For example, input mechanism 506 may be a rotatable input device or a depressible input device and a rotatable input device. In some examples, input mechanism 508 may be a button.
[0227] In some examples, input mechanism 508 may be a microphone. Personal electronic device 500 may include various sensors, such as GPS sensor 532, accelerometer 534, orientation sensor 540 (e.g., compass), gyroscope 536, motion sensor 538, and / or combinations thereof, all of which may be operatively connected to I / O portion 514.
[0228] The memory 518 of the personal electronic device 500 may include one or more non-transitory computer-readable storage media for storing computer-executable instructions that, when executed by one or more computer processors 516, may cause the computer processors to perform the above-described techniques, including processes 700, 900, 1100, 1300, 1500, 1700, and 1900 ( Figure 7 , Fig. 9 , Fig.11 , Fig.13 , Fig.15 , Fig.17 and Fig.19 ). The personal electronic device 500 is not limited to Figure 5B components and configurations, but may include other components or additional components in a variety of configurations.
[0229] As used herein, the term "affordance" refers to a user-interactive graphical user interface object that can be displayed on a display screen of device 100, 300, and / or 500 (FIGS. 1, 3, and 5). For example, an image (e.g., an icon), a button, and text (e.g., a hyperlink) can each constitute an affordance.
[0230] As used herein, the term "focus selector" refers to an input element used to indicate the current portion of a user interface with which a user is interacting. In some implementations that include a cursor or other position marker, the cursor acts as a "focus selector" such that when the cursor is over a particular user interface element (e.g., a button, window, slider, or other user interface element), a focus selector is displayed on a touch-sensitive surface (e.g., Figure 3 Touchpad 355 or Figure 4B In the event that an input (e.g., a press input) is detected on the touch-sensitive surface 451 in the display, the particular user interface element is adjusted according to the detected input. In the case that a touch-screen display (e.g., Figure 1A A touch-sensitive display system 112 or Figure 4A In some implementations of the touch screen 112 in FIG. 1 , a detected contact on the touch screen acts as a “focus selector” such that when an input (e.g., a press input by the contact) is detected at the location of a particular user interface element (e.g., a button, window, slider, or other user interface element) on the touch screen display, the particular user interface element is adjusted in accordance with the detected input. In some implementations, the focus moves from one area of the user interface to another area of the user interface without corresponding movement of a cursor or movement of a contact on the touch screen display (e.g., by using a tab key or arrow keys to move the focus from one button to another); in these implementations, the focus selector moves in accordance with the movement of focus between different areas of the user interface. Regardless of the specific form the focus selector takes, the focus selector is typically a user interface element (or contact on the touch screen display) that is controlled by the user to deliver the user's intended interaction with the user interface (e.g., by indicating to the device the element of the user interface with which the user desires to interact). For example, when a press input is detected on a touch-sensitive surface (e.g., a touchpad or touchscreen), the position of a focus selector (e.g., a cursor, contact, or selection box) over a corresponding button will indicate that the user intends to activate the corresponding button (rather than other user interface elements shown on the device display).
[0231] As used in the specification and claims, the term "characteristic intensity" of a contact refers to a characteristic of a contact based on one or more intensities of the contact. In some embodiments, the characteristic intensity is based on multiple intensity samples. The characteristic intensity is optionally based on a predefined number of intensity samples or a set of intensity samples collected during a predetermined time period (e.g., 0.05 seconds, 0.1 seconds, 0.2 seconds, 0.5 seconds, 1 second, 2 seconds, 5 seconds, 10 seconds) relative to a predefined event (e.g., after contact is detected, before contact is detected to be lifted, before or after contact begins to move, before contact ends, before or after contact intensity is detected to increase, and / or before or after contact intensity is detected to decrease). The characteristic intensity of a contact is optionally based on one or more of the following: the maximum value of contact intensity, the mean value of contact intensity, the average value of contact intensity, the value at the top 10% of contact intensity, the half-maximum value of contact intensity, the 90% maximum value of contact intensity, etc. In some embodiments, the duration of the contact is used when determining the characteristic intensity (e.g., when the characteristic intensity is the average value of the intensity of the contact over time). In some embodiments, the feature strength is compared to a set of one or more strength thresholds to determine whether the user has performed an operation. For example, the set of one or more strength thresholds may include a first strength threshold and a second strength threshold. In this example, a contact whose feature strength does not exceed the first threshold results in a first operation, a contact whose feature strength exceeds the first strength threshold but does not exceed the second strength threshold results in a second operation, and a contact whose feature strength exceeds the second threshold results in a third operation. In some embodiments, a comparison between the feature strength and one or more thresholds is used to determine whether to perform one or more operations (e.g., whether to perform the corresponding operation or to abandon the corresponding operation), rather than to determine whether to perform the first operation or the second operation.
[0232] Figure 5C Multiple contacts 552A-552E on touch-sensitive display screen 504 are shown detected using multiple intensity sensors 524A-524D. Figure 5C Also included is an intensity graph showing the current intensity measurements of intensity sensors 524A-524D relative to intensity units. In this example, the intensity measurements of intensity sensors 524A and 524D are each 9 intensity units, and the intensity measurements of intensity sensors 524B and 524C are each 7 intensity units. In some implementations, the aggregate intensity is the sum of the intensity measurements of multiple intensity sensors 524A-524D, which in this example is 32 intensity units. In some embodiments, each contact is assigned a corresponding intensity as a portion of the aggregate intensity. Figure 5DThe assignment of aggregate strengths to contacts 552A-552E based on their distance from the force center 554 is shown. In this example, each of contacts 552A, 552B, and 552E is assigned a contact strength of 8 strength units of the aggregate strength, and each of contacts 552C and 552D is assigned a contact strength of 4 strength units of the aggregate strength. More generally, in some embodiments, each contact j is assigned a corresponding strength Ij as a portion of the aggregate strength A according to a predefined mathematical function Ij=A·(Dj / ΣDi), where Dj is the distance of the corresponding contact j from the force center, and ΣDi is the sum of the distances of all corresponding contacts (e.g., i=1 to the last) from the force center. Reference Figure 5C-5D The operations described may be performed using an electronic device similar or identical to device 100, 300, or 500. In some embodiments, the characteristic intensity of the contact is based on one or more intensities of the contact. In some embodiments, an intensity sensor is used to determine a single characteristic intensity (e.g., a single characteristic intensity of a single contact). It should be noted that the intensity map is not part of the displayed user interface, but is included for the convenience of the reader. Figure 5C-5D middle.
[0233] In some embodiments, a portion of a gesture is identified for determining a characteristic strength. For example, a touch-sensitive surface may receive a continuous swipe contact that transitions from a starting position and reaches an end position, where the strength of the contact increases. In this example, the characteristic strength of the contact at the end position may be based only on a portion of the continuous swipe contact, rather than the entire swipe contact (e.g., only a portion of the swipe contact at the end position). In some embodiments, a smoothing algorithm may be applied to the strength of the swipe gesture before determining the characteristic strength of the contact. For example, the smoothing algorithm optionally includes one or more of the following: an unweighted sliding average smoothing algorithm, a triangular smoothing algorithm, a median filter smoothing algorithm, and / or an exponential smoothing algorithm. In some cases, these smoothing algorithms eliminate narrow peaks or dips in the strength of the swipe contact to achieve the purpose of determining the characteristic strength.
[0234] The intensity of a contact on a touch-sensitive surface may be characterized relative to one or more intensity thresholds, such as a contact detection intensity threshold, a light press intensity threshold, a deep press intensity threshold, and / or one or more other intensity thresholds. In some embodiments, the light press intensity threshold corresponds to an intensity at which the device will perform an operation typically associated with clicking a button of a physical mouse or trackpad. In some embodiments, the deep press intensity threshold corresponds to an intensity at which the device will perform an operation different from an operation typically associated with clicking a button of a physical mouse or trackpad. In some embodiments, when a contact having a characteristic intensity below a light press intensity threshold (e.g., and above a nominal contact detection intensity threshold, contacts below which are no longer detected) is detected, the device will move the focus selector in accordance with the movement of the contact on the touch-sensitive surface without performing an operation associated with the light press intensity threshold or the deep press intensity threshold. Generally speaking, unless otherwise stated, these intensity thresholds are consistent between different groups of user interface illustrations.
[0235] An increase in contact feature intensity from an intensity below a light press intensity threshold to an intensity between the light press intensity threshold and the deep press intensity threshold is sometimes referred to as a "light press" input. An increase in contact feature intensity from an intensity below a deep press intensity threshold to an intensity above the deep press intensity threshold is sometimes referred to as a "deep press" input. An increase in contact feature intensity from an intensity below a contact detection intensity threshold to an intensity between the contact detection intensity threshold and the light press intensity threshold is sometimes referred to as detecting contact on the touch surface. A decrease in contact feature intensity from an intensity above the contact detection intensity threshold to an intensity below the contact detection intensity threshold is sometimes referred to as detecting contact lifted from the touch surface. In some embodiments, the contact detection intensity threshold is zero. In some embodiments, the contact detection intensity threshold is greater than zero.
[0236] In some embodiments described herein, one or more operations are performed in response to detecting a gesture that includes a corresponding press input or in response to detecting a corresponding press input performed using a corresponding contact (or multiple contacts), wherein the corresponding press input is detected at least in part based on detecting that the strength of the contact (or multiple contacts) increases to above a press input strength threshold. In some embodiments, the corresponding operation is performed in response to detecting that the strength of the corresponding contact increases to above the press input strength threshold (e.g., a "down stroke" of the corresponding press input). In some embodiments, the press input includes an increase in the strength of the corresponding contact to above the press input strength threshold and the strength of the contact subsequently decreases to below the press input strength threshold, and the corresponding operation is performed in response to detecting that the strength of the corresponding contact subsequently decreases to below the press input threshold (e.g., an "up stroke" of the corresponding press input).
[0237] Figure 5E-5HDetection of a gesture is shown, the gesture comprising a press input corresponding to a change in the intensity of contact 562 from Figure 5E Below the light pressure threshold (e.g., “IT L ”) increases in intensity to Figure 5H Medium to above the deep compression intensity threshold (e.g., “IT D A gesture performed with contact 562 is detected on touch-sensitive surface 560, and cursor 576 is displayed over application icon 572B corresponding to App 2 on displayed user interface 570, which includes application icons 572A-572D displayed in predefined area 574. In some embodiments, gestures are detected on touch-sensitive display 504. The intensity sensor detects the intensity of the contact on touch-sensitive surface 560. The device determines that the intensity peak of contact 562 is above the deep press intensity threshold (e.g., “IT D ”). Contact 562 remains on touch-sensitive surface 560. In response to detecting the gesture, and based on contact 562 having a pressure exceeding a deep press intensity threshold (e.g., “IT D ”), displaying reduced scale representations 578A-578C (e.g., thumbnails) of recently opened documents of App 2, such as Figure 5F-5H In some embodiments, the intensity compared to one or more intensity thresholds is a characteristic intensity of the contact. It should be noted that the intensity map of contact 562 is not part of the displayed user interface, but is included for the convenience of the reader. Figure 5E-5H middle.
[0238] In some embodiments, the display of representations 578A-578C includes animation. For example, representation 578A is initially displayed near application icon 572B, such as Fig. 5F As the animation progresses, representation 578A moves upward, and representation 578B is displayed near application icon 572B, as shown. Figure 5G Then, representation 578A moves upward, representation 578B moves upward toward representation 578A, and representation 578C is displayed near application icon 572B, as shown. Figure 5H 578A-578C form an array above icon 572B. In some embodiments, the animation progresses according to the intensity of contact 562, such as Figure 5F-5G As shown, as the intensity of contact 562 moves toward a deep press intensity threshold (eg, “IT D ”) increases, indicating that 578A-578C appear and move upward. In some embodiments, the intensity on which the animation progresses is based on the characteristic intensity of the contact. Figure 5E-5H The described operations may be performed using an electronic device similar or identical to device 100 , 300 , or 500 .
[0239] In some embodiments, the device employs intensity hysteresis to avoid unexpected input, sometimes referred to as "jitter," where the device defines or selects a hysteresis intensity threshold that has a predefined relationship to a press input intensity threshold (e.g., the hysteresis intensity threshold is X intensity units lower than the press input intensity threshold, or the hysteresis intensity threshold is 75%, 90%, or some reasonable proportion of the press input intensity threshold). Thus, in some embodiments, a press input includes an increase in the intensity of the corresponding contact to above the press input intensity threshold and a subsequent decrease in the intensity of the contact to below a hysteresis intensity threshold corresponding to the press input intensity threshold, and a corresponding operation is performed in response to detecting that the intensity of the corresponding contact subsequently decreases to below the hysteresis intensity threshold (e.g., an "up stroke" of the corresponding press input). Similarly, in some embodiments, a press input is detected only when the device detects that the strength of the contact increases from an strength equal to or below a hysteresis strength threshold to an strength equal to or above a press input strength threshold and, optionally, the strength of the contact subsequently decreases to an strength equal to or below the hysteresis strength, and a corresponding operation is performed in response to detecting the press input (for example, depending on the circumstances, the strength of the contact increases or the strength of the contact decreases).
[0240] For ease of explanation, a description of an operation performed in response to a press input associated with a press input intensity threshold or in response to a gesture including a press input is optionally triggered in response to detecting any of the following: the intensity of the contact increases above the press input intensity threshold, the intensity of the contact increases from an intensity below a hysteresis intensity threshold to an intensity above the press input intensity threshold, the intensity of the contact decreases below the press input intensity threshold, and / or the intensity of the contact decreases below a hysteresis intensity threshold corresponding to the press input intensity threshold. Additionally, in examples where an operation is described as being performed in response to detecting that the intensity of the contact decreases below the press input intensity threshold, the operation is optionally performed in response to detecting that the intensity of the contact decreases below a hysteresis intensity threshold that corresponds to and is less than the press input intensity threshold.
[0241] Fig.5I Exemplary devices connected via one or more communication channels to complete payment transactions according to some embodiments are shown. One or more exemplary electronic devices (e.g., devices 100, 300, and 500) are configured to optionally detect input (e.g., specific user input, NFC field), and optionally transmit payment information (e.g., using NFC). The one or more electronic devices optionally include NFC hardware and are configured to support NFC.
[0242] The electronic device (e.g., devices 100, 300, and 500) is optionally configured to store payment account information associated with each of the one or more payment accounts. The payment account information includes, for example, one or more of the following: a person's name or company name, a billing address, a login name, a password, an account number, an expiration date, a security code, a phone number, a bank associated with the payment account (e.g., an issuing bank), and a card network identifier. In some examples, the payment account information includes an image, such as a photo of a payment card (e.g., a photo taken by the device and / or received by the device). In some examples, the electronic device receives user input including at least some payment account information (e.g., receiving a credit card number, a debit card number, an account number or a shopping card number and an expiration date entered by the user). In some examples, the electronic device detects at least some payment account information from an image (e.g., of a payment card captured by a camera sensor of the device). In some examples, the electronic device receives at least some payment account information from another device (e.g., another user device or a server). In some examples, the electronic device receives payment account information from a server associated with another service (e.g., an application for renting or selling audio files and / or video files) for which the user or user device's account has previously made a purchase or for which payment account data is identified.
[0243] In some embodiments, a payment account is added to an electronic device (e.g., devices 100, 300, and 500) so that the payment account information is securely stored on the electronic device. In some examples, after a user initiates such a process, the electronic device transmits the payment account information to a transaction coordination server, which then communicates with a server operated by the account's payment network (e.g., a payment server) to ensure the validity of the information. The electronic device is optionally configured to receive a script from the server that allows the electronic device to program the account's payment information onto a secure element.
[0244] In some embodiments, the communication between devices 100, 300 and 500 facilitates transactions (e.g., general transactions or specific transactions). For example, a first electronic device (e.g., 100) may be used as a configuration device or a management device, and may send new or updated payment account data (e.g., information about a new account, updated information about an existing account, and / or a warning about an existing account) to a second electronic device (e.g., 500). As another example, a first electronic device (e.g., 100) may send data to a second electronic device, wherein the data reflects information about a payment transaction facilitated at the first electronic device. The information optionally includes one or more of the following: the payment amount, the account used, the time of purchase, and whether to change the default account. The second device (e.g., 500) optionally uses such information to update the default payment account (e.g., based on a learning algorithm or explicit user input).
[0245] Electronic devices (e.g., 100, 300, 500) are configured to communicate with each other via any of a variety of networks. For example, the devices communicate using a Bluetooth connection 580 (e.g., including a traditional Bluetooth connection or a Bluetooth low energy connection) or using a WiFi network 582. Communications between user devices are optionally adjusted to reduce the possibility of improper sharing of information between devices. For example, communication about payment information requires that the communicating devices be paired (e.g., associated with each other via explicit user interaction) or associated with the same user account.
[0246] In some embodiments, an electronic device (e.g., 100, 300, 500) is used to communicate with a point-of-sale (POS) payment terminal 820, 1220, which optionally supports NFC. The communication is optionally carried out using various communication channels and / or technologies. In one example, an electronic device (e.g., 100, 300, 500) uses an NFC channel 584 to communicate with a payment terminal 820, 1220. In some examples, a payment terminal 820, 1220 uses a peer-to-peer NFC mode to communicate with an electronic device (e.g., 100, 300, 500). An electronic device (e.g., 100, 300, 500) is optionally configured to transmit a signal to a payment terminal 820, 1220, the signal including payment information of a payment account (e.g., a default account or an account selected for a specific transaction).
[0247] In some embodiments, the generation and / or transmission of the signal is controlled by a security element in an electronic device (e.g., 100, 300, 500). Before releasing the payment information, the security element optionally requires specific user input. For example, the security element optionally requires: detecting the electronic device being worn, detecting button presses, detecting password input, detecting touch, detecting one or more option selections (e.g., option selections received when interacting with an application), detecting fingerprint signatures, detecting voice or voice commands, and / or detecting gestures or movements (e.g., rotation or acceleration). In some examples, if a communication channel (e.g., NFC communication channel) with another device (e.g., payment terminal 820, 1220) is established within a defined time period from the detection of the input, the security element releases the payment information so that it is transmitted to another device (e.g., payment terminal 820, 1220). In some examples, the security element is a hardware component that controls the release of security information. In some examples, the security element is a software component that controls the release of security information.
[0248] In some embodiments, the protocol associated with transaction participation depends on, for example, the device type. For example, the conditions for generating and / or transmitting payment information may be different for a wearable device (e.g., device 500) and a phone (e.g., device 100). For example, a generation condition and / or a transmission condition for a wearable device includes detecting that a button has been pressed (e.g., after security verification), while a corresponding condition for a phone does not require a button press, but requires detection of a specific interaction with an application. In some embodiments, conditions for transmitting and / or releasing payment information include receiving specific input on each of a plurality of devices. For example, the release of payment information optionally requires detection of a fingerprint and / or password at a device (e.g., device 100), and detection of a mechanical input (e.g., a button press) on another device (e.g., device 500).
[0249] The payment terminal 820, 1220 optionally uses the payment information to generate a signal for transmission to the payment server 590 to determine whether the payment is authorized. The payment server 590 optionally includes any device or system configured to receive the payment information associated with the payment account and determine whether the proposed purchase is authorized. In some examples, the payment server 590 includes a server of the issuing bank. The payment terminal 820, 1220 communicates directly with the payment server 590 or indirectly via one or more devices or systems (e.g., a server of the acquiring bank and / or a server of the card network).
[0250] Payment server 590 optionally uses at least some of the payment information to identify a user account from a database of user accounts (e.g., 592). For example, each user account includes payment information. The account is optionally located by locating an account with specific payment information that matches the information from the POS communication. In some examples, payment is rejected when the provided payment information is inconsistent (e.g., the expiration date does not correspond to the credit card number, the debit card number, or the shopping card number does not correspond) or when no account includes payment information that matches the information from the POS communication.
[0251] In some embodiments, the user account data further identifies one or more limits (e.g., credit limit); current or previous period balance; last transaction date, transaction location and / or amount; account status (e.g., active or frozen), and / or authorization instructions. In some examples, the payment server (e.g., 590) uses such data to determine whether to authorize the payment. For example, the payment server denies payment when the purchase amount added to the current balance would cause the account limit to be exceeded, when the account is frozen, when the previous transaction amount exceeds a threshold, or when the number or frequency of previous transactions exceeds a threshold.
[0252] In some embodiments, the payment server 590 responds to the POS payment terminal 820, 1220 with an indication of whether the proposed purchase is authorized or rejected. In some examples, the POS payment terminal 820, 1220 transmits a signal to an electronic device (e.g., 100, 300, 500) to identify the result. For example, when the purchase (e.g., via a transaction coordination server that manages a transaction application on a user device) is authorized, the POS payment terminal 820, 1220 sends a receipt to the electronic device (e.g., 100, 300, 500). In some cases, the POS payment terminal 820, 1220 presents an output (e.g., a visual or audio output) indicating the result. The payment may be transmitted to the merchant as part of the authorization process, or may be transmitted later.
[0253] In some embodiments, the electronic device (e.g., 100, 300, 500) participates in a transaction that can be completed without involving a POS payment terminal 820, 1220. For example, upon detecting that a mechanical input has been received, a secure element in the electronic device (e.g., 100, 300, 500) releases payment information to allow an application on the electronic device to access the information (e.g., and transmit the information to a server associated with the application).
[0254] Attention is now turned to embodiments of a user interface ("UI") and associated processes that may be implemented on an electronic device, such as portable multifunction device 100, device 300, or device 500.
[0255] Some embodiments described below relate to loyalty accounts. For example, a loyalty account can be an account of a loyalty program that provides a structured marketing effort to reward a customer / member. A loyalty account is optionally dedicated to a specific company, store, or chain store. A company (such as a retail store or chain store) can use a loyalty account to track purchases or other information about a user (e.g., a buyer). A loyalty account generally allows a user to have a discount on current or future purchases and / or allows a user to have the right to allocate points that can be used for future purchases or gifts. In some examples, a loyalty account cannot be used to make payments. Generally speaking, a loyalty account cannot be used to make monetary payments.
[0256] Some embodiments described below relate to private label accounts. For example, a private label account includes a payment account that is trademarked for a specific merchant, independent distributor, or manufacturer. Some private label cards and private label accounts are only accepted at specific merchants, or may provide certain benefits that are only available at specific merchants. For example, a specific merchant may offer a private label account to a customer that can only be used when making a purchase through the specific merchant. Merchants are often more willing to offer private label accounts because the private label account provides customers with another way to shop from the merchant, thereby increasing sales and providing customers with a convenient payment option.
[0257] Some of the embodiments described below relate to transmitting payment account information from an electronic device to a contactless payment terminal, thereby enabling the contactless payment terminal to participate in a payment transaction, such as by routing the information to one or more financial institutions to verify payment credentials and / or receive authorization to complete the transaction. For example, an exemplary payment network architecture and additional details about the path of a payment transaction can be found in, e.g. Figure 2 and the accompanying description of the following application: U.S. Patent Application Serial No. 62 / 004,338, filed on May 29, 2014, entitled “USER DEVICE SECURE PARTICIPATION IN TRANSACTIONS VIA LOCAL SECURE ELEMENT DETECTION OF MECHANICAL INPUT” (Reference No. P22931USP1).
[0258] Figures 6A-6G Exemplary techniques and exemplary user interfaces for receiving a selection of an account from a plurality of accounts in an electronic wallet, such as a loyalty account or a payment account, are shown according to some embodiments. For example, account information for the selected account may then be transmitted to an NFC-enabled payment terminal for use in a transaction (e.g., when the device is placed in the field of the payment terminal). The user interfaces in these figures are used to illustrate the processes described below, including Figure 7 process.
[0259] Fig. 6A A wearable electronic device 500 is shown, which is, for example, a smart watch. The device includes a display, a touch-sensitive surface, and one or more wireless communication elements (e.g., one or more wireless antennas, such as NFC antennas, WiFi antennas). The device receives input (e.g., user input) for requesting that the device be enabled for payment transactions (e.g., a user double-clicks a hardware button 508 of the device to prepare the device for NFC payments and / or access to the device's electronic wallet).
[0260] In response to receiving an input requesting that the device be enabled for payment transactions, and Fig. 6A As shown, the device displays a first visual indicator 602 for identifying a first account on a display, and the device enables the electronic device to participate in a transaction using the first account via one or more wireless communication elements (e.g., preparing the device for NFC payment using a default payment account, or preparing the device for performing NFC transactions using a loyalty account). Ready indication 604 is a visual indication that the device is enabled to participate in a transaction using the first account represented by the first visual indicator 602. The first visual indicator 602 may occupy less than 70% (or less than 60%, 50%, or 40%) of the total display space of the display. The device may also display an indication 606 on the display that other accounts are also available, or an indication 606 of the number of other available accounts. In this example, indication 606 includes four paging points. The first paging point has a first color that is different from the second color of the second, third, and fourth paging points. The four paging points indicate that a total of four accounts are available. The color of the first paging point is different from the other paging points, indicating that the device is currently displaying information corresponding to the first account (e.g., the first visual indicator 602).
[0261] exist Figure 6B At , the electronic device receives one or more swipe inputs in a first direction (e.g., one or more left swipes or one or more right swipes) via the touch-sensitive surface. Figure 6B At , one or more swipe inputs are detected, and the first visual indicator 602 is being transformed to not be displayed (e.g., by sliding the first visual indicator 602 in the first direction). In some examples, when the first visual indicator 602 is being transformed to not be displayed, the ready indication 604 is no longer displayed.
[0262] like Figure 6CAs shown, in response to receiving one or more user swipe inputs, the device displays on the display a second visual indicator 620 for identifying a second account that is different from the first account, and the device enables the electronic device to participate in transactions using the second account via one or more wireless communication elements (for example, prepares the device for NFC transactions using the second account, and prohibits the device from participating in transactions using the first account). In some embodiments, the second visual indicator 620 is larger than the first visual indicator 602. For example, the second visual indicator occupies more than 70% (or more than 60%, 50%, or 40%) of the total display space of the display. Figure 6C At , first visual indicator 602 is no longer displayed, and paging point 606 has been updated to reflect that the device is currently displaying information corresponding to the second account (eg, second visual indicator 620). Ready indication 622 is a visual indication that the device is enabled to participate in transactions using the second account.
[0263] The first visual indicator 602 is different from the second visual indicator 610. For example, the first visual indicator 602 includes: the name of the first financial institution "AA Bank", with a first background design that corresponds to the background design of the payment card associated with the first account, at least a portion of the account number associated with the first account, and the expiration date associated with the first account. The second visual indicator 620 includes the name of the merchant associated with the loyalty account "SUPERMARKET INC.", with a second background design that is different from the first background design, and may or may not include at least a portion of the account number associated with the second account. In this example, the second visual indicator does not display the expiration date associated with the second account.
[0264] According to some embodiments, Figures 6A-6C As shown, the first account is a payment account and the second account is a loyalty account. According to some embodiments, Fig. 6A and 6G As shown, the first account is a payment account and the second account is a payment account.
[0265] According to some embodiments, Figure 6D-6F As shown, in display (e.g. of a loyalty account)
[0266] When the second visual indicator is displayed: the electronic device receives a card code display input (e.g., a user swipe input in a second direction different from the first direction; a tap on the "show barcode" enable indication 626), and in response to receiving the card code display input, the electronic device displays visual loyalty card code information (e.g., 624; a barcode or QR code) on the display. The visual loyalty card code information may optionally represent account information for the second account. For example, when Fig.6DAt , the device receives an upward swipe input on the touch-sensitive surface and, in response, displays a barcode 624. The user can allow the barcode 624 to be visually scanned by the payment terminal. Fig.6D At , the device receives the same upward swipe input on the touch-sensitive surface and, in response, displays an enable indication 626 that, when activated, displays visual loyalty card code information associated with the second account (e.g., 624).
[0267] According to some embodiments and with reference to Figure 6C The user interface of the contactless payment terminal is configured such that a user places the device in a field of the contactless payment terminal. While the second visual indicator is displayed: the electronic device receives a request for account information from the contactless payment terminal, and in response to receiving the request for account information, transmits account information of a second account to the contactless payment terminal via one or more wireless communication elements, wherein the account information enables the contactless payment terminal to participate in the payment transaction.
[0268] According to some embodiments, participating in the payment transaction includes routing the loyalty information to one or more servers for confirmation / authorization of the loyalty account (e.g., when the second account is a loyalty account). In some embodiments, participating in the payment transaction includes routing the information to one or more financial institutions to verify the payment credentials and / or receive authorization to complete the transaction (e.g., when the second account is a payment account). For example, NFC is used to transmit the account information to a contactless payment terminal.
[0269] According to some embodiments (e.g., where the second account is a payment account), while the second visual indicator is displayed and after the account information of the second account is transmitted to the contactless payment terminal: the electronic device receives a failed communication from the contactless payment terminal via one or more wireless communication elements (e.g., the payment was rejected because the payment account type was not accepted by the contactless payment terminal). In response to receiving the failed communication: the electronic device displays an indication on the display that the second account is not accepted, and provides an option for enabling the electronic device to participate in the transaction using an account different from the second account (e.g., a default payment account that is not a private-label payment account).
[0270] According to some embodiments, after (or in response to) transmitting the account information of the second account to the contactless payment terminal, the electronic device simultaneously displays on the display an indication that both the first account and the second account were used during the payment transaction (e.g., simultaneously displaying at least a portion of the first visual indicator and at least a portion of the second visual indicator). For example, a user may use the electronic device to provide loyalty account information with the second account and payment account information with the first account. Thus, the two visual indicators will be displayed simultaneously after the transaction.
[0271] According to some embodiments, enabling the electronic device to participate in a transaction using the second account via one or more wireless communication elements does not require receiving a second user input requesting that the device be enabled for a payment transaction. For example, the user does not need to double-click the hardware button 508 again to prepare the device for an NFC payment or NFC loyalty transaction using the second account.
[0272] According to some embodiments, enabling the electronic device to participate in a transaction using the first account includes: displaying a first animation of a ready indicator (e.g., 604) that appears from below the card image of the first account (e.g., first visual indicator 602). The ready indicator (e.g., 604) indicates that the device is enabled to participate in a payment transaction using the first account. In response to receiving a portion of one or more user swipe inputs, the electronic device displays a second animation of the ready indicator to slide the ready indicator (e.g., 604) back below the card image of the first account.
[0273] According to some embodiments, the electronic device displays a first visual indicator (e.g., 602) for identifying a first account, and then enables the electronic device to participate in transactions using the first account via one or more wireless communication elements. The electronic device displays a second visual indicator (e.g., 620) on the display for identifying a second account, and then enables the electronic device to participate in transactions using the second account via one or more wireless communication elements.
[0274] According to some embodiments, one of the first account and the second account is a payment account, and one of the first account and the second account is a loyalty account (e.g., the first account is a payment account, and the second account is a loyalty account). The first visual indicator (e.g., 602) of the first account has a first dimensional feature (e.g., size or aspect ratio), and the second visual indicator (e.g., 620) of the second account has a second dimensional feature different from the first dimensional feature (e.g., different size or different aspect ratio). Therefore, the visual indication of the loyalty account looks different from the visual indication of the payment account. This helps the user quickly identify whether the loyalty account or the payment account is displayed and / or enabled.
[0275] According to some embodiments, the electronic wallet of the electronic device includes payment account information of multiple payment accounts associated with the user of the electronic device (e.g., including payment accounts associated with 602 and 610).
[0276] like Fig. 6FAs shown, the electronic device receives a second one or more swipe inputs in a first direction via the touch-sensitive surface. In response to receiving the second one or more user swipe inputs, the electronic device displays a third visual indicator identifying a third account on the display, and the electronic device enables the electronic device to participate in transactions using the third account via one or more wireless communication elements; and (for example, prepares the device to conduct NFC transactions using the third account and prohibits the device from participating in transactions using the second account). The third visual indicator is different from the first visual indicator and the second visual indicator.
[0277] Figure 7 700 is a flow chart showing a method according to some embodiments for receiving a selection of an account from a plurality of accounts in an electronic wallet, such as a loyalty account or a payment account, using an electronic device. Method 700 is performed at a device (e.g., 100, 300, 500) having a display, a touch-sensitive surface, and one or more wireless communication elements. Some operations in method 700 may be combined, the order of some operations may be changed, and some operations may be omitted.
[0278] As described below, method 700 provides an intuitive way to receive a selection of an account, such as a loyalty account or a payment account, from a plurality of accounts in an electronic wallet. The method reduces the cognitive burden on the user to receive the selection of an account, thereby creating a more efficient human-computer interface. For battery-powered computing devices, enabling users to select accounts faster and more efficiently saves power and increases the time interval between battery charges.
[0279] At block 702 , the electronic device receives input (eg, the user input at 508 ) requesting that the device be enabled for a payment transaction.
[0280] At block 704, in response to receiving input requesting that the device be enabled for a payment transaction, the process proceeds to blocks 706-708.
[0281] At block 706, the electronic device displays on the display a first visual indicator (eg, 602) identifying the first account. At block 708, the electronic device enables the electronic device to participate in a transaction using the first account via one or more wireless communication elements.
[0282] At box 710, the electronic device receives one or more swipe inputs in a first direction (e.g., one or more left swipes) via the touch-sensitive surface.
[0283] At block 712 , in response to receiving one or more user swipe inputs, the process proceeds to blocks 714 - 716 .
[0284] At block 714, the electronic device displays on the display a second visual indicator (e.g., 620) for identifying the second account. At block 716, the electronic device enables the electronic device to participate in transactions using the second account via one or more wireless communication elements, wherein the first visual indicator (e.g., 601) is different from the second visual indicator (e.g., 620).
[0285] According to some embodiments, the first account is a payment account and the second account is a loyalty account. According to some embodiments, the first account is a payment account and the second account is a payment account.
[0286] In accordance with some embodiments, while a second visual indicator (e.g., a second visual indicator 620 of a loyalty account) is displayed: the electronic device receives a card code display input, and in response to receiving the card code display input, the electronic device displays visual loyalty card code information (e.g., 624; a bar code or QR code) on the display.
[0287] According to some embodiments, a user places the device in a field of the contactless payment terminal. While the second visual indicator is displayed: the electronic device receives a request for account information from the contactless payment terminal, and in response to receiving the request for account information, transmits account information for a second account to the contactless payment terminal via one or more wireless communication elements, wherein the account information enables the contactless payment terminal to participate in the payment transaction.
[0288] According to some embodiments (e.g., where the second account is a payment account), while the second visual indicator is displayed and after the account information of the second account is transmitted to the contactless payment terminal: the electronic device receives a failed communication from the contactless payment terminal via one or more wireless communication elements. In response to receiving the failed communication: the electronic device displays an indication on the display that the second account is not accepted, and provides an option for enabling the electronic device to participate in the transaction using an account different from the second account.
[0289] In accordance with some embodiments, after (or in response to) transmitting account information of the second account to the contactless payment terminal, the electronic device simultaneously displays on the display an indication that both the first account and the second account were used during the payment transaction (e.g., simultaneously displaying at least a portion of the first visual indicator and at least a portion of the second visual indicator).
[0290] According to some embodiments, enabling the electronic device to participate in a transaction using the first account includes displaying a first animation of a ready indicator (e.g., 604) that appears from below the card image of the first account (e.g., first visual indicator 602). The ready indicator (e.g., 604) indicates that the device is enabled to participate in a payment transaction using the first account. In response to receiving a portion of one or more user swipe inputs, the electronic device displays a second animation of the ready indicator to slide the ready indicator (e.g., 604) back below the card image of the first account.
[0291] According to some embodiments, the electronic device displays a first visual indicator (e.g., 602) for identifying a first account, and then enables the electronic device to participate in transactions using the first account via one or more wireless communication elements. The electronic device displays a second visual indicator (e.g., 620) on the display for identifying a second account, and then enables the electronic device to participate in transactions using the second account via one or more wireless communication elements.
[0292] According to some embodiments, one of the first account and the second account is a payment account, and one of the first account and the second account is a loyalty account (e.g., the first account is a payment account, and the second account is a loyalty account). The first visual indicator of the first account (e.g., 602) has a first dimensional feature (e.g., size or aspect ratio), and the second visual indicator of the second account (e.g., 620) has a second dimensional feature different from the first dimensional feature (e.g., a different size or a different aspect ratio).
[0293] According to some embodiments, the electronic wallet of the electronic device includes payment account information of multiple payment accounts associated with the user of the electronic device (e.g., including payment accounts associated with 602 and 610).
[0294] It should be noted that the process described above with reference to method 700 (eg Figure 7 ) also apply in a similar manner to the methods described below. For example, methods 900, 1100, 1300, 1500, 1700, and 1900 may include one or more features of the various methods described above with reference to method 700. For example, the electronic wallets, payment accounts, loyalty accounts, affordances, and inputs of methods 900, 1100, 1300, 1500, 1700, and 1900 optionally have one or more features of the electronic device, payment account, loyalty account, affordances, and inputs of the electronic device described in method 700. For the sake of brevity, these details are not repeated below.
[0295] Figures 8A-8DExemplary techniques and exemplary user interfaces for selecting an account to be displayed, such as a loyalty account or a payment account, are shown according to some embodiments. For example, account information for the selected account can then be transmitted to an NFC-enabled payment terminal for use in a transaction (e.g., when the device is placed in the field of the payment terminal). The techniques can be performed at an electronic device having a display and a position sensor. The user interfaces in these figures are used to illustrate the processes described below, including Fig. 9 process.
[0296] Some accounts, such as private label accounts or loyalty accounts, may be associated with specific locations (e.g., specific merchants or specific stores of merchants). When at these locations, users may prefer to use the associated private label accounts or loyalty accounts in transactions. For example, if the user is located at a Joe's Electronics store, the user may prefer to use a private label account (e.g., a private label credit card account) associated with the Joe's Electronics store. As another example, if the user is located at a supermarket, the user may prefer to use a loyalty account associated with the supermarket during a transaction in which the user pays using a default payment account. Therefore, displaying a visual indication of an account relevant to the current situation (e.g., location) on the display of an electronic device brings value to the user.
[0297] For example, a payment account may be associated with multiple locations (e.g., multiple stores in a chain). Additionally, different locations may be associated with different payment accounts (e.g., a user has a Joe's Electronics credit card and a Jack's Home Improvement Store credit card, and the Joe's Electronics credit card may be associated with the Joe's Electronics store, while the Jack's Home Improvement Store card is associated with the Jack's Home Improvement Store).
[0298] Now go to Fig. 8A The electronic device detects a current location using a location sensor (e.g., the electronic device determines that the device is physically located at a specific retailer or at a specific store of a specific retailer). The electronic device determines whether the current location is associated with a first account (e.g., determining that a specific private label payment account or a specific loyalty account is associated with a retailer).
[0299] like Fig. 8AAs shown, based on a failure to determine (e.g., during the time between receiving a request to prepare a default payment account and preparing the default payment account) that the current location is associated with an account other than the default payment account (e.g., the device determines that the location of the device is not associated with the current location, or the device fails to determine the location of the device), the electronic device displays a visual indication 802 of the default payment account on the display (e.g., a visual depiction of a credit card associated with the default payment account). In some embodiments, the visual indication 802 of the default payment account is displayed without displaying graphical indicators for other accounts. Fig. 8A At 804 , ready indication 804 is a visual indication that the device is ready to engage in a transaction using the default account represented by visual indicator 802 .
[0300] The visual indication 802 of the default payment account includes: the name of the first financial institution associated with the default payment account, "AA Bank", a first background design that corresponds to the background design of the payment card associated with the default payment account, at least a portion of the account number associated with the default payment account, and an expiration date associated with the default payment account.
[0301] like Figure 8B As shown, based on determining that the current location is associated with the first account, the electronic device simultaneously displays on the display a visual indication 802 of a default payment account (e.g., a visual depiction of a credit card associated with the default payment account) and a visual indication 806 of the first account (e.g., a visual depiction of a private label card or a specific loyalty account associated with a specific payment account). The default payment account and the first account are linked to the electronic device (e.g., stored in an electronic wallet of the device; the electronic device has been configured for both accounts), and the default payment account and the first account are different accounts. Figure 8B At 804 , ready indication 804 is a visual indication that the device is ready to engage in a transaction using either (or both) the default account represented by visual indicator 802 and the first account represented by visual indicator 806 .
[0302] The visual indication 806 of the first account may include: the name of the merchant or financial institution associated with the first account (e.g., "SHOPCO"), a first background design that corresponds to the first account, at least a portion of the account number associated with the first account, and an expiration date associated with the first account.
[0303] For example, a payment account (e.g., a first account) may be associated with multiple locations (e.g., multiple stores in a chain). In addition, different locations may be associated with different payment accounts (e.g., a user has a Joe's Electronics credit card and a Jack's Home Improvement Store credit card. The Joe's Electronics credit card may be associated with the Joe's Electronics store, and the Jack's Home Improvement Store card may be associated with the Jack's Home Improvement Store).
[0304] According to some embodiments, Figure 8B 802, the first account is a payment account. In some embodiments, the first account is a private brand account, and the visual indication 806 of the first account is an image of a payment card associated with the private brand account. In some embodiments, the visual indication 806 of the first account is partially displayed behind the visual indication 802 of the default account.
[0305] According to some embodiments, Figure 8C 802. As shown, the first account is a loyalty account. In some embodiments, the first account is a loyalty account, and the visual indication 808 is an image of a loyalty card associated with the loyalty account. In some embodiments, the visual indication 808 of the first account is partially displayed behind the visual indication 802 of the default account.
[0306] According to some embodiments, Fig.8D As shown, the electronic device receives a request associated with a payment transaction from a contactless payment terminal 820 (e.g., when the device is located in the NFC field of the contactless payment terminal 820). The electronic device determines whether the request includes a request for payment account information of a first account type corresponding to a first account (e.g., when the device is placed in the field of the terminal, the NFC-enabled terminal requests a private-label credit card of a specific retailer). Based on determining that the current location is associated with the first account and based on determining that the request includes a request for payment information of the first account type, the electronic device uses one or more wireless communication elements to transmit the payment account information of the first account to the contactless payment terminal, wherein the payment account information of the first account enables the contactless payment terminal to participate in the payment transaction. In some embodiments, participating in the payment transaction includes routing information to one or more financial institutions to verify payment credentials and / or receive authorization to complete the transaction. For example, NFC is used to transmit payment account information to a contactless payment terminal. In some embodiments, participating in the payment transaction includes routing loyalty information to one or more servers for confirmation / authorization of loyalty accounts.
[0307] According to some embodiments, an electronic device receives a request associated with a payment transaction from a contactless payment terminal. The electronic device determines that the request includes a request for payment account information of a first account type corresponding to a first account (e.g., when the device is placed in the field of the terminal, an NFC-enabled terminal requests a private-label credit card of a specific retailer). Based on the failure to determine that the current location is associated with an account other than a default payment account (and based on determining that the request includes a request for payment account information of a first account type), the electronic device uses one or more wireless communication elements to transmit the payment account information of the default payment account to the contactless payment terminal, wherein the payment account information of the default payment account enables the contactless payment terminal to participate in the payment transaction. In some embodiments, participating in the payment transaction includes routing information to one or more financial institutions to verify payment credentials and / or receive authorization to complete the transaction. For example, NFC is used to transmit payment account information to a contactless payment terminal.
[0308] According to some embodiments, the visual indication of the first account is displayed on the visual indication of the default account 802, and wherein the visual indication of the first account indicates that the first account is enabled to be selected by the device for payment transactions without additional user input. For example, the visual indication of the first account is simply text written on the card image of the default account, and the device determines which payment account to use (at the time of payment) without user intervention.
[0309] According to some embodiments, before using the location sensor to detect the current location, the electronic device receives input (e.g., user input) for requesting to enable the device for payment transactions (e.g., the user double-clicks the device's hardware button 508 to prepare the device for NFC payments and / or access to an electronic wallet). In some examples, in response to receiving user input requesting to enable the device for payment transactions, the device is enabled to participate in the transaction (e.g., preparing the device for NFC payments using a default payment account).
[0310] According to some embodiments, detecting the current location using a location sensor is performed in response to receiving input requesting that the device be enabled to conduct a payment transaction.
[0311] According to some embodiments, determining whether the current location is associated with the first account is performed in response to receiving input requesting that the device be enabled for a payment transaction (e.g., a user double-clicking the device's hardware button 508 to prepare the device for an NFC payment and / or access to an electronic wallet). In some examples, in response to receiving user input requesting that the device be enabled for a payment transaction, the device is enabled to participate in the transaction (e.g., preparing the device for an NFC payment using a default payment account).
[0312] According to some embodiments, failure to determine that the current location is associated with an account other than a default payment account occurs when the device fails to determine that the current location is associated with a first account before enabling the electronic device to participate in a transaction using the default payment account via one or more wireless communication elements (e.g., determining whether the current location is associated with the first account takes longer than enabling the electronic device to participate in a transaction using the default payment account via one or more wireless communication elements). Or optionally, when the device detects that a user of the electronic device is still viewing the electronic device or the electronic device is still facing the user, the electronic device simultaneously displays a visual indication of the default payment account and a visual indication of the first account on a display. For example, (1) while the user is still viewing the device or (2) while the device is still facing the user, the user is provided with an opportunity to view the change and recognize that a different payment account can be used in a payment transaction by changing only the visual indication of the account on the display.
[0313] In some embodiments, if the electronic device is worn on the user's wrist, the electronic device can detect that the user is viewing the electronic device by detecting that the user raises or turns their wrist (e.g., a raise gesture) to move the electronic device into a viewing position. The electronic device can detect that the user is no longer viewing the device by detecting that the user lowers their wrist. As used herein, a viewing position is a position of the electronic device where the user can view the display of the electronic device. In some embodiments, the electronic device can detect a signal indicating that the user raises or lowers their wrist, as described in U.S. Provisional Patent Application Serial No. 62 / 026,532, "Raise Gesture Detection in a Device," which is incorporated herein by reference in its entirety.
[0314] In some embodiments, the raise gesture detection algorithm may progress through a series of states of increasing confidence that a raise gesture has been performed. For example, the raise gesture detection algorithm may select a set of motion sensor data samples (including accelerometer and / or gyro sensor data) corresponding to a time interval of interest (e.g., the amount of time a user may need to perform a raise gesture). By considering the oldest samples in the set, the algorithm may define a "starting pose," which may reflect the spatial orientation of the device at the beginning of the time interval. The orientation may be defined relative to an assumed vertical axis of gravity. Based on the starting pose, the algorithm may determine the amount and / or direction of movement that may occur to bring the device's display into the user's line of sight (also referred to as bringing the device into a "focus pose"). The possible amount and / or direction of movement may be expressed as criteria for identifying a "possible" raise gesture, and these criteria may be used to identify whether a possible raise gesture has occurred based on some or all of the motion sensor data samples in the set. A possible raise gesture may be further identified as a "detected" raise gesture by determining whether a device that has reached a focus pose maintains the focus pose for at least a minimum period of time. If necessary, further confirmation may be performed using a gesture classifier. The raise gesture detection algorithm can notify other components of the device each time it identifies a possible, detected, and / or confirmed raise gesture.
[0315] According to some embodiments, an electronic device receives a request for loyalty account information from a contactless payment terminal, wherein a first account is a loyalty account. In response to receiving the request for loyalty account information, based on a failure to determine that the current location is associated with an account other than a default payment account (e.g., during the time between receiving a request to prepare an account and preparing the account), and based on a subsequent determination that the current location is associated with the first account: the electronic device transmits account information of the first account to the contactless payment terminal via one or more wireless communication elements, and the electronic device transmits payment account information of the default payment account to the contactless payment terminal via one or more wireless communication elements. In some embodiments, the account information of the first account is provided without regard to whether a representation of the first account is displayed on a display prior to participating in a payment transaction. In some embodiments, the account information of the first account is provided only when a representation of the first account is displayed on a display prior to participating in a payment transaction.
[0316] According to some embodiments, an electronic device receives a request associated with a payment transaction from a contactless payment terminal. The electronic device determines that the request includes a request for payment account information using a first account type corresponding to a first account, wherein the first account is a payment account different from a default payment account (e.g., when the device is placed in the field of the terminal, the NFC-enabled terminal requests a private-label credit card for a specific retailer). In response to receiving a request for account information, based on a failure to determine that the current location is associated with an account other than the default payment account (e.g., during the time between receiving a request to prepare the account and preparing the account), and based on a subsequent determination that the current location is associated with the first account: the electronic device abandons transmitting the account information of the first account to the contactless payment terminal via one or more wireless communication elements, and the electronic device transmits the payment account information of the default payment account to the contactless payment terminal via one or more wireless communication elements. In some embodiments, the account information of the first account is provided only when a representation of the first account is displayed on the display before engaging in a payment transaction.
[0317] According to some embodiments, an electronic device receives a request associated with a payment transaction from a contactless payment terminal. Prior to receiving the request associated with a payment transaction from a contactless payment terminal, a visual indication of a default payment account (e.g., a visual depiction of a credit card associated with the default payment account) and a visual indication of a first account (e.g., a visual depiction of a private-label card or a specific loyalty account associated with a specific payment account) are simultaneously displayed on a display. The request includes a request for payment account information of a first account type corresponding to the first account (e.g., when the device is placed in the field of the terminal, the NFC-enabled terminal requests a private-label credit card of a specific retailer). The first account is a payment account of the first account type. In response to receiving a request for account information and based on failing to determine that the current location is associated with an account other than the default payment account (e.g., during the time between receiving a request to prepare the account and preparing the account), and based on subsequently determining that the current location is associated with the first account: the electronic device abandons transmitting the account information of the default payment account to the contactless payment terminal via one or more wireless communication elements, and the electronic device transmits the payment account information of the first account to the contactless payment terminal via one or more wireless communication elements.
[0318] According to some embodiments, based on determining that the current location is associated with the first account, the electronic device receives a failed communication from the contactless payment terminal via one or more wireless communication elements (e.g., payment was rejected because the payment account was frozen by the bank or there was no funds). In response to receiving the failed communication, the electronic device transmits account information of the default payment account to the contactless payment terminal via one or more wireless communication elements (e.g., using the default card payment as an alternative). In some embodiments, the device simultaneously displays an indication of the default payment account and another payment account to indicate to the user that either payment account can be used for payment transactions.
[0319] According to some embodiments, displaying the visual indication of the default payment account and the visual indication of the first account on the display simultaneously includes displaying the visual indication of the default payment account superimposed on the visual indication of the first account (e.g., above or below the visual indication of the first account) on the display simultaneously. In some embodiments, the visual indication of the first account is at least partially obscured by the visual indication of the default payment account.
[0320] Fig. 9 1 is a flow chart showing a method 900 for selecting an account to be displayed, such as a loyalty account or a payment account, according to some embodiments. The method 900 is performed at a device (e.g., 100, 300, 500) having a display and a position sensor. Some operations in the method 900 may be combined, the order of some operations may be changed, and some operations may be omitted.
[0321] As described below, method 900 provides an intuitive way to select an account to be displayed, such as a loyalty account or a payment account. The method reduces the cognitive burden on the user when selecting an account, thereby creating a more efficient human-computer interface. For battery-powered computing devices, enabling users to select accounts faster and more efficiently saves power and increases the time between battery charges.
[0322] At block 902, the electronic device detects a current location using a location sensor. At block 904, the electronic device determines whether the current location is associated with a first account.
[0323] At box 904, based on failing to determine that the current location is associated with an account other than the default payment account, the electronic device displays a visual indication of the default payment account on the display (e.g., 802).
[0324] At block 906, based on determining that the current location is associated with the first account, the electronic device simultaneously displays on the display a visual indication of the default payment account (e.g., 802) and a visual indication of the first account (e.g., Figure 8B of 806; Figure 8C808). The default payment account and the first account are linked to the electronic device, and the default payment account and the first account are different.
[0325] According to some embodiments, the first account is a payment account. In some embodiments, the first account is a private label account, and the visual indication of the first account (e.g., 806) is an image of a payment card associated with the private label account. In some embodiments, the visual indication of the first account (e.g., 806) is partially displayed behind the visual indication of the default account (e.g., 802).
[0326] According to some embodiments, the first account is a loyalty account. In some embodiments, the first account is a loyalty account, and the visual indication (e.g., 808) is an image of a loyalty card associated with the loyalty account. In some embodiments, the visual indication (e.g., 808) of the first account is partially displayed behind the visual indication of the default account.
[0327] According to some embodiments, the electronic device receives a request associated with a payment transaction from a contactless payment terminal (e.g., when the device is located in the NFC field of the contactless payment terminal 820). The electronic device determines whether the request includes a request for payment account information of a first account type corresponding to the first account. Based on determining that the current location is associated with the first account and based on determining that the request includes a request for payment information of the first account type, the electronic device uses one or more wireless communication elements to transmit the payment account information of the first account to the contactless payment terminal, wherein the payment account information of the first account enables the contactless payment terminal to participate in the payment transaction. In some embodiments, participating in the payment transaction includes routing information to one or more financial institutions to verify payment credentials and / or receive authorization to complete the transaction. For example, NFC is used to transmit payment account information to a contactless payment terminal. In some embodiments, participating in the payment transaction includes routing loyalty information to one or more servers for confirmation / authorization of loyalty accounts.
[0328] According to some embodiments, an electronic device receives a request associated with a payment transaction from a contactless payment terminal. The electronic device determines that the request includes a request for payment account information of a first account type corresponding to a first account. Based on a failure to determine that the current location is associated with an account other than a default payment account (and based on determining that the request includes a request for payment account information of the first account type), the electronic device transmits payment account information of the default payment account to the contactless payment terminal using one or more wireless communication elements, wherein the payment account information of the default payment account enables the contactless payment terminal to participate in the payment transaction. In some embodiments, participating in the payment transaction includes routing information to one or more financial institutions to verify payment credentials and / or receive authorization to complete the transaction.
[0329] In some embodiments, the visual indication of the first account is displayed over the visual indication of the default account (e.g., 802), and wherein the visual indication of the first account indicates that the first account is enabled for selection by the device for payment transactions without additional user input.
[0330] In some embodiments, prior to using a location sensor to detect a current location, the electronic device receives input (e.g., user input) requesting that the device be enabled to conduct a payment transaction.
[0331] According to some embodiments, detecting the current location using a location sensor is performed in response to receiving input requesting that the device be enabled to conduct a payment transaction.
[0332] In some embodiments, determining whether the current location is associated with the first account is performed in response to receiving input requesting to enable the device to perform a payment transaction (e.g., a user double-clicks the device's hardware button 508 to prepare the device for NFC payments and / or access to an electronic wallet).
[0333] According to some embodiments, failure to determine that the current location is associated with an account other than a default payment account occurs when the device fails to determine that the current location is associated with a first account before enabling the electronic device to engage in a transaction using a default payment account via one or more wireless communication elements.
[0334] In some embodiments, if the electronic device is worn on the user's wrist, the electronic device can detect that the user is viewing the electronic device by detecting that the user has raised or turned their wrist to move the electronic device into a viewing position. The electronic device can detect that the user is no longer viewing the device by detecting that the user has lowered their wrist. As used herein, a viewing position is a position of the electronic device where the user can view a display of the electronic device.
[0335] According to some embodiments, an electronic device receives a request for loyalty account information from a contactless payment terminal, wherein a first account is a loyalty account. In response to receiving the request for loyalty account information, based on a failure to determine that the current location is associated with an account other than a default payment account (e.g., during the time between receiving a request to prepare an account and preparing the account), and based on a subsequent determination that the current location is associated with the first account: the electronic device transmits account information of the first account to the contactless payment terminal via one or more wireless communication elements, and the electronic device transmits payment account information of the default payment account to the contactless payment terminal via one or more wireless communication elements. In some embodiments, the account information of the first account is provided without regard to whether a representation of the first account is displayed on a display prior to participating in a payment transaction. In some embodiments, the account information of the first account is provided only when a representation of the first account is displayed on a display prior to participating in a payment transaction.
[0336] According to some embodiments, an electronic device receives a request associated with a payment transaction from a contactless payment terminal. The electronic device determines that the request includes a request for payment account information using a first account type corresponding to a first account, wherein the first account is a payment account different from a default payment account. In response to receiving the request for account information, based on a failure to determine that the current location is associated with an account other than the default payment account (e.g., during the time between receiving a request to prepare the account and preparing the account), and based on a subsequent determination that the current location is associated with the first account: the electronic device abandons transmitting the account information of the first account to the contactless payment terminal via one or more wireless communication elements, and the electronic device transmits the payment account information of the default payment account to the contactless payment terminal via one or more wireless communication elements. In some embodiments, the account information of the first account is provided only when a representation of the first account is displayed on the display before engaging in a payment transaction.
[0337] According to some embodiments, an electronic device receives a request associated with a payment transaction from a contactless payment terminal. Before receiving a request associated with a payment transaction from a contactless payment terminal, a visual indication of a default payment account (e.g., 802) and a visual indication of a first account (e.g., 806 or 808) are simultaneously displayed on a display. The request includes a request for payment account information of a first account type corresponding to the first account (e.g., when the device is placed in the field of the terminal, an NFC-enabled terminal requests a private-label credit card of a specific retailer). The first account is a payment account of the first account type. In response to receiving a request for account information and according to failing to determine that the current location is associated with an account other than the default payment account (e.g., during the time between receiving a request to prepare the account and preparing the account), and according to subsequently determining that the current location is associated with the first account: the electronic device abandons transmitting the account information of the default payment account to the contactless payment terminal via one or more wireless communication elements, and the electronic device transmits the payment account information of the first account to the contactless payment terminal via one or more wireless communication elements.
[0338] According to some embodiments, based on determining that the current location is associated with the first account, the electronic device receives a failed communication from the contactless payment terminal via one or more wireless communication elements (e.g., payment was rejected because the payment account was frozen by the bank or there was no funds). In response to receiving the failed communication, the electronic device transmits account information of the default payment account to the contactless payment terminal via one or more wireless communication elements (e.g., using the default card payment as an alternative). In some embodiments, the device simultaneously displays an indication of the default payment account and another payment account to indicate to the user that either payment account can be used for payment transactions.
[0339] According to some embodiments, simultaneously displaying the visual indication of the default payment account and the visual indication of the first account on the display includes simultaneously displaying the visual indication of the default payment account (e.g., 802) superimposed with the visual indication of the first account (e.g., 806, 808) on the display (e.g., above or below the visual indication of the first account). In some embodiments, the visual indication of the first account (e.g., 806, 808) is at least partially obscured by the visual indication of the default payment account (e.g., 802).
[0340] It should be noted that the process described above with reference to method 900 (eg Fig. 9) also apply in a similar manner to the methods described above and below. For example, methods 700, 1100, 1300, 1500, 1700, and 1900 may include one or more features of the various methods described above with reference to method 900. For example, the electronic wallets, payment accounts, loyalty accounts, affordances, and inputs of methods 700, 1100, 1300, 1500, 1700, and 1900 optionally have one or more features of the electronic device, payment account, loyalty account, affordances, and inputs of the electronic device described in method 900. For the sake of brevity, these details are not repeated below.
[0341] Figures 10A-10E Exemplary techniques and exemplary user interfaces for selecting an account to be displayed from a plurality of accounts in an electronic wallet, such as a loyalty account or a payment account, are shown according to some embodiments. For example, the account information of the selected account can then be transmitted to an NFC-enabled payment terminal for use in a transaction (e.g., when the device is placed in the field of the payment terminal). The technology is performed at an electronic device having a display, a position sensor, and one or more wireless communication elements. The user interfaces in these figures are used to illustrate the processes described below, which include Fig.11 process.
[0342] The electronic device receives input (eg, user input) requesting that the device be enabled for a payment transaction (eg, a user double-clicks a hardware button 508 of the device to prepare the device for an NFC payment).
[0343] In response to receiving the input, the electronic device detects the current location using the location sensor (e.g., determining that the device is physically located at a particular retailer or at a particular store of a particular retailer). The electronic device also determines whether a set of one or more payment criteria has been satisfied, wherein the set of one or more payment criteria includes criteria that are satisfied when the current location is associated with a first payment account (e.g., determining that a particular private label payment account is associated with a retailer).
[0344] like Fig. 10A As shown, based on determining that a set of one or more payment criteria are not met, the electronic device displays a visual indication 1002 of a default payment account on a display, wherein the default payment account is different from the first payment account (e.g., a visual depiction 1002 of a credit card associated with the default payment account, and forgoing displaying an indication of the first payment account).
[0345] The device may also display on the display an indication 1006 that other accounts are also available, or an indication 1006 of the number of other available accounts. In this example, the indication 1006 includes four paging dots. The first paging dot has a first color that is different from the second color of the second, third, and fourth paging dots. The four paging dots indicate that a total of four accounts are available. The first paging dot is a different color from the other paging dots, indicating that the device is currently displaying information corresponding to the default payment account (e.g., visual indication 1002).
[0346] The device may also display a ready indication 1004 on the display. Ready indication 1004 is a visual indication that the device is enabled to participate in a transaction using the default payment account represented by visual indication 1002. Visual indication 1002 may include: the name of the financial institution associated with the default payment account, "AA Bank", a background design that corresponds to the background design of the payment card associated with the default payment account, at least a portion of the account number associated with the default payment account, and an expiration date associated with the default payment account.
[0347] like Fig. 10B As shown, based on determining that a set of one or more payment criteria are met, the electronic device displays a visual indication 1008 of the first payment account on the display (and forgoes displaying an indication of the default payment account).
[0348] The device may also display a ready indication 1010 on the display. The ready indication 1010 is a visual indication that the device is enabled to participate in a transaction using the first payment account represented by the visual indication 1008. The visual indication 1008 may include: the name of the merchant associated with the first payment account, "SHOPCO", a background design that corresponds to the background design of the private label card associated with the first payment account, at least a portion of the account number associated with the first payment account, and an expiration date associated with the first payment account.
[0349] According to some embodiments, based on determining that a set of one or more payment criteria are met, the electronic device enables the electronic device to participate in the transaction via one or more wireless communication element accounts using the first payment. In addition, the electronic device may abandon enabling the electronic device to participate in the transaction using a default payment account.
[0350] According to some embodiments, based on determining that a set of one or more payment criteria is not met, the electronic device enables the electronic device to participate in the transaction via one or more wireless communication elements using a default payment account. In addition, the electronic device may abandon enabling the electronic device to participate in the transaction using the first payment account.
[0351] In some embodiments, based on determining that a set of one or more payment criteria are not met, the electronic device forgoes displaying a visual indication of the first payment account on the display (e.g., displays a visual indication of a default payment account instead of displaying a visual indication of the first payment account).
[0352] According to some embodiments, the electronic device includes a touch-sensitive surface. Fig. 10C As shown, the electronic device receives one or more inputs in a first direction (e.g., receiving one or more swipes to the left or right via the touch-sensitive surface, or detecting a change in the orientation of the device in the first direction). Fig. 10D As shown, in response to receiving one or more inputs: the electronic device displays on the display a second visual indicator 1012 for identifying (e.g., being able to identify) a second account different from the first payment account and the default payment account. The electronic device enables the electronic device to participate in transactions using the second account via one or more wireless communication elements (e.g., prepares the device for NFC transactions using the second account, and prohibits the device from participating in transactions using the first account). Therefore, when the device presents a payment account, the user can provide input to change to a payment account (e.g., select a payment account from a plurality of payment accounts in the device's electronic wallet).
[0353] According to some embodiments, an electronic device receives a request for account information from a contactless payment terminal (e.g., when the device detects that a user has placed the device in the field of an NFC-enabled contactless payment terminal). In response to receiving the request for account information, the electronic device transmits account information of a corresponding enabled account to the contactless payment terminal via one or more wireless communication elements (e.g., any one account for which the device is enabled to participate in a payment transaction; any one account currently displayed), wherein the account information enables the contactless payment terminal to participate in the payment transaction. In some embodiments, participating in a payment transaction includes routing information to one or more financial institutions to verify payment credentials and / or receive authorization to complete the transaction (e.g., if the account information of the payment account is transmitted to the terminal). For example, the payment account information is transmitted to the contactless payment terminal using NFC. In some embodiments, participating in a payment transaction includes routing loyalty information to one or more servers for confirmation / authorization of a loyalty account (e.g., if the account information of the loyalty account is transmitted to the terminal).
[0354] In some embodiments, the set of one or more criteria includes criteria that are met when the device is authorized to use (e.g., without user confirmation) a first payment account (e.g., to override a default payment account) to conduct a transaction at the current location.
[0355] According to some embodiments, the electronic device determines that the current location is associated with a loyalty account. The electronic device simultaneously displays a visual indication of the loyalty account on the display, together with a corresponding visual indication of the payment account (e.g., together with a visual indication of a default payment account or a first payment account). Thus, if the availability of an appropriate loyalty card is detected, the device displays an indication of the default payment card (or private label card) together with an indication of the loyalty card.
[0356] According to some embodiments, the electronic device includes one or more input devices. Prior to receiving user input requesting to enable the device for payment transactions: the electronic device receives a request to link a payment account with the electronic device (e.g., manually input, imported from a server, or input using a camera sensor of the electronic device). The request includes account information of the payment account (e.g., card number, card expiration date, name on the card). The electronic device links the payment account with the electronic device; (e.g., adds the payment account to an electronic wallet of the electronic device). The electronic device determines that a financial institution associated with the payment account has authorized the payment account for location-based selections without user input. The electronic device receives user input, thereby activating the payment account for location-based selections without user input, such as Fig.10E shown.
[0357] like Fig.10E As shown, the user can activate the payment account to be used for location-based selection by activating the "yes" enable indication 1030. Alternatively, the user can give up activating the payment account for location-based selection by activating the "no" enable indication 1032. In some embodiments, the option to activate the payment account for location-based selection is displayed during card setup (e.g., during or just after the card is linked to the electronic device). Alternatively (or in addition), at some time after the payment account has been linked to the electronic device, the financial institution may authorize the payment account for location-based selection (without user input). In this case, a new option may appear in the settings menu of the payment account. Similarly, when the device detects that a payment has been made, the device may display a pop-up notification. The notification indicates that the payment account is now capable of location-based selection. Subsequently, the user can choose to activate (or not activate) the feature for location-based selection without user input.
[0358] According to some embodiments, based on determining that a set of one or more payment criteria are met, the electronic device enables the electronic device to participate in a transaction via one or more wireless communication element accounts using a first payment. The electronic device receives a request associated with a payment transaction from a contactless payment terminal. The electronic device determines whether the request includes a request for payment account information of an account type corresponding to a second payment account different from the first payment account (for example, when the device is placed in the field of the terminal, the NFC-enabled terminal requests a private-label credit card for a specific retailer). Based on determining that the request includes a request for payment information using a second account type, the electronic device provides a notification (for example, a visual notification, an audio notification, or a tactile notification) requesting authorization to transmit the payment account information of the second account to the contactless payment terminal using one or more wireless communication elements, wherein the payment account information of the second account enables the contactless payment terminal to participate in the payment transaction. Therefore, when the device determines that the first payment account is applicable to a specific location, but the contactless payment terminal requests payment using a different payment account, the user receives a notification and is requested to provide authorization to continue the payment transaction using the second payment account.
[0359] Fig.11 1 is a flow chart showing a method 1100 for selecting an account to be displayed from a plurality of accounts in an electronic wallet, such as a loyalty account or a payment account, according to some embodiments. The method 1100 is performed at a device (e.g., 100, 300, 500) having a display and a position sensor. Some operations in the method 1100 may be combined, the order of some operations may be changed, and some operations may be omitted.
[0360] As described below, method 1100 provides an intuitive way to select an account. The method reduces the cognitive burden on the user to select an account to be displayed and / or paid, thereby creating a more efficient human-computer interface. For battery-powered computing devices, enabling users to select accounts faster and more efficiently saves power and increases the time between battery charges.
[0361] At box 1102, the electronic device receives input (e.g., user input) requesting that the device be enabled for payment transactions (e.g., the user performs a double-click on the device's hardware button 508 to prepare the device for NFC payments).
[0362] At block 1104, in response to receiving the input, the technique proceeds to block 1106. At block 1106, the electronic device detects a current location using a location sensor (eg, determines that the device is physically located at a particular retailer or at a particular store of a particular retailer).
[0363] At box 1108, the electronic device determines whether a set of one or more payment criteria have been satisfied, wherein the set of one or more payment criteria includes criteria that are satisfied when the current location is associated with the first payment account (e.g., determining that a particular private label payment account is associated with a retailer).
[0364] At box 1110, based on determining that the set of one or more payment criteria are not met, the electronic device displays a visual indication of a default payment account on a display (e.g., 1002), where the default payment account is different from the first payment account (e.g., a visual depiction of a credit card associated with the default payment account, and forgoing displaying an indication of a particular payment account).
[0365] In accordance with some embodiments, at box 1112, based on determining that the set of one or more payment criteria are not met, the electronic device enables the electronic device to participate in the transaction using a default payment account via one or more wireless communication elements.
[0366] In box 1114, based on determining that the set of one or more payment criteria is satisfied, the electronic device displays a visual indication of the first payment account on the display (e.g., 1008) (and forgoes displaying an indication of the default payment account).
[0367] In accordance with some embodiments, at box 1116, based on determining that a set of one or more payment criteria are satisfied, the electronic device enables the electronic device to participate in the transaction via one or more wireless communication element accounts using the first payment.
[0368] In some embodiments, based on determining that a set of one or more payment criteria are not met, the electronic device abandons displaying a visual indication of the first payment account on the display (e.g., 1008) (e.g., displaying a visual indication of a default payment account without displaying a visual indication of the first payment account).
[0369] According to some embodiments, the electronic device includes a touch-sensitive surface. The electronic device receives one or more inputs in a first direction (e.g., receiving one or more swipes to the left or right via the touch-sensitive surface, or detecting a change in the device orientation in the first direction). In response to receiving the one or more inputs, the electronic device displays a second visual indicator (e.g., 1012) on the display for identifying a second account different from the first payment account and the default payment account, and the electronic device enables the electronic device to participate in transactions using the second account via one or more wireless communication elements (e.g., preparing the device for NFC transactions using the second account, and prohibiting the device from participating in transactions using the first account).
[0370] According to some embodiments, the electronic device receives a request for account information from a contactless payment terminal. In response to receiving the request for account information, the electronic device transmits account information of a corresponding enabled account to the contactless payment terminal via one or more wireless communication elements, wherein the account information enables the contactless payment terminal to participate in the payment transaction. In some embodiments, participating in the payment transaction includes routing information to one or more financial institutions to verify payment credentials and / or receive authorization to complete the transaction (e.g., if the account information of the payment account is transmitted to the terminal).
[0371] In some embodiments, the set of one or more criteria includes criteria that are met when the device is authorized to use (e.g., without user confirmation) a first payment account (e.g., to override a default payment account) to conduct a transaction at the current location.
[0372] According to some embodiments, the electronic device determines that the current location is associated with a loyalty account. The electronic device simultaneously displays a visual indication of the loyalty account on the display, together with a corresponding visual indication of the payment account (e.g., together with a visual indication of a default payment account or a first payment account). Thus, if the availability of an appropriate loyalty card is detected, the device displays an indication of the default payment card (or private label card) together with an indication of the loyalty card.
[0373] According to some embodiments, the electronic device includes one or more input devices. Before receiving user input for requesting to enable the device for payment transactions: the electronic device receives a request to link the payment account with the electronic device (e.g., manually input, imported from a server, or input using a camera sensor of the electronic device). The request includes account information of the payment account (e.g., card number, card expiration date, name on the card). The electronic device links the payment account with the electronic device; (e.g., adding the payment account to the electronic wallet of the electronic device). The electronic device determines that the financial institution associated with the payment account has authorized the payment account for location-based selection without user input. The electronic device receives user input, thereby activating the payment account for location-based selection without user input.
[0374] According to some embodiments, based on determining that a set of one or more payment criteria are met, the electronic device enables the electronic device to participate in a transaction via one or more wireless communication element accounts using a first payment. The electronic device receives a request associated with a payment transaction from a contactless payment terminal. The electronic device determines whether the request includes a request for payment account information of an account type corresponding to a second payment account different from the first payment account (for example, when the device is placed in the field of the terminal, the NFC-enabled terminal requests a private-label credit card of a specific retailer). Based on determining that the request includes a request for payment information using a second account type, the electronic device provides a notification (for example, a visual notification, an audio notification, or a tactile notification) that requests authorization to transmit the payment account information of the second account to the contactless payment terminal using one or more wireless communication elements, wherein the payment account information of the second account enables the contactless payment terminal to participate in the payment transaction. Therefore, when the device determines that the first payment account is applicable to a specific location, but the contactless payment terminal requests payment using a different payment account, the user receives a notification and is requested to provide authorization to continue the payment transaction using the second payment account.
[0375] It should be noted that the above reference to method 1100 (eg, Fig.11 ) also apply in a similar manner to the methods described above and below. For example, methods 700, 900, 1300, 1500, 1700, and 1900 may include one or more features of the various methods described above with reference to method 1100. For example, the electronic wallets, payment accounts, loyalty accounts, affordances, and inputs of methods 700, 900, 1300, 1500, 1700, and 1900 optionally have one or more features of the electronic device, payment account, loyalty account, affordances, and inputs of the electronic device described in method 1100. For the sake of brevity, these details are not repeated below.
[0376] Figures 12A-12D Exemplary techniques and exemplary user interfaces for transmitting account information of an account selected from a plurality of accounts in an electronic wallet according to some embodiments are shown. The techniques are performed at an electronic device having a display and one or more wireless communication elements (e.g., one or more wireless antennas, such as NFC antennas, WiFi antennas). The user interfaces in these figures are used to illustrate the processes described below, including Fig.13 process.
[0377] The electronic device receives input (e.g., user input) requesting that the device be enabled for a payment transaction (e.g., a user double-clicking a hardware button of the device to prepare the device for an NFC payment). Fig. 12AAt, in response to receiving the input, the electronic device displays on a display a payment indication (e.g., 1202) representing multiple payment accounts including a first payment account and a second payment account (e.g., displaying a "smart selection" indication that does not identify a specific payment account).
[0378] like Fig. 12B As shown, the user places electronic device 500 in the NFC field of contactless payment terminal 1220. The electronic device receives a request for account information corresponding to a payment transaction (eg, received from contactless payment terminal 1220) via one or more wireless communication elements.
[0379] In response to receiving a request for account information corresponding to a payment transaction, based on determining that payment criteria for a first payment account have been met (e.g., the first payment account is associated with the current location of the device), the electronic device transmits account information for the first payment account via one or more wireless communication elements without transmitting account information for a second payment account (and, optionally, without transmitting payment account information for any other payment account associated with the payment instruction other than the first payment account). In response to receiving a request for account information corresponding to a payment transaction, based on determining that payment criteria for a second payment account have been met (e.g., the second payment account is associated with the current location of the device), the electronic device transmits account information for the second payment account via one or more wireless communication elements without transmitting account information for the first payment account (and, optionally, without transmitting payment account information for any other payment account associated with the payment instruction other than the second payment account). Thus, the user may see a visual indication that the “smart select” feature is selected. When the device detects an attempt to make a payment, the electronic device transmits account information for the appropriate account.
[0380] According to some embodiments, the electronic device is configured to enable payment using a default payment account and one of a plurality of non-default payment accounts (e.g., a payment account that is used only when payment criteria corresponding to the corresponding payment account are met). Based on determining that the payment criteria have not been met for any non-default payment account, the electronic device transmits account information of the default payment account via one or more wireless communication elements without transmitting account information of the non-default payment account.
[0381] According to some embodiments, the payment criteria include criteria based on a determination associated with the current location of the electronic device. For example, when the electronic device is within a determined geographic area, the criteria are met. For another example, when the electronic device is not within the determined geographic area, the criteria are not met.
[0382] According to some embodiments, Fig. 12AAs shown, the payment indication 1202 representing multiple payment accounts does not include an indication for the first payment account and does not include an indication for the second payment account. For example, there is no indication on the display for indicating the first payment account or the second payment account. The payment indication 1202 representing multiple payment accounts does not look like a credit card and does not look like an indication for the first payment account or an indication for the second payment account. Therefore, the user can understand at a glance that the device is in a special operating mode.
[0383] In some embodiments, the multiple payment accounts include only the following payment accounts: for which the electronic device has received user input to activate location-based selection without user input.
[0384] According to some embodiments, the plurality of payment accounts includes only payment accounts for which a financial institution associated with the payment account authorizes the corresponding payment account to be selected based on location without user input.
[0385] According to some embodiments, the contextual selection operating mode is represented as a selectable payment option, in which the device selects which payment account of multiple payment accounts to use for the payment transaction based on the context. In some embodiments, the device receives a selection of the selectable payment option and, in response to the selection of the selectable payment option, switches to the contextual selection operating mode.
[0386] exist Fig. 12C In some embodiments, the electronic device includes a touch-sensitive surface. Fig. 12B Before making the payment as shown, the electronic device receives one or more inputs (e.g., user input) in a first direction (e.g., receiving one or more swipes to the left or right via the touch-sensitive surface, or receiving a change in the orientation of the device in the first direction). Fig. 12C As shown, the electronic device may display an animation that includes causing the payment indication 1202 to transition away from the display. In response to receiving one or more inputs, the electronic device replaces the payment indication 1202 representing multiple payment accounts on the display with a second visual indicator 1220 that is different from the payment indication 1202 representing multiple payment accounts, wherein the second visual selection indicator identifies a third payment account that is different from the first payment account and the second payment account. In response to receiving one or more inputs, the electronic device enables the electronic device to participate in transactions using the third payment account via one or more wireless communication elements. (For example, the device is prepared to conduct NFC transactions using the second account, and the device is prohibited from participating in transactions using the first account). Thus, the user can select a specific payment account. Once the user selects a specific payment account, the user can use the account to make payments, such as Fig. 12B shown.
[0387] According to some embodiments, the payment instruction 1202 representing the plurality of payment accounts is different from the visual indicators (e.g., 1220) of the individual payment accounts in the plurality of payment accounts. For example, the payment instruction 1202 includes a logo without a surrounding card, while all other payment accounts are represented by a card image (e.g., visual indication 1220), or the payment instruction is accompanied by text indicating that the payment instruction represents a situational selection between a plurality of different payment accounts (e.g., "auto-select").
[0388] Fig.13 1 is a flow chart illustrating a method for transmitting account information of an account selected from a plurality of accounts in an electronic wallet according to some embodiments. Method 1300 is performed at an electronic device (e.g., 100, 300, 500) having a display and one or more wireless communication elements. Some operations in method 1300 may be combined, the order of some operations may be changed, and some operations may be omitted.
[0389] As described below, method 1300 provides an intuitive way to transfer account information of an account selected from multiple accounts in an electronic wallet. The method reduces the cognitive burden on the user when selecting an account for payment, thereby creating a more efficient human-computer interface. For battery-powered computing devices, enabling users to select accounts faster and more efficiently saves power and increases the time interval between battery charges.
[0390] At block 1302, the electronic device receives input (eg, user input) requesting that the device be enabled for a payment transaction (eg, a user performs a double-click on a hardware button 508 of the device to prepare the device for an NFC payment).
[0391] At box 1304, in response to receiving the input, the electronic device displays a payment indication (e.g., 1202) on a display, which indicates multiple payment accounts including a first payment account and a second payment account (e.g., displaying a "smart selection" indication that does not identify a specific payment account).
[0392] At block 1306 , the electronic device receives, via one or more wireless communication elements, a request for account information corresponding to a payment transaction (eg, received from contactless payment terminal 1220 ).
[0393] At block 1308, in response to receiving a request for account information corresponding to the payment transaction, the method further proceeds to blocks 1310-1312. At block 1310, based on determining that payment criteria for the first payment account have been met, the electronic device transmits account information for the first payment account via one or more wireless communication elements without transmitting account information for the second payment account (and, optionally, without transmitting payment account information for any other payment account associated with the payment instruction other than the first payment account).
[0394] At box 1312, based on determining that payment criteria for the second payment account have been met, account information of the second payment account is transmitted via one or more wireless communication elements without transmitting account information of the first payment account (and, optionally, without transmitting payment account information of any other payment account associated with the payment instruction other than the second payment account).
[0395] According to some embodiments, the electronic device is configured to enable payment using a default payment account and one of a plurality of non-default payment accounts (e.g., a payment account that is used only when payment criteria of the payment account are met). Based on determining that payment criteria have not been met for any non-default payment account, the electronic device transmits account information of the default payment account via one or more wireless communication elements without transmitting account information of the non-default payment account.
[0396] According to some embodiments, the payment criteria include criteria based on a determination associated with the current location of the electronic device. For example, when the electronic device is within a determined geographic area, the criteria are met. For another example, when the electronic device is not within the determined geographic area, the criteria are not met.
[0397] In some embodiments, a payment instruction (e.g., 1202) representing multiple payment accounts does not include an instruction for a first payment account and does not include an instruction for a second payment account.
[0398] In some embodiments, the multiple payment accounts include only the following payment accounts: for which the electronic device has received user input to activate location-based selection without user input.
[0399] According to some embodiments, the plurality of payment accounts includes only payment accounts for which a financial institution associated with the payment account authorizes the corresponding payment account to be selected based on location without user input.
[0400] According to some embodiments, the contextual selection operating mode is represented as a selectable payment option, in which the device selects which payment account of multiple payment accounts to use for the payment transaction based on the context. In some embodiments, the device receives a selection of the selectable payment option and, in response to the selection of the selectable payment option, switches to the contextual selection operating mode.
[0401] According to some embodiments, the electronic device includes a touch-sensitive surface. The electronic device receives one or more inputs (e.g., user inputs) in a first direction (e.g., one or more swipes to the left or right of the touch-sensitive surface, or a change in the orientation of the device in the first direction). In response to receiving one or more inputs, the electronic device replaces a payment indication (e.g., 1202) representing multiple payment accounts on a display with a second visual indicator (e.g., 1220) different from the payment indication (e.g., 1202) representing multiple payment accounts, wherein the second visual selection indicator identifies a third payment account different from the first payment account and the second payment account. In response to receiving one or more inputs, the electronic device enables the electronic device to participate in a transaction using a third payment account via one or more wireless communication elements. Thus, the user can select a specific payment account.
[0402] In some embodiments, the payment indication representing multiple payment accounts (e.g., 1202) is different from the visual indicators of individual payment accounts in the multiple payment accounts (e.g., 1220).
[0403] It should be noted that the above reference to method 1300 (e.g., Fig.13 ) also apply in a similar manner to the methods described above and below. For example, methods 700, 900, 1100, 1500, 1700, and 1900 may include one or more features of the various methods described above with reference to method 1300. For example, the electronic wallets, payment accounts, loyalty accounts, affordances, and inputs of methods 700, 900, 1100, 1500, 1700, and 1900 optionally have one or more features of the electronic device, payment account, loyalty account, affordances, and inputs of the electronic device described in method 1300. For the sake of brevity, these details are not repeated below.
[0404] FIG. 14A to FIG. 14EAn exemplary method and an exemplary user interface for receiving a selection of an account from a plurality of accounts in an electronic wallet according to some embodiments are shown. For example, the account information of the selected account can then be transmitted to an NFC-enabled payment terminal for use in a transaction (e.g., when the device is placed in the field of the payment terminal). The method is performed at an electronic device having a display, a touch-sensitive surface configured to detect the intensity of contact, and one or more wireless communication elements. The user interfaces in these figures are used to illustrate the processes described below, which include Fig.15 process.
[0405] The electronic device receives a first input (eg, a user input at a hardware button). For example, the user double-clicks a mechanical button or a capacitive button 508 of the device.
[0406] like Fig.14A As shown, in response to receiving the first input, the electronic device displays a first user interface (eg, Fig.14A ), wherein the first user interface includes a first visual indicator 1402 for identifying a payment card associated with a plurality of payment accounts, and a second visual identifier 1406 for identifying a first payment account (e.g., a savings account) among the plurality of payment accounts of the payment card. Fig.14A As shown, the second visual indicator 1406 may include "Savings Account" to indicate that the savings account of the payment card is active or selected. The first visual indicator 1402 may include one or more of the following: the name of the financial institution providing the payment account, the account number, the expiration date, the background design.
[0407] The electronic device enables the electronic device to participate in payment transactions using the first payment account via one or more wireless communication elements. For example, once enabled for the first payment account, the user can place the electronic device in the field of a contactless payment terminal to make an NFC payment using the first payment account. Fig.14A , ready indication 1404 is a visual indication that the device has been enabled to participate in a payment transaction using the first payment account.
[0408] like Fig. 14B As shown, the electronic device detects a first contact on the touch-sensitive surface and determines whether a characteristic intensity of the first contact is above an intensity threshold.
[0409] like Fig. 14C and Fig.14D As shown, based on determining that the characteristic intensity of the first contact is above the intensity threshold (e.g., pressing hard), the electronic device displays a second user interface on the display, wherein the second user interface enables selection between different payment accounts represented by the first visual indicator. For example, pressing hard can obtain Fig.14DFor example, pressing hard can get Fig. 14C The display, after that, in Fig. 14C The activation of the indication 1412 at the user interface is obtained Fig.14D Display of the user interface.
[0410] A user may access a user interface in a number of ways that allows selection from multiple payment accounts of a payment card. One method is to enable the electronic device to participate in a payment transaction (e.g., using an electronic wallet application) so that a first visual indicator is displayed when the device is in payment mode, as discussed above. Another method is to access settings or details of a specific payment account from the electronic wallet application so that a first visual indicator is displayed when the device is not in payment mode (e.g., not enabled to participate in payment transactions via one or more wireless communication elements). While displaying the user interface (and not in payment mode), the device detects contact on the touch-sensitive surface; the device determines whether a characteristic intensity of the contact is above an intensity threshold; and based on determining that the characteristic intensity of the contact is above the intensity threshold (e.g., pressing hard), the device displays an additional user interface on the display, wherein the additional user interface enables selection between different payment accounts represented by the first visual indicator. Both methods (via payment mode and non-payment mode) allow the user to select from multiple payment accounts of a payment card through an account selection interface.
[0411] like Fig. 14C As shown, according to some embodiments, the second user interface includes a payment account selection enable indication 1412. The electronic device detects a second contact on the touch-sensitive surface at a position corresponding to the payment account selection enable indication 1412. Fig.14D As shown, in response to detecting the second contact, the electronic device displays a third user interface 1418 on the display, wherein third user interface 1418 includes one or more account enable representations (e.g., 1420, 1422, 1424) corresponding to at least some of the multiple payment accounts. The electronic device detects the third contact at a location associated with account enable representation 1424 in the one or more account enable representations (e.g., 1420, 1422, 1424), wherein account enable representation 1424 corresponds to a second payment account (e.g., a credit account) in the multiple payment accounts, and the second payment account is different from the first payment account. In some examples, when the electronic device detects activation of cancel enable representation 1426, the electronic device displays Fig. 14C User interface.
[0412] like Fig.14E As shown, in response to detecting the third contact, the electronic device displays a fourth user interface (eg, Fig.14E), wherein the fourth user interface includes: a first visual indicator 1402 for identifying a payment card associated with multiple payment accounts (e.g., the payment card has not changed), and a third visual identifier 1430 for identifying a second payment account among the multiple payment accounts of the payment card (e.g., a credit account different from a checking account). For example, the third visual indicator 1430 specifies "credit account" to indicate that the credit account of the payment card is active or selected. In response to detecting the third contact, the electronic device also enables the electronic device to participate in payment transactions using the second payment account via one or more wireless communication elements (and prohibits the electronic device from participating in payment transactions using the first payment account). For example, a user can place the electronic device in the field of a contactless payment terminal to make an NFC payment using the first payment account. For example, the ready indication 14032 is a visual indication that the device has been enabled to participate in payment transactions using the second payment account.
[0413] In accordance with some embodiments, based on determining that the characteristic intensity of the first contact is below an intensity threshold (e.g., a light press), the electronic device maintains display of the first visual indicator 1402 (and optionally the second visual indicator 1406) without displaying the second user interface on the display.
[0414] According to some embodiments, one or more account enablement representations 1420, 1422, 1424 include multiple account enablement representations.
[0415] In some embodiments, a visual indicator of the currently selected payment account (e.g., 1420, 1422, 1424) is highlighted on the second user interface (e.g., a different color, with a check mark 1428, etc.).
[0416] In some embodiments, detecting the second contact includes determining that a characteristic intensity of the second contact is not above an intensity threshold (e.g., it is not a hard press).
[0417] According to some embodiments, the second user interface includes a payment account deletion enable indication 1410. The electronic device detects activation of the payment account deletion enable indication 1410. In response to detecting activation of the payment account deletion enable indication 1410, the electronic device removes (e.g., unlinks from the electronic device) multiple payment accounts of the payment card from the electronic wallet of the device.
[0418] According to some embodiments, payment account deletion affordance 1410 includes one or more visual features that distinguish the payment account deletion affordance from payment account selection affordance 1412. For example, affordances may have different shapes, different fill colors, or different text, thereby helping to prevent a user from mistaking one affordance for another affordance.
[0419] According to some embodiments, while displaying the fourth user interface on the display, the electronic device detects a swipe input (e.g., a horizontal swipe input) on the touch-sensitive surface. In some embodiments, the swipe input has a characteristic intensity below an intensity threshold. In response to detecting the swipe input, the electronic device displays a fifth user interface, wherein the fifth user interface includes a fourth visual indicator for identifying a second payment card that is different from the payment card. Thus, the user can swipe to change the payment card.
[0420] According to some embodiments, the first user interface, the second user interface, the third user interface, and the fourth user interface are user interfaces of a single electronic wallet application that includes multiple payment accounts associated with a user of the electronic device.
[0421] According to some embodiments, the electronic device receives a request for account information from a contactless payment terminal. In response to receiving the request for account information, the electronic device transmits the account information of the second payment account to the contactless payment terminal via one or more wireless communication elements, wherein the account information enables the contactless payment terminal to participate in the payment transaction. In some embodiments, participating in the payment transaction includes routing the information to one or more financial institutions to verify the payment credentials and / or receive authorization to complete the transaction. For example, NFC is used to transmit the payment account information to the contactless payment terminal.
[0422] Fig.15 1 is a flow chart illustrating a method for receiving a selection of an account from a plurality of accounts in an electronic wallet according to some embodiments. Method 1500 is performed at a device (e.g., 100, 300, 500) having a display, a touch-sensitive surface configured to detect the intensity of a contact, and one or more wireless communication elements. Some operations in method 1500 may be combined, the order of some operations may be changed, and some operations may be omitted.
[0423] As described below, method 1500 provides an intuitive way to receive a selection of an account from a plurality of accounts in an electronic wallet. The method reduces the cognitive burden on the user when selecting an account, thereby creating a more efficient human-computer interface. For battery-powered computing devices, enabling users to select accounts faster and more efficiently saves power and increases the time interval between battery charges.
[0424] At block 1502, the electronic device receives a first input (eg, a user input at a hardware button). For example, the user double-clicks a mechanical button or a capacitive button of the device.
[0425] At block 1504, in response to receiving the first input, the technology proceeds to 1506. At block 1506, the electronic device displays a first user interface (e.g., Fig.14A ), wherein the first user interface includes: a first visual indicator (e.g., 1402) for identifying a payment card associated with multiple payment accounts, and a second visual identifier (e.g., 1406) for identifying a first payment account among the multiple payment accounts of the payment card.
[0426] At block 1506, the electronic device enables the electronic device to participate in a payment transaction using the first payment account via one or more wireless communication elements.At block 1508, the electronic device detects a first contact on the touch-sensitive surface.
[0427] At box 1510, the electronic device determines whether the characteristic intensity of the first contact is above an intensity threshold.
[0428] At block 1512, based on determining that the characteristic intensity of the first contact is greater than an intensity threshold (eg, a hard press), the electronic device displays a second user interface (eg, Fig.14D 1418 or Fig. 14C ), wherein the second user interface enables selection between different payment accounts represented by the first visual indicator.
[0429] According to some embodiments, the second user interface includes a payment account selection enable representation (e.g., 1412). The electronic device detects a second contact on the touch-sensitive surface at a position corresponding to the payment account selection enable representation (e.g., 1412). In response to detecting the second contact, the electronic device displays a third user interface (e.g., 1418) on the display, wherein the third user interface (e.g., 1418) includes one or more account enable representations (e.g., 1420, 1422, 1424) corresponding to at least some of the multiple payment accounts. The electronic device detects a third contact at a position associated with an account enable representation (e.g., 1424) in one or more account enable representations (e.g., 1420, 1422, 1424), wherein the account enable representation (e.g., 1424) corresponds to a second payment account in the multiple payment accounts, and the second payment account is different from the first payment account.
[0430] In response to detecting the third contact, the electronic device displays a fourth user interface (eg, Fig.14EIn response to detecting the third contact, the electronic device enables the electronic device to participate in payment transactions using the second payment account via one or more wireless communication elements (and prohibits the electronic device from participating in payment transactions using the first payment account).
[0431] In accordance with some embodiments, based on determining that the characteristic intensity of the first contact is below an intensity threshold (e.g., a light press), the electronic device maintains display of the first visual indicator (e.g., 1402) (and optionally the second visual indicator 1406) without displaying a second user interface on the display.
[0432] According to some embodiments, one or more account enablement representations (e.g., 1420, 1422, 1424) include multiple account enablement representations.
[0433] In some embodiments, a visual indicator of the currently selected payment account (e.g., 1420, 1422, 1424) is highlighted on the second user interface (e.g., a different color, with a check mark 1428, etc.).
[0434] In some embodiments, detecting the second contact includes determining that a characteristic intensity of the second contact is not above an intensity threshold (e.g., it is not a hard press).
[0435] According to some embodiments, the second user interface includes a payment account deletion enable indication (e.g., 1410). The electronic device detects activation of the payment account deletion enable indication (e.g., 1410). In response to detecting activation of the payment account deletion enable indication (e.g., 1410), the electronic device removes (e.g., unlinks from the electronic device) multiple payment accounts of the payment card from the electronic wallet of the device.
[0436] In some embodiments, the payment account deletion enable indication (e.g., 1410) includes one or more visual features that distinguish the payment account deletion enable indication from the payment account selection enable indication (e.g., 1412).
[0437] According to some embodiments, while displaying the fourth user interface on the display, the electronic device detects a swipe input (e.g., a horizontal swipe input) on the touch-sensitive surface. In some embodiments, the swipe input has a characteristic intensity below an intensity threshold. In response to detecting the swipe input, the electronic device displays a fifth user interface, wherein the fifth user interface includes a fourth visual indicator for identifying a second payment card different from the payment card.
[0438] According to some embodiments, the first user interface, the second user interface, the third user interface, and the fourth user interface are user interfaces of a single electronic wallet application that includes multiple payment accounts associated with a user of the electronic device.
[0439] According to some embodiments, the electronic device receives a request for account information from a contactless payment terminal. In response to receiving the request for account information, the electronic device transmits the account information of the second payment account to the contactless payment terminal via one or more wireless communication elements, wherein the account information enables the contactless payment terminal to participate in the payment transaction. In some embodiments, participating in the payment transaction includes routing the information to one or more financial institutions to verify the payment credentials and / or receive authorization to complete the transaction. For example, NFC is used to transmit the payment account information to the contactless payment terminal.
[0440] It should be noted that the above reference to method 1500 (e.g., Fig.15 ) also apply in a similar manner to the methods described above and below. For example, methods 700, 900, 1100, 1300, 1700, and 1900 may include one or more features of the various methods described above with reference to method 1500. For example, the electronic wallets, payment accounts, loyalty accounts, affordances, and inputs of methods 700, 900, 1100, 1300, 1700, and 1900 optionally have one or more features of the electronic device, payment account, loyalty account, affordances, and inputs of the electronic device described in method 1500. For the sake of brevity, these details are not repeated below.
[0441] FIG. 16A to FIG. 16G An exemplary method and an exemplary user interface for linking a payment account to one or more electronic devices according to some embodiments are shown. The method is performed at a first electronic device having a display and one or more wireless communication elements (e.g., one or more wireless antennas, such as an AFC antenna, a WiFi antenna). The user interfaces in these figures are used to illustrate the processes described below, which include Fig.17 process.
[0442] A user may want to add a payment account to two devices that are paired with each other, such as the user's phone and the user's smartwatch. The following description describes a method for linking a payment account to a user's first device (e.g., phone) and the user's second device (e.g., smartwatch) in a convenient and efficient manner.
[0443] exist Fig.16A, the first electronic device displays a user interface including three enable representations for linking a payment account to the first electronic device. For example, enable representation 1606, when activated, allows payment account details to be imported from a remote server; enable representation 1608, when activated, allows payment account details to be manually entered (e.g., using a displayed keyboard); and enable representation 1610, when activated, allows payment account details to be captured using a camera sensor of the first electronic device.
[0444] exist Fig. 16B In the embodiment of the present invention, the first electronic device may display a user interface including a payment account indication 1612 for indicating a payment account. The device may prompt the user to enter a security code (e.g., a digital card security code, such as CVD, CVV, CVC) for the payment account. For example, the device may receive input using a keyboard 1616 for entering a security code into a field 1614. Thus, the first electronic device receives a first request (e.g., user input) for linking a payment account associated with a payment card (e.g., a credit card) to the first electronic device.
[0445] In response to receiving the first request, the first electronic device initiates a process for linking the payment account to the first electronic device. Fig. 16B As shown, in the process for linking a payment account to a first electronic device, the first electronic device receives input of a security code of a payment card (e.g., a digital card security code, such as CVD, CVV, CVC). For example, a user can enter the security code into field 1614 by using keyboard 1616. In some embodiments, the first electronic device determines whether further verification is required to link the payment account to the first electronic device. Based on determining that no further verification is required to link the payment account to the first electronic device, the first electronic device links the payment account to the electronic device. Fig. 16CAs shown, based on determining that further verification is required to link the payment account to the first electronic device, the first electronic device provides an indication that further verification is required to link the payment account to the corresponding device (e.g., displaying on the display of the first electronic device that approval for linking the payment account is under review, or requesting the user to call a phone number for verification). In this example, the user can activate the enable indication 1618 to receive a phone call to complete further verification, or the user can activate the enable indication 1620 to receive an email to complete further verification. In some embodiments, the indication that further verification is required to link the payment account to the first electronic device includes an alphanumeric visual indicator displayed on the display of the electronic device (e.g., including an alphanumeric indicator of "approval under review", which "approval under review" indicates that a further verification step has been initiated without additional user input). For example, a financial institution (e.g., a bank) associated with the payment account may need to confirm the details of the payment account before the payment account is linked to the corresponding device. Verification may or may not require additional user interaction with the financial institution. Further details regarding determinations and processes for further verification are described in U.S. Provisional Patent Application Serial No. 62 / 004,886, "USER INTERFACE FOR PAYMENTS," which is hereby incorporated by reference in its entirety.
[0446] like Fig.16D As shown, after the payment account is successfully linked to the first electronic device (for example, in response to linking the payment account to the first electronic device), the first electronic device simultaneously displays on the display an indication 1638 that the payment account has been successfully linked to the first electronic device and an optional enabling indication 1640 for linking the payment account to a second electronic device that is different from the first electronic device.
[0447] The first electronic device receives activation of selectable enable representation 1640 (e.g., the user activates selectable enable representation 1640 by tapping the enable representation). In response to receiving the activation of selectable enable representation 1640, the first electronic device initiates a process for linking the payment account to the second electronic device (e.g., as shown in FIG. 1 ). FIG. 16E to FIG. 16F shown).
[0448] According to some embodiments, the second electronic device is uniquely paired with the first electronic device. For example, the second electronic device has a special relationship with the first electronic device because the second electronic device is only paired with the first electronic device and is not paired with any other device.
[0449] According to some embodiments, a first electronic device is paired with a second electronic device, and the first electronic device is paired with a third electronic device, wherein the pairing relationship between the first electronic device and the second electronic device is different from the pairing relationship between the first electronic device and the third electronic device.
[0450] According to some embodiments, initiating a process for linking a payment account to a second electronic device includes (the first electronic device) transmitting, via one or more wireless communication elements, an indication that the second electronic device is uniquely paired with the first electronic device to a financial institution associated with the payment card. For example, the first electronic device sends a security token to the financial institution indicating that the second electronic device is uniquely paired with a device linked to the same payment account.
[0451] According to some embodiments, after initiating linking the payment account to the second electronic device, the first electronic device receives confirmation from the second electronic device that the second electronic device has been successfully linked to the payment account. The primary account number of the second electronic device linked to the payment account (e.g., a digital PAN, DPAN, a 16-digit account number, or other account number, which, for example, cannot be used to complete manual transactions through voice calls—can only be used to complete electronic payments through the device) is different from the primary account number of the first electronic device linked to the payment account (e.g., a digital PAN, DPAN, a 16-digit account number, or other account number). Figure 16G As shown, in some examples, the first electronic device displays a confirmation 1636 that the payment account is linked to the second electronic device.
[0452] In some embodiments, a first request (e.g., user input) to link a payment account (to a first electronic device) includes an account number of a payment card (e.g., which is provided by the user via manual input, imported from a server, or entered by the user via a camera sensor of the electronic device), and wherein initiating a process for linking the payment account to a second electronic device occurs without the need for additional input (e.g., user input) of the account number of the payment card.
[0453] like Fig.16F As shown, according to some embodiments, the second request (e.g., linking a payment account to a second electronic device, which initiates a process for linking a payment account to a second electronic device) includes a security code (e.g., a digital card security code, such as CVD, CVV, CVC) of a payment card (e.g., which is entered by a user). For example, the user can enter the security code into field 1634 using keyboard 1628.
[0454] In some embodiments, a first electronic device initiates a process for linking a payment account to a second electronic device.
[0455] According to some embodiments, initiating a process for linking a payment account to a second electronic device includes (the first electronic device) transmitting, via one or more wireless communication elements, (1) an account number of a credit card and (2) a security token used to confirm that the payment account was previously linked to the first electronic device to a financial institution associated with the payment card. In some embodiments, the security token is generated by the electronic device after the payment account is linked to the first device. In some embodiments, the security token is received by the electronic device from the financial institution after the payment account is linked to the first device.
[0456] According to some embodiments, initiating a process for linking a payment account to a second electronic device includes: (the first electronic device) determining whether further verification is required to link the payment account to the second electronic device; based on determining that further verification is not required to link the payment account to the second electronic device, (the first electronic device) initiating a process for linking the payment account to the second electronic device and providing an indication (e.g., on a display) that the payment account has been linked to the second electronic device; and, Fig.16E As shown, based on determining that further verification is required to link the payment account to the second electronic device, (the first electronic device) provides an indication 1642 (e.g., on a display) that further verification is required to link the payment account to the second electronic device.
[0457] like Fig.16E As shown, according to some embodiments, the indication that further verification is required to link the payment account to the second electronic device includes a visual indication of additional steps performed by the user to link the payment account to the corresponding device (e.g., an enabling indication 1630 including a telephone number to be called; an enabling indication 1632 including an email address to be sent).
[0458] According to some embodiments, the first electronic device transmits account linking information to the second electronic device. The account linking information enables the second electronic device to link the payment account to the second electronic device.
[0459] According to some embodiments, based on determining that further verification is required to link the payment account to the second electronic device, the first electronic device displays a plurality of communication method enable indications on a display, wherein each communication method enable indication is associated with a corresponding communication method for verifying the communication. The plurality of communication method enable indications are based on communications received from the financial institution.
[0460] According to some embodiments, based on determining that further verification is required to link the payment account to the second electronic device, the first electronic device receives a selection of a communication method enabling indication from a plurality of communication method enabling indications, and in response to receiving the selection of the communication method enabling indication, the first electronic device transmits an indication of a corresponding communication method of the selected communication method enabling indication to the financial institution. The verification communication is based on the communication method enabling indication.
[0461] According to some embodiments, the first electronic device receives a primary account number from a financial institution for use in authorizing payment from a payment account using a second electronic device. The primary account number is different from a credit card account number. The first electronic device assigns the primary account number to the second electronic device.
[0462] According to some embodiments, the electronic wallet of the second electronic device includes payment account information of a second payment account associated with a user of the second electronic device, wherein the second payment account is different from the payment account.
[0463] According to some embodiments, the first electronic device receives an instruction from the second electronic device that the second electronic device participate in a payment transaction using the linked payment account. For example, the second electronic device transmits payment account information of the linked payment account to a contactless payment terminal close to the second e...
Claims
1. A method comprising: At a first electronic device having a display and one or more wireless communication elements: displaying on the display a registration user interface for linking a payment account to the first electronic device, the user interface including displayed instructions for user input, the user input causing the first electronic device to initiate a process for linking a payment account to the first electronic device; receiving a sequence of one or more inputs consistent with the instructions and corresponding to a first request to link the payment account associated with a payment card to the first electronic device; in response to receiving the sequence of one or more inputs consistent with the instructions and corresponding to the first request, initiating a process for linking the payment account to the first electronic device; After the payment account is successfully linked to the first electronic device, the display simultaneously displays: an indication that the payment account has been successfully linked to the first electronic device; and an optional affordance for linking the payment account to a second electronic device that is different from the first electronic device and is paired to the first electronic device; receiving an activation of the selectable affordance; as well as In response to receiving activation of the optional enable indication, a process for linking the payment account to a second electronic device is initiated, wherein the second electronic device is different from the first electronic device and is paired to the first electronic device, wherein the process for linking the payment account to the second electronic device includes: displaying on the display of the first electronic device instructions for user input at the first electronic device to link the payment account to the second electronic device. The method of claim 1 , wherein the second electronic device is uniquely paired with the first electronic device.
3. The method according to claim 1, wherein the first electronic device is paired with the second electronic device, and the first electronic device is paired with a third electronic device, and wherein the pairing relationship between the first electronic device and the second electronic device is different from the pairing relationship between the first electronic device and the third electronic device.
4. The method according to any one of claims 1-3, wherein initiating the process for linking the payment account to the second electronic device comprises: An indication that the second electronic device is uniquely paired with the first electronic device is transmitted to a financial institution associated with the payment card via the one or more wireless communication elements.
5. The method according to any one of claims 1 to 3, further comprising: After initiating linking the payment account to the second electronic device, receiving confirmation from the second electronic device that linking the second electronic device to the payment account was successful; as well as The primary account number linked to the second electronic device used for the payment account is different from the primary account number linked to the first electronic device used for the payment account.
6. A method according to any one of claims 1-3, wherein the first request to link a payment account includes an account number of the payment card, and wherein initiating a process for linking the payment account to the second electronic device occurs without additional input of the account number of the payment card.
7. The method according to any one of claims 1-3, wherein the second request includes a security code of the payment card.
8. The method of claim 6, wherein initiating the process of linking the payment account to the second electronic device comprises: transmitting, via the one or more wireless communication elements, to a financial institution associated with the payment card: the account number of the payment card; as well as Confirming that the payment account was previously linked to a security token of the first electronic device.
9. The method according to any one of claims 1-3, wherein initiating the process for linking the payment account to the second electronic device comprises: determining whether further verification is required to link the payment account to the second electronic device; If it is determined that no further verification is required to link the payment account to the second electronic device, initiating a process for linking the payment account to the second electronic device and providing an indication that the payment account has been linked to the second electronic device; as well as If it is determined that further verification is required to link the payment account to the second electronic device, an indication is provided that further verification is required to link the payment account to the second electronic device.
10. The method of claim 9, wherein the indication that further verification is required to link the payment account to the second electronic device comprises a visual indication of additional steps to be taken by a user to link the payment account to a corresponding device.
11. The method according to any one of claims 1 to 3, further comprising: Account linking information is transmitted to the second electronic device, wherein the account linking information enables the second electronic device to link the payment account to the second electronic device.
12. The method according to claim 9, further comprising: If it is determined that further verification is required to link the payment account to the corresponding device: displaying a plurality of communication method enable indications on the display, wherein each communication method enable indication is associated with a corresponding communication method for verifying communications; and Wherein the plurality of communication methods may be represented based on communications received from a financial institution.
13. The method according to claim 12, further comprising: If it is determined that further verification is required to link the payment account to the second electronic device: receiving a selection of a communication method enablement indication from among the plurality of communication method enablement indications; In response to receiving the selection of the communication method indication, transmitting an indication of a corresponding communication method for the selected communication method indication to the financial institution; as well as Wherein the verification communication is indicated based on the communication method.
14. The method according to claim 4, further comprising: receiving a primary account number from the financial institution for use in authorizing payment from the payment account using the second electronic device, wherein the primary account number is different from the account number of the payment card; as well as Assign the primary account to the corresponding device.
15. The method of any one of claims 1-3, wherein the electronic wallet of the second electronic device includes payment account information for a second payment account associated with a user of the second electronic device, wherein the second payment account is different from the payment account.
16. The method according to any one of claims 1 to 3, further comprising: An indication is received from the second electronic device for the second electronic device to participate in a payment transaction using the linked payment account.
17. A first electronic device, comprising: monitor; one or more wireless communication elements; one or more processors; Memory; as well as One or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs comprising instructions for the following steps: displaying on the display a registration user interface for linking a payment account to the first electronic device, the user interface including displayed instructions for user input, the user input causing the first electronic device to initiate a process for linking a payment account to the first electronic device; receiving a sequence of one or more inputs consistent with the instructions and corresponding to a first request to link the payment account associated with a payment card to the first electronic device; in response to receiving the sequence of one or more inputs consistent with the instructions and corresponding to the first request, initiating a process for linking the payment account to the first electronic device; After the payment account is successfully linked to the first electronic device, the display simultaneously displays: an indication that the payment account has been successfully linked to the first electronic device; and an optional affordance for linking the payment account to a second electronic device that is different from the first electronic device and is paired to the first electronic device; as well as receiving an activation of the selectable affordance; as well as In response to receiving activation of the optional enable indication, a process for linking the payment account to the second electronic device is initiated, wherein the second electronic device is different from the first electronic device and is paired to the first electronic device, wherein the process for linking the payment account to the second electronic device includes: displaying on the display of the first electronic device instructions for user input at the first electronic device to link the payment account to the second electronic device.
18. The first electronic device of claim 17, wherein the second electronic device is uniquely paired with the first electronic device.
19. A first electronic device according to claim 17, wherein the first electronic device is paired with the second electronic device, and the first electronic device is paired with a third electronic device, and wherein the pairing relationship between the first electronic device and the second electronic device is different from the pairing relationship between the first electronic device and the third electronic device.
20. The first electronic device according to any one of claims 17-19, wherein initiating the process for linking the payment account to the second electronic device comprises: An indication that the second electronic device is uniquely paired with the first electronic device is transmitted to a financial institution associated with the payment card via the one or more wireless communication elements.
21. The first electronic device according to any one of claims 17 to 19, wherein the one or more programs further comprise instructions for the following steps: After initiating linking the payment account to the second electronic device, receiving confirmation from the second electronic device that linking the second electronic device to the payment account was successful; and The primary account number linked to the second electronic device used for the payment account is different from the primary account number linked to the first electronic device used for the payment account.
22. A first electronic device according to any one of claims 17-19, wherein the first request to link a payment account includes an account number of the payment card, and wherein initiating a process for linking the payment account to the second electronic device occurs without additional input of the account number of the payment card.
23. The first electronic device according to any one of claims 17-19, wherein the second request includes a security code of the payment card.
24. The first electronic device of claim 22, wherein initiating the process for linking the payment account to the second electronic device comprises: transmitting, via the one or more wireless communication elements, to a financial institution associated with the payment card: the account number of the payment card; as well as Confirming that the payment account was previously linked to a security token of the first electronic device.
25. The first electronic device of claim 24, wherein initiating the process for linking the payment account to the second electronic device comprises: determining whether further verification is required to link the payment account to the second electronic device; If it is determined that no further verification is required to link the payment account to the second electronic device, initiating a process for linking the payment account to the second electronic device and providing an indication that the payment account has been linked to the second electronic device; as well as If it is determined that further verification is required to link the payment account to the second electronic device, an indication is provided that further verification is required to link the payment account to the second electronic device.
26. A first electronic device according to claim 25, wherein the indication that further verification is required to link the payment account to the second electronic device includes a visual indication of additional steps taken by a user to link the payment account to the corresponding device.
27. The first electronic device according to any one of claims 17 to 19, wherein the one or more programs further comprise instructions for the following steps: The account linking information is transmitted to the second electronic device, wherein the account linking information enables the second electronic device to link the payment account to the second electronic device.
28. The first electronic device of claim 25, wherein the one or more programs further comprise instructions for: If it is determined that further verification is required to link the payment account to the corresponding device: displaying a plurality of communication method enable indications on the display, wherein each communication method enable indication is associated with a corresponding communication method for verifying communications; and Wherein the plurality of communication methods may be represented based on communications received from the financial institution.
29. The first electronic device of claim 28, wherein the one or more programs further comprise instructions for: If it is determined that further verification is required to link the payment account to the second electronic device: receiving a selection of a communication method enablement indication from among the plurality of communication method enablement indications; In response to receiving the selection of the communication method indication, transmitting an indication of a corresponding communication method for the selected communication method indication to a financial institution; and Wherein the verification communication is indicated based on the communication method.
30. The first electronic device of claim 20, wherein the one or more programs further comprise instructions for: receiving a primary account number from the financial institution for use in authorizing payment from the payment account using the second electronic device, wherein the primary account number is different from the account number of the payment card; and Assign the primary account to the corresponding device.
31. The first electronic device according to any one of claims 17-19, wherein the electronic wallet of the second electronic device includes payment account information for a second payment account associated with a user of the second electronic device, wherein the second payment account is different from the payment account.
32. The first electronic device according to any one of claims 17 to 19, wherein the one or more programs further comprise instructions for: An indication is received from the second electronic device for the second electronic device to participate in a payment transaction using the linked payment account.
33. A computer-readable storage medium storing one or more programs configured to be executed by one or more processors of a first electronic device having a display and one or more wireless communication elements, the one or more programs comprising one or more instructions for the following steps: displaying on the display a registration user interface for linking a payment account to the first electronic device, the user interface including displayed instructions for user input, the user input causing the first electronic device to initiate a process for linking a payment account to the first electronic device; receiving a sequence of one or more inputs consistent with the instructions and corresponding to a first request to link the payment account associated with a payment card to the first electronic device; in response to receiving the sequence of one or more inputs consistent with the instructions and corresponding to the first request, initiating a process for linking the payment account to the first electronic device; After the payment account is successfully linked to the first electronic device, the display simultaneously displays: an indication that the payment account has been successfully linked to the first electronic device; and an optional affordance for linking the payment account to a second electronic device that is different from the first electronic device and is paired to the first electronic device; as well as receiving an activation of the selectable affordance; as well as In response to receiving activation of the optional enable indication, a process for linking the payment account to the second electronic device is initiated, wherein the second electronic device is different from the first electronic device and is paired to the first electronic device, wherein the process for linking the payment account to the second electronic device includes: displaying on the display of the first electronic device instructions for user input at the first electronic device to link the payment account to the second electronic device.
34. The computer-readable storage medium of claim 33, wherein the second electronic device is uniquely paired with the first electronic device.
35. A computer-readable storage medium according to claim 33, wherein the first electronic device is paired with the second electronic device, and the first electronic device is paired with a third electronic device, and wherein the pairing relationship between the first electronic device and the second electronic device is different from the pairing relationship between the first electronic device and the third electronic device.
36. The computer-readable storage medium of any one of claims 33-35, wherein initiating the process for linking the payment account to the second electronic device comprises: An indication that the second electronic device is uniquely paired with the first electronic device is transmitted to a financial institution associated with the payment card via the one or more wireless communication elements.
37. The computer-readable storage medium of any one of claims 33 to 35, wherein the one or more programs further comprise instructions for: After initiating linking the payment account to the second electronic device, receiving confirmation from the second electronic device that linking the second electronic device to the payment account was successful; and The primary account number linked to the second electronic device used for the payment account is different from the primary account number linked to the first electronic device used for the payment account.
38. A computer-readable storage medium according to any one of claims 33 to claim 35, wherein the first request to link a payment account includes an account number of the payment card, and wherein initiating a process for linking the payment account to the second electronic device occurs without additional input of the account number of the payment card.
39. The computer-readable storage medium of any one of claims 33 to 35, wherein the second request includes a security code of the payment card.
40. The computer-readable storage medium of claim 38, wherein initiating the process for linking the payment account to the second electronic device comprises: transmitting, via the one or more wireless communication elements, to a financial institution associated with the payment card: the account number of the payment card; as well as Confirming that the payment account was previously linked to a security token of the first electronic device.
41. The computer-readable storage medium of claim 40, wherein initiating the process for linking the payment account to the second electronic device comprises: determining whether further verification is required to link the payment account to the second electronic device; If it is determined that no further verification is required to link the payment account to the second electronic device, initiating a process for linking the payment account to the second electronic device and providing an indication that the payment account has been linked to the second electronic device; as well as If it is determined that further verification is required to link the payment account to the second electronic device, an indication is provided that further verification is required to link the payment account to the second electronic device.
42. A computer-readable storage medium according to claim 41, wherein the indication that further verification is required to link the payment account to the second electronic device includes a visual indication of additional steps taken by a user to link the payment account to the corresponding device.
43. The computer-readable storage medium of any one of claims 33 to 35, wherein the one or more programs further comprise instructions for: The account linking information is transmitted to the second electronic device, wherein the account linking information enables the second electronic device to link the payment account to the second electronic device.
44. The computer-readable storage medium of claim 41, wherein the one or more programs further comprise instructions for: If it is determined that further verification is required to link the payment account to the corresponding device: displaying a plurality of communication method enable indications on the display, wherein each communication method enable indication is associated with a corresponding communication method for verifying communications; and Wherein the plurality of communication methods may be represented based on communications received from the financial institution.
45. The computer-readable storage medium of claim 44, wherein the one or more programs further comprise instructions for: If it is determined that further verification is required to link the payment account to the second electronic device: receiving a selection of a communication method enablement indication from among the plurality of communication method enablement indications; In response to receiving the selection of the communication method indication, transmitting an indication of a corresponding communication method for the selected communication method indication to a financial institution; and The verification communication is based on the communication method indication.
46. The computer-readable storage medium of claim 36, wherein the one or more programs further comprise instructions for: receiving a primary account number from the financial institution for use in authorizing payment from the payment account using the second electronic device, wherein the primary account number is different from the account number of the payment card; and Assign the primary account to the corresponding device.
47. A computer-readable storage medium according to any one of claims 33 to claim 35, wherein the electronic wallet of the second electronic device includes payment account information for a second payment account associated with a user of the second electronic device, wherein the second payment account is different from the payment account.
48. The computer-readable storage medium of any one of claims 33 to 35, wherein the one or more programs further comprise instructions for: An indication is received from the second electronic device for the second electronic device to participate in a payment transaction using the linked payment account.
49. A first electronic device, comprising: monitor; one or more wireless communication elements; as well as Means for performing the method according to any one of claims 1-3.
50. A computer program product comprising one or more programs configured to be executed by one or more processors of a first electronic device having a display and one or more wireless communication elements, the one or more programs including instructions for causing the first electronic device to perform a method according to any one of claims 1-16.
Citation Information
Patent Citations
Method and apparatus for integrating manual input
US20020015024A1
Acceleration-based theft detection system for portable electronic devices
US20050190059A1
Gestures for touch sensitive input devices
US20060026536A1
Virtual input device placement on a touch screen user interface
US20060033724A1
Multi-functional hand-held device
US20060197753A1
