Digital identification credential user interface

Abstract

The present disclosure generally relates to a digital identification credential user interface. A first application provides a request for digital identification information. A second application receives user input and, in response, provides the digital identification information to the first application.

Description

[0001] This application is a divisional application of the Chinese patent application with an application date of June 1, 2023, application number 202380044809.1, and invention name “Digital Identity Credential User Interface”. The Chinese patent application claims the benefits of U.S. Provisional Application No. 63 / 349,071 filed on June 4, 2022 and U.S. Patent Application No. 18 / 204,334 filed on May 31, 2023. Technical Field

[0002] The present disclosure relates generally to computer user interfaces and, more particularly, to techniques for managing and using digital credentials, including digital identity credentials. Background Art

[0003] As electronic devices such as smart phones become more and more widely used, their functionality has expanded beyond phone calls and text messages. Providing efficient methods for using and implementing various functions on these electronic devices can be complex and time consuming. Summary of the invention

[0004] However, some techniques for managing and using digital credentials using electronic devices are often cumbersome and inefficient. For example, some prior art techniques use complex and time-consuming user interfaces that may include multiple keystrokes or keystrokes. Prior art techniques require more time than necessary, which results in wasted user time and device energy. This latter consideration is particularly important in battery-powered devices.

[0005] Thus, the present technology provides electronic devices with faster, more efficient methods and interfaces for managing and using digital credentials. Such methods and interfaces optionally supplement or replace other methods for managing and using digital credentials. Such methods and interfaces reduce the cognitive burden imposed on users and produce more efficient human-computer interfaces. For battery-powered computing devices, such methods and interfaces save power and increase the time interval between battery charges.

[0006] According to some embodiments, a method is described. The method includes: at a computer system in communication with a display generation component and one or more input devices: displaying a first user interface corresponding to a first application via the display generation component; receiving a request for a digital identification of a user from the first application; in response to receiving the request for a digital identification of a user from the first application: displaying a second user interface corresponding to a second application different from the first application via the display generation component, wherein the second application has access to a first set of digital identification information corresponding to the user; while displaying the second user interface, receiving a first set of user input via the one or more input devices; and in response to receiving the first set of user input: providing a first subset of the first set of digital identification information corresponding to the user to the first application based on determining that the first set of user input meets authorization criteria.

[0007] 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 that are configured to be executed by one or more processors of a computer system that communicates with a display generation component and one or more input devices, and the one or more programs include instructions for the following operations: displaying a first user interface corresponding to a first application via the display generation component; receiving a request for a digital identification of a user from the first application; in response to receiving the request for a digital identification of a user from the first application: displaying a second user interface corresponding to a second application different from the first application via the display generation component, wherein the second application has access to a first set of digital identification information corresponding to the user; when displaying the second user interface, receiving a first set of user inputs via the one or more input devices; and in response to receiving the first set of user inputs: providing the first application with a first subset of the first set of digital identification information corresponding to the user based on determining that the first set of user inputs meets the authorization criteria.

[0008] According to some embodiments, a transient computer-readable storage medium is described. The transient computer-readable storage medium stores one or more programs that are configured to be executed by one or more processors of a computer system that communicates with a display generation component and one or more input devices, and the one or more programs include instructions for the following operations: displaying a first user interface corresponding to a first application via the display generation component; receiving a request for a digital identification of a user from the first application; in response to receiving the request for a digital identification of a user from the first application: displaying a second user interface corresponding to a second application different from the first application via the display generation component, wherein the second application has access to a first set of digital identification information corresponding to the user; when displaying the second user interface, receiving a first set of user inputs via the one or more input devices; and in response to receiving the first set of user inputs: providing the first application with a first subset of the first set of digital identification information corresponding to the user based on determining that the first set of user inputs meets the authorization criteria.

[0009] According to some embodiments, a computer system is described. The computer system is configured to communicate with a display generation component and one or more input devices, and 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 including instructions for the following operations: displaying a first user interface corresponding to a first application via the display generation component; receiving a request for a digital identification of a user from the first application; in response to receiving the request for a digital identification of a user from the first application: displaying a second user interface corresponding to a second application different from the first application via the display generation component, wherein the second application has access to a first set of digital identification information corresponding to the user; when displaying the second user interface, receiving a first set of user inputs via the one or more input devices; and in response to receiving the first set of user inputs: providing the first application with a first subset of the first set of digital identification information corresponding to the user based on determining that the first set of user inputs meets the authorization criteria.

[0010] According to some embodiments, a computer system is described. The computer system is configured to communicate with a display generation component and one or more input devices, and includes: a component for displaying a first user interface corresponding to a first application via the display generation component; a component for receiving a request for a digital identification of a user from the first application; a component for performing the following operations in response to receiving the request for the digital identification of the user from the first application: displaying a second user interface corresponding to a second application different from the first application via the display generation component, wherein the second application has access to a first set of digital identification information corresponding to the user; a component for receiving a first set of user inputs via the one or more input devices when displaying the second user interface; and a component for performing the following operations in response to receiving the first set of user inputs: providing a first subset of the first set of digital identification information corresponding to the user to the first application based on determining that the first set of user inputs meets authorization criteria.

[0011] According to some embodiments, a computer program product is described. The computer program product includes one or more programs configured to be executed by one or more processors of a computer system in communication with a display generation component and one or more input devices, the one or more programs including instructions for the following operations: displaying a first user interface corresponding to a first application via the display generation component; receiving a request for a digital identification of a user from the first application; in response to receiving the request for a digital identification of a user from the first application: displaying a second user interface corresponding to a second application different from the first application via the display generation component, wherein the second application has access to a first set of digital identification information corresponding to the user; when displaying the second user interface, receiving a first set of user inputs via the one or more input devices; and in response to receiving the first set of user inputs: providing a first subset of the first set of digital identification information corresponding to the user to the first application based on determining that the first set of user inputs meets the authorization criteria.

[0012] 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.

[0013] Thus, faster, more efficient methods and interfaces for managing and using digital credentials are 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 and using digital credentials. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] 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 drawings.

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

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

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

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

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

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

[0021] Figure 5A Personal electronic devices according to some embodiments are illustrated.

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

[0023] FIG. 6A to FIG. 6S An exemplary user interface for using and managing digital identification credentials according to some embodiments is illustrated.

[0024] Figure 7 A flowchart depicting a method for using digital identification credentials according to some embodiments is illustrated. DETAILED DESCRIPTION

[0025] 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.

[0026] There is a need for electronic devices that provide efficient methods and interfaces for managing and using digital credentials. For example, there is a need for technologies that provide a secure way to use and manage digital credentials while minimizing unnecessary manual effort caused by users to manage and use digital credentials. Such technologies can reduce the cognitive burden on users using digital credentials, thereby increasing productivity. In addition, such technologies can reduce processor power and battery power that would otherwise be wasted on redundant user input.

[0027] 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 using and managing digital credentials is provided. FIG. 6A to FIG. 6S An exemplary user interface for using and managing digital identification credentials according to some embodiments is illustrated. Figure 7 A flowchart illustrating a method of using digital identification credentials according to some embodiments. FIG. 6A to FIG. 6S The user interface in is used to illustrate the process described below, including Figure 7 process.

[0028] 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.

[0029] 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.

[0030] Although the following description uses the terms "first", "second", etc. to describe various elements, these elements should not be limited by the terms. In some embodiments, these terms are 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. In some embodiments, the first touch and the second touch are two separate references to the same touch. In some embodiments, both the first touch and the second touch are touches, but they are not the same touch.

[0031] 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 terms "including" and / or "comprising" when used in this specification specify the presence of stated features, integers, steps, operations, elements and / or components, but do not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components and / or their grouping.

[0032] 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.

[0033] Embodiments of electronic devices, user interfaces for such devices, and associated processes for using such devices are described herein. In some embodiments, the device is a portable communication device, such as a mobile phone, that also includes other functions, such as a PDA and / or a music player function. Exemplary embodiments of portable multifunction devices include, but are not limited to, the Apple Watch from Apple Inc. of Cupertino, California. Devices, iPod Equipment and Device. Other portable electronic devices are optionally used, such as laptop computers 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 sending 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).

[0034] 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 may optionally include one or more other physical user interface devices, such as a physical keyboard, mouse, and / or joystick.

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

[0036] 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 various applications with a user interface that is intuitive and clear to the user.

[0037] Attention is now turned to embodiments of portable devices having touch-sensitive displays. Figure 1A 1 is a block diagram illustrating a portable multifunction device 100 with a touch-sensitive display system 112 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.

[0038] 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 embodiments, force measurements from multiple force sensors are combined (e.g., weighted averaged) to determine an estimated contact force. Similarly, the pressure-sensitive tip of a stylus is optionally used to determine the pressure of the stylus on the touch-sensitive surface. Alternatively, the size of the contact area detected on the touch-sensitive surface and / or its change, the capacitance of the touch-sensitive surface near the contact and / or its change, and / or the resistance of the touch-sensitive surface near the contact and / or its change are optionally used as a substitute for the force or pressure of the contact on the touch-sensitive surface. In some embodiments, the substitute measurement of the contact force or pressure is used directly to determine whether the intensity threshold has been exceeded (e.g., the intensity threshold is described in units corresponding to the substitute measurement). In some embodiments, the substitute measurement of the contact force or pressure is converted into an estimated force or pressure, and the estimated force or pressure is used to determine whether the intensity threshold has been exceeded (e.g., the intensity threshold is a pressure threshold measured in units of pressure). Using the intensity of the contact as an attribute of the user input allows the user to access additional device functions that would otherwise be inaccessible to the user on a smaller device with limited real estate, which is used to display an enable indication (e.g., on a touch-sensitive display) and / or receive user input (e.g., via a touch-sensitive display, a touch-sensitive surface, or a physical control / mechanical control, such as a knob or button).

