User interface for managing secure operations

The method and interface streamline security operations by communicating with external devices to perform transfers and secure transactions efficiently, reducing user distraction and extending battery life.

CN119095041APending Publication Date: 2024-12-06APPLE INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202411112732.X
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2020-10-21
Filing Date
2021-06-17
Publication Date
2024-12-06

AI Technical Summary

Technical Problem

Existing techniques for managing security operations on electronic devices are cumbersome and inefficient, particularly when used in vehicles, leading to user distraction and increased cognitive burden.

Method used

A method and interface that allows for faster and more reliable security operations by communicating with an external automobile head unit and an external receiving device, enabling transfer operations without requiring additional user input, and providing secure transactions based on authorization criteria.

Benefits of technology

Reduces user distraction and cognitive burden, enhances efficiency, and extends battery life by minimizing redundant user inputs.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119095041A_ABST
    Figure CN119095041A_ABST
Patent Text Reader

Abstract

The invention relates to a user interface for managing secure operations. The present disclosure generally relates to methods for performing secure operations (e.g., secure operations) and methods for providing options (e.g., selectable options) to initiate secure operations (e.g., secure operations), such methods using computer systems and external devices.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] Division Statement

[0002] This application is a divisional application of the invention patent application with PCT international application number PCT / US2021 / 037949, international application date June 17, 2021, application number 202180041928.2 entering the Chinese national phase, and invention name “User Interface for Managing Security Operations”.

[0003] CROSS-REFERENCE TO RELATED APPLICATIONS

[0004] This application claims priority to U.S. Patent Application No. 17 / 076,694, entitled “USER INTERFACES FOR MANAGING SECURE OPERATIONS,” filed on October 21, 2020, and U.S. Provisional Patent Application No. 63 / 041,969, entitled “USER INTERFACES FOR MANAGING SECURE OPERATIONS,” filed on June 21, 2020. The contents of each of these patent applications are hereby incorporated by reference in their entirety. Technical Field

[0005] The present disclosure relates generally to computer user interfaces, and more particularly to techniques for managing security operations via input received at an external device. Background Art

[0006] Users usually use personal electronic devices to perform operations. Such technologies typically require users to provide various inputs and authorizations to perform these operations. Summary of the invention

[0007] However, some techniques for managing safety operations using electronic devices are often cumbersome and inefficient. For example, some existing techniques require the user to provide various inputs and authorizations to perform these operations on a personal device (e.g., a cellular phone), which may be inconvenient or unsafe for the user to provide while the user is operating a vehicle.

[0008] Thus, the present technology provides electronic devices with faster, more reliable, and more efficient methods and interfaces for managing safety operations using electronic devices. Such methods and interfaces optionally supplement or replace other methods for managing safety operations. Such methods and interfaces are more reliable, for example, do not distract users while they are operating a vehicle. Such methods and interfaces reduce the cognitive burden on users and produce more efficient human-machine interfaces.

[0009] According to some embodiments, a method is described. The method is performed at a computer system that communicates with an external automobile head unit including one or more input components and communicates with an external receiving device. The method includes: receiving first data corresponding to an input received at the one or more input components of the external automobile head unit from the external automobile head unit, the first data corresponding to a request to use an application associated with a first account on the computer system to perform a first transfer operation from the first account to a second account; and in response to receiving the first data, initiating a process of using the application on the computer system to perform the first transfer operation, wherein performing the first transfer operation includes transmitting second data including information identifying the first account to the external receiving device.

[0010] According to some embodiments, a non-transitory computer-readable storage medium is described. The non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system, the computer system communicating with an external automobile head unit including one or more input components, and communicating with an external receiving device. The one or more programs include instructions for the following operations: receiving first data corresponding to an input received at the one or more input components of the external automobile head unit from the external automobile head unit, the first data corresponding to a request to perform a first transfer operation from the first account to a second account using an application associated with a first account on the computer system; and in response to receiving the first data, initiating a process of performing the first transfer operation using the application on the computer system, wherein performing the first transfer operation includes transmitting second data including information identifying the first account to the external receiving device.

[0011] According to some embodiments, a transient computer-readable storage medium is described. The transient computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system, the computer system communicating with an external automobile head unit including one or more input components, and communicating with an external receiving device. The one or more programs include instructions for the following operations: receiving first data corresponding to an input received at the one or more input components of the external automobile head unit from the external automobile head unit, the first data corresponding to a request to perform a first transfer operation from the first account to a second account using an application associated with a first account on the computer system; and in response to receiving the first data, initiating a process of performing the first transfer operation using the application on the computer system, wherein performing the first transfer operation includes transmitting second data including information identifying the first account to the external receiving device.

[0012] According to some embodiments, a computer system is described. The computer system includes: one or more processors, wherein the computer system communicates with an external automobile head unit including one or more input components, and wherein the computer system communicates with an external receiving device; and a memory storing one or more programs configured to be executed by the one or more processors. The one or more programs include instructions for the following operations: receiving first data corresponding to an input received at the one or more input components of the external automobile head unit from the external automobile head unit, the first data corresponding to a request to perform a first transfer operation from the first account to a second account using an application associated with a first account on the computer system; and in response to receiving the first data, initiating a process of performing the first transfer operation using the application on the computer system, wherein performing the first transfer operation includes transmitting second data including information identifying the first account to the external receiving device.

[0013] According to some embodiments, a computer system is described, wherein the computer system communicates with an external automobile head unit including one or more input components, and wherein the computer system communicates with an external receiving device. The computer system includes: a receiving device for receiving first data corresponding to input received at the one or more input components of the external automobile head unit from the external automobile head unit, the first data corresponding to a request to use an application on the computer system associated with a first account to perform a first transfer operation from the first account to a second account; and an initiating device for initiating a process of using the application on the computer system to perform the first transfer operation in response to receiving the first data, wherein performing the first transfer operation includes transmitting second data including information identifying the first account to the external receiving device.

[0014] According to some embodiments, a method is described. The method is performed at a computer system. The computer system includes: when the computer system is connected to an external input device, receiving a first request from the external input device to interact with a first portion of a user interface associated with a secure transaction, the secure transaction will require a separate authorization from the user if authorized from the computer system. The computer system also includes, in response to receiving the first request: based on determining that the external input device meets a set of authorization criteria, providing an option to initiate a secure transaction via the external input device without requiring the separate authorization from the user; and based on determining that the external input device does not meet the set of authorization criteria, abandoning the option of providing the secure transaction without requiring the separate authorization from the user.

[0015] According to some embodiments, a non-transitory computer-readable storage medium is described. The non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system. The one or more programs include instructions for the following operations: when the computer system is connected to an external input device, a first request for interacting with a first portion of a user interface associated with a secure transaction is received from the external input device, and the secure transaction will require a separate authorization from the user when authorized from the computer system. The one or more programs also include instructions for the following operations: in response to receiving the first request: based on determining that the external input device meets a set of authorization criteria, an option of initiating a secure transaction without the need for the separate authorization from the user is provided via the external input device; and based on determining that the external input device does not meet the set of authorization criteria, the option of initiating a secure transaction without the need for the separate authorization from the user is abandoned.

[0016] According to some embodiments, a transient computer-readable storage medium is described. The transient computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system. The one or more programs include instructions for the following operations: when the computer system is connected to an external input device, a first request for interacting with a first portion of a user interface associated with a secure transaction is received from the external input device, and the secure transaction will require a separate authorization from the user when authorized from the computer system. The one or more programs also include instructions for the following operations: in response to receiving the first request: based on determining that the external input device meets a set of authorization criteria, an option is provided via the external input device to initiate a secure transaction without the need for the separate authorization from the user; and based on determining that the external input device does not meet the set of authorization criteria, the option of initiating a secure transaction without the need for the separate authorization from the user is abandoned.

[0017] According to some embodiments, a computer system is described. The computer system includes: one or more processors; and a memory storing one or more programs configured to be executed by the one or more processors. The one or more programs include instructions for the following operations: when the computer system is connected to an external input device, a first request for interacting with a first portion of a user interface associated with a secure transaction is received from the external input device, and the secure transaction will require a separate authorization from the user if authorized from the computer system. The one or more programs also include instructions for the following operations: in response to receiving the first request: based on determining that the external input device meets a set of authorization criteria, an option is provided via the external input device to initiate a secure transaction without the need for the separate authorization from the user; and based on determining that the external input device does not meet the set of authorization criteria, the option of initiating a secure transaction without the need for the separate authorization from the user is abandoned.

[0018] According to some embodiments, a computer system is described. The computer system includes: receiving means for receiving, when the computer system is connected to an external input device, a first request to interact with a first portion of a user interface associated with a secure transaction, the secure transaction requiring separate authorization from a user if authorized from the computer system; and means for the following operations, the means being responsive to receiving the first request: based on determining that the external input device meets a set of authorization criteria, providing an option to initiate a secure transaction via the external input device without requiring the separate authorization from the user; and based on determining that the external input device does not meet the set of authorization criteria, forgoing providing the option to initiate a secure transaction without requiring the separate authorization from the user.

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

[0020] Thus, a faster, more efficient method and interface for managing security operations is provided for devices, thereby increasing the effectiveness, efficiency, and user satisfaction of such devices. Such methods and interfaces may supplement or replace other methods for managing security operations. BRIEF DESCRIPTION OF THE DRAWINGS

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

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

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

[0024] Figure 2 A portable multifunction device with a touch screen according to some embodiments is shown.

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

[0026] Figure 4A An exemplary user interface for a menu of applications on a portable multifunction device is shown according to some embodiments.

[0027] Figure 4B An exemplary user interface is shown for a multifunction device having a touch-sensitive surface that is separate from the display according to some embodiments.

[0028] Figure 5A A personal electronic device according to some embodiments is shown.

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

[0030] 6A to 6F An exemplary user interface for performing security operations according to some embodiments is shown.

[0031] FIG. 7A to FIG. 7M An exemplary user interface for performing security operations according to some embodiments is shown.

[0032] Figure 8 is a flow chart illustrating a method for performing security operations according to some embodiments.

[0033] Fig. 9 is a flow chart illustrating a method for providing an option to initiate a security operation according to some embodiments. DETAILED DESCRIPTION

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

[0035] Electronic devices need to provide efficient methods and interfaces for managing safety operations. For example, there is a need to provide techniques that improve robustness when used to manage operations that may be performed while operating a vehicle. Such methods and interfaces are more robust, for example, they do not distract the user while the user is operating the vehicle. Such techniques can reduce the cognitive burden on the user who needs to perform the operation, thereby improving productivity. In addition, such techniques can reduce processor power and battery power that would otherwise be wasted on redundant user input.

[0036] under Figure 1A to Figure 1B , Figure 2 , Figure 3 , FIG. 4A to FIG. 4B and FIG. 5A to FIG. 5B A description of an example device for performing techniques for managing security operations is provided.

[0037] 6A to 6F An exemplary user interface for performing security operations according to some embodiments is shown. FIG. 7A to FIG. 7M An exemplary user interface for performing security operations according to some embodiments is shown. Figure 8 is a flow chart illustrating a method for performing security operations according to some embodiments. Fig. 9 is a flow chart illustrating a method for providing an option to initiate a security operation according to some embodiments. 6A to 6F and FIG. 7A to FIG. 7M The user interface in is used to illustrate the processes described below, which include Figure 8 and Fig. 9 process.

[0038] The processes described below enhance the operability of the device and make the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device) through various techniques, including by providing improved visual feedback to the user, reducing the number of inputs required to perform an operation, providing additional control options without cluttering the user interface with additional display controls, performing an operation without further user input when a set of conditions have been met, and / or additional techniques. These techniques also reduce power usage and extend the battery life of the device by enabling the user to use the device more quickly and more efficiently.

[0039] In addition, in the method described herein where one or more steps depend on one or more conditions being met, it should be understood that the method can be repeated in multiple repetitions so that in the process of repetition, all conditions for determining the steps in the method have been met in different repetitions of the method. For example, if the method needs to perform the first step (if the condition is met), and perform the second step (if the condition is not met), then the ordinary technician will know that the steps stated are repeated until both the condition is met and the condition is not met (in no particular order). Therefore, the method described as having one or more steps depending on one or more conditions being met can be rewritten as a method of repeating until each condition described in the method is met. However, this does not require the system or computer-readable medium to declare that the system or computer-readable medium contains instructions for performing a contingent operation based on the satisfaction of the corresponding one or more conditions, and is therefore able to determine whether the possible situation has been met without explicitly repeating the steps of the method until all conditions for determining the steps in the method have been met. It will also be understood by ordinary technicians in the art that, similar to the method with the contingent step, the system or computer-readable storage medium can repeat the steps of the method as many times as needed to ensure that all the contingent steps have been performed.

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

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

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

[0043] Embodiments of electronic devices, user interfaces for such devices, and associated processes for using such devices are described herein. In some embodiments, the device is a portable communication device, such as a mobile phone, that also includes other functions, such as a PDA and / or a music player function. Exemplary embodiments of portable multifunction devices include, but are not limited to, the Apple iPod from Apple Inc. (Cupertino, California). Devices, iPod Equipment, and Device. Optionally use other portable electronic devices, such as laptops or tablet computers with touch-sensitive surfaces (e.g., touch screen displays and / or touch pads). 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). In some embodiments, the electronic device is a computer system that communicates with the display generation component (e.g., via wireless communication, via wired communication). The display generation component is configured to provide visual output, such as display via a CRT display, display via an LED display, or display via image projection. In some embodiments, the display generation component is integrated with the computer system. In some embodiments, the display generation component is separated from the computer system. As used herein, "display" content includes transmitting data (e.g., image data or video data) to an integrated or external display generation component via a wired or wireless connection to visually generate content to display content (e.g., video data rendered or decoded by display controller 156).

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

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

[0046] Various applications executed on the device optionally use at least one common physical user interface device, such as a touch-sensitive surface. One or more functions of the touch-sensitive surface and corresponding information displayed on the device are optionally adjusted and / or varied for different applications, and / or adjusted and / or varied within the respective applications. In this way, the common physical architecture of the device (such as a touch-sensitive surface) optionally supports a variety of applications with a user interface that is intuitive and clear to the user.

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

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

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

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

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

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

