User interface for payment

Abstract

The present invention relates to user interfaces for payment. The present disclosure generally relates to making payments using a mobile device. In one example process, a device receives first authorization data such as fingerprint authentication information and second authorization data such as a bank authorization code. The device then transmits a transaction request for a payment transaction. In another example process, the device detects activation of a physical input structure and uses a biometric sensor to detect a fingerprint. The device is enabled to participate in an NFC payment transaction. In another example process, when the device detects partial credit card information of a credit card in a field of view of a camera sensor, the device displays a real-time preview of an image obtained via the camera sensor.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application is a divisional application of the Chinese invention patent application with the application date of February 1, 2016, the national application number 201610069731.0, and the invention name “User Interface for Payment”.

[0003] This application claims priority to U.S. Provisional Patent Application Serial No. 62 / 110,566, filed on February 1, 2015, entitled “USER INTERFACE FOR PAYMENTS,” and U.S. Provisional Patent Application Serial No. 62 / 172,000, filed on June 5, 2015, entitled “USER INTERFACE FOR PAYMENTS,” each of which is incorporated herein by reference in its entirety for all purposes.

[0004] This application is related to the following provisional applications: U.S. patent application serial number 61 / 912,727, filed on December 6, 2013, entitled “PROVISIONING AND AUTHENTICATING CREDENTIALS ON AN ELECTRONIC DEVICE” (reference number P19543USP1); U.S. patent application serial number 61 / 909,717, filed on November 27, 2013, entitled “PROVISIONING OF CREDENTIALS ON AN ELECTRONIC DEVICE USING PASSWORDS COMMUNICATED OVERVERIFIED CHANNELS” (reference number P19950USP1); ... ELECTRONIC DEVICE” filed on December 23, 2013 (reference number P20450USP4); U.S. patent application serial number 61 / 920,029 entitled “DELETION OF CREDENTIALS FROM AN ELECTRONIC DEVICE” filed on December 23, 2013 (reference number P21084USP1); U.S. patent application serial number 61 / 899,737 entitled “USING BIOAUTHENTICATION IN NEAR-FIELD-COMMUNICATION TRANSACTIONS” filed on November 4, 2013 (reference number P21646USP1); U.S. patent application serial number 61 / 899,737 entitled “USING BIOAUTHENTICATION IN NEAR-FIELD-COMMUNICATION TRANSACTIONS” filed on November 15 ...4, 2013 (reference number P21646USP1); U.S. patent application serial number 61 / 899,737 entitled “USING BIOAUTHENTICATION IN NEAR-FIELD-COMMUNICATION TRANSACTIONS” filed on November 15, 2013 (reference number P21646USP1); U.S. patent application serial number 61 / 899,737 entitled “USING BIOAUTHENTICATION IN NEAR-FIELD-COMMUNIC No. 61 / 905,035, entitled “ELECTRONIC RECEIPTS FOR NFC-BASED FINANCIAL TRANSACTIONS” (reference number P21714USP1), filed on November 15, 2013; No. 62 / 004,798, entitled “FINANCIAL-TRANSACTION NOTIFICATIONS” (reference number P23211USP1), filed on May 29, 2014;U.S. Patent Application Serial No. 62 / 004,837, filed May 29, 2014, entitled “METHODS FOR MANAGING PAYMENT APPLETS ON A SECURE ELECTRONIC DEVICE TO CONDUCT MOBILE PAYMENT TRANSACTIONS” (Reference Number P23215USP1); U.S. Patent Application Serial No. 62 / 004,840, filed May 29, 2014, entitled “METHODS FOR OPERATING A PORTABLE ELECTRONIC DEVICE TO CONDUCT MOBILE PAYMENT TRANSACTIONS” (Reference Number P23223USP1); U.S. Patent Application Serial No. 62 / 004,851, filed May 29, 2014, entitled “METHODS FOR USING A PRIMARY USER DEVICE TO PROVISION CREDENTIAL SON TO A SECONDARY USER DEVICE No. 62 / 004,835, filed on May 29, 2014, entitled “METHODS FOR USING A RANDOM AUTHORIZATION NUMBER TO PROVIDE ENHANCED SECURITY FOR A SECURE ELEMENT” (reference number P23261USP1); 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 number P22931USP1); and No. 62 / 004,836, filed on May 29, 2014, entitled “METHODS FOR USING A RANDOM AUTHORIZATION NUMBER TO PROVIDE ENHANCED SECURITY FOR A SECURE ELEMENT” (reference number P23261USP1); and 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 number P22931USP1); and No. 62 / 004,839, filed on May 29, 2014, entitled “METHODS FOR USING A RANDOM AUTHORIZATION NUMBER TO PROVIDE ENHANCED SECURITY FOR A SECURE ELEMENT” (reference number P23261USP1). ELECTRONIC DEVICE"; these applications are incorporated herein by reference in their entirety.; Technical Field

[0005] The present disclosure relates generally to user interfaces and, more particularly, to techniques for conducting payment transactions and linking payment accounts to electronic devices. Background Art

[0006] In recent years, the use of electronic devices for making payments at point-of-sale terminals and on the Internet has increased significantly. Exemplary point-of-sale terminals include terminals with near field communication capabilities (NFC capabilities), terminals with Bluetooth capabilities, and terminals with barcode scanner capabilities. Electronic devices can be used in conjunction with these exemplary terminals to enable users of the electronic devices to make payments for, for example, purchases of goods and services. Similarly, electronic devices can be used in conjunction with Internet shopping carts to enable users to make payments by entering their credit card information. Summary of the invention

[0007] However, some techniques for using electronic devices to conduct payment transactions and linking payment accounts for payment transactions are often cumbersome and inefficient. For example, prior art techniques use complex and time-consuming user interfaces, which may include multiple buttons or keystrokes. Prior art techniques take longer than necessary, thereby wasting user time and device energy. This latter consideration is particularly important in battery-powered devices.

[0008] Therefore, there is a need for electronic devices with faster, more efficient methods and interfaces for making payment transactions and linking payment accounts for payment transactions while maintaining a high level of security. Such methods and interfaces optionally supplement or replace other methods for making payments and linking payment accounts for payment transactions. These methods and interfaces reduce the cognitive burden on users and produce more efficient human-computer interfaces. For battery-powered computing devices, these methods and interfaces save power and increase the time between battery charges.

[0009] According to some embodiments, a method is performed at an electronic device. The method includes: detecting a request to initiate a payment transaction; in response to detecting the request to initiate a payment transaction, displaying a payment user interface; while displaying the payment user interface, receiving first authorization data; after receiving the first authorization data, determining whether the first authorization data is valid; receiving second authorization data; after receiving the first authorization data and the second authorization data, transmitting a transaction request corresponding to the payment transaction to one or more remote servers; receiving a reply to the transaction request; and in response to receiving the reply to the transaction request: based on determining that the transaction request is successful, dismissing the payment user interface; and based on determining that the transaction request fails, maintaining the display of the payment user interface and updating the payment user interface to display an indication of the reason why the transaction request failed.

[0010] According to some embodiments, a method is performed at an electronic device having a short-range communication radio and a physical input mechanism including an integrated biometric sensor. The method includes: when the electronic device is not enabled to participate in a payment transaction via the short-range communication radio: detecting activation of the physical input mechanism; in response to detecting at least a portion of the activation of the physical input mechanism, detecting a fingerprint using the integrated biometric sensor; and determining whether the fingerprint is consistent with a registered fingerprint that is enabled to authorize a payment transaction; and enabling the device to participate in a payment transaction via the short-range communication radio based on the determination that the fingerprint is consistent with the registered fingerprint that is enabled to authorize the payment transaction.

[0011] According to some embodiments, a method is performed at an electronic device having a display and a camera sensor. The method includes: displaying a user interface on the display, the user interface including: a credit card import affordance for importing at least a portion of credit card information from a remote server; and a credit card input affordance for receiving at least a portion of the credit card information at the electronic device; in response to receiving a selection of the credit card input affordance, displaying a real-time preview of an image obtained via the camera sensor on the display; and while displaying the real-time preview of the image obtained via the camera sensor, detecting at least a portion of the credit card information of the credit card in a field of view of the camera.

[0012] According to some embodiments, a method is performed at an electronic device having a short-range communication radio and a physical input mechanism including an integrated biometric sensor. When the electronic device is locked and in a first short-range communication radio payment mode: detecting activation of the physical input mechanism; detecting a fingerprint using the integrated biometric sensor; determining whether the fingerprint is consistent with a registered fingerprint; and determining whether a set of one or more criteria is satisfied, wherein the set of one or more criteria includes criteria satisfied when the physical input mechanism is reactivated within a predetermined time period after activation of the physical input mechanism; transitioning to a second short-range communication radio payment mode different from the first short-range communication radio payment mode based on a determination that the fingerprint is consistent with the registered fingerprint and a determination that the set of one or more criteria is satisfied; and unlocking the device based on a determination that the fingerprint is consistent with the registered fingerprint and a determination that the set of one or more criteria is not satisfied.

[0013] According to some embodiments, a method is performed at an electronic device having a short-range communication radio and a physical input structure including an integrated biometric sensor. When the electronic device is locked and in a first short-range communication radio payment mode: detecting a fingerprint using the integrated biometric sensor; determining whether the fingerprint is consistent with a registered fingerprint; determining whether a set of one or more criteria is satisfied, wherein the set of one or more criteria includes criteria satisfied when the physical input mechanism is activated within a first predetermined time period after the fingerprint is detected using the biometric sensor; unlocking the device based on a determination that the fingerprint is consistent with the registered fingerprint and a determination that the set of one or more criteria is not satisfied; and based on a determination that the set of one or more criteria is satisfied: determining whether the physical input mechanism is reactivated within a second predetermined time period after activation of the physical input mechanism; unlocking the device based on a determination that the physical input mechanism is not reactivated within the second predetermined time period and a determination that the fingerprint is consistent with the registered fingerprint; and transitioning to a second short-range communication radio payment mode different from the first short-range communication radio payment mode based on a determination that the physical input mechanism is reactivated within the second predetermined time period and a determination that the fingerprint is consistent with the registered fingerprint.

[0014] The executable instructions for performing these functions are optionally included in non-volatile computer readable storage media or other computer program products configured for execution by one or more processors. The executable instructions for performing these functions are optionally included in transient computer readable storage media or other computer program products configured for execution by one or more processors.

[0015] Thus, the device is provided with more efficient methods and interfaces for conducting payment transactions and linking payment accounts for payment transactions, thereby increasing the effectiveness, efficiency, and user satisfaction of utilizing such devices. These methods and interfaces may supplement or replace other methods for conducting payment transactions and linking payment accounts for payment transactions. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] For a better understanding of the various described embodiments, reference is made below to the description of the embodiments in conjunction with the accompanying drawings, wherein like reference numerals designate corresponding parts in the drawings.

[0017] Figure 1A is a block diagram illustrating a portable multifunction device with a display in accordance with some embodiments.

[0018] Figure 1B is a block diagram illustrating exemplary components for event handling in accordance with some embodiments.

[0019] Figure 2 A portable multifunction device with a touch screen is illustrated in accordance with some embodiments.

[0020] Figure 3 is a block diagram of an exemplary multifunction device with a display in accordance with some embodiments.

[0021] Figure 4A An exemplary user interface for an application menu on a portable multifunction device is illustrated in accordance with some embodiments.

[0022] Figure 4B An exemplary user interface for a multifunction device having a touch-sensitive surface that is separate from the display is illustrated in accordance with some embodiments.

[0023] Figure 5A A personal electronic device is illustrated in accordance with some embodiments.

[0024] Figure 5B is a block diagram illustrating a personal electronic device in accordance with some embodiments.

[0025] Figure 5C Illustrated are example devices connected via one or more communication channels to complete a payment transaction in accordance with some embodiments.

[0026] Figure 6A-Figure 6O An exemplary user interface for conducting a payment transaction is illustrated in accordance with some embodiments.

[0027] Figure 7 is a flow chart illustrating a method for conducting a payment transaction according to some embodiments.

[0028] Figure 8A-8K Illustrated are exemplary techniques and user interfaces for conducting payment transactions using a short-range communications radio in accordance with some embodiments.

[0029] Fig. 9 is a flow chart illustrating a method for conducting a payment transaction using a short-range communication radio according to some embodiments.

[0030] Figures 10A-10I Illustrated is an exemplary user interface for linking a payment account to an electronic device in accordance with some embodiments.

[0031] Fig.11 is a flow chart illustrating a method for linking a payment account to an electronic device according to some embodiments.

[0032] Fig.12 A functional block diagram according to some embodiments is illustrated.

[0033] Figures 13A-13E Illustrated are exemplary techniques and user interfaces for enabling an electronic device to engage in payment transactions in accordance with some embodiments.

[0034] Fig.14 is a flow chart illustrating a method for enabling an electronic device to participate in a payment transaction in accordance with some embodiments.

[0035] Figure 15A-15E Illustrated are exemplary techniques and user interfaces for enabling an electronic device to engage in payment transactions in accordance with some embodiments.

[0036] Fig.16 is a flow chart illustrating a method for enabling an electronic device to participate in a payment transaction in accordance with some embodiments.

[0037] Figure 17-Figure 18 A functional block diagram according to some embodiments is illustrated. DETAILED DESCRIPTION

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

[0039] Method 700( Figure 6A-6O , Figure 7 ), Method 900( Figures 8A-8K , Fig. 9 ), method 1100( Figures 10A-10I , Fig.11 ), method 1400( Figures 13A-13E , Fig.14 ) and method 1600( Figures 15A-15E , Fig.16 ) may be incorporated into each other. Among other things, U.S. Provisional Patent Application Serial No. 62 / 004,886 (reference number P22848USP1), filed on May 29, 2014, entitled “USER INTERFACE FOR PAYMENTS” (the “'886 Application”) and co-pending U.S. Provisional Patent Application Serial No. 62 / 047,545 (reference number P22848USP1), filed on September 8, 2014, entitled “USER INTERFACE FOR PAYMENTS” (the “'545 Application”), the technology of which is discussed below, may be incorporated.

[0040] For example, method 600 of the '886 application ( Figures 6A-6C ), Method 800( Figures 8A-8B ), Method 1000( Figures 10A-10B ) and method 1200( Fig.12 Aspects of the '545 application may be incorporated into each other and into method 600 (FIG. 6), method 800 (FIG. 8), method 1000 (FIG. 10), method 1200 (FIG. 11), and method 1210 (FIG. 122). Fig.12 ) and method 1400( Fig.14 ) and may also be incorporated with method 700 ( Figure 7 ), Method 900( Fig. 9 ) and method 1100( Fig.11 Thus, the techniques described with respect to each method of the '886 application, the '545 application, and the present application may be related to each other method of the '886 application, the '545 application, and the present application.

[0041] There is a need for electronic devices with more efficient methods and interfaces for conducting payment transactions and linking payment accounts for payment transactions. These methods and interfaces reduce the cognitive burden on users accessing event notifications, thereby enhancing productivity. Further, such techniques can reduce processor and battery power that would otherwise be wasted on redundant user input.

[0042] under, Figure 1A to Figure 1B , Figure 2 , Figure 3 and FIG. 4A to FIG. 4B as well as FIG. 5A to FIG. 5B Example devices are provided for performing techniques for conducting payment transactions and linking payment accounts for payment transactions. Figure 6A-6O , 8A-8K, 10A-10I, 13A-13D and 15A-15D illustrate exemplary techniques and user interfaces for conducting payment transactions and linking payment accounts. The user interfaces in the figures are also used to illustrate the processes described below, including Figure 7 , 9 , 11, 14 and 16.

[0043] 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 may be referred to as a second touch, and similarly, a second touch may be referred to as 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.

[0044] The terms used in the description of the various described embodiments are used herein only to describe specific embodiments and are not intended to be limiting. The singular forms "one", "an" and "said" used in the description of the various described embodiments and the appended claims are intended to also include plural forms, unless the context clearly indicates otherwise. It should also be understood that the term "and / or" used herein refers to and encompasses any item in one or more items of the associated listed items and all possible combinations. It should be further understood that the terms "include", "have", "include" and / or "contain" when used in this specification specify the presence of features, wholes, steps, operations, elements and / or parts, but do not exclude the presence or addition of one or more other features, wholes, steps, operations, elements, components and / or combinations thereof.

[0045] The term "if" may be interpreted to mean "when" or "upon" or "in response to determining" or "in response to detecting," depending on the context. Similarly, the phrase "if it is determined" or "if [certain condition or event] is detected" may be interpreted to mean "upon determination" or "in response to determining" or "upon detecting [certain condition or event]" or "in response to detecting [certain condition or event]," depending on the context.

[0046] Embodiments of electronic devices, user interfaces for such devices, and associated processes for using such devices are described. In some embodiments, the device is a portable communication device (such as a mobile phone) that also includes other functions, such as PDA and / or music player functions. Exemplary embodiments of portable multifunction devices include, but are not limited to, the Apple Computer, Inc. from Cupertino, California. iPod and Device. Other portable electronic devices such as laptop computers or tablet computers with touch-sensitive surfaces (e.g., touch screen displays and / or touch pads) may also be 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).

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

[0048] The device can support various applications, such as one or more of the following applications: drawing application, presentation application, word processing application, website creation application, disk authoring application, spreadsheet application, game application, telephone application, video conferencing application, email application, instant messaging application, exercise support application, photo management application, digital camera application, digital video recorder application, web browsing application, digital music player application and / or digital video player application.

[0049] Various applications executed on the device optionally use at least one common physical user interface device, such as a touch-sensitive surface. One or more functions of the touch-sensitive surface and corresponding information displayed on the device are optionally adjusted and / or changed from one application to the next and / or within the respective applications. In this way, the common physical architecture of the device (such as a touch-sensitive surface) optionally supports various applications through a user interface that is intuitive and transparent to the user.

[0050] Attention will now be turned 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 in accordance with some embodiments. Touch-sensitive display 112 is sometimes referred to as a "touch screen" and is sometimes considered or referred to as a touch-sensitive display system. Device 100 includes memory 102 (which optionally includes one or more computer-readable storage media), memory controller 122, one or more processing units (CPUs) 120, peripheral interfaces 118, RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, input / output (I / O) subsystem 106, other input or control devices 116, and external ports 124. Device 100 optionally includes one or more optical sensors 164. Device 100 optionally includes one or more contact intensity sensors 165 for detecting contact intensity on device 100 (e.g., a touch-sensitive surface, such as touch-sensitive display system 112 of device 100). Device 100 optionally includes one or more tactile output generators 167 for generating tactile output on device 100 (e.g., generating tactile output on a touch-sensitive surface such as touch-sensitive display system 112 of device 100 or touch pad 335 of device 300). These components optionally communicate via one or more communication buses or signal lines 103.

[0051] As used in the 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 (proxy) for the force or pressure of a contact on the touch-sensitive surface. The contact intensity 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). Optionally, various methods and various sensors or combinations of sensors are used to determine (or measure) the contact intensity. For example, one or more force sensors below or adjacent to the touch-sensitive surface are optionally used to measure the force at various points on the touch-sensitive surface. In some implementations, the force measurements from multiple force sensors are combined (e.g., a weighted average) to determine an estimated force of the contact. Similarly, the pressure-sensitive tip of the stylus is optionally used to determine the pressure of the stylus on the touch-sensitive surface. Alternatively, the size of and / or changes to the contact area detected on the touch-sensitive surface, the capacitance of and / or changes to the touch-sensitive surface in proximity to the contact, and the resistance of and / or changes to the touch-sensitive surface in proximity to the contact are optionally used as a surrogate for the force or pressure of the contact on the touch-sensitive surface. In some implementations, the surrogate measurement for contact force or contact 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 surrogate measurement). In some implementations, the surrogate measurement for contact force or contact pressure is converted into an estimated force or estimated pressure, and the estimated force or estimated 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 contact intensity as an attribute of user input allows user access to additional device functionality that would otherwise be impossible to access by a user on a reduced size device (e.g., via a touch-sensitive display) with limited real estate for displaying affordances and / or receiving user input (e.g., via a touch-sensitive display, touch-sensitive surface, or physical / mechanical controls such as knobs or buttons).