[0039] 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 surface that is sensitive to touch by a user (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 that corresponds to a perceived change in a physical property of the device or a component of the device. For example, movement of a touch-sensitive surface (e.g., a touch-sensitive display or trackpad) is optionally interpreted by the user as a "press click" or "release click" to a physical actuation button. In some cases, the user will feel a tactile sensation, such as a "press click" or "release click", even when the physical actuation button associated with the touch-sensitive surface that is physically pressed (e.g., displaced) by the user's movement does not move. As another example, movement of a touch-sensitive surface may optionally be interpreted or sensed by a user as "roughness" of the touch-sensitive surface even when there is no change in the smoothness of the touch-sensitive surface. While such 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.

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

[0041] 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.

[0042] 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 (such as computer programs (e.g., including instructions)) 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.

[0043] RF (radio frequency) circuit 108 receives and transmits 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 may optionally use any of a variety of communication standards, protocols and technologies, including, but not limited to, Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), High Speed ​​Downlink Packet Access (HSDPA), High Speed ​​Uplink Packet Access (HSUPA), Evolution, Data-Only (EV-DO), HSPA, HSPA+, Dual Cell HSPA (DC-HSPDA), Long Term Evolution (LTE), Near Field Communication (NFC), Wideband Code Division Multiple Access (W-CDMA), Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Bluetooth, Bluetooth Low Energy (BTLE), Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11d), IEEE 802.11e, IEEE 802.11f, IEEE 802.11g, IEEE 802.11g). 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.

[0044] 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 sends 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 sends the audio data to the peripheral device interface 118 for processing. The audio data is optionally retrieved from and / or sent 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).

[0045] 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 / transmit electrical signals from / to 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 and / or air 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. In some embodiments, an air gesture is a gesture that is detected without the user touching an input element that is part of the device (or is independent of an input element that is part of the device) and is based on detected movement of a part of the user's body through the air, including movement of the user's body relative to an absolute reference (for example, the angle of the user's arm relative to the ground or the distance of the user's hand relative to the ground), movement relative to another part of the user's body (for example, movement of the user's hand relative to the user's shoulder, movement of one of the user's hands relative to the user's other hand, and / or movement of the user's fingers relative to another finger or part of the user's hand), and / or absolute movement of a part of the user's body (for example, a tap gesture involving a hand moving a predetermined amount and / or speed in a predetermined position, or a shake gesture involving a predetermined speed or amount of rotation of a part of the user's body).

[0046] 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," 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.

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

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

[0049] 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 iPod Touch from Apple Inc. of Cupertino, California. and iPod The technology used in

[0050] 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.

[0051] The touch-sensitive display in some embodiments of the touch screen 112 is described in the following applications: (1) U.S. patent application No. 11 / 381,313, filed on May 2, 2006, "Multipoint Touch Surface Controller"; (2) U.S. patent application No. 10 / 840,862, filed on May 6, 2004, "Multipoint Touchscreen"; (3) U.S. patent application No. 10 / 903,964, filed on July 30, 2004, "Gestures For Touch Sensitive Input Devices"; (4) U.S. patent application No. 11 / 048,264, filed on January 31, 2005, "Gestures For Touch Sensitive Input Devices"; (5) U.S. patent application No. 11 / 038,590, filed on January 18, 2005, "Mode-Based Graphical User Interfaces For Touch Sensitive Input Devices”; (6) U.S. patent application No. 11 / 228,758, filed on September 16, 2005, “Virtual Input Device Placement On A Touch Screen User Interface”; (7) U.S. patent application No. 11 / 228,700, filed on September 16, 2005, “Operation Of A Computer With A Touch Screen Interface”; (8) U.S. patent application No. 11 / 228,737, filed on September 16, 2005, “Activating Virtual Keys Of A Touch-Screen Virtual Keyboard”; and (9) U.S. patent application No. 11 / 367,749, filed on March 3, 2006, “Multi-Functional Hand-Held Device”. All of these applications are incorporated herein by reference in their entirety.

[0052] 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 positioning or commands for performing the actions desired by the user.

[0053] 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 separate from the touch screen 112, or an extension of the touch-sensitive surface formed by the touch screen.

[0054] 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.

[0055] 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 a 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 image of the user can be optionally obtained for video conferencing when the user views other video conference participants on the touch screen display. In some embodiments, the positioning 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.

[0056] 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 positioning 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.

[0057] 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.

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

[0059] Device 100 optionally also includes one or more tactile output generators 167 . Figure 1AA tactile output generator coupled to a tactile feedback controller 161 in the I / O subsystem 106 is shown. 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 juxtaposition or proximity 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.

[0060] 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 U.S. Patent Publication Nos. 20050190059, entitled "Acceleration-based TheftDetection System for Portable Electronic Devices" and 20060017692, entitled "Methods And Apparatuses For Operating A Portable Device Based On AnAccelerometer", 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.

[0061] 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: active application state, which indicates which application (if any) is currently active; display state, which indicates what applications, views, or other information occupy various areas of the touch screen display 112; sensor state, including information obtained from the device's various sensors and input control devices 116; and position information related to the device's position and / or posture.

[0062] 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.

[0063] 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.

[0064] 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.

[0065] In some embodiments, the contact / motion module 130 uses a set of one or more intensity thresholds to determine whether an action has been performed by 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. Additionally, 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).

[0066] 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). Thus, 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.

[0067] 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.

[0068] 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 or the like, along with coordinate data and other graphic attribute data if necessary, and then generates screen image data to be output to the display controller 156.

[0069] 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 .

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

[0071] 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).

[0072] The application 136 may optionally include the following modules (or instruction sets) or a subset or superset thereof:

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

[0074] ● Telephone module 138;

[0075] ● Video conferencing module 139;

[0076] ● Email client module 140;

[0077] ●Instant messaging (IM) module 141;

[0078] ●Fitness support module 142;

[0079] ● Camera module 143 for still images and / or video images;

[0080] ●Image management module 144;

[0081] ●Video player module;

[0082] ●Music player module;

[0083] ●Browser module 147;

[0084] ●Calendar module 148;

[0085] 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;

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

[0087] ●Search module 151;

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

[0089] ●Note module 153;

[0090] ● Map module 154; and / or

[0091] ●Online video module 155.

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

[0093] In combination with the touch screen 112, display controller 156, touch / motion module 130, graphics module 132 and text input module 134, the contact module 137 is optionally used to manage an address book or contact list (for example, 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.

[0094] 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 noted above, wireless communications optionally use any of a variety of communication standards, protocols, and technologies.

[0095] 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.

[0096] 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, transmitting, 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 transmit emails with still images or video images captured by camera module 143.

[0097] In conjunction with the RF circuit 108, the touch screen 112, the display controller 156, the contact / motion module 130, the graphics module 132, and the text input module 134, the instant messaging module 141 includes executable instructions for the following operations: inputting a character sequence corresponding to an instant message, modifying previously input characters, sending a corresponding instant message (e.g., using a short message service (SMS) or multimedia message service (MMS) protocol for telephone-based instant messaging or using XMPP, SIMPLE, or IMPS for Internet-based instant messaging), receiving instant messages, and viewing received instant messages. In some embodiments, the instant messages sent and / or received may 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 telephone-based messages (e.g., messages transmitted using SMS or MMS) and Internet-based messages (e.g., messages transmitted using XMPP, SIMPLE, or IMPS).

[0098] In 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 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 sending fitness data.

[0099] 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.

[0100] 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.

[0101] 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.

[0102] 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.

[0103] 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).

[0104] 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).

[0105] 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.

[0106] 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.).

[0107] 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.

[0108] 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 related to stores and other points of interest at or near a particular location, and other location-based data) in accordance with user instructions.

[0109] 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 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 may 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.

[0110] 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.

[0111] 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.

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

[0113] Figure 1B 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).

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

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

[0116] Event monitor 171 receives event information from peripherals interface 118. Event information includes information about sub-events (e.g., a user touch on touch-sensitive display 112 as part of a multi-touch gesture). Peripherals interface 118 sends 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.

[0117] In some embodiments, event monitor 171 transmits a request to peripheral device interface 118 at predetermined intervals. In response, peripheral device interface 118 sends event information. In other embodiments, peripheral device interface 118 sends 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).

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

[0119] 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.

[0120] 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 that are recognized as correct input is optionally determined based at least in part on the hit view of the initial touch that started the touch-based gesture.

[0121] 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 that should handle the sub-events. 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 is identified as the hit view.

[0122] 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.

[0123] 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.

[0124] 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.

[0125] 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 191 include one or more corresponding event handlers 190. In addition, in some embodiments, one or more of the data updater 176, the object updater 177, and the GUI updater 178 are included in the corresponding application view 191.