[0053] RF (radio frequency) circuit 108 receives and sends RF signals, also referred to as electromagnetic signals. RF circuit 108 converts electrical signals into / converts electromagnetic signals into electrical signals, and communicates with communication networks and other communication devices via electromagnetic signals. RF circuit 108 optionally includes well-known circuits for performing these functions, including but not limited to antenna systems, RF transceivers, one or more amplifiers, tuners, one or more oscillators, digital signal processors, codec chipsets, user identity modules (SIM) cards, memories, and the like. RF circuit 108 optionally communicates with networks and other devices via wireless communications, such as the Internet (also referred to as the World Wide Web (WWW)), intranets, and / or wireless networks (such as cellular telephone networks, wireless local area networks (LANs), and / or metropolitan area networks (MANs)). RF circuit 108 optionally includes well-known circuits for detecting near field communications (NFC) fields, such as through short-range communications radio components. Wireless communication optionally uses any of a variety of communication standards, protocols and technologies, including, but not limited to, Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), High Speed ​​Downlink Packet Access (HSDPA), High Speed ​​Uplink Packet Access (HSUPA), Evolution, Data-Only (EV-DO), HSPA, HSPA+, Dual Cell HSPA (DC-HSPDA), Long Term Evolution (LTE), Near Field Communication (NFC), Wideband Code Division Multiple Access (W-CDMA), Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Bluetooth, Bluetooth Low Energy (BTLE), Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11d), IEEE 802.11e, IEEE 802.11f, IEEE 802.11g, IEEE 802.11g). 802.11n and / or IEEE 802.11ac), Voice over Internet Protocol (VoIP), Wi-MAX, email protocols (e.g., Internet Message Access Protocol (IMAP) and / or Post Office Protocol (POP)), instant messaging (e.g., Extensible Messaging and Presence Protocol (XMPP), Session Initiation Protocol for Instant Messaging and Presence Utilizing Extensions (SIMPLE), Instant Messaging and Presence Service (IMPS)), and / or Short Message Service (SMS), or any other suitable communication protocol including communication protocols that have not been developed as of the filing date of this document.

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

[0055] The I / O subsystem 106 couples input / output peripherals on the device 100, such as a touch screen 112 and other input control devices 116, to a peripheral device interface 118. The I / O subsystem 106 optionally includes a display controller 156, an optical sensor controller 158, a depth camera controller 169, an intensity sensor controller 159, a tactile feedback controller 161, and one or more input controllers 160 for other input or control devices. The one or more input controllers 160 receive / send electrical signals from other input control devices 116. The other input control devices 116 optionally include physical buttons (e.g., push buttons, rocker buttons, etc.), dials, slide switches, joysticks, click wheels, etc. In some embodiments, the input controller 160 is optionally coupled to any of the following (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 increase / decrease 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 2206 in). In some embodiments, the electronic device is a computer system that communicates with one or more input devices (e.g., via wireless communication, via wired communication). In some embodiments, the one or more input devices include a touch-sensitive surface (e.g., a touchpad as part of a touch-sensitive display). In some embodiments, the one or more input devices include one or more camera sensors (e.g., one or more optical sensors 164 and / or one or more depth camera sensors 175), such as for tracking a user's gestures (e.g., hand gestures) as input. In some embodiments, the one or more input devices are integrated with the computer system. In some embodiments, the one or more input devices are separate from the computer system.

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

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

[0058] The touch screen 112 has a touch-sensitive surface, sensor, or sensor group that accepts input from a user based on tactile and / or haptic contact. The touch screen 112 and display controller 156 (together with any associated modules and / or instruction sets in memory 102) detect contact on the touch screen 112 (and any movement or interruption of the contact) 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.

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

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

[0061] In some embodiments, the touch-sensitive display of the touch screen 112 is as described in the following patent applications: (1) U.S. patent application No. 11 / 381,313, filed on May 2, 2006, entitled “Multipoint Touch Surface Controller”; (2) U.S. patent application No. 10 / 840,862, filed on May 6, 2004, entitled “Multipoint Touchscreen”; (3) U.S. patent application No. 10 / 903,964, filed on July 30, 2004, entitled “Gestures For Touch Sensitive Input Devices”; (4) U.S. patent application No. 11 / 048,264, filed on January 31, 2005, entitled “Gestures For Touch Sensitive Input Devices”; (5) U.S. patent application No. 11 / 050,694, filed on 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.

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

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

[0064] The device 100 also includes a power system 162 for powering the various components. The power system 162 optionally includes a power management system, one or more power sources (e.g., batteries, alternating current (AC)), a recharging system, a power fault detection circuit, a power converter or inverter, a power status indicator (e.g., a light emitting diode (LED)), and any other components associated with the generation, management, and distribution of power in a portable device.

[0065] Device 100 optionally also includes one or more optical sensors 164 . Figure 1AAn optical sensor coupled to an optical sensor controller 158 in the I / O subsystem 106 is shown. The optical sensor 164 optionally includes a charge coupled device (CCD) or a complementary metal oxide semiconductor (CMOS) phototransistor. The optical sensor 164 receives light projected through one or more lenses from the environment and converts the light into data representing an image. In conjunction with the imaging module 143 (also called a camera module), the optical sensor 164 optionally captures a static image or video. In some embodiments, the optical sensor is located on the rear of the device 100, opposite to the touch screen display 112 on the front of the device, so that the touch screen display can be used as a viewfinder for static images and / or video image acquisition. In some embodiments, the optical sensor is located on the front of the device so that the user's image is optionally obtained for video conferencing while the user views other video conference participants on the touch screen display. In some embodiments, the position of 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 is used with the touch screen display for both video conferencing and static image and / or video image acquisition.

[0066] Device 100 optionally also includes one or more depth camera sensors 175 . Figure 1A A depth camera sensor coupled to a depth camera controller 169 in the I / O subsystem 106 is shown. The depth camera sensor 175 receives data from the environment to create a three-dimensional model of an object (e.g., a face) within the scene from a viewpoint (e.g., a depth camera sensor). In some embodiments, in conjunction with the imaging module 143 (also referred to as a camera module), the depth camera sensor 175 is optionally used to determine a depth map of different portions of an image captured by the imaging module 143. In some embodiments, the depth camera sensor is located at the front of the device 100, so that an image of the user with depth information is optionally obtained for video conferencing while the user is viewing other video conference participants on the touch screen display, and a selfie with depth map data is captured. In some embodiments, the depth camera sensor 175 is located at the rear of the device, or at both the rear and front of the device 100. In some embodiments, the position of the depth camera sensor 175 can be changed by the user (e.g., by rotating the lens and sensor in the device housing) so that the depth camera sensor 175 is used with the touch screen display for both video conferencing and still image and / or video image acquisition.

[0067] Device 100 optionally also includes one or more contact intensity sensors 165 . Figure 1AA contact force sensor is shown coupled to a force sensor controller 159 in the I / O subsystem 106. Contact force sensor 165 optionally includes one or more piezoresistive strain gauges, capacitive force sensors, electrical force sensors, piezoelectric force sensors, optical force sensors, capacitive touch-sensitive surfaces, or other force sensors (e.g., sensors for measuring the force (or pressure) of contact on a touch-sensitive surface). Contact force sensor 165 receives contact force information (e.g., pressure information or a surrogate for pressure information) from the environment. In some embodiments, at least one contact force sensor is juxtaposed or adjacent to a touch-sensitive surface (e.g., touch-sensitive display system 112). In some embodiments, at least one contact force sensor is located on the back of device 100, opposite to touch screen display 112 located on the front of device 100.

[0068] Device 100 optionally also includes 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 is optionally coupled to the input controller 160 in the I / O subsystem 106. The proximity sensor 166 is optionally implemented as described in the following U.S. patent applications: No. 11 / 241,839, entitled "Proximity Detector In Handheld Device"; No. 11 / 240,788, entitled "Proximity Detector In Handheld Device"; No. 11 / 620,702, entitled "Using Ambient Light Sensor To Augment Proximity Sensor Output"; No. 11 / 586,862, entitled "Automated Response To And Sensing Of User Activity In Portable Devices"; and No. 11 / 638,251, entitled "Methods And Systems For Automatic Configuration Of Peripherals", which are hereby incorporated by reference in their entirety. In some embodiments, when the multifunction device is placed near the user's ear (e.g., when the user is on a phone call), the proximity sensor turns off and disables the touch screen 112.

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

[0070] Device 100 optionally also includes one or more accelerometers 168 . Figure 1A An accelerometer 168 is shown coupled to the peripheral device interface 118. Alternatively, the accelerometer 168 is optionally coupled to the input controller 160 in the I / O subsystem 106. The accelerometer 168 is optionally implemented as described in the following U.S. Patent Publication 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 incorporated herein by reference in their entirety. In some embodiments, information is displayed in a portrait view or a landscape view on the touch screen display based on analysis of data received from one or more accelerometers. The device 100 optionally includes a magnetometer and a GPS (or GLONASS or other global navigation system) receiver in addition to the accelerometer 168 for obtaining information about the position and orientation (e.g., portrait or landscape) of the device 100.

[0071] In some embodiments, the software components stored in memory 102 include an operating system 126, a communication module (or instruction set) 128, a contact / motion module (or instruction set) 130, a graphics module (or instruction set) 132, a text input module (or instruction set) 134, a global positioning system (GPS) module (or instruction set) 135, and an application (or instruction set) 136. In addition, in some embodiments, memory 102 ( Figure 1A ) or 370( Figure 3 ) storage device / global internal state 157, such as Figure 1A and Figure 3 . The device / global internal state 157 includes one or more of the following: an active application state, which indicates which applications (if any) are currently active; a display state, which indicates what applications, views, or other information occupy various areas of the touch screen display 112; a sensor state, including information obtained from the device's various sensors and input control devices 116; and position information about the device's position and / or posture.

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

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

[0074] The contact / motion module 130 optionally detects contact with the touch screen 112 (in conjunction with the display controller 156) and other touch-sensitive devices (e.g., a touchpad or physical click wheel). The contact / motion module 130 includes various software components for performing various operations related to contact detection, such as determining whether contact has occurred (e.g., detecting a finger press event), determining the contact strength (e.g., the force or pressure of the contact, or a substitute for the force or pressure of the contact), determining whether there is movement of the contact and tracking the movement on the touch-sensitive surface (e.g., detecting one or more finger drag events), and determining whether the contact has stopped (e.g., detecting a finger lift event or contact disconnection). The contact / motion module 130 receives contact data from the touch-sensitive surface. Determining the movement of the contact point optionally includes determining the rate (magnitude), velocity (magnitude and direction), and / or acceleration (change in magnitude and / or direction) of the contact point, the movement of the contact point being represented by a series of contact data. These operations are optionally applied to a single point of contact (e.g., a single finger contact) or multiple points of simultaneous contact (e.g., "multi-touch" / multiple finger contacts). In some embodiments, the contact / motion module 130 and display controller 156 detect contact on the touch pad.

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

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

[0077] The graphics module 132 includes various known software components for rendering and displaying graphics on the touch screen 112 or other display, including components for changing the visual impact (e.g., brightness, transparency, saturation, contrast, or other visual 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.

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

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

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

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

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

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

[0084] Telephone module 138;

[0085] Video conferencing module 139;

[0086] Email client module 140;

[0087] Instant messaging (IM) module 141;

[0088] Fitness support module 142;

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

[0090] Image management module 144;

[0091] Video player module;

[0092] Music player module;

[0093] Browser module 147;

[0094] Calendar module 148;

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

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

[0097] Search module 151;

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

[0099] Note module 153;

[0100] Map module 154; and / or

[0101] Online video module 155.

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

[0103] In conjunction with the touch screen 112, display controller 156, touch / motion module 130, graphics module 132, and text input module 134, the contact module 137 is optionally used to manage an address book or contact list (e.g., stored in the application internal state 192 of the contact module 137 in memory 102 or memory 370), including: adding one or more names to the address book; deleting names from the address book; associating phone numbers, email addresses, physical addresses, or other information with names; associating images with names; categorizing and classifying names; providing phone numbers or email addresses to initiate and / or facilitate communications via telephone 138, video conferencing module 139, email 140, or IM 141; and the like.

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

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

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

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

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

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

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

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

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

[0113] In conjunction with RF circuit 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 mini-application that is optionally downloaded and used by a user (e.g., weather widget 149-1, stock market widget 149-2, calculator widget 149-3, alarm widget 149-4, and dictionary widget 149-5) or a mini-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).

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

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

[0116] In conjunction with touch screen 112, display controller 156, contact / motion module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, and browser module 147, video and music player module 152 includes executable instructions that allow a user to download and play back recorded music and other sound files stored in one or more file formats, such as MP3 or AAC files, and executable instructions for displaying, presenting, or otherwise playing back video (e.g., on touch screen 112 or on an external display connected via external port 124). In some embodiments, device 100 optionally includes the functionality of an MP3 player, such as an iPod (trademark of Apple Inc.).

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

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

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

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

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

[0122] A predefined set of functions that are performed exclusively through the touch screen and / or touchpad optionally includes navigation between user interfaces. In some embodiments, the touchpad, when touched by the user, navigates the device 100 to a main menu, a home menu, or a root menu from any user interface displayed on the device 100. In such embodiments, a "menu button" is implemented using the touchpad. In some other embodiments, the menu button is a physical push button or other physical input control device, rather than a touchpad.

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

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

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

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

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

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

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

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

[0131] Hit view determination module 172 receives information related to sub-events of touch-based gestures. When an application has multiple views organized in a hierarchy, hit view determination module 172 identifies the hit view as the lowest view in the hierarchy where the sub-events should be processed. In most cases, the hit view is the lowest level view in which the initiating sub-event (e.g., the first sub-event in a sequence of sub-events that form an event or potential event) occurs. Once a hit view is identified by hit view determination module 172, the hit view typically receives all sub-events related to the same touch or input source for which it was identified as the hit view.

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

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

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