[0052] As used in the 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 gravity 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 surface (e.g., a finger, palm, or other part of a user's hand) that is sensitive to touch, the tactile output generated by the physical displacement will be interpreted by the user as a tactile sensation corresponding to a change in the physical properties of the device or device component that is felt. For example, the movement of a touch-sensitive surface (e.g., a touch-sensitive display or a touchpad) is optionally interpreted by the user as a "press click" or "lift click" of a physical actuator button. In some cases, even when there is no movement of a physical actuator button associated with a touch-sensitive surface that is physically pressed (e.g., displaced) by the user's movement, the user will feel a tactile sensation, such as a "press click" or "lift click". As another example, even when the smoothness of the touch-sensitive surface does not change, the movement of the touch-sensitive surface is optionally interpreted or felt by the user as the "roughness" of the touch-sensitive surface. While this interpretation of touch by a user will be influenced by the user's personalized sensory perception, there are many sensory perceptions of point touch that are common to most users. Therefore, when a tactile output is described as corresponding to a particular sensory perception of a user (e.g., "lift-click," "press-click," "roughness"), unless otherwise explicitly indicated, the tactile output produced will correspond to a physical displacement of the device or a component thereof that will produce the described sensory perception for a typical (or average) user.

[0053] It should be understood that device 100 is only one example of a portable multifunction device and that device 100 may optionally have more or fewer components than shown, may optionally combine two or more components, or may optionally have a different configuration or arrangement of components. Figure 1A The various components shown in the drawings may be implemented in hardware, software, or a combination of both hardware and software, including one or more signal processing and / or application specific integrated circuits.

[0054] The memory 102 may include one or more computer-readable storage media. The computer-readable storage medium may be tangible and non-volatile. The memory 102 may include high-speed random access memory, and may also include non-volatile memory, such as one or more disk storage devices, flash memory devices, or other non-volatile solid-state memory devices. The memory controller 122 may control access to the memory 102 by other components of the device 100.

[0055] The peripheral interface 118 may be used to couple the input and output peripherals 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 for the device 100 and to process data. In some embodiments, the peripheral interface 118, the CPU 120, and the memory controller 122 may be implemented on a single chip, such as the chip 104. In some other embodiments, they may be implemented on separate chips.

[0056] RF (radio frequency) circuit device 108 receives and sends RF signals, also known as electromagnetic signals. RF circuit device 108 converts electrical signals into electromagnetic signals / converts electromagnetic signals into electrical signals, and communicates with communication networks and other communication devices via electromagnetic signals. RF circuit device 108 optionally includes known circuit devices for performing these functions, including but not limited to: antenna system, RF transceiver, one or more amplifiers, tuner, one or more oscillators, digital signal processor, CODEC chipset, customer identification module (SIM) card, memory, etc. RF circuit device 108 optionally communicates with the Internet, also known as the World Wide Web (WWW), intranets and / or wireless networks such as cellular telephone networks, wireless local area networks (LANs) and / or metropolitan area networks (MANs), and other devices through wireless communication. RF circuit device 108 optionally includes known circuit devices for detecting near field communication (NFC) fields, such as through short-range communication radios. Wireless communication may optionally use any of a variety of communication standards, protocols, and technologies, including, but not limited to, Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), High Speed ​​Downlink Packet Access (HSDPA), High Speed ​​Uplink Packet Access (HSUPA), Evolution Data Only (EV-DO), HSPA, HSPA+, Dual Cell HSPA (DC-HSPDA), Long Term Evolution (LTE), Near Field Communication (NFC), Wideband Code Division Multiple Access (W-CDMA), Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Bluetooth, Bluetooth Low Energy (BTLE), Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11n, and / or IEEE 802.11ac), Voice over Internet Protocol (VoIP), Wi-MAX, protocols for email (e.g., Internet Message Access Protocol (IMAP) and / or Post Office Protocol (POP)), instant messaging (e.g., Extensible Messaging and Presence Protocol (XMPP), Session Initiation Protocol for Instant Messaging and Presence Leveraged Extensions (SIMPLE), Instant Messaging and Presence Services (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.

[0057] The audio circuit device 110, the speaker 111 and the microphone 113 provide an audio interface between the user and the device 100. The audio circuit device 110 receives audio data from the peripheral interface 118, converts the audio data into an electrical signal, and transmits the electrical signal to the speaker 111. The speaker 111 converts the electrical signal into sound waves audible to humans. The audio circuit device 110 also receives the electrical signal converted from the sound wave by the microphone 113. The audio circuit device 110 converts the electrical signal into audio data and transmits the audio data to the peripheral interface 118 for processing. The audio data can be obtained from the memory 102 and / or the RF circuit device 108 and / or transmitted to the memory 102 and / or the RF circuit device 108 through the peripheral interface 118. In some embodiments, the audio circuit device 110 also includes a headphone jack (e.g., Figure 2 The headphone jack provides an interface between the audio circuit device 110 and a removable audio input / output peripheral device, such as an output-only receiver or a headset capable of both output (e.g., a single or dual-ear receiver) and input (e.g., a microphone).

[0058] The I / O subsystem 106 couples input / output peripherals on the device 100, such as the touch screen 112 and other input control devices 116, to the peripherals interface 118. The I / O subsystem 106 optionally includes a display controller 156, an optical sensor controller 158, an intensity sensor controller 159, a tactile feedback controller 161, and one or more input controllers 160 for other input or control devices. The one or more input controllers 160 receive / send electrical signals from / to other input or control devices 116. Other input or control devices 116 optionally include physical buttons (e.g., push buttons, rocker buttons, etc.), dials, slide switches, joysticks, click wheels, etc. In some alternative embodiments, the (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 pointing 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).

[0059] A quick press of the push button can disengage the lock of the touch screen 112 or begin the process of using gestures on the touch screen to unlock the device, as described in U.S. Patent Application No. 11 / 322,549, entitled "Unlocking a Device by Performing Gestures on an Unlock Image," filed on December 23, 2005, U.S. Patent No. 7,657,849, which are incorporated herein by reference in their entirety. A longer press of the push button (e.g., 206) can power on or off the device 100. The user can customize the function of one or more of the buttons. The touch screen 112 is used to implement virtual buttons or soft buttons and one or more soft keyboards.

[0060] 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 of the above (collectively referred to as "graphics"). In some embodiments, some or all of the visual output may correspond to user interface objects.

[0061] The touch screen 112 has a touch-sensitive surface, sensor, or set of sensors that accepts input from a user based on haptic and / or tactile 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 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.

[0062] 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 to detect contact and any movement or interruption of contact, including but not limited to: capacitive, resistive, infrared, and surface acoustic wave technologies, as well as other proximity sensor arrays or other elements for determining one or more points of contact with the touch screen 112. In an exemplary embodiment, projected mutual capacitance sensing technology is used, such as that available from Apple Inc. of Cupertino, California. and iPod Technology found in.

[0063] In some embodiments of touch screen 112, the touch-sensitive display may be similar to the multi-touch sensitive touch pad described in U.S. Pat. Nos. 6,323,846 (Westerman et al.), 6,570,557 (Westerman et al.), and / or 6,677,932 (Westerman), and / or U.S. Patent Publication 2002 / 0015024A1, each of which is incorporated herein by reference in its entirety. However, touch screen 112 displays visual output from device 100, whereas a touch-sensitive track pad does not provide visual output.

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

[0065] 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 make contact with the touch screen 112 using any suitable object or appendage, such as a stylus, finger, etc. In some embodiments, the user interface is designed to work primarily through finger-based contacts and gestures, which may be less precise than stylus-based input due to the larger contact area of ​​the finger on the touch screen. In some embodiments, the device translates the rough finger-based input into a precise pointer / cursor position or command to perform the action desired by the user.

[0066] In some embodiments, in addition to the touch screen, the device 100 may also 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 may be a touch-sensitive surface separate from the touch screen 112 or an extension of the touch-sensitive surface formed by the touch screen.

[0067] 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 charging system, a power failure detection circuit, a power converter or inverter, a power status indicator (e.g., a light emitting diode (LED)), and any other components related to the generation, management, and distribution of power in a portable device.

[0068] The device 100 may also include one or more optical sensors 164 . Figure 1A An optical sensor coupled to the controller 158 of the optical sensor 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 from the environment projected through one or more lenses and converts the light into data representing an image. In combination with the imaging module 143 (also referred to as a camera module), the optical sensor 164 can capture a still image or a video. In some embodiments, the optical sensor is located on the back of the device 100, opposite 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 and / or video image acquisition. In some embodiments, the optical sensor is located on the front of the device so that the user image can be acquired for the video conference while the user views other video conference participants on the touch screen display. 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 and / or video image acquisition.

[0069] Device 100 optionally also includes one or more contact intensity sensors 165 . Figure 1A A contact force sensor is shown coupled to force sensor controller 159 in I / O subsystem 106. Contact force sensor 165 optionally includes one or more piezoresistive strain gauges, capacitive force sensors, electrostatic 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 a contact on a touch-sensitive surface). Contact force sensor 165 receives contact force information (e.g., pressure information or a substitute for pressure information) from the environment. In some embodiments, at least one contact force sensor is juxtaposed or proximate 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 back of device 100, opposite touch screen display 112 located on the front of device 100.

[0070] 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 U.S. patent application Ser. No. 11 / 241,839, entitled “Proximity Detector In Handheld Device,” U.S. patent application Ser. No. 11 / 240,788, entitled “Proximity Detector In Handheld Device,” U.S. patent application Ser. No. 11 / 620,702, entitled “Using Ambient Light Sensor To Augment Proximity Sensor Output,” U.S. patent application Ser. No. 11 / 586,862, entitled “Automated Response To And Sensing Of User Activity In Portable Devices,” and U.S. patent application Ser. No. 11 / 638,251, entitled “Methods And Systems For Automatic Configuration Of Peripherals,” which are incorporated herein by reference in their entirety. In some embodiments, when the multifunction device is near the user's ear (eg, when the user is making a phone call), the proximity sensor turns off and the touch screen 112 is disabled.

[0071] Device 100 optionally also includes one or more tactile output generators 167 . Figure 1A A 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 that converts electrical energy into linear motion (such as a motor, solenoid, electrically active polymer, piezoelectric actuator, electrostatic actuator, or other tactile output generating component (e.g., a component that converts an electrical signal into a tactile output on the device)). The contact force sensor 165 receives tactile feedback generation instructions from the tactile feedback module 133 and generates 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 juxtaposed or proximate to a touch-sensitive surface (e.g., touch-sensitive display system 112) and optionally generates tactile output by moving the touch-sensitive surface vertically (e.g., in / out of the surface of the device 100) or laterally (reciprocating in the same plane as the surface of the device 100). In some embodiments, at least one tactile output generator sensor is located on the back of device 100 , opposite touch screen display 112 located on the front of device 100 .

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

[0073] 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, as Figure 1A and Figure 3 As shown, in some embodiments, the memory 102 ( Figure 1A ) or memory 370( Figure 3 ) stores device / global internal state 157. Device / global internal state 157 includes one or more of the following: active application state, indicating which applications (if any) are currently active; display state, indicating what applications, views, and other information occupy various areas of the touch screen display 112; sensor state, including information obtained from the device's various sensors and input control devices 116; and position information related to the device's position and / or posture.

[0074] 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 facilitates communication between various hardware and software components.

[0075] Communications module 128 facilitates communications with other devices over one or more external ports 124 and also includes various software components for processing data received by RF circuitry 108 and / or external ports 124. External ports 124 (e.g., Universal Serial Bus (USB), FireWire, etc.) are suitable for coupling directly to other devices or indirectly to other devices via a network (e.g., the Internet, wireless LAN, etc.). In some embodiments, the external ports are used in conjunction with (trademark of Apple Inc.) devices.

[0076] The contact / motion module 130 optionally detects contact with the touch screen 112 (in combination 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 the detection of contact, such as determining whether contact has occurred (e.g., detecting a finger press event), determining the contact strength (e.g., the force or pressure of the contact, or a substitute for the force or pressure of the contact), determining whether there is movement of the contact and tracking the movement across 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 interruption). The contact / motion module 130 receives contact data from the touch-sensitive surface. Determine the movement of the contact point (which is represented by a series of contact data), optionally including determining the rate (magnitude), velocity (magnitude and direction) and / or acceleration (change in magnitude and / or direction) of the contact point. These operations are optionally applied to a single contact (e.g., one finger contact) or multiple simultaneous contacts (e.g., "multi-touch" / multiple finger contacts). In some embodiments, contact / motion module 130 and display controller 156 detect contact on a touch pad.

[0077] In some embodiments, 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 are adjusted without changing the physical hardware of device 100). For example, a mouse "click" threshold for a touchpad or touchscreen can be set to any large range of a predetermined threshold range without changing the touchpad or touchscreen display hardware. In addition, in some embodiments, a user of the device is provided with a software setting for adjusting one or more of the intensity thresholds in a set of intensity thresholds (e.g., adjusting single and / or multiple intensity thresholds at once via a system-level click "intensity" parameter).

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

[0079] 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 effects (e.g., brightness, transparency, saturation, contrast, or other visual attributes) of the displayed graphics. As used herein, the term "graphics" includes any object that can be displayed to a user, including but not limited to: text, web pages, icons (such as user interface objects including soft keys), digital images, videos, animations, etc.

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

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

[0082] Text input module 134, which may be a component of graphics module 132, provides a soft keyboard for entering text into various applications (eg, contacts 137, email 140, IM 141, browser 147, and any other application requiring text input).

[0083] The GPS module 135 determines the location of the device and provides this information for use by various applications (e.g., to the phone 138 for use in location-based dialing; to the camera 143 as picture / video metadata; and to location-based service applications such as weather widgets, local yellow pages widgets, and map / navigation widgets).

[0084] Application 136 may include the following modules (or instruction sets), or a subset or superset thereof:

[0085] Contacts module 137 (sometimes referred to as an address book or contact list);

[0086] Telephone module 138;

[0087] Video conferencing module 139;

[0088] Email client module 140

[0089] Instant messaging (IM) module 141;

[0090] Exercise support module 142;

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

[0092] Image management module 144;

[0093] Video player module;

[0094] Music player module;

[0095] Browser module 147;

[0096] Calendar module 148;

[0097] 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 obtained by the user, and a user-created widget 149-6;

[0098] A widget creator module 150, used to create a user-created widget 149-6;

[0099] Search module 151;

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

[0101] Memo module 153;

[0102] Map module 154; and / or

[0103] Online video module 155.

[0104] Examples of other applications 136 that may be stored in memory 102 include other word processing applications, other image editing applications, drawing applications, presentation applications, JAVA-enabled applications, encryption, digital rights management, voice recognition, and voice replication.

[0105] In combination 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 (for example, in the application internal state 192 of the contact module 137 stored 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 images with names; categorizing and sorting names; providing a telephone number or email address to initiate and / or facilitate communication via telephone 138, video conferencing 139, email 140 or instant messaging 141, etc.

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

[0107] In combination with the RF circuit device 108, the audio circuit device 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.

[0108] In conjunction with RF circuit device 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.

[0109] In conjunction with the RF circuit device 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 entering a character sequence corresponding to an instant message, for modifying previously entered characters, for transmitting a corresponding instant message (e.g., using a short message service (SMS) or multimedia message service (MMS) protocol for telephone-based instant messaging, or using XMPP, SIMPLE, or IMPS for Internet-based instant messaging), for receiving instant messages, and for 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 telephone-based messages (e.g., messages sent using SMS or MMS) and Internet-based messages (e.g., messages using XMPP, SIMPLE, or IMPS).

[0110] In combination with the RF circuit device 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 exercise support module 142 includes executable instructions for creating exercises (e.g., with time, distance and / or calorie burn goals); communicating with exercise sensors (exercise equipment); receiving exercise sensor data; executable instructions for calibrating sensors for monitoring exercise; executable instructions for selecting and playing music for exercise; and executable instructions for displaying, storing and transmitting exercise data.

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

[0112] 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 manipulating, annotating, deleting, presenting (e.g., in a digital slide show or album), and storing still and / or video images.

[0113] In combination with the RF circuit device 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 according to user instructions (including searching, linking, receiving and displaying web pages or multiple parts of web pages and attachments and other files linked to the web pages).

[0114] In combination with the RF circuit device 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 lists, etc.) in accordance with user instructions.

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

[0116] In conjunction with RF circuitry 108, touch screen 112, display controller 156, touch / motion module 130, graphics module 132, text input module 134, and browser module 147, widget creator module 150 may be used by a user to create widgets (e.g., convert a user-specified portion of a web page into a widget).

[0117] 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, image, video and / or other files that match one or more search criteria (e.g., one or more user-specified search terms) in accordance with user instructions.

[0118] In conjunction with touch screen 112, display controller 156, contact / motion module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, and browser module 147, video and music player module 152 includes executable instructions that allow a user to download and play back recorded music and other sound files stored in one or more file formats (such as MP3 or AAC files), and includes executable instructions for displaying, presenting, or otherwise playing back video (e.g., on touch screen 112 or on a display connected externally 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.).

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

[0120] In combination with the RF circuit device 108, the touch screen 112, the display controller 156, the touch / motion module 130, the graphics module 132, the text input module 134, the GPS module 135 and the browser module 147, the map module 154 can be used to receive, display, modify and store maps and data associated with the maps (e.g., driving directions; data about stores and other points of interest at or near a particular location; and other location-based data) in accordance with user instructions.

[0121] In conjunction with touch screen 112, display controller 156, contact / motion module 130, graphics module 132, audio circuit device 110, speaker 111, RF circuit device 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 a particular online video (e.g., on the touch screen or on a display connected externally via external port 124), send an email with a link to a particular online video, and 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 for the link sent to the particular online video. Additional description of online video applications can be found in U.S. Provisional Patent Application No. 60 / 936,562, filed on June 20, 2007, entitled “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos,” and U.S. Patent Application No. 11 / 968,067, filed on December 31, 2007, entitled “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos,” the entire texts of which are hereby incorporated by reference in their entirety.

[0122] Each of the modules and applications identified above corresponds to an instruction set for performing one or more of the functions described above and the methods described in this application (e.g., the computer-implemented methods and other information processing methods described herein). These modules (e.g., instruction sets) need not be implemented as separate software programs, processes, or modules, and therefore various subsets of these modules may be combined or 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 other modules and data structures not described above.

[0123] In some embodiments, the device 100 is a device that performs operations of a predetermined set of functions on the device exclusively through a touch screen and / or a touch pad. By using the touch screen and / or the touch pad as the primary input control device for operating the device 100, the number of physical input control devices (such as push buttons, dials, etc.) on the device 100 can be reduced.

[0124] The predetermined set of functions performed exclusively through the touch screen and / or touchpad optionally includes navigation between user interfaces. In some embodiments, when the user touches the touchpad, the device 100 is navigated from any user interface on the device 100 display to a home screen, a main screen, or a root menu. In such embodiments, a "menu button" is implemented using a touchpad. In some other embodiments, the menu button is a physical push button or other physical input control device instead of a touchpad.

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

[0126] 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 dispatcher module 174. In some embodiments, application 136-1 includes application internal state 192, which indicates the current application view(s) displayed on touch-sensitive display 112 when the application is active or executing. In some embodiments, device / global content state 157 is used by event classifier 170 to determine which application or applications are 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.

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

[0128] 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, accelerometer(s) 168, and / or microphone 113 (through audio circuitry 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.

[0129] In some embodiments, event monitor 171 sends requests to peripheral interface 118 at predetermined intervals. In response, peripheral interface 118 sends event information. In other embodiments, peripheral interface 118 sends event information only when a significant event occurs (e.g., receiving an input that exceeds a predetermined noise threshold and / or is longer than a predetermined duration).

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

[0131] Hit view determination module 172 provides software routines for determining where a sub-event has occurred in one or more views when touch-sensitive display 112 displays more than one view. A view consists of controls and other elements that a user can see on the display.

[0132] 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 view (of the corresponding application) in which a touch is detected can correspond to a program level in the program or view hierarchy of the application. For example, the lowest level view in which a touch is detected can be referred to as a hit view, and the set of events recognized as correct input can be determined based at least in part on the hit view of the initial touch that started the touch-based gesture.

[0133] Hit view determination module 172 receives information related to sub-events of touch-based gestures. When an application has multiple views organized in a hierarchical structure, hit view determination module 172 identifies the lowest-level view in the hierarchy that should handle the sub-event as the hit view. In most cases, the hit view is the lowest-level view in which the initiating sub-event (e.g., the first sub-event that forms an event or potential event in a sequence of sub-events) 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 that caused it to be identified as the hit view.

[0134] Active event recognizer determination module 173 determines which view or views in 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, including 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 the touch sub-events are completely confined to the area associated with one particular view, views higher in the hierarchy will still remain as actively participating views.

[0135] Event dispatcher module 174 dispatches the event information to an event recognizer (e.g., event recognizer 180). In embodiments including active event recognizer determination module 173, event dispatcher module 174 delivers the event information to the event recognizer determined by active event recognizer determination module 173. In some embodiments, event dispatcher module 174 stores the event information in an event queue for retrieval by a corresponding event receiver 182.

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

[0137] 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 event recognizers 180 are part of an independent module (such as a user interface kit (not shown)), or a higher-level object from which application 136-1 inherits methods and other properties. In some embodiments, 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 191 include one or more corresponding event handlers 190. Likewise, in some embodiments, one or more of the data updater 176 , the object updater 177 , and the GUI updater 178 are included in a corresponding application view 191 .

[0138] A corresponding event identifier 180 receives event information (e.g., event data 179) from event classifier 170 and identifies an event based on the event information. Event identifier 180 includes an event receiver 182 and an event comparator 184. In some embodiments, 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).

[0139] Event receiver 182 receives event information from event classifier 170. The event information includes information about a sub-event (e.g., a touch or touch movement). Depending on the sub-event, the event information also includes additional information, such as the location of the sub-event. When the sub-event involves the movement of a touch, the event information may also include the rate and direction of the sub-event. In some embodiments, the event includes a rotation of the device from one orientation to another (e.g., from portrait to landscape, or vice versa), and the event information includes corresponding information about the current orientation of the device (also referred to as the device posture).

[0140] The event comparator 184 compares the event information with the predefined event or sub-event definition, and determines the event or sub-event based on the comparison, or determines or updates the state of the event or sub-event. In some embodiments, the event comparator 184 includes an event definition 186. The event definition 186 contains the definition of an event (e.g., a predetermined sequence of sub-events), such as event 1 (187-1), event 2 (187-2), etc. In some embodiments, the sub-events in the event 187 include, for example, touch start, touch end, touch movement, touch cancellation, and multi-touch. In one example, the definition of event 1 (187-1) is a double-click on a display object. The double-click, for example, includes a first touch (touch start) of a predetermined stage on the display object, a first lift (touch end) of a predetermined stage, a second touch (touch start) of a predetermined stage on the display object, and a second lift (touch end) of a predetermined stage. In another example, the definition of event 2 (187-2) is a drag on a display object. The drag, for example, includes a touch (or contact) of a predetermined stage on the display object, a movement of the touch on the touch-sensitive display 112, and a lift (touch end) of the touch. In some embodiments, the event also includes information for one or more associated event handlers 190 .

[0141] 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 the user interface object associated with a sub-event. For example, in an application view in which three user interface objects are displayed on touch-sensitive display 112, when a touch is detected on touch-sensitive display 112, event comparator 184 performs a hit test to determine which of the three user interface objects is associated with the touch (sub-event). If each displayed object is associated with a corresponding event handler 190, the event comparator uses the result of the hit test to determine which event handler 190 should be activated. For example, event comparator 184 selects an event handler associated with the sub-event and object that triggered the hit test.

[0142] 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 sequence of sub-events corresponds to the event type of the event identifier.

[0143] When a corresponding event recognizer 180 determines that the sequence of sub-events does not match any event in event definition 186, the corresponding event recognizer 180 enters an event impossible, event failed, or event ended state, after which the corresponding event recognizer 180 ignores subsequent sub-events of the touch-based gesture. 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.

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

[0145] In some embodiments, corresponding event recognizer 180 activates event handler 190 associated with the event when one or more specific sub-events of the event are recognized. In some embodiments, corresponding event recognizer 180 delivers event information associated with the event to event handler 190. Activating event handler 190 is different from sending (or delaying sending) the sub-event to the corresponding hit view. In some embodiments, event recognizer 180 throws a flag associated with the recognized event, and event handler 190 associated with the flag grabs the flag and performs a predetermined process.

[0146] 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 event information to an event handler associated with a series of sub-events or an actively participating view. The event handler associated with a series of sub-events or an actively participating view receives the event information and performs a predetermined process.

[0147] 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 145. In some embodiments, object updater 177 creates and updates data 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.

[0148] 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, data updater 176, object updater 177, and GUI updater 178 are included in two or more software modules.

[0149] It should be understood that the foregoing discussion regarding event processing of user touches on a touch-sensitive display also applies to other forms of user input for operating a multifunction device 100 with an input device, where not all user input is initiated on a touch screen, for example, mouse movements and mouse button presses optionally combined with single or multiple keyboard presses or holds; contact motions on a touch pad (such as taps, drags, scrolls, etc.); stylus input, movement of the device; voice commands; detected eye movements, biometric input; and / or any combination of the above, optionally used as input corresponding to sub-events defining an event to be recognized.

[0150] Figure 2 A portable multifunction device 100 with a touch screen 112 is illustrated in accordance with some embodiments. The touch screen optionally displays one or more graphics within a user interface (UI) 200. In this embodiment and other embodiments described below, a user can select one or more graphics by making gestures to the graphics (e.g., with one or more fingers 202 (not drawn to scale in the figure) or one or more styluses (not drawn to scale in the figure)). In some embodiments, selection of the one or more graphics occurs when the user breaks contact with the one or more graphics. In some embodiments, the gesture optionally includes one or more taps, one or more swipes (from left to right, from right to left, up and / or down), and / or rotation of a finger that has made contact with the device 100 (from right to left, from left to right, up and / or down). In some implementations or situations, unintentional contact with a graphic does not select the graphic. For example, a swipe gesture that sweeps across an application icon optionally does not select the corresponding application when the gesture corresponding to the selection is a tap.

[0151] The device 100 may also include one or more physical buttons, such as a “home” or menu button 204. As previously described, the menu button 204 may be used to navigate to any application 136 in the application collection that may be executed on the device 100. Alternatively, in some embodiments, the menu button is implemented as a soft key in a GUI displayed on the touch screen 112.

[0152] In some embodiments, the device 100 includes a touch screen 112, a menu button 204, a push button 206 for turning the device power on / off and locking the device, and (one or more) volume adjustment buttons 208, a subscriber identity module (SIM) card slot 210, a headphone interface 212, and a docking / charging external port 124. The push button 206 is optionally used to turn the device power on / off by pressing the button and keeping the button in a pressed state for a predetermined time interval; to lock the device by pressing the button and releasing the button before a predetermined time interval passes; and / or to 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 the microphone 113. The device 100 optionally also includes one or more contact intensity sensors 165 for detecting contact intensity on the touch screen 112 and / or one or more tactile output generators 167 for generating tactile outputs to a user of the device 100.

[0153] Figure 3 300 is a block diagram of an exemplary multifunction device with a display and a touch-sensitive surface according to some embodiments. Device 300 need not be portable. In some embodiments, device 300 is a laptop 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 gaming system, or a control device (e.g., a home or industrial controller). Device 300 typically includes one or more processing units (CPUs) 310, one or more network or other communication interfaces 360, a memory 370, and one or more communication buses 320 for interconnecting these components. Communication bus 320 optionally includes circuitry (sometimes referred to as a chipset) that interconnects and controls communication between system components. Device 300 includes an input / output (I / O) interface 330, which includes a display 340, which is typically a touch screen display. Input / output interface 330 also optionally includes a keyboard and / or mouse (or other pointing device) 350 and a touchpad 355, a tactile output generator 357 for generating tactile output on device 300 (e.g., similar to the above referenced appendix). Figure 1A (multiple) tactile output generators 167 described above), sensors 359 (e.g., similar to those described in the above referenced appendix) Figure 1A1). 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 may optionally include one or more storage devices remote from CPU(s) 310. In some embodiments, memory 370 stores programs, modules, and data structures similar to, or a subset of, the programs, modules, and data structures stored in memory 102 of portable multifunction device 100 (FIG. 1). In addition, memory 370 optionally stores additional programs, modules, and data structures that are not present in memory 102 of portable multifunction device 100. For example, the memory 370 of the device 300 may optionally store a drawing module 380, a presentation module 382, ​​a word processing module 384, a website creation module 386, a disk authoring module 388, and / or a spreadsheet module 390, while the portable multifunction device 100 ( Figure 1A )'s memory 102 optionally does not store these modules.

