Devices, methods, and graphical user interfaces for activating, configuring, and interacting with different operating modes

Abstract

The present disclosure relates to devices, methods, and graphical user interfaces for activating, configuring, and interacting with different modes of operation. A computer system includes: a display; a sensor for detecting user input; a wireless power transfer coil for wirelessly receiving a power transfer signal from a charging source; a rectifier adapted to charge a battery of the computer system using the power transfer signal; and a communication circuit adapted to obtain identification data representing a respective identity of the charging source from a power transfer signal wirelessly received from the charging source; and one or more processors configured to perform operations. The operations include displaying a customizable user interface that is not displayed prior to detecting the first event in accordance with a determination that a first criterion is satisfied as a result of the first event. If a power transfer signal wirelessly received from the charging source includes identification data representing an identity of the charging source, the computer system displays a customizable user interface corresponding to the identity of the charging source.

Description

[0001] This application is a divisional application of the invention patent application filed on May 7, 2024, with application number 202480031337.0 and entitled "Device, method and graphical user interface for activating, configuring different operating modes and interacting with different operating modes".

[0002] Related patent applications This patent application is a continuation to U.S. Patent Application No. 18 / 656,538, filed May 6, 2024, which claims priority to U.S. Provisional Patent Application No. 63 / 465,238, filed May 9, 2023; U.S. Provisional Patent Application No. 63 / 470,966, filed June 4, 2023; U.S. Provisional Patent Application No. 63 / 605,507, filed December 2, 2023; and U.S. Provisional Patent Application No. 63 / 607,056, filed December 6, 2023. Technical Field

[0003] This article relates in general to electronic devices with touch-sensitive surfaces, including but not limited to electronic devices with touch-sensitive surfaces. Background Technology

[0004] The use of touch-sensitive surfaces as input devices for computers and other electronic computing devices has grown significantly in recent years. Examples of touch-sensitive surfaces include touchpads and touchscreen displays. These surfaces are widely used to manipulate user interfaces and objects on the display. Examples of user interface objects include digital images, videos, text, icons, and control elements such as buttons, as well as other graphics.