[0135] 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 in event recognizers 180 are part of an independent module, which is a higher-level object such as a user interface toolkit or application 136-1 from which methods and other properties are inherited. In some embodiments, the corresponding event handler 190 includes one or more of the following: data updater 176, object updater 177, GUI updater 178, and / or event data 179 received from event classifier 170. Event handler 190 optionally utilizes or calls data updater 176, object updater 177, or GUI updater 178 to update application internal state 192. Alternatively, one or more of the application views in application view 191 include one or more corresponding event handlers 190. In addition, in some embodiments, one or more of data updater 176, object updater 177, and GUI updater 178 are included in the corresponding application view 191.

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

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

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

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

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

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

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

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

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

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

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

[0147] It should be understood that the foregoing discussion of event processing for user touches on a touch-sensitive display also applies to other forms of user input utilizing input devices to operate portable multifunction device 100, not all of which are initiated on a touch screen. For example, mouse movement and mouse button presses, optionally in conjunction with single or multiple keyboard presses or holddowns; contact movement on a touch pad, such as taps, drags, scrolls, etc.; stylus input; movement of the device; verbal commands; detected eye movement; biometric input; and / or any combination thereof, are optionally used as input corresponding to sub-events defining an event to be recognized.

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

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

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

[0151] Figure 3300 is a block diagram of an exemplary multifunction device with a display and a touch-sensitive surface according to some embodiments. The device 300 does not have to be portable. In some embodiments, the device 300 is a laptop, a desktop computer, a tablet computer, a multimedia player device, a navigation device, an educational device (such as a children's learning toy), a game system, or a control device (e.g., a home controller or an industrial controller). The device 300 typically includes one or more processing units (CPUs) 310, one or more network or other communication interfaces 360, a memory 370, and one or more communication buses 320 for interconnecting these components. The communication bus 320 optionally includes circuits (sometimes referred to as a chipset) that interconnect system components and control communications between system components. The device 300 includes an input / output (I / O) interface 330 with a display 340, which is typically a touch screen display. The I / O interface 330 also optionally includes a keyboard and / or a mouse (or other pointing device) 350 and a touchpad 355, a tactile output generator 357 for generating tactile output on the device 300 (e.g., similar to the above reference Figure 1A The tactile output generator 167 described above), sensor 359 (e.g., optical sensor, acceleration sensor, proximity sensor, touch sensor and / or contact intensity sensor (similar to the above reference Figure 1A The memory 370 may include a high-speed random access memory, such as DRAM, SRAM, DDR RAM, or other random access solid-state memory devices; and may optionally include a non-volatile memory, such as one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid-state storage devices. The memory 370 may optionally include one or more storage devices located away from the CPU 310. In some embodiments, the memory 370 stores data related to the portable multifunction device 100 ( Figure 1A ) or a subset thereof. In addition, memory 370 optionally stores additional programs, modules, and data structures not present in memory 102 of portable multifunction device 100. For example, memory 370 of device 300 optionally stores a drawing module 380, a presentation module 382, ​​a word processing module 384, a website creation module 386, a disk editing module 388, and / or a spreadsheet module 390, while portable multifunction device 100 ( Figure 1A )'s memory 102 optionally does not store these modules.

[0152] Figure 3Each element in the above-mentioned elements in is optionally stored in one or more memory devices of the previously mentioned memory device. Each module in the above-mentioned modules corresponds to an instruction set for performing the above-mentioned functions. The above-mentioned modules or computer programs (for example, instruction sets or including instructions) do not have to be implemented with separate software programs (such as computer programs (for example, including instructions)), processes or modules, and therefore the various subsets of these modules are optionally combined or otherwise rearranged in various embodiments. In some embodiments, memory 370 optionally stores a subset of the above-mentioned modules and data structures. In addition, memory 370 optionally stores additional modules and data structures not described above.

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

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

[0155] Signal strength indicators 402 for wireless communications such as cellular signals and Wi-Fi signals;

[0156] Time 404;

[0157] Bluetooth indicator 405;

[0158] Battery status indicator 406;

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

[0160] o An icon 416 of the phone module 138 labeled "Phone," which optionally includes an indicator 414 of the number of missed calls or voicemails;

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

[0162] o An icon 420 labeled "Browser" of the browser module 147; and

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

[0164] Icons of other applications, such as:

[0165] o Icon 424 labeled "Message" of IM module 141;

[0166] o An icon 426 labeled “Calendar” of the calendar module 148;

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

[0168] o An icon 430 labeled “Camera” of the camera module 143;

[0169] o An icon 432 labeled “Online Video” of the online video module 155;

[0170] ○ Icon 434 labeled “Stock Market” of the Stock Market Widget 149 - 2 ;

[0171] o An icon 436 labeled “Map” of the map module 154;

[0172] ○ Icon 438 labeled “Weather” of the weather widget 149 - 1 ;

[0173] ○ Icon 440 labeled as “Clock” of the alarm clock widget 149 - 4 ;

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

[0175] o An icon 444 labeled "Notes" of the notes module 153; and

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

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

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

[0179] Although some of the examples below are given with reference to input on a touch screen display 112 (where a touch-sensitive surface and a display are combined), in some embodiments, the device detects input on a touch-sensitive surface that is separate from the display, such as Figure 4B In some embodiments, the touch-sensitive surface (e.g., Figure 4B 451) has a main axis (e.g., Figure 4B 453) corresponding to the principal axis (for example, Figure 4B According to these embodiments, the device detects a position corresponding to a corresponding position on the display (e.g., Figure 4B 460 corresponds to 468 and 462 corresponds to 470) in contact with touch-sensitive surface 451 (e.g., Figure 4B Thus, when the touch-sensitive surface (e.g., Figure 4B 451) and a display of a multi-function device (e.g., Figure 4B When the user input detected by the device on the touch-sensitive surface (e.g., contacts 460 and 462 and their movement) is separated, the device is used to manipulate the user interface on the display. It should be understood that similar methods are optionally used for other user interfaces described herein.

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

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

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

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

[0184] 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 portion 514 to one or more computer processors 516 and a memory 518. I / O portion 514 may be connected to a touch-sensitive display 504, which may have a touch-sensitive component 522 and optionally an intensity sensor 524 (e.g., a contact intensity sensor). In addition, I / O portion 514 may be connected to a communication unit 530 for receiving application and operating system data using Wi-Fi, Bluetooth, near field communication (NFC), cellular and / or other wireless communication technologies. Device 500 may include input mechanisms 506 and / or 508. For example, input mechanism 506 is optionally a rotatable input device or a depressible input device and a rotatable input device. In some examples, input mechanism 508 is optionally a button.

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

[0186] The memory 518 of the personal electronic device 500 may include one or more non-transitory computer-readable storage media for storing computer-executable instructions that, when executed by one or more computer processors 516, may cause the computer processors to perform the techniques described below, including processes 800 and 900 ( Figure 8 and Fig. 9). Computer-readable storage media can be any medium that can tangibly contain or store computer-executable instructions for use by or in conjunction with instruction execution systems, devices, and apparatuses. In some examples, the storage medium is a transient computer-readable storage medium. In some examples, the storage medium is a non-transitory computer-readable storage medium. Non-transitory computer-readable storage media may include, but are not limited to, magnetic storage devices, optical storage devices, and / or semiconductor storage devices. Examples of such storage devices include magnetic disks, optical disks based on CD, DVD, or Blu-ray technology, and persistent solid-state memories such as flash memory, solid-state drives, and the like. Personal electronic device 500 is not limited to Figure 5B components and configurations, but may include other components or additional components in a variety of configurations.

[0187] As used herein, the term "indicative representation" refers to an optional feature of the apparatus 100, 300, and / or 500 ( Figure 1A , Figure 3 and FIG. 5A to FIG. 5B ) is a user-interactive graphical user interface object displayed on a display screen of a computer. For example, an image (e.g., an icon), a button, and text (e.g., a hyperlink) optionally each constitute an affordance.

[0188] As used herein, the term "focus selector" refers to an input element used to indicate the current portion of a user interface with which a user is interacting. In some implementations that include a cursor or other position marker, the cursor acts as a "focus selector" such that when the cursor is over a particular user interface element (e.g., a button, window, slider, or other user interface element), a focus selector is displayed on a touch-sensitive surface (e.g., Figure 3 Touchpad 355 or Figure 4B In the event that an input (e.g., a press input) is detected on the touch-sensitive surface 451 in the display, the particular user interface element is adjusted according to the detected input. In the case that a touch-screen display (e.g., Figure 1A A touch-sensitive display system 112 or Figure 4AIn some implementations of the touch screen 112 in FIG. 1 , a contact detected on the touch screen acts as a “focus selector” such that when an input (e.g., a press input by the contact) is detected at the location of a particular user interface element (e.g., a button, window, slider, or other user interface element) on the touch screen display, the particular user interface element is adjusted in accordance with the detected input. In some implementations, the focus moves from one area of ​​the user interface to another area of ​​the user interface without corresponding movement of a cursor or movement of a contact on the touch screen display (e.g., by using a tab key or arrow keys to move the focus from one button to another); in these implementations, the focus selector moves in accordance with the movement of the focus between different areas of the user interface. Regardless of the specific form the focus selector takes, the focus selector is typically a user interface element (or contact on the touch screen display) that is controlled by the user to deliver the user's intended interaction with the user interface (e.g., by indicating to the device the element of the user interface with which the user desires to interact). For example, when a press input is detected on a touch-sensitive surface (e.g., a touchpad or touchscreen), the position of a focus selector (e.g., a cursor, contact, or selection box) over a corresponding button will indicate that the user intends to activate the corresponding button (rather than other user interface elements shown on the device display).

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

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

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

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

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

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

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

[0196] Attention is now turned to an embodiment of a user interface ("UI") and associated processes implemented on an electronic device, such as portable multifunction device 100, device 300, or device 500.

[0197] 6A to 6F An exemplary user interface for performing security operations according to some embodiments is shown. Specifically, 6A to 6F 600. An exemplary user interface is shown that may be displayed during a scenario in which a secure transaction (e.g., transferring a parking space between accounts) is completed in response to receiving one or more gestures and biometric data from a user of device 600. The user interfaces in these figures are used to illustrate the processes described below, including Figure 8 and Fig. 9 In some embodiments, 6A to 6F The exemplary user interface of FIG. 7A to FIG. 7M The exemplary user interfaces of are combined or displayed simultaneously.

[0198] Fig. 6A Device 600 is shown displaying a user interface 602 on a touch-sensitive display. In some embodiments, device 600 includes one or more features of devices 100, 300, and 500 described below.

[0199] like Fig. 6A As shown, user interface 602 includes application icons 604. Application icons 604 include multiple application icons for launching different applications that cause different user interfaces to be displayed on device 600. Application icons 604 include parking application icon 604a for launching a parking application and coffee shop application icon 604b for launching a coffee shop application. Fig. 6A At , the device 600 detects a tap gesture 650a on the parking application icon 604a (eg, detects a tap gesture involving the icon, detects a tap gesture at a location corresponding to the icon).

[0200] like Figure 6B As shown, in response to detecting the tap gesture 650a, the device 600 launches the parking application corresponding to the parking application icon 604a and displays the user interface 610 of the parking application. The user interface 610 includes an account identifier 612, current parking information 614, and recommended parking information 616. The account identifier 612 indicates that the device 600 is currently logged into a specific account ("Jane's account") that is recognized by the parking application and / or belongs to the parking application (e.g., stored in a database in communication with the parking application). The recommended parking information 616 includes information about one or more available parking spaces that are being recommended to the user of the device 600.

[0201] like Figure 6B As shown, current parking information 614 indicates that parking space #31 is currently assigned to Jane's account and is located in Garage A at 123 Gala Street. Current parking information 614 also includes a time frame (e.g., 9:00 AM - 11:00 AM) during which parking space #31 will be assigned to Jane's account before parking space #31 is automatically transferred back to the account associated with Garage A. In addition, the current parking information includes a registration control 618 for transferring parking space #31 from Jane's account to an account belonging to Garage A. Figure 6B , device 600 detects a tap gesture 650b on registration control 618.

[0202] like Figure 6CAs shown, in response to detecting tap gesture 650b, device 600 initiates a process for performing a transaction (e.g., performing a security operation) that includes transferring parking space #31 from Jane's account to an account associated with garage A. Figure 6C As shown, in response to detecting the tap gesture 650b, the device 600 displays the user interface 620 on a portion of the user interface 610 and blurs the user 610 while keeping the display on the Figure 6C User interface 620 includes transaction information 622, confirmation instructions 624, and input instructions 626. Transaction information 622 includes information such as: an email address (e.g., "jane-apples@mail.com") that is assigned to a particular account (e.g., "Jane's Account") to which parking space #31 is currently assigned (e.g., the email address is on file with the particular account); and an identifier ("Garage A") that is associated with the account to which parking space #31 will be transferred. Figure 6C , the parking application is configured to perform the transfer operation using Jane's account (e.g., and / or an email address assigned to Jane's account). Confirmation instructions 624 indicate that input must be received on hardware button 648 (e.g., a "side button") in order to initiate the transaction, and input instructions 626 indicate that hardware button 648 must be pressed twice quickly (e.g., "double-clicking" the hardware button) in order to initiate the transaction. Figure 6C At , device 600 detects a double-click input 650c on hardware button 648.

[0203] exist Fig.6D In response to detecting the double-click input 650c, device 600 initiates an authentication process that causes camera 646a and / or camera 646b to capture an image to obtain biometric data (e.g., data corresponding to one or more features of the user's face). As part of the authentication process, device 600 also replaces confirmation instruction 624 with biometric identification state indicator 628 to indicate that device 600 is attempting to capture an image to obtain biometric information.

[0204] exist Fig.6DAt, after capturing a set of images, the device 600 obtains biometric data (e.g., one or more features of the user's face) in order to authenticate the user so that the transaction can be authorized. The device 600 uses this newly obtained biometric data to authenticate the current user of the device 600 by matching the newly obtained biometric data with previously stored biometric data associated with a known user (e.g., matching within a certain confidence level) and the known user has permission to complete a secure transaction via the device 600. In some embodiments, the biometric data (e.g., previously stored biometric data and newly captured biometric data) can be accessed by an application that manages secure transactions (or operations) on the device 600. In some embodiments, the parking application cannot access the biometric data. In some embodiments, when the device 600 cannot match the newly obtained biometric data with the previously stored biometric data, the device 600 will continue to capture images to obtain additional biometric data in order to match the previously stored biometric data. In some embodiments, the device 600 will only capture images for a predetermined period of time. In some embodiments, when device 600 cannot match the biometric data, device 600 will display an indication that parking space #31 cannot be transferred to garage A because the user of device 600 cannot be authenticated, and / or display an authentication control for completing the transaction in other ways (e.g., via a passcode entry). In some embodiments, device 600 can authenticate the user by capturing and comparing other types of biometric data, such as fingerprint data (e.g., captured via a touch-sensitive display including a fingerprint sensor), voice data (e.g., via one or more microphones), etc. Fig.6D At , device 600 (or another device in communication with device 600 ) matches the newly acquired set of biometric data with previously stored biometric data, which authenticates the current user of device 600 as a user with permission to complete secure transactions via device 600 .

[0205] exist Fig. 6E At , in response to authenticating the current user of device 600 as a user with permission to complete the secure transaction (e.g., via Jane's account), device 600 causes parking space #31 to be transferred from Jane's account to Garage A's account. In some embodiments, device 600 causes parking space #31 to be transferred from Jane's account to Garage A's account using a secure hardware component (e.g., a hardware chip) that stores information representing Jane's account (e.g., Jane's email address; a device-specific account identifier). In some embodiments, the secure hardware component does not store or access primary information associated with Jane's account (e.g., a primary account number). In some embodiments, authenticating that the current user of device 600 has permission to complete the secure transaction authorizes device 600 to use the secure hardware component to complete the secure transaction.

[0206] like Fig. 6E As shown, in response to authenticating the current user of device 600 as a user with permission to complete the secure transaction, device 600 also replaces biometric status indicator 628 with authenticated status indicator 630 to indicate that the user has been authenticated and the transfer has been completed.

[0207] like Fig. 6F As shown, after completing the transfer, device 600 stops displaying user interface 620 and updates user interface 610 to show (e.g., via confirmation instruction 624) that parking space #31 is no longer assigned to Jane's account. In addition, after completing the transfer, device 600 also receives and displays notification 632 (e.g., from one or more external devices) indicating that the transfer has been completed.

[0208] FIG. 7A to FIG. 7M An exemplary user interface for performing security operations according to some embodiments is shown. Specifically, FIG. 7A to FIG. 7M 1 shows exemplary user interfaces that may be displayed during a scenario in which one or more secure transactions are attempted to be completed in response to receiving one or more gestures on a touch-sensitive display of an automobile head unit 700 in communication with a device 600. The user interfaces in these figures are used to illustrate the processes described below, including Figure 8 and Fig. 9 process.

[0209] like Fig. 7A As shown, device 600 is in operative communication with automobile head unit 700, as indicated by communication link 708. In some embodiments, device 600 is in operative communication with automobile head unit 700 via a wireless or wired connection. In some embodiments, automobile head unit 700 includes a touch-sensitive display and is mounted in the dashboard of the automobile. In some embodiments, automobile head unit 700 includes one or more features of devices 100, 300, and 500 described above.

[0210] like Fig. 7AAs shown, the device 600 displays a user interface 670 including a lock indication 672, which indicates that the device 600 is in a locked state (e.g., a state in which one of the displays or functions (e.g., display function; input function) available in the unlocked state is disabled / unavailable). When the device 600 is in the locked state, one or more operations that can be performed when the device 600 is in the unlocked state cannot be performed when the device 600 is in the locked state. The one or more operations include the device 600 performing one or more operations for interacting with the automobile head unit 700 when the device 600 is in the locked state without receiving prior permission to do so. The one or more operations for interacting with the automobile head unit 700 include (e.g., by sending instructions and data) an operation to cause the automobile head unit 700 to display one or more user interface components (e.g., user interface, icons) corresponding to an application installed on the device 600.

[0211] exist Fig. 7A , the device 600 has not received prior permission to interact with the automobile head unit 700 while the device 600 is operating in a locked state. Fig. 7A At , the device 600 causes the car head unit 700 to display a user interface 714. The user interface 714 is displayed in response to the device 600 detecting a connection between the car head unit 700 and the device 600 (e.g., operable communication has been established). The user interface 714 includes instructions for causing the user to unlock the device 600 so as to cause the device 600 to cause “Carplayer” to launch on the car head unit 700 and / or to perform one or more operations that cause the car head unit 700 to display one or more user interface components corresponding to applications installed on the device 600.

[0212] like Fig. 7A As shown, because the device 600 has not received prior permission to interact with the automobile head unit 700 (e.g., provide data to and / or receive data from the automobile head unit) while the device 600 is operating in a locked state, the device 600 displays a notification 676 that includes instructions similar to the instructions displayed on the automobile head unit 700. In some embodiments, when the device 600 is in operative communication with another display device (e.g., the automobile head unit 700) and has received prior permission to interact with the other display device, the device 600 causes the other display device to display one or more user interface components corresponding to an application installed on the device 600. Fig. 7A, device 600 receives an upward swipe gesture 750a on user interface 670 and obtains biometric data (e.g., via one or more of cameras 646a and 646b) to authenticate the user in order to perform a security operation to unlock device 600. In some embodiments, device 600 obtains biometric data (e.g., via cameras 646a and / or 646b) and / or authenticates the user of device 600 to unlock device 600 using one or more techniques similar to those described above (e.g., in response to detecting a swipe gesture 750a). Figure 6C 650c) to unlock the device 600.

[0213] like Figure 7B As shown, in response to receiving the upward swipe gesture 750a and in response to authenticating the user of device 600, device 600 switches to operate in the unlocked state and stops displaying user interface 670. In addition, in response to receiving the upward swipe gesture 750a and in response to authenticating the user of device 600, device 600 displays user interface 602 including application icons 604. Figure 7B At , user interface 602 is displayed because user interface 602 is the last user interface displayed by device 600 before device 600 enters the locked state.

[0214] like Figure 7B As shown, because the device 600 is operated in an unlocked state, the device 600 causes the automobile head unit 700 to display a user interface 702, which includes an enlarged setting application icon 704. The application icons 704 include: a parking application icon 704a, which corresponds to the same application as the parking application icon 604a (e.g., it launches an application on the automobile head unit 700 that is compatible with (e.g., can access data from) the parking application of the application icon 604; causes the device 600 to cause the automobile head unit 700 to display an interface directly generated by the parking application on the device 600); and a coffee shop application icon 704b, which corresponds to the same application as the coffee shop application icon 604b. The application icon 704 is larger than the application icon 604, so that the application icon 704 can be seen and interacted with by the user operating the vehicle in a more readable manner. In addition, the application icon 704 is a subset of the application icon 604. That is, the number of application icons 704 is smaller than the number of application icons 604, and some of the application icons included in the application icons 604 are not included in the application icons 704 (eg, a camera application icon).

[0215] like Figure 7BAs shown, in response to receiving the upward swipe gesture 750a and in response to authenticating the user of the device 600, the device 600 also displays a user interface 660 overlaid on the user interface 602. The device 600 displays the user interface 660 because the device 600 has not received previous permission to interact with the automobile head unit 700 when the device 600 is operating in the locked state. The user interface 660 includes an allow interaction when locked control 661. Figure 7B At , device 600 allows a tap gesture 750b to be detected on control widget 661 when locked.

[0216] exist Figure 7C In response to detecting the tap gesture 750b, the device 600 receives permission to interact with the automobile head unit 700 while the device 600 is operating in the locked state, and stops displaying the user interface 660. Figure 7C As shown, in response to detecting the tap gesture 750b, the device 600 displays a user interface 662 overlaid on the user interface 602. The user interface 662 is a user interface for setting a trust level assigned to the automobile head unit 700, which the device 600 will use to determine whether the automobile head unit 700 can be trusted to initiate one or more security operations, as further described below. Figure 7C As shown, user interface 662 includes three options 664: an always option 664a; a once option 664b, and a never option 664c.

[0217] When the always option 664a is selected (e.g., via a gesture, such as a tap gesture), the device 600 is configured to permanently trust the car head unit 700, such that the car head unit 700 will be trusted by the device 600 until the device 600 is manually reconfigured (e.g., via one or more inputs on a different interface) to not trust the car head unit 700. Thus, the device 600 does not display FIG. 7A to FIG. 7C The user interface shown, because the automobile head unit 700 is a permanently trusted device in the following scenario, in which the device 600 disconnects (e.g., has ceased operable communications) and subsequently reconnects to the automobile head unit 700 (e.g., has initiated operable communications) after option always 664a has been selected.

[0218] When the one-time option 664b is selected, the device 600 is configured to temporarily trust the car head unit 700, so that the car head unit 700 will be trusted by the device 600 until the device 600 is disconnected from the car head unit 700. Therefore, the device 600 redisplays FIG. 7A to FIG. 7CThe user interface shown, because the automobile head unit 700 will no longer be a trusted device in the following scenario, in which the device 600 disconnects (e.g., has ceased operable communications) after option 664b has been selected once and is subsequently reconnected to the automobile head unit 700 (e.g., has initiated operable communications).

[0219] When the Never option 664c is selected, the device 600 is configured to not trust the car head unit 700, so that the car head unit 700 is not a trusted device. Therefore, the device 600 displays FIG. 7A to FIG. 7C The user interface shown because the automobile head unit 700 is not a trusted device in the following scenario, in which the device 600 disconnects (e.g., has ceased operable communications) and subsequently reconnects to the automobile head unit 700 (e.g., has initiated operable communications) after the Never option 664c has been selected.

[0220] Although Figure 7C A user interface 662 including three options 664 for setting the level of trust of the device 600 to the car head unit 700 is shown, but the car head unit 700 may be trusted or untrusted based on other factors. In some embodiments, the device 600 will be configured to trust the car head unit 700 when the car head unit 700 is a specific type of display device (such as a display device from a specific manufacturer or has a specific type of software installed). In some embodiments, the device 600 will be configured to trust the car head unit 700 when the device 600 is physically connected to a vehicle that includes hardware (e.g., a secure identity chip) that is trusted by the device 600. In some embodiments, the user interface 662 is not displayed in response to detecting the tap gesture 750b when the device 600 trusts the car head unit 700 based on other factors.

[0221] FIG. 7D to FIG. 7E It shows that Figure 7C An exemplary user interface displayed after the Never option 664c has been selected in . Figure 7C At , the device 600 detects a tap gesture 750c3 on the Never option 664c.

[0222] exist Fig.7D In response to detecting the tap gesture 750c3, the device 600 is configured such that the car head unit 700 is not a trusted device, as described above with respect to Figure 7C As discussed. Fig.7DAs shown, because the predetermined time period has passed since the tap gesture 750c3 was detected, the device 600 is also in the locked state (e.g., as indicated by the lock indication indicator 672), and the device 600 is configured to enter the locked state after the predetermined time period has passed. It is worth noting that the device 600 continues to interact with the automobile head unit 700 (e.g., causing the user interface 702 to be displayed) while the device 600 is in the locked state because the device 600 (e.g., via Figure 7B 750b) receives permission to do so. Fig.7D At , device 600 receives an indication from automobile head unit 700 that tap gesture 752d1 has been detected at a location on automobile head unit 700 that corresponds to parking application icon 704a.

[0223] like Fig. 7E As shown, in response to device 600 receiving an indication that tap gesture 752d1 has been detected, device 600 causes automobile head unit 700 to display user interface 710. User interface 710 corresponds to the above description of FIG. 6B to FIG. 6D The user interface 610 discussed above. Thus, the user interface 710 is a user interface for a parking application. Figure 6B When compared to user interface 610 of FIG. 7 , user interface 710 includes less information than that displayed on user interface 610 (e.g., no recommendation information on user interface 710). In addition, one or more similar components (e.g., account identifier 712) displayed on user interface 710 are enlarged when compared to corresponding components (e.g., account identifier 612) on user interface 610. However, Figure 6B User interface 610 and user interface 710 convey similar information.

[0224] like Fig. 7E As shown, user interface 710 includes account identifier 712 and current parking information 714 (e.g., which is displayed using similar techniques and for similar reasons as discussed above with respect to account identifier 612 and current parking information 614). Fig. 7E As shown, account identifier 712 indicates that device 600 is currently logged into "Jane's account," and current parking information 714 indicates that parking space #31 in garage A is currently assigned to Jane's account.

[0225] It is worth noting that Fig. 7EAs shown, in response to device 600 receiving an indication that tap gesture 752d1 has been detected, device 600 does not display a control corresponding to registration control 618. Here, device 600 does not display a control corresponding to registration control 618 because automobile head unit 700 is not a trusted device (e.g., via tap gesture 750c3 on never option 664c). Instead of causing the registration control to be displayed, device 600 causes automobile head unit 700 to display instructions 716 that indicate that the user must (e.g., via one or more inputs on device 600, as described above with respect to FIG. 6A to FIG. 6E ) completes the registration process on device 600. In some embodiments, if the parking application on device 600 does not have an account already filed with (e.g., linked to) the application, device 600 causes automobile head unit 700 to display instructions 716, even if the device is a trusted device. Fig. 7E At this point, one or more inputs that would cause device 600 to complete a secure operation cannot be detected on automobile head unit 700 because automobile head unit 700 is not trusted by device 600 .

[0226] FIG. 7F to FIG. 7I It shows that Figure 7C An exemplary user interface displayed after the always option 664a or the once option 644b has been selected in FIG. Figure 7C At , the device 600 detects a tap gesture 750c1 on the always option 664a, or a tap gesture 750c2 on the once option 644b. Figure 7F In response to detecting the tap gesture 750c1 or the tap gesture 750c2, the device 600 is configured to make the automobile head unit 700 a trusted device (e.g., as described above with respect to Figure 7C discussed). Figure 7F At the automobile head unit 700 and the device 600 display and display at Fig.7D The user interface in is the same as the corresponding user interface in Figure 7F At , device 600 receives an indication from automobile head unit 700 that tap gesture 752d1 has been detected at a location on automobile head unit 700 that corresponds to parking application icon 704a.

[0227] like Figure 7G As shown, in response to device 600 receiving an indication that tap gesture 752d1 has been detected, device 600 causes automobile head unit 700 to display user interface 710. In addition to one different component, Figure 7G The user interface 710 includes the Fig. 7E The same components as described in the user interface. Figure 7G As shown, the user interface 710 includes a Fig. 7E718 in the registration control and excludes the display Fig. 7E Instruction 716. Figure 7G At , device 600 causes car head unit 700 to display a registration control because car head unit 700 is trusted by device 600 (eg, via selection of always option 664a or once option 644b). Figure 7C In some embodiments where a tap gesture 750c2 on option 644b is detected once, the registration control 718 will not be displayed when the user interface 710 is redisplayed after the device 600 is disconnected and subsequently reconnected to the automobile head unit 700. Figure 7C In some embodiments where a tap gesture 750c1 on the always option 644a is detected, the enrollment control 718 will be displayed when the user interface 710 is redisplayed after the device 600 is disconnected and subsequently reconnected to the automobile head unit 700. Figure 7G At , device 600 receives an indication from automobile head unit 700 that tap gesture 752g has been detected at a location on automobile head unit 700 that corresponds to enrollment control 718. In some embodiments, enrollment control 718 is not displayed when account information associated with Jane's account (e.g., Jane's email address) is not stored in the secure hardware component and is configured for use in completing transactions using the parking application.

[0228] like Figure 7H As shown, in response to receiving an indication that tap gesture 752g has been detected, device 600 causes automobile head unit 700 to replace registration control 718 with confirmation control 728. Figure 7H At , device 600 receives an indication from automobile head unit 700 that tap gesture 752h has been detected at a location on automobile head unit 700 that corresponds to confirmation control 728.

[0229] exist Fig.7I In response to receiving an indication that tap gesture 752h has been detected, device 600 causes parking space #31 to be transferred from Jane's account to garage A's account. In some embodiments, the transfer occurs in response to tap gesture 752g on registration control 718 without requiring further confirmation input. Fig.7IAt , when device 600 causes parking space #31 to be transferred from Jane's account to garage A's account, device 600 (rather than automobile head unit 700) transmits one or more external devices (e.g., databases, account management servers) that update Jane's account information and garage A's account information to perform the transfer. In some embodiments, information corresponding to Jane's account (e.g., Jane's email address) is stored in a secure hardware component of device 600, and device 600 accesses information corresponding to Jane's account in the secure hardware component. In some embodiments, device 600 sends the accessed information corresponding to Jane's account (e.g., or a token corresponding to the accessed information) to one or more external devices as part of performing the transfer.

[0230] Re-view FIG. 6C to FIG. 6D , device 600 causes parking space #31 to be transferred in response to detecting a confirmation gesture (e.g., double-tap input 650c) after authenticating the user via capturing biometric data (e.g., via cameras 646a and 646b). Figure 7H , upon receiving an indication that tap gesture 752h was detected, device 600 causes parking space #31 to be transferred from Jane's account to Garage A's account without authenticating the user of device 600 and / or automobile head unit 700. Figure 7H In some embodiments, device 600 does not need to authenticate the user via capturing biometric data because the automobile head unit 700 is trusted by device 600. When the user is operating the vehicle, it may be beneficial to allow the user of the trusted display device to complete transactions without providing biometric data (or other authentication data) via device 600 for simplicity and security reasons. In some embodiments, device 600 also does not need to authenticate the user via biometric data because when device 600 is in FIG. 6A to FIG. 6B When not unlocked, device 600 has previously authenticated the user.

[0231] like Fig.7I As shown, in response to receiving an indication that a tap gesture 752h has been detected, device 600 causes automobile head unit 700 to display a transaction interface 720 including transaction information 722. Transaction interface 720 includes information about the transaction that has completed the transfer of parking space #31 from Jane's account to Garage A's account. Transaction information 722 uses the same information as described above regarding Fig. 6E Transaction information 622 is displayed using a similar technique as described for transaction information 622. Here, transaction information 722 and transaction information 622 are displayed using different layouts. In some embodiments, transaction information 722 and transaction information are displayed using the same layout.

[0232] Figures 7J to 7LAn exemplary user interface is shown displayed in a scenario in which another type of transaction (e.g., a payment transaction) using a different application (e.g., a coffee shop application) is attempted. Figure 7C After you have selected Always option 664a or Once option 644b. Return to Figure 7F (or Fig.7D ), device 600 receives an indication from automobile head unit 700 that a tap gesture 752d2 has been detected at a location on automobile head unit 700 corresponding to coffee shop application icon 704b.

[0233] like Figure 7J As shown, in response to receiving an indication that a tap gesture 752d2 has been detected, the device 600 causes the car head unit 700 to display a user interface 730, which is a user interface for a coffee shop application. The user interface 730 includes an order recommendation 734 and a purchase control 738. Figure 7J At , device 600 causes car head unit 700 to display purchase controls 738 because car head unit 700 is a trusted device (e.g., Figure 7C In some embodiments, when the car head unit 700 is not trusted by the device 600, the device 600 does not cause the car head unit 700 to display the purchase control 738. In some embodiments, the car head unit 700 may display instructions indicating that the device 600 must be used to purchase items from the coffee shop (e.g., instructions similar to instructions 716, as described above with reference to FIG. 714). Fig. 7E discussed). Figure 7J At , device 600 receives an indication from automobile head unit 700 that tap gesture 752 j has been detected at a location on automobile head unit 700 that corresponds to confirmation control 728 .

[0234] like Figure 7K As shown, in response to receiving an indication that tap gesture 752j has been detected, device 600 causes automobile head unit 700 to display user interface 740. User interface 740 is a user interface for purchasing an order associated with Jane's account. Figure 7J In the example, Jane's account is associated with a favorite order that includes a cup of cold brew coffee priced at $2.59. Figure 7J As shown, Jane's account is also associated with a card representation 734 ("Jane's card"), which is a representation of a payment card linked to the bank account associated with Jane. Figure 7J As shown, the user interface 740 also includes an order confirmation control 742, which is similar to Figure 7H Confirmation control 728 in the Figure 7KAt , device 600 receives an indication from automobile head unit 700 that tap gesture 752k has been detected at a location on automobile head unit 700 that corresponds to confirmation control 728.

[0235] like Figure 7L As shown, in response to receiving an indication that tap gesture 752k has been detected, device 600 causes $2.59 to be transferred from the bank account associated with Jane's card to the bank account associated with garage A (and / or the parking application) without capturing biometric data and / or authenticating the user of automobile head unit 700 and / or device 600 (e.g., for reasons described above with respect to Fig.7I for similar reasons as discussed in Figure 7L At , when device 600 causes money to be transferred from a bank account associated with Jane's card to a bank account associated with garage A, device 600 (rather than car head unit 700) transmits one or more external devices (e.g., databases, account management servers) that update the balances of Jane's account and garage A's account to reflect the completed transaction. In some embodiments, device 600 causes money to be transferred from Jane's account to garage A's account using a secure hardware component (e.g., a hardware chip) having stored information representing an account number associated with Jane's card. In some embodiments, the secure hardware component does not store or access primary information associated with Jane's card (e.g., primary account number). In some embodiments, when device 600 is not configured to process transactions using Jane's card, device 600 cannot process transactions, and device 600 does not display purchase controls 638 in user interface 730, regardless of whether car head unit 700 is trusted by device 600.

[0236] like Figure 7L As shown, in response to receiving an indication that a tap gesture 752k has been detected, device 600 causes automobile head unit 700 to display user interface 760 including transaction information 762. Transaction information 762 displays information similar to transaction information 722, as described above with respect to Figure 7L In addition, use Figure 7L The transaction information 722 is displayed in the same layout Figure 7L Transaction information 762. Figure 7L As shown, transaction information 762 indicates a transfer of $2.59 from an account associated with Jane's card, which is indicated by card representation 762.

[0237] Figure 7MThe device 600 is shown displaying a settings user interface having a settings position 772. The settings position 772 is enabled (e.g., "on") and is a settings position for allowing transactions to be processed via gestures received at the automobile head unit 700. FIG. 7A to FIG. 7M In the example discussed above, when the automobile head unit 700 is trusted by the device 600, the device 600 can cause various transactions to be processed in response to detecting a gesture received on the automobile head unit 700. FIG. 7A to FIG. 7M In the example discussed, setting position 772 is on. In some embodiments, when setting position 772 is off, regardless of whether the car head unit 700 is trusted by the device 600, the device 600 is unable to cause various transactions to be processed in response to detecting gestures received at the car head unit 700. In some embodiments, there are one or more other setting positions similar to setting position 772. These setting positions may allow a user of the device 600 to control whether the device 600 is able to cause various transactions to be processed for a particular application. In some embodiments, the device 600 is configured to allow transactions to be processed via gestures received at the car head unit 700 for a parking space application but not for a coffee shop application (e.g., via one or more setting positions). Thus, in some of these embodiments, and regardless of whether the car head unit 700 is trusted by the device 600, the device 600 is unable to cause one or more user interfaces (e.g., Figure 7G When the user interface 710 in FIG. 1 is displayed on the automobile head unit 700, the automobile head unit 700 is caused to display transaction controls (e.g., the registration control 718), and the device 600 is no longer caused to display one or more user interfaces used for the coffee shop application (e.g., Figure 7G The user interface 710 in FIG. 7A is displayed on the automobile head unit 700, causing the automobile head unit 700 to display transaction controls (eg, purchase controls 738).

[0238] Figure 8800 is a flowchart illustrating a method for performing security operations using a computer system according to some embodiments. Method 800 is performed at a computer system (e.g., 100, 300, 500, 600). The computer system (e.g., 600) communicates (e.g., wirelessly; wiredly) with an external automobile head unit (e.g., 700) (e.g., a unified hardware interface (e.g., a stereo head unit; an infotainment system) of multiple entertainment and information systems (e.g., sound; navigation) of a car), the external automobile head unit includes one or more input components (e.g., a touch-sensitive surface (e.g., a touch screen), a hardware button), and wherein the computer system communicates with an external receiving device (e.g., a transaction management server; a payment terminal). Some operations in method 800 are optionally combined, the order of some operations is optionally changed, and some operations are optionally omitted.

[0239] As described below, method 800 provides an intuitive way to use a computer system to perform security operations. The method reduces the cognitive burden of a user using a computer system to perform security operations, thereby creating a more effective human-computer interface. The method also enables a user to use a computer system to perform security operations more securely and more safely. For battery-powered computing devices, enabling a user to use a computer system to perform operations faster and more efficiently saves power and increases the time between battery charges.

[0240] The computer system receives (802) first data from an external automobile head unit (e.g., 700) corresponding to input (e.g., 752g, 752h, 752j, 752k) received at one or more input components of the external automobile head unit (e.g., 700) corresponding to a request to use an application (e.g., a digital store application; a digital wallet application; an e-commerce application) associated with a first account on the computer system (e.g., 600) to perform a first transfer operation from a first account (e.g., Jane's account indicated by 712, Jane's card indicated by 734) (e.g., an account associated with a user of the computer system; a credit account; a debit account; a cash balance account) to a second account (e.g., a garage account, a coffee shop account) (e.g., an account associated with a merchant).

[0241] In response to receiving first data (e.g., data associated with input 752g, 752h, 752j, or 752k), the computer system initiates (804) a process (e.g., a process that may require one or more additional inputs (e.g., a process that requires input at the computer system to fully complete)) to perform a first transfer operation using an application on the computer system (e.g., a transaction (e.g., a payment transaction; a purchase). In some embodiments, the first operation is performed in response to receiving the first data. In some embodiments, the first data includes one or more parameters or variables that affect the operation (e.g., an amount purchased; an item purchased). As part of performing the first transfer operation, the computer system transmits second data including information identifying a first account (e.g., an encrypted representation of an account stored on the computer system (e.g., a device-specific account number); a representation of a payment account (e.g., a credit account, a debit account, and / or a cash balance account)) to an external receiving device. In some embodiments, the second data includes information other than the account identifier (e.g., transaction parameters (e.g., price; amount)). Performing the transfer operation based on input on the automobile head unit using an application on the computer system provides the user with the ability to perform the transfer operation without having to interact directly with the computer system. Performing the operation without having to interact directly with the computer system can increase user confidence when using the computer system and operating the automobile. Performing the transfer operation based on input on the automobile head unit using an application on the computer system also provides the user with the option of performing the operation using input on the head unit. Providing additional control options enhances the operability of the computer system and makes the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device), which in turn reduces power usage and extends the battery life of the device by enabling the user to use the computer system more quickly and efficiently.

[0242] In some embodiments, an application (e.g., an application indicated by 604a, 704a, 604b, 704b) is configured (e.g., and continues to be configured) to perform a transfer operation from a first account prior to receiving the first data (e.g., the first account was previously associated with the application (e.g., the first account was archived with the application)). In some embodiments, a second application that has not been previously configured to perform a transfer operation from an existing account (e.g., the first account) cannot be used in conjunction with the external automobile head unit to perform the transfer operation (e.g., until the second application is associated with the existing account). Performing the transfer operation using an application on the computer system that has been configured to perform an operation using the first account (e.g., by reducing the risk of errors when using the wrong account or providing account information) reduces the risk of erroneous operation. Reducing the risk of errors when operating the computer system enhances the operability of the computer system and makes the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device), which in turn reduces power usage and extends the battery life of the device by enabling the user to use the computer system more quickly and efficiently.

[0243] In some embodiments, a second application (e.g., an application indicated by 604a, 704a, 604b, 704b) different from the first application (e.g., an application indicated by 604a, 704a, 604b, 704b) is installed on the computer system (e.g., 600). In some embodiments, based on (e.g., based on determining) that the second application (e.g., an application indicated by 604a, 704a, 604b, 704b) is configured to perform a transfer operation from a third account (e.g., Jane's account as indicated by 712, Jane's card as indicated by 734) (e.g., an account different from the first account; the same account as the first account), the second application is configured to perform a transfer operation in response to receiving a request from the external automobile head unit (e.g., 700) to perform a transfer operation from the third account (e.g., Jane's account, Jane's card). In some embodiments, the second application (e.g., the application indicated by 604a, 704a, 604b, 704b) is not configured to perform a transfer operation from a third account (e.g., not configured (e.g., preconfigured) to perform a transfer operation from any existing account) based on (e.g., based on a determination). In some embodiments, the second application is not configured to perform a transfer operation in response to a request (e.g., 752g, 752h, 752j, 752k) received from an external automobile head unit (e.g., 700) to perform a transfer operation from a third account (e.g., Jane's account as indicated by 712, Jane's card as indicated by 734). In some embodiments, only installed applications that have been configured to perform transfer operations from one or more existing accounts can perform a transfer operation based on input received at the external automobile head unit. Based on whether a given application has been configured to perform an operation using an account, using an application on a computer system to perform a transfer operation (e.g., by reducing the risk of errors in using an incorrect account or providing account information) reduces the risk of erroneous operations. Reducing the risk of errors when operating a computer system enhances the operability of the computer system and makes the user-device interface more efficient (e.g., by helping users provide appropriate input and reducing user errors when operating / interacting with the device), which in turn reduces power usage and extends device battery life by enabling users to use the computer system more quickly and efficiently.

[0244] In some embodiments, the second application is configured to perform the transfer operation from the third account. In some embodiments, the computer system (e.g., before receiving the first data; after receiving the first data) receives third data from an external automobile head unit (e.g., 700) (e.g., in some embodiments, from an external automobile head unit different from the external automobile head unit) corresponding to input (e.g., 752g, 752h, 752j, 752k) received at one or more input components of the external automobile head unit (e.g., 700) corresponding to a request to use a second application (e.g., applications indicated by 604a, 704a, 604b, 704b) to perform a second transfer operation from a third account (e.g., Jane's account indicated by 712, Jane's card indicated by 734) (e.g., an account associated with a user of the computer system; a credit account; a debit account; a cash balance account) to a fourth account (e.g., an account at Garage A; an account at a coffee shop) (e.g., an account associated with a merchant; the same account as the second account; an account different from the second account). In some embodiments, in response to receiving the third data, the computer system initiates a process (e.g., a process that may require one or more additional inputs (e.g., a process that requires input at the computer system to fully complete)) to perform a second transfer operation using a second application (e.g., an application indicated by 604a, 704a, 604b, 704b) (e.g., a transaction (e.g., a payment transaction; a purchase)) (and in some embodiments, performs the first operation in response to receiving the first data). In some embodiments, the first data includes one or more parameters or variables that affect the operation (e.g., the amount purchased; the item purchased). In some embodiments, as part of performing the second transfer operation, the computer system transmits fourth data including information identifying a third account (e.g., Jane's account as indicated by 712, Jane's card as indicated by 734) to an external receiving device (e.g., an encrypted representation of an account stored on the computer system (e.g., a device-specific account number); a representation of a payment account (e.g., a credit account, a debit account, and / or a cash balance account)). In some embodiments, the second data includes information other than an account identifier (e.g., a transaction parameter (e.g., price; amount)). Based on the input on the automobile head unit, using a second application on the computer system to perform a second transfer operation provides the user with the ability to perform the second transfer operation without having to interact directly with the computer system. Performing the operation without having to interact directly with the computer system can increase user confidence when using the computer system and operating the automobile. Based on the input on the automobile head unit, using an application on the computer system to perform the transfer operation also provides the user with the option of performing the operation using the input on the head unit.Providing additional control options enhances the operability of the computer system and makes the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device), which in turn reduces power usage and extends the battery life of the device by enabling the user to use the computer system more quickly and efficiently.

[0245] In some embodiments, a computer system (e.g., 600) communicates with (e.g., includes) a display generating component (e.g., a display (e.g., an integrated touch screen display)), wherein when the computer system (e.g., 600) receives the first data, the display generating component is in a locked state (e.g., 760) (e.g., a state in which one or more functions of the display that are available in an unlocked state (e.g., display functions; input functions) are disabled / unavailable). Using an application on the computer system to perform a transfer operation based on input on a car head unit when the computer system is in a locked state also provides the user with the option of using input on the head unit to perform operations without having to separately unlock the computer system, which can reduce the risk of unintentional input at the computer system; doing so also enhances the security of the system by allowing the computer system to remain in a locked state more often (e.g., while still being available). Providing additional control options and improving security enhances the operability of the computer system and makes the user-device interface more efficient (e.g., by helping users provide appropriate input and reducing user errors when operating / interacting with the device) and secure, which in turn reduces power usage and extends device battery life by enabling users to use the computer system more quickly, efficiently, and safely.

[0246] In some embodiments, the external automobile head unit (e.g., 700) has been authorized (e.g., before receiving the first data) (e.g., the external automobile head unit is a trusted unit; authorized via input from a user) to request a transfer operation from a first account (e.g., Jane's account as indicated by 712, Jane's card as indicated by 734) (e.g., and from other accounts accessible to and / or stored on the computer system). In some embodiments, an unauthorized (e.g., trusted) external automobile head unit cannot request a transfer operation from an account accessible to and / or stored on the computer system. Using an application on the computer system to perform transfer operations based on input on the automobile head unit (only if the unit is authorized) reduces the risk of unauthorized operations (e.g., particularly where the user of the computer system does not control the input provided at the head unit). Reducing the risk of unauthorized operation and improving the security of computer systems enhances the operability of computer systems and makes user-device interfaces more efficient (e.g., by helping users provide appropriate input and reducing user errors when operating / interacting with devices), which in turn reduces power usage and extends device battery life by enabling users to use computer systems more quickly and efficiently.

[0247] In some embodiments, the computer system receives a first set of one or more inputs (e.g., 750c1, 750c2) (e.g., inputs at an external automobile head unit and / or the computer system) prior to detecting first data (e.g., data associated with input 752g, 752h, 752j, or 752k). In some embodiments, in response to the first set of one or more inputs (e.g., 750a, 750b, 750c1, 750c2), the computer system authorizes (e.g., authorizes before communicating) connecting the external automobile head unit (e.g., 700) to the computer system (e.g., 600) when the computer system is in a locked state (e.g., 760) (e.g., a state in which one or more functions of the computer system that are available when in an unlocked state are unavailable); and authorizes the external automobile head unit (e.g., 700) to request a transfer operation from a first account (e.g., and from other accounts accessible to and / or stored on the computer system) . Authorizing an external automobile head unit to request to perform a transfer operation based on previous user input provides the user with additional control options and reduces the need for authorization input on a per-operation basis. Providing additional control options and performing operations without requiring input at specific times enhances the operability of the computer system and makes the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device), which in turn reduces power usage and extends the battery life of the device by enabling the user to use the computer system more quickly and efficiently. Utilizing an authorized (e.g., trusted) external automobile head unit to perform the transfer operation also improves security by reducing the risk of unauthorized requests for transfer operations. Reducing the risk of unauthorized operations and improving the security of the computer system enhances the operability of the computer system and makes the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device), which in turn reduces power usage and extends the battery life of the device by enabling the user to use the computer system more quickly and efficiently.

[0248] In some embodiments, the computer system receives a second set of one or more inputs (e.g., 750a) while the computer system is communicating with (e.g., while connected to) an external automobile unit (e.g., 700) and while the computer system (e.g., 600) is in a locked state (e.g., 760) (e.g., a state in which one or more functions of the computer system that are available when in the unlocked state are unavailable). In some embodiments, in response to the second set of one or more inputs (e.g., 750a), the computer system: transitions the computer system (e.g., 600) to an unlocked state (e.g., 602) (e.g., a state in which one or more functions of the computer system that are unavailable when in the locked state are available); and authorizes the external automobile head unit (e.g., 700) to request a transfer operation from the first account (e.g., and from other accounts accessible to and / or stored on the computer system). In some embodiments, the authorization occurs simultaneously as part of transitioning the computer system to the unlocked state (e.g., the authorization is a result of transitioning the computer system to the unlocked state). Authorizing an external automobile head unit request to perform a transfer operation based on a user input that also unlocks the computer system reduces the number of inputs required to perform a set of operations and also reduces the risk of unintentional operation of the computer system, because unlocking the computer system is associated with intentional use of the system. Reducing the number of inputs required to perform a set of operations and reducing the risk of unintentional operation of the inputs enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user provide appropriate inputs and reducing user errors when operating / interacting with the device), which in turn reduces power usage and extends the battery life of the device by enabling the user to use the device more quickly and efficiently. Authorizing an external automobile head unit request to perform a transfer operation based on a user input that also unlocks the computer system improves security by providing the user with the option to link the authorization of the unit with another authorized function. Improving the security of the computer system enhances the operability of the computer system and makes the user-device interface more efficient (e.g., by helping the user provide appropriate inputs and reducing user errors when operating / interacting with the device), which in turn reduces power usage and extends the battery life of the device by enabling the user to use the computer system more quickly and efficiently.

[0249] In some embodiments, before receiving the first data (e.g., data associated with input 752g, 752h, 752j, or 752k), the computer system transmits fifth data including one or more user interface elements (e.g., 718, 738) to be displayed by the automobile head unit. In some embodiments, the one or more user interface elements include one or more elements associated with an application (e.g., an identifier of the application) and / or one or more elements associated with a first account (e.g., an identifier of the first account). Transmitting data including one or more user interface elements to be displayed by the automobile head unit provides the user with visual feedback about the computer system and its connection with the head unit. Providing improved visual feedback to the user enhances the operability of the computer system and makes the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device), which in turn reduces power usage and extends the battery life of the computer system by enabling the user to use the computer system more quickly and efficiently.

[0250] In some embodiments, the computer system (e.g., 600) is a smartphone (e.g., a mobile computing device configured to make and receive calls over a cellular network) that includes a hardware security element (e.g., a chip that stores information representing an account that is not directly accessible to an operating system or installed applications of the computer system (e.g., account-related information, such as a device-specific account number provided by the issuer of the account (e.g., different from the account number)). In some embodiments, the security element does not store or access the primary account number. In some embodiments, as part of the transfer operation, the security element provides an encrypted version of the device-specific account number (e.g., a version unique to a given transaction), which is decrypted by the issuer of the account to identify the account. In some embodiments, information identifying the first account is stored in the hardware security element.

[0251] In some embodiments, when a computer system (e.g., 600) communicates (806) with a second external automobile head unit (e.g., 700) including one or more input components and a second external receiving device, wherein the second external automobile head unit (e.g., 700) is different from the external automobile head unit (e.g., 700), the computer system receives (808) from the second external automobile head unit (e.g., 700) sixth data corresponding to input (e.g., 752g, 752h, 752j, 752k) received at one or more input components of the second external automobile head unit corresponding to a request to use an application (e.g., a digital store application; a digital wallet application; an e-commerce application; an application different from the first application or the second application; an application that is the same as the first application and / or the second application) to perform a third transfer operation from a first account to a fifth account (e.g., an account associated with a provider). In some embodiments, when the computer system (e.g., 600) communicates (806) with a second external automobile head unit (e.g., 700) including one or more input components and a second external receiving device, in response to receiving the sixth data, the computer system initiates (810) a process (e.g., a process that may require one or more additional inputs (e.g., requires input at the computer system to be fully completed)) using an application on the computer system (e.g., 600) to perform a third transfer operation. In some embodiments, as part of performing the third transfer operation, the computer system transmits to the second external receiving device seventh data including information identifying a first account (e.g., an encrypted representation of an account stored on the computer system (e.g., a device-specific account number); a representation of a payment account (e.g., a credit account, a debit account, and / or a cash balance account). In some embodiments, the first operation is performed in response to receiving the first data. In some embodiments, the second data includes information other than an account identifier (e.g., transaction parameters (e.g., price; amount)). Providing different head units with the ability to request transfer operations at the computer system provides users with additional options for operating the computer system. Providing additional control options and performing operations without requiring input at specific times enhances the operability of the computer system and makes the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device), which in turn reduces power usage and extends device battery life by enabling the user to use the computer system more quickly and efficiently.

[0252] Note that the process described above with respect to method 800 (eg, Figure 8) also applies in a similar manner to the methods described below. For example, method 800 optionally includes one or more of the features of the various methods described below with reference to method 900. For example, method 800 can be used to initiate a process of performing a first transfer operation (e.g., 804) when the external input device meets a set of authorization criteria, and provide an option to initiate a secure transaction (e.g., in 906). For the sake of brevity, these details are not repeated below.

[0253] Fig. 9 900 is a flow chart illustrating a method for providing an option to initiate a security operation using a computer system according to some embodiments. Method 900 is performed at a computer system (e.g., 100, 300, 500, 600). Some operations in method 900 are optionally combined, the order of some operations is optionally changed, and some operations are optionally omitted.

[0254] As described below, method 900 provides an intuitive way to provide an option to use a computer system to initiate a security operation. The method reduces the cognitive burden of a user providing an option to use a computer system to initiate a security operation, thereby creating a more efficient human-computer interface. The method also enables a user to use a computer system to perform security operations more securely and more safely. For battery-powered computing devices, enabling a user to provide an option to use a computer system to initiate a security operation faster and more efficiently saves power and increases the time interval between battery charges.

[0255] After a computer system (e.g., 600) is connected to an external input device (e.g., 700) (e.g., an automobile head unit (e.g., a unified hardware interface for multiple entertainment and information systems (e.g., audio; navigation) of an automobile (e.g., a stereo head unit; an infotainment system))), the computer system receives (902) from the external input device a first portion (e.g., 710, 730) of a user interface associated with a secure transaction (e.g., a transfer of resources (e.g., credit; funds) from a first account (e.g., an account associated with a user of the computer system) to a second account (e.g., an account associated with a merchant) (e.g., an interface for a digital store application; a digital wallet application) associated with a secure transaction (e.g., a transfer of resources (e.g., credit; funds) from a first account (e.g., an account associated with a user of the computer system) to a second account (e.g., an account associated with a merchant)). package application; e-commerce application; an interface displayed at an external input device (e.g., generated at least in part based on data from the computer system)) to interact with a first request (e.g., 752d1, 752d2) (e.g., selection of an option or variable) that, if authorized from the computer system (e.g., 600), would require a separate authorization (e.g., 646a, 646b, 638) from the user (e.g., a transaction that requires additional authentication (such as entering a password or via fingerprint, facial, iris or other biometric authentication) when performed on the computer system via one or more inputs received via one or more input devices of the computer system).

[0256] In response to (904) receiving the first request (e.g., 752d1, 752d2) and based on determining that the external input device (e.g., 700) satisfies a set of authorization criteria (e.g., a set of criteria that are satisfied when the external input device has been authorized by a previous user input, when the external input device is a first type of device, and / or when the external input device is not a second type of device), the computer system provides (906) an option (e.g., 718) to initiate a secure transaction via the external input device (e.g., 700) without requiring separate authorization from the user (e.g., a selectable user interface object; a prompt (e.g., a visual or audio prompt) of one or more input devices (e.g., a touch-sensitive surface; a microphone) of the external input device to use the external input device).

[0257] In response to (904) receiving the first request (e.g., 752d1, 752d2) and based on determining that the external input device (e.g., 700) does not satisfy the set of authorization criteria, the computer system forgoes (912) providing an option to initiate a secure transaction without requiring separate authorization from the user (e.g., Fig. 7E716 in). In some embodiments, as part of giving up providing the option of initiating a secure transaction without requiring a separate authorization from the user, the computer system provides a second option of initiating a secure transaction requiring a separate authorization from the user at the external input device and / or the computer system. Providing the option of initiating a secure transaction without requiring a separate authorization from the user in response to a request at the external input device provides the user with the option of performing a secure transaction without requiring a separate authorization and without having to interact directly with the computer system. Providing the option of performing an operation without having to interact directly with the computer system and reducing the number of required inputs can improve the ease of use of the computer; doing so also provides the user with the option of using input on the external input device to perform the operation. Providing additional control options enhances the operability of the computer system and makes the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device), which in turn reduces power usage and extends the battery life of the device by enabling the user to use the computer system more quickly and efficiently. Providing the option of initiating a secure transaction when the external input device meets a set of authorization criteria improves security by not providing the option when the external input device does not meet the criteria. Improving the security of a computer system enhances the operability of the computer system and makes the user-device interface more efficient (e.g., by helping users provide appropriate input and reducing user errors when operating / interacting with devices), which in turn reduces power usage and extends device battery life by enabling users to use the computer system more safely, quickly, and efficiently.

[0258] In some embodiments, the external input device (e.g., 700) is an external automobile head unit (e.g., a unified hardware interface for multiple entertainment and information systems (e.g., sound; navigation) of a car (e.g., a stereo head unit; an infotainment system)). In some embodiments, the computer system (e.g., 600) is a smart phone (e.g., a mobile computing device configured to make and receive calls over a cellular network)) that includes a hardware security element for use in secure transactions (e.g., a chip that stores information representing an account that is not directly accessible to an operating system or installed applications of the computer system (e.g., account-related information, such as a device-specific account number provided by the issuer of the account (e.g., different from the account number)). In some embodiments, the security element does not store or access the primary account number. In some embodiments, as part of the transfer operation, the security element provides an encrypted version of the device-specific account number (e.g., a version unique to a given transaction), which is decrypted by the issuer of the account to identify the account.

[0259] In some embodiments, the computer system (e.g., 600) includes one or more external device communication interfaces (e.g., a communication system for transferring data between the computer system and one or more external devices; a wired communication bus; a wireless communication bus; a data bus). In some embodiments, the computer system detects a connection between the computer system and an external input device via the one or more external device communication interfaces (e.g., 708). In some embodiments, a first request is received after detecting a connection between the computer system and the external input device (e.g., 752d1, 752d2).

[0260] In some embodiments, a computer system (e.g., 600) communicates with one or more hardware input devices (e.g., a touch-sensitive display of 600) (e.g., a touch-sensitive surface (e.g., a touch screen); a microphone; a biometric reader (e.g., a fingerprint reader; an optical and / or depth sensor for detecting facial features)). In some embodiments, a secure transaction requires authorization from a user provided via one or more hardware input devices (e.g., authorization of the secure transaction is performed using information from a hardware security element (e.g., a chip that stores account information that is not directly accessible to an operating system or an installed application of the computer system) that stores information for use in a secure transaction (e.g., account information; information identifying an account)). In some embodiments, a computer receives a request to perform a secure transaction at the computer system. In some embodiments, after receiving a first request and based on determining that authorization has been provided via one or more hardware input devices (e.g., provided before receiving the first request; provided after receiving the first request), the computer system performs the secure transaction. Requiring authorization to perform a secure transaction improves security by reducing the risk of unauthorized requests. Improving the security of a computer system enhances the operability of the computer system and makes the user-device interface more efficient (e.g., by helping users provide appropriate input and reducing user errors when operating / interacting with devices), which in turn reduces power usage and extends device battery life by enabling users to use the computer system more safely, quickly, and efficiently.

[0261] In some embodiments, one or more hardware input devices include a biometric reader (e.g., 646a, 646b) (e.g., a fingerprint reader; an optical and / or depth sensor for detecting facial features)), and the authorization from the user provided via the one or more hardware input devices is a biometric authorization (e.g., indicated by 628, 630) received via the biometric reader (e.g., 646a, 646b) (e.g., an authorized fingerprint scan or an authorized facial scan) (e.g., authorization of the secure transaction is performed using information from a hardware security element (e.g., a chip that stores account information that is not directly accessible to an operating system or installed applications of the computer system) that stores information for use in secure transactions (e.g., account information; information that identifies an account). Requiring authorization via a biometric reader improves security by reducing the risk of unauthorized requests. Improving the security of a computer system enhances the operability of the computer system and makes the user-device interface more efficient (e.g., by helping users provide appropriate input and reducing user errors when operating / interacting with the device), which in turn reduces power usage and extends the battery life of the device by enabling users to use the computer system more securely, quickly, and efficiently.

[0262] In some embodiments, after providing the option to initiate a secure transaction without requiring separate authorization from the user (e.g., 718), a request to continue the secure transaction is received (e.g., 752g, 752h) from an external input device (e.g., 700) (e.g., input; selection of a payment-selectable user interface object displayed at a display of the external input device; a voice command received at the external input device). In some embodiments, as part of providing the option, the computer system transmits data to the external input device including one or more user interface elements to be displayed by the external input device). In some embodiments, in response to receiving a request to continue a secure transaction from an external input device (e.g., 700), the computer system performs (910) a secure transaction that includes securely transmitting first data to an external receiving device (e.g., a transaction management server; a payment terminal), the first data including information identifying a first account (e.g., "Jane's account," as indicated by 612, 712; "Jane's card," as indicated by 734) for use in the secure transaction (e.g., an encrypted representation of an account stored on the computer system (e.g., a device-specific account number); a representation of a payment account (e.g., a credit account, a debit account, and / or a cash balance account)). In some embodiments, the second data includes information other than the account identifier (e.g., transaction parameters (e.g., price; amount)). Performing a secure transaction based on a request from an external input device provides the user with the option of performing an operation using input at the external input device. Providing additional control options enhances the operability of the computer system and makes the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device), which in turn reduces power usage and extends the battery life of the device by enabling the user to use the computer system more quickly and efficiently.

[0263] In some embodiments, a computer system (e.g., 600) communicates with (e.g., includes) a display generating component (e.g., a display (e.g., an integrated touch screen display)). In some embodiments, performing a secure transaction (e.g., including securely transmitting first data including information identifying a first account to an external receiving device) occurs when the display generating component is in a locked state (e.g., 670) (e.g., a state in which one or functions of the display (e.g., display function; input function) available in an unlocked state are disabled / unavailable). Performing a secure transaction when a display generating component in communication with a computer system is in a locked state provides a user with the option of performing a transaction without having to interact with the display generating component (e.g., viewing or providing input involving the component). Providing additional control options enhances the operability of the computer system and makes the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device), which in turn reduces power usage and extends the battery life of the device by enabling the user to use the computer system more quickly and efficiently. Performing secure transactions while a display generating component in communication with a computer system is in a locked state also improves security by allowing the computer system to remain in a locked state while still permitting interaction via external input devices. Improving the security of a computer system enhances the operability of the computer system and makes the user-device interface more efficient (e.g., by helping users provide appropriate input and reducing user errors when operating / interacting with the device), which in turn reduces power usage and extends device battery life by enabling users to use the computer system more securely, quickly, and efficiently.

[0264] In some embodiments, a secure transaction is performed using a first application (e.g., an application corresponding to 604a, 604b) on a computer system (e.g., 600). In some embodiments, a user interface (e.g., 720, 760) is an interface displayed at an external input device (e.g., 700). In some embodiments, the user interface (e.g., 720, 760) is arranged according to a first interface layout template (e.g., a scheme for arranging graphical elements and / or content of an interface) and includes information (e.g., 722, 762) provided by the first application (e.g., an application corresponding to 604a, 604b) (e.g., a (e.g., textual and / or graphical) identifier of the first application; parameters affecting the execution of the secure transaction (e.g., the amount of credit or currency being transferred; the service or commodity being purchased); an identifier of an account to be used within the secure transaction). In some embodiments, the computer system receives a second request (e.g., 752d1, 752d2) from an external input device (e.g., 700) to interact with a first portion (e.g., the same interface as the user interface; a different interface from the user interface) of a second user interface (e.g., 720, 760) displayed at the external input device (e.g., 700) and associated with a second secure transaction performed using a second application (e.g., an application corresponding to 604a, 604b) on the computer system (e.g., 600), the second secure transaction requiring a separate authorization from the user if authorized from the computer system (e.g., 600). In some embodiments, the second application (e.g., an application corresponding to 604a, 604b) is different from the first application. In some embodiments, the second user interface (e.g., 720, 760) is arranged according to the first interface layout template and includes information (e.g., 722, 762) provided by the second application (e.g., the application corresponding to 604a, 604b) (e.g., a (e.g., text and / or graphic) identifier of the second application; parameters affecting the execution of the secure transaction (e.g., the amount of credit or currency being transferred; the service or commodity being purchased); an identifier of an account to be used within the second secure transaction). Arranging interfaces corresponding to different applications for executing different secure transactions according to the same interface layout provides the user with improved visual feedback that consistently informs the user of various aspects of the secure transaction. Providing improved visual feedback to the user enhances the operability of the computer system and makes the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device), which in turn reduces power usage and extends the battery life of the computer system by enabling the user to use the computer system more quickly and efficiently.