[0154] Figure 3 Each element 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 functions as described above. The above-mentioned modules or programs (e.g., instruction sets) do not need to be implemented as separate software programs, processes or modules, so in various embodiments, various subsets of these modules can be combined or otherwise rearranged. 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.

[0155] Attention will now be turned to embodiments of user interfaces that may be implemented on portable multifunction device 100, for example.

[0156] Figure 4A An exemplary user interface for an application menu on portable multifunction device 100 is illustrated in accordance with some embodiments. A similar user interface may be implemented on device 300. In some embodiments, user interface 400 includes the following elements, or a subset or superset thereof:

[0157] Signal strength indicators 402 for wireless communication(s), such as cellular signals and Wi-Fi signals;

[0158] Time 404;

[0159] Bluetooth indicator 405;

[0160] Battery status indicator 406;

[0161] Tray 408, with icons for frequently used applications such as:

[0162] o an icon 416 for the phone module 138, labeled "Phone," which optionally includes an indicator 414 of the number of missed calls or voice messages;

[0163] o an icon 418 for the email client module 140, labeled "Mail," which optionally includes an indicator 410 of the number of unread emails;

[0164] o An icon 420 for the browser module 147, labeled "Browser"; and

[0165] o Icon 422 for video and music player module 152, also referred to as iPod (trademark of Apple Inc.) module 152, labeled “iPod”; and

[0166] Icons for other applications, such as:

[0167] o Icon 424 for IM module 141, labeled "Message";

[0168] o Icon 426 for calendar module 148, labeled "Calendar";

[0169] o Icon 42 for image management module 144, labeled "Photos";

[0170] o Icon 430 for camera module 143, labeled “Camera”;

[0171] o Icon 432 for online video module 155, labeled "Online Video";

[0172] o Icon 434 for the stock widget 149-2, labeled "Stocks";

[0173] o Icon 436 for the map module 154, labeled "Map";

[0174] o Icon 438 for the weather widget 149-1, labeled "Weather";

[0175] o Icon 440 for the alarm clock widget 149-4, labeled "Clock";

[0176] o Icon 442 for exercise support module 142, labeled "Exercise Support";

[0177] o Icon 444 for memo module 153, labeled "Memo";

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

[0179] It should be understood Figure 4A The icon labels illustrated in are exemplary only. For example, icon 422 for video and music player module 152 may optionally be labeled "Music" or "Music Player". Other labels may optionally be used for individual application icons. In some embodiments, the label for a respective application icon includes the name of the application corresponding to the respective application icon. In some embodiments, the label for a particular application icon is different from the name of the application corresponding to the particular application icon.

[0180] Figure 4B A touch-sensitive surface 451 (eg, touch screen display 112) is shown having a separate touch-sensitive surface 451 from a display 450 (eg, touch screen display 112). Figure 3 A device (e.g., a tablet or touch pad 355) Figure 3 Device 300 also optionally includes one or more contact intensity sensors (e.g., one or more sensors of sensor 357) for detecting contact intensity on touch-sensitive surface 451 and / or one or more tactile output generators 359 for generating tactile output to a user of device 300.

[0181] Although some examples will be given with reference to input on a touch screen display 112 (where the touch sensitive surface is combined with the display), in some embodiments, such as Figure 4B As shown, the device detects input on a touch-sensitive surface that is separate from the display. In some embodiments, the touch-sensitive surface (e.g., Figure 4B 451) has a coordinate corresponding to the main coordinate axis (e.g., Figure 4B 453) of the main coordinate 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 In this way, when the touch-sensitive surface is in contact with the display of the multifunction device (e.g., Figure 4B 450) is separated by the device on the touch-sensitive surface (e.g., Figure 4B 451 in ) detected on the user input (eg, contact 460 and contact 462 and its movement) is used by the device to manipulate the user interface on the display. It should be understood that similar methods are optionally used for other user interfaces described herein.

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

[0183] Figure 5A An exemplary personal electronic device 500 is shown. Device 500 includes a body 502. In some embodiments, device 500 may include a device 502 such as device 100 or device 300 (eg, Figures 1A-4B ) may include some or all of the features described in the foregoing description. In some embodiments, device 500 has a touch-sensitive display screen 504, hereinafter referred to as touch screen 504. Alternatively, or in addition to touch screen 504, device 500 has a display and a touch-sensitive surface. As with device 100 and device 300, in some embodiments, touch screen 504 (or touch-sensitive surface) may have one or more intensity sensors for detecting the intensity of contact (e.g., touch) being applied. The one or more intensity sensors of the touch screen 504 (or touch-sensitive surface) may provide output data representing the intensity of the touch. The user interface of device 500 may respond to touches based on their intensity, which means that touches of different intensities may invoke different user interface operations on device 500.

[0184] Technology for detecting and processing touch intensity can be found, for example, in the following related applications: International patent application serial number PCT / US2013 / 040061, filed on May 8, 2013, entitled “Device, Method, and Graphical User Interface for Displaying User Interface Objects Corresponding to an Application,” and International patent application serial number PCT / US2013 / 069483, filed on November 11, 2013, entitled “Device, Method, and Graphical User Interface for Transitioning Between Touch Input to Display Output Relationships,” which are incorporated herein by reference in their entirety.

[0185] In some embodiments, the device 500 has one or more input mechanisms 506 and 508. If included, the input mechanisms 506 and 508 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. If included, these attachment mechanisms can allow the device 500 to be attached to, for example, hats, glasses, earrings, necklaces, shirts, jackets, bracelets, watchbands, fobs, pants, belts, shoes, handbags, backpacks, etc. These attachment mechanisms can allow the device 500 to be worn by a user.

[0186] Figure 5B An exemplary personal electronic device 500 is depicted. 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 component 514 with one or more computer processors 516 and a memory 518. The I / O component 514 can be connected to a display 504, which can have a touch-sensitive component 522 and optionally a touch-intensity-sensitive component 524. In addition, the I / O component 514 can be connected to a communication unit 530 using Wi-Fi, Bluetooth, near field communication (NFC), cellular, and / or other wireless communication technologies to receive application and operating system data. Device 500 may include input mechanisms 506 and / or 508. The input mechanism 506 can be, for example, a rotatable input device or a depressible and rotatable input device. In some examples, the input mechanism 508 can be a button.

[0187] 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 component 514.

[0188] The memory 518 of the personal electronic device 500 may be a non-volatile computer-readable storage medium for storing computer-executable instructions that, when executed by one or more computer processors 516, may cause the computer processors to perform the techniques described above, including process 700 ( Figure 7 )、900( Fig. 9 )、1100( Fig.11 )、1400( Fig.14 ) and 1600( Fig.16 ). Computer-executable instructions may also be stored and / or transmitted within any non-volatile computer-readable storage medium for use by, or in conjunction with, an instruction execution system, apparatus, or device, such as a computer-based system, a system containing a processor, or other system that can obtain instructions from an instruction execution system, apparatus, or device and execute the instructions. For the purposes of this document, a "non-volatile computer-readable storage medium" may be any medium that tangibly contains or stores computer-executable instructions that may be used by, or in conjunction with, an instruction execution system, apparatus, or device. Non-volatile computer-readable storage media may include, but are not limited to, magnetic, optical, and / or semiconductor storage devices. Examples of these storage devices include magnetic disks, optical disks based on CD, DVD, or Blu-ray technology, and persistent solid-state memory (such as flash memory, solid-state drives, etc.). Personal electronic device 500 is not limited to Figure 5B components and configurations, but may include other or additional components in various configurations.

[0189] As used herein, the term "affordance" refers to an item that can be present on device 100, device 300, and / or device 500 (FIG. 1, Figure 3 5 ). For example, an image (e.g., an icon), a button, and text (e.g., a hyperlink) can each constitute an affordance.

[0190] As used herein, the term "focus selector" refers to an input element of a user interface that is currently interacting with a portion of the user interface. In some implementations, a cursor or other position marker is included that serves as a "focus selector" to facilitate focusing when a user is on a touch-sensitive surface (e.g., Figure 3 Touchpad 355 or Figure 4B When an input (e.g., a press input) is detected on a touch-sensitive surface 451 in the display and a cursor is over a particular user interface element (e.g., a button, a window, a slider, or other user interface element), the particular user interface element is adjusted according to the detected input. In some implementations, a touch screen display (e.g., a touch screen display) that enables direct interaction with user interface elements on the touch screen display is included. Figure 1A A touch-sensitive display system 112 or Figure 4A In some implementations, focus is moved 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 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 particular 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 communicate the user's intended interaction with the user interface (e.g., by indicating to the device the user interface element with which the user is intending to interact). For example, when a press input is detected on a touch-sensitive surface (e.g., a touchpad or touch screen), the position of a focus selector (e.g., a cursor, contact, or selection box) on a corresponding button will indicate that the user is intending to activate the corresponding button (as opposed to other user interface elements displayed on the device's display).

[0191] 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 a plurality of intensity samples. The characteristic intensity is optionally based on a predetermined 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 predetermined event (e.g., after detecting the contact, before detecting the contact is lifted, before or after detecting the contact starts to move, before detecting the contact ends, before or after detecting the contact intensity increases, and / or before or after detecting the contact intensity decreases). The characteristic intensity of the contact is optionally based on one or more of the following: the maximum value of the contact intensity, the median value of the contact intensity, the average value of the contact intensity, the highest 10% value of the contact intensity, the value at half height of the contact intensity, the value at 90% of the maximum value of the contact intensity, etc. In some embodiments, the duration of the contact is used to determine the characteristic intensity (e.g., when the characteristic intensity is the average value of the contact intensity over time). In some embodiments, the characteristic intensity is compared with one or more sets of intensity thresholds to determine whether an operation has been performed by the user. For example, one or more sets of intensity thresholds may include a first intensity threshold and a second intensity threshold. In this example, a contact with a characteristic intensity that does not exceed the first threshold results in a first operation, a contact with a characteristic intensity that exceeds the first intensity threshold and does not exceed the second intensity threshold results in a second operation, and a contact with a characteristic intensity that exceeds the second threshold results in a third operation. In some embodiments, a comparison between the characteristic intensity 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 give up performing the corresponding operation) and is not used to determine whether to perform the first operation or the second operation.

[0192] In some embodiments, a portion of a gesture is recognized for the purpose of determining characteristic intensity. 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 contact intensity increases. In this example, the characteristic intensity of the contact at the end position may be based on only 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 swipe contact intensity before determining the characteristic intensity of the contact. For example, the smoothing algorithm may optionally include 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, for the purpose of determining characteristic intensity, these smoothing algorithms may eliminate narrow spikes or dips in the swipe contact intensity.

[0193] The intensity of a contact on a touch-sensitive surface can 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 the operation typically associated with clicking a button of a physical mouse or trackpad. In some embodiments, when a contact is detected having a characteristic intensity below the light press intensity threshold (e.g., and detected above a nominal contact detection intensity threshold, where the contact is no longer detected below the nominal contact detection intensity threshold), 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. Typically, unless otherwise noted, these intensity thresholds are consistent between different sets of user interface graphics.

[0194] An increase in the characteristic intensity of a contact 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 the characteristic intensity of a contact 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 the characteristic intensity of a contact from an intensity below a contact detection intensity threshold to an intensity between the contact detection intensity threshold and the light press intensity threshold is sometimes referred to as detecting contact on the touch surface. A decrease in the characteristic intensity of a contact from an intensity above the contact detection intensity threshold to an intensity below the contact detection intensity threshold is sometimes referred to as detecting lift-off of the contact from the contact surface. In some embodiments, the contact detection intensity threshold is zero. In some embodiments, the contact detection intensity threshold is greater than zero.

[0195] 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 by a corresponding contact (or multiple contacts), where the corresponding press input is detected based at least in part on detecting an increase in strength of the contact (or multiple contacts) above a press input strength threshold. In some embodiments, the corresponding operation is performed in response to detecting an increase in strength of the corresponding contact above the press input strength threshold (e.g., a "down hit" of the corresponding press input). In some embodiments, the press input includes an increase in strength of the corresponding contact above the press input strength threshold, and a subsequent decrease in strength of the contact below the press input strength threshold, and in response to detecting a subsequent decrease in strength of the corresponding contact below the press input strength threshold (e.g., a "lift hit" of the corresponding press input), the corresponding operation is performed.

[0196] In some embodiments, the device employs intensity hysteresis to avoid unexpected inputs, sometimes referred to as "jitter," where the device defines or selects a hysteresis intensity threshold that has a predetermined relationship to a press input intensity threshold (e.g., the hysteresis intensity threshold is X intensity units below 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 corresponding contact intensity to above the press input intensity threshold and a subsequent decrease in the contact intensity to below a hysteresis intensity threshold corresponding to the press input intensity threshold, and a corresponding operation is performed in response to detecting a subsequent decrease in the corresponding contact intensity to below the hysteresis intensity threshold (e.g., a "lift-and-strike" of the corresponding press input). Similarly, in some embodiments, a press input is detected only when the device detects an increase in contact intensity from an intensity at or below the hysteresis intensity threshold to an intensity at or above the press input intensity threshold, and optionally a subsequent decrease in contact intensity to at or below the hysteresis intensity, and a corresponding operation is performed in response to detecting the press input (e.g., an increase in contact intensity or a decrease in contact intensity, depending on a variety of circumstances).

[0197] For ease of explanation, the 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: contact intensity increasing to above the press input intensity threshold, contact intensity increasing from an intensity below a hysteresis intensity threshold to an intensity above the press input intensity threshold, contact intensity decreasing to below the press input intensity threshold, and / or contact intensity decreasing to below a hysteresis intensity threshold corresponding to the press input intensity threshold. Additionally, in examples where an operation is described as being performed in response to detecting a decrease in contact intensity below the press input intensity threshold, the operation is optionally performed in response to detecting a decrease in contact intensity below a hysteresis intensity threshold corresponding to the press input intensity threshold, or to a hysteresis intensity threshold less than the press input intensity threshold.

[0198] Figure 5C Illustrated are exemplary devices for completing a payment transaction connected via one or more communication channels in accordance with some embodiments. One or more exemplary electronic devices (e.g., devices 100, 300, and 500) are configured to optionally detect input (e.g., specific user input, NFC field) and optionally send payment information (e.g., using NFC). One or more electronic devices optionally include NFC hardware and are configured to be NFC-enabled.

[0199] An electronic device (e.g., devices 100, 300, and 500) is optionally configured to store payment account information associated with each of one or more payment accounts. The payment account information includes, for example, one or more of the following: a personal or company name, a billing address, a login, a password, an account number, an expiration date, a security code, a phone number, a bank associated with the payment account (e.g., an issuing bank), and a card network identifier. In some examples, the payment account information includes an image, such as a photo of a payment card (e.g., taken by the device and / or received at the device). In some examples, the electronic device receives user input including at least some payment account information (e.g., receiving a credit card, debit card, account or gift card number and expiration date entered by a 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 or identified payment account data associated with the user's account or another service for which the user device previously made a purchase (e.g., an application for renting or selling audio and / or video files).

[0200] 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 the user initiates such a process, the electronic device sends the payment account information to a transaction-coordination server, which then communicates with a server (e.g., a payment server) operating through the account's payment network to ensure the validity of the information. The electronic device is optionally configured to receive a script from a server that allows the electronic device to program the account's payment information onto a secure element.

[0201] In some embodiments, communication between electronic devices 100, 300, and 500 facilitates transactions (e.g., generally or specifically). For example, a first electronic device (e.g., 100) may serve as a providing or management device and may send a notification of new or updated payment account data (e.g., information of a new account, updated information of an existing account, and / or an alert about an existing account) to a second electronic device (e.g., 500). In 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 may optionally include one or more of the following: the payment amount, the account used, the time of purchase, and whether the default account has changed. The second electronic device (e.g., 500) may optionally use such information to update the default payment account (e.g., based on a learning algorithm or explicit user input).

[0202] Electronic devices (e.g., 100, 300, 500) are configured to communicate with each other over any of a variety of networks. For example, the devices communicate using a Bluetooth connection 550 (which includes a traditional Bluetooth connection or a Bluetooth low energy connection) or using a WiFi network 552. Communications between user devices are optionally met to reduce the possibility of inappropriate sharing of information across devices. For example, communications involving payment information require that the communicating devices be paired (e.g., associated with each other via explicit user interaction) or associated with the same user account.

[0203] In some embodiments, an electronic device (e.g., 100, 300, 500) is used to communicate with a point of sale (POS) payment terminal 850, which is optionally NFC enabled. Communication optionally occurs using various communication channels and / or technologies. In one example, an electronic device (e.g., 100, 300, 500) communicates with a payment terminal 850 using an NFC channel 554. In some examples, the payment terminal 850 communicates with an electronic device (e.g., 100, 300, 500) using a peer-to-peer NFC mode. The electronic device (e.g., 100, 300, 500) is optionally configured to send a signal to the payment terminal 850, which includes payment information of a payment account (e.g., a default account or an account selected for a particular transaction).

[0204] 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). The security element optionally requires specific user input before releasing the payment information. For example, the security element optionally requires detection that the electronic device is being worn, detection button presses, detection of password entry, detection of touch, detection of one or more option selections (received when interacting with the application), detection of fingerprint signatures, detection of voice or voice commands, and / or detection of gestures or movements (e.g., rotation or acceleration). In some examples, if a communication channel (e.g., an NFC communication channel) with another device (e.g., a payment terminal 850) is established within a predefined time period from detection of the input, the security element releases the payment information to be sent to the other device (e.g., payment terminal 850). 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.

[0205] In some embodiments, the protocol associated with transaction participation depends, for example, on the device type. For example, the conditions for generating and / or sending payment information may be different for a wearable device (e.g., device 500) and a phone (e.g., device 100). For example, the generation and / or sending conditions for a wearable device include detecting that a button has been pressed (e.g., after security verification), while the corresponding conditions for the phone do not require a button press, but require detection of a specific interaction with the application. In some examples, the conditions for sending and / or releasing payment information include receiving a 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).

[0206] Payment terminal 850 optionally uses the payment information to generate a signal to send to payment server 560 to determine whether the payment is authorized. Payment server 560 optionally includes any device or system configured to receive payment information associated with a payment account and determine whether the proposed purchase is authorized. In some examples, payment server 560 includes a server of an issuing bank. Payment terminal 850 communicates directly or indirectly with payment server 560 via one or more other devices or systems (e.g., a server of an acquiring bank and / or a server of a card network).

[0207] The payment server 560 optionally uses at least some of the payment information to identify the user from a database of user accounts (e.g., 562). For example, each user account includes payment information. The account is optionally located by locating an account with specific payment information that matches the payment 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, debit card, or gift card number) or when no account includes specific payment information that matches the payment information from the POS communication.

[0208] In some embodiments, the user account data further identifies one or more limits (e.g., credit limit); current or previous balance; previous transaction date, location, and / or amount; account status (e.g., active or frozen), and / or authorization indication. In some examples, the payment server (e.g., 560) uses such data to determine whether to authorize 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.

[0209] In some embodiments, the payment server 560 responds to the POS payment terminal 850 with an indication of whether the proposed purchase is authorized or rejected. In some examples, the POS payment terminal 850 sends a signal to the electronic device (100, 300, 500) to identify the result. For example, when the purchase (e.g., via a transaction-coordinating server that manages the transaction application on the user device) is authorized, the POS payment terminal 850 sends a receipt to the electronic device (100, 300, 500). In some instances, the POS payment terminal 850 presents an output (e.g., a visual or audio output) indicating the result. The payment can be sent to the merchant as part of the authorization process or can be sent subsequently.

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

[0211] Figure 6A-Figure 6O Figures illustrate user interfaces for conducting payment transactions according to some embodiments. The user interfaces in these figures are used to illustrate the processes described below, including Figure 7 process.

[0212] The payment technology allows the user to authorize both the electronic device and the remote server (such as a bank) (e.g., using a fingerprint or device password). Each of the two authorizations requires their own authorization data provided by the user. This payment technology is safer and more convenient than other payment technologies.

[0213] Fig. 6A Illustrated is a user interface for conducting a payment transaction according to some embodiments. Fig. 6A , electronic device 100 displays a user interface for a first application 602 (e.g., a third-party merchant application or a website accessed by a web browser). The user interface for the first application 602 includes a payment affordance 610 (e.g., a submit button to purchase the contents of a shopping cart) associated with a payment transaction (e.g., a purchase to be made). For example, payment affordance 610 may be a submit button to initiate a purchase of the contents of electronic shopping cart 604. In the illustrated Fig. 6A In the example of FIG. 6 , the electronic shopping cart 604 includes a plurality of clothing items 606 .

[0214] The electronic device detects a request to initiate a payment transaction (e.g., detecting a selection of a payment affordance 610 associated with a payment transaction; a user tapping on payment affordance 610). In response to detecting the request to initiate a payment transaction, the device displays a payment user interface 620, such as Figure 6B As shown in the picture.

[0215] In some embodiments, the payment user interface is a payment user interface of a second application. For example, the second application may be part of an operating system of the electronic device, and the second application has access to an electronic wallet of the device. In some embodiments, the second application is a first-party application provided by a provider of the operating system of the electronic device, and the second application has access to an electronic wallet of the device.