[0126] 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).

[0127] 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 rate 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).

[0128] 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 sub-event sequence), such as event 1 (187-1), event 2 (187-2), and others. In some embodiments, sub-events in events (e.g., 187-1 and / or 187-2) 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.

[0129] In some embodiments, event definition 186 includes a definition of an event for a corresponding user interface object. 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.

[0130] 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.

[0131] 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.

[0132] 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.

[0133] 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 transmitting (and deferred transmission) 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 executes a predefined process.

[0134] 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 executes a predetermined process.

[0135] 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 positioning of user interface objects. GUI updater 178 updates the GUI. For example, GUI updater 178 prepares display information and transmits the display information to graphics module 132 for display on a touch-sensitive display.

[0136] 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.

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

[0138] Figure 2A portable multifunction device 100 with a touch screen 112 according to some embodiments is illustrated. 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, the gesture optionally includes one or more taps, one or more swipes (from left to right, from right to left, up and / or down) and / or 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.

[0139] 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.

[0140] 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.

[0141] 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 computer, a desktop computer, a tablet computer, a multimedia player device, a navigation device, an educational device (such as a children's learning toy), a game system, or a control device (e.g., a home controller or an industrial controller). 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 chipsets) 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), the sensor 359 (e.g., an optical sensor, an acceleration sensor, a proximity sensor, a touch sensitive sensor, and / or a contact intensity sensor (similar to the above reference Figure 1A Memory 370 may include high-speed random access memory, such as DRAM, SRAM, DDR RAM, or other random access solid-state memory devices; and may optionally include non-volatile memory, such as one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid-state storage devices. Memory 370 may optionally include one or more storage devices located away from CPU 310. In some embodiments, memory 370 stores data related to portable multifunction device 100 ( Figure 1A ) or a subset thereof. In addition, memory 370 optionally stores additional programs, modules, and data structures that are 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.

[0142] 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 the instruction set for performing the function described above. 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 the subsets of the above-mentioned modules and data structures. In addition, memory 370 optionally stores additional modules and data structures not described above.

[0143] Attention is now turned to embodiments of a user interface that may optionally be implemented on, for example, portable multifunction device 100 .

[0144] Figure 4A An exemplary user interface of an application menu on portable multifunction device 100 according to some embodiments is illustrated. 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:

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

[0146] ●Time 404;

[0147] ●Bluetooth indicator 405;

[0148] ●Battery status indicator 406;

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

[0150] 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;

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

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

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

[0154] ● Icons for other apps, such as:

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

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

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

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

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

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

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

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

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

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

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

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

[0167] It should be noted that Figure 4A The illustrated icon labels are exemplary only. For example, the icon 422 of the video and music player module 152 is labeled "Music" or "Music Player". Other labels may be used for various application icons. In some embodiments, the label of the 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.

[0168] Figure 4B The example embodiment has a touch-sensitive surface 451 (eg, touch screen display 112) that is separate from a display 450 (eg, touch screen display 112). Figure 3 A device (e.g., a tablet computer or touch pad 355) 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.

[0169] 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.

[0170] Additionally, 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 a 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 mice and finger contacts are optionally used simultaneously.

[0171] Figure 5AAn exemplary personal electronic device 500 is illustrated. 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. Alternatively, or in addition to touch screen 504, device 500 also 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 intensity sensors for detecting the intensity of contact (e.g., touch) applied. One or more intensity 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.

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

[0173] 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.

[0174] Figure 5B An exemplary personal electronic device 500 is depicted. In some embodiments, the device 500 may include a Figure 1A , Figure 1B and Figure 3 Some or all of the components described. Device 500 has a bus 512 that operatively couples an I / O portion 514 to one or more computer processors 516 and a memory 518. I / O portion 514 may be connected to a display 504, which may have a touch-sensitive component 522 and optionally a strength sensor 524 (e.g., a contact strength 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 may be optionally a rotatable input device or a depressible input device and a rotatable input device. In some examples, input mechanism 508 may be optionally a button.

[0175] 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.

[0176] 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 process 700 ( Figure 7). 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.

[0177] As used herein, the term "indicative representation" refers to an optional feature of the device 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) may each optionally constitute an affordance.

[0178] As used herein, the term "focus selector" refers to an input element used to indicate the current portion of a user interface that a user is interacting with. 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).

[0179] 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 may optionally include a first strength threshold and a second strength threshold. In this example, a contact whose feature strength does not exceed the first threshold results in a first operation, a contact whose feature strength exceeds the first strength threshold but does not exceed the second strength threshold results in a second operation, and a contact whose feature strength exceeds the second threshold results in a third operation. In some embodiments, a comparison between the feature strength and one or more thresholds is used to determine whether to perform one or more operations (e.g., whether to perform the corresponding operation or to abandon the corresponding operation) rather than to determine whether to perform the first operation or the second operation.

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

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

[0182] ● The active app currently displayed on the display of the device on which the app is being used;

[0183] ● Background applications (or background processes) that are not currently displayed but for which one or more processes are being processed by one or more processors; and

[0184] ●Not running but has data stored in memory (volatile and non-volatile respectively)

[0185] A suspended or dormant application that contains status information that can be used to resume execution of the application.

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

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

[0188] FIG. 6A to FIG. 6S Illustrated are exemplary user interfaces for using and managing digital identity credentials according to some embodiments. The user interfaces in these figures are used to illustrate the processes described below, including Figure 7 process.