[0265] In some embodiments, the set of authorization criteria is met when: the computer system receives a first set of one or more inputs (e.g., 750a) (e.g., selection of an option in a peripheral management interface; a set of inputs received at an external input device; a set of inputs received at a computer system) prior to receiving a first request (e.g., 752d1, 752d2) (e.g., and when movement of a car connected to the external input device is not detected). In some embodiments, in response to the first set of one or more inputs (e.g., 750a), the computer system authorizes (e.g., authorizes before communicating with the external input device) connecting the external input device (e.g., 700) to the computer system (e.g., 600) while the computer system is in a locked state (e.g., 670) (e.g., a state in which one or more functions of the computer system that are available when in an unlocked state are unavailable). Authorizing the connection of the external input device to the computer system while the computer system is in a locked state provides additional control options for the user and reduces the need for authorization input when requesting a secure transaction. Providing additional control options enhances the operability of the computer system and makes the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device), which in turn reduces power usage and extends the battery life of the device by enabling the user to use the computer system more quickly and efficiently. Improving security by linking authorization features to reduce the risk of inadvertent authorization based on previous input that also authorizes connecting an external input device to the computer system when in a locked state to meet the authorization criteria. Improving the security of the computer system enhances the operability of the computer system and makes the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device), which in turn reduces power usage and extends the battery life of the device by enabling the user to use the computer system more safely, quickly, and efficiently.