[0216] exist Figure 6B At , the payment user interface 620 optionally includes an indication of a default / selected payment account 624, a name associated with the payment account (e.g., the cardholder's name), a billing address, a shipping address 626, a shipping method 628, contact information 630, a subtotal 630, a tax amount 634, a shipping amount 636, and a total 638.

[0217] Figure 6C-6DAn exemplary user interface for changing options for a payment transaction in accordance with some embodiments is illustrated. In some embodiments, the electronic device receives a selection of (e.g., a user taps on) a first purchase details affordance displayed on payment user interface 620 (e.g., a caret associated with a payment account 624A, a shipping address 626A, a shipping method 628A, contact information 630A). First purchase details affordance 624A is associated with a first purchase detail of the payment transaction (e.g., a selected payment account, shipping address, shipping method, contact information). In response to receiving a selection of first purchase details affordance 624A, the device displays one or more affordances for selecting alternative values ​​for the first purchase detail of the payment transaction (e.g., displaying different options for a payment account). For example, when the user selects Figure 6C When the caret 624A is associated with the payment account used for the first purchase details, such as Fig.6D As illustrated, the device displays several payment account options 660 and 662 for the first purchase details. The currently selected payment account option 660 is identified, such as by selecting a list 664. Thus, the user can change the default payment account 624 that will be used for payment transactions.

[0218] exist Figure 6E-6F At the time when the payment user interface 620 is displayed, the electronic device receives the first authorization data (e.g., fingerprint authorization information or device password). In this example, the fingerprint authorization technology is illustrated, such as by Fig. 6E As indicated by visual indicator 650A, the user is instructed to use fingerprint sensor 204 and Fig. 6F The visual indicator 650 provides authorization, indicating to the user that the user's fingerprint is being read using the fingerprint sensor 204.

[0219] After receiving the first authorization data, the electronic device (e.g., at the electronic device) determines whether the first authorization data is valid (e.g., the electronic device confirms that the fingerprint or device password is authorized for payment). Figure 6G At , the device has determined that the first authorization data is valid (eg, the fingerprint is authorized for payment), as indicated by visual indicator 656 .

[0220] exist Figure 6H At the electronic device receives second authorization data (e.g., a bank personal identification number (PIN) authorization code, such as a 6-digit value). In this example, the electronic device prompts the user for the second authorization data and receives the second authorization data after receiving the first authorization data. Figure 6HIn the example of, the user can use, for example, a keyboard to enter the second authorization data. The second authorization data is not limited to keyboard entry. The user can use a fingerprint sensor, voice command, or use other technologies to provide the second authorization data. In some examples, the electronic device can receive the second authorization data before receiving the first authorization data.

[0221] After receiving the first authorization data and the second authorization data, the electronic device sends a transaction request corresponding to the payment transaction to one or more remote servers (e.g., the transaction request is based on the second authorization data). The electronic device receives a reply to the transaction request. For example, the reply to the transaction request is received from one or more remote servers or another server associated with the one or more remote servers.

[0222] In response to receiving a reply to the transaction request, the device dismisses the payment user interface (and, optionally, provides an indication of transaction success) based on confirmation that the transaction request is successful (e.g., the reply indicates that the transaction request contains valid or authorized second authorization data). Fig.6I At , the electronic device has received a reply to the transaction request and has determined that the transaction request is successful. Based on this determination, the device dismisses the payment user interface 620g (e.g., no longer displays the payment user interface 620) and displays the confirmation user interface 662 of the first application, including the order number 664.

[0223] In response to receiving a reply to the transaction request, based on a confirmation that the transaction request failed (e.g., the reply indicates that the transaction request does not include valid or authorized second authorization data or due to insufficient funds in the payment account), the electronic device maintains display of the payment user interface 620 and updates the payment user interface 620 to display an indication of the reason why the transaction request failed 666, such as in Figure 6J As shown in the figure.

[0224] In some embodiments, the indication of the reason why the transaction request failed includes an indication that the transaction request failed due to a merchant associated with the payment transaction (e.g., an item from the shopping cart cannot be delivered to the address provided or an item from the shopping cart is out of stock) or an indication that the transaction request failed due to a financial institution (e.g., a bank or other authorization agent) associated with the payment transaction (e.g., the financial institution determined that there were insufficient funds or that the second authorization data was invalid or unauthorized).

[0225] In some embodiments, displaying the payment user interface 620 (e.g., a user interface on an operating system) includes displaying the user interface 620 on only a portion of the first user interface (e.g., a user interface of a third-party merchant application or a website accessed by a web browser), for example, displaying the payment user interface 620 so that the payment user interface 620 covers only a portion of the first user interface but not all of it (e.g., a user interface of the first application 602, a third-party merchant application, or a website accessed by a web browser), thereby providing context for a payment transaction initiated using the first user interface. For example, in Figure 6B , payment user interface 620 (which, for example, includes displayed items 624, 626, 628, 630, 624A, 626A, 628A, 630A, 632, 634, 636, 638, and 650A) covers a bottom portion of the display of device 100, leaving a top portion of the user interface for the first application 602 visible, the top portion including a portion of the electronic shopping cart 604 and one of the clothing items 606 (e.g., a navy blue shirt for $85.00).

[0226] In some examples, sending the transaction request includes sending the transaction request while displaying payment user interface 620, and receiving a reply to the transaction request includes receiving a reply to the transaction request while displaying payment user interface 620. Thus, the transaction request is sent and the reply is received while payment user interface 620 is displayed. This defines the need for displaying different user interfaces.

[0227] In some embodiments, based on a determination that the transaction request is successful (and optionally a determination that the second authorization data (e.g., a bank pin authorization code) is not currently stored), the electronic device stores (e.g., in a memory of the electronic device) the second authorization data (e.g., a bank pin authorization code) and / or stores (e.g., in a memory of the electronic device) a representation of the second authorization data (e.g., an encrypted version of the bank pin authorization code). Based on a determination that the transaction request is successful, the electronic device abandons storing (e.g., not storing in the memory of the electronic device) the second authorization data (e.g., a bank pin authorization code). Thus, when the user performs a payment transaction, the device determines whether the payment transaction is successful. If the payment transaction is not successful (e.g., the financial institution indicates that the second authorization data is invalid or unauthorized), the electronic device does not store the second authorization data for future reuse (because the second authorization data is invalid) and associates the stored second authorization data with the selected payment account.

[0228] like Figure 6KAs illustrated in , in some embodiments, the electronic device detects a second request (e.g., detecting a selection of a second payment affordance 676 associated with a second payment transaction; the user taps the second payment affordance 676 using an application different from the first application during a different shopping experience) to initiate the second payment transaction. Figure 6K As illustrated, second payment affordance 676 can be displayed as part of user interface 670 of an application different from the first application. User interface 670 can include advertisement 672 and items 674 in an electronic shopping cart.

[0229] exist Figure 6L At , in response to detecting the second request to initiate a second payment transaction, the electronic device displays a second payment interface 676. Figure 6M At , when the second payment interface 676 is displayed, the electronic device receives third authorization data (e.g., fingerprint authorization data or device password). In some examples, the third authorization data has the same value as the first authorization data (or represents the same fingerprint). After receiving the third authorization data, the electronic device (e.g., at the electronic device) determines whether the third authorization data is valid (e.g., the electronic device confirms that the fingerprint or device password is authorized for payment), such as Figure 6M The indicator 678 and Figure 6N As indicated by indicator 680 .

[0230] After receiving the third authorization data (and without receiving the second authorization data again from the user (e.g., without requesting or receiving the bank pin authorization code again from the user)), the electronic device (e.g., based on (or including) the stored second authorization data or a representation of the stored second authorization data) sends a second payment request corresponding to the second payment transaction to one or more remote servers. Optionally, the electronic device sends the second transaction request only after determining that the third authorization data is valid, such as by Figure 6N The electronic device receives a reply to the second transaction request (eg, from one or more remote servers).

[0231] In response to receiving the reply to the second transaction request, based on the determination that the second transaction request is successful, the electronic device dismisses the second payment user interface (and optionally provides an indication of transaction success), such as Fig.6O In response to receiving a reply to the second transaction request, based on a determination that the second transaction request has failed, maintaining display of the second payment user interface and updating the second payment user interface to display a second indication of a second reason for failure of the second transaction request.

[0232] In some embodiments, sending a transaction request corresponding to a payment transaction to one or more remote servers (based on the stored second authorization data) includes sending the second authorization data to a financial institution (eg, a bank or other authorization agent).

[0233] In some embodiments, based on the determination of a transaction request failure (e.g., insufficient funds, wrong PIN): when displaying the payment user interface, the electronic device receives third authorization data (e.g., fingerprint authorization information or a device password); after receiving the third authorization data, the electronic device (e.g., at the electronic device) determines whether the third authorization data is valid (e.g., confirms that the fingerprint or device password is authorized for payment). The electronic device receives fourth authorization data (e.g., a bank PIN authorization code). After receiving the third authorization data and the fourth authorization data, the electronic device (e.g., based on the stored second authorization data) sends a second transaction request corresponding to the payment transaction to one or more remote servers; and the electronic device receives a reply to the transaction request (from one or more servers). Therefore, for example, if the transaction request fails, such as Figure 6J As shown, if the user initiates a second attempt to complete the transaction, the user must authenticate again using two authentication methods, such as using Fig. 6F The illustrated locally authenticated fingerprint authorization, and the use of Figure 6H The bank pin authorization code authenticated at the remote server as shown in FIG.

[0234] In some embodiments, receiving first authorization data (e.g., fingerprint authentication information or a device password) includes detecting a corresponding fingerprint on a fingerprint sensor of the electronic device, and wherein determining (e.g., at the electronic device) whether the first authorization data is valid (e.g., confirming that the fingerprint authentication information or device password is authorized for payment) includes determining whether the corresponding fingerprint is consistent with a registered fingerprint that enables authorization of the payment transaction.

[0235] In some embodiments, receiving first authorization data (e.g., fingerprint authentication information or a device password) includes receiving a payment password (e.g., using a physical or displayed keyboard), and determining (e.g., at the electronic device) whether the first authorization data is valid (e.g., confirming that the fingerprint authentication information or device password is authorized for payment) includes determining whether the payment password is consistent with a registered password that enables authorization of the payment transaction.

[0236] In some embodiments, the first authorization data is different from the second authorization data (e.g., the device password is different from the bank pin authorization code). For example, the user may have previously selected a device password for making payments using the electronic device (and / or unlocking the electronic device), and the user may have previously selected (or been assigned) another bank pin authorization code for making payments using the electronic device.

[0237] In some embodiments, when the electronic device is in a specific country or region, the second authorization data may not be required, and when the electronic device is not in a specific country or region, the second authorization data may be required. This policy may be set, for example, by a bank that services a payment account. The electronic device determines the current location of the electronic device. Based on determining the current location of the electronic device, a second authorization data is requested (and subsequently received) from the user within a first predefined geographic area (e.g., a first country or other geographic area that requires a second form of authentication to authorize a payment transaction). On the contrary, based on determining that the electronic device is in a second predefined geographic area (e.g., outside the first predefined geographic area or in a second country different from the first country), the electronic device only authenticates the payment transaction with a single form of authentication (e.g., the electronic device only requests and uses the first authorization data). For example, when the electronic device is located in a specific country, the bank that processes the payment request may require the payment request to include a bank pin authorization code.

[0238] In some embodiments, the electronic device determines whether the payment amount of the payment transaction meets a predefined criterion (e.g., the payment amount is greater than a threshold payment amount). Based on determining that the payment amount of the payment transaction meets the predefined criterion (e.g., the payment amount is greater than the threshold payment amount), (e.g., only) requesting (and subsequently receiving) second authorization data from the user. Conversely, based on determining that the payment amount of the payment transaction does not meet the predefined criterion (e.g., the payment amount is equal to or less than the threshold payment amount), the electronic device authenticates the payment transaction using only a single form of authentication (e.g., the electronic device only requests and uses the first authorization data). For example, when the total amount of the transaction (e.g., the price) exceeds a certain amount, the user may have previously requested that a bank pin authorization code be sent only to one or more servers. For another example, when the total amount of the transaction exceeds a certain value, the bank processing the payment request may require that the payment request include a bank pin authorization code.

[0239] In some embodiments, the first entropy of the first authorization data is higher than the second entropy of the second authorization data (e.g., it is more difficult to guess a user's device password than to guess a bank pin authorization code). This is particularly useful when the electronic device stores a bank pin authorization code (or a representation of a bank pin authorization code), and therefore the electronic device must protect the bank pin authorization code.

[0240] Figure 7 700 is a flow chart illustrating a method for performing a payment transaction using an electronic device according to some embodiments. The method 700 is performed at a device (e.g., 100, 300, 500). Some operations in the method 700 may be combined, the order of some operations may be changed, and some operations may be omitted.

[0241] As described above, method 700 provides an intuitive way to conduct payment transactions. The method reduces the cognitive load of users for conducting payment transactions, thereby creating a more efficient human-computer interface. For battery-operated computing devices, enabling users to conduct payment transactions faster and more efficiently conserves power and increases the time between battery charges.

[0242] At block 702, the electronic device detects a request to initiate a payment transaction. For example, the device detects a payment affordance associated with the payment transaction (e.g., Fig. 6A 610) selection.

[0243] At block 704, in response to detecting a request to initiate a payment transaction, the electronic device displays a payment user interface (eg, Figure 6B of 620).

[0244] At box 706, when the payment user interface is displayed, the electronic device receives first authorization data (e.g., fingerprint authentication information or a device password).

[0245] At box 708, after receiving the first authorization data, the electronic device (eg, at the electronic device) determines whether the first authorization data is valid (eg, the electronic device confirms that the fingerprint or device password is authorized for payment).

[0246] At block 710, the electronic device receives second authorization data (eg, a bank pin authorization code).

[0247] At box 712, after receiving the first authorization data (e.g., fingerprint authentication information or device password) and the second authorization data (e.g., bank pin authorization code), the electronic device (e.g., based on the second authorization data) transmits a transaction request corresponding to the payment transaction to one or more remote servers.

[0248] At block 714, the electronic device receives a reply to the transaction request.

[0249] At box 716, in response to receiving a reply to the transaction request: based on determining that the transaction request is successful, the electronic device dismisses the payment user interface (and, optionally, provides an indication of a successful transaction); and based on determining that the transaction request has failed (for example, due to insufficient funds, incorrect bank pin authorization code), the electronic device maintains display of the payment user interface (e.g., 620) and updates the payment user interface (e.g., 620) to display an indication of the reason the payment request failed.

[0250] In some embodiments, an indication of the reason why the payment request failed (e.g., Figure 6J666) includes: an indication that the transaction request failed due to a merchant associated with the payment transaction (e.g., the item cannot be delivered to the provided address or the item is out of stock); or an indication that the transaction request failed due to a financial institution (e.g., a bank or other authorization agent) associated with the payment transaction (e.g., insufficient funds, incorrect bank pin authorization code) (e.g., Figure 6J of 666).

[0251] In some embodiments, displaying the payment user interface (e.g., 620) includes displaying the payment user interface (e.g., 620) over only a portion of the first user interface (e.g., 620) (e.g., such that the payment user interface covers only a portion of the first user interface and not all of it, thereby providing context for the transaction being initiated using the first user interface).

[0252] In some embodiments, transmitting the transaction request includes transmitting the transaction request while displaying the payment user interface (e.g., 620) and wherein receiving a reply to the transaction request includes receiving a reply to the transaction request while displaying the payment user interface (e.g., 620).

[0253] In some embodiments, based on determining that the transaction request is successful (and optionally determining that the bank pin authentication code is not currently stored), the electronic device stores the second authorization data (e.g., the bank pin authorization code) (e.g., in the memory of the electronic device). Based on determining that the transaction request fails, the electronic device abandons storing (e.g., not storing in the memory of the electronic device) the second authorization data (e.g., the bank pin authorization code).

[0254] In some embodiments, the electronic device detects a second request for initiating a second payment transaction (e.g., detecting another payment affordance 676 associated with the second payment transaction). In response to detecting the second request for initiating the second payment transaction, the electronic device displays a second payment user interface (e.g., 676). While displaying the second payment user interface, the electronic device receives third authorization data (e.g., fingerprint authentication information or a device password). After receiving the third authorization data, the electronic device (e.g., at the electronic device) determines whether the third authorization data is valid (e.g., confirms that the fingerprint authentication information or the device password is authorized for payment). After receiving the third authorization data (without receiving the second authorization data again from the user (e.g., a bank pin authorization code)), the electronic device (based on the stored second authorization data) transmits a second transaction request corresponding to the second payment transaction to one or more remote servers, wherein the second transaction request is based at least in part on a representation of the stored second authorization data. The electronic device receives a second reply to the second transaction request.

[0255] In some embodiments, in response to receiving a second reply to a second transaction request: based on determining that the second transaction request is successful, the electronic device dismisses the second payment user interface (and, optionally, provides an indication of a successful transaction); and based on determining that the second transaction request has failed, the electronic device maintains display of the second user payment interface and updates the second user payment interface to display an indication of a second reason for the failure of the second transaction request.

[0256] In some embodiments, transmitting the transaction request corresponding to the payment transaction to one or more remote servers (based on the stored second authorization data) includes transmitting the second authorization data to a financial institution (eg, a bank or other authorization agent).

[0257] In some embodiments, based on determining that a transaction request has failed (e.g., insufficient funds, wrong PIN): when displaying a payment user interface, the electronic device receives third authorization data (e.g., fingerprint authentication information or a device password); after receiving the third authorization data, the electronic device (e.g., at the electronic device) determines whether the third authorization data is valid (e.g., confirms that the fingerprint or device password is authorized for payment); the electronic device receives fourth authorization data (e.g., a bank PIN authorization code); after receiving the third authorization data and the fourth authorization data, the electronic device (e.g., based on the stored second authorization data) transmits a second transaction request corresponding to the payment transaction to one or more remote servers; and the electronic device receives a reply to the transaction request.

[0258] In some embodiments, receiving first authorization data (e.g., fingerprint authorization information or a device password) includes detecting a corresponding fingerprint on a fingerprint sensor of the electronic device, and wherein determining (e.g., at the electronic device) whether the first authorization data is valid (e.g., confirming that the fingerprint or device password is authorized for payment) includes determining whether the corresponding fingerprint is consistent with a registered fingerprint that enables authorization of the payment transaction.

[0259] In some embodiments, receiving first authorization data (e.g., fingerprint authorization information or a device password) includes receiving a payment password (e.g., using a keypad), and wherein determining (e.g., at the electronic device) whether the first authorization data is valid (e.g., confirming that the fingerprint or device password is authorized for payment) includes determining whether the payment password is consistent with a registered password that enables authorization of the payment transaction.

[0260] In some embodiments, the first authorization data is different from the second authorization data (eg, a payment password is different from a bank pin authorization code).

[0261] In some embodiments, based on determining that the current location of the electronic device is within a first predefined geographic area (e.g., a first country or other geographic area that requires a second form of authentication to authorize the payment transaction), the second authorization data is requested from the user (and subsequently received). Conversely, based on determining that the current location of the electronic device is within a second predefined geographic area (e.g., outside the first predefined geographic area or in a second country different from the first country), the electronic device authenticates the payment transaction using only a single form of authentication (e.g., the first authorization data).

[0262] In some embodiments, based on determining that the payment amount of the payment transaction meets the predefined criteria (e.g., the payment amount is greater than the threshold payment amount), the second authorization data is requested from the user (and subsequently received). Conversely, based on determining that the payment amount of the payment transaction does not meet the predefined criteria (e.g., the payment amount is not greater than the threshold payment amount), the electronic device authenticates the payment transaction using only a single form of authentication (e.g., the first authorization data).

[0263] Note that the above description of method 700 (eg, Figure 7 ) also apply in a similar manner to the methods described below. For example, methods 900 and 1100 may include one or more of the features of the various methods described above with reference to method 700. For the sake of brevity, these details are not repeated below.

[0264] Figure 8A-8K Illustrated are exemplary techniques and user interfaces for conducting payment transactions using a short-range communication radio, such as a near field communication (NFC) radio, according to some embodiments. The techniques and user interfaces in these figures are used to illustrate the processes described below, including Fig. 9 process.

[0265] The NFC standard, which is related to the Radio Frequency Identification (RFID) standard, describes a communication protocol for transferring information between two devices, such as for making a payment. However, it should be understood that other communication standards and technologies may also be used.

[0266] Device 100 (and device 300) may include near field communication circuitry, such as a short-range communication radio and a physical input mechanism 204 (e.g., a mechanical or capacitive button) including an integrated biometric sensor. Thus, device 100 may use near field communication to wirelessly communicate with an external device (e.g., a contactless payment transaction terminal 850 with NFC functionality). For example, the near field communication circuitry in device 100 may include a near field transmitter and a near field receiver. Near field communication for device 100 may be supported using a capacitively coupled near field communication structure and / or an inductively coupled near field communication structure. In near field communication technology, wireless signals are typically communicated over distances of, for example, 1 meter or less, 100 centimeters or less, 10 centimeters or less, or 1 centimeter or less, rather than over longer distances.

[0267] exist Fig. 8A In the embodiment, a contactless payment transaction terminal 850 with NFC function generates a field 852. For example, a device with NFC function entering the field 852 can communicate with the contactless payment transaction terminal 850 using NFC. Fig. 8A , the electronic device 100 has not been placed in the field 852. The contactless payment transaction terminal 850 may be part of a payment system (eg, a check register) installed at a retail store for processing payment transactions (such as purchases of products and services).

[0268] In some embodiments, the electronic device 100 receives authorization to enable the electronic device to participate in a payment transaction via a short-range communication radio (e.g., from a user as described in detail below). Optionally, the authorization is valid only for a predetermined time period (e.g., up to 30 seconds). If the user places the device into the field 852 after receiving the authorization and before the predetermined time period has passed, the device will continue to make a payment transaction (e.g., a payment of funds being requested by the contactless payment transaction terminal 850). After the predetermined time period has passed, the device will no longer be enabled to participate in authorization for payment transactions via the short-range communication radio (unless the user once again authorizes the device), and therefore the device will not continue to make payment transactions even if it is placed within the range of the field 852. Therefore, optionally, after being enabled to participate in authorization for payment transactions via the short-range communication radio, the device will not remain enabled indefinitely.

[0269] By enabling the electronic device to participate in a payment transaction via a short-range communication radio before the electronic device is placed within the range of field 852, the user is able to reduce the number of interactions required with the electronic device once the electronic device is placed within the range of field 852, facilitating a simplified user experience. Further, some NFC-enabled contactless payment transaction terminals use a reduced timeout duration. This reduced timeout duration requires that the payment transaction be completed within a short period of time for a successful payment, starting from the time the contactless payment transaction terminal detects that the device has entered the field of the contactless payment transaction terminal. By enabling the electronic device to participate in a payment transaction via a short-range communication radio before the electronic device is within the range of field 852, the timeout rate is reduced and successful payment transactions are increased.

[0270] Device 100 includes near field communication circuitry (eg, an NFC radio) and a physical input mechanism 204 (eg, a mechanical or capacitive button). Physical input mechanism 204 includes an integrated biometric sensor, such as a fingerprint sensor.

[0271] exist Figure 8B and Figure 8C In the embodiment, the electronic device 100 is not enabled to participate in payment transactions via the short-range communication radio. Figure 8B At , the device's display is turned off (e.g., disabled and not displaying anything). Figure 8B The device can also be in a locked state or an unlocked state.

[0272] In the locked state, the electronic device 100 is powered on and operable but is blocked from performing a predefined set of operations in response to user input. The predefined set of operations may include navigation between user interfaces, activation or deactivation of a predefined set of functions, and activation or deactivation of certain applications. The locked state may be used to prevent unintended or unauthorized use of some functions of the electronic device 100 or activation or deactivation of some functions on the electronic device 100. In the unlocked state, the electronic device 100 is powered on and operable and is not blocked from performing at least a portion of a predefined set of operations that cannot be performed when in the locked state.

[0273] When device 100 is in the locked state, device 100 may be referred to as being locked. In some embodiments, device 100 in the locked state may respond to a limited set of user inputs, including inputs corresponding to attempts to transition device 100 to a user interface unlocked state or inputs corresponding to powering off device 100.

[0274] exist Figure 8C At , the display of device 100 is turned on (eg, displaying the current date or other information) and the device is in a locked state (eg, locked).

[0275] When the electronic device is not enabled to participate in a payment transaction via the short-range communication radio (regardless of whether the display is on or off), the device detects activation of the physical input mechanism 204. For example, activation of the physical input mechanism may require two presses (or clicks) within a predetermined time period. Thus, the user may Figure 8B or Figure 8C Activation of the physical input mechanism 204 is initiated at.

[0276] In response to detecting at least a portion of the activation of the physical input mechanism (e.g., the first click or a button-down portion of the first click), the electronic device detects the position using the integrated biometric sensor, such as Fig.8D 804. The electronic device also determines (eg, at the electronic device) whether the fingerprint is consistent with a registered fingerprint that enables authorization of the payment transaction.

[0277] like FIG. 8E to FIG. 8G As shown, based on determining that the fingerprint is consistent with a registered fingerprint that enables authorization of a payment transaction, the electronic device enables the device to participate in a payment transaction via a short-range communication radio, as indicated by indicators 810A-810C. For example, the electronic device transitions to a standby state (e.g., the electronic device uses the short-range communication radio to notify the device that an NFC payment can be made) to prepare for the payment transaction.

[0278] although FIG. 8C to FIG. 8H The illustration shows a user interface, but the same techniques described above can be performed when the display is not turned on.

[0279] In some embodiments, upon determining that the fingerprint matches a registered fingerprint that enables authorization of a payment transaction, the electronic device displays an electronic wallet, such as FIG. 8E to FIG. 8G As shown. The electronic wallet may optionally include multiple payment card offerings (such as payment card offerings 802 and 812). For example, if the electronic device is used for a payment transaction, then Fig. 8E The user interface allows the user to easily determine which payment account will be used. In this example, payment card offering 802 is displayed at the top of the display, indicating that the payment account associated with payment card offering 802 will be used for payment. The user can select a different payment account for payment transaction, for example, by activating one of payment card offerings 812 associated with other payment accounts.

[0280] exist Figure 8HIn some embodiments, based on determining that the fingerprint is inconsistent with a registered fingerprint that enables authorization of a payment transaction, the electronic device abandons enabling (e.g., not enabling) the electronic device to participate in a payment transaction via a short-range communication radio, as indicated by indicator 806. Additionally, in some embodiments, based on determining that the fingerprint is inconsistent with a registered fingerprint that enables authorization of a payment transaction, the electronic device displays affordance 808, which, when activated, displays a user interface (such as Figure 8K ) is used to receive a device password (rather than using a fingerprint) to enable the device to authorize a payment transaction.

[0281] Figure 8I The user is illustrated placing the electronic device 100 in a field 852 generated by a contactless payment transaction terminal 850. When the device is enabled to participate in a payment transaction via a short-range communication radio, the device detects the presence of the field 852 generated by the contactless payment transaction terminal 850 via the short-range communication radio; performs a handshake with the contactless payment transaction terminal 850 using the short-range communication radio; and authorizes the payment transaction, such as Figure 8J As illustrated and as indicated by indicator 814. Thus, the user does not need to authenticate when the device is within range of field 852 because the user has already enabled the device to participate in the payment.

[0282] Conversely, if a user places an electronic device within the range of field 852 generated by contactless payment transaction terminal 850 and the device is not enabled to participate in payment transactions via a short-range communication radio, the device will detect field 852, determine that the electronic device has not been pre-authorized by the user to process payment transactions, and attempt to receive authorization from the user to enable the electronic device to participate in payment transactions via a short-range communication radio.

[0283] In some embodiments, the activation of a physical input mechanism is detected while the device is in a locked state (e.g., the electronic device detects activation of a physical input mechanism while the device is in a locked state), such as Figure 8C As shown in the figure.

[0284] In some embodiments, enabling the device to participate in payment transactions via the short range communications radio includes enabling the device to participate in payment transactions via the short range communications radio while the device is in (eg, maintained in) a locked state.

[0285] In some embodiments, enabling the device to participate in a payment transaction via the short-range communication radio includes enabling the device to participate in a payment transaction via the short-range communication radio without turning on a display (or any display) of the device, such as Figure 8B As shown.

[0286] In some embodiments, when the electronic device is not enabled to participate in a payment transaction via a short-range communication radio, the electronic device displays a first user interface (eg, Figure 8C lock screen user interface) and maintaining (e.g., not updating) the first user interface after enabling the device to participate in a payment transaction via the short-range communication radio.

[0287] In some embodiments, the device is enabled to communicate via a short-range communication radio using a method such as that described in reference method 11 ( Figures 10A-10I and Fig.11 ) described in the specification and the accompanying drawings, to participate in a payment transaction comprising configuring the electronic device to respond to payment transaction requests (e.g., a handshake and subsequent payment request) of the payment account using at least partial credit card information (e.g., account number, expiration date, and / or cardholder name) of a payment account (e.g., a bank card, a credit card, or other account previously linked to the device) of multiple payment accounts linked to the device (e.g., using a default payment account, but the device can be configured to use one of the other accounts in the multiple payment accounts), and wherein the payment transaction request is received from a contactless payment transaction terminal 850 (e.g., an NFC-equipped payment terminal located at a physical retail store).

[0288] In some embodiments, after enabling the electronic device to participate in a payment transaction via a short-range communication radio, and while the electronic device is enabled to participate in a payment transaction via a short-range communication radio, and while the electronic device is in a locked state, the electronic device receives user input to place the device in an unlocked state (e.g., the user unlocks the device by performing an unlock action, using fingerprint authentication, or entering a password). The electronic device receives user input selecting a second payment account linked to multiple payment accounts used by the device for payment transactions (e.g., the user selects a different credit card (not the default credit card) to use for this particular payment).

[0289] In some embodiments, enabling a device to participate in payment transactions via a short-range communications radio does not require detection of a field generated by a contactless payment transaction terminal (e.g., a user can standby the device for making NFC payments without detecting (or being near) an NFC-enabled contactless payment transaction terminal).

[0290] In some embodiments, enabling the device to participate in a payment transaction via a short-range communication radio includes transmitting a signal using the short-range communication radio, the signal indicating that the device is configured to make a transaction using near field communication. In contrast, when the electronic device is not enabled to participate in a payment transaction via a short-range communication radio, the electronic device does not immediately respond to the contactless payment transaction terminal using the short-range communication radio to transmit when the electronic device detects a field generated by the contactless payment transaction terminal. Instead, the electronic device requests (and receives) authorization from the user before responding to the contactless payment transaction terminal.

[0291] In some embodiments, after enabling the electronic device to participate in payment transactions via the short range communications radio, in response to determining that payment has not been authorized within a predetermined time period using the short range communications radio, the electronic device becomes disabled from participating in payment transactions via the short range communications radio.

[0292] Fig. 9 To illustrate a method for performing a payment transaction using a short-range communication radio according to some embodiments. Method 900 is performed at a device (100, 300, 500). Some operations in method 900 may be combined, the order of some operations may be changed, and some operations may be omitted.

[0293] As described below, method 900 provides an intuitive way to conduct payment transactions using a short-range communication radio. The method reduces the cognitive load on a user when conducting a payment transaction, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a user to conduct payment transactions faster and more efficiently conserves power and increases the time between battery charges.

[0294] At box 902, when the electronic device is not enabled to participate in a payment transaction via a short-range communication radio: the electronic device detects activation of a physical input mechanism (e.g., two presses of a mechanical or capacitive button within a predetermined time period) at block 904; at box 906, in response to detecting at least a portion of the activation of the physical input mechanism (e.g., a first click, or a button-down portion of the first click), the electronic device detects a fingerprint using an integrated biometric sensor; and at box 908, the electronic device (e.g., at the electronic device) determines whether the fingerprint is consistent with a registered fingerprint that enables authorization of the payment transaction.

[0295] At box 910, based on a determination that the fingerprint is consistent with a registered fingerprint that enables authorization of the payment transaction, the electronic device enables the device to participate in the payment transaction via the short-range communication radio (e.g., transitions the electronic device to a standby state in preparation for the payment transaction).

[0296] In some embodiments, at block 912 , based on a determination that the fingerprint is inconsistent with a registered fingerprint that enables authorization of the payment transaction, the electronic device forgoes enabling the electronic device to engage in the payment transaction via the short-range communication radio.

[0297] In some embodiments, when a device is enabled to participate in a payment transaction via a short-range communication radio: the electronic device detects the presence of a field generated by a contactless payment transaction terminal via the short-range communication radio; the electronic device performs a handshake with the contactless payment transaction terminal using the short-range communication radio; and the electronic device authorizes the payment transaction.

[0298] In some embodiments, activation of the physical input mechanism is detected while the device is in a locked state.

[0299] In some embodiments, enabling the device to participate in payment transactions via the short-range communications radio includes enabling the device to participate in payment transactions via the short-range communications radio while the device is in a locked state.

[0300] In some embodiments, enabling the device to participate in payment transactions via the short range communications radio includes enabling the device to participate in payment transactions via the short range communications radio when a display of the device (or any display) is not turned on.

[0301] In some embodiments, the electronic device displays a first user interface when the device is not enabled to participate in a payment transaction via a short-range communications radio; and maintains (e.g., does not update) the first user interface after the device is enabled to participate in a payment transaction via the short-range communications radio.

[0302] In some embodiments, enabling the device to participate in a payment transaction via a short-range communication radio includes configuring the device to respond to a payment request via the short-range communication radio using at least partial credit card information (e.g., account number, expiration date, and or cardholder name) of a payment account (e.g., a bank card, a credit card, or other account previously linked to the device) from a plurality of payment accounts linked to the device (e.g., using a default payment account, but the device may be configured to accept other accounts in the plurality of payment accounts), and wherein a payment request is received from a contactless payment transaction terminal (e.g., Fig. 8A 850) receives a payment transaction request.

[0303] In some embodiments, after enabling the device to participate in a payment transaction via a short-range communication radio, and while the device is enabled to participate in a payment transaction via a short-range communication radio, and while the device is in a locked state, the electronic device receives user input to place the device in an unlocked state (for example, the user unlocks the device by performing an unlock action, using fingerprint authentication, or entering a password); and the electronic device receives user input selecting a second payment account linked to multiple payment accounts used by the device for payment transactions (for example, the user selects a different credit card (not the default credit card) to be used for this particular payment).

[0304] In some embodiments, enabling an electronic device to participate in payment transactions via a short-range communications radio does not require the electronic device to detect a field generated by a contactless payment transaction terminal (e.g., a user can standby the device for making NFC payments without being near an NFC-enabled contactless payment transaction terminal).

[0305] In some embodiments, enabling the electronic device to participate in a payment transaction via a short-range communications radio includes transmitting a signal using the short-range communications radio indicating that the device is configured to make the transaction using near field communications.

[0306] In some embodiments, after enabling the device to participate in payment transactions via the short range communications radio: in response to determining that payment has not been authorized within a predetermined time period using the short range communications radio, the electronic device disables the device from participating in payment transactions via the short range communications radio.

[0307] Note that the above description of method 900 (eg, Fig. 9 ) also apply in a similar manner to the methods described below and above. For example, methods 700 and 1100 may include one or more of the features of the various methods described above with reference to method 900. For the sake of brevity, these details are not repeated below.

[0308] Figures 10A-10I Figures illustrate exemplary user interfaces for linking a payment account to a corresponding device according to some embodiments. The user interfaces in these figures are used to illustrate the following process, including Fig.11 process.

[0309] Figures 10A-10I Illustrated is an exemplary user interface for linking a payment account, such as a bank account or a revolving credit account, associated with a corresponding device (e.g., a cell phone, laptop, wearable electronic device) via a credit card in accordance with some embodiments.

[0310] For example, in Fig. 10A, an electronic wallet is displayed on a display of an electronic device having a display and a camera sensor. The electronic wallet includes a first stack of card objects 1002 and a second stack of card objects 1008, 1010, and 1012. The first stack of card objects 1002 is visually separated from the second stack of card objects 1008, 1010, and 1012. In this example, a credit card (e.g., an American Express credit card) has been linked to the electronic device and is displayed as part of the first stack of card objects 1002. The electronic device displays affordance 1020. In response to the electronic device receiving activation of affordance 1020, the electronic device displays Fig. 10B The user interface shown in the figure.

[0311] Fig. 10B The user interface is illustrated for selecting from an add payment card affordance 1014 to link a payment account to the device (e.g., to make the payment account available in an electronic wallet) and a scan code affordance 1016 to link a pass. If the device determines that a selection of a finish affordance 1018 has been received, the device returns to displaying Fig. 10A If the device receives a selection to add a payment card affordance 514, the device transitions to Fig. 10C The user interface shown in the figure.

[0312] exist Fig. 10C At the electronic device, a user interface is displayed on the display including: a credit card import affordance 1024 for importing at least a portion of the credit card information from a remote server (e.g., importing a credit / debit card from an iTunes server) and a credit card input affordance 1026 for receiving at least a portion of the credit card information at the electronic device (e.g., receiving credit / debit card details using a camera or manual value entry). The electronic device receives a selection of the credit card input affordance 1026.

[0313] In response to receiving a selection of credit card input affordance 1026, the electronic device displays on the display a live preview 1004 of an image obtained via the camera sensor. For example, the camera preview opens to show a live preview 1004 of an image to indicate that the user should place credit card 1028 in the camera's field of view to link a payment account associated with credit card 1028 to the electronic device.

[0314] While the electronic device displays a live preview 1004 of an image obtained via a camera sensor, the electronic device detects (e.g., using a camera sensor on the back of the electronic device) at least a portion of the credit card information of a credit card 1028 that is in the camera field of view of the camera sensor. Fig. 10DAs illustrated, a user places a credit card in the field of view of a camera sensor and the electronic device performs optical characteristic recognition of one or more of the following: (1) the account number displayed on the credit card, (2) the expiration date displayed on the credit card, (3) the name of the account holder displayed on the credit card.

[0315] In some embodiments, in response to receiving a selection of credit card input affordance 1026, live preview 1004 is immediately displayed on a display of the electronic device without displaying an intervening user interface on the display (e.g., an intervening user interface for receiving manual user-entered credit card information is not displayed on the display). Thus, in response to detecting a selection of credit card input affordance 1026, the electronic device directly receives the credit card from the user. Fig. 10C The user interface transitions to Fig. 10D User interface.

[0316] In some embodiments, the electronic device displays manual credit card entry affordance 1006 on the display simultaneously with a real-time preview of an image obtained via a camera sensor. For example, manual credit card entry affordance 1006, when activated, causes the electronic device to display a user interface for manually entering credit card information. The electronic device receives a selection of manual credit card entry affordance 1006, and the electronic device displays a user interface for receiving at least a portion of the credit card information via displayed keyboard 1050, such as Fig.10F As shown in the picture.

[0317] In some embodiments, in response to selection of manual credit card input affordance 1026, the electronic device displays manual credit card entry affordance 1006 for activating a manual credit card entry user interface (such as a keyboard 1050) for receiving at least a portion of the credit card information via keyboard 1050. Fig.10F ).

[0318] In some embodiments, the electronic device receives a selection of a manual credit card entry affordance, and in response to receiving the selection of the manual credit card entry affordance, the electronic device displays the manual credit card entry affordance, such as Fig.10F The manual credit card entry user interface includes one or more input fields 1042, 1044, 1046, and 1048 for receiving credit card information entered by a user.

[0319] exist Fig.10FAt , the electronic device receives user input, such as a portion of the credit card information at field 1042. Based on determining that the credit card information is of the first type (e.g., based on the portion of the credit card number received), the electronic device forgoes displaying input fields 1046 (enter security code input field) and 1048 (expiration date input field). Based on determining that the credit card information is not of the first type (e.g., based on the portion of the credit card number received), the electronic device displays input fields 1046 (enter security code input field) and 1048 (expiration date input field). If fields such as first entry field 1046 and second entry field 1048 are displayed, and then the electronic device subsequently determines that displayed fields 1046 or 1048 are not needed (e.g., the user goes back and changes the entered credit card number), the electronic device marks the displayed but unneeded field as "unavailable", grays out the field, or indicates that a date is not needed for that field, rather than deleting the field.

[0320] In some embodiments, the manual credit card entry user interface includes two or more input fields (e.g., 1042 and 1044) for receiving account information of a payment account entered by a user, the two or more input fields selected from the group consisting of the name of the cardholder associated with the payment account (e.g., pre-filled with the name from the device, but editable), the account number associated with the payment account (e.g., a credit card number), the expiration date associated with the payment account, and the security code associated with the payment account (e.g., CCV).

[0321] Optionally, credit card information detected while displaying the live preview 1004 of the image can be used to determine how many (and which) fields to display. In some embodiments, at least a portion of the credit card information of the credit card includes a portion of the account number of the credit card. The electronic device determines whether the credit card is of a first type (e.g., the credit card number falls within some predetermined number range) based on the portion of the account number of the credit card. Based on determining that the credit card is not of the first type (e.g., the credit card number does not fall within some predetermined number range), the electronic device displays the expiration date of the credit card in the first entry field 1038 and the security code of the credit card (and / or a space for the security code, such as CCV) in the second entry field 1036, as shown. Figure 10GAs shown in the figure. Based on determining that the credit card is of the first type, the electronic device abandons the expiration date of the credit card displayed in the first entry field 1038 and abandons the security code (and / or the space for the security code, such as CCV) displayed in the first entry field 1036 (e.g., the electronic device does not display the expiration date and security code or their corresponding fields), as indicated within the dotted line 1040 of Figure 10E. If a field such as the first entry field 1038 or the second entry field 1036 is displayed, and then the electronic device subsequently determines that the displayed field 1046 or 1048 is not needed (e.g., the user returns and changes the entered credit card number), the electronic device marks the displayed but unneeded field as "unavailable", grays out the field, or indicates that a date is not needed for that field, rather than deleting the field.

[0322] In some embodiments, a portion of the account information of a credit card includes a bin identification number of the credit card (e.g., the issuer identification number portion of the credit card number, the first 6 digits of the credit card), and determining whether the credit card is of a first type based on the portion of the account information of the credit card includes determining whether the credit card is of a first type (e.g., a first type of card is a card in which the issuer of the credit card requires an expiration date and a security code for payment) based on the bin identification number of the credit card (e.g., the issuer identification number portion of the credit card number, the first 6 digits of the credit card).

[0323] In some embodiments, the electronic device displays two or more input fields associated with a credit card (e.g., fields 1032, 1034, 1036, and 1038). The number of the two or more input fields is based on an image obtained via a camera sensor (e.g., the image includes a credit card number, which is used to determine whether an expiration date field 1038 and a security code field 1036 are required).

[0324] However, in some embodiments, the credit card number in the credit card field 1034 can be changed or updated by the user. The electronic device displays two or more input fields (e.g., the account holder's name field 1032 and the credit card number field 1034) associated with the credit card (and not the fields within the dotted line 1040). The electronic device receives a user input selecting a first field of the two or more input fields. In response to receiving the user input selecting the first field, in addition to the two or more input fields, the attached user input fields (e.g., the expiration date field or security code field that was not previously displayed, such as those in the dotted line 1040) are displayed (e.g., without regard to the credit card number / bin). Thus, in some cases, the device determines (based on the credit card number) that the security code and expiration date of the credit card are not required for the payment transaction and does not display those corresponding areas. If the electronic device then detects a selection of one of the displayed fields 1032 or 1034, the additional fields (such as those in the dotted line 1040) are displayed, regardless of whether the credit card number indicates that the card is of the first type.

[0325] In some embodiments, once the attached user input fields (e.g., the fields in dotted line 1040) are displayed, they are not deleted, even if the device determines that the attached user input fields are not needed. Instead, the device identifies the fields as inactive. The electronic device receives user input on a keyboard at a first field of two or more fields (e.g., the user has selected the credit card number field 1034 and has used the keyboard to change the value of the field). The electronic device determines whether the credit card is of the first type based on the user input. Based on determining that the credit card is not of the first type, the device abandons marking the attached user input fields as inactive (e.g., so that the user can select / edit the contents of the expiration date field and / or the security code field). Based on determining that the credit card is of the first type, the device marks the attached user input fields as active (e.g., if the bin number of the credit card entered by the user indicates that it is of the first type, the field is grayed out or marked as "unavailable").

[0326] Fig.11 11 is a flow chart showing a method for linking a payment account to an electronic device according to some embodiments. The method 1100 is performed at a device (e.g., 100, 300, 500). Some operations in the method 1100 may be combined, the order of some operations may be changed, and some operations may be omitted.

[0327] As described above, method 1100 provides an intuitive way to conduct payment transactions. The method reduces the cognitive load of users for conducting payment transactions, thereby creating a more efficient human-computer interface. For battery-operated computing devices, enabling users to conduct payment transactions faster and more efficiently conserves power and increases the time between battery charges.

[0328] At block 1102, the electronic device displays a user interface (eg, Fig. 10C The user interface includes: a credit card importing component ( Fig. 10C 1024); and a credit card input component ( Fig. 10C 1026).

[0329] At block 1104, the electronic device receives a credit card input affordance ( Fig. 10C 1026) selection.

[0330] At block 1106, in response to receiving an offer for credit card input ( Fig. 10C 1026), the electronic device displays a real-time preview of the image obtained via the camera sensor on the display ( Fig. 10D 1004).

[0331] At block 1108, when a real-time preview of an image obtained via the camera sensor is displayed ( Fig. 10D 1004), the electronic device detects (e.g., using a camera sensor) at least a portion of the credit card information of the credit card within the field of view of the camera sensor (e.g., Fig. 10D 1028).

[0332] In some embodiments, in response to receiving a selection of the credit card input affordance, a real-time preview is immediately displayed on the display ( Fig. 10D 1004) without displaying an intermediate user interface on the display (e.g., an intermediate user interface for receiving credit card information entered manually by a user is not displayed on the display).

[0333] In some embodiments, at block 1110, the electronic device displays on a display a real-time preview ( Fig. 10D 1004) while displaying a manual credit card entry affordance (e.g., Fig. 10D 1006).

[0334] In some embodiments, at block 1112, the electronic device receives a request for a manual credit card entry affordance (e.g., Fig. 10D 1006) selection.

[0335] In some embodiments, at block 1114, in response to receiving a selection of the manual credit card entry affordance, the electronic device displays an option for entering a credit card via a displayed keyboard (e.g., Fig.10F 1050) receives at least part of the credit card information from a user interface (e.g., Fig.10F ).

[0336] In some embodiments, in response to receiving a selection of a manual credit card input affordance (e.g., Fig. 10C 1026), the electronic device displays a manual credit card entry offer (e.g., Fig. 10D 1006) is used to activate the function of activating the user via a keyboard (e.g., Fig.10F 1050) receives at least a portion of the credit card information in a manual credit card entry user interface (e.g., Fig.10F ).

[0337] In some embodiments, the electronic device receives a request for a manual credit card entry offer (e.g., Fig. 10D In response to receiving a request for manual credit card input affordance (e.g., Fig. 10D 1006), the electronic device displays a manual credit card entry user interface (e.g., Fig.10F ). Manual credit card entry user interface (e.g., Fig.10F The user interface of the embodiment includes one or more input fields (e.g., 1042, 1044, 1046, 1048) for receiving user-entered credit card information.

[0338] In some embodiments, a manual credit card entry user interface (e.g., Fig.10F The user interface of the present invention includes two or more input fields (e.g., 1042, 1044, 1046, 1048) for receiving account information of a payment account entered by a user, the two or more input fields selected from the group consisting of: the name of the cardholder associated with the payment account (e.g., pre-filled with the name from the device, but editable), the account number associated with the payment account (e.g., a credit card number), the expiration date associated with the payment account, and the security code associated with the payment account (e.g., CCV).

[0339] In some embodiments, at least part of the credit card information of the credit card includes a portion of the account number of the credit card. The electronic device determines whether the credit card is of the first type based on the portion of the account number of the credit card. Based on determining that the credit card is not of the first type, the electronic device displays, in the first entry field (e.g., Fig. 10E 1038) and the expiration date of the credit card in the second entry field (e.g., Fig. 10E Based on determining that the credit card has a first type, the electronic device abandons the security code of the credit card in the first entry field (e.g., Fig. 10E 1038) and waives the requirement to enter the expiration date of the credit card in the second entry field (e.g., Fig. 10E1036) displays the security code of the credit card (e.g., without displaying the expiration date and security code or field).

[0340] In some embodiments, a portion of the account information of a credit card includes a bin identification number of the credit card (e.g., the issuer identification number portion of the credit card number, the first 6 digits of the credit card), and wherein determining whether the credit card is of a first type based on the portion of the account information of the credit card includes determining whether the credit card is of a first type based on the bin identification number of the credit card (e.g., the issuer identification number portion of the credit card number, the first 6 digits of the credit card) (e.g., the first type of card is a card in which the issuer of the credit card requires an expiration date and a security code for processing payments).

[0341] In some embodiments, the electronic device displays two or more input fields associated with a credit card (e.g., Fig. 10E The number of two or more input fields is based on an image obtained via a camera sensor (e.g., the image includes a credit card number, which is used to determine whether an expiration date field and a security code field are required).

[0342] In some embodiments, the electronic device displays two or more input fields associated with a credit card (e.g., Fig. 10E 1032, 1034). The electronic device receives a selection of two or more input fields (e.g., Fig. 10E In response to receiving a user input selecting the first domain (e.g., Fig.10E 1032, 1034), in addition to two or more input fields, display (e.g., not considering credit card number / bin) additional user input fields (e.g., Fig. 10E 1036, 1038; no expiration date field or security code field was previously displayed).

[0343] In some embodiments, the electronic device receives user input at a first input field of two or more input fields (e.g., using a keyboard). The electronic device determines whether the credit card is of a first type based on the user input. Based on determining that the credit card is not of the first type, the electronic device forgoes marking the associated user input field as inactive (e.g., so the user can select / edit the contents of the expiration date field and / or the security code field). Based on determining that the credit card is of the first type, the electronic device marks the associated user input field as active (e.g., if the bin number of the credit card entered by the user indicates that it is of the first type, gray out the field or mark it as "unavailable").

[0344] Note that the details of the process described above for method 1100 (e.g., FIG. 1 ) also apply in a similar manner to the methods described above. For example, methods 700 and 900 may include one or more of the features of the various methods described above with reference to method 1100. For the sake of brevity, these details are not repeated below.

[0345] Fig.12 1 shows a schematic functional block diagram of an electronic device 1200. In some embodiments, the electronic device 1200 performs the above features. Fig.12 As shown in , the electronic device 1200 includes a display unit 1202 configured to display a graphic object; a touch-sensitive surface unit 1204 configured to receive a user gesture (e.g., touch); one or more RF units 1206 configured to detect and communicate with an external electronic device; and a processing unit 1208 coupled to the display unit 1202, the touch-sensitive surface unit 1204, and the RF unit 1206. In some embodiments, the processing unit 1208 includes a display enabling unit 1210, a receiving unit 1212, a determining unit 1214, a detecting unit 1216, a transmitting unit 1218, an enabling unit 1220, a communicating unit 1222, an authorizing unit 1224, a configuring unit 1226, and a storing unit 1228. Fig.12 The units in FIG. 6 can be used to implement the above Fig.11 Various techniques and methods are described.

[0346] For example, the display enabling unit 1210 may be used by a user to: display a payment user interface; display a real-time preview of an image obtained via a camera sensor; display a user interface on a display, the user interface including a credit card import affordance for importing at least a portion of credit card information from a remote server, and a credit card input affordance for receiving at least a portion of credit card information at an electronic device; dismiss the payment user interface; maintain display of the payment user interface; update the payment user interface to display an indication of a reason why a transaction request failed; display the payment user interface on only a portion of a first user interface; display a second payment user interface; dismiss the second payment user interface; maintain display of the second payment user interface; update the second payment user interface to display a second indication of a reason why a second transaction request failed; display the first payment user interface; maintain display of the first payment user interface; display a manual credit card entry affordance simultaneously with a real-time preview of an image obtained via a camera sensor; display a user interface for receiving at least a portion of credit card information via a displayed keyboard; display a manual credit card entry affordance for activating a manual credit card user interface for receiving at least a portion of credit card information via a keyboard; display a manual credit card user interface; display an expiration date of a credit card in a first entry field and a security code of a credit card in a second entry field; and display the expiration date of a credit card in the first entry field and the security code of a credit card in the second entry field.

[0347] For example, receiving unit 1212 can be used to: receive first authorization data; receive second authorization data; receive a reply to a transaction request; receive a selection of a credit card input offer; receive a selection of a credit card input offer when displaying a payment user interface; receive third authorization data; receive a second reply to a second transaction request; receive third authorization data; receive fourth authorization data; receive a second reply to the transaction request; receive a payment password; receive user input to put the device in an unlocked state; receive user input selecting a second payment account of multiple payment accounts connected to the device for payment transactions; receive a selection of a manual credit card entry offer; and receive a selection of a manual credit card entry offer.

[0348] For example, the determination unit 1214 can be used to: determine whether the first authorization data is valid; determine whether the fingerprint is consistent with the registered fingerprint that enables authorization of the payment transaction; determine whether the third authorization data is valid; whether the authorization data is valid; determine whether the corresponding fingerprint is consistent with the registered fingerprint that enables authorization of the payment transaction; determine whether the payment password is consistent with the registered password that enables authorization of the payment transaction; determine whether the credit card is of the first type based on a part of the account number of the credit card; and determine whether the credit card is of the first type based on the bin identification number of the credit card.

[0349] For example, the detection unit 1216 can be used to: detect a request to initiate a payment transaction; detect activation of a physical input mechanism; detect a fingerprint using an integrated biometric sensor; detect at least a portion of credit card information in the field of view of a camera sensor; detect a second request to initiate a second payment transaction; detect a corresponding fingerprint on a fingerprint sensor of the electronic device; and detect the presence of a field generated by a contactless payment transaction terminal via a short-range communication radio.

[0350] For example, the transmission unit can be used to: transmit a payment request corresponding to a payment transaction to one or more remote servers; transmit a transaction request when displaying a payment transaction user interface; transmit a second payment request corresponding to a second payment transaction to one or more remote servers; transmit second authorization data to a financial institution; and transmit a second transaction request corresponding to a payment transaction to one or more remote servers.

[0351] For example, the enabling unit 1220 may be used to: enable the device to participate in payment transactions via a short-range communication radio; forgo enabling the device to participate in payment transactions via a short-range communication radio; and enable the device to participate in payment transactions via a short-range communication radio while the device is in a locked state.

[0352] For example, the communication unit 1222 may be used to perform a handshake with a contactless payment transaction terminal using a short-range communication radio.

[0353] For example, the authorization unit 1224 can be used to: authorize a payment transaction.

[0354] For example, configuration unit 1226 can be used to: configure the device to respond to payment transaction requests via a short-range communication radio using at least partial credit card information of a payment account of multiple payment accounts linked to the device; and disable the device from participating in payment transactions via a short-range communication radio.

[0355] For example, the storage unit 1228 can be used to: store the second authorization data; and abandon storing the second authorization data.

[0356] Optionally, the functional modules of the device 1200 may be implemented by hardware, software, or a combination of hardware and software to implement the principles of the various described examples. Fig.12 The functional modules described in the present invention may be optionally combined or divided into sub-blocks to implement the principles of various described examples. Therefore, the description herein may optionally support any possible combination or division or further definition of the functional modules described herein.

[0357] The operations described above with reference to the accompanying drawings can be performed by Figure 1A-1B , Figure 2 , Figure 3 and Figure 5A-Figure 5B The operations described above with reference to the accompanying drawings can be implemented by Figure 1A-1B . For example, detecting an operation, displaying an operation, and determining an operation may be implemented by event classifier 170, event identifier 180, and event handler 190. Event detector 171 in event classifier 170 detects contact on touch-sensitive surface 112, and event dispatcher module 174 delivers event information to application 136-1. The corresponding event identifier 180 of application 136-1 compares the event information with the corresponding event definition, and determines whether the first contact at the first position on the touch-sensitive surface corresponds to a predefined event or sub-event, such as the activation of an available component on a user interface. When a corresponding predefined event or sub-event is detected, event identifier 180 activates event handler 190 associated with the detection of the event or sub-event. Event handler 190 may utilize or call data updater 176 or object updater 177 to update application internal state 192. In some embodiments, event handler 190 accesses the corresponding GUI updater 178 to update the content displayed by the application. Similarly, how to update the content displayed by the application based on the GUI updater 178 is described in detail below. Figure 1A-1B , Figure 2 , Figure 3 and Figure 5A-Figure 5B It will be apparent to those skilled in the art that the depicted components can be used to implement other processes.

[0358] Figures 13A-13E Illustrated are exemplary techniques and user interfaces for enabling an electronic device to participate in a payment transaction using a short-range communication radio according to some embodiments. The user interfaces in these figures are used to illustrate the processes described below, including Fig.14 process.

[0359] Fig.13A An electronic device 100 is illustrated in which the display is turned off, the integrated biometric sensor of the physical input mechanism (menu button) 204 is not enabled to detect fingerprints, the device is locked, and the short-range communication radio (e.g., NFC radio) of the device is not enabled to participate in payment transactions (first short-range communication radio payment mode). Typically, the device 100 may be in this state when it has not been recently used by a user. Although the short-range communication radio may be monitoring the NFC field, it is not enabled to participate in payment transactions.

[0360] The device may need to distinguish between a user request to unlock the device and a user request to enable the device to participate in a payment transaction. In some examples, (1) detecting a single press of the physical input mechanism 204 together with fingerprint authentication unlocks the device, and alternatively (2) detecting a double press of the physical input mechanism 204 together with fingerprint authentication enables the device to participate in a payment transaction. Additional details of this technology are described below.

[0361] exist Fig. 13B At, when the electronic device is locked and in a first short-range communication radio payment mode (i.e., not enabled to participate in payment transactions via a short-range communication radio), the device detects activation of a physical input mechanism 204 (e.g., a first press of a mechanical or capacitive button). The device detects a fingerprint (e.g., at least a portion of a fingerprint without identifying or matching the complete fingerprint) using an integrated biometric sensor. The device determines whether the fingerprint is consistent with a registered fingerprint. In some examples, the determination of whether the fingerprint is consistent with the registered fingerprint occurs before or after detecting the activation of the physical input mechanism. The device determines (e.g., at the electronic device) whether a set of one or more criteria is satisfied. The set of one or more criteria includes criteria that are satisfied when the physical input mechanism 204 is reactivated within a predetermined time period (e.g., 300ms) after the activation of the physical input mechanism (e.g., a second press of a mechanical or capacitive button, resulting in a double press).

[0362] exist Fig. 13C At, based on a determination that the fingerprint is consistent with a registered fingerprint and a determination that a set of one or more criteria is satisfied (e.g., a double press of the physical input mechanism 204 is detected), the device transitions to a second short-range communication radio payment mode that is different from the first short-range communication radio payment mode. For example, enabling the device to participate in a payment transaction via the short-range communication radio or transitioning the electronic device to a standby state in preparation for a payment transaction (e.g., the broadcasting device can make a payment).

[0363] As in Fig. 13C , the user interface of the device, when in the second short-range communication radio payment mode, may include an indication 1302 of the payment account to be used for the payment transaction. The user interface may also include one or more affordances 1304 that, when activated, change the payment account to be used for the payment transaction. While in the second short-range communication radio payment mode, the device will enable the contactless payment terminal to participate in the payment transaction by transmitting the payment account information to the contactless payment terminal. Thus, in order to use their electronic device for payment while it is in a locked state, the user may simply double-press the physical input mechanism 204 and place the device into the field of the contactless payment terminal.

[0364] exist Fig.13D At, based on a determination that the fingerprint is consistent with a registered fingerprint and a determination that a set of one or more criteria is not satisfied, the device is unlocked (e.g., the electronic device is transitioned from a locked state to an unlocked state). For example, in the unlocked state one or more affordances 1306 may be displayed, and when activated, one or more affordances 1306 start and / or display a corresponding application.

[0365] In the locked state, the electronic device 100 is powered on and operational, but is prevented from performing a predefined set of operations in response to user input. The predefined set of operations may include navigation between user interfaces, activation or deactivation of a predefined set of functions, and activation or deactivation of certain applications. The locked state may be used to prevent unintentional or unauthorized use of some functions of the electronic device 100, or activation or deactivation of some functions on the electronic device 100. In the unlocked state, the electronic device 100 is powered on and operational, and is not prevented from performing at least a portion of the predefined set of operations that cannot be performed when in the locked state.

[0366] In some embodiments, according to the determination that the fingerprint is consistent with the registered fingerprint and the determination that the set of one or more criteria is met (e.g., double pressing), the device abandons unlocking. As a result, the device is in the second short-range communication radio payment mode, but remains locked.

[0367] In some embodiments, based on the determination that the fingerprint is consistent with the registered fingerprint and the determination that a set of one or more criteria (e.g., double press) is not met, the device abandons the transition to the second short-range communication radio payment mode. For example, the device is unlocked, but the device remains in the first short-range communication radio payment mode.

[0368] In some embodiments, as discussed above, the first short-range communication radio payment mode is a mode in which the electronic device is not enabled to participate in payment transactions via the short-range communication radio, and the second short-range communication radio payment mode is a mode in which the device is enabled to participate in payment transactions via the short-range communication radio.

[0369] In some embodiments, the set of one or more criteria includes criteria that are satisfied when at least one payment account is linked to the device for use in a payment transaction using a short-range communication radio (e.g., a credit card was previously provided on the device for NFC payment). Thus, the device must be provided with at least one payment account number to satisfy the criteria. If the device is not provided with at least one payment account, then the device does not satisfy the set of one or more criteria.

[0370] Thus, in one example, a set of one or more criteria is satisfied when: (1) the physical input mechanism is reactivated within a predetermined time period (e.g., 300 ms) after activation of the physical input mechanism, and (2) at least one payment account is linked to the device for use in payment transactions using a short-range communication radio.

[0371] In some embodiments, in response to detecting activation of the physical input mechanism, the device enables the integrated biometric sensor to detect a fingerprint. Thus, power saving can be achieved by keeping the integrated biometric sensor disabled (e.g., turned off) and enabling it after detecting activation of the physical input mechanism.

[0372] In some embodiments, in response to detecting activation of the physical input mechanism, the device turns on a display of the device. As a result, the user is notified that activation of the physical input mechanism is detected.

[0373] In some embodiments, unlocking the device does not enable the device to participate in a payment transaction via a short-range communication radio. In some embodiments, enabling the device to participate in a payment transaction via a short-range communication radio does not unlock the electronic device.

[0374] In some embodiments, the device determines whether the fingerprint is consistent with an enrolled fingerprint after determining whether a set of one or more criteria is satisfied.

[0375] In some embodiments, based on the determination that the fingerprint is inconsistent with the registered fingerprint, the device abandons the transition to the second short-range communication radio payment mode and abandons unlocking the device. Therefore, if the user's fingerprint is not registered with the device, the device is not unlocked and does not transition to the second short-range communication radio mode.

[0376] In some embodiments, to unlock the device, the device provides fingerprint sensor information of the integrated biometric sensor (e.g., confirmation of a fingerprint match) to a first application of the electronic device. The first application is configured to unlock the device based on the fingerprint sensor information. For example, the integrated biometric sensor sends a single-use confirmation to the operating system allowing the operating system to unlock the device.

[0377] In some embodiments, based on a determination that the fingerprint is consistent with a registered fingerprint and a determination that a set of one or more criteria is not satisfied, the device transitions the integrated biometric sensor from the first sensor mode to the second sensor mode. For example, when in the second sensor mode, the integrated biometric sensor sends a confirmation of a single use to the operating system that allows the operating system to unlock the device. Based on a determination that the fingerprint is consistent with a registered fingerprint and a determination that a set of one or more criteria is satisfied, the device transitions the integrated biometric sensor from the first sensor mode to the third sensor mode. For example, when in the third sensor mode, the integrated biometric sensor sends a confirmation of a single use to the electronic wallet application that allows the electronic wallet application to enable the electronic device to participate in a payment transaction via a short-range communication radio. However, when in the first sensor mode, the integrated biometric sensor does not send a confirmation to the operating system or the electronic wallet application because it does not yet know whether a single-use confirmation should be sent to the operating system or the electronic wallet application.

[0378] Fig.13E An exemplary timeline for the detected activation of a physical input mechanism is illustrated. In a first exemplary timeline 1320, prior to event 1322, the electronic device is locked and in a first short-range communication radio payment mode (e.g., not enabled to participate in a payment transaction via a short-range communication radio). At event 1322, the electronic device detects activation of the physical input mechanism (e.g., a first press of a mechanical or capacitive button). At event 1324, the device detects reactivation of the physical input mechanism within a predetermined time period of 300ms. As a result, the device transitions to a second short-range communication radio payment mode that is different from the first short-range communication radio payment mode (e.g., enabled to participate in a payment transaction via a short-range communication radio) (if the user's fingerprint is authenticated).

[0379] In a second exemplary timeline 1330, the electronic device is locked and in a first short-range communication radio payment mode (e.g., not enabled to participate in payment transactions via a short-range communication radio) prior to event 1332. At event 1332, the electronic device detects activation of a physical input mechanism (e.g., a first press of a mechanical or capacitive button). At event 1334, the device is unlocked because a second activation of the physical input mechanism is not detected within a predetermined time period of 300 ms (if the user's fingerprint is authenticated).

[0380] Fig.141400 is a flow chart illustrating a method for enabling an electronic device to participate in a payment transaction using a short-range communication radio according to some embodiments. Method 1400 is performed at a device (e.g., 100, 300, 500) having a short-range communication radio (e.g., an NFC radio) and a physical input mechanism (e.g., a mechanical or capacitor button) including an integrated biometric sensor (e.g., a fingerprint sensor). Some operations in method 1400 may be combined, the order of some operations may be changed, and some operations may be omitted.

[0381] As described below, method 1400 provides an intuitive way to enable an electronic device to participate in a payment transaction using a short-range communication radio. The method reduces the cognitive burden on a user when enabling an electronic device to participate in a payment transaction, thereby creating a more efficient human-machine interface. For battery-powered computing devices, enabling a user to enable an electronic device to participate in a payment transaction using a short-range communication radio more quickly and efficiently saves power and increases the time between battery charges.

[0382] At block 1402, the electronic device is locked and in a first short-range communication radio payment mode.

[0383] At block 1404 , the electronic device detects activation of the physical input mechanism 204 (eg, a first press of a mechanical or capacitive button).

[0384] At block 1406 , the electronic device detects a fingerprint (eg, at least a portion of a fingerprint without identifying or matching a full fingerprint) using the integrated biometric sensor.

[0385] At block 1408, the electronic device determines whether the fingerprint is consistent with an enrolled fingerprint. In some examples, the determination of whether the fingerprint is consistent with an enrolled fingerprint occurs before or after detecting activation of the physical input mechanism.

[0386] At box 1410, the electronic device determines (e.g., at the electronic device) whether a set of one or more criteria is satisfied, where the set of one or more criteria includes a criterion that is satisfied when the physical input mechanism is reactivated within a predetermined time period (e.g., 300 ms) after activation of the physical input mechanism (e.g., a second press of a mechanical or capacitive button, resulting in a double press).

[0387] At box 1412, based on a determination that the fingerprint is consistent with a registered fingerprint and a determination that a set of one or more criteria are satisfied (e.g., a double press), a transition is made to a second short-range communication radio payment mode that is different from the first short-range communication radio payment mode (e.g., enabling the device to participate in payment transactions via a short-range communication radio; transitioning the electronic device to a standby state in preparation for a payment transaction (e.g., the broadcasting device can make payments)).

[0388] At block 1414, based on a determination that the fingerprint is consistent with an enrolled fingerprint and a determination that a set of one or more criteria is not satisfied, the device is unlocked.

[0389] In some embodiments, based on a determination that the fingerprint is consistent with an enrolled fingerprint and a determination that a set of one or more criteria is satisfied (eg, a double press), the electronic device forgoes unlocking the device.

[0390] In some embodiments, based on a determination that the fingerprint is consistent with a registered fingerprint and a determination that a set of one or more criteria are not met (e.g., a double press), the electronic device forgoes transitioning to a second short-range communication radio payment mode (e.g., forgoes enabling the device to participate in payment transactions via the short-range communication radio).

[0391] In some embodiments, the first short range communication radio payment mode is a mode in which the electronic device is not enabled to participate in payment transactions via the short range communication radio, and the second short range communication radio payment mode is a mode in which the device is enabled to participate in payment transactions via the short range communication radio.

[0392] In some embodiments, the set of one or more criteria includes criteria that are satisfied when at least one payment account is linked to a device for use in a payment transaction using a short-range communication radio (eg, a credit card was previously presented on the device for NFC payment).

[0393] In some embodiments, in response to detecting activation of the physical input mechanism, the electronic device enables the integrated biometric sensor to detect a fingerprint.

[0394] In some embodiments, the electronic device includes a display, and in response to detecting activation of the physical input mechanism, the electronic device turns on the display of the electronic device.

[0395] In some embodiments, unlocking the electronic device does not enable the electronic device to participate in a payment transaction via a short-range communication radio. In some embodiments, enabling the electronic device to participate in a payment transaction via a short-range communication radio does not unlock the electronic device.

[0396] In some embodiments, determining whether the fingerprint is consistent with an enrolled fingerprint occurs after determining whether a set of one or more criteria are satisfied.

[0397] In some embodiments, based on a determination that the fingerprint is inconsistent with an enrolled fingerprint, the electronic device forgoes transitioning to the second short-range communication radio payment mode and forgoes unlocking the device.

[0398] In some embodiments, unlocking the device further includes providing fingerprint sensor information of the integrated biometric sensor (e.g., confirmation of a fingerprint match) to a first application of the electronic device, the first application being configured to unlock the device. For example, the integrated biometric sensor sends a single-use confirmation to the OS allowing the operating system to unlock the device.

[0399] In some embodiments, based on a determination that the fingerprint is consistent with an enrolled fingerprint and a determination that a set of one or more criteria is not satisfied, the electronic device transitions the integrated biometric sensor from a first sensor mode to a second sensor mode. For example, while in the second sensor mode, the integrated biometric sensor sends a single-use confirmation to the operating system allowing the operating system to unlock the device.

[0400] In some embodiments, based on a determination that the fingerprint is consistent with a registered fingerprint and a determination that a set of one or more criteria is satisfied, the electronic device transitions the integrated biometric sensor from the first sensor mode to the third sensor mode. For example, when in the third sensor mode, the integrated biometric sensor sends a single-use confirmation to the electronic wallet application allowing the electronic wallet application to enable the electronic device to participate in a payment transaction via the short-range communication radio. However, when in the first sensor mode, the integrated biometric sensor does not send a confirmation to the operating system or the wallet application.

[0401] Note that the above reference method 1400 (e.g., Fig.14 ) also apply in a similar manner to the methods described below and above. For example, method 1400 may include one or more of the features of the various methods described above and below with reference to method 700, method 900, method 1100, and method 1600. For the sake of brevity, these details are not repeated below.

[0402] Figure 15A-15E Illustrated are exemplary techniques and user interfaces for enabling an electronic device to participate in a payment transaction using a short-range communication radio according to some embodiments. The user interfaces in these figures are used to illustrate the processes described below, including Fig.16 process.

[0403] Fig.15AThe electronic device 100 is illustrated with the display turned on, the integrated biometric sensor of the physical input mechanism (menu button) 204 enabled to detect fingerprints, the device locked, and the short-range communication radio (e.g., NFC radio) of the device not enabled to participate in payment transactions (first short-range communication radio payment mode). Typically, the device 100 may be in this state when the electronic device has been awakened by a user (such as by activating the physical input mechanism 204 or a button other than the physical input mechanism 204). Although the short-range communication radio may be monitoring the NFC field, it is not enabled to participate in payment transactions.

[0404] The device may need to distinguish between a user request to unlock the device and a user request to enable the device to participate in a payment transaction. In some examples, (1) detecting a fingerprint in the absence of a press of the physical input mechanism 204 together with fingerprint authentication unlocks the device, (2) detecting a single press of the physical input mechanism 204 together with fingerprint authentication unlocks the device, and (3) detecting a double press of the physical input mechanism 204 together with fingerprint authentication enables the device to participate in a payment transaction. Additional details of this technology are described below.

[0405] exist Fig. 15B At, when the electronic device is locked and in a first short-range communication radio payment mode (i.e., not enabled to participate in payment transactions via a short-range communication radio), the electronic device detects a fingerprint (e.g., at least a portion of a fingerprint) using an integrated biometric sensor. The electronic device determines whether the fingerprint is consistent with a registered fingerprint. In some examples, the determination of whether the fingerprint is consistent with the registered fingerprint occurs before or after detecting activation of the physical input mechanism. The electronic device determines (e.g., at the electronic device) whether a set of one or more criteria is satisfied, wherein the set of one or more criteria includes a criterion satisfied when the physical input mechanism 204 is activated within a predetermined time period (e.g., 300ms) after the fingerprint (e.g., the first touch of the physical input mechanism) is detected using the biometric sensor.

[0406] Based on a determination that the fingerprint is consistent with a registered fingerprint and a determination that a set of one or more criteria is not satisfied (e.g., no press within 300 ms), the electronic device is unlocked (e.g., the electronic device is transitioned from a locked state to an unlocked state), as in Fig. 15C For example, in the unlocked state one or more affordances 1506 may be displayed, and one or more affordances 1506, when activated, start and / or display corresponding applications.

[0407] Based on a determination that a set of one or more criteria are satisfied (e.g., a press of a physical input mechanism within 300ms), the electronic device determines (e.g., at the electronic device) whether the physical input mechanism is reactivated (e.g., a second press of a mechanical or capacitive button, resulting in a double press) within a second predetermined time period (e.g., 300ms) after activation of the physical input mechanism.

[0408] Based on a determination that the physical input mechanism has not been reactivated within a second predetermined time period (e.g., no second press within 100 ms of the first press) and a determination that the fingerprint is consistent with the registered fingerprint, the electronic device is unlocked (e.g., the electronic device is transitioned from a locked state to an unlocked state), as in Fig. 15C Thus, to unlock the electronic device, a user may place a finger on a physical input mechanism with an integrated biometric sensor and either (1) not press the physical input mechanism or (2) press the physical input mechanism once.

[0409] Based on a determination that the physical input mechanism is reactivated within a second predetermined time period (e.g., a double press) and based on a determination that the fingerprint is consistent with a registered fingerprint, the electronic device transitions to a second short-range communication radio payment mode that is different from the first short-range communication radio payment mode (e.g., enabling the device to participate in a payment transaction via a short-range communication radio; transitioning the electronic device to a standby state in preparation for a payment transaction (e.g., broadcasting that the device can make a payment)), as in Fig.15D As shown in the figure.

[0410] As in Fig.15D , the user interface of the device, when in the second short-range communication radio payment mode, may include an indication 1502 of the payment account to be used for the payment transaction. The user interface may also include one or more affordances 1504 that, when activated, change the payment account to be used for the payment transaction. While in the second short-range communication radio payment mode, the device will enable the contactless payment terminal to participate in the payment transaction by transmitting the payment account information to the contactless payment terminal. Thus, in order to use their electronic device for payment while it is in a locked state, the user may simply double-press the physical input mechanism 204 and place the device into the field of the contactless payment terminal.

[0411] In the locked state, the electronic device 100 is powered on and operational, but is prevented from performing a predefined set of operations in response to user input. The predefined set of operations may include navigation between user interfaces, activation or deactivation of a predefined set of functions, and activation or deactivation of certain applications. The locked state may be used to prevent unintentional or unauthorized use of some functions of the electronic device 100, or activation or deactivation of some functions on the electronic device 100. In the unlocked state, the electronic device 100 is powered on and operational, and is not prevented from performing at least a portion of the predefined set of operations that cannot be performed when in the locked state.

[0412] In some embodiments, based on a determination that the fingerprint is consistent with an enrolled fingerprint and a determination that a set of one or more criteria is satisfied (eg, a double press), the electronic device forgoes unlocking.

[0413] In some embodiments, based on a determination that the fingerprint is consistent with a registered fingerprint and a determination that a set of one or more criteria are not met (e.g., a double press), the electronic device forgoes transitioning to a second short-range communication radio payment mode (e.g., forgoes enabling the device to participate in payment transactions via the short-range communication radio).

[0414] In some embodiments, the first short range communication radio payment mode is a mode in which the electronic device is not enabled to participate in payment transactions via the short range communication radio, and the second short range communication radio payment mode is a mode in which the device is enabled to participate in payment transactions via the short range communication radio.

[0415] In some embodiments, the set of one or more criteria includes criteria that are satisfied when at least one payment account is linked to a device for use in a payment transaction using a short-range communication radio (eg, a credit card was previously presented on the device for NFC payment).

[0416] Thus, in this example, a set of one or more criteria is satisfied when: (1) the physical input mechanism is activated within a predetermined time period (e.g., 300 ms) after detection of the fingerprint, and (2) at least one payment account is linked to the device for use in payment transactions using a short-range communication radio.

[0417] In some embodiments, unlocking the device does not enable the device to participate in payment transactions via the short-range communication radio. In some embodiments, enabling the device to participate in payment transactions via the short-range communication radio does not unlock the device.

[0418] In some embodiments, determining whether the fingerprint is consistent with an enrolled fingerprint occurs after determining whether a set of one or more criteria are satisfied.

[0419] In some embodiments, based on a determination that the fingerprint is inconsistent with an enrolled fingerprint, the electronic device forgoes transitioning to the second short-range communication radio payment mode and forgoes unlocking the device.

[0420] In some embodiments, the electronic device includes a display, and when the fingerprint is detected using the integrated biometric sensor, the display is turned on.

[0421] In some embodiments, unlocking the device further includes providing fingerprint sensor information of the integrated biometric sensor (e.g., confirmation of a fingerprint match) to a first application of the electronic device, the first application being configured to unlock the device. For example, the integrated biometric sensor sends a single-use confirmation to the OS allowing the operating system to unlock the device.

[0422] In some embodiments, based on a determination that (1) the fingerprint matches an enrolled fingerprint and (2) a set of one or more criteria are not met (e.g., no presses within 300 ms), the electronic device transitions the integrated biometric sensor from a first sensor mode to a second sensor mode. For example, while in the second sensor mode, the integrated biometric sensor sends a single-use confirmation to the operating system allowing the operating system to unlock the device.

[0423] In some embodiments, based on (1) a set of one or more criteria being satisfied (e.g., a press within 300 ms), (2) the physical input mechanism not being reactivated within a second predetermined time period (e.g., no second press within 300 ms of the first press), and (3) a determination that the fingerprint is consistent with an enrolled fingerprint, the electronic device transitions the integrated biometric sensor from a first sensor mode to a second sensor mode. For example, while in the second sensor mode, the integrated biometric sensor sends a single-use confirmation to the operating system allowing the operating system to unlock the device.

[0424] In some embodiments, based on (1) a set of one or more criteria being satisfied (e.g., a press within 300 ms), (2) the physical input mechanism being reactivated within a second predetermined time period (e.g., within another 300 ms, resulting in a double press), and (3) a determination that the fingerprint is consistent with an enrolled fingerprint, the electronic device transitions the integrated biometric sensor from the first sensor mode to the third sensor mode. For example, while in the third sensor mode, the integrated biometric sensor sends a single-use confirmation to the wallet application allowing the wallet application to enable the device to participate in a payment transaction via the short-range communication radio. However, while in the first sensor mode, the integrated biometric sensor does not send a confirmation to the operating system or the wallet application.

[0425] Thus, (1) detecting a fingerprint in the absence of a press of the physical input mechanism 204 together with fingerprint authentication transitions the integrated biometric sensor from the first sensor mode to the second sensor mode, (2) detecting a single press of the physical input mechanism 204 together with fingerprint authentication transitions the integrated biometric sensor from the first sensor mode to the second sensor mode, and (3) detecting a double press of the physical input mechanism 204 together with fingerprint authentication transitions the integrated biometric sensor from the first sensor mode to the third sensor mode.

[0426] Fig.15E Exemplary timelines for detected activations of physical input mechanisms are illustrated. In a first exemplary timeline 1520, prior to event 1522, the electronic device is locked and in a first short-range communication radio payment mode (e.g., not enabled to participate in payment transactions via a short-range communication radio). At event 1522, the electronic device detects a finger on a fingerprint sensor. At event 1524, the device is unlocked because activation of the physical input mechanism is not detected within a predetermined time period of 275 ms (if the user's fingerprint is authenticated).

[0427] In a second exemplary timeline 1530, prior to event 1532, the electronic device is locked and in a first short-range communication radio payment mode (e.g., not enabled to participate in payment transactions via the short-range communication radio). At event 1532, the electronic device detects a finger on a fingerprint sensor. At event 1534, the device detects activation of a physical input mechanism within a predetermined time period of 275 ms. At event 1536, the device unlocks because activation of the physical input mechanism is not detected within a second predetermined time period of 300 ms (if the user's fingerprint is authenticated).

[0428] In a third exemplary timeline 1540, prior to event 1542, the electronic device is locked and in a first short-range communication radio payment mode (e.g., not enabled to participate in payment transactions via the short-range communication radio). At event 1542, the electronic device detects a finger on a fingerprint sensor. At event 1544, the device detects activation of a physical input mechanism within a predetermined time period of 275 ms. At event 1546, the device detects activation of the physical input mechanism within 300 ms, and as a result, the device transitions to a second short-range communication radio payment mode different from the first short-range communication radio (e.g., enabled to participate in payment transactions via the short-range communication radio) (if the user's fingerprint is authenticated).

[0429] Fig.161600 is a flow chart illustrating a method for enabling an electronic device to participate in a payment transaction using a short-range communication radio according to some embodiments. Method 1600 is performed at a device (e.g., 100, 300, 500) having a short-range communication radio (e.g., an NFC radio) and a physical input mechanism (e.g., a mechanical or capacitor button) including an integrated biometric sensor (e.g., a fingerprint sensor). Some operations in method 1600 may be combined, the order of some operations may be changed, and some operations may be omitted.

[0430] As described below, method 1600 provides an intuitive way to enable an electronic device to participate in a payment transaction using a short-range communication radio. The method reduces the cognitive burden on a user when enabling an electronic device to participate in a payment transaction, thereby creating a more efficient human-machine interface. For battery-powered computing devices, enabling a user to enable an electronic device to participate in a payment transaction using a short-range communication radio more quickly and efficiently saves power and increases the time between battery charges.

[0431] At block 1602, the electronic device is locked and in a first short-range communication radio payment mode.

[0432] At block 1604, the electronic device detects a fingerprint (eg, at least a portion of a fingerprint) using an integrated biometric sensor.

[0433] At block 1606, the electronic device determines whether the fingerprint is consistent with an enrolled fingerprint. In some examples, the determination of whether the fingerprint is consistent with an enrolled fingerprint occurs before or after detecting activation of the physical input mechanism.

[0434] At box 1608, the electronic device determines (e.g., at the electronic device) whether a set of one or more criteria is satisfied, where the set of one or more criteria includes a criterion that is satisfied when the physical input mechanism is activated within a first predetermined time period after a fingerprint is detected using a biometric sensor (e.g., a first touch of a mechanical or capacitive button).

[0435] At box 1610, based on the determination that the fingerprint is consistent with the registered fingerprint and the determination that the set of one or more criteria is not met (e.g., no press), the electronic device is unlocked (e.g., the electronic device is transitioned from a locked state to an unlocked state).

[0436] At block 1612, based on a determination that a set of one or more criteria is satisfied (eg, a press), blocks 1614-1618 are evaluated.

[0437] At box 1614, the device determines (e.g., at the electronic device) whether the physical input mechanism is reactivated within a second predetermined time period after the activation of the physical input mechanism (e.g., a second press of a mechanical or capacitive button, resulting in a double press).

[0438] At box 1616, based on a determination that the physical input mechanism has not been reactivated within a second predetermined time period (e.g., a second press resulting in a double press) and a determination that the fingerprint is consistent with a registered fingerprint, the electronic device is unlocked (e.g., transitioning the electronic device from a locked state to an unlocked state).

[0439] At box 1618, based on a determination that the physical input mechanism has been reactivated within a second predetermined time period (e.g., a double press) and based on a determination that the fingerprint is consistent with a registered fingerprint, the electronic device transitions to a second short-range communication radio payment mode that is different from the first short-range communication radio payment mode (e.g., enabling the device to participate in payment transactions via a short-range communication radio; transitioning the electronic device to a standby state in preparation for a payment transaction (e.g., the broadcasting device can make payments)).

[0440] In some embodiments, based on a determination that the fingerprint is consistent with an enrolled fingerprint and a determination that a set of one or more criteria is satisfied (eg, a double press), the electronic device forgoes unlocking.

[0441] In some embodiments, based on a determination that the fingerprint is consistent with a registered fingerprint and a determination that a set of one or more criteria are not met (e.g., a double press), the electronic device forgoes transitioning to a second short-range communication radio payment mode (e.g., forgoes enabling the device to participate in payment transactions via the short-range communication radio).

[0442] In some embodiments, the first short range communication radio payment mode is a mode in which the electronic device is not enabled to participate in payment transactions via the short range communication radio, and the second short range communication radio payment mode is a mode in which the device is enabled to participate in payment transactions via the short range communication radio.

[0443] In some embodiments, the set of one or more criteria includes criteria that are satisfied when at least one payment account is linked to a device for use in a payment transaction using a short-range communication radio (eg, a credit card was previously presented on the device for NFC payment).

[0444] Thus, in this example, a set of one or more criteria is satisfied when: (1) the physical input mechanism is activated within a predetermined time period (e.g., 300 ms) after detection of the fingerprint, and (2) at least one payment account is linked to the device for use in payment transactions using a short-range communication radio.

[0445] In some embodiments, unlocking the device does not enable the device to participate in payment transactions via the short-range communication radio. In some embodiments, enabling the device to participate in payment transactions via the short-range communication radio does not unlock the device.

[0446] In some embodiments, determining whether the fingerprint is consistent with an enrolled fingerprint occurs after determining whether a set of one or more criteria are satisfied.

[0447] In some embodiments, based on a determination that the fingerprint is inconsistent with an enrolled fingerprint, the electronic device forgoes transitioning to the second short-range communication radio payment mode and forgoes unlocking the device.

[0448] In some embodiments, the electronic device includes a display, and when the fingerprint is detected using the integrated biometric sensor, the display is turned on.

[0449] In some embodiments, unlocking the device further includes providing fingerprint sensor information of the integrated biometric sensor (e.g., confirmation of a fingerprint match) to a first application of the electronic device, the first application being configured to unlock the device. For example, the integrated biometric sensor sends a single-use confirmation to the OS allowing the operating system to unlock the device.

[0450] In some embodiments, based on (1) a determination that the fingerprint is consistent with a registered fingerprint and (2) a set of one or more criteria are not met (e.g., no press within 200ms), the electronic device transitions the integrated biometric sensor from a first sensor mode to a second sensor mode. For example, while in the second sensor mode, the integrated biometric sensor sends a confirmation to the operating system that allows the operating system to unlock the device for a single use. Based on (1) a set of one or more criteria are met (e.g., press within 300ms), (2) the physical input mechanism is not reactivated within a second predetermined time period (e.g., no second press within 300ms of the first press), and (3) a determination that the fingerprint is consistent with a registered fingerprint, the electronic device transitions the integrated biometric sensor from the first sensor mode to the second sensor mode. For example, while in the second sensor mode, the integrated biometric sensor sends a confirmation to the operating system that allows the operating system to unlock the device for a single use. Based on (1) a set of one or more criteria being satisfied (e.g., a press within 300 ms), (2) the physical input mechanism being reactivated within a second predetermined time period (e.g., within another 300 ms, resulting in a double press), and (3) a determination that the fingerprint is consistent with an enrolled fingerprint, the electronic device transitions the integrated biometric sensor from the first sensor mode to the third sensor mode. For example, while in the third sensor mode, the integrated biometric sensor sends a single-use confirmation to the wallet application allowing the wallet application to enable the device to participate in a payment transaction via the short-range communication radio. However, while in the first sensor mode, the integrated biometric sensor does not send a confirmation to the operating system or the wallet application.

[0451] Thus, (1) detecting a fingerprint in the absence of a press of the physical input mechanism 204 together with fingerprint authentication transitions the integrated biometric sensor from the first sensor mode to the second sensor mode, (2) detecting a single press of the physical input mechanism 204 together with fingerprint authentication transitions the integrated biometric sensor from the first sensor mode to the second sensor mode, and (3) detecting a double press of the physical input mechanism 204 together with fingerprint authentication transitions the integrated biometric sensor from the first sensor mode to the third sensor mode.

[0452] Note that the above reference method 1600 (e.g., Fig.16 ) also apply in a similar manner to the methods described below and above. For example, method 1600 may include one or more of the features of the various methods described above and below with reference to method 700, method 900, method 1100, and method 1400. For the sake of brevity, these details are not repeated below.

[0453] According to some embodiments, Fig.17An exemplary functional block diagram of an electronic device 1700 configured according to the principles of various described embodiments is shown. According to some embodiments, the functional blocks of the electronic device 1700 are configured to perform the techniques described above. The functional blocks of the device 1700 may be optionally implemented by hardware, software, or a combination of hardware and software to perform the principles of various described examples. Those skilled in the art will appreciate that Fig.17 The functional blocks described in the invention may be optionally combined or separated into sub-blocks to implement the principles of various described examples. Therefore, the description herein may optionally support any possible combination or separation or further limitation of the functional blocks described herein.

[0454] As in Fig.17 As shown in , the electronic device 1700 includes a (optional) display unit 1702 configured to display a graphical user interface, a physical input mechanism unit 1704 including an integrated biometric sensor unit 1706 configured to detect a fingerprint, a short-range communication radio unit 1708, and a processing unit 1710 coupled to the (optional) display unit 1704, the physical input mechanism unit 1704 including an integrated biometric sensor unit 1706 configured to detect a fingerprint, and the short-range communication radio unit 1708. In some embodiments, the processing unit 1710 includes a detection unit 1712, a determination unit 1714, a transition unit 1716, an unlocking unit 1718, a display enabling unit 1720, an enabling unit 1722, and a providing unit 1724.

[0455] The processing unit 1710 is configured to: detect (e.g., using the detection unit 1712) the activation of the physical input mechanism unit 1704; detect (e.g., using the detection unit 1712) a fingerprint using the integrated biometric sensor unit 1706; determine (e.g., using the determination unit 1714) whether the fingerprint is consistent with a registered fingerprint; determine (e.g., using the determination unit 1714) whether a set of one or more criteria is satisfied, wherein the set of one or more criteria includes criteria satisfied when the physical input mechanism unit 1704 is reactivated within a predetermined time period after the activation of the physical input mechanism unit 1704; based on the determination that the fingerprint is consistent with the registered fingerprint and the determination that the set of one or more criteria is satisfied, transition (e.g., using the transition unit 1716) to a second short-range communication radio payment mode different from the first short-range communication radio payment mode (e.g., using the short-range communication radio unit 1708); and, based on the determination that the fingerprint is consistent with the registered fingerprint and the determination that the set of one or more criteria is not satisfied, unlock the electronic device (e.g., using the unlocking unit 1719).

[0456] According to some embodiments, processing unit 1710 is further configured to: based on a determination that the fingerprint is consistent with an enrolled fingerprint and a determination that a set of one or more criteria is satisfied, forego unlocking (eg, using unlocking unit 1718) the device.

[0457] According to some embodiments, processing unit 1710 is further configured to: based on a determination that the fingerprint is consistent with a registered fingerprint and a determination that a set of one or more criteria is not satisfied, abandon transition (e.g., using transition unit 1716) to a second short-range communication radio payment mode.

[0458] In accordance with some embodiments, the first short-range communication radio payment mode is a mode in which the electronic device is not enabled to participate in payment transactions via the short-range communication radio unit 1708, and the second short-range communication radio payment mode is a mode in which the device is enabled to participate in payment transactions via the short-range communication radio unit 1708.

[0459] According to some embodiments, the set of one or more criteria includes criteria that are satisfied when at least one payment account is linked to the electronic device for use in payment transactions using the short-range communication radio unit 1708.

[0460] According to some embodiments, the processing unit 1710 is further configured to: in response to detecting (eg, using the detecting unit 1712 ) activation of the physical input mechanism unit 1704 , enable (eg, using the enabling unit 1722 ) the integrated biometric sensor unit 1706 to detect a fingerprint.

[0461] According to some embodiments, the processing unit 1710 is further configured to: in response to detecting (eg, using the detection unit 1712 ) activation of the physical input mechanism unit 1704 , turn on (eg, using the display enabling unit 1720 ) the display unit 1702 of the electronic device.

[0462] According to some embodiments, unlocking the electronic device (eg, using unlocking unit 1718 ) does not enable (eg, using enabling unit 1722 ) the device to participate in a payment transaction via short-range communication radio 1708 .

[0463] According to some embodiments, the device is enabled (eg, using enabling unit 1722) to participate in a payment transaction via short-range communication radio unit 1708 without unlocking the device (eg, using unlocking unit 1718).

[0464] According to some embodiments, determining (eg, using determining unit 1714 ) whether the fingerprint is consistent with an enrolled fingerprint occurs after determining (eg, using determining unit 1714 ) whether a set of one or more criteria is satisfied.

[0465] According to some embodiments, the processing unit 1710 is further configured to: based on a determination that the fingerprint is inconsistent with a registered fingerprint, abandon the transition (e.g., using the transition unit 1716) to the second short-range communication radio payment mode and abandon unlocking (e.g., using the unlocking unit 1718) the electronic device.

[0466] According to some embodiments, in order to unlock the device, the processing unit 1710 is further configured to: provide (e.g., using the providing unit 1724) fingerprint sensor information of the integrated biometric sensor unit 1706 to a first application of the electronic device, wherein the first application is configured to unlock (e.g., using the unlocking unit 1718) the device.

[0467] According to some embodiments, the processing unit 1710 is further configured to: transition the integrated biometric sensor unit 1706 from the first sensor mode to the second sensor mode (e.g., using the transition unit 1716) based on the determination that the fingerprint is consistent with the registered fingerprint and the determination that the set of one or more criteria is not satisfied; and transition the integrated biometric sensor unit 1706 from the first sensor mode to the third sensor mode (e.g., using the transition unit 1716) based on the determination that the fingerprint is consistent with the registered fingerprint and the determination that the set of one or more criteria is not satisfied.

[0468] References Fig.14 The described operations are optionally performed by Figure 1A-1B or Fig.17 1404, determining operation 1406, and transition operation 1412 may be implemented by event classifier 170, event identifier 180, and event handler 190. Event monitor 171 in event classifier 170 detects contact on touch-sensitive display 112, and event dispatcher module 174 delivers event information to application 136-1. A corresponding event identifier 180 of application 136-1 compares the event information with a corresponding event definition 186, and determines whether a first contact at a first position on the touch-sensitive surface corresponds to a predefined event or sub-event, such as activation of an available item on a user interface. When a corresponding predefined event or sub-event is detected, event identifier 180 activates an event handler 190 associated with the detection of the event or sub-event. Event handler 190 may use or call data updater 176 or object updater 177 to update application internal state 192. In some embodiments, event handler 190 accesses a corresponding GUI updater 178 to update the content displayed by the application. Similarly, it will be clear to those skilled in the art how other processes can be based on Figure 1A-1B The components depicted are implemented.

[0469] According to some embodiments, Fig.18 An exemplary functional block diagram of an electronic device 1800 configured according to the principles of the various described embodiments is shown. According to some embodiments, the functional blocks of the electronic device 1800 are configured to perform the techniques described above. The functional blocks of the device 1800 may be optionally implemented by hardware, software, or a combination of hardware and software to perform the principles of the various described examples. Those skilled in the art will appreciate that Fig.18 The functional blocks described in the invention may be optionally combined or separated into sub-blocks to implement the principles of various described examples. Therefore, the description herein may optionally support any possible combination or separation or further limitation of the functional blocks described herein.

[0470] As in Fig.18 As shown in , the electronic device 1800 includes a (optional) display unit 1802 configured to display a graphical user interface, a physical input mechanism unit 1804 including an integrated biometric sensor unit 1806 configured to detect a fingerprint, a short-range communication radio unit 1808, and a processing unit 1810 coupled to the (optional) display unit 1804, the physical input mechanism unit 1804 including an integrated biometric sensor unit 1806 configured to detect a fingerprint, and the short-range communication radio unit 1808. In some embodiments, the processing unit 1810 includes a detection unit 1812, a determination unit 1814, a transition unit 1816, an unlocking unit 1818, an enabling unit 1820, and a providing unit 1822.

[0471] The processing unit 1810 is configured to: detect (e.g., using the detection unit 1812) a fingerprint using the integrated biometric sensor unit 1806; determine (e.g., using the determination unit 1814) whether the fingerprint is consistent with a registered fingerprint; determine (e.g., using the determination unit 1814) whether a set of one or more criteria is satisfied, wherein the set of one or more criteria includes a criterion satisfied when the physical input mechanism unit 1804 is activated within a first predetermined time period after the fingerprint is detected using the biometric sensor unit 1806; unlock (e.g., using the unlocking unit 1818) the electronic device based on the determination that the fingerprint is consistent with the registered fingerprint and the determination that the set of one or more criteria is not satisfied; and unlock (e.g., using the unlocking unit 1818) the electronic device based on the determination that the fingerprint is consistent with the registered fingerprint and the determination that the set of one or more criteria is not satisfied. Determination: determining (for example, using determination unit 1814) whether the physical input mechanism unit 1804 is reactivated within a second predetermined time period after the activation of the physical input mechanism unit 1804; unlocking (for example, using unlocking unit 1818) the electronic device based on the determination that the physical input mechanism unit 1804 has not been reactivated within the second predetermined time period and the determination that the fingerprint is consistent with the registered fingerprint; and transitioning (for example, using transition unit 1816) to a second short-range communication radio payment mode different from the first short-range communication radio payment mode (for example, using short-range communication radio unit 1808) based on the determination that the physical input mechanism unit 1804 is reactivated within the second predetermined time period and the determination that the fingerprint is consistent with the registered fingerprint.

[0472] According to some embodiments, processing unit 1810 is further configured to: based on a determination that the fingerprint is consistent with an enrolled fingerprint and a determination that a set of one or more criteria is satisfied, forego unlocking (eg, using unlocking unit 1818) the device.

[0473] According to some embodiments, processing unit 1810 is further configured to: based on a determination that the fingerprint is consistent with an enrolled fingerprint and a determination that a set of one or more criteria is not satisfied, abandon transition (e.g., using transition unit 1816) to a second short-range communication radio payment mode.

[0474] In accordance with some embodiments, the first short-range communication radio payment mode is a mode in which the electronic device is not enabled to participate in payment transactions via the short-range communication radio unit 1808, and the second short-range communication radio payment mode is a mode in which the device is enabled to participate in payment transactions via the short-range communication radio unit 1808.

[0475] According to some embodiments, the set of one or more criteria includes criteria that are satisfied when at least one payment account is linked to the device for use in payment transactions using the short-range communication radio unit 1808 .

[0476] According to some embodiments, unlocking the device (eg, using unlocking unit 1818 ) does not enable (eg, using enabling unit 1820 ) the device to participate in payment transactions via short-range communication radio 1808 .

[0477] According to some embodiments, the device is enabled (eg, using enabling unit 1820 ) to participate in a payment transaction via short-range communication radio unit 1808 without unlocking the device (eg, using unlocking unit 1818 ).

[0478] According to some embodiments, determining (eg, using determining unit 1814 ) whether the fingerprint is consistent with an enrolled fingerprint occurs after determining (eg, using determining unit 1814 ) whether a set of one or more criteria is satisfied.

[0479] According to some embodiments, the processing unit 1810 is further configured to: based on a determination that the fingerprint is inconsistent with a registered fingerprint, abandon the transition (e.g., using the transition unit 1816) to the second short-range communication radio payment mode and abandon unlocking (e.g., using the unlocking unit 1818) the device.

[0480] According to some embodiments, display unit 1802 is turned on when a fingerprint is detected (eg, using detection unit 1812) using integrated biometric sensor unit 1806.

[0481] According to some embodiments, in order to unlock the device, the processing unit 1810 is further configured to: provide (e.g., using the providing unit 1822) fingerprint sensor information of the integrated biometric sensor unit 1806 to a first application of the electronic device, and the first application is configured to unlock (e.g., using the unlocking unit 1818) the electronic device.

[0482] According to some embodiments, the processing unit 1810 is further configured to: transition the integrated biometric sensor unit 1806 from the first sensor mode to the second sensor mode (e.g., using the transition unit 1816) based on the determination that the fingerprint is consistent with the registered fingerprint and the determination that the set of one or more criteria is not satisfied; and based on the determination that the fingerprint is consistent with the registered fingerprint and the determination that the set of one or more criteria is satisfied: transition the integrated biometric sensor unit 1806 from the first sensor mode to the second sensor mode (e.g., using the transition unit 1816) based on the determination that the physical input mechanism has not been reactivated within a second predetermined time period and the determination that the fingerprint is consistent with the registered fingerprint; and transition the integrated biometric sensor unit 1806 from the first sensor mode to the third sensor mode based on the determination that the physical input mechanism is reactivated within the second predetermined time period and the determination that the fingerprint is consistent with the registered fingerprint.

[0483] References Fig.16 The described operations are optionally performed by Figure 1A-1B or Fig.18 1604, determining operation 1606, and unlocking operation 1610 may be implemented by event classifier 170, event identifier 180, and event handler 190. Event monitor 171 in event classifier 170 detects contact on touch-sensitive display 112, and event dispatcher module 174 delivers event information to application 136-1. A corresponding event identifier 180 of application 136-1 compares the event information with a corresponding event definition 186, and determines whether a first contact at a first position on the touch-sensitive surface corresponds to a predefined event or sub-event, such as activation of an available item on a user interface. When a corresponding predefined event or sub-event is detected, event identifier 180 activates an event handler 190 associated with the detection of the event or sub-event. Event handler 190 may use or call data updater 176 or object updater 177 to update application internal state 192. In some embodiments, event handler 190 accesses a corresponding GUI updater 178 to update the content displayed by the application. Similarly, it will be clear to those skilled in the art how other processes can be based on Figure 1A-1B The components depicted are implemented.

[0484] For the purpose of illustration, the present invention has been described with reference to specific embodiments. However, the above exemplary discussion is not intended to be exhaustive or to limit the present invention to the exact form disclosed. Many modifications and changes can be made in accordance with the above teachings. These embodiments are selected and described in order to best illustrate the principles of the technology and its practical application. Thereby enabling those skilled in the art to best utilize the technology and various embodiments that make various modifications suitable for the specific use envisioned.

[0485] Although the disclosure and examples have been fully described with reference to the accompanying drawings, it should be noted that various changes and modifications will become apparent to those skilled in the art. Such changes and modifications should be understood to be included within the scope of the disclosure and examples as defined by the claims.

[0486] As described above, one aspect of the present technology is to collect and use available data from various sources to improve the content of the invitations delivered to users or any other content that may be of interest to them. The present disclosure contemplates that in some instances, the collected data may include personal information data that uniquely identifies or can be used to contact or locate a specific person. Such personal information data may include demographic data, location-based data, telephone numbers, email addresses, home addresses, or any other identifying information.

[0487] The present disclosure recognizes that in the present technology, the use of such personal information data can be used to benefit the user. For example, the personal information data can be used to deliver targeted content of greater interest to the user. Thus, the use of such personal information data can computationally control the content delivered. In addition, other uses of personal information data that benefit the user are also contemplated through the present disclosure.

[0488] The disclosure further contemplates that the entity responsible for collecting, analyzing, publicizing, transmitting, storing, or otherwise using such personal information data will comply with well-established privacy policies and / or privacy practices. In particular, such an entity should implement and consistently use privacy policies and practices that are generally considered to meet or exceed industry or government requirements for maintaining privacy and security of personal information data. For example, personal information from the user should be collected for the legal, reasonable use of the entity, and not shared or sold outside those legal uses. In addition, only after the user's informed consent, such collection can be carried out. In addition, such an entity will perform any necessary steps for security protection and safe access to such personal information data and ensure that other people with servers for personal information data adhere to their privacy policies and procedures. In addition, such an entity can subject themselves to evaluation by a third party to prove that they adhere to widely accepted privacy policies and practices.

[0489] Notwithstanding the foregoing description, the present disclosure also contemplates embodiments in which a user selectively blocks the use of or access to personal information data. That is, the present disclosure contemplates that hardware and / or software elements may be provided to prevent or block access to such personal information data. For example, in the case of an advertising delivery service, the present technology may be configured to allow a user to "opt-in" or "opt-out" from the collection of personal information data during registration for the service. In another example, a user may choose not to provide location information for a targeted content delivery service. In yet another example, a user may choose not to provide precise location information, but allow transmission of location region information.

[0490] Therefore, while the present disclosure broadly covers the use of personal information data to implement one or more of the various disclosed embodiments, the present disclosure also contemplates that various embodiments may be attempted without requiring access to such personal information data. That is, the lack of all or a portion of the information in such personal information data does not render the various embodiments of the present technology inoperable. For example, based on non-personal information data or a minimum amount of personal information (such as content requested by a device associated with a user, non-personal information that can be used for content delivery services, or publicly available information), content may be selected and delivered to a user by inferring preferences.

Claims

1. A method comprising: At Electronic Equipment: while displaying a first user interface corresponding to the first application, detecting a request for initiating a payment transaction; in response to detecting the request to initiate the payment transaction, displaying a payment user interface corresponding to a second application different from the first application while maintaining at least a portion of the first user interface corresponding to the first application; While displaying the payment user interface, receiving first authorization data; After receiving the first authorization data, determining whether the first authorization data is valid; Based on determining that the first authorization data is valid, simultaneously displaying the payment user interface and a visual indication that the first authorization data is valid; receiving second authorization data; After receiving the first authorization data and the second authorization data, transmitting a transaction request corresponding to the payment transaction to one or more remote servers; receiving a response to the transaction request; as well as In response to receiving the reply to the transaction request: Based on the determination that the transaction request is successful, releasing the payment user interface; as well as Based on a determination that the transaction request has failed, maintaining display of the payment user interface and updating the payment user interface to display an indication of a reason why the transaction request has failed.

2. The method of claim 1 , wherein the indication of the reason why the transaction request failed comprises: an indication that the transaction request failed due to a merchant associated with the payment transaction; or An indication that the transaction request failed due to a financial institution associated with the payment transaction.

3. The method according to any one of claims 1-2, wherein displaying the payment user interface comprises displaying the payment user interface only on a portion of the first user interface.

4. The method according to any one of claims 1-2, wherein transmitting the transaction request includes transmitting the transaction request while displaying the payment user interface, and wherein receiving the reply to the transaction request includes receiving the reply to the transaction request while displaying the payment user interface.

5. The method according to any one of claims 1 to 2, further comprising: storing the second authorization data based on a determination that the transaction request is successful; as well as Based on the determination that the transaction request fails, the storing of the second authorization data is abandoned.

6. The method according to any one of claims 1 to 2, further comprising: detecting a second request for initiating a second payment transaction; In response to detecting the second request for initiating the second payment transaction, displaying a second payment user interface; While displaying the second payment user interface, receiving third authorization data; After receiving the third authorization data, determining whether the third authorization data is valid; after receiving the third authorization data, transmitting to one or more remote servers a second transaction request corresponding to the second payment transaction, wherein the second transaction request is based at least in part on a stored representation of the second authorization data; as well as A second reply to the second transaction request is received.

7. The method according to claim 6, further comprising: In response to receiving the second reply to the second transaction request: upon determining that the second transaction request is successful, releasing the second payment user interface; as well as Based on a determination that the second transaction request has failed, display of the second payment user interface is maintained and the second payment user interface is updated to display a second indication of a second reason why the second transaction request has failed.

8. The method according to any one of claims 1-2, wherein transmitting the transaction request corresponding to the payment transaction to the one or more remote servers comprises: The second authorization data is transmitted to a financial institution.

9. The method according to any one of claims 1-2, further comprising: According to the determination of the failure of the transaction request: While displaying the payment user interface, receiving third authorization data; After receiving the third authorization data, determining whether the third authorization data is valid; receiving fourth authorization data; After receiving the third authorization data and the fourth authorization data, transmitting a second transaction request corresponding to the payment transaction to one or more remote servers; as well as A second reply to the transaction request is received.

10. A method according to any one of claims 1-2, wherein receiving first authorization data includes detecting a corresponding fingerprint on a fingerprint sensor of the electronic device, and wherein determining whether the first authorization data is valid includes determining whether the corresponding fingerprint is consistent with a registered fingerprint that enables authorization of a payment transaction.

11. The method according to any one of claims 1-2, wherein receiving first authorization data comprises receiving a payment password, and wherein determining whether the first authorization data is valid comprises determining whether the payment password is consistent with a registered password enabling authorization of a payment transaction.

12. The method according to any one of claims 1-2, wherein the first authorization data is different from the second authorization data.

13. The method according to any one of claims 1-2, wherein the second authorization data is requested from the user based on a determination that the current location of the electronic device is within a first predetermined geographical area.

14. The method according to any one of claims 1-2, wherein the second authorization data is requested from the user based on a determination that a payment amount of the payment transaction meets a predetermined criterion.

15. The method according to any one of claims 1-2, wherein a first entropy of the first authorization data is higher than a second entropy of the second authorization data.

16. A computer-readable storage medium storing one or more programs configured to be executed by one or more processors of an electronic device, the one or more programs comprising instructions for: while displaying a first user interface corresponding to the first application, detecting a request for initiating a payment transaction; in response to detecting the request to initiate the payment transaction, displaying a payment user interface corresponding to a second application different from the first application while maintaining at least a portion of the first user interface corresponding to the first application; While displaying the payment user interface, receiving first authorization data; After receiving the first authorization data, determining whether the first authorization data is valid; Based on determining that the first authorization data is valid, simultaneously displaying the payment user interface and a visual indication that the first authorization data is valid; receiving second authorization data; After receiving the first authorization data and the second authorization data, transmitting a transaction request corresponding to the payment transaction to one or more remote servers; receiving a response to the transaction request; as well as In response to receiving the reply to the transaction request: Based on the determination that the transaction request is successful, releasing the payment user interface; as well as Based on a determination that the transaction request has failed, maintaining display of the payment user interface and updating the payment user interface to display an indication of a reason why the transaction request has failed.

17. The computer-readable storage medium of claim 16, wherein the indication of the reason why the transaction request failed comprises: an indication that the transaction request failed due to a merchant associated with the payment transaction; or An indication that the transaction request failed due to a financial institution associated with the payment transaction.

18. The computer-readable storage medium of any one of claims 16-17, wherein displaying the payment user interface comprises displaying the payment user interface on only a portion of a first user interface.

19. The computer-readable storage medium of any one of claims 16-17, wherein transmitting the transaction request comprises transmitting the transaction request while displaying the payment user interface, and wherein receiving the reply to the transaction request comprises receiving the reply to the transaction request while displaying the payment user interface.

20. The computer-readable storage medium of any one of claims 16-17, wherein the one or more programs further comprise instructions for: Based on the determination that the transaction request is successful, storing the second authorization data; and Based on the determination that the transaction request fails, the storing of the second authorization data is abandoned.

21. The computer-readable storage medium of any one of claims 16-17, wherein the one or more programs further comprise instructions for: detecting a second request for initiating a second payment transaction; In response to detecting the second request for initiating the second payment transaction, displaying a second payment user interface; While displaying the second payment user interface, receiving third authorization data; After receiving the third authorization data, determining whether the third authorization data is valid; after receiving the third authorization data, transmitting to one or more remote servers a second transaction request corresponding to the second payment transaction, wherein the second transaction request is based at least in part on a stored representation of the second authorization data; as well as A second reply to the second transaction request is received.

22. The computer-readable storage medium of claim 21, wherein the one or more programs further comprise instructions for: In response to receiving the second reply to the second transaction request: Based on a determination that the second transaction request is successful, releasing the second payment user interface; and Based on a determination that the second transaction request has failed, display of the second payment user interface is maintained and the second payment user interface is updated to display a second indication of a second reason why the second transaction request has failed.

23. The computer-readable storage medium of any one of claims 16-17, wherein transmitting the transaction request corresponding to the payment transaction to the one or more remote servers comprises: The second authorization data is transmitted to a financial institution.

24. The computer-readable storage medium of any one of claims 16-17, wherein the one or more programs further comprise instructions for: According to the determination of the failure of the transaction request: While displaying the payment user interface, receiving third authorization data; After receiving the third authorization data, determining whether the third authorization data is valid; receiving fourth authorization data; After receiving the third authorization data and the fourth authorization data, transmitting a second transaction request corresponding to the payment transaction to one or more remote servers; as well as A second reply to the transaction request is received.

25. A computer-readable storage medium according to any one of claims 16-17, wherein receiving first authorization data includes detecting a corresponding fingerprint on a fingerprint sensor of the electronic device, and wherein determining whether the first authorization data is valid includes determining whether the corresponding fingerprint is consistent with a registered fingerprint that enables authorization of a payment transaction.

26. The computer-readable storage medium of any one of claims 16-17, wherein receiving first authorization data comprises receiving a payment password, and wherein determining whether the first authorization data is valid comprises determining whether the payment password is consistent with a registered password that enables authorization of a payment transaction.

27. The computer-readable storage medium of any one of claims 16-17, wherein the first authorization data is different from the second authorization data.

28. The computer-readable storage medium of any one of claims 16-17, wherein the second authorization data is requested from the user based on a determination that a current location of the electronic device is within a first predetermined geographic area.

29. The computer-readable storage medium of any one of claims 16-17, wherein the second authorization data is requested from the user based on a determination that a payment amount of the payment transaction satisfies a predetermined criterion.

30. The computer-readable storage medium of any one of claims 16-17, wherein a first entropy of the first authorization data is higher than a second entropy of the second authorization data.

31. An electronic device comprising: one or more processors; as well as A memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for: while displaying a first user interface corresponding to the first application, detecting a request for initiating a payment transaction; in response to detecting the request to initiate the payment transaction, displaying a payment user interface corresponding to a second application different from the first application while maintaining at least a portion of the first user interface corresponding to the first application; While displaying the payment user interface, receiving first authorization data; After receiving the first authorization data, determining whether the first authorization data is valid; Based on determining that the first authorization data is valid, simultaneously displaying the payment user interface and a visual indication that the first authorization data is valid; receiving second authorization data; After receiving the first authorization data and the second authorization data, transmitting a transaction request corresponding to the payment transaction to one or more remote servers; receiving a response to the transaction request; as well as In response to receiving the reply to the transaction request: Based on the determination that the transaction request is successful, releasing the payment user interface; as well as Based on a determination that the transaction request has failed, maintaining display of the payment user interface and updating the payment user interface to display an indication of a reason why the transaction request has failed.

32. The electronic device of claim 31 , wherein the indication of the reason why the transaction request failed comprises: an indication that the transaction request failed due to a merchant associated with the payment transaction; or An indication that the transaction request failed due to a financial institution associated with the payment transaction.

33. The electronic device of any one of claims 31-32, wherein displaying the payment user interface comprises displaying the payment user interface only on a portion of the first user interface.

34. An electronic device according to any one of claims 31-32, wherein transmitting the transaction request includes transmitting the transaction request while displaying the payment user interface, and wherein receiving the reply to the transaction request includes receiving the reply to the transaction request while displaying the payment user interface.

35. The electronic device according to any one of claims 31-32, wherein the one or more programs further comprise instructions for: Based on the determination that the transaction request is successful, storing the second authorization data; and Based on the determination that the transaction request fails, the storing of the second authorization data is abandoned.

36. The electronic device of any one of claims 31-32, wherein the one or more programs further comprise instructions for: detecting a second request for initiating a second payment transaction; In response to detecting the second request for initiating the second payment transaction, displaying a second payment user interface; While displaying the second payment user interface, receiving third authorization data; After receiving the third authorization data, determining whether the third authorization data is valid; after receiving the third authorization data, transmitting to one or more remote servers a second transaction request corresponding to the second payment transaction, wherein the second transaction request is based at least in part on a stored representation of the second authorization data; as well as A second reply to the second transaction request is received.

37. The electronic device of claim 36, wherein the one or more programs further comprise instructions for: In response to receiving the second reply to the second transaction request: Based on a determination that the second transaction request is successful, releasing the second payment user interface; and Based on a determination that the second transaction request has failed, display of the second payment user interface is maintained and the second payment user interface is updated to display a second indication of a second reason why the second transaction request has failed.

38. The electronic device of any one of claims 31-32, wherein transmitting the transaction request corresponding to the payment transaction to the one or more remote servers comprises: The second authorization data is transmitted to a financial institution.

39. The electronic device of any one of claims 31-32, wherein the one or more programs further comprise instructions for: According to the determination of the failure of the transaction request: While displaying the payment user interface, receiving third authorization data; After receiving the third authorization data, determining whether the third authorization data is valid; receiving fourth authorization data; After receiving the third authorization data and the fourth authorization data, transmitting a second transaction request corresponding to the payment transaction to one or more remote servers; as well as A second reply to the transaction request is received.

40. An electronic device according to any one of claims 31-32, wherein receiving first authorization data includes detecting a corresponding fingerprint on a fingerprint sensor of the electronic device, and wherein determining whether the first authorization data is valid includes determining whether the corresponding fingerprint is consistent with a registered fingerprint that enables authorization of a payment transaction.

41. An electronic device according to any one of claims 31-32, wherein receiving first authorization data includes receiving a payment password, and wherein determining whether the first authorization data is valid includes determining whether the payment password is consistent with a registered password that enables authorization of a payment transaction.

42. An electronic device according to any one of claims 31-32, wherein the first authorization data is different from the second authorization data.

43. An electronic device according to any of claims 31-32, wherein the second authorization data is requested from the user based on a determination that a current location of the electronic device is within a first predetermined geographical area.

44. An electronic device according to any one of claims 31-32, wherein the second authorization data is requested from the user based on a determination that a payment amount of the payment transaction meets predetermined criteria.

45. The electronic device according to any one of claims 31-32, wherein a first entropy of the first authorization data is higher than a second entropy of the second authorization data.

46. ​​An electronic device comprising: means for detecting a request to initiate a payment transaction while displaying a first user interface corresponding to a first application; means for displaying a payment user interface corresponding to a second application different from the first application while maintaining at least a portion of the first user interface corresponding to the first application in response to detecting the request to initiate the payment transaction; means for receiving first authorization data while displaying the payment user interface; means for determining whether the first authorization data is valid after receiving the first authorization data; means for, based on determining that the first authorization data is valid, simultaneously displaying the payment user interface and a visual indication that the first authorization data is valid; means for receiving second authorization data; means for transmitting, after receiving the first authorization data and the second authorization data, to one or more remote servers a transaction request corresponding to the payment transaction; means for receiving a response to said transaction request; as well as means for, in response to receiving the reply to the transaction request, performing: Based on the determination that the transaction request is successful, releasing the payment user interface; and Based on a determination that the transaction request has failed, maintaining display of the payment user interface and updating the payment user interface to display an indication of a reason why the transaction request has failed.

Images