[0189] Fig. 6AAn electronic device 600 is depicted that is a smartphone with a touch-sensitive display 602 and a button 604. In some embodiments, the electronic device 600 includes one or more features of the devices 100, 300, and / or 500. The electronic device 600 depicts a wallet user interface 606. The wallet user interface 606 includes representations 608a to 608f of digital credentials stored on the electronic device 600 (e.g., in a secure element of the electronic device 600). The digital credential representations 608a to 608f include digital payment credential representations 608a to 608c (e.g., digital credentials that can be used to pay for goods and services) and digital access credential representations 608e to 608f (e.g., digital credentials that can be used to obtain access rights for goods and services (such as flights, events, etc.) for a user. The digital credential representations 608a to 608f also include a digital identification credential representation 608d representing a first digital identification credential (e.g., an Arizona ID card). The digital identification credential representation 608d is associated with identification information about an individual and / or user and, in some embodiments, can be used to verify identification information about the user (e.g., name, age, gender, address, and / or state of residence). In some embodiments, the digital identification credential representation 608d does not represent a payment credential (e.g., not a credit card credential, a debit card credential, and / or a gift card credential). The wallet user interface 606 also includes an option 610 that can be selected to initiate a process of adding a new digital credential to the electronic device 600 (e.g., registering a new digital credential and / or storing a new digital credential on the electronic device 600).

[0190] exist Figure 6B, the electronic device 600 depicts a food delivery user interface 612 corresponding to a food delivery application (e.g., generated and / or displayed by the food delivery application). The food delivery user interface 612 identifies one or more items that the user of the electronic device 600 is attempting to purchase. The electronic device 600 and / or the food delivery application determine that there are one or more items in the user's order that require the user to be over 21 years old and therefore require verification of the user's age. Therefore, the food delivery user interface 612 includes an option 614a that can be selected to use a wallet application (e.g., a wallet application separate from the food delivery application) to verify the user's age, and the wallet application has access to one or more digital identification credentials stored on the electronic device 600. In some embodiments, the wallet application has access to one or more digital identification credentials stored on the electronic device 600, and the food delivery application does not have access to one or more digital identification credentials stored on the electronic device 600. The food delivery user interface 612 also includes an option 614b that can be selected to use a different method (e.g., not using and / or not calling the wallet application and / or not using one or more digital identification credentials stored on the electronic device 600) to verify the user's age. For example, in some embodiments, option 614b can be selected to initiate a process for verifying the user's age based on a method provided by the food delivery application without using the wallet application and / or one or more digital identification credentials registered on the electronic device 600. The food delivery user interface 612 also includes option 614c, which can be selected to cancel the food purchase transaction. Fig. 6A At , the electronic device 600 detects a user input 616 (eg, a tap input) corresponding to the selection of option 614a.

[0191] exist Figure 6C At , in response to user input 616 (and / or in response to a request from a food delivery application), the electronic device 600 displays a user interface 618. Figure 6C, user interface 618 is overlaid on user interface 612. In some embodiments, in response to user input 616, while user interface 618 is overlaid on user interface 612, user interface 612 visually reduces emphasis (e.g., is displayed with lower saturation, lower brightness, and / or lower sharpness and / or focus (e.g., blurred)). In some embodiments, user interface 618 is generated and / or displayed by the wallet application and / or the operating system of the electronic device 600, and is not generated and / or displayed by the food delivery application. User interface 618 includes entity information 620a, which identifies the entity and / or application (e.g., the "food delivery" application) requesting digital identification credential information. User interface 618 also includes a digital identification credential indication 620b, which identifies a digital identification credential stored on the electronic device 600, which is the source of the digital identification credential information to be provided to the food delivery application (in the depicted scenario, the digital identification credential is an Arizona driver's license stored on the electronic device 600). The user interface 618 also includes a requested information indication 620c that identifies all digital identification credential information that the food delivery application is requesting. In the depicted scenario, the food delivery application is requesting: (1) verification that the user is over 21 years of age; (2) a photograph of the user associated with the digital identification credential; (3) a state associated with the digital identification credential; and the user's name (e.g., as presented and / or stored on the digital identification credential). All requested information corresponds to, is part of, and / or is stored as part of the digital identification credential. In some embodiments, the request to verify that the user is over 21 years of age is a request for the user's date of birth. In some embodiments, the request to verify that the user is over 21 years of age is a request for a binary determination of whether the user is over 21 years of age without providing the user's actual date of birth. The requested information indication 620c in the user interface 618 also indicates that all requested digital identification credential information will be stored by the food delivery application for 30 days.

[0192] The user interface 618 includes an indication 620e instructing the user to press the side button 604 if the user wishes to proceed with providing the requested digital identification credential information to the food delivery application. Figure 6C At , the electronic device 600 detects a user input 622 on the side button 604 (eg, a button press input or a button double press input).

[0193] exist Fig.6DAt, in response to user input 622, the electronic device 600 collects biometric information from the user, as indicated by indication 620f. For example, in some embodiments, the electronic device 600 collects facial scan information (e.g., collected via a camera 621 and / or a depth sensor of the electronic device 600). In some embodiments, the biometric information includes fingerprint scan information and / or eye scan information. In some embodiments, the digital identification credential is bound to a specific biometric profile (e.g., a facial scan profile, a fingerprint scan profile, and / or an eye scan profile) on the electronic device 600. Once the biometric information is collected from the user, the electronic device 600 determines whether the collected biometric information matches the specific biometric profile associated with the digital identification credential. In some embodiments, the electronic device 600 stores multiple biometric profiles corresponding to multiple users and / or multiple appearances of the same user. For example, the electronic device 600 stores a first biometric profile corresponding to a first user and a second biometric profile corresponding to a second user. Both users are authorized to use the electronic device 600, so both the first biometric profile and the second biometric profile can be used to perform one or more functions, such as unlocking the electronic device 600. However, if the first digital identification credential is bound to the first biometric profile but not to the second biometric profile (e.g., the first digital identification credential corresponds only to the first user and not to the second user), the user biometric information corresponding to (e.g., matches) the first biometric profile will authorize the sending of the digital identification credential information corresponding to the first digital identification credential, but the user biometric information corresponding to (e.g., matches) the second biometric profile will not authorize the sending of the digital identification credential information corresponding to the first digital identification credential. In some embodiments, the first digital identification credential may be bound only to a single biometric profile of the electronic device 600.

[0194] exist Fig. 6E , the electronic device 600 confirms that the biometric information collected from the user matches the biometric profile corresponding to the digital identification credential, and in response, displays an indication 620g. In addition, based on determining that the biometric information collected from the user matches the biometric profile corresponding to the digital identification credential, the wallet application provides the requested digital identification credential information corresponding to the digital identification credential to the food delivery application.

[0195] exist Fig. 6FIn the embodiment depicted, in response to the food delivery application receiving the requested digital identification credential information and confirming that the user is over 21 years of age, the user interface 612 displays options 624a and 624b that can be selected to complete payment for the food delivery order. In the depicted embodiment, option 624a can be selected to initiate a process for completing payment within the food delivery application, and option 624a can be selected to initiate a process for completing payment using a wallet application (e.g., using one or more digital payment credentials (e.g., digital payment credentials 608a to 608c) stored on the electronic device 600, which can be accessed by the wallet application but not by the food delivery application).

[0196] Figure 6G An alternative scenario is shown in which the electronic device 600 determines that the biometric information collected from the user does not match the biometric profile corresponding to the digital identification credential. In response to the determination, the electronic device 600 displays a user interface 626 that includes: an option 628a for retrying biometric authentication (e.g., option 628a can be selected to cause the electronic device 600 to collect second biometric information from the user and compare the second biometric information to the biometric profile associated with the digital identification credential); and an option 628b that can be selected to cancel and / or abandon providing the digital identification credential information to the food delivery application.

[0197] FIG. 6H to FIG. 6L A second example scenario involving an event franchise application is depicted. Figure 6H, the electronic device 600 depicts an event concession user interface 630 corresponding to the event concession application (e.g., generated and / or displayed by the event concession application). The event concession user interface 630 identifies one or more items that the user of the electronic device 600 is trying to purchase. The electronic device 600 and / or the event concession application determine that there are one or more items in the user's order that require the user to be over 21 years old, and therefore require verification of the user's age. Therefore, the event concession user interface 630 includes an option 632a, which can be selected to use a wallet application (e.g., a wallet application separate from the event concession application) to verify the user's age. In some embodiments, the wallet application has access to one or more digital identification credentials stored on the electronic device 600, while the event concession application does not have access to one or more digital identification credentials stored on the electronic device 600. The event concession user interface 630 also includes an option 632b, which can be selected to use a different method (e.g., not using and / or not calling the wallet application and / or not using one or more digital identification credentials stored on the electronic device 600) to verify the user's age. For example, in some embodiments, option 632b can be selected to initiate a process for verifying the user's age within the event concession application without using the wallet application and / or one or more digital identification credentials registered on the electronic device 600. Event concession user interface 630 also includes option 632c, which can be selected to cancel the purchase transaction. Figure 6H At , the electronic device 600 detects a user input 634 (eg, a tap input) corresponding to a selection of option 632a.

[0198] exist Fig.6I In response to the user input 634, the electronic device 600 displays a user interface 618 generated and / or displayed by the wallet application, as described above with reference to FIG. 6B to FIG. 6G discussed. Fig.6I , user interface 618 is overlaid on event concession user interface 630. In some embodiments, in response to user input 634, user interface 618 is visually reduced in emphasis (e.g., displayed with lower saturation, lower brightness, and / or lower sharpness and / or focus (e.g., blurred)) while user interface 630 is overlaid on user interface 630.

[0199] As discussed above, user interface 618 includes entity information 620a that identifies the entity and / or application (e.g., an “event concession” application) requesting the digital identification credential information. User interface 618 also includes a digital identification credential indication 620b that identifies a digital identification credential stored on electronic device 600 that is the source of the digital identification credential information to be provided to the event concession application (e.g., an Arizona driver’s license stored on electronic device 600). User interface 618 also includes a requested information indication 620c that identifies all of the information that the event concession application is requesting. Fig.6I In the scenario depicted in , the event concession application is requesting: (1) verification that the user is over 21 years of age; and (2) the state associated with the digital identification credential (e.g., the state that issued the digital identification credential). All of the requested information corresponds to, is part of, and / or is stored as part of the digital identification credential. User interface 618 also indicates that the information will be stored by the event concession application for 30 days. In addition, in Fig.6I In the example, user interface 618 also includes a second requested information indication 620h that identifies digital identification credential information that the event franchise application is requesting but will not be stored by the event franchise application, the digital identification credential information being stored in the event franchise application. Fig.6I For example, if the user consents to sending digital identification credential information to an event concession application, the wallet application will provide the event concession application with: confirmation that the user is over 21 years of age; the state associated with the user's digital identification credential; and the photo associated with the user's digital identification credential, and the event concession application will store the first two pieces of information for 30 days, but will not store the photo (e.g., the photo will be used for less than a threshold duration to confirm the user's identity for that transaction, but will not be stored after the user's identity is confirmed).

[0200] User interface 618 includes an indication 620e instructing the user to press (or double-press) side button 604 if the user wishes to proceed with providing the requested digital identification credential information to the event franchise application. Fig.6I At , the electronic device 600 detects user input 636 on the side button 604 (eg, a button press input or a button double press input).

[0201] exist Figure 6J At 630, in response to user input 636, electronic device 600 collects biometric information from the user, as indicated by indication 620f. Figure 6K, electronic device 600 confirms that the biometric information collected from the user matches the biometric profile corresponding to the digital identification credential, and in response, displays indication 620g. In addition, based on determining that the biometric information collected from the user matches the biometric profile corresponding to the digital identification credential, the wallet application provides the requested digital identification credential information corresponding to the digital identification credential to the event franchise application executed on electronic device 600.

[0202] exist Figure 6L In the embodiment, in response to the event concession application receiving the requested digital identification credential information and confirming that the user is over 21 years of age, the user interface 630 displays an option 638 that can be selected to initiate a process for completing payment for the concession order. In the depicted embodiment, option 638 can be selected to initiate a process for completing payment using a wallet application (e.g., using one or more digital payment credentials (e.g., digital payment credentials 608a-608c) stored on the electronic device 600, which can be accessed by the wallet application but not by the event concession application).

[0203] Although FIG. 6B to FIG. 6L Depicts two example scenarios in which a user uses digital identity credential information associated with a digital identity credential to proceed with a payment transaction, but Figure 6M A third scenario is depicted in which a user uses digital identification credentials to create an account for a child. In order to create an account for a child, the user must verify that the user is an adult (e.g., over 18 years old).

[0204] exist Figure 6M , the electronic device 600 displays a child account creation user interface 640 on the display 602. In the depicted scenario, the child account creation user interface 640 is associated with (e.g., generated and / or displayed by) a first application that is separate from a wallet application (e.g., a wallet application that has access to one or more digital identification credentials stored on the electronic device 600). The child account creation user interface 640 includes a first name field 642a, a last name field 642b, and a date of birth field 642c. In some embodiments, the first name field 642a, the last name field 642b, and the date of birth field 642c are initially displayed as incomplete, and the device 600 receives a set of one or more inputs (e.g., tap inputs) corresponding to selections of each field to present a keyboard and / or date selection affordance for completing each field. The child account creation user interface 640 also includes an option 642d that can be selected to cancel the creation of the child account and an option 642e that can be selected to initiate a process for verifying the user's age using one or more digital identification credentials stored on the electronic device 600. Figure 6MAt , the electronic device 600 detects a user input 644 (eg, a tap input) corresponding to the selection of option 642e.

[0205] exist Figure 6N In response to user input 644, the electronic device 600 displays a user interface 618, as described above with reference to FIG. 6B to FIG. 6L In Figure 6N , user interface 618 identifies "Computer Company" as the entity and / or application requesting digital identification credential information, such as Figure 6N 620a and includes a requested information indication 620h indicating that the computer company is requesting confirmation that the user is over 18 years of age and indicating that the information will not be stored by the computer company after verification of the user's age.

[0206] FIG. 6O to FIG. 6S Illustrate a sample user interface for managing digital identity credentials. Fig.6O In the embodiment, the electronic device 600 displays the wallet user interface 600, as described above with reference to Fig. 6A In Fig.6O , the electronic device detects user input 646 (e.g., a tap input) corresponding to a selection of representation 608d, which is a representation of a first digital identification credential (e.g., an Arizona driver's license / state ID).

[0207] exist Figure 6P At 646, in response to user input 646, electronic device 600 displays a digital credential details user interface 648 corresponding to representation 608d and the first digital identification credential. Digital credential details user interface 648 includes image 650, which is a representation of the first digital identification credential. Digital credential details user interface 648 also includes option 652b, which can be selected to view digital identification credential information (e.g., all digital identification credential information and / or a subset of digital identification credential information) associated with the first digital identification credential (e.g., an Arizona driver's license), as described below with reference to Figure 6Qwill be described in more detail. The digital credential details user interface 648 also includes representations 652c through 652f, which represent digital identification credential information sending instances in which a user previously consented to having the digital identification credential information sent to an application. For example, representation 652c corresponds to an instance in which digital identification credential information was sent to an event concession application, and identifies the specific digital identification credential information (e.g., verification that the user is over 21 years of age, photo ID, and state) that was sent to the event concession application in the sending instance (e.g., by a wallet application). Similarly, representation 652e corresponds to an instance in which digital identification credential information was sent to a food delivery application, and identifies the specific digital identification credential information (e.g., verification that the user is over 21 years of age, photo ID, state, and name) that was sent to the food delivery application (e.g., by a wallet application). Figure 6P At , the electronic device 600 detects user input 654a (e.g., a tap input) corresponding to selection of option 652b, user input 654b (e.g., a tap input) corresponding to selection of send instance representation 652c, and user input 654c (e.g., a tap input) corresponding to selection of send instance representation 652e.

[0208] exist Figure 6Q At 654a, in response to user input 654a, electronic device 600 displays digital identification credential user interface 656. In the depicted scenario, digital identification credential user interface 656 presents digital identification credential information (e.g., all digital identification credential information) corresponding to the digital identification credential (e.g., ID photo 658a, full name 658b, address 658c, date of birth 658d, gender 658e, height 658f, weight 658g, eye color 658h, hair color 658i, race 658j, organ donor status 658k, and / or veteran status 658l). Digital identification credential user interface 656 indicates FIG. 6B to FIG. 6G Food delivery applications, event concession applications 6H to 6L, and Figures 6M to 6N The computer company in only requests a small subset of the digital identification credential information associated with the first digital identification credential. Thus, in each of these scenarios, the wallet application only provides the requested digital identification credential information to the requesting entity / application, and does not provide any digital identification credential information stored on the first digital identification credential but not requested to the requesting entity / application.

[0209] exist Figure 6R At 654b, in response to user input 654b, electronic device 600 displays a send instance user interface 660-1 that provides the user with details about a particular send instance in which the digital identification credential information is sent to the application. Figure 6RIn the example, user interface 660-1 includes entity information 662b-1 identifying an entity and / or application that received digital identification credential information, location information 662c-1, 662h-1, 662i-1 corresponding to the sending instance (e.g., the sending occurred at 401 East Jefferson Street in Phoenix, Arizona), and date and time information 662d-1 corresponding to the sending instance (e.g., the sending occurred at 10:09 AM on March 1). User interface 660-1 also includes a digital identification credential indication 662e-1 identifying a first digital identification credential, requested and stored information 662f-1 (e.g., information provided to and stored by the application), and requested but not stored information 662g-1 (e.g., information provided to but not stored by the application). User interface 660-1 also includes option 662j-1, which can be selected to initiate a request for receiving a digital identification credential from Figure 6P The user interface 648 removes the sending instance information corresponding to the sending instance, thereby providing the user with increased privacy.

[0210] exist Figure 6S At 654c, in response to user input 654c, electronic device 600 displays a send instance user interface 660-2 that provides the user with details about a particular send instance in which the digital identification credential information is sent to the application. Figure 6S , user interface 660-2 includes entity information 662b-2 identifying the entity and / or application (e.g., a "food delivery" application) that received the digital identification credential information, and date and time information 662d-2 corresponding to the sending instance (e.g., the sending occurred at 10:09 AM on March 1). User interface 660-2 also includes a digital identification credential indication 662e-2 identifying the first digital identification credential, and requested and stored information 662f-2 (e.g., digital identification credential information provided to and stored by the application). User interface 660-2 also includes an option 662j-2 that can be selected to initiate a request for receiving the digital identification credential from the application. Figure 6P The user interface 648 is used to remove the sending instance information corresponding to the sending instance.

[0211] Figure 7Flowchart illustrating a method for managing and using digital identification credentials using a computer system according to some embodiments. Method 700 is performed at a computer system (e.g., 100, 300, 500, and / or 600) that communicates with a display generation component (e.g., a display controller, a touch-sensitive display system; a head-mounted display system; and / or a display (e.g., integrated and / or connected)) and one or more input devices (e.g., a touch-sensitive surface (e.g., a touch-sensitive display); an accelerometer; a rotatable input mechanism; a pressable input mechanism; and / or a rotatable and pressable input mechanism) (e.g., a wearable device, a smart watch, a smart phone, a tablet computer, a head-mounted device (e.g., a head-mounted augmented reality and / or extended reality device), and / or a computer system that controls an external display). Some operations in method 700 are optionally combined, the order of some operations is optionally changed, and some operations are optionally omitted.

[0212] As described below, method 700 provides an intuitive way to use and manage digital identification credentials. The method reduces the cognitive burden on users to use and manage digital identification credentials, thereby creating a more efficient human-computer interface. For battery-powered computing devices, users are enabled to use and manage digital identification credentials faster and more efficiently, thereby saving power and increasing the time between battery charges.

[0213] A computer system (e.g., 600) displays (702) a first user interface (e.g., 612, 630, 640) corresponding to a first application (e.g., a first application and / or a third-party application running on the computer system) (e.g., a first user interface generated by the first application) via a display generation component (e.g., 602).

[0214] The computer system receives (704) a request for a digital identification of a user from a first application. In some embodiments, the request for a digital identification is initiated and / or generated by the first application.

[0215] In response to (708) receiving a request for a digital identification of a user from a first application: the computer system (e.g., 600), via a display generation component (e.g., 602), displays (708) a second user interface (e.g., 618) corresponding to a second application (e.g., a second application running on the computer system) that is different from the first application (e.g., a wallet application and / or a digital identification application) (e.g., a first-party application, an application provided by a manufacturer of the computer system, and / or an application that is part of an operating system), wherein the second application has access to (e.g., is authorized to access and / or store) a first set of digital identification information corresponding to the user (e.g., Figure 6R, information corresponding to digital identification credential 608d) (e.g., digital identification credential 608d). In some embodiments, a second user interface (e.g., 618) is displayed while maintaining display of at least a portion of a first user interface (e.g., 612, 630, 640) (e.g., the second user interface is displayed concurrently with at least a portion of the first user interface). In some embodiments, the second user interface covers at least a portion of the first user interface. In some embodiments, the digital identification information (e.g., a first set of digital identification information corresponding to a user) corresponds to a digital identification account (e.g., digital identification credential 608d) stored as part of an electronic wallet (e.g., storing the digital identification information / credentials in a secure element of a computer system). The digital identification account does not include payment information (e.g., not a debit card, credit card, or payment card). The electronic wallet stores one or more other accounts corresponding to a payment account (e.g., 608a to 608c) (e.g., a debit card, a credit card, and / or a payment card). The digital identification information corresponds to a government-issued identification account.

[0216] While displaying the second user interface (e.g., 618), the computer system receives (710) a first set of user inputs (e.g., 622 and / or 636) (e.g., one or more user inputs) (e.g., one or more button presses, one or more touch inputs, one or more biometric inputs (e.g., a facial scan, an eye scan, and / or a fingerprint scan)) via one or more input devices.

[0217] In response to (712) receiving a first set of user input (e.g., 622 and / or 636): based on determining that the first set of user input meets authorization criteria, the computer system provides (714) to the first application a first subset of the first set of digital identification information corresponding to the user (e.g., 620c and / or 620h) (e.g., the first subset includes all of the first set of digital identification information corresponding to the user, or the first subset includes less than all of the first set of digital identification information corresponding to the user (e.g., providing the first subset without providing a second subset of the first set of digital identification information corresponding to the user)).

[0218] In some embodiments, in response to receiving the first set of user input (e.g., 622, 636), and based on determining that the first set of user input does not satisfy the authorization criteria, the computer system forgoes providing the first application with a first subset of the first set of digital identification information corresponding to the user (e.g., Figure 6G). In some embodiments, the computer system displays a third user interface indicating that the first set of user inputs does not meet the authorization criteria (e.g., 626). In some embodiments, the request for the digital identification of the user requests a first subset of the first set of digital identification information corresponding to the user, and does not request a second subset of the first set of digital identification information corresponding to the user. Displaying a second user interface corresponding to a second application in response to receiving a request for the digital identification of the user from the first application provides feedback about the state of the device (e.g., the device has received a request for the digital identification of the user from the first application). If the first set of user inputs meets the authorization criteria, a subset of the digital identification information is provided, providing enhanced security by preventing unauthorized users from initiating sensitive operations.

[0219] In some embodiments, a second user interface (e.g., 618) corresponding to a second application identifies (e.g., indicates, displays, and / or presents) a first subset of the first set of digital identification information corresponding to the user (e.g., 620c, 620h). In some embodiments, the second user interface (e.g., 618) does not identify (e.g., does not display and / or present) a second subset of the first set of digital identification information corresponding to a user different from the first subset. In some embodiments, the second user interface does not identify (e.g., does not display and / or present) digital identification information corresponding to the user that is not in the first subset of the first set of digital identification information corresponding to the user (e.g., does not identify digital identification information corresponding to the user that is not requested by the first application). In some embodiments, the first application does not access the first set of digital identification information and / or the first subset of the first set of digital identification information, except for content provided to the first application by the second application. In some embodiments, a request for a digital identification of a user received from the first application includes a request for a first subset of the first set of digital identification information corresponding to the user, and does not include a request for a second subset of the first set of digital identification information corresponding to the user. In some embodiments, information based on the request (e.g., the request itself or the requested digital identification information) is sent to the second application. Displaying the first subset of the first set of digital identification information corresponding to the user within the second user interface provides feedback about the status of the device (e.g., the device has received a request for the first subset of the first set of digital identification information corresponding to the user from the first application).

[0220] In some embodiments, the computer system receives a request to unlock the computer system (e.g., one or more user inputs (e.g., one or more touch inputs, non-touch inputs, gesture inputs, and / or non-gesture inputs)) via one or more input devices (e.g., a request to transition the computer system from a locked state to an unlocked state). In some embodiments, after receiving the request to unlock the computer system (in some embodiments, in response to receiving the request to unlock the computer system), the computer system receives first biometric information corresponding to the user (e.g., a facial scan, a fingerprint scan, and / or an eye scan) via one or more input devices. In some embodiments, in response to receiving first biometric information corresponding to a user: based on determining that the first biometric information corresponds to (e.g., matches and / or satisfies a similarity threshold relative to a first biometric profile (e.g., a first biometric profile stored on and / or accessible by the computer system) (e.g., a first facial scan profile, a first eye scan profile, and / or a first fingerprint scan profile), the computer system unlocks the computer system (and, optionally, in some embodiments, the computer system displays an unlock user interface indicating that the computer system has transitioned to an unlocked state); based on determining that the first biometric information corresponds to (e.g., matches and / or satisfies a similarity threshold relative to a first biometric profile (e.g., a first biometric profile stored on and / or accessible by the computer system) (e.g., a second facial scan profile, a second eye scan profile, and / or a first fingerprint scan profile) that is different from the first biometric profile. The computer system unlocks the computer system (and, optionally, in some embodiments, displays an unlock user interface indicating that the computer system has transitioned to an unlocked state) based on a determination that the first biometric information corresponding to the user corresponds to a known biometric profile (e.g., does not match and / or does not satisfy a similarity threshold relative to the known biometric profile) (e.g., does not match a biometric profile stored on the computer system and / or accessible by the computer system and / or does not match a biometric profile of a known and / or registered user) (e.g., does not match the first biometric profile or the second biometric profile), the computer system abandons unlocking the computer system (e.g., maintains the computer system in a locked state and / or maintains display of a lock user interface indicating that the computer system is in an unlocked state).

[0221] In some embodiments, in response to receiving a first set of user input (e.g., Fig.6D and Figure 6J622, 636, and / or biometric information collected in the first set of user inputs), wherein the first set of user inputs includes second biometric information corresponding to the user (e.g., Fig.6D and Figure 6J In some embodiments, the computer system provides a first application with a first subset of the first set of digital identification information corresponding to the user (e.g., a facial scan, a fingerprint scan, and / or an eye scan) based on determining that the first set of user input satisfies the authorization criteria, including determining that the second biometric information corresponds to the first biometric profile (e.g., matches and / or satisfies a similarity threshold relative to the first biometric profile), the computer system providing the first application with a first subset of the first set of digital identification information corresponding to the user (e.g., Fig. 6E , Figure 6K ); and based on determining that the first set of user input does not satisfy the authorization criteria, including determining that the second biometric information corresponds to the second biometric profile (e.g., and does not correspond to the first biometric profile) (e.g., matches and / or satisfies a similarity threshold relative to the second biometric profile), the computer system forgoes providing the first application with the first subset of the first set of digital identification information corresponding to the user (e.g., Figure 6G ) (and, optionally, in some embodiments, the computer system displays a user interface indicating that a first subset of the first set of digital identification information corresponding to the user has not yet been provided to the first application (e.g., 626)). In some embodiments, the first set of user inputs includes second biometric information and one or more additional user inputs (e.g., 622, 636) (e.g., one or more touch inputs, one or more non-touch inputs, one or more button presses, and / or one or more gestures).

[0222] In some embodiments, the computer system stores and / or has access to multiple biometric profiles corresponding to multiple users. In some embodiments, multiple users are authorized to unlock the computer system, and the biometric information corresponding to any one of the multiple users will unlock the computer system. In some embodiments, the first set of digital identification information corresponds to the first user of the multiple users. In some embodiments, the first biometric profile corresponds to the first user of the multiple users, and the second biometric profile corresponds to the second user of the multiple users who is different from the first user. In some embodiments, the authorization criteria include criteria that are met if the first set of user inputs include biometric information corresponding to the first user. Therefore, if the first set of user inputs include biometric information corresponding to the second user (rather than the first user), the authorization criteria are not met, and the digital identification information corresponding to the first user program is not provided to the first application. If the second biometric information corresponds to the first biometric profile, the digital identification information is provided to the first application, and if the second biometric information corresponds to the second biometric profile (for example, and does not correspond to the first biometric profile), the digital identification information is abandoned to the first application, and the security and privacy of the device are improved by preventing unauthorized users from sharing digital identification information.

[0223] In some embodiments, the computer system displays a first user interface (e.g., 612, 630, 640), and concurrently displays the following items within the first user interface: a first selectable option (e.g., 614a, 632a) that can be selected to initiate a process of authenticating a user using a second application, including causing the first application to send a request for a digital identification of the user to the second application (e.g., a second selectable option that can be selected to cause the computer system to display a second user interface corresponding to the second application (e.g., displayed and / or generated by the second application) and / or a second user interface corresponding to the second application (e.g., generated by the second application); and a second selectable option (e.g., 614b, 632b) that can be selected to initiate a process of user authentication without using a second application (e.g., a first selectable option corresponding to a request to verify identity information corresponding to the user himself and / or a first selectable option that can be selected to display an authentication user interface corresponding to the first application (e.g., generated and / or displayed by the first application (and in some embodiments, not generated and / or displayed by the second application))) (e.g., without calling the second application and / or without displaying a second user interface corresponding to the second application).

[0224] In some embodiments, while displaying a first user interface (e.g., 612, 630, 640) (including concurrently displaying a first selectable option (e.g., 614a, 632a) and a second selectable option (e.g., 614b, 632b)), the computer system receives user input (e.g., touch input, non-touch input, gesture input, and / or non-gesture input); and in response to receiving the user input: based on determining that the user input corresponds to a selection of the first selectable option (e.g., 616, 634), the computer system displays a user interface (e.g., 618) corresponding to the second application (e.g., generated and / or displayed by the second application) via a display generation component (a second user interface and / or a different user interface corresponding to the second application (e.g., displayed and / or generated by the second application)); and based on determining that the user input corresponds to a selection of the second selectable option, the computer system abandons displaying the user interface (e.g., 618) corresponding to the second application (and optionally displays a user interface corresponding to the first application (e.g., displayed and / or generated by the first application)). Displaying a first selectable option that can be selected to initiate a process for user authentication using a second application reduces the amount of input required to perform user authentication.

[0225] In some embodiments, after providing the first subset of the first set of digital identification information corresponding to the user to the first application, the computer system displays a third user interface (e.g., generated and / or displayed by the first application) corresponding to the first application via the display generation component. Fig. 6F 612 and Figure 6L 630), wherein the third user interface is different from the first user interface and the second user interface (e.g., Fig. 6F 612 includes options 624a, 624b that were not previously displayed). In some embodiments, the user interface does not correspond to the second application (e.g., is not generated and / or displayed by the second application). In some embodiments, after receiving the first set of user inputs and / or after providing the first application with a first subset of the first set of digital identification information corresponding to the user, the computer system stops displaying the second user interface. In some embodiments, after receiving the first set of user inputs and / or after providing the first application with a first subset of the first set of digital identification information corresponding to the user, the computer system stops displaying the first user interface. Displaying a third user interface corresponding to the first application after providing the first subset of the first set of digital identification information to the first application provides feedback about the state of the device (e.g., digital identification information corresponding to the user has been provided to the first application).

[0226] In some embodiments, a second user interface (e.g., 618) corresponding to a second application identifies the first application (e.g., 620a ( Figure 6C in “Food Delivery”; Fig.6I "Event privileges" in the first application) (e.g., displaying the name of the first application and / or a visual indication (e.g., an icon and / or glyph) corresponding to the first application). Having the second user interface identify the first application provides improved security / privacy by ensuring that the user knows which application is requesting and / or receiving digital identification information corresponding to the user.

[0227] In some embodiments, a second user interface corresponding to a second application identifies (e.g., presents and / or displays) a first subset of a first set of digital identification information (e.g., 620c, 620h) corresponding to a user (e.g., identifies which information in the first set of digital identification information is being requested by the first application and / or will be provided to the first application). In some embodiments, the second user interface does not identify digital identification information that is in the first set of digital identification information but is not in the first subset of the first set of digital identification information (e.g., the second user interface does not identify digital identification information that is not requested by the first application and / or will not be provided to the first application). Having the second user interface identify the first subset of the first set of digital identification information provides improved security / privacy by ensuring that the user knows which digital identification information is being requested by the first application and / or will be provided to the first application.

[0228] In some embodiments, a second user interface corresponding to the second application identifies (e.g., presents and / or displays) the first digital identification information (e.g., 620c) that the first application is requesting (e.g., the first digital identification information that is part of the first subset of the first set of digital identification information) and indicates that the first digital identification information is to be stored by the first application (e.g., Figure 6C , Fig.6I In some embodiments, the second user interface identifies the second digital identification information that the first application is requesting and indicates that the second digital identification will also be stored by the first application (e.g., will be stored by the first application for greater than a threshold duration and / or will be stored by the first application in a memory that resides external to and / or separate from the computer system). Having the second user interface identify which digital identification information will be stored by the first application provides improved security and privacy by ensuring that the user knows which digital identification information will be stored by the first application.

[0229] In some embodiments, the computer system displays a second user interface, including concurrently displaying the following items: first content (e.g., 620c) identifying the first digital identification information (e.g., text content and / or non-text content) (e.g., indicating that the first application is requesting the first content for the first digital identification information), wherein the first content is displayed in a first manner (e.g., displayed together with the first visual indication and / or displayed in a first area of ​​the second user interface), indicating that the first digital identification information will be stored by the first application (e.g., Fig.6I , 620c, displayed in a first area of ​​the user interface) (e.g., will be stored by the first application for greater than a threshold duration and / or will be stored by the first application in a memory residing external to and / or separate from the computer system); and second content (e.g., text content and / or non-text content) (e.g., 620h) identifying second digital identification information that is different from the first digital identification information (e.g., indicating that the first application is requesting the second content of the second digital identification information), wherein the second content is displayed in a second manner that is different from the first manner (e.g., displayed without a first visual indication, displayed with a second visual indication, and / or displayed in a second area of ​​the second user interface), indicating that the second digital identification information will not be stored by the first application (e.g., 620h, displayed in the second area of ​​the user interface) (e.g., will be provided to the first application, but will not be stored by the first application) (e.g., will not be stored by the first application for more than a threshold duration and / or will not be stored by the first application in a memory residing external to and / or separate from the computer system).

[0230] In some embodiments, displaying the second user interface (e.g., 618) also includes displaying the following items concurrently with the first content and the second content: third content identifying third digital identification information, wherein the third content is displayed in a first manner, indicating that the third digital identification information will be stored by the first application. In some embodiments, displaying the second user interface also includes displaying the following items concurrently with the first content, the second content, and / or the third content: fourth content identifying fourth digital identification information, wherein the fourth content is displayed in a second manner, indicating that the fourth digital identification information will not be stored by the first application. Having the second user interface identify which digital identification information will be stored by the first application and which digital identification information will not be stored by the first application provides improved security and privacy by ensuring that the user knows which digital identification information will be stored by the first application.

[0231] In some embodiments, the second user interface (e.g., 618) displays an indication (e.g., a visual indication, a textual indication, and / or a non-textual indication) of how long (e.g., hours, days, weeks, months, and / or years) the first digital identification information will be stored by the first application (e.g., Figure 6C and Fig.6I Having the second user interface identify how long the digital identification information will be stored by the first application provides improved security and privacy by ensuring that the user knows what digital identification information will be stored by the first application and for how long.

[0232] In some embodiments, a first subset of the first set of digital identification information corresponding to the user includes an indication of whether the user meets an age threshold (e.g., Figure 6C and Fig.6I Automatically providing an indication of whether the user meets the age threshold to the first application in response to determining that the authorization criteria are met allows the user to provide digital identification information with less user input.

[0233] In some embodiments, the first set of digital identification information corresponding to the user is associated with a geographic region (in some embodiments, the first set of digital identification information corresponds to a digital identification credential (e.g., a card and / or license) issued and / or authorized by a jurisdiction and / or entity corresponding to the geographic region (e.g., issued and / or authorized by a state and / or country), and the first subset of the first set of digital identification information includes an indication of the geographic region (e.g., Figure 6C and Fig.6I Automatically providing geographic region information corresponding to the user and / or the first set of digital identification information to the first application in response to determining that the authorization criteria are met allows the user to provide digital identification information with less user input.

[0234] In some embodiments, the first subset of the first set of digital identification information corresponding to the user includes a photo of the user (e.g., Figure 6C and Fig.6I In some embodiments, the first set of digital identification information corresponding to the user is a digital representation of a physical identification card, and the photo of the user is a photo of the user displayed on the physical identification card. In some embodiments, the first set of digital identification information corresponds to a digital identification credential (e.g., a card and / or license) issued and / or authorized by an entity or jurisdiction, and the photo of the user is a photo of the user corresponding to the digital identification credential. Automatically providing the user's photo to the first application in response to determining that the authorization criteria are met allows the user to provide digital identification information with less user input.

[0235] In some embodiments, the first application requests a digital identification of the user (e.g., requests a first subset of a first set of digital identification information corresponding to the user) in order to verify that the user is authorized to create a user account for the child (e.g., Figures 6M to 6N ) (e.g., to verify that a user meets an age threshold required to create a user account for a child (e.g., a child who does not meet an age threshold and / or is below a minimum age) and / or to verify that a user meets one or more identity criteria required to create a user account for a child). Ensuring that a user meets the criteria for creating a user account for a child improves the security and privacy of the device by ensuring that unauthorized users do not perform sensitive and / or unauthorized actions.

[0236] In some embodiments, the first application requests a digital identification of a user (e.g., requests a first subset of a first set of digital identification information corresponding to the user) in order to verify that the user is authorized to complete the purchase transaction (e.g., FIG. 6B to FIG. 6L ) (e.g., to verify that the user is authorized to make the purchase using payment credentials associated with the user and / or to verify that the user meets the age threshold required for the purchase). Ensuring that the user meets the criteria for making a purchase improves the security and privacy of the device by ensuring that unauthorized users do not perform sensitive and / or unauthorized actions.

[0237] In some embodiments, the computer system displays a digital identification user interface (eg, 648, 649) that is different from the first user interface and the second user interface via a display generation component. Figure 6P ) (e.g., a digital identification user interface corresponding to a second application (e.g., displayed and / or generated by the second application), comprising concurrently displaying: a representation of a first sending instance (e.g., 652c to 652f) in which a subset (e.g., all and / or less than all) of a first set of digital identification information corresponding to a user is provided to a third application (e.g., a third application different from the first application and / or the same as the first application); and a representation of a second sending instance (e.g., 652c to 652f) different from the first sending instance, in which a subset (e.g., all and / or less than all) of the first set of digital identification information corresponding to the user is provided to a fourth application (e.g., a fourth application different from the first application and / or the third application and / or the same as the first application and / or the third application). In some embodiments, the representation of the first sending instance identifies the third application. In some embodiments, the representation of the second sending instance identifies the fourth application. Displaying a digital identification user interface in which a user can view past instances in which digital identification information was provided to an application improves the security and privacy of a device by allowing a user to ensure that unauthorized applications do not improperly access digital identification information.

[0238] In some embodiments, a representation of a first sending instance (e.g., 652c to 652f) is selectable by a user to display one or more details of the first sending instance (e.g., 660-1, 660-2) via a display generation component (e.g., the date of the first sending instance; the time of the first sending instance; which digital identification information in the first set of digital identification information is sent to a third application in the first sending instance; which digital identification information in the first set of digital identification information is sent to a third application in the first sending instance and stored by the third application; and / or which digital identification information in the first set of digital identification information is sent to a third application in the first sending instance but is not stored by the third application) (e.g., without displaying one or more details of the second sending instance), which are not displayed in the digital identification user interface.

[0239] In some embodiments, the representation of the second sending instance is selectable by the user to display one or more details of the second sending instance (e.g., 660-1, 660-2) via the display generation component (e.g., the date of the second sending instance; the time of the second sending instance; which digital identification information in the first set of digital identification information is sent to the fourth application in the second sending instance; which digital identification information in the first set of digital identification information is sent to the third application in the second sending instance and stored by the third application; and / or which digital identification information in the first set of digital identification information is sent to the third application in the second sending instance but not stored by the third application) (e.g., one or more details of the first sending instance are not displayed), which one or more details are not displayed in the digital identification user interface. Displaying representations of the sending instances that can be selected by the user to view additional details about these sending instances improves the security and privacy of the device by allowing the user to ensure that unauthorized applications do not improperly access digital identification information.

[0240] For the purpose of explanation, the preceding description is described by reference to specific embodiments. However, the above exemplary discussion is not intended to be exhaustive or 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.

[0241] 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.

[0242] As described above, one aspect of the present technology is to collect and use data available from various sources to improve the user experience when using and / or managing digital identification credentials. The present disclosure contemplates that, in some instances, such 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 driver's license information, demographic data, location-based data, phone numbers, email addresses, social network IDs, home addresses, data or records related to a user's health or fitness level (e.g., vital sign measurements, medication information, exercise information), date of birth, or any other identification or personal information.

[0243] The present disclosure recognizes that the use of such personal information data in the present invention technology can be used to benefit users. For example, personal information data can be used to provide services to users or facilitate transactions. In addition, the present disclosure also anticipates other uses of personal information data that benefit users.

[0244] The disclosure anticipates that entities responsible for the collection, analysis, disclosure, transmission, storage or other purposes of such personal information data will comply with sound privacy policies and / or privacy measures. Specifically, such entities should implement and adhere to the use of privacy policies and practices that are recognized as meeting or exceeding the industry or government requirements for maintaining the privacy and security of personal information data. Such policies should be easy for users to access and should be updated as changes in the collection and / or use of data occur. Personal information from users should be collected for legal and reasonable entity purposes and should not be shared or sold outside these legal purposes. In addition, such collection / sharing should be carried out after receiving the informed consent of the user. Additionally, such entities should consider taking any necessary steps to protect and safeguard access to such personal information data, and ensure that other entities with access to personal information data comply with their privacy policies and procedures. In addition, such entities can subject themselves to third-party assessments to prove that they comply with widely accepted privacy policies and practices. In addition, policies and practices should be adapted to specific types of personal information data collected and / or accessed, and to applicable laws and standards including considerations of special jurisdictions. For example, in the United States, the collection or acquisition 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 measures should be advocated for different types of personal data in each country.

[0245] 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 hardware elements and / or software elements to prevent or block access to such personal information data. For example, with respect to digital identification credentials, 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 registration for a service. In another example, a user may choose not to provide personal information, such as information associated with a digital identification credential. In yet another example, a user may choose to limit the length of time that digital identification credential information is maintained or to completely prohibit sharing of digital identification credential information. In addition to providing "opt-in" and "opt-out" options, the present disclosure also 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.

[0246] In addition, the intention of the present disclosure is that personal information data should be managed and processed in a manner that minimizes the risk of unintentional or unauthorized access or use. Once the data is no longer needed, the risk can be minimized by limiting data collection and data deletion. In addition, and when applicable, including in certain health-related applications, data anonymization can be used to protect the privacy of users. Where appropriate, anonymization can be promoted 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 the storage mode of data (e.g., how long is stored and where is stored), and / or other methods.

[0247] 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, content may be selected and delivered to a user by inferring preferences based on non-personal information data or an absolute minimum amount of personal information, such as content requested by a device associated with the user, other non-personal information available to the service, or publicly available information.

Claims

1. A method comprising: At a computer system in communication with a display generation component and one or more input devices: displaying, via the display generation component, a first user interface corresponding to the first application; receiving a request for a digital identification of a user from the first application; In response to receiving the request for the digital identification of the user from the first application: displaying, via the display generation component, a second user interface corresponding to a second application different from the first application, wherein the second application has access to a first set of digital identification information corresponding to the user; receiving a first set of user inputs via the one or more input devices while displaying the second user interface; as well as In response to receiving the first set of user input: Based on determining that the first set of user input meets authorization criteria, a first subset of the first set of digital identification information corresponding to the user is provided to the first application. 2 . The method of claim 1 , wherein the second user interface corresponding to the second application identifies the first subset of the first set of digital identification information corresponding to the user.

3. The method according to any one of claims 1 to 2, further comprising: receiving, via the one or more input devices, a request to unlock the computer system; After receiving the request to unlock the computer system, receiving, via the one or more input devices, first biometric information corresponding to a user; In response to receiving the first biometric information corresponding to the user: unlocking the computer system based on determining that the first biometric information corresponds to a first biometric profile; unlocking the computer system based on determining that the first biometric information corresponds to a second biometric profile that is different from the first biometric profile; as well as abandoning unlocking the computer system based on determining that the first biometric information corresponding to the user does not correspond to a known biometric profile; as well as In response to receiving the first set of user inputs, wherein the first set of user inputs includes second biometric information corresponding to a user: providing the first subset of the first set of digital identification information corresponding to the user to the first application based on determining that the first set of user input satisfies authorization criteria, including determining that the second biometric information corresponds to the first biometric profile; as well as Based on determining that the first set of user inputs does not satisfy authorization criteria, including determining that the second biometric information corresponds to the second biometric profile, Forget about providing the first subset of the first set of digital identification information corresponding to the user to the first application.

4. The method according to any one of claims 1 to 2, wherein: Displaying the first user interface includes concurrently displaying the following items within the first user interface: a first selectable option selectable to initiate a process of user identity authentication using the second application, comprising causing the first application to send the request for the digital identification of the user to the second application; and A second selectable option that can be selected to initiate a process for user authentication without using the second application.

5. The method according to any one of claims 1 to 2, further comprising: After providing the first subset of the first set of digital identification information corresponding to the user to the first application, a third user interface corresponding to the first application is displayed via the display generation component, wherein the third user interface is different from the first user interface and the second user interface. 6 . The method according to claim 1 , wherein the second user interface corresponding to the second application identifies the first application.

7. The method according to any one of claims 1 to 2, wherein the second user interface corresponding to the second application identifies the first digital identification information being requested by the first application and indicates that the first digital identification information is to be stored by the first application.

8. The method of claim 7, wherein displaying the second user interface comprises concurrently displaying: first content, the first content identifying the first digital identification information, wherein the first content is displayed in a first manner, indicating that the first digital identification information is to be stored by the first application; and Second content, the second content identifying second digital identification information different from the first digital identification information, wherein the second content is displayed in a second manner different from the first manner, indicating that the second digital identification information will not be stored by the first application.

9. The method of claim 7, wherein the second user interface displays an indication of how long the first digital identification information is to be stored by the first application.

10. The method of any one of claims 1 to 2, wherein the first subset of the first set of digital identification information corresponding to the user includes an indication of whether the user meets an age threshold.

11. The method of any one of claims 1 to 2, wherein the first set of digital identification information corresponding to the user is associated with a geographic region, and the first subset of the first set of digital identification information includes an indication of the geographic region.

12. The method of any one of claims 1 to 2, wherein the first subset of the first set of digital identification information corresponding to the user includes a photo of the user.

13. The method of any one of claims 1 to 2, wherein the first application requests a digital identification of the user to verify that the user is authorized to create a user account for a child.

14. The method of any one of claims 1 to 2, wherein the first application requests a digital identification of the user to verify that the user is authorized to complete a purchase transaction.

15. The method according to any one of claims 1 to 2, further comprising: Displaying, via the display generation component, a digital identity user interface that is different from the first user interface and the second user interface includes concurrently displaying: a representation of a first transmission instance in which a subset of the first set of digital identification information corresponding to the user is provided to a third application; and A representation of a second instance of sending, different from the first instance of sending, wherein a subset of the first set of digital identification information corresponding to the user is provided to a fourth application.

16. The method of claim 15, wherein: The representation of the first sending instance is selectable by a user to display, via the display generation component, one or more details of the first sending instance that are not displayed in the digital signage user interface; and The representation of the second sending instance is selectable by a user to display, via the display generation component, one or more details of the second sending instance that are not displayed in the digital identity user interface.

17. A computer-readable storage medium storing one or more programs configured to be executed by one or more processors of a computer system in communication with a display generation component and one or more input devices, the one or more programs comprising instructions for performing the method according to any one of claims 1 to 16.

18. A computer system configured to communicate with a display generation component and one or more input devices, 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 16.

19. A computer system configured to communicate with a display generation component and one or more input devices, comprising: A component for carrying out the method according to any one of claims 1 to 16.

20. A computer program product comprising one or more programs configured to be executed by one or more processors of a computer system in communication with a display generation component and one or more input devices, the one or more programs comprising instructions for performing the method according to any one of claims 1 to 16.

Images