[0266] In some embodiments, an external input device (e.g., 700) satisfies the set of authorization criteria based on a state (e.g., a state that establishes a duration for which the external input device will satisfy the set of authorization criteria (e.g., permanently (e.g., until revoked), temporarily (e.g., for an instantaneous duration (e.g., 1 day, 1 week) or for a preset number of connection events (e.g., 1 connection event; 5 connection events)) that is established (e.g., set) based on a second set of one or more inputs (e.g., 750b, 750c1, 750c2) received after a first set of one or more inputs (e.g., 750a) has been received (e.g., selection of a second option in a peripheral management interface; a set of inputs received at the external input device; a set of inputs received at the computer system). Establishing a state that affects satisfying the authorization criteria provides a user with a means to precisely control the computer system and the external input device. Additional control options for the relationship between a computer system and a device are provided. Additional control options are provided, which enhance the operability of the computer system and make the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device), which in turn reduces power usage and extends the battery life of the device by enabling the user to use the computer system more quickly and efficiently. Satisfying authorization criteria based on prior input improves security by providing the user with an opportunity to provide authorization outside the context of performing a specific secure transaction, which can reduce the risk of unintended authorization. Improving the security of the computer system enhances the operability of the computer system and makes the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device), which in turn reduces power usage and extends the battery life of the device by enabling the user to use the computer system more safely, quickly, and efficiently.