[0005] Example manipulations include adjusting the position and / or size of one or more user interface objects, activating a button or opening a file / application represented by a user interface object, associating metadata with one or more user interface objects, or otherwise manipulating the user interface. Example user interface objects include digital images, videos, text, icons, control elements (such as buttons), and other graphics. In some cases, users will need to perform such manipulations on user interface objects from the following categories: file management programs (e.g., Finder from Apple Inc. (Cupertino, California); image management applications (e.g., Aperture, iPhoto, Photos from Apple Inc. (Cupertino, California); digital content (e.g., video and music) management applications (e.g., iTunes from Apple Inc. (Cupertino, California); drawing applications; presentation applications (e.g., Keynote from Apple Inc. (Cupertino, California); word processing applications (e.g., Pages from Apple Inc. (Cupertino, California); or spreadsheet applications (e.g., Numbers from Apple Inc. (Cupertino, California)).

[0006] While touch-sensitive displays are frequently used when their associated devices are in use, they are rarely used when the devices are not in use. Even when the device is not in use, it still provides access to the device's functions and / or applications, and can also provide status information for events and / or applications. Summary of the Invention

[0007] Therefore, there is a need for electronic devices that can provide users with improved functionality and information while meeting certain criteria (e.g., ensuring the device does not unnecessarily sacrifice battery power and / or provide such functionality in situations where it is not needed or accessible to the user). Such methods and interfaces reduce the amount, extent, and / or nature of user input, resulting in more efficient human-machine interfaces. For battery-powered devices, such methods and interfaces can save power and increase the time interval between battery charges.

[0008] The disclosed devices reduce or eliminate the aforementioned drawbacks and other problems associated with the user interface of electronic devices (or more generally, computer systems) having touch-sensitive surfaces. In some embodiments, the device is a desktop computer. In some embodiments, the device is portable (e.g., a laptop, tablet, or handheld device). In some embodiments, the device is a personal electronic device (e.g., a wearable electronic device, such as a watch). In some embodiments, the device has a touchpad. In some embodiments, the device has a touch-sensitive display (also referred to as a "touchscreen" or "touchscreen display"). In some embodiments, the device has a graphical user interface (GUI), one or more processors, memory, and one or more modules, and a program or set of instructions stored in memory for performing multiple functions. In some embodiments, the user interacts with the GUI primarily through stylus and / or finger contact and gestures on the touch-sensitive surface. In some embodiments, these functions may optionally include image editing, drawing, presentations, word processing, spreadsheet creation, gaming, making and receiving phone calls, video conferencing, sending and receiving emails, instant messaging, fitness support, digital photography, digital video recording, web browsing, digital music playback, note-taking, and / or digital video playback. Executable instructions for performing these functions may optionally be included in a nontransitory computer-readable storage medium or other computer program product configured for execution by one or more processors.

[0009] According to some embodiments, a method is performed at a computer system communicating with a display generation component and one or more sensors. The method includes detecting a first event. The method includes, in response to detecting the first event: displaying a first customizable user interface that was not displayed prior to the detection of the first event, based on a determination that the first event is a result of satisfying a first criterion, wherein the first criterion requires that the orientation of the display generation component is a first orientation and that the computer system is charging to satisfy the first criterion; and abandoning the display of the first customizable user interface based on a determination that the first event is a result of not satisfying the first criterion.

[0010] According to some embodiments, a method is performed at a computer system communicating with a display generation component and one or more input devices. The method includes displaying a first user interface selected from a first set of user interfaces via the display generation component, wherein the first user interface displays content of a first type according to a first set of configuration options. The method includes detecting first user input directed to the first user interface when the first user interface is displayed. The method includes, in response to detecting the first user input directed to the first user interface: replacing the display of the first user interface with the display of a second user interface, wherein the second user interface is selected from the first set of user interfaces and displays content of a second type different from the first type of content, based on determining that the first user input satisfies a first directional criterion, wherein the first directional criterion requires the first user input to include movement in a second direction different from the first direction to satisfy the second directional criterion, and replacing the display of the first user interface with the display of content of the first type according to a second set of configuration options different from the first set of configuration options. The method includes detecting second user input directed to a corresponding user interface when a corresponding user interface in the first set of user interfaces is displayed after the first user input is detected. The method includes, in response to detecting a second user input: based on determining that the second user input satisfies a first directional criterion, wherein the first directional criterion requires the second user input to include movement in a first direction in order to satisfy the first directional criterion, replacing the display of a corresponding user interface with the display of a third user interface selected from a first set of user interfaces, wherein the third user interface displays third type content that is different from the first type of content and the second type of content.

[0011] According to some embodiments, a method is performed at a computer system communicating with a display generation component and one or more input devices. The method includes displaying a first user interface corresponding to a constrained state of the computer system, including simultaneously displaying a first widget in a first set of widgets at a first placement position and a second widget in a second set of widgets at a second placement position within the first user interface. The first placement position is configured to accommodate a corresponding widget in the first set of widgets, and the second placement position is configured to accommodate a corresponding widget in the second set of widgets. The method includes detecting a first user input directed to the first user interface while simultaneously displaying the first widget in the first set of widgets at the first placement position and the second widget in the second set of widgets at the second placement position within the first user interface. The method includes, in response to detecting a first user input pointing to a first user interface: replacing the display of a first widget with a different widget from a first group of widgets located at the first placement position, based on determining that the first user input points to a first placement position within the first user interface and that the first user input meets a first switching criterion; and replacing the display of a second widget with a different widget from a second group of widgets located at the second placement position, based on determining that the first user input points to a second placement position within the first user interface and that the first user input meets the first switching criterion.

[0012] According to some embodiments, a method is performed at a computer system communicating with a display generation component and one or more sensors. The method includes, when displaying a first user interface, detecting that one or more conditions for displaying a corresponding user interface object of a first object type are met. The corresponding user interface object of the first type corresponds to a corresponding application and provides state information updated over time in the corresponding user interface object without requiring the display of the corresponding application. The method includes, in response to detecting that one or more conditions for displaying a corresponding user interface object of the first object type are met, displaying the corresponding user interface object. The method includes, when displaying the corresponding user interface object, detecting a first user input corresponding to a request to eliminate the corresponding user interface object. The method includes, in response to detecting the first user input corresponding to a request to eliminate the corresponding user interface object: stopping the display of the corresponding user interface object and redisplaying the first user interface object based on determining that the first user interface is a first type of user interface; and stopping the display of the corresponding user interface object and displaying a second user interface different from the first user interface object in the position previously occupied by the first user interface object based on determining that the first user interface is a second type of user interface different from the first type of user interface.

[0013] According to some embodiments, a method is performed at a computer system communicating with a display generation component and one or more sensors. The method includes detecting a disconnection between the computer system and a charging source. In response to detecting the disconnection, the method further includes activating a flashlight function of the computer system based on determining that the disconnection occurred when the computer system was in a first operating mode, wherein the computer system displays a clock user interface via the display generation component for at least a portion of the duration of operation in the first operating mode.

[0014] According to some embodiments, a method is performed at a computer system including a display generation component and one or more sensors. The method includes, when the computer system is operating in a first mode, wherein the computer system operates in the first mode upon meeting a first criterion, detecting the presence of a person approaching the computer system via one or more sensors without detecting contact between the person and the computer system. The method includes, in response to detecting the presence of a person approaching the computer system without detecting contact between the person and the computer system, updating the display content displayed via the display generation component of the computer system while remaining in the first mode.

[0015] In some implementations, a method is performed at a computer system communicating with a display generation component and one or more sensors for detecting user input. The method includes detecting a first event. The method includes, in response to detecting the first event and based on determining that a first criterion is met as a result of the first event, displaying a corresponding customizable user interface that was not displayed prior to the detection of the first event. Displaying the corresponding customizable user interface includes, based on determining that one or more power transmission signals received from a charging source include first identification data representing a first identity of the charging source, and that the first identity of the charging source is stored at the computer system in association with a first set of custom parameters, displaying a first customizable user interface configured according to the first set of custom parameters corresponding to the first identity of the charging source.

[0016] In some embodiments, a computer system includes: a display generation component; one or more sensors for detecting user input; a power transfer coil adapted to receive a power transfer signal from a charging source; a rectifier adapted to charge a battery of the computer system using the power transfer signal received from the charging source by the power transfer coil; a communication circuit adapted to obtain identification data representing a corresponding identity of the charging source from at least one of the power transfer signals received from the charging source; and one or more processors. The computer system includes a memory storing instructions that, when executed by one or more processors, cause the processors to perform operations including: detecting a first event; and, in response to detecting the first event: displaying a corresponding customizable user interface that was not displayed prior to the detection of the first event, based on determining that a first criterion is met as a result of the first event.

[0017] According to some embodiments, an electronic device (or more generally, a computer system) includes: a display, a touch-sensitive surface, one or more sensors optionally for detecting the intensity of contact with the touch-sensitive surface, one or more tactile output generators optionally, one or more processors, and a memory storing one or more programs; the one or more programs are configured to be executed by the one or more processors, and the one or more programs include instructions for performing or causing the operation of any of the methods described herein. According to some embodiments, a computer-readable storage medium stores instructions therein that, when executed by an electronic device having a display, a touch-sensitive surface, one or more sensors optionally for detecting the intensity of contact with the touch-sensitive surface, and optionally one or more tactile output generators, cause the device to perform or cause the operation of any of the methods described herein to be performed. According to some embodiments, a graphical user interface on an electronic device having a display, a touch-sensitive surface, optionally one or more sensors for detecting the intensity of contact with the touch-sensitive surface, optionally one or more tactile output generators, memory, and one or more processors for executing one or more programs stored in the memory includes one or more elements displayed in any of the methods described herein, the one or more elements being updated in response to input as described in any of the methods described herein. According to some embodiments, an electronic device includes: a display, a touch-sensitive surface, optionally one or more sensors for detecting the intensity of contact with the touch-sensitive surface, and optionally one or more tactile output generators; and components for performing or causing operation of any of the methods described herein. According to some embodiments, an information processing apparatus for an electronic device having a display, a touch-sensitive surface, optionally one or more sensors for detecting the intensity of contact with the touch-sensitive surface, and optionally one or more tactile output generators, includes components for performing or causing operation of any of the methods described herein.

[0018] Therefore, improved methods and interfaces are provided to electronic devices and other computer systems having a display, a touch-sensitive surface, one or more sensors optionally for detecting the intensity of contact with the touch-sensitive surface, one or more tactile output generators optionally, one or more device orientation sensors optionally, and an audio system, for activating, configuring different operating modes (e.g., providing access to different functions and / or information), and interacting with different operating modes, thereby improving effectiveness, efficiency, and user satisfaction with such devices. Such methods and interfaces can complement or replace conventional methods for activating, configuring (existing) operating modes, and interacting with (existing) operating modes. Attached Figure Description

[0019] To better understand the various described embodiments, reference should be made to the following detailed description in conjunction with the accompanying drawings, wherein similar reference numerals in all the drawings indicate corresponding parts.

[0020] Figure 1A This is a block diagram illustrating a portable multi-functional device with a touch-sensitive display according to some implementation schemes.

[0021] Figure 1B This is a block diagram illustrating example components for event handling according to some implementation schemes.

[0022] Figure 2 Examples of portable multi-functional devices with touchscreens according to some implementation schemes are shown.

[0023] Figure 3 This is a block diagram of an example multifunctional device with a display and a touch-sensitive surface, according to some implementation schemes.

[0024] Figure 4A An example user interface for an application menu on a portable multifunction device according to some implementation schemes is shown.

[0025] Figure 4B An example user interface for a multi-functional device having a touch-sensitive surface separate from the display is illustrated according to some implementation schemes.

[0026] Figures 4C1 to 4C2 An example state diagram illustrating navigation between various user interfaces of a multifunctional device according to some implementation schemes is shown.

[0027] Figures 5A to 5AT Example user interfaces are shown, based on some implementation schemes, for automatically displaying a customizable user interface when certain criteria are met.

[0028] Figures 6A to 6AN Example user interfaces for switching between different operating modes (e.g., environment modes), interacting with different operating modes, and configuring different operating modes are illustrated according to some implementation schemes.

[0029] Figures 7A to 7V Example user interfaces for interacting with and configuring customizable user interfaces, according to some implementation schemes, are illustrated.

[0030] Figures 8A to 8K Examples of user interfaces for interacting with different operating modes (e.g., environment modes) and switching between different operating modes are illustrated according to some implementation schemes.

[0031] Figures 9A to 9AAAn example user interface is shown according to some implementations for automatically activating the flashlight function of a computer system 100 (e.g., a portable multifunction device, a display generation component associated with a computing device, or other device) when certain criteria are met.

[0032] Figures 10A to 10L This is a flowchart of a process for automatically displaying a customizable user interface when certain criteria are met, based on some implementation schemes.

[0033] Figures 11A to 11G It is a flowchart of a process for switching between different operating modes (e.g., environment modes), interacting with different operating modes, and configuring different operating modes, according to some implementation schemes.

[0034] Figures 12A to 12D It is a flowchart of a process for interacting with and configuring a customizable user interface, based on some implementation schemes.

[0035] Figures 13A to 13J It is a flowchart of a process for interacting with different user interfaces for different operating modes (e.g., environment modes) and switching between different operating modes, according to some implementation schemes.

[0036] Figures 14A to 14G This is a flowchart of a process for automatically activating the flashlight function of a computer system 100 (e.g., a portable multifunction device, a display generation component associated with a computing device, or other device) when certain criteria are met, according to some implementation schemes.

[0037] Figures 15A to 15Q An example user interface for updating displayed content when an existence criterion is met, according to some implementation schemes, is illustrated.

[0038] Figures 16A to 16F It is a flowchart of a process for updating the displayed content when certain criteria are met, according to some implementation schemes.

[0039] Figures 17A to 17C This is a flowchart of a process for displaying a customized user interface configured according to customized parameters corresponding to the received identity of the charging source, based on some implementation schemes. Detailed Implementation

[0040] While portable electronic devices such as smartphones and tablets have become increasingly prevalent, little attention has been paid to how to effectively utilize them when they are not actively used. Such devices can be used to provide users with useful information, even when not actively used. For example, a device can be configured to operate in a specific operating mode that provides time information (e.g., by acting as a clock and / or displaying a clock face), and / or provides quick access to useful utilities or time-sensitive information (e.g., via widgets and / or by displaying a user interface that shows status information that changes or updates over time, e.g., in real time). Furthermore, operating modes can be configured to be active when specific criteria are met (e.g., the device is charging and / or in a specific orientation), which can be tailored to scenarios where the device is not used and where operating in the operating mode will not adversely affect the device (e.g., when not connected to a charging source, it will not adversely affect the device's battery life). Such operating modes provide efficient access to useful functions and information, even when the device is not actively used.

[0041] The processes described below enhance device operability and make user-device interfaces more efficient through various technologies (e.g., by helping users provide appropriate input and reducing user errors when operating / interacting with the device), including providing users with improved visual, auditory, and / or haptic feedback; reducing the amount of input required to perform operations; providing additional control options without cluttering the user interface with additional displayed controls; and performing operations when a set of conditions have been met without further user input and / or additional features. These technologies also reduce power consumption and extend device battery life by enabling users to use the device faster and more efficiently.

[0042] under, Figures 1A to 1B , Figure 2 and Figure 3 Provide a description of the example device. Figures 4A to 4B and Figures 5A to 5AT An example user interface is shown for automatically displaying a customizable user interface when certain criteria are met. Figures 6A to 6AN Example user interfaces are shown for switching between different operating modes (e.g., environment mode), interacting with different operating modes, and configuring different operating modes. Figures 7A to 7V Example user interfaces are shown for interacting with and configuring customizable user interfaces. Figures 8A to 8K Examples of user interfaces for interacting with different operating modes (e.g., ambient mode) and switching between different operating modes are shown. Figures 9A to 9AAAn example user interface is shown for automatically activating the flashlight function of a computer system 100 (e.g., a portable multifunction device, a display generation component associated with a computing device, or other device) when certain criteria are met. Figures 10A to 10L This is a flowchart of a method for automatically displaying a customizable user interface when certain criteria are met. Figures 11A to 11G It is a flowchart of methods for switching between different operating modes (e.g., environment modes), interacting with different operating modes, and configuring different operating modes. Figures 12A to 12D This is a flowchart of methods for interacting with and configuring customizable user interfaces. Figures 13A to 13J It is a flowchart of a method for interacting with different user interfaces in different operating modes (e.g., environment modes) and switching between different operating modes. Figures 14A to 14G This is a flowchart of a process for automatically activating the flashlight function of a computer system 100 (e.g., a portable multifunction device, a display generation component associated with a computing device, or other device) when certain criteria are met. Figures 15A to 15Q An example user interface is shown for updating the displayed content when an existence criterion is met. Figures 16A to 16F This is a flowchart of a method for updating the displayed content when an existence criterion is met. Figures 5A to 5AT The user interface in the example is used to demonstrate Figures 10A to 10L The process in. Figures 6A to 5AN The user interface in the example is used to demonstrate Figure 11A middle Figure 11G The process in. Figures 7A to 7V The user interface in the example is used to demonstrate Figures 12A to 12D The process in. Figures 8A to 8K The user interface in the example is used to demonstrate Figures 13A to 13J The process in. Figures 9A to 9AA The user interface in the example is used to demonstrate Figures 14A to 14G The process in. Figures 15A to 15Q The user interface in the example is used to demonstrate Figures 16A to 16F The process in.

[0043] Example device Reference will now be made in detail to the embodiments, examples of which are illustrated in the accompanying drawings. Numerous specific details are shown in the following detailed description in order to provide a full understanding of the various described embodiments. However, it will be apparent to those skilled in the art that the various described embodiments can be practiced without these specific details. In other instances, well-known methods, processes, components, circuits, and networks are not described in detail so as not to unnecessarily obscure the various aspects of the embodiments.

[0044] It will also be understood that, although in some cases the terms “first,” “second,” etc., are used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first contact may be referred to as a second contact, and similarly, a second contact may be referred to as a first contact, without departing from the scope of the various described embodiments. Both the first contact and the second contact are contacts, but they are not the same contact unless the context clearly indicates otherwise.

[0045] The terminology used in the description of the various described embodiments herein is for the purpose of describing particular embodiments only and is not intended to be limiting. As used in the description of the various described embodiments and the appended claims, the singular forms “a” and “the” are intended to include the plural forms as well, unless the context expressly indicates otherwise. It will also be understood that the term “and / or” as used herein refers to and covers any and all possible combinations of one or more of the associated listed items. It will also be understood that the terms “comprising” and / or “including” as used in this specification specify the presence of the 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 groups thereof.

[0046] As used herein, depending on the context, the term "if" may optionally be interpreted as meaning "when" followed by "at," "in response to determination," or "in response to detection." Similarly, depending on the context, the phrases "if it is determined..." or "if [the stated condition or event] is detected" may optionally be interpreted as meaning "in response to determination..." or "when [the stated condition or event] is detected," or "in response to the detection of [the stated condition or event]."

[0047] This document describes implementations of electronic devices (and more generally computer systems), user interfaces for such devices, and associated processes for using such devices. In some implementations, the device is a portable communication device, such as a mobile phone, that also includes other functionalities such as PDA and / or music player functionality. Example implementations of portable multi-functional devices include, but are not limited to, the iPhone from Apple Inc., Cupertino, California. ® iPod Touch ® and iPad ®Device. Alternatively, other portable electronic devices may be used, such as laptops or tablets with touch-sensitive surfaces (e.g., touchscreen displays and / or touchpads). It should also be understood that in some embodiments, the device is not a portable communication device, but a desktop computer with touch-sensitive surfaces (e.g., touchscreen displays and / or touchpads).

[0048] The following discussion describes a computer system in the form of an electronic device including a display and a touch-sensitive surface. 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.

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

[0050] Various applications running on this device may 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 the corresponding information displayed on the device may optionally be adjusted and / or varied for different applications, and / or within the respective applications. In this way, the common physical architecture of the device (such as the touch-sensitive surface) may optionally utilize a user interface that is intuitive and clear to the user to support various applications.

[0051] Now let’s turn our attention to implementation schemes for computer systems, such as portable devices with touch-sensitive displays. Figure 1AThis is a block diagram illustrating a computer system 100 having a touch-sensitive display system 112 according to some embodiments. The touch-sensitive display system 112 is sometimes referred to as a "touchscreen" for convenience, and sometimes simply as a touch-sensitive display. 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 interface 118, RF circuitry 108, audio circuitry 110, a speaker 111, a microphone 113, an input / output (I / O) subsystem 106, other input or control devices 116, and an external port 124. Device 100 optionally includes one or more optical sensors 164. Device 100 optionally includes one or more intensity sensors 165 (e.g., touch-sensitive surfaces, such as the touch-sensitive display system 112 of device 100) for detecting the intensity of contact on device 100. Device 100 may optionally include one or more haptic output generators 167 for generating haptic output on device 100 (e.g., generating haptic output on a touch-sensitive surface such as the touch-sensitive display system 112 of device 100 or the touchpad 355 of device 300). These components may optionally communicate via one or more communication buses or signal lines 103.

[0052] As used in this specification and claims, the term "haptic output" refers to a physical displacement of the 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., the housing), or a displacement of a component relative to the center of mass of the device, which is detected by the user using the user's tactile sense. For example, when the device or a component of the device comes into contact with a touch-sensitive surface (e.g., a finger, palm, or other part of the user's hand), the haptic output generated by the physical displacement will be interpreted by the user as a tactile sensation corresponding to a perceived change in the physical characteristics of the device or a component of the device. For example, movement of a touch-sensitive surface (e.g., a touch-sensitive display or touchpad) may optionally be interpreted by the user as a "press-click" or "release-click" on a physically actuated button. In some cases, the user will feel a tactile sensation, such as a "press-click" or "release-click," even when a physically actuated button associated with the touch-sensitive surface, which has been physically pressed (e.g., displaced) by the user's movement, does not move. For example, even when the smoothness of a touch-sensitive surface remains unchanged, movement of that surface can optionally be interpreted or sensed by the user as “roughness.” While such interpretations of touch by a user will be limited by the user’s individualized sensory perceptions, many sensory perceptions of touch are common to most users. Therefore, when haptic output is described as corresponding to a user’s specific sensory perception (e.g., “release click,” “press click,” “roughness”), unless otherwise stated, the generated haptic output corresponds to a physical displacement of the device or its components that will generate the sensory perception described by a typical (or average) user. Providing haptic feedback to the user using haptic output enhances device operability and makes the user device interface more efficient (e.g., by helping users provide appropriate input and reducing user errors when operating / interacting with the device). This also further reduces power consumption and extends device battery life by enabling users to use the device more quickly and efficiently.

[0053] In some implementations, the haptic output mode specifies the characteristics of the haptic output, such as the amplitude of the haptic output, the shape of the motion waveform of the haptic output, the frequency of the haptic output, and / or the duration of the haptic output.

[0054] When a device (e.g., one or more tactile output generators that generate tactile output via a movable mass) generates tactile output with different tactile output modes, the tactile output can produce different tactile sensations for a user holding or touching the device. While the user's senses are based on their perception of the tactile output, most users will be able to recognize variations in the waveform, frequency, and amplitude of the tactile output generated by the device. Therefore, the waveform, frequency, and amplitude can be adjusted to indicate to the user that different actions have been performed. Thus, tactile output with tactile output modes designed, selected, and / or arranged to simulate the characteristics (e.g., size, material, weight, stiffness, smoothness, etc.); behaviors (e.g., oscillation, displacement, acceleration, rotation, extension, etc.); and / or interactions (e.g., collision, adhesion, repulsion, attraction, friction, etc.) of objects in a given environment (e.g., a user interface including graphical features and objects, a simulated physical environment with virtual boundaries and virtual objects, a real physical environment with physical boundaries and physical objects, and / or any combination thereof), will in some cases provide helpful feedback to the user, reducing input errors and improving the efficiency of the user's operation of the device. Additionally, haptic output can optionally be generated as feedback independent of the simulated physical characteristics, such as input thresholds or object selection. Such haptic output can provide helpful feedback to the user in some cases, reducing input errors and improving the efficiency of user operation of the device.

[0055] In some implementations, haptic output with an appropriate haptic output mode serves as a cue for an event of interest occurring in the user interface or behind the screen of the device. Examples of events of interest include activation of a power indication provided on the device or in the user interface (e.g., a real or virtual button, or a toggle switch), success or failure of a requested operation, reaching or crossing a boundary in the user interface, entering a new state, switching input focus between objects, activating a new mode, reaching or crossing an input threshold, detecting or recognizing a type of input or gesture, and so on. In some implementations, haptic output is provided to serve as a warning or alert about an impending event or outcome that will occur unless a change of orientation or interruption of input is detected in a timely manner. Haptic output is also used in other contexts to enrich the user experience, improve the accessibility of the device for users with visual or motor difficulties or other accessibility needs, and / or improve the efficiency and functionality of the user interface and / or the device. Optionally, haptic output can be compared with changes in audio input and / or the visual user interface, which further enhances the user experience when interacting with the user interface and / or the device, facilitates better transmission of information about the state of the user interface and / or the device, and reduces input errors and improves the efficiency of user operation of the device.

[0056] It should be understood that device 100 is merely an example of a portable multifunctional device, and device 100 may optionally have more or fewer components than those shown, may optionally combine two or more components, or may optionally have different configurations or arrangements of these components. Figure 1A The various components shown are implemented in hardware, software, firmware, or any combination thereof, including one or more signal processing circuits and / or application-specific integrated circuits.

[0057] Memory 102 may optionally include high-speed random access memory, and may also optionally include non-volatile memory, such as one or more disk storage devices, flash memory devices, or other non-volatile solid-state memory devices. Access to memory 102 by other components of device 100, such as CPU 120 and peripheral interface 118, may optionally be controlled by memory controller 122.

[0058] Peripheral interface 118 can be used to couple the device's input peripherals and output peripherals to CPU 120 and memory 102. One or more processors 120 run or execute various software programs and / or instruction sets stored in memory 102 to perform various functions of device 100 and process data.

[0059] In some implementations, the peripheral interface 118, CPU 120, and memory controller 122 are optionally implemented on a single chip, such as chip 104. In other implementations, they are optionally implemented on separate chips.

[0060] RF (Radio Frequency) circuit 108 receives and transmits RF signals, also known as electromagnetic signals. RF circuit 108 converts electrical signals into electromagnetic signals / converts electromagnetic signals into electrical signals, and communicates with communication networks and other communication devices via electromagnetic signals. RF circuit 108 may optionally include well-known circuitry 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, subscriber identity module (SIM) cards, memory, etc. RF circuit 108 may optionally communicate wirelessly with networks (such as the Internet (also known as the World Wide Web (WWW)), intranets, and / or wireless networks (such as cellular telephone networks, wireless local area networks (LANs), and / or metropolitan area networks (MANs))) and other devices. This 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), Evolved Pure Data (EV-DO), HSPA, HSPA+, Dual-Unit HSPA (DC-HSPA), Long Term Evolution (LTE), Near Field Communication (NFC), Wideband Code Division Multiple Access (W-CDMA), Code Division Multiple Access (CDMA), Time Division Multiple Access (DMA), Bluetooth, and Wi-Fi (e.g., IEEE 802.11a, IEEE 802.11ac, IEEE 802.11ax, IEEE 802.11b, IEEE 802.11g and / or IEEE 802.11n), Voice over Internet Protocol (VoIP), Wi-MAX, email protocols (e.g., Internet Messaging 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 with Extended Utility (SIMPLE), Instant Messaging and Presence Service (MPS)), and / or Short Message Service (SMS), or any other suitable communication protocol including those not yet developed as of the date of this document submission.

[0061] Audio circuitry 110, speaker 111, and microphone 113 provide an audio interface between the user and device 100. Audio circuitry 110 receives audio data from peripheral interface 118, converts the audio data into electrical signals, and sends the electrical signals to speaker 111. Speaker 111 converts the electrical signals into sound waves that are audible to humans. Audio circuitry 110 also receives electrical signals converted from sound waves by microphone 113. Audio circuitry 110 converts the electrical signals into audio data and sends the audio data to peripheral interface 118 for processing. Audio data may optionally be retrieved from memory 102 and / or sent to RF circuitry 108 by peripheral interface 118. In some embodiments, audio circuitry 110 also includes a headset jack (e.g., ...). Figure 2 (212 in the text). The headset jack provides an interface between the audio circuitry 110 and a removable audio input / output peripheral device, such as an output-only headset or a headset with both outputs (e.g., a single-ear or dual-ear headset) and inputs (e.g., a microphone).

[0062] I / O subsystem 106 couples input / output peripherals on device 100, such as touch-sensitive display system 112 and other input or control devices 116, to peripheral interface 118. I / O subsystem 106 optionally includes display controller 156, optical sensor controller 158, intensity sensor controller 159, haptic feedback controller 161, and one or more input controllers 160 for other input or control devices. One or more input controllers 160 receive electrical signals from / send electrical signals to other input or control devices 116. Other input control devices 116 optionally include physical buttons (e.g., push-buttons, rocker buttons, etc.), dial pads, slide switches, joysticks, click wheels, etc. In some alternative embodiments, one or more input controllers 160 may optionally be coupled to (or not coupled to) any of the following: keyboard, infrared port, USB port, stylus, and / or pointing device such as mouse. One or more buttons (e.g., Figure 2 208 in the document may optionally include an up / down button (e.g., a single button that shakes in opposite directions, or separate up and down buttons) for volume control of the speaker 111 and / or microphone 113. One or more buttons may optionally include a push-down button (e.g., Figure 2 (206 in the middle).

[0063] The touch-sensitive display system 112 provides input and output interfaces between the device and the user. The display controller 156 receives electrical signals from and / or sends electrical signals to the touch-sensitive display system 112. The touch-sensitive display system 112 displays visual output to the user. Visual output may optionally include graphics, text, icons, video, and any combination thereof (collectively, "graphics"). In some embodiments, some or all of the visual output corresponds to a user interface object. As used herein, the term "enabled representation" refers to a user-interactive graphical user interface object (e.g., a graphical user interface object configured to respond to input directed to it). Examples of user-interactive graphical user interface objects include, but are not limited to, buttons, sliders, icons, selectable menu items, switches, hyperlinks, or other user interface controls.

[0064] The touch-sensitive display system 112 has a touch-sensitive surface, sensor, or sensor array that accepts input from a user based on tactile and / or tactile contact. The touch-sensitive display system 112 and the display controller 156 (along with any associated modules and / or instruction sets in memory 102) detect contact on the touch-sensitive display system 112 (and any movement or interruption of that contact) and translate the detected contact into interaction with user interface objects (e.g., one or more soft keys, icons, web pages, or images) displayed on the touch-sensitive display system 112. In some embodiments, the point of contact between the touch-sensitive display system 112 and the user corresponds to the user's finger or stylus.

[0065] The touch-sensitive display system 112 may optionally use LCD (Liquid Crystal Display) technology, LPD (Light Emitting Polymer Display) technology, or LED (Light Emitting Diode) technology, but other display technologies are used in other embodiments. The touch-sensitive display system 112 and display controller 156 may optionally use any of a variety of touch sensing technologies now known or to be developed hereafter, along with other proximity sensor arrays or other elements for determining one or more points of contact with the touch-sensitive display system 112, to detect contact and any movement or interruption therein. These various touch sensing technologies include, but are not limited to, capacitive, resistive, infrared, and surface acoustic wave technologies. In some embodiments, projected mutual capacitance sensing technology is used, such as that used in the iPhone from Apple Inc. (Cupertino, California). ® iPod Touch ® and iPad ® The technology discovered in [the text].

[0066] The touch-sensitive display system 112 optionally has a video resolution exceeding 100 dpi. In some embodiments, the touchscreen video resolution exceeds 400 dpi (e.g., 500 dpi, 800 dpi, or greater). Users may optionally use any suitable object or attachment such as a stylus, finger, etc., to interact with the touch-sensitive display system 112. In some embodiments, the user interface is designed to work with finger-based touch and gestures, which may be less precise than stylus-based input due to the larger contact area of ​​a finger on the touchscreen. In some embodiments, the device translates coarse finger-based input into precise pointer / cursor positioning or commands for performing the user-desired actions.

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

[0068] The device 100 also includes a power system 162 for supplying power to various components. The power system 162 may optionally include a power management system, one or more charging 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., light-emitting diodes (LEDs)), and any other components associated with the generation, management, and distribution of power in the portable device.

[0069] The device 100 may also include one or more optical sensors 164 (e.g., as part of one or more cameras). Figure 1A An optical sensor coupled to an optical sensor controller 158 in the I / O subsystem 106 is shown. One or more optical sensors 164 optionally include charge-coupled devices (CCDs) or complementary metal-oxide-semiconductor (CMOS) phototransistors. The one or more optical sensors 164 receive light projected through one or more lenses from the environment and convert the light into data representing an image. In conjunction with an imaging module 143 (also referred to as a camera module), the one or more optical sensors 164 optionally capture still images and / or video. In some embodiments, the optical sensor is located on the rear of the device 100, opposite to the touch-sensitive display system 112 on the front of the device, enabling the touchscreen to be used as a viewfinder for still image and / or video image acquisition. In some embodiments, another optical sensor is located on the front of the device to acquire images of the user (e.g., for selfies, for video conferencing when the user is viewing other video conference participants on the touchscreen, etc.).

[0070] The device 100 may optionally also include one or more contact strength sensors 165. Figure 1A A contact strength sensor coupled to a strength sensor controller 159 in I / O subsystem 106 is shown. One or more contact strength sensors 165 may optionally include one or more piezoresistive strain gauges, capacitive force sensors, electro-force sensors, piezoelectric sensors, optical force sensors, capacitive touch-sensitive surfaces, or other strength sensors (e.g., sensors for measuring the force (or pressure) of contact on a touch-sensitive surface). One or more contact strength sensors 165 receive contact strength information (e.g., pressure information or a substitute for pressure information) from the environment. In some embodiments, at least one contact strength sensor is arranged juxtaposed with or adjacent to a touch-sensitive surface (e.g., touch-sensitive display system 112). In some embodiments, at least one contact strength sensor is located on the rear of device 100 opposite to the touch-sensitive display system 112 located on the front of device 100.

[0071] The device 100 may optionally also include one or more proximity sensors 166. Figure 1A A proximity sensor 166 coupled to a peripheral device interface 118 is shown. Alternatively, the proximity sensor 166 is coupled to an input controller 160 in an I / O subsystem 106. In some embodiments, the proximity sensor turns off and disables the touch-sensitive display system 112 when the multifunction device is placed near the user's ear (e.g., when the user is making a phone call).

[0072] The device 100 may optionally also include one or more tactile output generators 167. Figure 1AA haptic output generator coupled to a haptic feedback controller 161 in I / O subsystem 106 is shown. In some embodiments, the haptic output generator 167 includes one or more electroacoustic devices such as speakers or other audio components; and / or electromechanical devices such as motors, solenoids, electroactive polymerizers, piezoelectric actuators, electrostatic actuators, or other haptic output generating components (e.g., components for converting electrical signals into haptic outputs on the device). The haptic output generator 167 receives haptic feedback generation instructions from haptic feedback module 133 and generates a haptic output on device 100 that can be sensed by a user of device 100. In some embodiments, at least one haptic output generator is juxtaposed or adjacent to a haptic surface (e.g., haptic display system 112) and optionally generates the haptic output by moving the haptic surface vertically (e.g., in / outward from the surface of device 100) or laterally (e.g., back and forth in the same plane as the surface of device 100). In some embodiments, at least one tactile output generator sensor is located on the rear of the device 100, opposite to the touch-sensitive display system 112 located on the front of the device 100.

[0073] The device 100 may optionally also include one or more accelerometers 168. Figure 1A An accelerometer 168 coupled to a peripheral interface 118 is shown. Alternatively, the accelerometer 168 may be coupled to an input controller 160 in an I / O subsystem 106. In some embodiments, information is displayed on a touchscreen display in portrait or landscape view based on analysis of data received from the one or more accelerometers. The device 100 may optionally include, in addition to the accelerometer 168, a magnetometer and a GPS (or GLONASS or other global navigation system) receiver for acquiring information about the location and orientation (e.g., portrait or landscape) of the device 100.

[0074] In some embodiments, software components stored in memory 102 include an operating system 126, a communication module (or instruction set) 128, a touch / motion module (or instruction set) 130, a graphics module (or instruction set) 132, a haptic feedback module (or instruction set) 133, 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. Furthermore, in some embodiments, memory 102 stores device / global internal state 157, as shown in Figures 1A and 1B. Figure 3As shown in the diagram, the device / global internal state 157 includes one or more of the following: active application state, which indicates which applications (if any) are currently active; display state, which indicates what applications, views or other information occupy the various areas of the touch-sensitive display system 112; sensor state, which includes information obtained from the various sensors of the device and other input or control devices 116; and position and / or location information about the position and / or orientation of the device.

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

[0076] The communication module 128 facilitates communication with other devices via one or more external ports 124 and includes various software components for processing data received by the RF circuitry 108 and / or the external ports 124. The external ports 124 (e.g., Universal Serial Bus (USB), FireWire, etc.) are adapted to be directly coupled to other devices or indirectly coupled via a network (e.g., the Internet, wireless LAN, etc.). In some embodiments, the external port is compatible with some iPhones from Apple Inc. (Cupertino, California). ® iPod Touch ® and iPad ® The device uses the same or similar and / or compatible multi-pin (e.g., 30-pin) connectors as the 30-pin connector used in the device. In some implementations, the external port is compatible with some iPhones from Apple Inc. (Cupertino, California). ® iPod Touch ® and iPad ® The device uses the same or similar and / or compatible Lightning connector. In some implementations, the external port is a USB Type-C connector that is the same or similar and / or compatible with the USB Type-C connector used in some electronic devices of Apple Inc. (Cupertino, California).

[0077] The contact / motion module 130 optionally detects contact with the touch-sensitive display system 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 (e.g., via a finger or stylus), such as determining whether contact has occurred (e.g., detecting a finger press event), determining the intensity of the contact (e.g., the force or pressure of the contact, or an alternative to force or pressure), determining whether there is movement of the contact and tracking movement across the touch-sensitive surface (e.g., detecting one or more finger drag events), and determining whether the contact has stopped (e.g., detecting a finger lift event or a 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 which is represented by a series of contact data. These operations can be optionally applied to single-point contact (e.g., single-finger contact or stylus contact) or simultaneous multi-point contact (e.g., "multi-touch" / multi-finger contact). In some embodiments, the contact / motion module 130 and the display controller 156 detect contact on the touchpad.

[0078] The touch / motion module 130 optionally detects gesture input performed by the user. Different gestures on a touch-sensitive surface have different contact patterns (e.g., different movements, timings, and / or intensities of the detected contact). Therefore, gestures can optionally be detected by detecting specific contact patterns. For example, detecting a single-finger tap gesture includes detecting a finger press event, and then detecting a finger lift-off (lift-away) event at the same (or substantially the same) location as the finger press event (e.g., at the icon location). As another example, detecting a finger swipe gesture on a touch-sensitive surface includes detecting a finger press event, then detecting one or more finger drag events, and subsequently detecting a finger lift-off (lift-away) event. Similarly, stylus taps, swipes, drags, and other gestures can optionally be detected by detecting specific contact patterns of the stylus.

[0079] In some implementations, detecting a finger tap depends on the length of time between a finger press event and a finger lift event, but is independent of the intensity of finger contact during that time. In some implementations, a tap is detected based on the determination that the length of time between a finger press event and a finger lift event is less than a predetermined value (e.g., less than 0.1 seconds, 0.2 seconds, 0.3 seconds, 0.4 seconds, or 0.5 seconds), regardless of whether the intensity of finger contact during the tap reaches a given intensity threshold (greater than a nominal contact detection intensity threshold), such as a light press or deep press intensity threshold. Therefore, a finger tap can satisfy a specific input criterion that does not require the characteristic intensity of the contact to meet a given intensity threshold to satisfy that specific input criterion. For clarity, finger contact in a tap gesture typically needs to meet a nominal contact detection intensity threshold to detect a finger press event; below this threshold, no contact is detected. Similar analysis applies to detecting tap gestures via a stylus or other contact method. When the device is able to detect contact from a finger or stylus hovering above a touch-sensitive surface, the nominal contact detection strength threshold may optionally not correspond to the physical contact between the finger or stylus and the touch-sensitive surface.

[0080] The same concept applies to other types of gestures in a similar manner. For example, swipe gestures, pinch gestures, spread gestures, and / or long press gestures can be optionally detected based on criteria that are independent of the intensity of the contact involved in the gesture or do not require one or more contacts performing the gesture to reach an intensity threshold for recognition. For example, a swipe gesture is detected based on the amount of movement of one or more contacts; a pinch gesture is detected based on the movement of two or more contacts toward each other; a spread gesture is detected based on the movement of two or more contacts away from each other; and a long press gesture is detected based on the duration of contact with less than a threshold amount of movement on a touch-sensitive surface. Therefore, the statement that a particular gesture recognition criterion does not require the contact intensity to meet a corresponding intensity threshold implies that a particular gesture recognition criterion can be met when the contact in the gesture does not reach the corresponding intensity threshold, and also when one or more contacts in the gesture reach or exceed the corresponding intensity threshold. In some implementations, tap gestures are detected based on determining that a finger press event and a finger lift event are detected within a predefined time period, regardless of whether the contact is above or below a corresponding intensity threshold during the predefined time period. Similarly, swipe gestures are detected based on determining that the contact movement is greater than a predefined amount, even if the contact movement ends above a corresponding intensity threshold. Even in specific implementations where gesture detection is affected by the intensity of the contact performing the gesture (e.g., the device detects a long press faster when the contact intensity is above an intensity threshold, or delays the detection of a tap input when the contact intensity is even higher), the detection of these gestures does not require the contact to reach a specific intensity threshold (e.g., even if the amount of time required to recognize the gesture varies).

[0081] In some cases, contact intensity thresholds, duration thresholds, and movement thresholds are combined in various ways to create heuristic algorithms that distinguish between two or more different gestures targeting the same input element or region, allowing for a richer set of user interactions and responses from multiple different interactions with the same input element. Statements that a particular set of gesture recognition criteria does not require the intensity of one or more contacts to meet a corresponding intensity threshold in order to satisfy a particular gesture recognition criterion do not preclude the simultaneous evaluation of other intensity-related gesture recognition criteria to identify other gestures that meet criteria when the gesture includes a contact with an intensity higher than the corresponding intensity threshold. For example, in some cases, a first gesture recognition criterion for a first gesture (which does not require the contact intensity to meet a corresponding intensity threshold to satisfy the first gesture recognition criterion) competes with a second gesture recognition criterion for a second gesture (which depends on the contact reaching the corresponding intensity threshold). In such competition, if the second gesture recognition criterion for the second gesture is satisfied first, the gesture may optionally not be recognized as satisfying the first gesture recognition criterion for the first gesture. For example, if the contact reaches the corresponding intensity threshold before the contact moves a predefined amount of movement, a deep press gesture is detected instead of a swipe gesture. Conversely, if the contact moves a predefined amount of motion before reaching the corresponding intensity threshold, a swipe gesture is detected instead of a deep press gesture. Even in such cases, the first gesture recognition criterion for the first gesture still does not require the contact intensity to meet the corresponding intensity threshold to satisfy the first gesture recognition criterion, because if the contact remains below the corresponding intensity threshold until the gesture ends (e.g., a swipe gesture with a contact intensity that does not increase to above the corresponding intensity threshold), the gesture will be recognized as a swipe gesture by the first gesture recognition criterion. Therefore, a specific gesture recognition criterion that does not require the contact intensity to meet the corresponding intensity threshold to satisfy a specific gesture recognition criterion will (A) in some cases ignore the contact intensity relative to the intensity threshold (e.g., for a tap gesture) and / or (B) in some cases fail to satisfy the specific gesture recognition criterion (e.g., for a long press gesture) if a set of competing intensity-related gesture recognition criteria (e.g., for a deep press gesture) recognize the input as corresponding to an intensity-related gesture before the specific gesture recognition criterion recognizes the gesture corresponding to the input, in this sense, still depend on the contact intensity relative to the intensity threshold (e.g., for a long press gesture that competes with a deep press gesture for recognition).

[0082] The graphics module 132 includes various known software components for rendering and displaying graphics on the touch-sensitive display system 112 or other displays, including components for altering the visual impact of the displayed graphics (e.g., brightness, transparency, saturation, contrast, or other visual properties). As used herein, the term "graphics" includes any object that can be displayed to a user, and non-limitingly includes text, web pages, icons (such as user interface objects including soft keys), digital images, videos, animations, etc.

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

[0084] The haptic feedback module 133 includes various software components for generating instructions (e.g., instructions used by the haptic feedback controller 161) to generate haptic output at one or more locations on the device 100 using the haptic output generator 167 in response to user interaction with the device 100.

[0085] Optionally, the text input module 134, which is a component of the graphics module 132, provides a soft keyboard for entering text in various applications, such as contacts 137, email 140, IM 141, browser 147, and any other application that requires text input.

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

[0087] Application 136 may optionally include the following modules (or instruction sets) or subsets or supersets thereof: • Contacts module 137 (sometimes called address book or contact list); • Telephone module 138; • Video conferencing module 139; • Email client module 140; • Instant Messaging (IM) module 141; • Fitness support module 142; • Camera module 143 for still images and / or video images; • Image management module 144; • Browser module 147; • Calendar module 148; • Widget module 149, which may optionally include one or more of the following: weather widget 149-1, stock market widget 149-2, calculator widget 149-3, alarm clock widget 149-4, dictionary widget 149-5, and other widgets acquired by the user, and user-created widgets 149-6. • Widget creator module 150 for creating user-created widgets 149-6; • Search module 151; •Optionally, a video and music player module 152 consisting of a video player module and a music player module; •Notepad module 153; • Map module 154; and / or • Online video module 155.

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

[0089] In conjunction with the touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, and text input module 134, the contact module 137 includes executable instructions for managing an address book or contact list (e.g., in application internal state 192 of the contact module 137 stored in memory 102 or memory 370), including: adding 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 and / or email addresses to initiate and / or facilitate communication via telephone 138, video conferencing 139, email 140, or IM 141; etc.

[0090] Combining RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, and text input module 134, telephone module 138 includes executable instructions for performing the following operations: entering a character sequence corresponding to a telephone number, accessing one or more telephone numbers in the address book 137, modifying an entered telephone number, dialing a corresponding telephone number, initiating a conversation, and disconnecting or hanging up when the conversation is complete. As described above, wireless communication may optionally use any of a variety of communication standards, protocols, and technologies.

[0091] Combining RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch-sensitive display system 112, display controller 156, one or more optical sensors 164, optical sensor controller 158, contact module 130, graphics module 132, text input module 134, contact list 137, and telephone module 138, video conferencing module 139 includes executable instructions to initiate, conduct, and terminate video conferences between the user and one or more other participants based on user instructions.

[0092] Incorporating RF circuitry 108, touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, and text input module 134, email client module 140 includes executable instructions for creating, sending, receiving, and managing emails in response to user commands. Combined with image management module 144, email client module 140 makes it very easy to create and transmit emails containing still images or video images captured by camera module 143.

[0093] In conjunction with RF circuitry 108, touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, and text input module 134, instant messaging module 141 includes executable instructions for performing the following operations: inputting a character sequence corresponding to an instant message, modifying previously input characters, transmitting a corresponding instant message (e.g., using Short Message Service (SMS) or Multimedia Messaging Service (MMS) protocols for telephone-based instant messaging or using XMPP, SIMPLE, Apple Push Notification Service (APN), or IMPS protocols for internet-based instant messaging), receiving an instant message, and viewing a received instant message. 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 message" refers to both telephone-based messages (e.g., messages sent using SMS or MMS) and internet-based messages (e.g., messages sent using XMPP, SIMPLE, APNs, or IMPS).

[0094] Incorporating RF circuitry 108, touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, text input module 134, GPS module 135, map module 154, and video and music player module 152, fitness support module 142 includes executable instructions for creating fitness (e.g., with time, distance, and / or calorie burning goals); communicating with fitness sensors (in sports equipment and smartwatches); receiving fitness sensor data; calibrating sensors used for monitoring fitness; selecting and playing music for fitness; and displaying, storing, and transmitting fitness data.

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

[0096] In conjunction with the touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, text input module 134, and camera module 143, the image management module 144 includes executable instructions for arranging, modifying (e.g., editing), or otherwise manipulating, tagging, deleting, displaying (e.g., in a digital slideshow or photo album), and storing still images and / or video images.

[0097] Combining RF circuitry 108, touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, and text input module 134, browser module 147 includes executable instructions for browsing the Internet (including searching, linking to, receiving, and displaying web pages or portions thereof, as well as attachments and other files linked to web pages) according to user instructions.

[0098] Incorporating RF circuitry 108, touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, text input module 134, email client module 140, and browser module 147, calendar module 148 includes executable instructions for creating, displaying, modifying, and storing calendars and associated data (e.g., calendar entries, to-dos, etc.) according to user instructions.

[0099] In conjunction with RF circuitry 108, touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, text input module 134, and browser module 147, widget module 149 is optionally a mini-application downloaded and used by a user (e.g., weather widget 149-1, stock market widget 149-2, calculator widget 149-3, alarm clock widget 149-4, and dictionary widget 149-5) or a user-created mini-application (e.g., user-created widget 149-6). In some embodiments, the widget includes HTML (Hypertext Markup Language) files, CSS (Cascading Style Sheets) files, and JavaScript files. In some embodiments, the widget includes XML (Extensible Markup Language) files and JavaScript files (e.g., Yahoo! widgets).

[0100] In conjunction with RF circuitry 108, touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, text input module 134, and browser module 147, widget creator module 150 includes executable instructions for creating widgets (e.g., transferring user-specified portions of a webpage into a widget).

[0101] In conjunction with the touch-sensitive display system 112, display controller 156, contact 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) according to user instructions.

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

[0103] In conjunction with the touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, and text input module 134, the notepad module 153 includes executable instructions for creating and managing notes, to-do items, etc., according to user instructions.

[0104] Combining RF circuitry 108, touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, text input module 134, GPS module 135, and browser module 147, map module 154 includes executable instructions for receiving, displaying, modifying, and storing maps and map-related data (e.g., driving directions; data on shops and other points of interest at or near specific locations; and other location-based data) according to user instructions.

[0105] In conjunction with the touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, text input module 134, email client module 140, and browser module 147, the online video module 155 includes executable instructions that allow users to access, browse, receive (e.g., via streaming and / or downloading), play back (e.g., on the touchscreen 112, or on an external display connected wirelessly or via external port 124), send emails with links to specific online videos, and otherwise manage online videos in one or more file formats such as H.264. In some embodiments, an instant messaging module 141 is used instead of the email client module 140 to deliver links to specific online videos.

[0106] Each module and application identified above corresponds to a set of executable instructions for performing one or more of the functions described above and the methods described in this application (e.g., computer-implemented methods and other information processing methods described herein). These modules (e.g., instruction sets) need not be implemented as standalone software programs, processes, or modules; therefore, various subsets of these modules may optionally be combined or otherwise rearranged in various embodiments. In some embodiments, memory 102 may optionally store a subset of the modules and data structures described above. Furthermore, memory 102 may optionally store additional modules and data structures not described above.

[0107] In some implementations, device 100 is a device on which the operation of a predefined set of functions is performed solely via a touchscreen and / or touchpad. By using a touchscreen and / or touchpad as the primary input control device for operating device 100, the number of physical input control devices (such as push-buttons and dial pads) on device 100 can be optionally reduced.

[0108] A predefined set of functions, uniquely performed via a touchscreen and / or touchpad, may optionally include navigation between user interfaces. In some embodiments, the touchpad, when touched by a user, navigates device 100 from any user interface displayed on device 100 to the main menu, home screen menu, or root menu. In such embodiments, a "menu button" is implemented using the touchpad. In some other embodiments, the menu button is a physical push-button or other physical input control device, rather than a touchpad.

[0109] In some implementations, gestures include air gestures. An air gesture is a gesture detected without the user touching an input element that is part of the device (e.g., computer system 101, one or more input devices 125 and / or hand tracking device 140) (or independent of an input element that is part of the device) and based on the detected movement of a part of the user's body (e.g., head, one or two arms, one or two hands, one or more fingers and / or one or two legs) through the air (including movement of the user's body relative to an absolute reference (e.g., 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 (e.g., 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 (e.g., including a tapping gesture in which the hand moves a predetermined amount and / or speed in a predetermined pose, or a shaking gesture including a predetermined speed or amount of rotation of a part of the user's body)).

[0110] In some embodiments, the input gestures used in the various examples and embodiments described herein include air gestures for interacting with an XR environment (e.g., a virtual or mixed reality environment) performed by the movement of a user's fingers relative to other fingers or portions of the user's hand. In some embodiments, air gestures are detected without the user touching an input element that is part of the device (or independently of an input element that is part of the device) and are based on the 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 (e.g., 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 (e.g., 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 portion of the user's hand), and / or absolute movement of a part of the user's body (e.g., a tapping gesture that includes the hand moving a predetermined amount and / or speed in a predetermined pose, or a shaking gesture that includes a predetermined speed or amount of rotation of a part of the user's body)).

[0111] In some implementations where the input gesture is an air gesture (e.g., where the input device provides information to the computer system about which user interface element is the target of the user input in the absence of physical contact, such as contact with a user interface element displayed on a touchscreen, or contact with a mouse or touchpad to move the cursor to a user interface element), the gesture takes into account the user's attention (e.g., gaze) to determine the target of the user input (e.g., for direct input, as described below). Therefore, in implementations involving air gestures, for example, the input gesture is combined with (e.g., simultaneously) movement of the user's fingers and / or hand to detect attention (e.g., gaze) toward a user interface element to perform pinch and / or tap input, as described below.

[0112] In some implementations, input gestures directed to a user interface object are performed, either directly or indirectly, by referencing the user interface object. For example, user input is performed directly on the user interface object based on the user's hand performing an input gesture at a location corresponding to the user interface object's position in the three-dimensional environment (e.g., determined based on the user's current viewpoint). In some implementations, when user attention to the user interface object (e.g., gazing) is detected, input gestures are performed indirectly on the user interface object based on the user's hand not being positioned at a location corresponding to the user interface object's position in the three-dimensional environment while the user is performing the input gesture. For example, for direct input gestures, the user can guide their input to the user interface object by initiating a gesture at or near a location corresponding to the user interface object's display position (e.g., within 0.5 cm, 1 cm, 5 cm, or a distance between 0 and 5 cm measured from the outer edge or center of the option). For indirect input gestures, the user can guide their input to the user interface object by focusing on it (e.g., by gazing at the user interface object), and while focusing on the option, the user initiates an input gesture (e.g., at any location detectable by the computer system) (e.g., at a location not corresponding to the user interface object's display position).

[0113] In some implementations, the input gestures (e.g., air gestures) used in the various examples and implementations described herein include pinch input and tap input for interacting with a virtual or mixed reality environment. For example, the pinch input and tap input described below are performed as air gestures.

[0114] In some implementations, pinch input is part of an air gesture that includes one or more of the following: a pinch gesture, a long pinch gesture, a pinch and drag gesture, or a double pinch gesture. For example, a pinch gesture as an air gesture includes the movement of two or more fingers of the hand to contact each other, i.e., optionally followed by an immediate (e.g., within 0 to 1 second) interruption of contact. A long pinch gesture as an air gesture includes the movement of two or more fingers of the hand to contact each other for at least a threshold amount of time (e.g., at least 1 second) before an interruption of contact is detected. For example, a long pinch gesture includes the user holding a pinch gesture (e.g., where two or more fingers are in contact), and the long pinch gesture continues until an interruption of contact between the two or more fingers is detected. In some implementations, a double pinch gesture as an air gesture includes two (e.g., more) pinch inputs (e.g., performed by the same hand) that are detected consecutively with each other immediately (e.g., within a predefined time period). For example, a user performs a first pinch input (e.g., a pinch input or a long pinch input), releases the first pinch input (e.g., interrupts the contact between two or more fingers), and performs a second pinch input within a predefined time period after releasing the first pinch input (e.g., within 1 second or within 2 seconds).

[0115] In some embodiments, pinch-and-drag gestures as air gestures (e.g., air drag gestures or air swipe gestures) include pinch gestures (e.g., pinch gestures or long pinch gestures) performed in conjunction with (e.g., following) a drag input that changes the user's hand position from a first position (e.g., the start position of the drag) to a second position (e.g., the end position of the drag). In some embodiments, the user holds the pinch gesture while performing the drag input and releases the pinch gesture (e.g., opening two or more of their fingers) to end the drag gesture (e.g., at the second position). In some embodiments, the pinch input and drag input are performed by the same hand (e.g., the user pinches two or more fingers together to touch each other and uses the drag gesture to move the same hand to the second position in the air). In some implementations, pinch input is performed by the user's first hand, and drag input is performed by the user's second hand (e.g., while the user continues pinch input with the user's first hand, the user's second hand moves in the air from a first position to a second position). In some implementations, input gestures as air gestures include inputs performed using both of the user's hands (e.g., pinch and / or tap inputs). For example, input gestures include two (e.g., more) pinch inputs performed in combination with each other (e.g., concurrently or within a predefined time period). For example, a first pinch gesture (e.g., pinch input, long pinch input, or pinch and drag input) is performed using the user's first hand, and a second pinch input is performed using the other hand (e.g., the second hand in both of the user's hands). In some implementations, movement between the user's two hands is performed (e.g., increasing and / or decreasing the distance or relative orientation between the user's two hands).

[0116] In some implementations, a tap input performed as an air gesture (e.g., pointing at a user interface element) includes movement of a user's finger toward the user interface element, movement of a user's hand toward the user interface element (optionally, the user's finger extends toward the user interface element), downward movement of a user's finger (e.g., mimicking a mouse click or a tap on a touchscreen), or other predefined movements of the user's hand. In some implementations, the tap input performed as an air gesture is detected based on the movement characteristics of the finger or hand performing the tap gesture movement, which is the finger or hand moving away from the user's viewpoint and / or toward an object that is the target of the tap input, followed by the end of the movement. In some implementations, the end of the movement is detected based on changes in the movement characteristics of the finger or hand performing the tap gesture (e.g., the end of movement away from the user's viewpoint and / or toward an object that is the target of the tap input, a reversal of the direction of finger or hand movement, and / or a reversal of the acceleration direction of finger or hand movement).

[0117] In some implementations, the user's attention is determined to be directed to a portion of the 3D environment based on the detection of a gaze directed to that portion of the 3D environment (optionally, no other conditions are required). In some implementations, the user's attention is determined to be directed to that portion of the 3D environment based on the detection of a gaze directed to that portion of the 3D environment using one or more additional conditions, such as requiring the gaze to be directed to that portion of the 3D environment for at least a threshold duration (e.g., dwell time) and / or requiring the gaze to be directed to that portion of the 3D environment when the user's viewpoint is within a distance threshold from that portion of the 3D environment, so that the device determines that the user's attention is directed to that portion of the 3D environment, wherein if one of these additional conditions is not met, the device determines that the attention is not directed to the portion of the 3D environment to which the gaze is directed (e.g., until the one or more additional conditions are met).

[0118] In some implementations, the detection of the readiness configuration of a user or a portion of a user is performed by a computer system. The detection of the hand's readiness configuration is used by the computer system as an indication that the user may be preparing to interact with the computer system using one or more air gesture inputs performed by the hand (e.g., pinch, tap, pinch and drag, double pinch, long pinch, or other air gestures described herein). For example, the readiness of the hand is determined based on whether it has a predetermined hand shape (e.g., a pre-pinch shape with the thumb and one or more fingers extended and spaced apart in preparation for a pinch or grasping gesture, or a pre-tap with one or more fingers extended and the back of the hand facing the user), whether the hand is in a predetermined position relative to the user's viewpoint (e.g., below the user's head and above the user's waist and extending at least 15 cm, 20 cm, 25 cm, 30 cm, or 50 cm from the body), and / or whether the hand has moved in a particular manner (e.g., moving towards an area in front of the user above the user's waist and below the user's head, or moving away from the user's body or legs). In some implementations, the readiness state is used to determine whether an interactive element of the user interface responds to attentional (e.g., gaze) input.

[0119] In scenarios where input is described by reference to air gestures, it should be understood that hardware input devices attached to or held by one or both of the user's hands can be used to detect such gestures. Optical tracking, one or more accelerometers, one or more gyroscopes, one or more magnetometers and / or one or more inertial measurement units can be used to track the spatial positioning of the hardware input device, and the positioning and / or movement of the hardware input device can be used in place of the positioning and / or movement of one or both hands in relation to the corresponding air gesture. In scenarios describing input using air gestures, it should be understood that similar gestures can be detected using hardware input devices attached to or held by one or both of the user's hands. User input can be detected using controls contained within the hardware input device, such as one or more touch-sensitive input elements, one or more pressure-sensitive input elements, one or more buttons, one or more knobs, one or more dials, one or more joysticks, one or more hand or finger covers that can detect the positioning or changes in positioning of parts of the hand and / or fingers relative to each other, relative to the user's body, and / or relative to the user's physical environment, and / or other hardware input device controls. User input using controls contained within the hardware input device replaces hand and / or finger gestures such as air taps or air pinches in the corresponding air gesture. For example, a selection input described as being performed using an air tap or air pinch input can alternatively be detected using button presses, taps on touch-sensitive surfaces, presses on pressure-sensitive surfaces, or other hardware inputs. As another example, motion input described as being performed using air pinch and drag (e.g., air drag gestures or air swipe gestures) can be optionally detected based on interaction with hardware input controls (such as button press and hold, touch on a touch-sensitive surface, press on a pressure-sensitive surface, or other hardware input following movement of a hardware input device (e.g., a hand associated with the hardware input device) through space). Similarly, two-handed input involving movement of hands relative to each other can be performed using an air gesture and a hardware input device not in the hand performing the air gesture, two hardware input devices held in different hands, or two air gestures performed by different hands using air gestures and / or inputs detected by one or more of the aforementioned hardware input devices.

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

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

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

[0123] Event monitor 171 receives event information from peripheral device interface 118. The event information includes information about sub-events, such as user touches on touch-sensitive display system 112 as part of a multi-touch gesture. Peripheral device interface 118 transmits information it receives from I / O subsystem 106 or sensors such as proximity sensor 166, one or more accelerometers 168, and / or microphone 113 (via audio circuitry 110). The information received by peripheral device interface 118 from I / O subsystem 106 includes information from touch-sensitive display system 112 or touch-sensitive surfaces.

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

[0125] In some implementations, the event classifier 170 also includes a hit view determination module 172 and / or an activity event recognizer determination module 173.

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

[0127] Another aspect of the user interface associated with an application is a set of views, sometimes referred to herein as application views or user interface windows, in which information is displayed and touch-based gestures occur. The application view (of the corresponding application) in which a touch is detected optionally corresponds to a procedural level within the application's procedural or view hierarchy. For example, the lowest-level view in which a touch is detected may optionally be called the hit view, and the set of events identified as correct input may optionally be determined at least in part based on the hit view of the initial touch that initiates the touch-based gesture.

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

[0129] The activity event recognizer determination module 173 determines which views(s) within the view hierarchy should receive a specific sub-event sequence. In some embodiments, the activity event recognizer determination module 173 determines that only the hit view should receive the specific sub-event sequence. In other embodiments, the activity event recognizer determination module 173 determines that all views including the physical location of the sub-event are actively participating views, and therefore determines that all actively participating views should receive the specific sub-event sequence. In other embodiments, even if the touch sub-event is entirely confined to the area associated with a particular view, higher views in the hierarchy will still remain actively participating views.

[0130] Event assigner module 174 assigns event information to event identifiers (e.g., event identifier 180). In embodiments that include active event identifier determination module 173, event assigner module 174 delivers event information to the event identifier determined by active event identifier determination module 173. In some embodiments, event assigner module 174 stores event information in an event queue, which is retrieved by the corresponding event receiver module 182.

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

[0132] In some implementations, application 136-1 includes a plurality of 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 application's user interface. Each application view 191 of application 136-1 includes one or more event recognizers 180. Typically, a corresponding application view 191 includes a plurality of event recognizers 180. In other implementations, one or more of the event recognizers 180 are part of a separate module, such as a user interface toolkit or a higher-level object from which application 136-1 inherits methods and other properties. In some implementations, a corresponding event handler 190 includes one or more of the following: a data updater 176, an object updater 177, a GUI updater 178, and / or event data 179 received from an event classifier 170. Event handlers 190 may optionally utilize or invoke the data updater 176, the object updater 177, or the GUI updater 178 to update the application's internal state 192. Alternatively, one or more application views in application view 191 include one or more corresponding event handlers 190. Additionally, in some embodiments, one or more of data updater 176, object updater 177, and GUI updater 178 are included in the corresponding application view 191.

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

[0134] Event receiver 182 receives event information from event classifier 170. The 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 touch movement, the event information may optionally also include the speed and direction of the sub-event. In some embodiments, the event includes the device rotating from one orientation to another (e.g., from a portrait orientation to a lateral orientation, or vice versa), and the event information includes corresponding information about the device's current orientation (also referred to as device orientation).

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

[0136] In some implementations, event definition 187 includes definitions of events for corresponding user interface objects. In some implementations, event comparator 184 performs a hit test to determine which user interface object is associated with the sub-event. For example, in an application view displaying three user interface objects on a touch-sensitive display system 112, when a touch is detected on the touch-sensitive display system 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 the event handler associated with the sub-event and the object that triggered the hit test.

[0137] In some implementations, the definition of the corresponding event 187 also includes delay actions that delay the delivery of event information until it has been determined whether the sub-event sequence actually corresponds to or does not correspond to the event type of the event recognizer.

[0138] When the corresponding event recognizer 180 determines that the sub-event sequence 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 based on touch gestures are ignored. In this case, other event recognizers (if any) that remain active in the hit view continue to track and process the ongoing sub-events based on touch gestures.

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

[0140] In some implementations, when one or more specific sub-events of an event are identified, the corresponding event recognizer 180 activates the event handler 190 associated with the event. In some implementations, 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 delivering (and deferred delivering) the sub-events to the corresponding hit view. In some implementations, the event recognizer 180 throws a flag associated with the identified event, and the event handler 190 associated with the flag acquires the flag and performs a predefined process.

[0141] In some implementations, event delivery instruction 188 includes 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 the sub-event sequence or to an actively participating view. The event handler associated with the sub-event sequence or the actively participating view receives the event information and performs a predetermined process.

[0142] In some implementations, 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 or music player module 152. In some implementations, 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 that display information to graphics module 132 for display on a touch-sensitive display.

[0143] In some implementations, event handler 190 includes, or has access to, a data updater 176, an object updater 177, and a GUI updater 178. In some implementations, 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 implementations, they are included in two or more software modules.

[0144] It should be understood that the above discussion regarding event handling for user touch on a touch-sensitive display also applies to other forms of user input used to operate the multifunction device 100 using an input device, and not all user input is initiated on the touchscreen. For example, mouse movement and mouse button presses optionally in conjunction with single or multiple keyboard presses or holds; touch movements on the touchpad, such as taps, drags, scrolls, etc.; stylus input; device movement; verbal commands; detected eye movements; biometric input; and / or any combination thereof may optionally be used as input corresponding to sub-events that define the event to be identified.

[0145] Figure 2 Examples are given of devices with touchscreens (e.g., according to some implementation schemes). Figure 1AA computer system 100 includes a touch-sensitive display system 112. The touchscreen optionally displays one or more graphics within a user interface (UI) 200. In these embodiments and other embodiments described below, a user can select one or more graphics by gesturing over the graphics, for example, using one or more fingers 202 (not drawn to scale in the figures) or one or more styluses 203 (not drawn to scale in the figures). In some embodiments, selection of one or more graphics occurs when the user breaks contact with the graphics. In some embodiments, gestures optionally include one or more taps, one or more swipes (from left to right, from right to left, up and / or down), and / or scrolling (from right to left, from left to right, up and / or down) of a finger already in contact with the device 100. In some embodiments or in some cases, unintentional contact with a graphic does not select the graphic. For example, a swipe gesture over an application icon may optionally not select the corresponding application when the gesture corresponding to selection is a tap.

[0146] Device 100 may optionally also include one or more physical buttons, such as a "home screen" or menu button 204. As previously described, menu button 204 may optionally be used to navigate to any of a set of applications 136 that may optionally be executed on device 100. Alternatively, in some embodiments, the menu button may be implemented as a soft key in a GUI displayed on a touchscreen display, or as a system gesture such as a swipe up from the edge.

[0147] In some embodiments, device 100 includes a touchscreen display, a menu button 204 (sometimes referred to as a home button 204), a push-button 206 for powering on / off the device and locking the device, a volume control button 208, a SIM card slot 210, a headset jack 212, and / or a docking / charging external port 124. The push-button 206 may optionally be used to: power on / off the device by pressing the button and holding it in the pressed state for a predefined time interval; lock the device by pressing the button and releasing it before the predefined time interval has elapsed; and / or unlock the device or initiate an unlocking process. In some embodiments, device 100 also accepts voice input via microphone 113 for activating or deactivating certain functions. Device 100 may also optionally include one or more contact strength sensors 165 for detecting contact strength on the touch-sensitive display system 112 and / or one or more haptic output generators 167 for generating haptic outputs for a user of device 100.

[0148] Figure 3This is a block diagram of an example multifunctional device with a display and a touch-sensitive surface according to some embodiments. Device 300 need not be portable. In some embodiments, device 300 is a laptop computer, desktop computer, tablet computer, multimedia player device, navigation device, educational device (such as a children's learning toy), gaming system, or control device (e.g., a home controller or industrial controller). Device 300 typically includes one or more processing units (CPUs) 310, one or more network or other communication interfaces 360, memory 370, and one or more communication buses 320 for interconnecting these components. The communication bus 320 may optionally include circuitry (sometimes referred to as a chipset) that interconnects system components and controls communication between system components. Device 300 includes an input / output (I / O) interface 330 with a display 340, which is typically a touchscreen display. The I / O interface 330 may also optionally include a keyboard and / or mouse (or other pointing device) 350 and a touchpad 355, and a haptic output generator 357 for generating haptic output on device 300 (e.g., similar to the above reference). Figure 1A The described tactile output generator 167) and sensor 359 (e.g., optical sensor, accelerometer, proximity sensor, touch sensor and / or similar to those described above) are referenced in the reference. Figure 1A The contact strength sensor 165 described is a contact strength sensor. Memory 370 includes high-speed random access memory, such as DRAM, SRAM, DDR RAM, or other random access solid-state memory devices; and optionally includes non-volatile memory, such as one or more disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid-state memory devices. Memory 370 optionally includes one or more storage devices located remotely from CPU 310. In some embodiments, memory 370 stores data in computer system 100 (…). Figure 1A The memory 370 stores programs, modules, and data structures similar to those stored in the memory 102 of the computer system 100, or subsets thereof. Additionally, the memory 370 may optionally store additional programs, modules, and data structures not present in the memory 102 of the computer system 100. For example, the memory 370 of the device 300 may optionally store a drawing module 380, a rendering module 382, ​​a word processing module 384, a website creation module 386, a disk editing module 388, and / or a spreadsheet module 390, while the computer system 100 ( Figure 1A The memory 102 may optionally not store these modules.

[0149] Figure 3Each of the elements identified above may optionally be stored in one or more of the previously mentioned memory devices. Each of the modules identified above corresponds to an instruction set for performing the functions described above. The modules or programs identified above (i.e., instruction sets) need not be implemented as standalone software programs, processes, or modules; therefore, various subsets of these modules may optionally be combined or otherwise rearranged in various embodiments. In some embodiments, memory 370 may optionally store a subset of the modules and data structures described above. Furthermore, memory 370 may optionally store additional modules and data structures not described above.

[0150] Now let’s turn our attention to the implementation of the user interface (“UI”) that may be implemented on the computer system 100.

[0151] Figure 4A An example user interface for an application menu on a computer system 100 according to some embodiments is illustrated. A similar user interface may optionally be implemented on device 300. In some embodiments, user interface 400 includes the following elements or a subset or superset thereof: • One or more signal strength indicators for one or more wireless communications, such as cellular signals and Wi-Fi signals; •time; • Bluetooth indicator; • Battery status indicator; • Tray 408 features icons for frequently used applications, such as: ○ The telephone module 138 has an icon 416 labeled "telephone", which optionally includes an indicator 414 indicating the number of missed calls or voicemail messages; ○ An icon 418 labeled "Mail" in the email client module 140, which optionally includes an indicator 410 for the number of unread emails; ○ The icon 420 labeled "Browser" in browser module 147; and ○ The icon 422 labeled "Music" in the video and music player module 152; and • Icons of other applications, such as: ○The icon 424 of the IM module 141 marked as "Message"; ○The calendar module 148 has an icon 426 labeled "Calendar"; ○ The icon 428 of the image management module 144 is labeled "Photo". ○ The icon 430 of camera module 143, which is labeled "camera"; ○ The icon 432 of the online video module 155, which is marked as "Online Video"; ○ The icon 434 labeled "Stock Market" in the Stock Market widget 149-2; ○The icon 436 of the map module 154 that is labeled "map"; ○The weather widget 149-1 has icon 438 labeled "weather"; ○ The alarm clock widget 149-4 has an icon 440 labeled "clock"; ○ The icon 442 of the fitness support module 142 is labeled "fitness support"; ○ The icon 444 labeled "Notepad" in Notepad module 153; and ○ An icon 446 is used to set up an application or module, which provides access to settings for the device 100 and its various applications 136.

[0152] It should be noted that Figure 4A The icon labels illustrated are merely examples. Other labels may be optionally used for various application icons, for instance. In some embodiments, the label for a particular application icon includes the name of the application corresponding to that particular application icon. In some embodiments, the label for a specific application icon differs from the name of the application corresponding to that specific application icon.

[0153] Figure 4B An example is illustrated by a touch-sensitive surface 451 that is separate from the display 450 (e.g., Figure 3 Devices (e.g., tablets or touchpads 355) Figure 3 Example user interface on device 300). Although many subsequent examples are given with reference to input on touchscreen display 112 (which combines a touch-sensitive surface and a display), in some embodiments the device detects input on a touch-sensitive surface separate from the display, such as Figure 4B As shown in the diagram. In some embodiments, the touch-sensitive surface (e.g., Figure 4B 451) has a main axis (e.g., on the display (e.g., 450) that is aligned with the main axis on the display (e.g., 451). Figure 4B The principal axis corresponding to 453 in the middle (e.g., Figure 4B (452 in the middle). According to these embodiments, the device detects contact with the touch-sensitive surface 451 at a position corresponding to the corresponding position on the display (e.g., Figure 4B (460 and 462 in the example) Figure 4B In the diagram, 460 corresponds to 468 and 462 corresponds to 470. Thus, on a touch-sensitive surface (e.g., Figure 4B 451 in the middle) and the display of a multi-functional device (e.g., Figure 4BWhen 450 is separated, user input detected by the device on the touch-sensitive surface (e.g., touches 460 and 462 and their movement) is used by the device to manipulate the user interface on the display. It should be understood that similar methods can be optionally used for other user interfaces described herein.

[0154] Additionally, while the examples below are primarily given with reference to finger input (e.g., finger touch, single-finger tap gesture, finger swipe gesture, etc.), it should be understood that in some implementations, one or more of these finger inputs may be replaced by input from another input device (e.g., mouse-based input or stylus input). For example, a swipe gesture may optionally be replaced by a mouse click (e.g., instead of a touch), followed by movement of the cursor along the path of the swipe (e.g., instead of movement of the touch). Similarly, a tap gesture may optionally be replaced by a mouse click while the cursor is over the location of the tap gesture (e.g., instead of detection of touch, followed by cessation of touch detection). Likewise, when multiple user inputs are detected simultaneously, it should be understood that multiple computer mice may optionally be used simultaneously, or mouse and finger touch may optionally be used simultaneously.

[0155] In some implementations, the device's response to input detected by the device depends on a criterion based on the intensity of contact during the input. For example, for some "light press" inputs, a first response is triggered by the intensity of contact exceeding a first intensity threshold during the input. In some implementations, the device's response to input detected by the device depends on a criterion that includes both the intensity of contact during the input and a time-based criterion. For example, for some "deep press" inputs, a second response is triggered by the intensity of contact exceeding the second intensity threshold (greater than the first intensity threshold for a light press) during the input, provided a delay time has elapsed between satisfying the first intensity threshold and satisfying the second intensity threshold. The duration of this delay time is typically less than 200 ms (e.g., 40 ms, 100 ms, or 120 ms, depending on the magnitude of the second intensity threshold, where the delay time increases as the second intensity threshold increases). This delay time helps avoid unintentionally identifying deep press inputs. As another example, for some "deep press" inputs, there is a period of decreased sensitivity after the first intensity threshold is reached. During this period of decreased sensitivity, the second intensity threshold increases. This temporary increase in the second intensity threshold also helps to prevent accidental deep press inputs. For other deep press inputs, the response to the detected deep press input does not depend on time-based criteria.

[0156] In some implementations, one or more of the input intensity threshold and / or the corresponding output varies based on one or more factors, such as user settings, contact motion, input timing, application operation, rate at which intensity is applied, number of simultaneous inputs, user history, environmental factors (e.g., ambient noise), focus selector position, etc. Example factors are described in U.S. Patent Applications 14 / 399,606 and 14 / 624,296, the entire contents of which are incorporated herein by reference.

[0157] Figures 4C1 to 4C2Example state diagram 4000 illustrates navigation between various user interfaces of a multifunction device 100 according to some embodiments. In some embodiments, the multifunction device 100 displays corresponding user interfaces from multiple different user interfaces, including a wake-up screen user interface 490 (also referred to as a cover user interface 496), a home screen user interface 492, a widget user interface 491, a control user interface 498, a search user interface 494, an application library user interface 497, and an application user interface 493 for a corresponding application among multiple applications (e.g., a camera application (e.g., a camera application user interface 495), a flashlight application, a settings application, a messaging application (e.g., an application user interface 493), a phone application, a map application, a browser application, or another type of application). In some embodiments, the multifunction device utilizes various portions of a display (e.g., a touchscreen display 112, a display 340 associated with a touch-sensitive surface, a head-mounted display, or another type of display) to display persistent content on multiple user interfaces. For example, in some embodiments, the display includes a dynamic status area 4002 for displaying alerts, status updates, and / or current status of various subscribed events and / or ongoing events and / or various application activities in real time or substantially in real time. In some embodiments, the display includes a static status area 4022 for displaying status information of one or more system functions that are relatively stable over a period of time. In some embodiments, the dynamic status area 4002 changes (e.g., expands and / or shrinks) from an area housing one or more hardware elements (e.g., a camera lens, microphone, and / or speaker) of a multifunctional device. As described herein, although the examples below are given with touch gestures on a touchscreen display, similar functionality can be implemented using a display associated with a touch-sensitive surface, wherein a position on the touch-sensitive surface (e.g., a position on the top edge, bottom edge, left edge, right edge, upper left portion, lower right portion, inner portion, and / or another portion) has a corresponding position on the display (and / or on the user interface presented on the display) (e.g., a position on the top edge, bottom edge, left edge, right edge, upper left portion, lower right portion, inner portion, and / or another portion). Furthermore, although the examples below are given using touch gestures on a touchscreen display, similar functionality can be achieved using a display associated with another type of input, such as mouse input, pointer input, gaze input (e.g., gaze with temporal and positional characteristics pointing to parts of the displayed user interface and / or user interface elements) combined with air gesture input (e.g., air tap, air swipe, air pinch, pinch and hold, pinch hold and drag, and / or another type of air gesture).As described in this article, although the examples below are given using touch gestures on a touchscreen display, similar functionality can be achieved using a head-mounted display that displays a user interface in a three-dimensional environment and is controlled by various input devices and sensors that detect various types of user input, such as touch gestures, input provided by pointers or controllers, gaze input, voice input, and / or air gestures.

[0158] like Figure 4C1 As shown, when the multifunction device 100 is initially powered on (for example, in response to the power button 116a of the multifunction device 100), Figure 4A (4100) Long press or other activation input on the multifunction device display (4100) wake-up screen user interface 490, which is the system user interface initially displayed by the multifunction device 100 when the multifunction device 100 changes from a power-off state to a power-on state.

[0159] In some embodiments, when the wake-up screen user interface 490 is displayed after a certain period of time, the multifunction device 100 may optionally transition (4101) to a low-power state, wherein the display of the multifunction device 100 may optionally be turned off or dimmed, as shown in user interface 489. In some embodiments, when the multifunction device 100 is in a low-power state, the wake-up screen user interface 490 remains displayed in a dimmed, always-on state. For example, in the low-power state shown in user interface 489, a time indicator and / or date indicator continues to be displayed.

[0160] In some implementations, in response to user input 4101 activating the power button 116a of the multifunction device 100 (e.g., when the wake-up screen user interface 490 and / or any other user interface described herein are displayed), the multifunction device 100 transitions (4101) to a low-power state (e.g., turning off the display or displaying the wake-up screen user interface 490 in a dimmed normally-on state).

[0161] In some implementations, the multifunction device transitions from a normal operating state (e.g., automatically after a period of inactivity, and / or in response to detecting user input activating the power button 116a) to a low-power state. In the normal operating state, any of the multiple user interfaces (e.g., wake-up screen user interface 490, main screen user interface 492, application user interface 493 of the corresponding application, or another system and / or application user interface) may be the last user interface displayed before transitioning to the low-power state.

[0162] In some embodiments, when the multifunction device 100 is in a low-power state, the multifunction device continues to detect input (e.g., device movement, touch gestures (e.g., swipes, taps, or other touch inputs), gaze input, air gestures, impacts to the device, pressing a power button, rotating a knob, or other types of input) via one or more sensors and input devices of the multifunction device. In some embodiments, in response to the detection of user input via one or more sensors and input devices of the multifunction device, the multifunction device transitions from a low-power state (4100) to a normal operating state and displays the wake-up screen user interface 490 in a normal, undimmed state.

[0163] In some implementations, when the multifunction device 100 is in the low-power state shown in the user interface 489, the multifunction device continues to detect the arrival of events such as notifications and status updates (e.g., message notifications, incoming communication requests and / or other application-generated events and system-generated events, as well as session state updates, subscription events and / or other state changes that require user attention). In some implementations, in response to detecting an event that generates an alert, notification, and / or status update, the multifunction device transitions from the low-power state to a normal operating state and displays the alert, notification, and / or status update in a normal, undimmed state on the wake-up screen user interface 490. In some implementations, the multifunction device automatically returns to the low-power mode after a short period of time following the display of the alert, notification, and / or status update.

[0164] In some implementations, the wake-up screen user interface 490, displayed in a dimmed always-on state, includes a display that is in a normal operating state (e.g., with...). Figure 4C1 and Figure 4C2The wake-up screen user interface 490 displayed (as opposed to the dark screen shown) has the same or substantially the same set of user interface elements as the wake-up screen user interface 490 displayed in a dimmed, always-on state. In some embodiments, the wake-up screen user interface 490 displayed in a dimmed, always-on state has fewer user interface elements than the wake-up screen user interface 490 displayed in normal operation. For example, in some embodiments, the wake-up screen user interface 490 displayed in normal operation includes a time element 4004 indicating the current time, a date element 4006 indicating the current date, and one or more widgets 4008 including content from the corresponding application that is updated from time to time without user intervention. In some embodiments, the wake-up screen user interface 490 displayed in normal operation includes one or more application icons corresponding to the corresponding application, such as an application icon 4010 for a flashlight application, an application icon 4012 for a camera application, or another system-recommended or user-selected application. In some embodiments, the wake-up screen user interface 490 displayed in normal operation includes one or more shortcuts for accessing corresponding actions in one or more system-recommended and / or user-selected applications (e.g., a shortcut to play music using a media player application, send a quick message using a messaging application, or open DND or sleep mode using a system application). In some implementations, the wake-up screen user interface 490 includes a dynamic status area 4002 that displays status updates or current status of ongoing activities of one or more applications (such as communication sessions, charging sessions, running timers, music playback sessions, delivering updates, navigation instructions, location sharing status), and / or status updates of subscribed applications and system events. In some implementations, the wake-up screen user interface 490 includes a static status area 4022 that displays the status of one or more system functions, such as network connectivity status, battery status, location sharing status, cellular signal and carrier information, and other system status information. In some implementations, dynamic status updates (e.g., battery charging, screen recording, location sharing, and other status updates) are initially displayed in the dynamic status area 4002 and then move to the static status area 4022 after a certain period of time. In some implementations, in the dimmed always-on state, the wake-up screen user interface 490 omits the dynamic state area 4002, the static state area 4022, application icons 4010 and 4012 and / or shortcuts for application and / or system operations, and optionally disables interaction with the remaining user interface elements of the wake-up screen user interface 490 (e.g., wallpaper, time element 4004, date element 4006 and / or widget 4008).

[0165] In some implementations, waking up the screen user interface includes one or more recently received notifications corresponding to one or more applications (e.g., notification 4016 or other newly received notifications). In some implementations, in response to detecting a new notification (e.g., notification 4018), Figure 4C2 Upon receipt or generation of a notification (or one or more newly received notifications), the wake-up screen user interface displayed in a dimmed state transitions to a wake-up screen user interface 490. In some embodiments, notifications 4016 are grouped or merged based on the event type and / or application corresponding to the notification. In some embodiments, the user can interact with the notification to dismiss it, send it to the notification history, and / or extend the notification to view additional notification content (e.g., optionally after requesting and / or obtaining valid authentication data).

[0166] In some implementations, the wake-up screen user interface 490 may be displayed when the multifunction device is in a locked or unlocked state. In some implementations, when the wake-up screen user interface 490 is displayed when the multifunction device is locked, a lock symbol 4020a may optionally be displayed in a status area of ​​the wake-up screen user interface 490 (e.g., the dynamic status area 4002, the static status area in the upper right corner of the display) or elsewhere (e.g., below the dynamic status area 4002, in the upper left corner, or in another part of the display) to indicate that the multifunction device is locked (e.g., as shown in the image). Figure 4C1 The wake-up screen user interface 490 is shown in the diagram, and authentication data is required to clear the wake-up screen user interface 490 to navigate to the main screen user interface 492 or the last displayed application user interface. In some embodiments, when the wake-up screen user interface 490 is displayed (e.g., in a low-power state and / or normal operating state), the multifunction device automatically attempts to obtain authentication data via biometric scanning (e.g., face, fingerprint, voiceprint, and / or iris), and if valid authentication data is successfully obtained, it automatically transitions to an unlocked state. In some embodiments, in conjunction with transitioning to an unlocked state, the multifunction device replaces the lock symbol 4020a with the unlock symbol 4020b to indicate that the multifunction device is now in an unlocked state (e.g., in the context of...). Figure 4C2 (As shown in the wake-up screen user interface 490).

[0167] In some implementations, when the wake-up screen user interface 490 is displayed in normal operating mode, the multifunction device allows user interaction with the user interface elements of the wake-up screen user interface 490.

[0168] For example, in some implementations, selection on a user interface element (such as one of widget 4008, status area 4002, notification 4018, and / or application icon 4010 or 4012) (e.g., by tapping, clicking, and / or air tapping) causes the multifunction device to navigate away from the wake-up screen user interface 490 and display the corresponding user interface for the application corresponding to the selected user interface element, or display an enlarged version of the user interface element to show additional information and / or controls related to the initial display content in the selected user interface element. For example, as Figure 4C2 As shown, in response to user input 4113 of selecting message notification 4018, the computer system displays (4113) the application user interface 493 for the messaging application.

[0169] For example, in some embodiments, corresponding user interface elements such as the time element 4004, date element 4006, or enhanced selection input 4112 on the wallpaper of the wake-up screen user interface 490 (e.g., touch and hold gesture, press input, or another type of input) cause the multifunction device to display a configuration user interface for configuring one or more aspects of the wake-up screen user interface 490 (e.g., selecting a wallpaper, configuring the color or font scheme of user interface elements, configuring how to lay out the different elements of the wake-up screen user interface, configuring additional wake-up screens, selecting a previously configured wake-up screen, and viewing additional customization options for the wake-up screen user interface). In some embodiments, the configuration of the wake-up screen user interface 490 is partially applied to the main screen user interface 492, and vice versa.

[0170] In some implementations, enhanced selection input (e.g., touch and hold gesture, tap input, or another type of input) on the flashlight app icon 4010 or camera app icon 4012 causes the multifunction device to activate the flashlight of the multifunction device or display the camera user interface 495 of the camera app. For example, in response to detecting selection input 4104a on the camera app icon 4012 in the wake-up screen user interface 490, the multifunction device activates the camera app and displays (4104a) the camera app UI 495 (e.g., as shown in the image). Figure 4C1 (As shown).

[0171] In some implementations, if the multifunction device detects user interaction with user interface elements shown in the wake-up screen user interface 490 and determines that the wake-up screen user interface is locked, the multifunction device attempts to obtain authentication data from the user by displaying an authentication user interface (e.g., a password input interface, a password input interface, and / or a biometric scanning user interface). The multifunction device continues to navigate away from the wake-up screen user interface 490 and performs actions based on the user's interaction after obtaining valid authentication data from the user.

[0172] In some implementations, in addition to performing operations such as navigating to an application user interface, displaying an extended version of a user interface element showing additional information, and / or displaying configuration options for the corresponding user interface element or the wake-up screen user interface, the multifunction device also allows the user to navigate from the wake-up screen user interface 490 to other user interfaces (optionally, after valid authentication data has been obtained) in response to navigation inputs (e.g., swipe gestures or other types of navigation inputs pointing to an area of ​​the wake-up screen user interface that is not occupied by user interface elements, and / or an area of ​​the wake-up screen user interface occupied by user interface elements (e.g., widgets, app icons, and / or time elements) that are not responsive to swipe gestures or the other types of navigation inputs).

[0173] For example, in some implementations, an upward swipe gesture 4105 starting from the bottom edge of the wake-up screen user interface 490 causes (4105) the multifunction device to navigate away from the wake-up screen user interface 490 and display the main screen user interface 492 or the last displayed application user interface (optionally, after requesting and obtaining valid authentication data).

[0174] In some implementations, the up swipe gesture 4105 is a representative example of a gesture to return to the home screen or a gesture to cancel (e.g., other examples include up swipe gestures 4103a, 4103c, 4103d, 4103e, 4110a, and 4111a), which causes the multifunction device to cancel the currently displayed user interface (e.g., wake-up screen user interface 490, application user interface (e.g., camera user interface 495, messaging user interface 493, or another application user interface), control user interface 498, search user interface 494, app library user interface 497, or home screen configuration user interface) and navigate to the home screen user interface 492 or the last displayed user interface (e.g., wake-up screen user interface 490, wake-up screen configuration user interface, search user interface 494, application user interface, or home screen user interface 492).

[0175] In some implementations, a downward swipe from the top edge (e.g., the center portion of the top edge or any part of the top edge) or inner area of ​​the wake-up screen user interface 490 (e.g., a downward swipe 4106a or another downward swipe) causes the multifunction device (4106a) to display a search user interface 494, which includes a search input area 4030 and one or more application icons 4032 for recommending applications (e.g., recently used applications and / or relevant applications based on the current context), such as Figure 4C1As shown. In some embodiments, in response to detecting search input in search input area 4030, the multifunction device retrieves and displays search results, which include relevant application content (e.g., messages, notepad, media files, and / or documents) from different applications installed on the multifunction device, relevant applications (e.g., applications installed on the multifunction device and / or applications available in app stores), relevant web pages (e.g., bookmarked web pages and / or web pages newly retrieved from the Internet), and / or search results from other sources (e.g., news, social media platforms, and / or reference websites). In some embodiments, different groups of search results are provided depending on the locked and unlocked states of the multifunction device, and if the multifunction device is unlocked when performing a search, more detailed or additional search results may be displayed. In some embodiments, the multifunction device attempts to obtain valid authentication data in response to receiving search input, and displays different groups of search results depending on whether valid authentication data is obtained. In some implementations, an upward swipe gesture 4103d (or another type of input elimination) starting from the bottom edge of the search user interface causes the multifunction device to eliminate the search user interface 494 and redisplay the wake-up screen user interface 490 (e.g., because the wake-up screen user interface is the last user interface displayed), such as Figure 4C1 As shown. In some embodiments, in response to a downward swipe 4106b from the inner area of ​​the main screen user interface 494, the multifunction device displays the search user interface 494; and in response to a subsequent upward swipe gesture 4103d from the bottom edge of the search user interface 492, the main screen user interface 492 is redisplayed (4103d) (e.g., because the main screen user interface is the last user interface displayed), as shown. Figure 4C1 As shown.

[0176] In some implementation schemes, such as Figure 4C1As shown, a right swipe gesture 4102a starting from the left edge or inner area of ​​the wake-up screen user interface 490 enables (4102a) the multifunction device to navigate from the wake-up screen user interface 490 to the widget user interface 491 (or another system user interface besides the main screen user interface, such as a control user interface, search user interface, or notification history user interface). In some embodiments, the widget user interface 491 includes a plurality of widgets 4026 (e.g., widgets 4026a, 4026b, and 4026c) automatically selected by the operating system and / or selected by the user to be included in the widget user interface 491. In some embodiments, the widgets 4026 displayed in the widget user interface 491 have a shape factor larger than that of the widget 4008 displayed below the time element 4004 in the wake-up screen user interface 490. In some embodiments, the widgets 4026 displayed in the widget user interface 491 and the widgets 4008 displayed in the wake-up screen user interface 490 are selected and / or configured independently of each other. In some implementations, the widget 4026 in the widget user interface 491 includes content from its respective application, and the content is automatically updated from time to time as updates become available in the respective application. In some implementations, selecting the corresponding widget in the widget user interface (e.g., tapping the corresponding widget, or providing other selection input to the corresponding widget) causes the multifunction device to navigate away from the widget user interface 491 and display the user interface of the application corresponding to the corresponding widget (optionally, after requesting and / or obtaining valid authentication data).

[0177] In some implementations, an upward swipe gesture 4103a starting from the bottom edge of the widget user interface 491 and / or a leftward swipe gesture 4103b starting from the right edge or inner area of ​​the widget user interface 491 causes (4103a-1 / 4103b-1) the multifunction device to clear the widget user interface 491 and redisplay the wake-up screen user interface 490, as... Figure 4C1 As shown.

[0178] In some implementations, a left-swipe gesture 4104b starting from the right edge or inner portion of the wake-up screen user interface 490 enables (4104b) the multifunction device to navigate from the wake-up screen user interface 490 to the camera user interface 495 of the camera application. In some implementations, access to the photo library via the camera application is restricted in the camera user interface 495 unless valid authentication data has been obtained. In some implementations, such as Figure 4C1As shown, an upward swipe gesture 4103c or another elimination input starting from the bottom edge of the camera user interface 495 causes (4103c) the multifunction device navigation to leave the camera user interface 495 and redisplay the wake-up screen user interface 490 (e.g., because the wake-up screen user interface 490 is the last user interface displayed before the camera user interface 495 is displayed).

[0179] In some implementations, a downward swipe gesture 4109a (e.g., as shown in the image) starts from the right side of the top edge of the wake-up screen user interface. Figure 4C2 (As shown) This causes (4109a) the multifunction device to display a control user interface 498 that overlays or replaces the wake-up screen user interface 490. In some embodiments, the control user interface 498 includes status information for displaying one or more static status indicators in the static status area 4022, and corresponding control groups 4028 for various system functions (e.g., including controls 4028a, 4028b, and 4028c), such as network connectivity (WiFi, cellular data, airplane mode, Bluetooth, and other connection types), media playback controls, display controls (e.g., display brightness, color temperature, night mode, True Tone, and Dark Mode controls), audio controls (e.g., volume and / or mute / unmute controls), focus mode controls (e.g., DND, work, study, sleep, and other modes that adjust the generation of alerts and notifications based on context and configuration), and application icons (e.g., flashlight, timer, calculator, camera, screen recording, and / or other user-selected or system-recommended applications)). In some implementations, an upward swipe gesture 4110a (or another input cancellation gesture) starting from the bottom edge of the control user interface 498 causes the multifunction device to cancel the control user interface 498 and redisplay (4110a-1) the wake-up screen user interface 490 (e.g., because the wake-up screen user interface 490 is the last user interface displayed before the control user interface 498 is displayed).

[0180] In some embodiments, an upward swipe gesture 4107 starting from an inner area of ​​the wake-up screen user interface 490 and / or an upward swipe gesture starting from the inner area of ​​the cover user interface 496 (e.g., optionally when no unread notifications are displayed in the cover user interface) causes the multifunction device (4107) to display a notification history user interface that includes multiple previously saved notifications and notifications that have been sent directly to the notification history but have not yet been displayed on the wake-up screen user interface 490. In some embodiments, in response to an upward swipe gesture 4118 pointing to the notification history in the wake-up screen user interface 490 and / or the cover user interface 496, the notification history user interface can be scrolled to reveal additional notifications. In some embodiments, the notification history is displayed as part of the wake-up screen user interface 490 and / or the cover user interface 496, and a downward swipe gesture 4103f pointing to an inner portion of the notification history causes the notification history to stop displaying and causes the wake-up screen user interface 490 and / or the cover user interface 496 to redisplay without a notification history.

[0181] As described above, after navigating from the wake-up screen user interface 490 to a corresponding user interface other than the main screen user interface (e.g., in response to a swipe gesture in the down, left, or right direction), an upward swipe gesture 4103 (e.g., 4103a and 4103c to 4103f) starting from the bottom edge of the corresponding user interface (e.g., an upward swipe gesture starting from the bottom edge of a touch-sensitive display showing the corresponding user interface in full-screen mode, or an upward swipe gesture starting from the bottom edge of a touch-sensitive surface corresponding to the display showing the corresponding user interface) causes the multifunction device to clear the corresponding user interface and return to the wake-up screen user interface 490. In contrast, an upward swipe gesture 4105 starting from the bottom edge of the wake-up screen user interface 490 causes (4105) the multifunction device to navigate away from the wake-up screen user interface 490 and display the main screen user interface 492, and another upward swipe gesture starting from the bottom edge of the main screen user interface 492 does not cause the multifunction device to clear the main screen user interface 492 and return to the wake-up screen user interface 490. In other words, once navigation from the wake-up screen user interface 490 to the main screen user interface 492 is complete, the multifunction device is no longer restricted, and access to application icons displayed on the main screen user interface 492, as well as access to the content and functions of the computer system, is unrestricted for the user. An upward swipe gesture starting from the bottom edge of the currently displayed user interface is a representative example of an input cancellation gesture that clears the currently displayed user interface and redisplays the last displayed user interface. An upward swipe gesture starting from the bottom edge of the currently displayed user interface is also a representative example of a return-to-home gesture that clears the currently displayed user interface and displays the main screen user interface (e.g., regardless of whether the main screen user interface was the last displayed user interface before the currently displayed user interface was displayed).

[0182] like Figure 4C2 As shown, once the multifunction device navigates away from the wake-up screen user interface 490 and displays the main screen user interface 492, the user has unrestricted access to the functions and applications of the multifunction device. For example, in some embodiments, the main screen user interface 492 includes multiple pages, and the respective pages of the main screen user interface include application icons and / or widgets corresponding to different applications, and the user's selection of a corresponding widget or application icon (e.g., by tapping, clicking, or otherwise selecting) causes the multifunction device to display the application's user interface corresponding to the corresponding widget or application icon.

[0183] In some implementations, the main screen user interface 492 displays a search capability display 4034 (e.g., as shown in the image). Figure 4C1As shown), a tap on the search enable display 4034 causes the search user interface 494 to be displayed over the main screen user interface 492. In some embodiments, in response to detecting an upward swipe gesture 4103d (or another clear input) starting from the bottom edge of the search user interface, the multifunction device clears the search user interface 494 and redisplays (4103d) the main screen user interface 492 (e.g., not waking up the screen user interface 490, because the upward swipe gesture clears the currently displayed user interface and redisplays the last displayed system user interface).

[0184] In some implementation schemes, such as Figure 4C1 As shown, a rightward swipe gesture 4102b starting from the left edge of the first page of the main screen user interface 492 causes the multifunction device to display the aforementioned widget user interface 491. In some embodiments, a leftward swipe gesture (e.g., gesture 4103b or another leftward swipe gesture) starting from the right edge or inner area of ​​the widget user interface (e.g., gesture 4103b or another leftward swipe gesture) or an upward swipe gesture (e.g., gesture 4103a or another upward swipe gesture) starting from the bottom edge of the widget user interface 491 causes the multifunction device to navigate away from the widget user interface 491 and redisplay the first page of the main screen user interface 492 (e.g., when the main screen user interface 492 is the last user interface displayed before the widget user interface 491 was displayed).

[0185] In some implementation schemes, such as Figure 4C2 As shown, a continuous left-swipe gesture 4116 on the home screen user interface 492 navigates through consecutive pages of the home screen user interface 492 until the app library user interface 497 is displayed (4116). In some embodiments, the app library user interface 497 displays app icons from multiple pages grouped into different categories from the home screen user interface. In some embodiments, the app library user interface 497 includes a search user interface element 4036 that accepts search criteria (e.g., keywords, images, and / or other search criteria) and returns app icons of relevant apps (e.g., apps stored on the multifunction device and / or available in the app store) as search results. In some embodiments, user selection of app icons in the search results and / or app library (e.g., by tap input, click input, or another type of selection input) causes the multifunction device to display the app user interface corresponding to the selected app icon.

[0186] In some implementations, a downward swipe gesture 4109c, starting from the right side of the top edge of the application library user interface 497, causes the control user interface 498 as described above to be displayed. In some implementations, an up-swipe gesture starting from the bottom edge of the control user interface 498 (e.g., up-swipe gesture 4110a or another up-swipe gesture) or another cancel input causes the multifunction device to cancel the control user interface 498 and redisplay the application library user interface 497 (e.g., because the application library user interface was the last user interface displayed before the control user interface was displayed) (e.g., or redisplay another user interface (e.g., redisplaying (4110a-1) the wake-up screen user interface 490 (e.g., if the control user interface 498 was displayed in response to a swipe gesture 4109a), redisplaying (4110a-3) the home screen user interface 492 (e.g., if the control user interface was displayed in response to a down swipe from the top right portion of the top edge of the display), or redisplaying (4110a-2) the application user interface that was the last user interface displayed before the control user interface was displayed (e.g., if the control user interface was displayed in response to a down swipe 4109b)).

[0187] In some implementations, a right swipe gesture 4115 starting from the inner area or left edge of the App Library user interface 497 or an up swipe gesture starting from the bottom edge of the App Library user interface 497 causes (4115) the multifunction device to clear the App Library user interface 497 and redisplay the last page of the home screen user interface 492.

[0188] In some implementations, a downward swipe gesture 4114 starting from the inner area of ​​the application library user interface 497 causes the multifunction device to display application icons of applications stored on the multifunction device in a scrollable list (e.g., in chronological or alphabetical order).

[0189] In some embodiments, an upward swipe gesture originating from the bottom edge of the home screen user interface causes the multifunction device to display either the first page of the home screen user interface 492 or the multitasking user interface 488 (also referred to as the app switcher user interface). In some embodiments, in response to detecting an upward swipe gesture originating from the bottom edge of the home screen user interface, different criteria (e.g., criteria based on speed, direction, duration, distance, intensity, and / or other characteristics) are used to determine whether navigation is to the first page of the home screen user interface 492 or to the multitasking user interface 488. For example, in some embodiments, a short flick and a slow, long swipe cause the multifunction device to navigate to the first page of the home screen user interface 492, while a slow, medium-length swipe causes the multifunction device to display the multitasking user interface 488. In some embodiments, the navigation gesture is dynamically evaluated before the termination of the gesture is detected, and therefore, the estimated destination user interface for the navigation gesture continues to change, and visual feedback regarding the estimated destination user interface continues to be provided to guide the user to end the gesture when the visual feedback indicates the desired destination user interface. In some implementations, in response to user input 4117 at a location not corresponding to a part of the application in response to multitasking user interface 488, the last displayed user interface that was displayed before multitasking user interface 488 is displayed (e.g., the main screen user interface 492 is displayed when multitasking user interface 488 is displayed in response to user input 4111b).

[0190] In some embodiments, a reconfiguration mode of the main screen user interface 492 is displayed, wherein application icons and / or widgets can be repositioned, removed from, or added to different pages of the main screen user interface 492. In some embodiments, a touch and hold gesture or another enhanced selection input, such as pointing at the main screen user interface 492 for a corresponding threshold amount of time, causes the multifunction device to display the main screen user interface 492 in configuration mode. In some embodiments, selecting the search enablement 4034 in the main screen user interface 492 while it is in reconfiguration mode causes the multifunction device to display a page editing user interface of the main screen user interface, in which pages of the main screen user interface can be reordered, deleted, hidden, or created. In some embodiments, a tap input on the main screen user interface in reconfiguration mode causes the main screen user interface to exit reconfiguration mode. In some embodiments, a tap input on an unoccupied portion of the page editing user interface causes the multifunction device to maintain the page editing user interface and redisplay the main screen user interface in reconfiguration mode. Another tap on the home screen user interface causes the home screen user interface to exit reconfiguration mode and redisplay in normal mode.

[0191] In some embodiments, when the home screen user interface 492 is displayed, a downward swipe gesture 4108a starting from the top edge of the home screen user interface 492 causes (4108a) the multifunction device to cover the home screen user interface 492 with a cover user interface 496 (also referred to as waking up the screen user interface 490 if the user interface is displayed when transitioning from normal mode to low power mode or vice versa (e.g., due to inactivity, due to activation of the power button, and / or due to user input corresponding to a request to wake up or lock the device)), and access to the home screen user interface is temporarily restricted by the cover user interface 496. In some embodiments, when the cover user interface 496 is displayed, an upward swipe gesture 4103e starting from the bottom edge of the cover user interface 496 eliminates (4103e) the cover user interface 496 and redisplays the home screen user interface 492 (e.g., because the home screen user interface is the last user interface displayed). In some embodiments, the cover user interface responds to user input in a manner similar to that described with respect to the waking up screen user interface 490.

[0192] In some implementations, the application user interface of a given application may be displayed in response to user input in multiple scenarios, such as a tap on a widget in the home screen user interface or widget user interface; a tap on an application icon in search results provided in the home screen, widget user interface, search results or recommended applications section of the search user interface, app library user interface, or search within the app library user interface; a tap on a notification in the wake-up screen user interface or notification history; a tap on an application representation in the multitasking user interface; or a tap on a link to an application in the user interface of another application (e.g., a link to a document, a link to a phone number, a link to a message, a link to an image, and other types of links). In some implementations, the user interface of a single application is displayed in full-screen mode. In some implementations, the user interfaces of two or more applications are displayed in a simultaneous display configuration, such as a side-by-side display configuration where the user interfaces of the applications are displayed adjacent to each other to fit within the display, or an overlay display configuration where the user interface of the first application is displayed in full-screen mode, while the user interfaces of other applications are overlaid on portions of the user interface of the first application (e.g., in a single stack or on separate portions).

[0193] In some embodiments, when the application's user interface is displayed, an up-swipe gesture (e.g., up-swipe gesture 4111a or another up-swipe gesture) or another gesture to clear input or return to the home screen, starting from the bottom edge of the application's user interface (e.g., the messaging user interface 493 or another user interface of the application), causes the multifunction device (4111a-1 or 4111a-2) to clear the currently displayed application user interface and display the home screen user interface (e.g., shown as transition 4111a-1) or the multitasking user interface (e.g., shown as transition 4111a-1) depending on the characteristics of the up-swipe gesture. In some embodiments, when the home screen user interface 492 is displayed, an up-swipe gesture 4111b, starting from the bottom edge of the home screen user interface, causes the multifunction device (4111b) to clear the currently displayed home screen user interface 492 and display the multitasking user interface 488.

[0194] In some implementations, a horizontal swipe gesture performed in the bottom portion of the application user interface in the left and / or right direction causes the multifunction device to switch to another previously displayed application user interface for a different application. In some implementations, the same swipe gesture starting from the bottom portion of the respective application user interface is continuously evaluated to determine and update the estimated destination user interface in the multitasking user interface 488, the home screen user interface 492, or the user interface of the previously displayed application based on the characteristics of the swipe gesture (e.g., position, speed, direction, and / or changes in one or more of the above), and the final destination user interface is displayed based on the estimated destination user interface when the swipe gesture terminates (e.g., touch lift-off, touch intensity reduction, movement pause, and / or another type of change in input).

[0195] In some implementations, when the application user interface of the corresponding application is displayed (or multiple application user interfaces are displayed in a simultaneous display configuration), a downward swipe gesture 4108b starting from the top edge of the application user interface causes (4108b) the multifunction device to display a cover user interface 496 above the application user interface. Figure 4C1 )(or Figure 4C2 (Wake-up screen user interface 490). In response to an upward swipe gesture (or another clear input) starting from the bottom edge of the cover user interface, the multifunction device clears the cover user interface 496 (or wake-up screen user interface 490) and redisplays the application user interface.

[0196] In some implementation schemes, such as Figure 4C2As shown, a downward swipe gesture 4109b starting from the static area 4022 on the display causes the multifunction device to display the control user interface 498 above the application user interface, and an upward swipe gesture 4110a (or another clear input) starting from the bottom edge of the control user interface 498 clears the control user interface 498 and causes the application user interface to be redisplayed (e.g., or the last displayed user interface before the control user interface 498 is displayed).

[0197] In some implementations, rotating the display causes the multifunction device to display a currently displayed user interface (e.g., application user interface, home screen user interface, wake-up screen user interface, control user interface, notification user interface, widget user interface, app library user interface, and about user interface) with different layouts (e.g., landscape and portrait versions). Figures 4C1 to 4C2 Different versions of the other user interfaces described. In some implementations, rotating the display has no effect on the orientation of the currently displayed corresponding user interface.

[0198] The above description of navigation between user interfaces and the exact appearance and components of various user interfaces is merely illustrative and can be implemented using variations of the various implementations described herein. Furthermore, according to the various implementations, Figures 4C1 to 4C2 The transitions between the user interface pairs shown are only Figures 4C1 to 4C2 A subset of all possible transitions between different user interface pairs shown, and a transition from any of a plurality of other user interfaces to a corresponding user interface may be possible based on the same type of corresponding user input pointing to the same interactive area of ​​the display, and / or based on different types of input or pointing to different interactive areas.

[0199] User interface and related processes Now turn to implementations of user interface (“UI”) and associated processes that may be implemented on an electronic device (or more generally a computer system) such as computer system 100 or device 300 having a display, a touch-sensitive surface, one or more touch output generators for generating tactile output, and one or more sensors for detecting the intensity of contact with the touch-sensitive surface.

[0200] Figures 5A to 5AT An example user interface is shown for automatically displaying a customizable user interface when certain criteria are met. Figures 6A to 6AN Example user interfaces are shown for switching between different operating modes (e.g., environment mode), interacting with different operating modes, and configuring different operating modes. Figures 7A to 7VExample user interfaces are shown for interacting with and configuring customizable user interfaces. Figures 8A to 8K Examples of user interfaces for interacting with different operating modes (e.g., ambient mode) and switching between different operating modes are shown. Figures 9A to 9AA An example user interface is shown for automatically activating the flashlight function of computer system 100 when certain criteria are met. Figures 10A to 10L This is a flowchart of a method for automatically displaying a customizable user interface when certain criteria are met. Figures 11A to 11G It is a flowchart of methods for switching between different operating modes (e.g., environment modes), interacting with different operating modes, and configuring different operating modes. Figures 12A to 12D This is a flowchart of methods for interacting with and configuring customizable user interfaces. Figures 13A to 13J It is a flowchart of a method for interacting with different user interfaces in different operating modes (e.g., environment modes) and switching between different operating modes. Figures 14A to 14G This is a flowchart of the process for automatically activating the flashlight function of computer system 100 when certain criteria are met. Figures 15A to 15Q An example user interface is shown for updating the displayed content when an existence criterion is met. Figures 16A to 16F This is a flowchart of a method for updating displayed content when an existence criterion is met. The user interface in these figures is used to illustrate the process described below, including... Figures 10A to 10L , Figures 11A to 11G , Figures 12A to 12D , Figures 13A to 13J , Figures 14A to 14G and Figures 16A to 16F The process is described below. For ease of explanation, some embodiments of the implementation will be discussed with reference to the operation performed on a device having a touch-sensitive display system 112. In such embodiments, the focus selector is optionally: a corresponding finger or stylus contact, a representation point corresponding to the finger or stylus contact (e.g., the center of gravity of the corresponding contact or a point associated with the corresponding contact), or the center of gravity of two or more contacts detected on the touch-sensitive display system 112. However, similar operation may optionally be performed on a device having a display 450 and a separate touch-sensitive surface 451 in response to a contact detected on the touch-sensitive surface 451 when the user interface shown in the figures, along with the focus selector, is displayed on the display 450.

[0201] Figures 5A to 5AT Example user interfaces are shown, based on some implementation schemes, for automatically displaying a customizable user interface when certain criteria are met.

[0202] exist Figure 5AIn this configuration, computer system 100 is in a low-power state. In some implementations, the low-power state is a shutdown state, in which portable multifunction devices display nothing. In some implementations, such as... Figure 5A As shown, in a low-power state, some user interface elements, such as the current time 5002, widgets 5004, 5006, and 5008, are displayed, but these user interface elements have reduced prominence (e.g., brightness) compared to when the computer system 100 is not in a low-power state. In some embodiments, displaying user interface elements with reduced prominence is referred to as a "normally on" display.

[0203] When the computer system 100 is in a low-power state, the computer system 100 detects user input 5010 (e.g., tap input) directed at a touch-sensitive surface (e.g., a touch screen) of the computer system 100.

[0204] exist Figure 5B In response to detecting user input 5010, computer system 100 displays a wake-up user interface (e.g., with...). Figure 4C1 The wake-up screen user interface 490 is the same as the wake-up user interface in the computer system 100. The wake-up user interface includes the current time 5002, widgets 5004, 5006, and 5008. The wake-up user interface also includes notifications 5014 and 5016 (e.g., not displayed when the computer system 100 is in a low-power state). When the wake-up user interface is displayed, the computer system 100 detects user input 5018 (e.g., swipe left input).

[0205] exist Figure 5C In response to the detection of user input 5018, computer system 100 displays a camera user interface. The camera user interface includes a preview of the current field of view of the computer system 100's camera, and also includes display functions for switching to video recording, taking photos, and switching to the field of view of different cameras on the computer system 100. When the camera user interface is displayed, computer system 100 detects user input 5020 (e.g., an upward swipe gesture starting from the bottom edge of computer system 100).

[0206] exist Figure 5D In response to detecting user input 5020, the portable multifunction device redisplays the wake-up user interface (e.g., Figure 5B(The wake-up user interface is shown). When the wake-up user interface is displayed, the user can interact with different elements of the wake-up user interface to perform different functions of the computer system 100. For example, in response to user input 5022 on area 5021. In response to user input 5024 (e.g., a swipe down from the upper right corner of the touch-sensitive display of the computer system 100), the computer system 100 displays a control center user interface. In response to user input 5026 pointing to widget 5006 (e.g., a tap), the computer system 100 displays a user interface corresponding to the application associated with widget 5006. In response to detecting user input 5028 pointing to notification 5014 (e.g., a tap), the computer system 100 displays additional content associated with notification 5014, and / or displays additional options for interacting with notification 5014 (e.g., an option to open the application associated with notification 5014). In response to detecting user input 5030 directed to notification 5016 (e.g., swipe left or right), computer system 100 displays a power-on option for opening an application associated with notification 5016, a power-on option for adjusting one or more notification settings, and / or a power-on option for clearing or eliminating notification 5016.

[0207] In response to the detection of user input 5032 (e.g., a swipe-down input), computer system 100 displays a search user interface (e.g., optionally including one or more suggested apps or features). In response to the detection of user input 5034 (e.g., a swipe-up input), computer system 100 displays a notification history (e.g., including one or more additional notifications besides notifications 5014 and 5016). In some embodiments, user input 5032 and / or user input 5034 may also be used to navigate between displays of additional notifications (e.g., scrolling) (e.g., if the number of notifications available for display is greater than the maximum number of notifications that computer system 100 can display simultaneously).

[0208] In response to detecting user input 5036 (e.g., swipe-left input) in an area of ​​the user interface that is not occupied by a notification (e.g., notification 5014 or notification 5016), computer system 100 displays the camera user interface (e.g., as shown in the image). Figures 5B to 5C As shown and described above). In response to detecting user input 5038 (e.g., swipe-to-right input) in an area of ​​the user interface that is not occupied by a notification, the computer system 100 displays a widget user interface (e.g., one or more widgets that include the computer system 100 and may optionally be configured by the user of the computer system 100).

[0209] In response to detecting user input 5040 (e.g., an upward swipe input from the bottom edge of computer system 100), and as Figure 5E As shown, computer system 100 displays an authentication user interface. In some implementations, such as... Figure 5E As shown, the authentication user interface includes one or more enablements for entering a password or passphrase for the user of the authentication computer system 100. In some embodiments, the computer system 100 authenticates the user by another method, such as by biometrics such as facial recognition or by scanning the user's fingerprint. The computer system 100 may optionally still display one or more enablements for entering a password or passphrase, providing an alternative authentication mechanism for biometric authentication (e.g., when the user's face is obscured by a mask or helmet or when the user is wearing gloves).

[0210] exist Figure 5F If the user successfully authenticates, the computer system 100 displays a main user interface. The main user interface includes application icons that can be interacted with to launch the corresponding applications of the computer system 100. The main user interface may also include one or more widgets that display application information without requiring the corresponding application to be launched or opened. The main user interface includes a settings icon 5043 (e.g., for accessing and / or configuring one or more settings of the computer system 100). In some embodiments, when the settings icon 5043 is activated by user input 5041, the computer system 100 displays a settings user interface for configuring different modes of the computer system 100 (e.g., the environment mode of the computer system 100). References are made below. Figure 5AL and Figure 5AM A more detailed description of the exemplary settings user interface is provided.

[0211] exist Figure 5G In this process, computer system 100 displays a wake-up user interface (e.g., because the user has not interacted with computer system 100 for a threshold amount of time, thus restoring computer system 100 to a "locked" (or unauthenticated) state; or because the user manually locks computer system 100). Figure 5G In this scenario, computer system 100 is not connected to a power source. The display of computer system 100 starts in portrait orientation and then rotates to landscape orientation. Because computer system 100 is not connected to a power source, computer system 100 maintains the display of the wake-up user interface.

[0212] In some implementations (e.g., such as) Figure 5G As shown), the computer system 100 is not configured to display the wake-up user interface in landscape orientation, so the computer system 100 maintains the display of the wake-up user interface in portrait orientation (e.g., even though the monitor of the computer system 100 has been rotated to landscape orientation).

[0213] Figure 5H yes Figure 5GAlternative forms are shown, and computer systems 100 are illustrated with different sizes (e.g., where the width and height of the displays of computer systems 100 are substantially similar, which allows computer systems 100 to operate more efficiently when the displays of computer systems 100 are in landscape orientation). Figure 5H In this scenario, computer system 100 is again not connected to a power source. The display of computer system 100 is rotated to landscape orientation, and computer system 100 maintains the display of the wake-up user interface, but with landscape orientation (e.g., with...). Figure 5G Compared to the longitudinal orientation in ( ).

[0214] Figure 5I It shows Figure 5G An alternative form. (and) Figure 5G On the contrary, Figure 5I In this configuration, computer system 100 is connected to a charging source via physical charger 5044. In response to detecting that physical charger 5044 is connected, computer system 100 displays an indicator 5042 indicating that computer system 100 is charging. For example, indicator 5042 includes text indicating that computer system 100 is charging and the current battery level (e.g., 38%).

[0215] exist Figure 5J In this configuration, after a threshold time has elapsed (e.g., 1 second, 2 seconds, 5 seconds, or 10 seconds), the computer system 100 stops displaying indicator 5042. In some embodiments, the computer system 100 displays an animated transition of indicator 5042 to (e.g., folded into) area 5046 or to a status area (e.g., the upper right corner of the computer system 100's display) for the battery indicator. Because the computer system 100's display remains portrait-oriented when connected to a charging source via physical charger 5044, the computer system 100 maintains the display of the wake-up user interface.

[0216] Figure 5K It shows Figure 5I An alternative form uses a wireless charger 5048 instead of a physical charger 5044. Figure 5K Various views of the computer system 100 are illustrated (when the display of the computer system 100 is in portrait orientation), showing the position of the wireless charger 5048 relative to the computer system 100. In response to detecting that the computer system 100 is connected to a charging source via the wireless charger 5048, the computer system 100 displays an indicator 5050. In some embodiments, the indicator 5050 is... Figure 5J The indicator 5042 is the same (e.g., when the computer system 100 is charging, regardless of whether the computer system 100 is charging via a physical cable or a wireless charger, the computer system 100 displays the same indicator). In some embodiments, with Figure 5J Compared to indicator 542, indicator 5050 has a different appearance (e.g., to provide visual feedback on a specific method by which computer system 100 is being charged).

[0217] Figure 5L It shows Figure 5I Another alternative form uses a long-range wireless charger 5052. In some embodiments, the long-range wireless charger 5052 includes at least one antenna configured to send (e.g., and / or focus) energy to the computer system 100 (e.g., without requiring the computer system 100 to be in close proximity to the long-range wireless charger 5052). In response to detecting that power is being received from the long-range wireless charger 5052, the computer system 100 displays an indicator 5054. In some embodiments, the indicator 5054 is associated with (e.g., Figure 5J The indicator 5042 and / or (e.g., Figure 5K The indicator 5054 is the same as indicator 5050. In some embodiments, indicator 5054 is different from indicators 5042 and 5050.

[0218] Figures 5J to 5L Different ways in which computer system 100 can be connected to a charging source (e.g., being charged) are illustrated. For ease of discussion, the following description will refer to charging source 5056, which means any suitable method of connecting computer system 100 to the charging source (e.g., wired charging, wireless charging, and / or long-range wireless charging, such as...). Figures 5J to 5L (As shown). The following description is to be understood as applicable to any (or all) variations of how computer system 100 is connected to a charging source.

[0219] Figure 5MThe illustration shows a computer system 100 connected to a charging source 5056, with the display of the computer system 100 in landscape orientation. Because both conditions are met simultaneously, the computer system 100 displays a clock user interface 5058 (e.g., an ambient mode user interface in which the computer system 100 operates in response to detecting that both conditions are met). In some embodiments, the computer system 100 also requires operation in a restricted mode (e.g., low-power mode or lockout mode) in order to display the clock user interface 5058. If the computer system 100 is connected to the charging source 5056 and the display of the computer system 100 is in landscape orientation, but the computer system 100 is not operating in a restricted mode, then the computer system 100 does not display the clock user interface 5058 (e.g., or enters ambient mode). If computer system 100 enters a restricted mode (e.g., in response to detecting that the user has locked computer system 100 and / or performing user input to operate computer system 100 in a low-power mode) (e.g., when computer system 100 remains connected to charging source 5056 and when the display of computer system 100 remains in landscape orientation), then computer system 100 displays clock user interface 5056 (e.g., and enters ambient mode) (e.g., in response to detecting that computer system 100 has entered restricted mode).

[0220] In some implementations, the clock user interface 5058 is a user interface displayed when a specific mode (e.g., "environment mode") of the computer system 100 is active. In some implementations, the specific mode is a mode in which the computer system 100 is configured to (e.g., continuously) display content relevant to the user of the computer system 100 without any user input.

[0221] In some implementations, in addition to the two conditions described above, computer system 100 may also require additional criteria to be met in order to display the clock user interface 5058 (e.g., an ambient mode user interface). For example, computer system 100 may also require computer system 100 to be in a locked (or other restricted) state (e.g., if computer system 100 is unlocked and its main screen user interface is displayed before the two conditions described in the preceding paragraph are met, computer system 100 will not switch to displaying the clock user interface 5058). For example, computer system 100 may also require computer system 100 not to be in communication with a vehicle (e.g., activity) (e.g., not connected to a vehicle such as a car via a wireless communication protocol such as Bluetooth). For example, computer system 100 may also require computer system 100 not to detect movement exceeding a threshold amount (e.g., computer system 100 is not being carried by a user walking or running, or computer system 100 is not in a moving vehicle). In some implementations, if the computer system 100 detects a movement amount exceeding a threshold within a threshold time amount while displaying the clock user interface 5058 (e.g., when the computer system 100 is operating in ambient mode), the computer system 100 stops displaying the clock user interface 50508 (e.g., the computer system 100 automatically stops operating in ambient mode).

[0222] exist Figure 5M In this configuration, computer system 100 displays indicator 5060 (e.g., in response to detecting that computer system 100 is connected to a charging source 5056). In some embodiments, and as in... Figure 5M As shown, indicator 5060 and (for example, Figure 5J The indicator 5042 (for example, Figure 5K The indicator 5050 and (for example, Figure 5L The indicator 5060 is different from indicator 5054. This provides visual feedback on whether the computer system 100 is currently in an environmental mode (e.g., or the normal mode of the computer system 100). In some embodiments, indicator 5060 is the same as at least one of indicator 5042, indicator 5050 and / or indicator 5054.

[0223] In some implementations, if an environment mode has never been active for computer system 100 (e.g., computer system 100 recently received an activation system update that enables environment modes), computer system 100 displays additional descriptions of the environment mode (e.g., the specific environment mode currently active, or information about a single environment mode available to computer system 100). In some implementations, the additional descriptions are displayed as pop-ups, banners, or other user interfaces, shown as an overlay. Figure 5MThe clock user interface 5058 is displayed on at least a portion of the system. In some embodiments, additional description is displayed before the clock user interface 5058 is displayed. In some embodiments, the additional description includes instructions for activating the ambient mode (e.g., the correct orientation of the display of the computer system 100 and / or the requirement for the computer system 100 to be connected to the charging power source 5056). In some embodiments, the additional information is displayed only when the computer system 100 first enters the ambient mode (e.g., or a single ambient mode), and not every time the computer system 100 enters the ambient mode (e.g., or a single ambient mode).

[0224] exist Figure 5N In some embodiments, after a threshold time period (e.g., 1 second, 2 seconds, 5 seconds, or 10 seconds), computer system 100 stops displaying indicator 5060. In some embodiments, computer system 100 stops displaying indicator 5060 and displays indicator 6062. In some embodiments, computer system 100 displays an animated transition where the indicator collapses into indicator 6062.

[0225] In response to detecting user input 6062 pointing to indicator 6062 (e.g., tap input), and as Figure 5O As shown, computer system 100 redisplays indicator 5060. In some embodiments, computer system 100 optionally displays additional power and / or battery information (e.g., in addition to or as a supplement to the information displayed in indicator 5060). Figure 5P In the middle, after a threshold time, the computer system 100 stops displaying (re-displaying) the indicator 5060.

[0226] In some implementation schemes, such as Figures 5Q to 5XAs shown, when the computer system 100 is in an ambient mode, the computer system 100 displays a context-dependent user interface. In some embodiments, the computer system 100 has different ambient modes, such as: (1) a time or clock ambient mode, (2) a widget ambient mode, (3) a home control ambient mode, (4) a voice memo ambient mode, (5) an ambient sound ambient mode, and / or (6) a visual media ambient mode. In some embodiments, the computer system 100 has only one ambient mode, but may display different categories of user interfaces (e.g., “ambient mode user interfaces”) for a single ambient mode of the computer system 100 (e.g., the first category of ambient mode user interfaces is a time / clock ambient mode user interface, the second category of ambient mode user interfaces is a widget ambient mode user interface, the third category of ambient mode user interfaces is a home control ambient mode user interface, the fourth category of ambient mode user interfaces is a voice memo ambient mode user interface, the fifth category of ambient mode user interfaces is an ambient sound ambient mode user interface, and / or the sixth category of ambient mode user interfaces is a visual media ambient mode user interface).

[0227] In some implementations, users of computer system 100 can configure settings for different environment modes or a single environment mode via a settings user interface. For example, Figure 5AL A settings user interface 5136 is shown for configuring the environment mode of computer system 100. In some embodiments, in response to detecting one or more user inputs (e.g., launching a settings application and / or opening the settings user interface of computer system 100)... Figure 5F The user input 5041 points to the settings icon 5043 on the main screen user interface of the computer system 100, and the computer system 100 displays the settings user interface 5136.

[0228] The user interface 5136 includes an "Environmental Mode" option 5140 for enabling or disabling an environment mode (e.g., whether the computer system 100 will operate in environment mode when certain criteria are detected). In some embodiments, the "Environmental Mode" option 5140 is a toggle mechanism (e.g., for enabling or disabling environment mode via user input 5152). In some embodiments, the "Environmental Mode" option 5140 includes additional options for specifying one or more criteria for when the computer system 100 operates in environment mode. In some embodiments, one or more criteria include default criteria (e.g., the computer system 100's display is in landscape orientation, and / or the computer system 100 is connected to a power source 5056). In some embodiments, the default criteria are not configurable (e.g., must always be met), but in some embodiments, the default criteria may be replaced by other user-specified criteria (e.g., to provide greater flexibility to the user when environment mode is active). In some embodiments, the "Environmental Mode" option 5140 also includes one or more additional options for configuring the environment mode user interface. For example, the user can configure which environment mode user interface (and / or the category of environment mode user interface) is displayed in which situations. Users can also configure the default environment mode user interface that is initially displayed when the computer system 100 enters environment mode (for example, or the default environment mode user interface that is initially displayed for a specific category of environment mode user interface when the computer system 100 displays a specific category of environment mode user interface).

[0229] The user interface 5136 includes a “normally on” option 5142 for enabling or displaying (e.g., user input 5154 on a toggle device via the “normally on” option 5142) a “normally on” state of the environment mode user interface (e.g., a state in which at least some user interface elements are always displayed but with reduced visual prominence when the computer system 100 is operating in a reduced power mode (e.g., hibernation mode)).

[0230] The user interface 5136 includes a “bump to wake” option 5146 for enabling or disabling (e.g., via user input 5158 on a toggle device of the “bump to wake” option 5146) the wake-up of the computer system 100 (e.g., from a sleep state or other low-power state) in response to the detection of vibration of the computer system 100 (e.g., vibration exceeding a threshold vibration amount) (e.g., vibration corresponding to an external impact on the support surface of the computer system 100, or a direct impact with the computer system 100 itself).

[0231] The user interface 5136 includes an "indicator" option 5148 for enabling or disabling (e.g., via user input 5160 on a toggle device of the "indicator" option 5148) the display of notifications (e.g., alerts) when the computer system 100 is operating in ambient mode. In some embodiments, when the "indicator" option is toggled on, the computer system 100 displays a visual indicator (e.g., a dot, banner, or other visual representation) for incoming and / or missed notifications. In some embodiments, the visual indicator includes a preview of the notification content corresponding to the respective notification.

[0232] The settings user interface 5136 includes a “night mode” option 5144 for enabling or disabling a “night mode” for the ambient mode user interface (e.g., a mode in which some user interface elements are displayed with a different appearance (e.g., reduced, simplified, dimmed, lowered, and / or less saturated) compared to the normal or default appearance of user interface elements). In some embodiments, the “night mode” option 5144 allows the user to configure additional options related to the night mode and / or ambient mode of the computer system 100. In response to detecting user input 5156 directed to option 5144, the computer system 100 displays a settings user interface 5162 (e.g., a settings user interface for configuring the night mode of the computer system 100).

[0233] Figure 5AM A settings user interface 5162 for configuring a night mode of computer system 100 is shown. The settings user interface 5162 includes an option 5164 for enabling or disabling (e.g., via user input 5168 on a toggle switch of option 5164) the night mode of computer system 100. The settings user interface 5162 includes a "Motion to Wake" option 5166 for enabling or disabling (e.g., via user input 5170 on a toggle switch of "Motion to Wake" option 5166) the wake-up of a device when motion is detected while computer system 100 is operating in night mode.

[0234] The user interface 5162 includes a "back" function indicator 5172 (e.g., when activated, causing the computer system 100 to redisplay). Figure 5AL The settings user interface 5136 includes a "settings" enable display 5150 (e.g., when activated, causing the computer system 100 to display or redisplay the settings user interface of the computer system 100 (e.g., a general settings user interface for configuring one or more settings of the computer system 100)).

[0235] Figures 5Q to 5X An exemplary user interface corresponding to an exemplary environment mode is shown. (Reference) Figures 6A to 6AJ and Figures 7A to 7V, Figures 9A to 9AA and Figures 15A to 15Q More details about these exemplary environment modes are described in more detail, as well as user inputs for switching between environment modes, switching between variations of the same environment mode, and / or interacting with different environment modes.

[0236] For ease of discussion, the following descriptions (including) Figures 6A to 6AN , Figures 7A to 7V , Figures 8A to 8K , Figures 9A to 9AA and Figures 15A to 15Q The description references different environment modes (e.g., time or clock environment mode, widget environment mode, home control environment mode, voice memo environment mode, ambient sound environment mode, and / or visual media environment mode) to provide an intuitive classification of environment mode user interfaces (e.g., variations of the time or clock environment mode include different methods of displaying time-related information and / or different types of clocks and / or clock faces, while variations of the widget environment mode include different methods of displaying widgets). However, in some implementations, only a single environment mode exists (e.g., for computer system 100, the environment mode is active or inactive), and all described user interfaces (e.g., a clock user interface corresponding to a time or clock environment mode; a widget user interface corresponding to a widget environment mode; a voice memo user interface corresponding to a voice memo environment mode; an ambient sound user interface corresponding to an ambient sound environment mode; and a media user interface corresponding to a visual media environment mode) are variations of the environment mode user interface for the (single) environment mode of computer system 100 (e.g., may also be described as: a clock user interface variation of the environment mode; a widget user interface variation of the environment mode; a voice memo user interface variation of the environment mode; an ambient sound user interface variation of the environment mode; and a media user interface variation of the environment mode).

[0237] In some implementation schemes, Figures 5Q to 5X Transformations between graphs may occur automatically (e.g., in response to meeting certain context-specific criteria, such as time-based or location-based criteria), but Figures 5Q to 5X Optional user input (e.g., swipe up input) for manually switching between different variations of the corresponding environment mode, or optional user input (e.g., swipe left input) for switching between different environment modes, is also shown. In some embodiments, even when the computer system 100 automatically switches between one or more environment modes, the user can still manually adjust the environment mode (e.g., via...). Figures 5Q to 5X (Optional user input).

[0238] Figure 5QA clock user interface 5068 (e.g., corresponding to a time or clock environment mode) is shown. In some embodiments, clock user interface 5068 is a variant of a clock user interface for a time or clock environment mode. Clock user interface 5058 is another variant of a clock user interface for a time or clock environment mode. In some embodiments, in response to (in Figure 5P (In the middle) User input 5066 was detected, and the clock user interface 5068 was displayed.

[0239] In some implementations, the clock user interface 5058 automatically displays according to a time-based standard (e.g., time of day). For example, in Figure 5Q In this context, the current time is 1:30 PM (e.g., "daytime"), and computer system 100 displays a clock user interface 5068 during "daytime" (e.g., a user-specified time period corresponding to daytime, or a predefined time period based at least in part on sunrise and / or sunset at the current location of computer system 100). In some embodiments, the clock user interface 5058 is displayed based on lighting standards (e.g., computer system 100 determines whether it is "daytime" or "nighttime" based on the amount of ambient light detectable by one or more sensors of computer system 100).

[0240] Figure 5R A clock user interface 5072 is illustrated (e.g., another variation of a clock user interface for a time or clock environment mode). In some embodiments, the clock user interface 5072 displays the current time with different levels of emphasis (e.g., and / or detail). For example, in Figure 5R In this case, the current time is 1:25 AM, and the computer system 100 only displays "1" to indicate the current hour (e.g., in contrast to displaying both hours and minutes, as in the clock user interface 5068 in the "daytime" scenario).

[0241] In some implementations, and as referenced Figures 9A to 9AA As discussed in further detail, the clock user interface 5072 is alternatively a user interface for different environment modes or different categories of environment mode user interfaces (e.g., a time or clock environment mode different from a "night" or hibernation environment mode). In some embodiments, the clock user interface 5072 is displayed when the computer system 100 is in a hibernation mode (e.g., a "hibernation" focus mode).

[0242] Figure 5SA widget user interface 5078 is shown (e.g., corresponding to a widget environment mode of computer system 100). In some embodiments, the widget user interface 5078 is referred to as an "infographic" user interface (e.g., and the widget environment mode is referred to as an "infographic environment mode"). In some embodiments, in response to detection Figure 5R User input 5076 (e.g., swiping left) displays a widget user interface 5078. The widget user interface 5078 is displayed context-dependently when a specific focus mode of the computer system 100 (e.g., a "Work" focus mode) is active. In some embodiments, when a focus mode of the computer system 100 is active, the computer system 100 adjusts how content (e.g., notifications, messages, calendar events, and / or other application content) is displayed (e.g., displaying a subset of available content) and / or generated (e.g., suppressing some notifications when the focus mode is active). In some embodiments, each corresponding focus mode of the computer system 100 modifies how content is displayed and / or generated accordingly (e.g., different focus modes adjust how content is displayed and / or generated differently).

[0243] In some implementations, the widget user interface 5078 is optionally displayed when the computer system 100 detects that the computer system 100 is in a working location (e.g., the location of a known office corresponding to the user of the computer system 100). In some implementations, the widget user interface 5078 is displayed when a "work" focus mode is active for the computer system 100, and the "work" focus mode is active when the computer system 100 is in a "work" location.

[0244] Widget user interface 5078 includes a calendar widget on the left and a notepad widget on the right. In some embodiments, a user can interact with widget user interface 5078 (e.g., without leaving the widget environment mode). For example, in response to detecting user input 5080 (e.g., an up / down swipe in the area occupied by the calendar widget), computer system 100 stops displaying the calendar widget and displays different widgets of computer system 100 (e.g., in addition to the calendar and notepad widgets). Similarly, in response to detecting user input 5082 (e.g., an up / down swipe in the area occupied by the notepad widget), computer system 100 stops displaying the notepad widget and displays different widgets. In some embodiments, a user can switch between a first subset of widgets via the left side of widget user interface 5078, and a user can switch between a second subset of widgets (e.g., different from the first subset of widgets) via the right side of widget user interface 5078.

[0245] In some implementations, different variations of the widget user interface for the widget environment mode include different available widgets (e.g., different subsets of the widgets on computer system 100). For example, widget user interface 5078 includes a calendar widget and a notepad widget, and another widget user interface may include one or more of a weather widget, a stock widget, a stopwatch widget, or another widget available on computer system 100.

[0246] In some implementations, each widget user interface for a widget environment mode has access to every available widget (e.g., or at least a subset of widgets) of the computer system 100, and variations in different widget user interfaces are relative to the layout and / or presentation of the widgets. For example, a variant of the widget user interface may display only a single widget, rather than as... Figure 5S The widget user interface 5078 displays two widgets side-by-side. Another variation of the widget user interface can display three or more widgets instead of just two. Figure 5S The widget user interface 5078 displays two widgets simultaneously. Another variation of the widget user interface can display widgets arranged vertically, instead of... Figure 5S The widget user interface 5078 is displayed horizontally. In some implementations, different widget user interfaces (e.g., including different widgets) are displayed depending on the context. For example, in Figure 5S In the user interface 5078, the widgets include a calendar widget and a notepad widget, while a "work" focus mode is active for the computer system 100. Different focus modes (e.g., such as...) Figure 5T When the "Family" focus mode is active, the computer system 100 displays various widgets, including stock widgets and weather widgets, such as... Figure 7C The different widget user interfaces are shown.

[0247] Figure 5T A home control user interface 5086 (e.g., corresponding to a home control environment mode) is shown. In some embodiments, in response to detection... Figure 5S User input 5084 (e.g., swiping left) displays the home control user interface 5086. The home control user interface 5086 is displayed depending on the context when the computer system 100's "Work" focus mode is active. In some implementations (e.g., as...) Figure 5U As shown), when the computer system 100 detects that the computer system 100 is in a preset position (e.g., the main position), the home control user interface 5086 is optionally displayed according to the context.

[0248] The home control user interface 5086 includes a climate indicator 5088, a lighting indicator 5090, a security indicator 5092, an audio / visual indicator 5094, and a water indicator 5096. The indicator displays of the home control user interface 5086 allow the user to adjust the settings of one or more features in the user's home (e.g., smart thermostat, smart lights, smart speakers, and / or smart TV) via the computer system 100.

[0249] In some implementations, different variations of the home control user interface for home control environment modes provide access to different power representations (and / or subsets of power representations). For example, one variation of the home control user interface may include a user-curated list (e.g., favorite) of power representations for frequently adjusted features. For example, different variations of the home control user interface may include power representations for adjusting settings of features in specific areas of a user's home (e.g., different variations of the home control user interface correspond to different rooms in a user's home).

[0250] In some implementation schemes, such as Figure 5U As shown, the user can interact with the home control user interface 5088. The computer system 100 detects user input 5098 into the directional lighting indicator 5090.

[0251] exist Figure 5V In response to the detection of user input 5098, computer system 100 displays a home control user interface 5100. The home control user interface 5100 includes indicator lights for adjusting lighting-related settings. For example, the home control user interface 5100 includes an indicator light 5106 that allows the user to adjust the settings of a table lamp in the user's home office (e.g., in response to the detection of user input 5108 pointing to indicator light 5106). The home control user interface also includes an indicator light 5102 that allows the user to adjust the settings of lights in the user's home entrance area, and an indicator light 5104 that allows the user to adjust the settings of lights in the user's home office.

[0252] In some implementation schemes, such as Figures 5W to 5X As shown, context-specific standards include those that depend on how the computer system 100 is charged. For example, in Figure 5P In this process, computer system 100 can be connected via a physical charger (e.g., Figures 5I to 5J The physical charger 5044 in the computer system 100 charges the computer, and the computer system 100 displays a clock user interface 5058. Figure 5X In this process, computer system 100 is charged via wireless charger 5048 (e.g., as...). Figure 5W As shown), and the computer system 100 displays a clock user interface 5110 (e.g., different from...). Figure 5PThe clock user interface 5058).

[0253] exist Figure 5Y In this system, computer system 100 displays an indicator 5112 corresponding to an active timer (e.g., a clock application of computer system 100). Indicator 5112 includes icons (e.g., clock, timer, or stopwatch icons) that provide visual feedback about the application and / or function represented by indicator 5112, and indicator 5112 includes the current time of the active timer (e.g., a timer counting down with 5:38 remaining). When indicator 5112 is displayed, computer system 100 detects user input 5114 (e.g., a tap) directed at indicator 5112.

[0254] In response to detecting user input 5114, and as Figure 5Z As shown, computer system 100 displays user interface 5116. User interface 5116 includes the current time (5:38 remaining) of the active timer, and also includes a pause indicator for pausing the active timer and a stop indicator for stopping or canceling the active timer. In some embodiments, computer system 100 displays an animated transition of indicator 5112 extending (e.g., downward and / or outward) into user interface 5116.

[0255] exist Figure 5AA In this embodiment, the display of computer system 100 is rotated from portrait orientation to landscape orientation. Because the display of computer system 100 is rotated to landscape orientation and computer system 100 is connected to a power source (e.g., as shown in charger 5136), computer system 100 displays user interface 5118. In some embodiments, user interface 5118 is a different appearance of user interface 5116 (e.g., but displayed with a different appearance and / or with enhanced visual prominence).

[0256] In some implementations, the user interface 5118 occupies the entire display of the computer system 100 (e.g., the user interface 5118 is a full-screen user interface). Similar to... Figure 5Z The user interface 5116 and user interface 5118 include a pause indicator for pausing the active timer, a stop indicator for stopping or canceling the active timer, and the current time of the active timer (5:38 remaining). Additionally, the user interface 5118 includes a (non-numerical) visual representation of the current time of the active timer. The gray areas of the user interface 5118 represent the amount of time elapsed since the active timer started, while the white areas of the user interface 5118 represent the time remaining before the active timer expires. Figure 5AAIn this example, the active timer is configured to count down from 10 minutes, and the active timer has 5 minutes and 38 seconds remaining. A visual indicator is displayed as a gray area slightly smaller than the white area (e.g., because 5:38 indicates that the total time of the active timer is just over halfway through). In some implementations, the visual indicator updates as the timer progresses (e.g., in real-time or at predetermined time intervals). For example, the gray area continues to expand further to the right as the timer progresses to indicate how close the timer is to its expiration.

[0257] In some implementations, the user interface 5118 displays content corresponding to multiple active timers (e.g., visual representations of multiple active timers and / or controls for interacting with multiple active timers). In some implementations, content corresponding to each active timer is displayed simultaneously in the user interface 5118 (e.g., vertically stacked or horizontally arranged).

[0258] When user interface 5118 is displayed, computer system 100 detects user input directed at user interface 5118 (e.g., swipe up input). In response to detecting user input 5120, and as... Figure 5AB As shown, computer system 100 displays a clock user interface 5058 (e.g., Figure 5M The same clock user interface 5058 is shown. The clock user interface 5058 is displayed because the monitor of the computer system 100 is landscape-oriented when connected to power. User interface 5122 is displayed as an overlay on a portion of user interface 5058. In some embodiments, user interface 5122 is similar to... Figure 5Z The user interface 5116 (e.g., but with a different appearance and a landscape orientation for the computer system 100, and when the computer system 100 is operating in ambient mode).

[0259] When user interface 5122 is displayed over user interface 5058, computer system 100 detects user input 5124 directed at user interface 5122 (e.g., swipe up input). In response to detecting user input 5124, and as Figure 5AC As shown, computer system 100 displays an indicator 5126 overlaid on user interface 5058. In some embodiments, indicator 5126 is similar to Figure 5Y Indicator 5112 (e.g., but with a different appearance and for the horizontal orientation of the display of computer system 100).

[0260] In some implementations, computer system 100 displays an indicator 5126 overlaid on user interface 5058 after a threshold amount of time (e.g., during periods of inactivity or when the user does not interact with computer system 100 and / or user interface 5122). In other words, computer system 100 may automatically (e.g., without requiring user input 5124) remove the indicator from the display. Figure 5AB The user interface 5122 was transformed into a display. Figure 5AC The indicator is 5126.

[0261] When indicator 5126 is displayed, computer system 100 detects user input 5128 directed at indicator 5126 (e.g., tap input or long press input). In response to detecting user input 5128, computer system 100 displays (e.g., redisplays) one or more user interfaces from the previously displayed user interface.

[0262] For example, Figure 5AD An example is shown in which computer system 100 redisplays user interface 5122 (e.g., overlays it on user interface 5058 again). Figure 5AE Another example of computer system 100 redisplaying user interface 5116 is shown. In some implementations, in response to detecting user input 5128, and based on determining that user input 5128 is a tap input, computer system 100 redisplays user interface 5512 (in...). Figure 5AD In response to detecting user input 5128, and based on determining that user input 5128 is a long press input, computer system 100 redisplays user interface 5116 (e.g., computer system 100 skips...). Figure 5AD The state shown, and alternatively from Figure 5AC The state shown directly changes to Figure 5AE The state shown). In some implementations, in response to detecting a pointer (e.g., Figure 5AD User input in user interface 5122, computer system 100 redisplays user interface 5116.

[0263] Figure 5AE User input 5130 is also shown (e.g., an upward swipe input starting from the bottom edge of the display of the computer system 100 in landscape orientation). The computer system 100 detects user input 5130 when the user interface 5118 is displayed.

[0264] In some implementations, since user input 5130 starts from the bottom edge of computer system 100 (e.g., contrary to starting from a non-edge area, such as...), Figure 5AA Similar to input 5120), therefore in response to detecting user input 5130, and as Figure 5AF and Figure 5AG As shown, computer system 100 displays a wake-up user interface (e.g., Figure 5G and / or Figure 5H The same wake-up user interface, but the current time is 9:05 instead of 9:00. In some implementations, the active timer of computer system 100 continues to run (e.g., because the user has not activated the stop power indicator for the active timer).

[0265] In some implementations, computer system 100 does not display the wake-up user interface, and in response to the detection of user input 5130, computer system 100 maintains the display of user interface 5118. In some implementations, in response to the detection of user input 5130, computer system 100 redisplays the clock user interface 5058 (e.g., instead of displaying the wake-up user interface). In some implementations, when a certain criterion is detected as no longer met, computer system 100 displays only the wake-up user interface (e.g., or the home screen user interface) (e.g., as referenced below). Figures 5AH to 5AK (As described) (e.g., computer system 100 remains in ambient mode and does not display a wake-up user interface or home screen user interface, while continuing to meet certain criteria).

[0266] Figure 5AF A wake-up user interface with a horizontal orientation is shown. Since the computer system 100's activity timer is still running (e.g., the user is not interacting with the activity timer's stop power indication in the user interface 5118), the computer system 100 also displays an indicator corresponding to the activity timer (e.g., similar to...). Figure 5Y The indicator 5112 is an indicator for horizontal orientation, which is overlaid on the wake-up user interface in horizontal orientation.

[0267] Figure 5AG yes Figure 5AF An alternative form is shown, and a wake-up user interface with a vertical orientation is illustrated. Since the active timer is still running on computer system 100, computer system 100 displays an indicator 5112 overlaid on the wake-up user interface (e.g., Figure 5Y The same indicator 5112 is shown.

[0268] Figures 5AH to 5AK An exemplary method for exiting the environment mode of computer system 100 is shown. Figure 5AH In the computer system 100, a clock user interface 5058 is displayed for the computer system 100's time or clock environment mode. The user begins to rotate the computer system 100's display from landscape orientation to portrait orientation. Figure 5AHThe dashed outline in the diagram indicates the initial landscape orientation of the display of computer system 100, serving as a reference for the amount of rotation of computer system 100. When the amount of rotation of computer system 100 (e.g., degrees) is below a threshold amount (e.g., the same or similar threshold amount used by computer system 100 to determine whether content is displayed in portrait or landscape orientation), computer system 100 maintains the display of clock user interface 5058 and remains in ambient mode. This prevents computer system 100 from accidentally exiting ambient mode (e.g., in the event of a slight bump or movement of computer system 100 and / or the surface on which computer system 100 is placed).

[0269] exist Figure 5AI In the middle, computer system 100 has rotated beyond a threshold amount, and computer system 100 exits ambient mode and displays an alternative user interface (e.g., wake-up user interface). The dashed outline shows... Figure 5AH The computer system 100's display is previously oriented (e.g., with a slight rotation below a threshold amount). In some embodiments, if the charging source 5056 is disconnected from the computer system 100 (e.g., regardless of the orientation of the computer system 100's display), the computer system 100 exits ambient mode. In some embodiments, in response to detecting user input 5132 directed at a portion of the clock user interface 5058 (e.g., a predetermined area of ​​the clock user interface 5058) (e.g., a tap on the user input), the computer system 100 exits ambient mode (e.g., regardless of the orientation of the computer system 100's display and regardless of whether the computer system 100 is connected to the charging source 5056).

[0270] In some implementations, the replacement user interface is the user interface displayed before the computer system 100 operates in ambient mode. For example, Figure 5G to Figure 5L Various states of the computer system 100 before entering ambient mode are shown (e.g., because the criteria for entering ambient mode are not met). In these states, the computer system 100 displays the wake-up user interface of the computer system 100. Figure 5AI In the middle, replacing the user interface is Figure 5G to Figure 5L The same wake-up user interface is displayed.

[0271] In some implementations, the computer system 100 displays a clock user interface 5058 to a display... Figure 5AI The animation transitions the user interface. In some implementations, the animation transitions are based on the amount of rotation of the computer system 100. For example, the animation transition occurs when the computer system 100 rotates by a first amount (e.g., greater than...). Figure 5AH The amount in, but less than Figure 5AIIt begins when the amount in the middle is reached, and rotates through the computer system to a threshold amount (e.g., 100 rotations). Figure 5AI The animation transition ends when the computer system 100 rotates to a threshold value. During the rotation of the computer system 100, the animation transition reflects the amount of rotation between the first value and the threshold value (e.g., the animation transition has progressed to the midpoint when the display of the computer system 100 has rotated to an orientation midway between the first value and the threshold value). In some embodiments, the animation transition is reversible, such that while the animation transition is in progress, the user can reverse the rotation direction of the computer system 100 to reverse the animation transition. In some embodiments, the animation transition is displayed only after the computer system 100 has rotated by the threshold value (e.g., a small amount of rotation will not result in the display of the animation transition).

[0272] Figure 5AJ Similar to Figure 5AH However, computer system 100 is displaying home control user interface 5086. Since computer system 100 has not rotated more than the threshold amount, computer system 100 operates in ambient mode and displays home control user interface 5086.

[0273] exist Figure 5 AK In this case, computer system 100 has rotated beyond a threshold amount. Computer system 100 exits ambient mode and displays an alternative user interface. In some implementations, Figure 5 AK Replacement user interface and Figure 5AI The alternative user interface is the same (e.g., when computer system 100 exits ambient mode, computer system 100 displays the same wake-up screen user interface, regardless of which user interface was displayed when computer system 100 was in ambient mode). In some embodiments, in response to detecting user input 5134 directed to a portion of home control user interface 5086 (e.g., a predetermined area of ​​home control user interface 5086) (e.g., a tap on user input), computer system 100 exits ambient mode (e.g., regardless of the orientation of the computer system 100's display and regardless of whether computer system 100 is connected to charging power source 5056).

[0274] In some implementation schemes, Figure 5 AK The alternative user interface is with Figure 5AI Different alternative user interfaces may be displayed in the environment (e.g., computer system 100 may display different alternative user interfaces depending on the user interface and / or user interface category displayed before exiting environment mode).

[0275] In some implementations, the computer system 100 displays a home control user interface 5086 to a display... Figure 5 AK The animated transition of the user interface is similar to the reference above. Figure 5AH and Figure 5AIThe animated transition described.

[0276] As disclosed herein, in some embodiments, computer system 100 performs personalization and / or customization of a user interface displayed based on a context surrounding the user interface. In some embodiments, the computer system determines the context based on an identifier associated with a charging source currently coupled to the computer system. In some embodiments, if the identifier is uniquely associated with a charging source, the computer system records the identifier and stores personalization and / or customization parameters associated with the unique identifier of the charging source, such that when the charging source is recoupled to the computer system at a later time and the computer system is able to recognize the identifier of the charging source as matching a previously encountered stored identifier of a charging source, the user experience is personalized and customized based on the personalization and / or customization parameters already stored associated with the unique identifier of the charging source. In this disclosure, a wireless or wired charging source coupled to the computer system transmits transmitter identification data packets to the computer system, for example, via one or more power transmission signals or via one or more signals not used for charging or powering the computer system (e.g., one or more Bluetooth signals, NFC signals, or signals of other communication protocols). In some embodiments, the transmitter identification data packets encode the identifier of the charging source and optionally include an indicator specifying whether the identifier is unique to the charging source. In some implementations, identifiers and optional indicators are encoded in the payload of the transmitter-identified data packet, which also includes a header specifying the nature of the data packet. In some implementations, the power source transmits the transmitter-identified data packet in response to a request from a computer system. The following example relates to... Figures 5AN to 5AR and Figures 17A to 17C The accompanying figures and descriptions contained herein provide further details on the interaction between the power source and the computer system, the format of the data packets, and / or how the computer system and the power source utilize the information contained in the data packets.

[0277] Figure 5ANA simplified block diagram of a wireless power transfer system 5101 according to some embodiments is illustrated. The wireless power transfer system 5101 includes a power transmitter (PTx) 5174 that wirelessly transmits power to a power receiver (PRx) 5184 via an inductive coupling 5194. The power transmitter 5174 is adapted to receive input power, which is converted by an inverter 5178 into an AC voltage with specific voltage and frequency characteristics. The inverter 5178 is adapted to be controlled by a controller / communication module 5180, which operates as further described below. In various embodiments, the inverter, controller, and communication module may be implemented in a common system, such as a microprocessor-based, microcontroller-based system. In some embodiments, the inverter controller may be implemented by a separate controller module and communication module having communication components therebetween. Depending on the implementation, the inverter 5178 can be constructed using any suitable circuit topology (e.g., full-bridge, half-bridge, etc.) and can be implemented using any suitable semiconductor switching device technology (e.g., MOSFETs, IGBTs, etc. made using silicon, silicon carbide, or gallium nitride devices).

[0278] In some implementations, inverter 5178 is adapted to deliver the generated AC voltage to transmitter coil 5176 of power transmitter 5174. This, in addition to allowing magnetic coupling to the receiver's wireless coil, Figure 5AN The transmitter coil block 5176 shown may include tuning circuitry (such as additional inductors and capacitors) that facilitates transmitter operation under various conditions, such as different degrees of magnetic coupling to the receiver and / or different operating frequencies. According to various embodiments, the wireless coil itself may be constructed in a variety of different ways. In some embodiments, the wireless coil is formed as a metal wire winding around a suitable spool. In some embodiments, the wireless coil is formed as a trace on a printed circuit board. Other arrangements are also possible and can be used in conjunction with the various embodiments described herein. The wireless transmitter coil 5176 may also include a magnetically permeable material (e.g., ferrite) core configured to influence the flux pattern of the coil in a manner suitable for a particular application. According to various embodiments, the teachings herein can be applied in conjunction with any of the various transmitter coil arrangements suitable for a given application.

[0279] In some implementations, the PTx controller / communication module 5180 is adapted to monitor the transmitter coil 51786 and use information derived therefrom to control the inverter 5178 to suit a given situation. For example, in some implementations, the controller / communication module 5180 is configured to operate the inverter 5178 at a given frequency or output voltage depending on the specific application. In some implementations, the controller / communication module 5180 is configured to receive information from the PRx 5184 and control the inverter 5178 accordingly. This information may be received via the power transmission coil (i.e., via in-band communication) or via a separate communication channel (e.g., out-of-band communication using NFC or Bluetooth). According to some implementations, for in-band communication, the controller / communication module 5180 is adapted to detect and decode signals (such as voltage, frequency, or load changes) applied to the magnetic link by PRx 5184 to receive information (e.g., requests for information, such as requests for an identifier for PTx 5174), and is adapted to instruct the inverter 5178 to modulate the delivered power by manipulating various parameters (such as voltage, frequency, phase, etc.) to transmit information to PRx 5184 (e.g., including, but not limited to, transmitter-identified data packets including an identifier for PTx and an indicator of whether the identifier is unique to PTx). In some implementations, the controller / communication module 5180 is configured to transmit data (e.g., including, but not limited to, transmitter-identified data packets) to PRx 5184 using Frequency Shift Keying (FSK) communication, in which the frequency of the inverter signal is modulated. In some implementations, the controller / communication module 5180 is configured to detect amplitude shift keying (ASK) communication (e.g., including but not limited to requests for transmitter identification of data packets) or load-modulated communication from the PRx 5184. In either case, the controller / communication module 5190 may be configured to change the current drawn on the receiver side to manipulate the waveform seen on the Tx coil 5176, thereby delivering information from the PRx 5184 to the PTx 5174. According to various implementations, for out-of-band communication, additional modules, such as WiFi, Bluetooth, or other radio links, or any other suitable communication channel, may be provided to allow communication between the PTx 5174 and the PRx 5184.

[0280] As mentioned above, the controller / communication module 5180 can be, for example, a single module disposed on a single integrated circuit, or it can be constructed from multiple modules / devices disposed on different integrated circuits, or a combination of integrated circuits and discrete circuits having both analog and digital components. The teachings herein are not limited to any particular arrangement of the controller / communication circuitry.

[0281] In some embodiments, PTx 5174 may optionally include other systems and components, such as a near-field communication (“NFC”) module 5182. In some embodiments, NFC module 5182 is adapted to communicate with a corresponding module or radio frequency identification (RFID) tag in PTx 5184 via power transfer coils 5176 and 7186. In other embodiments, NFC module 5182 is adapted to communicate with a corresponding module or tag using a separate physical channel 5196. In some embodiments, inductive power transfer may be optionally paused during out-of-band communication (e.g., NFC communication or Bluetooth communication) to prevent interference with out-of-band communication.

[0282] As described above, according to various embodiments, the wireless power transmission system also includes a wireless power receiver (PTx) 5184. According to some embodiments, the wireless power receiver PTx 5184 includes a receiver coil 5186 adapted to be magnetically coupled 5194 to a transmitter coil 5176. As discussed above, the transmitter coil 5176... Figure 5AN The receiver coil block 5186 shown may include tuning circuitry (such as additional inductors and capacitors) that facilitates receiver operation under various conditions, such as different degrees of magnetic coupling to the transmitter, different operating frequencies, etc. The wireless coil itself can be constructed in a variety of different ways. In some embodiments, the wireless coil may be formed as a metal wire winding around a suitable spool. In other embodiments, the wireless coil may be formed as a trace on a printed circuit board. Other arrangements are also possible and can be used in conjunction with the various embodiments described herein. According to various embodiments, the wireless receiver coil may also include a magnetically permeable material (e.g., ferrite) core configured to influence the flux pattern of the coil in a manner suitable for a particular application. The teachings herein can be applied in conjunction with any of the various receiver coil arrangements suitable for a given application.

[0283] In some embodiments, receiver coil 5186 outputs an AC voltage induced therein via transmitter coil 5176 through magnetic induction. This output AC voltage can be provided to rectifier 5188, which provides DC output power to one or more loads associated with PRx 5184 (e.g., a computer system battery, and / or various power-consuming components of the computer system to function). Rectifier 5188 can be controlled by controller / communication module 5190, which operates as further described below. In various embodiments, the rectifier controller and communication module can be implemented in a common system (such as a microprocessor-based, microcontroller-based system). In some embodiments, the rectifier controller can be implemented by a separate controller module and communication module having communication components therebetween. Rectifier 5188 can be constructed using any suitable circuit topology (e.g., full-bridge, half-bridge, etc.) and can be implemented using any suitable semiconductor switching device technology (e.g., MOSFETs, IGBTs, etc., made using silicon, silicon carbide, or gallium nitride devices).

[0284] In some embodiments, the PRx controller / communication module 5190 is adapted to monitor the receiver coil 5186 and use information derived therefrom to control the rectifier 5188 to suit a given situation. For example, in some embodiments, the controller / communication module 5190 is configured to operate the rectifier 5188 to provide a given output voltage depending on the specific application. In some embodiments, the controller / communication module 5190 is configured to transmit information to the PTx 5174 to effectively control the power delivered to the receiver. This information may be transmitted via the power transmitting coil (i.e., in-band communication) or via a separate communication channel (not shown, i.e., out-of-band communication). For in-band communication, the controller / communication module 5190 may, for example, modulate the load current or other electrical parameters of the received power to transmit information to the PTx 5174 (e.g., including, but not limited to, requests for a transmitter to identify a data packet containing an identifier of the PTx). In some embodiments, the controller / communication module 5190 is configured to detect and decode signals (such as voltage, frequency, or load changes) applied to the magnetic link by the PTx 5174 to receive information (e.g., including but not limited to transmitter identification data packets) from the PTx 5174. In some embodiments, the controller / communication module 5190 is configured to receive frequency shift keying (FSK) communication to convey data to the PRx 5184, in which the frequency of the inverter signal has been modulated. In some embodiments, the controller / communication module 5190 is configured to generate amplitude shift keying (ASK) communication or load-modulated communication from the PRx 5184. In either case, the controller / communication module 5190 may be configured to change the current drawn on the receiver side to manipulate the waveform seen on the Tx coil 5176, thereby delivering information from the PRx 5184 to the PTx 5174. For out-of-band communication, additional modules are available to allow communication between the PTx 5174 and PRx 5184, such as WiFi, Bluetooth, or other radio links, or any other suitable communication channel.

[0285] As mentioned above, according to some implementations, the controller / communication module 5190 may be, for example, a single module disposed on a single integrated circuit, or it may be constructed from multiple modules / devices disposed on different integrated circuits, or a combination of integrated circuits and discrete circuits having both analog and digital components. The teachings herein are not limited to any particular arrangement of the controller / communication circuitry.

[0286] In some embodiments, PRx 5184 may optionally include other systems and components, such as a near-field communication (“NFC”) module 5192. In some embodiments, NFC module 5192 is adapted to communicate with a corresponding module or radio frequency identification (RFID) tag in PTx 5174 via a power transfer coil. In some embodiments, NFC module 5192 is adapted to communicate with the corresponding module or tag using a separate physical channel 138. In some embodiments, inductive power transfer is paused while out-of-band communication is in progress to prevent interference with out-of-band communication on other channels.

[0287] Many variations and enhancements to the wireless power transmission system 5101 described above are possible, and the following teachings apply to any of such variations and enhancements. As described above, according to some implementations, the PRx controller / communication module 5190 and the PTx controller / communication module 5174 are adapted to communicate with each other to identify themselves and negotiate power delivery between them. This identification and negotiation process can be performed in conjunction with standard-defined protocols, such as those defined by the Wireless Power Union Qi standard, enabling interoperability between devices from different manufacturers. Compliance with such standards provides the benefit of interoperability at the potential cost of specialization. In other implementations, the identification and negotiation process can be performed in conjunction with proprietary protocols determined by the device manufacturer, which provides the benefit of improved flexibility and potential scalability, but the disadvantage is the loss of interoperability with devices that do not implement proprietary protocols.

[0288] In some implementations, the controller / communication module is configured to initiate a negotiation process according to a standard-defined protocol. During this negotiation process, one device, another device, or both devices may identify themselves in a standard-compliant manner as supporting a set of enhanced capabilities beyond the standard's scope. If both devices are capable of operating according to that enhanced capability set, the device may choose to operate according to that enhanced capability set. Otherwise, the device may choose to operate in combination with a standard-based capability set. In some implementations, the enhanced capability set includes the ability to operate at different frequencies, at different power levels, or in other ways beyond those defined in existing standards. In some implementations, the transmitted enhanced capabilities include the ability to transmit / encode and receive / decode transmitter-identified data packets, which includes a header identifying the data packet as a transmitter-identified data packet constructed according to a predefined structure, such as... Figure 5AQ , Figure 5AS and Figure 5ATAs shown, and including an indicator that the identifier carried in the payload of the data packet is unique to both the sender of the packet (e.g., PTx, and optionally PRx) and the sender's identifier. In some embodiments, the receiving device that identifies the data packet performs one or more operations (e.g., displaying a user interface and / or responding to user input) based on the unique identifier contained in the data packet. In some embodiments, if one of the devices does not support the enhanced capabilities, the sender-identified data packet is not transmitted, or the sender-identified data packet is not utilized in the personalization and customization of the operation of the receiver that identifies the data packet.

[0289] Figures 5AO to 5AP An exemplary communication exchange 5103 between a wireless power receiver (PRx) 5184 and a wireless power transmitter (PTx) 5174 is illustrated to enable the display of a corresponding customizable user interface (e.g., during standby mode as described herein, such as in...). Figures 5A to 5AM (in Chinese). In some implementations, communication exchange occurs via a communication protocol mechanism based on standards, such as the Wireless Power Transfer Alliance Qi charging protocol. The various communication packets described can take any of a variety of forms, thus employing different packet structures, different modulation schemes for transmitting packets, etc. The following description illustrates the components of the communication packets at a high level, but it should be understood that specific protocol implementations may specify different or additional data that may be included in these packets as appropriate.

[0290] refer to Figure 5AO The exemplary negotiation process begins with PRx 5184 transmitting a sequence of messages 5198-5202 to power transmitter 5174. This exchange can be triggered by PTx 5174 detecting the proximity of PRx 5184. The exchange can be performed using in-band communication at a frequency specified by the standard. In some embodiments, this frequency may be between approximately 100 kHz and approximately 250 kHz. In some embodiments, the frequency may be 128 kHz, 326 kHz, 360 kHz, 1.78 MHz, or another suitable frequency. In the illustrated example, the four messages 5198-5204 correspond to messages transmitted according to the Qi standard; however, in some embodiments, more or fewer messages may exist, and they may conform to alternative standards or protocols.

[0291] In some implementations, the first message 5198 is a SIG packet, i.e., a signal strength packet according to the Qi standard. In some implementations, the second message 5200 is an ID packet, i.e., an identification packet according to the Qi standard. In some implementations, the third message 5202 is a CFG packet, i.e., a configuration packet according to the Qi standard. In some implementations, these three packets correspond to the "verification" and "configuration phases" according to the Qi standard. Details of these packets (including the information contained therein and the effects of such packets in the system) are described in detail in their respective Qi standard versions and therefore will not be repeated here. It should be understood that different versions of such packets may be incorporated into various versions of the Qi standard, and later versions may combine, eliminate, or otherwise modify such packets. Therefore, the packets shown here are provided only as examples of standard-compliant initialization, and other similar arrangements may also be used. According to some implementations, upon receiving communication from PRx 5184, PTx 5174 transmits response packet 5204 ( Figure 5AO The ACK packet in the PRx 5184 acknowledges the communication from the PRx 5184. In implementations that utilize in-band communication to send packets such as SIG 5198, ID 5200, CFG 5200, and ACK 5204, it should be noted that such in-band (e.g., ASK, FSK) communication can be transmitted between the PRx 5184 and PTx 5174 using signals referred to herein as wireless power transmission signals.

[0292] Now go to Figure 5APThe diagram illustrates further communication between PRx 5184 and PTx 5174. In some implementations, upon receiving acknowledgment of communication from PRx 5184 (e.g., receiving response packet 5204 in Figure AO), PRx 5184 transmits another packet 5206 requesting PTx 5174 to provide a unique ID (if any). This can take the form of a “GET” request, where PRx 5184 requests PTx 5174 to transmit its unique ID (if any). If available, PTx 5174 transmits an “EXT ID” packet 5208 including PTx 5174’s unique ID. The “EXT ID” packet provides an identifier specific to (e.g., unique to) PTx 5174 (e.g., a device identification (ID) number or another type of ID number) (e.g., for authentication, security, and / or customization purposes). In some implementations, the “EXT ID” packet 5208 may include an identifier for a PTx 5174 that is not unique for the PTx 5174, and includes an indication that the identifier is not unique. In some implementations, the sender's identifier and the indication are included in the payload of the “EXT ID” packet, wherein the header of the “EXT ID” packet specifies the type of the “EXT ID” packet (e.g., as a sender identifier for a data packet). In some implementations, a device identifier is considered “unique” for a device if it is unique for the device within the corresponding manufacturer code of the device manufacturer, and the same identifier can be reused by another manufacturer within a different manufacturer code. In some implementations, the device identifier in a data packet includes the manufacturer code of the device manufacturer, followed by the device identifier assigned to the device by the manufacturer. In some implementations, a device identifier is considered unique for a device if it is unique for the device across all devices in the same group or type of device (e.g., all charging devices, all wireless charging devices, all wireless charging devices certified by a specific wireless charging specification, and / or other groups or types of devices). In some implementations, a device identifier is considered unique for a device if the probability of a consumer purchasing two devices with the same identifier is sufficiently low, such as below a probability threshold. It should be understood that the degree of uniqueness depends on the bit length of the identifier payload. In other words, if 20 bits are used for the identifier field, the field will support 2^20, or approximately one million, unique identifiers.

[0293] In some implementations, PRx 5184 transmits another packet 5210 requesting PTx 5174 to provide personalization information (if any). This may take the form of a “GET” request, in which PRx 5184 requests PTx 5174 to transmit personalization information (if any). If available, PTx 5174 transmits a “UI parameters” packet 5212 that includes the personalization information. The “UI parameters” packet 5212 may provide information related to personalization and / or customization specific to (e.g., unique to) PTx 5174 (e.g., personalization and / or customization of user preferences, the user interface to be displayed, or other information related to the customization and / or personalization of PRx 5184 and / or PTx 5174 and / or the user interface displayed by PRx 5184 and / or PTx 5174). In some implementations, the information in the "UI parameters" group 5212 is included in the "EXT ID" group 5208 (e.g., requests 5206 and 5210 are combined, and groups 5208 and 5212 are combined).

[0294] In some implementations, PRx 5184 does not request a unique ID and / or personalized information from PTx 5174. Upon receiving initial communication from PRx 5184, PTx 5174 automatically transmits the unique ID and / or personalized information as part of acknowledgment 5204 (e.g., the “EXT ID” packet 5208 and “UI Parameters” packet 5212 in Figure AP are included). Figure 5AO (in ACK 5204).

[0295] Figure 5AO and Figure 5AP The power transfer steps are also illustrated. Figure 5AO The power transmission 5214 in the middle, and Figure 5APPower transfer steps 5216 and 5218 are described in some embodiments. In some implementations, the power transfer step (5214) occurs after PTx 5174 sends an acknowledgment packet 5204 (e.g., power transfer occurs / starts before (and / or during) PTx 5174 sends a unique ID and / or personalized information to PRx 5184; and / or the wireless power signal can be used to enable in-band transmission of the “EXT ID” packet 5208 and / or the “UI parameter” packet 5212 from PTx 5174 to PRx 5184). In some implementations, the power transfer step (5216) occurs after PTx 5174 sends the “EXT ID” packet 5208 (e.g., power transfer occurs / starts after PRx 5184 receives the “EXT ID” packet 5208 from PTx 5174; and / or the wireless power signal can be used to enable in-band transmission of the “UI parameter” packet 5212 from PTx 5174 to PRx 5184). In some implementations, the power transfer step (5218) occurs after PTx 5174 sends the "UI parameter" packet 5212. In some implementations, the power transfer signal used to transfer power to PRx is a portion of a wireless power signal encoded with information (e.g., messages as described above) at various intervals, and the power transfer to PRx is accomplished by at least some portions of the wireless power transfer signal (e.g., in some cases, a previously encoded wireless power transfer signal, or in other cases, a previously uncoded wireless power transfer signal).

[0296] Figure 5AQ An example data grouping is shown (e.g., Figure 5AP The exemplary “EXT ID” group 5206 and / or the exemplary “UI Parameters” group 5210 shown above are examples of data groups. Figure 5AO and Figure 5AP Discussion (and reference below) Figure 5AR and Figures 17A to 17C (Further discussion) Unique ID. For ease of illustration and discussion, Figure 5AQ The example data packet in the example includes 8 bytes (bytes B0-B8), but it should be understood that the data packet may include any suitable number of bytes.

[0297] In some implementation schemes, Figure 5AQ The data packets in the packet include a preamble (“0 (selector)”) and / or a reserved portion (e.g., as shown in B0-B4). For example, the reserved portion may include a header (e.g., identifying the type of packet and / or protocol information used for the data packet) and / or a checksum (e.g., for error correction and / or verification purposes). In some embodiments, the header and / or checksum are each 8 bits (1 byte) of data, or any other suitable number of bits.

[0298] In some implementations, the data packet includes a payload portion (e.g., bytes B5-B8). The payload portion includes an indicator (bit b7 of byte B5) that indicates whether the payload portion includes a unique ID (e.g., a unique identifier for PTx5174, as referenced above). Figure 5AO to 5AP (As described). In some embodiments, indicator bit b7 is "1" if the payload portion includes a unique ID, and is "0" when the payload portion does not include a unique ID (e.g., bit b7 is a Boolean indicator of whether the payload portion includes a unique ID). In some embodiments, indicator bit b7 (or unique ID) is not included in the payload portion if the payload portion does not include a unique ID. In some embodiments, the indicator is 1 bit and the unique ID is 31 bits (e.g., the payload is 32 bits). In some embodiments, the indicator is 1 bit and the unique ID is any suitable number of bits (e.g., N-1 bits, where N is the total number of bits including the payload portion) such that the payload is of a suitable number of bits (e.g., to meet certain criteria for managing the structure of the payload portion of data packets and / or data packets). For example, in some embodiments, the payload portion is 64 bits, the indicator is 1 bit, and the unique ID is 63 bits (where N = 64, and N-1 = 64-1 = 63).

[0299] In some implementations, the payload portion also includes personalized information (e.g., in addition to the indicator and unique ID). In some implementations (e.g., where...) Figure 5AQ The example data grouping in is Figure 5AP (Example "UI Parameters" group 5212 in the example), the payload portion includes personalized information (e.g., instead of...) Figure 5AQ (The indicator and / or unique ID shown). In some embodiments, the personalization information is optionally loaded onto the PTx by the PTx's manufacturer. In some embodiments, after customization or personalization occurs on the computer system corresponding to the PRx, the personalization information (e.g., an indicator of whether personalization is based on a unique sender identifier, and / or customization parameters associated with the unique sender identifier) ​​previously sent from the same or different PRx to the PTx is intended for future customization and personalization.

[0300] Figure 5AS Another example data grouping is shown (e.g., Figure 5AP The exemplary “EXT ID” group 5206 and / or the exemplary “UI Parameters” group 5210 shown above are examples of data groups. Figure 5AO and Figure 5AP Discussion (and reference below) Figure 5AR and Figures 17A to 17C (Further discussion) ID. For ease of illustration and discussion, Figure 5AS The example data packet in the example includes 8 bytes (bytes B0-B8), but it should be understood that the data packet may include any suitable number of bytes.

[0301] In some implementation schemes, Figure 5AS The data packets include a preamble (“0 (selector)”) and / or reserved portions (e.g., as shown in B0-B4 and B6b2-B8). For example, the reserved portions may include a header (e.g., identifying the type of packet and / or protocol information used for the data packets) and / or a checksum (e.g., for error correction and / or verification purposes). In some implementations, the header and / or checksum are each 8 bits (1 byte) of data, or any other suitable number of bits. The reserved portions (e.g., B6b2-B8) may also provide an indication of whether the ID portion of B4-B6 is intended to serve as a unique ID. In one example, in Figure 5AS In the data packet, the device identifier is included in a portion of the payload spanning B4b6-B6b3 (20 bits), and an indication of whether the device identifier is unique is included in a manufacturer-reserved portion of the payload spanning B6b2-B8 (19 bits). In some embodiments, to indicate that the device identifier included in the payload is unique, the manufacturer-reserved portion of the payload is set to a non-zero value. In some embodiments, the receiving... Figure 5ASThe computer system transmitting the data packets will be able to determine whether to perform personalization and / or customization based on the device identifier decoded from the payload (e.g., from the portion of the payload spanning B4b6-B6b3) based on whether the manufacturer-reserved portion (e.g., the portion across B6b2-B8) is set to a non-zero value. For example, in some embodiments, if the manufacturer-reserved portion is set to a non-zero value (e.g., 1 or another non-zero integer value less than or equal to 2^19), the computer system treats the identifier as unique to the PTx and performs personalization and / or customization based on the unique identifier of the PTx. On the other hand, if the manufacturer-reserved portion is set to zero, the computer system does not treat the identifier as unique to the PTx and abandons performing personalization and / or customization based on the identifier obtained from the data packets. In some embodiments, when the PTx transmits data packets, the PTx sets the manufacturer-reserved portion to a non-zero value according to the manufacturer specification preloaded into the PTx. The manufacturer is also responsible for preloading the PTx with a unique identifier, which is a number in the range of 2^20 (approximately one million), a range that can be accommodated in a portion of the payload of the device identifier (e.g., in B4b6-B6b3 of the payload). In some implementations, the manufacturer may use a hash function to generate the unique identifier, such that the identifier is extended within the range of 2^20 (approximately one million).

[0302] Figure 5AT Another example of data grouping is shown (e.g., Figure 5AP The exemplary “EXT ID” group 5206 and / or the exemplary “UI Parameters” group 5210 shown above are examples of data groups. Figure 5AO and Figure 5AP Discussion (and reference below) Figure 5AR and Figures 17A to 17C (Further discussion) ID. For ease of illustration and discussion, Figure 5AT The example data packet in the example includes 8 bytes (bytes B0-B8), but it should be understood that the data packet may include any suitable number of bytes.

[0303] In some implementation schemes, Figure 5AT The data packets include a preamble (“0 (selector)”) and / or reserved portions (e.g., as shown in B0-B4 and B6b2-B8). For example, the reserved portions may include a header (e.g., identifying the type of packet and / or protocol information used for the data packets) and / or a checksum (e.g., for error correction and / or verification purposes). In some implementations, the header and / or checksum are each 8 bits (1 byte) of data, or any other suitable number of bits. The reserved portions (e.g., B0b3-B4b7) may also provide an indication of whether the ID portion of B4-B6 is intended to serve as a unique ID. In one example, in Figure 5AT In the data grouping, the device identifier is included in the portion of the payload spanning at least B4b6-B6b3 (20 bits or longer), and an indication of whether the device identifier is unique is included in a reserved portion of the payload spanning B0b3-B4b7 (e.g., at B0b0, or in another sub-portion of the reserved portion). In some embodiments, to indicate that the device identifier included in the payload is unique, the manufacturer reserved portion of the payload is set to a non-zero value. In some embodiments, the receiving... Figure 5AS The computer system transmitting the data packets will be able to determine whether to perform personalization and / or customization based on the device identifier decoded from the payload (e.g., from the portion of the payload spanning B0b3-B4b7) based on whether the reserved portion (e.g., B0b0) is set to a non-zero value (e.g., "1"). For example, in some embodiments, if the reserved portion (e.g., B0b0) is set to a non-zero value (e.g., "1"), the computer system treats the identifier as unique to the PTx and performs personalization and / or customization based on the unique identifier of the PTx. On the other hand, if the reserved portion (e.g., B0b0) is set to zero, the computer system does not treat the identifier as unique to the PTx and abandons performing personalization and / or customization based on the identifier obtained from the data packets. In some embodiments, when the PTx transmits data packets, the PTx sets the reserved portion (e.g., B0b0) to a non-zero value (e.g., "1") according to the manufacturer specifications preloaded into the PTx. The manufacturer is also responsible for preloading the PTx with a unique identifier, which is a number in the range of 2^20 (approximately one million), a range that can be accommodated in a portion of the payload of the device identifier (e.g., in B4b6-B6b3 of the payload, or further extended to the manufacturer-reserved portion B6b2-B8). In some embodiments, the manufacturer may use a hash function to generate the unique identifier, such that the identifier is extended within the range of 2^20 (approximately one million) or the extended range including the manufacturer-reserved portion B6b2-B8. In some embodiments, the device identifier includes a manufacturer code, followed by a device identifier assigned to the device by the manufacturer, and the unique identifier of the device includes the manufacturer code and the identifier assigned to the device by the manufacturer. In some embodiments, based on instructions stored on a computer system and / or instructions and preferences established by the manufacturer of the PTx (which may be received in a transmitter identification data packet containing an indicator of whether the device identifier is unique and / or in an additional data packet following the transmitter identification data packet), the PTx selects a unique identifier based on the PTx to perform personalization and / or customization.

[0304] Figure 5ARAn exemplary method 50000 for conveying personalized information between PRx and PTx is illustrated. First, PRx (e.g., Figures 5AN to 5AP PRx 5184 in PTx (e.g., Figures 5AN to 5AP The PRx (5174) moves within the vicinity of the PTx (e.g., within the wireless charging range and / or coupling range) (50002). For example, the PRx is a computer system or electronic device, such as a smartphone or other handheld device, and the PTx is a wireless charger. According to some implementations, the PRx is in the "vicinity" of the PTx when it is able to wirelessly receive power from the PTx.

[0305] According to some implementations, PRx uses (50004) pulse ping to detect PTx (or alternatively, PTx uses pulse ping to detect PRx, or both PTx and PRx use pulse ping to detect another device).

[0306] According to some implementations, in response to the detection of a ping from another device, the PRx and / or PTx initiates (50006) a digital handshake between the PRx and PTx. As discussed in more detail below with respect to subsequent steps of method 50000, the digital handshake allows the PRx and PTx to communicate relevant information about personalization information that can be used by the PRx (and / or PTx) to customize one or more outputs (e.g., a display user interface customized based on the personalization information). In some implementations, the digital handshake involves the transmission and / or verification of a unique identifier (e.g., an identification number) and corresponding personalization information optionally specific to (e.g., bound to and / or otherwise corresponding to) the corresponding unique identifier (hereinafter referred to as "unique ID"). This allows, for example, the PRx to identify a specific neighboring PTx and display a customized user interface corresponding to that specific PTx (e.g., the PRx displays a first customized user interface when it is neighboring a first PTx, and displays a second customized user interface different from the first customized user interface when it is neighboring a second PTx different from the first PTx). In some implementations, if PRx does not receive and / or PTx does not transmit a unique identifier and / or personalized information (e.g., no identifier is transmitted, or an identifier that is not unique to PTx is transmitted), then PRx abandons customization and provides the user with a generic and / or default user interface or interaction behavior.

[0307] In some implementations, PRx requests (50008) PTx to transmit a unique ID from PTx to PRx (e.g., PRx sends a request to PTx to cause PTx to send a unique ID packet), and PTx does not transmit the unique ID until it receives the request from PRx. In some implementations, PRx does not request a unique ID (e.g., PTx automatically transmits the unique ID (if available), without needing to receive a request from PRx), such as... Figure 5AR The dashed outline of step 50008 is shown in the figure.

[0308] PTx transmits a unique ID (50010) to PRx (e.g., automatically or in response to a request received from PRx). In some embodiments, the unique ID packet includes personalization information. In some embodiments, the personalization information includes customizations associated with the displayed user interface (e.g., the personalization information includes a customized and / or user-configured user interface that may be displayed when PRx and PTx are in close proximity, such as when PRx is being wirelessly charged by PTx). In some embodiments, the personalization information is sent in a separate packet (e.g., in a manner similar to the unique ID described above with reference to steps 50008 and 50010).

[0309] According to various implementations, this interaction sequence and data exchange allows the PRx to display different contextual information depending on the identity of the PTx coupled to the PRx. For example, when the PRx (e.g., a smartphone or handheld device) is within range of a first PTx (e.g., a wireless charger in a bedroom), the PRx can display a context-sensitive user interface, such as those referenced below. Figures 9A to 9G The described clock user interface 9002 (and / or clock user interface 9008) (e.g., a clock user interface suitable for and / or configured for bedtime / nighttime use). According to some embodiments, when the PRx is within range of a second PTx (e.g., a wireless charger in an office or work location), the PRx detects that the PTx has a unique identifier different from the previous one and displays a different context-sensitive user interface, such as the one referenced above. Figure 5S The described widget user interface 5078.

[0310] In some implementations, the PTx also initiates (50012) a wireless power transfer. In some implementations, the PTx initiates the wireless power transfer after detecting that the PRx is within the PTx's vicinity (e.g., in response to this). In some implementations, the wireless power transfer involves the transmission of a wireless power signal, and the digital handshake uses the wireless power signal to transmit at least some of the communications involved in the digital handshake (e.g., the digital handshake occurs over in-band communication). In some implementations, a unique ID is also transmitted via the wireless power signal (e.g., in-band communication).

[0311] After receiving a unique ID from PTx, PRx displays (50014) a customized user interface based on the personalized information received via the unique ID (e.g., as referenced herein). Figures 5A to 5AM , Figures 6A to 6AN , Figures 7A to 7V , Figures 8A to 8J K and / or Figures 9A to 9AA One or more custom user interfaces in the custom user interface discussed.

[0312] In some implementations, the PTx performs (e.g., all or substantially all) the activity steps that require data transmission (e.g., sending). For example, the PTx uses pulse ping to detect the PRx, send a unique ID, and / or initiate wireless power transmission, which allows the PTx to handle all transmission steps via wireless power signals (e.g., in-band).

[0313] The following is an additional description of a computer system (e.g., having exemplary hardware) for displaying a customized user interface configured according to customized parameters corresponding to the received identity of the charging source, according to various embodiments. In some embodiments, the computer system described below is configured to perform the functions referenced above. Figure 5AR The described operations and / or the execution of the above references Figures 17A to 17C The operations described in method 17000. Some of the operations described below may be combined, and / or the order of some operations may be changed.

[0314] In some implementations, the computer system includes: a display generation component (e.g., a touchscreen display, a stand-alone display, or another type of display enclosed in the same housing as some or all of the other components of the computer system) (e.g., Figure 1A The touch-sensitive display system 112 in the middle Figure 2 and Figures 4A to 4C2 The touchscreen 112 in the device; one or more sensors for detecting user input (e.g., camera, touch-sensitive surface, pressure sensor, orientation sensor, motion sensor and / or other input sensors) (e.g., Figure 1A The touch-sensitive display system 112 in the middle Figure 2 and Figure 4A To the touchscreen 112 in Figure 4CS, Figure 1A and Figure 2 One or more contact strength sensors 165 Figure 3 Keyboard / mouse 350 and / or Figure 3 The touchpad 355 in the middle); power transmission coil, which is adapted to receive power from a charging source (e.g., a wireless power transmission (WPT) transmitting device or a wired power transmission device) (e.g., Figure 5AN The receiving coil 5186 in the middle receives the power transmission signal; the rectifier (e.g., Figure 5AN The rectifier 5188 in the rectifier is adapted to charge a computer system battery (e.g., a battery powering one or more processors, one or more sensors, and / or display generating components) using a power transfer signal received from a charging source by a power transfer coil; and a communication circuit (e.g., Figure 5AN The PRx controller / communication module 5190 is configured to obtain identification data representing the corresponding identity of the charging source from at least one of the power transfer signals received from the charging source (e.g., in some embodiments, the power transfer coil, rectifier, and communication circuitry are integrated into a single charging component that receives power from the charging source and supplies power to the computer system's battery); one or more processors; and a memory that stores instructions that, when executed by one or more processors, cause the processors to perform operations.

[0315] The operation includes: detecting a first event (e.g., a change in the orientation of the display-generating component, e.g., as...) Figure 5G (as shown) and / or changes in the charging state of the computer system (e.g., as shown) Figures 5I to 5K An event that is at least one of the events shown, or other events related to whether the corresponding operating mode of the device is activated (e.g., detecting the user's hand and / or the user's gaze toward the computer system, such as...). Figure 9B and Figure 9C (as shown). In some implementations, the first event can be any of a plurality of events that trigger the determination of the identity of the charging source and / or the subsequent display of a first customizable user interface based on identification data received in a power transfer signal from the charging source.

[0316] The operation includes responding to the detection of a first event (e.g., in response to the detection of the first event, or in response to the detection of another triggering event different from the first event) (e.g., in Figure 5M In this context, computer system 100 has been rotated to a lateral orientation and connected to charging source 5056. The computer system is coupled to the charging source when it is in a lateral orientation, or when the computer system is coupled to the charging source and in a lateral orientation, conditions for entering a low-power mode or a locked state are met, or other events occur.

[0317] The operation includes satisfying a first criterion based on the determination that the result is the first event (e.g., in...). Figure 5M In this configuration, the computer system 100 is both in a horizontal orientation and connected to a charging source 5056 or another customizable user interface described herein, displaying a corresponding customizable user interface that was not displayed prior to the detection of the first event (e.g., Figure 5MThe clock user interface 5058 (for example, in Figure 5G to Figure 5L The clock user interface 5058 is not shown in the document. In some embodiments, the corresponding customizable user interface includes a user interface with customizable content, appearance, and / or behavior, and includes, but is not limited to, the customizable user interface described herein. In some embodiments, meeting the first criterion does not require the computer system to be charged by a power source. In some embodiments, meeting the first criterion does not require the computer system to be in a particular orientation. In some embodiments, the first criterion requires other conditions (e.g., conditions regarding authentication status, current time, current location, and / or other conditions) to be met before the first customizable user interface can be displayed.

[0318] Displaying a corresponding customizable user interface includes: based on one or more power transmission signals (e.g., wireless power transmission signals or wired power transmission signals) received from a charging source (e.g., a power transmission coil of a computer system or another charging component of a computer system), including first identification data (e.g., indicating a first identity of the charging source) representing a first identity of the charging source. Figure 5AQ and Figure 5AR The first identity of the charging source is stored in the computer system in association with a unique ID or another unique identifier (and optionally, the first identity of the charging source is stored in association with a first set of customized parameters), and a first customizable user interface corresponding to the first identity of the charging source is displayed (e.g., a first customizable user interface configured according to a first set of customized parameters corresponding to the first identity of the charging source) (e.g., such as...). Figure 5AR(as described in step 50014 of method 50000) (e.g., having a user interface with content, appearance, and / or behavior customized based on a first set of customized parameters corresponding to a first identity of the charging source obtained from a power transfer signal received from the charging source). In some embodiments, one or more processors and memories include embedded systems, firmware, software, hardware, and / or combinations of both or more of the above to perform at least some of the steps described herein. For example, in some embodiments, the reception of the power transfer signal, encoding and transmitting a request for identification data to the charging source, decoding the power transfer signal received from the charging source to obtain the identification data of the charging source, and charging the battery of the computer system are performed by a subsystem different from the processor and memory that provide the main operating system and associated functions of the computer system, including but not limited to: evaluating conditions for displaying various user interfaces, storing identifiers of known charging sources in association with corresponding customized parameters of known charging sources for various types of customizable user interfaces, comparing the identifier of a newly acquired charging source with the stored identifier of a previously encountered charging source; and customizing the stored customized parameters in association with the currently used charging source based on user input received when the currently used charging source is coupled to the computer system. In some implementations, the operations described herein may be assigned to different types of processors in the computer system, and for the sake of brevity, they will not be listed here. In some implementations, the payload of a transmitter identification packet carried by one or more power transmission signals includes an indication that the corresponding identifier carried in the transmitter identification packet's payload is unique to the charging source, and according to this indication, the computer system performs personalization and / or customization steps for the charging source, and displays a customized version of the corresponding customizable user interface based on the charging source's unique identifier. In some implementations, the payload of a transmitter identification packet carried by one or more power transmission signals includes an indication that the corresponding identifier carried in the transmitter identification packet's payload is not unique to the charging source, and according to this indication, the computer system does not perform personalization and / or customization steps for the charging source, and displays a generic or default version of the corresponding customizable user interface, and does not record personalization and / or customization performed by the user when the charging source is coupled to the computer system.In some implementations, the computer system performs automatic personalization and / or customization steps (e.g., storing unique identifiers, comparing unique identifiers, and storing personalization parameters associated with the unique identifiers) to ensure that the display of the next user interface is personalized and / or customized based on a previously recorded state of the user interface, according to a determination that personalization criteria are met. These personalization criteria include requirements (e.g., via in-band power transfer signals or out-of-band communication packets) for a transmitter identity packet received from the charging source to include an indicator indicating that the identifier carried in the transmitter identity packet is unique to the charging source in order to meet the personalization criteria. For example, in some implementations, the indicator in the payload of the determined data packet is set to a non-zero value (e.g., "1" or another positive integer value). Figure 5AQ Indicators in B5b7 Figure 5AS Manufacturer-reserved portions of B6b2-B8 in the series or Figure 5AT (B0b0 in the computer system) Figure 5AQ , Figure 5AS and / or Figure 5AT The transmitter identification data packet shown includes a unique identifier for the charging source and should be used for personalization / customization.

[0319] In some embodiments, operation includes displaying a corresponding customizable user interface that was not displayed prior to the detection of the first event, including: based on determining that one or more power transmission signals (e.g., wireless or wired power transmission signals) received from a charging source (e.g., via a power transmission coil of the computer system or another charging component of the computer system) include second identification data representing a second identity different from the first identity of the charging source (and optionally, the second identity of the charging source is stored at the computer system in association with a second set of customized parameters different from the first set of customized parameters), displaying a second customizable user interface corresponding to the second identity of the charging source (e.g., a second customizable user interface configured according to the second set of customized parameters corresponding to the second identity of the charging source) (e.g., a user interface having content, appearance, and / or behavior customized based on the second set of customized parameters corresponding to the second identity of the charging source obtained from the power transmission signals received from the charging source). In some embodiments, the computer system may be charged by multiple different charging sources, and the computer system is capable of distinguishing different charging sources based on identification data embedded in the power transmission signals received from different charging sources, since the different charging sources are coupled to the computer system respectively at a given time. In some embodiments, the payload of the transmitter identification packet carried by one or more power transmission signals includes an indication that the corresponding identifier carried in the transmitter identification packet's payload is unique to the charging source, and according to this indication, the computer system performs personalization and / or customization steps for the charging source, and displays a customized version of the corresponding customizable user interface based on the charging source's unique identifier. In some embodiments, the payload of the transmitter identification packet carried by one or more power transmission signals includes an indication that the corresponding identifier carried in the transmitter identification packet's payload is not unique to the charging source, and according to this indication, the computer system does not perform personalization and / or customization steps for the charging source, and displays a generic or default version of the corresponding customizable user interface, and does not record personalization and / or customization performed by the user when the charging source is coupled to the computer system. In some implementations, the computer system performs automatic personalization and / or customization steps (e.g., storing unique identifiers, comparing unique identifiers, and storing personalization parameters associated with the unique identifiers). These automatic personalization and / or customization steps ensure that the display of the next user interface is personalized and / or customized based on a previously recorded state of the user interface, according to a determination that personalization criteria are met. These personalization criteria include requirements (e.g., via in-band power transfer signals or out-of-band communication packets) for a transmitter identity packet received from the charging source, including an indicator that the identifier carried in the transmitter identity packet is unique to the charging source in order to meet the personalization criteria. For example, as referenced... Figure 5ARAs described in step 50006, in some embodiments, the corresponding personalization information is specific to (e.g., bound to and / or otherwise corresponds to) a corresponding unique identifier (hereinafter referred to as "unique ID"). This allows, for example, a PRx to identify a specific neighboring PTx and display a customized user interface corresponding to that specific PTx (e.g., the PRx displays a first customized user interface when it is adjacent to a first PTx, and displays a second customized user interface different from the first customized user interface when it is adjacent to a second PTx different from the first PTx). In some embodiments, an indication based on determining the payload of the data packet is set to a non-zero value (e.g., "1" or another positive integer value) (e.g., Figure 5AQ Indicators in B5b7 Figure 5AS Manufacturer-reserved portions of B6b2-B8 in the series or Figure 5AT (B0b0 in the computer system) Figure 5AQ , Figure 5AS and / or Figure 5AT The transmitter identification data packet shown includes a unique identifier for the charging source and should be used for personalization / customization.

[0320] In some embodiments, the operation includes displaying a corresponding customizable user interface that was not displayed prior to the detection of the first event, including: abandoning the display of a first customizable user interface (and abandoning the display of a second customizable user interface) based on determining that no identification data representing the identity of the charging source was obtained from the power transmission signal received from the charging source, and displaying a third customizable user interface that is different from the first customizable user interface (and different from the second customizable user interface), wherein the third customizable user interface is configured according to a set of default customization parameters that are different from the first set of customization parameters (and different from the second set of customization parameters) (e.g., displaying a user interface with content, appearance, and / or behavior customized based on general customization parameters corresponding to the general identity of the charging source). In some embodiments, the computer system is coupled to a charging source that does not embed its identity data in its power transmission signal, and the computer system cannot obtain the identity data of the charging source from the power transmission signal of the charging source. In some embodiments, the computer system is coupled to a charging source that embeds its identity data in its power transmission signal in a different manner that is undecipherable by the computer system, and the computer system cannot obtain the identity data of the charging source from the power transmission signal of the charging source. For example, as referenced Figure 5AR As described in step 50014, in some implementations, if PRx does not receive a unique ID from PTx (e.g., PTx does not have a unique ID and / or is not configured to send a unique ID to PRx), then PRx abandons displaying the first customizable user interface and instead displays a default user interface that optionally includes a set of default (e.g., custom) parameters and is different from the first customizable user interface.

[0321] In some implementations, operation includes displaying a corresponding customizable user interface that was not displayed prior to the detection of the first event, including: determining that one or more power transmission signals include a first indication (e.g., Figure 5AQ Indicators in the payload, such as a single leading bit in the payload that includes the corresponding identifier, or another portion of the payload that includes the corresponding identifier. Figure 5AS The manufacturer-reserved portion of the payload (e.g., B6b2-B8), or Figure 5AT The first indication indicates that the corresponding identifier of the charging source embedded in one or more power transmission signals is a unique identifier of the charging source, displaying a corresponding customizable user interface based on the unique identifier (e.g., a fourth customizable user interface for a first customizable user interface or a second customizable user interface, depending on whether the unique identifier corresponds to a first identity or a second identity stored in the computer system); and based on determining that one or more power transmission signals include a second indication (e.g., ... Figure 5AQ Indicators in the payload, such as a single leading bit in the payload including the corresponding identifier, Figure 5AS The second indication indicates that the corresponding identifier of the charging source embedded in one or more power transmission signals is not unique for the charging source, and that there is no corresponding customizable user interface based on the corresponding identifier (e.g., a reserved field of the manufacturer (MFG), a reserved portion of the payload (e.g., B0b0), or another portion of the payload including the corresponding identifier). In some embodiments, the payload of the transmitter identification group carried by one or more power transmission signals includes an indication that the corresponding identifier carried in the payload is not unique for the charging source, and according to this indication, the computer system does not perform personalization and / or customization steps for the charging source, and displays a generic or default version of the corresponding customizable user interface, and does not record personalization and / or customization performed by the user when the charging source is coupled to the computer system. In some implementations, the computer system performs automatic personalization and / or customization steps (e.g., storing unique identifiers, comparing unique identifiers, and storing personalization parameters associated with the unique identifiers). These automatic personalization and / or customization steps ensure that the display of the next user interface is personalized and / or customized based on a previously recorded state of the user interface, according to a determination that personalization criteria are met. These personalization criteria include requirements (e.g., via in-band power transfer signals or out-of-band communication packets) for a transmitter identity packet received from the charging source, including an indicator that the identifier carried in the transmitter identity packet is unique to the charging source in order to meet the personalization criteria. For example, as referenced... Figure 5AQ As described, the data packet includes a payload portion that includes an indicator (bit b7 of byte B5) that indicates whether the payload portion includes a unique ID (e.g., a unique identifier for PTx 5174, as referenced above). Figure 5AO to 5AP (As described). For example, Figure 5AS Data grouping is exemplified as a payload portion including a manufacturer (mfg) reserved portion (starting from b2 of bytes 6 to 8), which can be used to carry an indicator indicating whether the payload portion includes a unique ID. For example, Figure 5AT Data groups are exemplified as payloads including a reserved portion, which includes a single-bit indicator at B0b0 that can be used to carry an indicator of whether the payload portion includes a unique ID. (See also: Regarding...) Figure 5AR As described in step 50014, in some implementations, if PRx does not receive a unique ID from PTx (e.g., PTx does not have an ID, PTx only has a non-unique ID, and / or is not configured to send a unique ID to PRx), then PRx abandons displaying the first customizable user interface.

[0322] In some implementations, the first standard requires a charging source to be coupled to the computer system, enabling the computer system's battery to be charged by the charging source (e.g., by receiving a power transfer signal from the charging source), and the computer system to be in a first orientation to meet the first standard. In some implementations, the corresponding customizable user interface is selected from the example user interfaces described herein (e.g., Figures 5A to 5AM , Figures 6A to 6AN , Figures 7A to 7V , Figures 8A to 8K , Figures 9A to 9AA and Figures 15A to 15Q The user interface shown, and Figures 10A to 10L , Figures 11A to 11G , Figures 12A to 12D , Figures 13A to 13J , Figures 14A to 14G and Figures 16A to 16F The user interface described herein is a set or all of the user interfaces displayed in response to detection of a first criterion being met, wherein the selected user interface is configured according to custom parameters stored in association with the stored identity of the charging source, the stored identity being matched with the identity decoded from the power transfer signal received from the charging source currently coupled to the computer system. For example, as referenced Figure 5AR As described in step 50014, in some implementations, a custom user interface is displayed only when the PRx and / or PTx meet a specific standard (e.g., a first standard). This also... Figure 5G (For example, where the computer system is not being charged by the charging source but is in a first orientation) and Figure 5I(For example, where the computer system is being charged by a...

Claims

1. A computer system, the computer system comprising: Display generated components; One or more sensors, the one or more sensors being used to detect user input; A wireless power transmission coil adapted to wirelessly receive power transmission signals from a charging source; A rectifier adapted to charge the computer system's battery using the power transmission signal received from the charging source by the wireless power transmission coil; and A communication circuit adapted to obtain identification data representing the corresponding identity of the charging source from at least one of the power transmission signals wirelessly received from the charging source. One or more processors, the one or more processors being configured to perform operations including the following: Detect the first event; as well as Based on the detection of the first event: Based on the determination that a first criterion is met as a result of the first event, a corresponding customizable user interface that was not displayed before the first event was detected is displayed. The display of the corresponding customizable user interface includes, based on determining one or more power transmission signals wirelessly received from the charging source, including first identification data representing a first identity of the charging source, and displaying a first customizable user interface corresponding to the first identity of the charging source.

2. The computer system of claim 1, wherein the corresponding customizable user interface, which was not displayed prior to the detection of the first event, comprises: Based on the determination that one or more power transmission signals received from the charging source include second identification data representing a second identity different from the first identity of the charging source, a second customizable user interface corresponding to the second identity of the charging source is displayed.

3. The computer system of claim 1, wherein the corresponding customizable user interface, which was not displayed before the first event was detected, comprises: If it is determined that no identification data representing the identity of the charging source is obtained from the power transmission signal wirelessly received from the charging source, the first customizable user interface is abandoned, and a third user interface different from the first customizable user interface is displayed, wherein the third user interface is configured according to a set of default parameters.

4. The computer system of claim 1, wherein the corresponding customizable user interface, which was not displayed before the first event was detected, comprises: Based on the determination that the one or more power transmission signals include a first indication, the first indication indicating that a corresponding identifier of the charging source embedded in the one or more power transmission signals is a unique identifier of the charging source, a corresponding customizable user interface with a customization based on the unique identifier is displayed; as well as If the determination of the one or more power transmission signals includes a second indication, the second indication indicating that the corresponding identifier of the charging source embedded in the one or more power transmission signals is not unique for the charging source, then no corresponding customizable user interface is displayed based on the corresponding identifier.

5. The method according to any one of claims 1 to 4, wherein the first criterion requires the charging source to be coupled to the computer system such that the battery of the computer system can be charged by the charging source, and the computer system is in a first orientation to satisfy the first criterion.

6. The computer system according to any one of claims 1 to 4: The communication circuit is adapted to decode, from at least one of the one or more power transmission signals received from the charging source, the first identification data representing the first identity of the charging source.

7. The computer system according to any one of claims 1 to 4, wherein: The communication circuit is adapted to decode first identification data representing the first identity of the charging source from data signals other than the one or more power transmission signals wirelessly received from the charging source, wherein the data signals are not used to power the computer system.

8. The computer system of claim 7, wherein the wireless power transmission coil is adapted to wirelessly receive, from the charging source, the one or more power transmission signals including the first identity data of the charging source during a period when the charging source is not charging the battery of the computer system.

9. The computer system according to any one of claims 1 to 4, wherein: The communication circuit is adapted to decode the first identification data from the one or more power transmission signals using a frequency shift keying decoder.

10. The computer system according to any one of claims 1 to 4, wherein the communication circuit is adapted to: Before the wireless power transmission coil receives the one or more power transmission signals, a request for identification data is sent to the charging source, wherein, in response to receiving the request from the communication circuit, the first identification data is transmitted by the charging source to the computer system in the one or more power transmission signals.

11. The computer system according to claim 10, wherein: The communication circuit is adapted to use an amplitude shift keying encoder to encode the request for identification data in the corresponding power transmission signal.

12. The computer system according to any one of claims 1 to 4, wherein the communication circuit is adapted to decode the one or more power transmission signals carrying a payload, wherein the payload encodes an identifier of the charging source.

13. The computer system of claim 12, wherein the communication circuitry is adapted to decode the payload, wherein the payload includes a first portion of an indicator encoded, the indicator specifying whether a second portion of the payload following the first portion includes a corresponding identifier uniquely corresponding to a corresponding charging source.

14. The computer system of claim 13, wherein the length of the first portion of the payload is a single bit and the length of the second portion of the payload is 20 bits.

15. The computer system of claim 12, wherein the communication circuitry is adapted to decode the one or more power transmission signals carrying a header prior to the payload, and the header indicates whether the one or more power transmission signals include a data packet identifying a charging source.

16. The computer system according to any one of claims 1 to 4, wherein the one or more processors are further configured to perform operations including: When the corresponding customizable user interface is displayed, detect one or more user inputs that configure a set of corresponding custom parameters for the corresponding customizable user interface; and Based on the determination that the power transmission signal includes a corresponding identifier of the charging source that uniquely corresponds to the charging source, the set of corresponding customized parameters configured by the one or more users are stored in association with the corresponding identifier of the charging source.

17. The computer system of claim 16, wherein the one or more processors are further configured to perform operations including: After storing the set of corresponding custom parameters configured by the one or more user inputs in association with the corresponding identifier of the charging source, the computer system is detected to be decoupled from the charging source and the display of the corresponding customizable user interface configured with the set of corresponding custom parameters according to the one or more user inputs is stopped; After detecting that the computer system is decoupled from the charging source and stopping the display of the corresponding customizable user interface configured with the corresponding set of corresponding custom parameters according to the one or more user inputs, a subsequent event is detected, wherein the first criterion is satisfied as a result of the subsequent event. as well as In response to the detection of the subsequent event, the corresponding customizable user interface is redisplayed based on the set of corresponding custom parameters stored in association with the corresponding identifier of the charging source, according to the determination that the computer system is coupled to the corresponding charging source and the identifier encoded in one or more power transmission signals received from the corresponding charging source is matched with the corresponding identifier.

18. A method, the method comprising: At a computer system communicating with a display generation component and one or more sensors for detecting user input, the computer system further includes a wireless power transmission coil adapted to wirelessly receive power transmission signals from a charging source, a rectifier adapted to charge the computer system's battery using the power transmission signals received from the charging source by the wireless power transmission coil, and communication circuitry adapted to obtain identification data representing a corresponding identity of the charging source from at least one of the power transmission signals wirelessly received from the charging source. Detecting the first event; and Based on the detection of the first event: Based on the determination that a first criterion is met as a result of the first event, a corresponding customizable user interface that was not displayed before the first event was detected is displayed. The display of the corresponding customizable user interface includes, based on determining one or more power transmission signals wirelessly received from the charging source, including first identification data representing a first identity of the charging source, and displaying a first customizable user interface corresponding to the first identity of the charging source.

19. A method corresponding to an operation performed by a computer system according to any one of claims 2 to 17.

20. A computer-readable storage medium storing one or more programs, the one or more programs comprising instructions that, when executed by a computer system in communication with a display generation component and one or more sensors for detecting user input, cause the computer system to perform operations including, wherein, The computer system further includes a wireless power transmission coil adapted to wirelessly receive power transmission signals from a charging source, a rectifier adapted to charge the computer system's battery using the power transmission signals received from the charging source by the wireless power transmission coil, and a communication circuit adapted to obtain identification data representing a corresponding identity of the charging source from at least one of the power transmission signals wirelessly received from the charging source. Detect the first event; as well as Based on the detection of the first event: Based on the determination that a first criterion is met as a result of the first event, a corresponding customizable user interface that was not displayed before the first event was detected is displayed. The display of the corresponding customizable user interface includes, based on determining one or more power transmission signals wirelessly received from the charging source, including first identification data representing a first identity of the charging source, and displaying a first customizable user interface corresponding to the first identity of the charging source.

21. A computer-readable storage medium storing one or more programs, the one or more programs comprising instructions executable by a computer system according to any one of claims 2 to 17.

Images