[0267] In some embodiments, the external input device (e.g., 700) satisfies the set of authorization criteria based on a state being a long-term (e.g., ambiguous until withdrawn) authorized state. In some embodiments, the first set of one or more inputs (e.g., 750a, 750b, 752c1) is received in the following circumstances: when the computer system (e.g., 600) and the external input device (e.g., 700) are in a connection session (e.g., a session that starts when the computer system is connected to the external input device and is sent when the connection is interrupted), the connection session is also the connection session during which the first request (e.g., 752d1, 752d2) is received; or when the computer system (e.g., 600) and the external input device (e.g., 700) are in a previous connection session, the previous connection session is different from the connection session during which the first request (e.g., 752d1, 752d2) is received.

[0268] In some embodiments, the external input device (e.g., 700) satisfies the set of authorization criteria based on the state being a short-term (e.g., temporary or lasting for an instantaneous duration (e.g., 1 day, 1 week) or lasting for a preset number of connection events (e.g., 1 connection event; 5 connection events); expiring without further user input) authorization state. In some embodiments, the first set of one or more inputs (e.g., 750a, 750b, 750c2) is received when the computer system and the external input device (e.g., 700) are in a connection session (e.g., a session that starts when the computer system is connected to the external input device and is sent when the connection is interrupted), which is also the connection session during which the first request (e.g., 752d1, 752d2) is received. In some embodiments, when the state is a temporary authorized state, the set of one or more inputs is not received (e.g., cannot be received) when the computer system and the external input device are in a previous connection session different from the connection session during which the first request was received.

[0269] In some embodiments, the external input device (e.g., 700) satisfies the set of authorization criteria based on input (e.g., 750a, 750b, 750c1, 750c2) received prior to receiving the first request (e.g., prior to connecting to the external input device) (e.g., selection of an option in a peripheral management interface), and the computer system authorizes (e.g., pre-authorizes) the external input device (e.g., 700) to provide a request to initiate one or more secure transactions that would require a separate authorization from the user if authorized from the computer system (e.g., 600). In some embodiments, authorizing (e.g., pre-authorizing) the external input device to provide input to initiate one or more secure transactions that would require a separate authorization from the user if authorized from the computer system is different from authorizing the external input device to connect to the computer system when the computer system is in a locked state (e.g., a state in which one or more functions of the computer system that are available when in an unlocked state are unavailable). Authorizing the external input device based on prior input allows the user to better control the relationship between the computer system and the external input device. Providing additional control options enhances the operability of the computer system and makes the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device), which in turn reduces power usage and extends the battery life of the device by enabling the user to use the computer system more quickly and efficiently. Satisfying authorization criteria based on prior and explicit input to authorize a secure transaction reduces the risk of unintended authorization and improves security. Improving the security of the computer system enhances the operability of the computer system and makes the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device), which in turn reduces power usage and extends the battery life of the device by enabling the user to use the computer system more safely, quickly, and efficiently.

[0270] In some embodiments, the external input device (e.g., 700) satisfies the set of authorization criteria based on input (e.g., 750a) received while connected to the external input device (e.g., 700) (e.g., while connected in the same connection session during which the first request was received) (e.g., accepting a prompt to provide authorization), and the computer system authorizes the external input device (e.g., 700) to provide a request to initiate one or more secure transactions, which would require a separate authorization from the user if authorized from the computer system (e.g., 600). Authorizing the external input device based on input received while connected to the external input device allows the user to better control the relationship between the computer system and the external input device and also reduces the risk of inadvertently authorizing the wrong device. Providing additional control options and reducing the risk of errors enhances the operability of the computer system and makes the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device), which in turn reduces power usage and extends the battery life of the device by enabling the user to use the computer system more quickly and efficiently.

[0271] In some embodiments, an external input device (e.g., 700) satisfies the set of authorization criteria based on the external input device (e.g., 700) being identified as a first type of device (e.g., a pre-authorized type of device (e.g., a device from a particular manufacturer; a type of device with particular hardware (e.g., secure hardware); a type of device with particular software (e.g., secure software)). In some embodiments, an external input device of a second type (e.g., not the first type) does not satisfy the set of authorization criteria. Authorizing an external input device based on the device being a first type of device reduces the risk of authorizing a device that does not have the necessary characteristics, thereby improving security, and also reduces the need for explicit input to authorize the first type of device. Improving security and reducing the number of inputs required to perform an operation enhances the operability of the computer system and makes the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device), which in turn reduces power usage and extends the battery life of the device by enabling the user to use the computer system more quickly and efficiently.

[0272] In some embodiments, an external input device (e.g., 700) (e.g., an automobile head unit (e.g., a unified hardware interface for multiple entertainment and information systems (e.g., sound; navigation) of an automobile (e.g., a stereo head unit; an infotainment system))) satisfies the set of authorization criteria based on the external input device being connected to a vehicle (e.g., a car; a motorcycle) that is identified as having authorized authentication hardware (e.g., an authentication identity chip). Authorizing an external input device based on the device being connected to a vehicle that is identified as having authorized authentication hardware improves security and also reduces the need for explicit input to authorize devices connected to such vehicles. Improving security and reducing the number of inputs required to perform an operation enhances the operability of the computer system and makes the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device), which in turn reduces power usage and extends the battery life of the device by enabling the user to use the computer system more quickly and efficiently.

[0273] Note that the above description is relative to method 900 (eg, Fig. 9 ) also applies in a similar manner to the methods described below. For example, method 900 optionally includes one or more features of the various methods described above with reference to method 800. For example, method 800 can be used to initiate a process of performing a first transfer operation (e.g., 804) when an external input device meets a set of authorization criteria, and provide an option to initiate a secure transaction (e.g., in 906). For the sake of brevity, these details are not repeated below.

[0274] For the purpose of explanation, the foregoing description has been described with reference to specific embodiments. However, the above exemplary discussion is not intended to be exhaustive or to limit the invention to the disclosed precise form. According to the above teachings, many modifications and variations are possible. These embodiments are selected and described in order to best explain the principles of these technologies and their practical applications. Others skilled in the art can thus best utilize these technologies and various embodiments with various modifications suitable for the intended specific use.

[0275] 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. It should be understood that such changes and modifications are considered to be included within the scope of the disclosure and examples defined by the claims.

[0276] As described above, one aspect of the present technology is to collect and use data from various resources to improve the management and security of operations (e.g., transactions) being performed at various devices. The present disclosure contemplates that, in some instances, these 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, phone numbers, email addresses, Twitter IDs, home addresses, data or records related to the user's health or fitness level (e.g., vital sign measurements, medication information, exercise information), date of birth, or any other identifying or personal information.

[0277] The present disclosure recognizes that the use of such personal information data in the present technology can be used to benefit users. For example, personal information data can be used to provide electronic devices with authorization to perform security operations (e.g., transactions) based on the personal information provided. Therefore, the use of such personal information data enables users to calculate control and / or increased security relative to security operations performed via electronic devices. In addition, the present disclosure also anticipates other uses of personal information data that benefit users. For example, health and fitness data can be used to provide insights into the user's overall health status, or can be used as positive feedback to individuals who use technology to pursue health goals.

[0278] This disclosure envisions that entities responsible for collecting, analyzing, disclosing, transmitting, storing or otherwise using such personal information data will comply with established privacy policies and / or privacy practices. Specifically, such entities should implement and adhere to privacy policies and practices that are recognized as meeting or exceeding industry or government requirements for maintaining the privacy and security of personal information data. Such policies should be easily accessible to users and should be updated as the collection and / or use of data changes. Personal information from users should be collected for legitimate and reasonable purposes of the entity and not shared or sold outside of these legitimate uses. In addition, such collection / sharing should be performed after receiving informed consent from the user. In addition, such entities should consider taking any necessary steps to safeguard and protect access to such personal information data and ensure that others who have access to personal information data comply with their privacy policies and processes. In addition, such entities may subject themselves to third-party assessments to demonstrate their compliance with widely accepted privacy policies and practices. In addition, policies and practices should be adjusted to specific types of personal information data collected and / or accessed, and to applicable laws and standards including specific considerations of jurisdiction. For example, in the United States, the collection or access of certain health data may be governed by federal and / or state laws, such as the Health Insurance Portability and Accountability Act (HIPAA), while health data in other countries may be subject to other regulations and policies and should be handled accordingly. Therefore, different privacy practices should be maintained in each country for different types of personal data.

[0279] Regardless of the foregoing, the present disclosure also contemplates implementation schemes in which users selectively block the use or access of personal information data. That is, the present disclosure contemplates that hardware elements and / or software elements may be provided to prevent or block access to such personal information data. For example, with respect to performing security operations (e.g., payment transactions), the technology of the present invention may be configured to allow users to choose to "opt in" or "opt out" to participate in the collection of personal information data during or at any time after the registration service. In another example, a user may choose to provide other information (e.g., such as a password) to use an electronic device to perform one or more security operations. In yet another example, a user may choose to limit the length of time to maintain the collected data (e.g., biometric data) or completely prohibit authorization of operations based on the collected data. In addition to providing "opt in" and "opt out" options, the present disclosure contemplates providing notifications related to access or use of personal information. For example, a user may be notified that their personal information data will be accessed when downloading an application, and then the user may be reminded again just before the personal information data is accessed by the application.

[0280] In addition, it is an object of the present disclosure that personal information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use. Risks can be minimized by limiting data collection and deleting data once it is no longer needed. In addition, and when applicable, including in certain health-related applications, data de-identification can be used to protect the privacy of users. De-identification can be facilitated by removing specific identifiers (e.g., date of birth, etc.), controlling the amount or specificity of stored data (e.g., collecting location data at the city level rather than at the address level), controlling how data is stored (e.g., aggregating data between users), and / or other methods when appropriate.

[0281] Thus, 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 also be implemented without access to such personal information data. That is, various embodiments of the present technology will not fail to function properly due to the lack of all or a portion of such personal information data. For example, security operations may be performed based on non-personal information data or an absolute minimum amount of personal information (such as content requested by a device associated with a user, other non-personal information available to an authorization system, or publicly available information).

Claims

1. A method comprising: At a computer system in communication with an external automobile head unit including one or more input components, the computer system communicates with an external receiving device: receiving, from the external automobile head unit, first data corresponding to input received at the one or more input components of the external automobile head unit, The first data corresponds to a request to perform a first transfer operation from the first account to a second account using an application on the computer system associated with the first account; as well as In response to receiving the first data, a process is initiated to perform the first transfer operation using the application on the computer system, wherein performing the first transfer operation includes transmitting second data including information identifying the first account to the external receiving device. 2 . The method of claim 1 , wherein the application is configured to perform a transfer operation from the first account before receiving the first data.

3. The method according to claim 1, wherein a second application different from the application is installed on the computer system: In accordance with the second application being configured to perform a transfer operation from a third account, the second application being configured to perform a transfer operation in response to a request received from the external automobile head unit to perform a transfer operation from the third account; and According to the second application not being configured to perform a transfer operation from a third account, wherein the second application is not configured to perform a transfer operation in response to a request received from the external automobile head unit to perform a transfer operation from the third account.

4. The method according to claim 3, wherein the second application is configured to perform a transfer operation from the third account, the method further comprising: receiving, from the external automobile head unit, third data corresponding to input received at the one or more input components of the external automobile head unit, the third data corresponding to a request to perform a second transfer operation from the third account to a fourth account using the second application; as well as In response to receiving the third data, a process of performing the second transfer operation using the second application is initiated, wherein performing the second transfer operation includes transmitting fourth data including information identifying the third account to the external receiving device.

5. The method of claim 1, wherein the computer system is in communication with a display generation component, and wherein the display generation component is in a locked state when the computer system receives the first data.

6. The method of claim 1, wherein the external automobile head unit has been authorized to request a transfer operation from the first account.

7. The method according to claim 6, further comprising: Prior to detecting the first data, receiving a first set of one or more inputs; as well as In response to the first set of one or more inputs: authorizing connection of the external automobile head unit to the computer system while the computer system is in a locked state; as well as The external automobile head unit is authorized to request a transfer operation from the first account.

8. The method according to claim 6, further comprising: receiving a second set of one or more inputs while the computer system is in communication with the external automobile head unit and while the computer system is in a locked state; as well as In response to the second set of one or more inputs: converting the computer system to an unlocked state; as well as The external automobile head unit is authorized to request a transfer operation from the first account.

9. The method according to claim 1, further comprising: Prior to receiving the first data, fifth data is transmitted to the external automobile head unit including one or more user interface elements to be displayed by the external automobile head unit.

10. The method of claim 1, wherein the computer system is a smartphone including a hardware security element, and wherein the information identifying the first account is stored in the hardware security element.

11. The method according to claim 1, further comprising: When the computer system is in communication with a second external automobile head unit including one or more input components and a second external receiving device, wherein the second external automobile head unit is different from the external automobile head unit: receiving, from the second external automobile head unit, sixth data corresponding to input received at the one or more input components of the second external automobile head unit, the sixth data corresponding to a request to use the application to perform a third transfer operation from the first account to a fifth account; as well as In response to receiving the sixth data, a process is initiated to perform the third transfer operation using the application on the computer system, wherein performing the third transfer operation includes transmitting seventh data including information identifying the first account to the second external receiving device.

12. A computer-readable storage medium storing one or more programs configured to be executed by one or more processors of a computer system that communicates with an external automobile head unit including one or more input components and communicates with an external receiving device, the one or more programs including instructions for executing the method according to any one of claims 1 to 11.

13. A computer system configured to communicate with an external automobile head unit comprising one or more input components, wherein the computer system is configured to communicate with an external receiving device, the computer system comprising: one or more processors; and A memory storing one or more programs configured to be executed by the one or more processors, the one or more programs comprising instructions for executing the method according to any one of claims 1 to 11.

14. A computer system configured to communicate with an external automobile head unit comprising one or more input components, wherein the computer system is configured to communicate with an external receiving device, the computer system comprising: Device for carrying out the method according to any one of claims 1 to 11.

15. A computer program product comprising one or more programs configured to be executed by one or more processors of a computer system communicating with an external automobile head unit comprising one or more input components and with an external receiving device, the one or more programs comprising instructions for executing the method according to any one of claims 1 to 11.

16. A method for providing an option to initiate a security operation, the method comprising: At the Computer Systems Department: receiving, while the computer system is connected to an external input device, a first request from the external input device to interact with a first portion of a user interface associated with a secure transaction; as well as In response to receiving the first request: providing, based on determining that the external input device satisfies a set of authorization criteria, an option to initiate a secure transaction via the external input device without requiring separate authorization from the user; as well as Based on determining that the external input device does not satisfy the set of authorization criteria, abandoning the option of initiating a secure transaction without requiring the separate authorization from the user, and providing a second option of initiating the secure transaction at the external input device and / or the computer system that requires separate authorization from the user.