CN119365933A

CN119365933A - Systems and methods for sleep tracking

Info

Publication number: CN119365933A
Application number: CN202380044845.8A
Authority: CN
Inventors: N·D·费尔顿; K·B·梅利曼; C·S·托马斯; S·G·托马斯
Original assignee: Apple Inc
Current assignee: Apple Inc
Priority date: 2022-06-03
Filing date: 2023-06-02
Publication date: 2025-01-24
Also published as: WO2023235608A1; EP4515573A1; WO2023235608A9

Abstract

The present disclosure as a whole relates to sleep tracking. An example method includes: receiving sleep data corresponding to a sleep period, the sleep data including first data corresponding to a first sub-period of the sleep period; and displaying a sleep representation that classifies the sleep period into sleep stages based on the sleep data, wherein displaying the sleep representation includes displaying a first indication corresponding to the first sub-period, wherein the first indication: indicates that the first sub-period is a first type of sleep period corresponding to the first sleep stage based on determining that the first data corresponds exclusively to the first sleep stage; and indicates that the first sub-period corresponds to at least a second sleep stage and a third sleep stage different from the second sleep stage based on determining that the first data does not exclusively correspond to a single sleep stage.

Description

System and method for sleep tracking

Cross Reference to Related Applications

The present application claims priority from U.S. provisional patent application No. 63/348,727 entitled "SYSTEMS AND METHOD FOR SLEEP TRACKING" filed on month 3 of 2022 and U.S. patent application No. 18/204,905 entitled "SYSTEMS AND METHOD FOR SLEEP TRACKING" filed on month 1 of 2023. The contents of each of these patent applications are incorporated herein by reference in their entirety.

Technical Field

The present disclosure relates generally to computer user interfaces, and more particularly to techniques for sleep tracking.

Background

For example, one or more sensors may be used to track user sleep behavior. For example, data generated by the sensors may be used to generate a sleep structure map indicating various sleep stages of a user sleeping over a period of time.

Disclosure of Invention

However, some techniques for tracking sleep behavior using electronic devices are often cumbersome and inefficient. For example, some prior art techniques use complex and time consuming user interfaces that may include multiple key presses or keystrokes. The prior art requires more time than is necessary, which results in wasted user time and device energy. This latter consideration is particularly important in battery-powered devices.

Thus, the present technology provides faster, more efficient methods and interfaces for sleep tracking for electronic devices. Such methods and interfaces optionally supplement or replace other methods for sleep tracking. Such methods and interfaces reduce the cognitive burden on the user and create a more efficient human-machine interface. For battery-powered computing devices, such methods and interfaces conserve power and increase the time interval between battery charges.

An exemplary method is described herein. An example method includes receiving sleep data corresponding to a sleep period from one or more input devices, wherein the sleep data includes first data corresponding to a first sub-period of the sleep period, and based on the sleep data, displaying, via a display generation component, a sleep representation classifying the sleep period into a plurality of sleep stages, wherein displaying the sleep representation includes displaying a first indication corresponding to the first sub-period of the sleep period, wherein the first indication indicates that the first sub-period is a first type of sleep period corresponding to the first sleep stage in accordance with a determination that the first data exclusively corresponds to the first sleep stage of the plurality of sleep stages, and indicates that the first sub-period corresponds to at least a second sleep stage of the plurality of sleep stages and a third sleep stage different from the second sleep stage in accordance with a determination that the first data does not exclusively correspond to a single sleep stage of the plurality of sleep stages.

Example non-transitory computer-readable storage media are described herein. An example non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system in communication with a display generation component and one or more input devices and includes instructions for receiving sleep data corresponding to a sleep period from the one or more input devices, wherein the sleep data includes first data corresponding to a first subperiod of the sleep period, and displaying, via the display generation component, a sleep representation classifying the sleep period into a plurality of sleep stages based on the sleep data, wherein displaying the sleep representation includes displaying a first indication corresponding to the first subperiod of the sleep period, wherein the first indication indicates that the first subperiod is a first type of sleep period corresponding to the first sleep stage in accordance with a determination that the first data does not exclusively correspond to a single sleep stage of the plurality of sleep stages, and indicates that the first subperiod corresponds to at least a second sleep stage of the plurality of sleep stages and a third sleep stage different from the third sleep stage.

Example transitory computer-readable storage media are described herein. An example non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system in communication with a display generation component and one or more input devices and includes instructions for receiving sleep data corresponding to a sleep period from the one or more input devices, wherein the sleep data includes first data corresponding to a first subperiod of the sleep period, and displaying, via the display generation component, a sleep representation classifying the sleep period into a plurality of sleep stages based on the sleep data, wherein displaying the sleep representation includes displaying a first indication corresponding to the first subperiod of the sleep period, wherein the first indication indicates that the first subperiod is a first type of sleep period corresponding to the first sleep stage in accordance with a determination that the first data does not exclusively correspond to a single sleep stage of the plurality of sleep stages, and indicates that the first subperiod corresponds to at least a second sleep stage of the plurality of sleep stages and a third sleep stage different from the third sleep stage.

An exemplary computer system is described herein. An example computer system is configured to communicate with a display generation component and one or more input devices and includes one or more processors and a memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for receiving sleep data corresponding to a sleep period from the one or more input devices, wherein the sleep data includes first data corresponding to a first sub-period of the sleep period, and based on the sleep data, displaying a sleep representation classifying the sleep period into a plurality of sleep periods via the display generation component, wherein displaying the sleep representation includes displaying a first indication corresponding to the first sub-period of the sleep period, wherein the first indication indicates that the first sub-period is a first type of sleep corresponding to the first sleep period in accordance with a determination that the first data exclusively corresponds to the first sleep period, and indicating that the first sub-period is different from at least a second sub-period of the sleep period and the second sleep period of the sleep period in accordance with a determination that the first data does not exclusively correspond to a single sleep period of the plurality of sleep periods.

An example computer system is configured to communicate with a display generating component and one or more input devices and includes means for receiving sleep data corresponding to a sleep period from the one or more input devices, wherein the sleep data includes first data corresponding to a first sub-period of the sleep period, and means for displaying a sleep representation classifying the sleep period into a plurality of sleep stages via the display generating component based on the sleep data, wherein displaying the sleep representation includes displaying a first indication corresponding to the first sub-period of the sleep period, wherein the first indication indicates that the first sub-period is a first type of sleep period corresponding to the first sleep stage in accordance with a determination that the first data exclusively corresponds to the first sleep stage of the plurality of sleep stages, and indicates that the first sub-period corresponds to at least a second sleep stage of the plurality of sleep stages and a third sleep stage different from the second sleep stage in accordance with a determination that the first data does not exclusively correspond to a single sleep stage of the plurality of sleep stages.

An exemplary computer program product is described herein. An example computer program product includes one or more programs configured to be executed by one or more processors of a computer system in communication with a display generation component and one or more input devices, the one or more programs including instructions for receiving sleep data corresponding to a sleep period from the one or more input devices, wherein the sleep data includes first data corresponding to a first sub-period of the sleep period, and displaying, via the display generation component, a sleep representation classifying the sleep period into a plurality of sleep stages based on the sleep data, wherein displaying the sleep representation includes displaying a first indication corresponding to the first sub-period of the sleep period, wherein the first indication indicates that the first sub-period is a first type of sleep period corresponding to the first sleep stage in accordance with a determination that the first data corresponds exclusively to a first sleep stage of the plurality of sleep stages, and indicating that the first sub-period corresponds to at least a second sleep stage of the plurality of sleep stages and a second sleep stage different from the third sleep stage in accordance with a determination that the first data does not correspond exclusively to a single sleep stage of the plurality of sleep stages.

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

Thus, faster, more efficient methods and interfaces for sleep tracking are provided for devices, thereby improving the effectiveness, efficiency, and user satisfaction of such devices. Such methods and interfaces may supplement or replace other methods for sleep tracking.

Drawings

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

FIG. 1A is a block diagram illustrating a portable multifunction device with a touch-sensitive display in accordance with some embodiments.

FIG. 1B is a block diagram illustrating exemplary components for event processing according to some embodiments.

Fig. 2 illustrates a portable multifunction device with a touch screen in accordance with some embodiments.

FIG. 3 is a block diagram of an exemplary multifunction device with a display and a touch-sensitive surface in accordance with some embodiments.

Fig. 4A illustrates an exemplary user interface for a menu of an application on a portable multifunction device in accordance with some embodiments.

Fig. 4B illustrates an exemplary user interface for a multifunction device with a touch-sensitive surface separate from a display in accordance with some embodiments.

Fig. 5A illustrates a personal electronic device in accordance with some embodiments.

Fig. 5B is a block diagram illustrating a personal electronic device in accordance with some embodiments.

Fig. 6A-6K illustrate exemplary user interfaces for tracking sleep behavior according to some embodiments.

Fig. 7 illustrates a flow chart of a process for tracking sleep behavior according to some embodiments.

Detailed Description

The following description sets forth exemplary methods, parameters, and the like. However, it should be recognized that such description is not intended as a limitation on the scope of the present disclosure, but is instead provided as a description of exemplary embodiments.

Electronic devices are needed to provide more efficient methods and interfaces for tracking sleep behavior. Such techniques may reduce the cognitive burden of a user to view one or more user interfaces corresponding to tracked sleep behavior, thereby improving productivity. Further, such techniques may reduce processor power and battery power that would otherwise be wasted on redundant user inputs.

1A-1B, 2, 3, 4A-4B, and 5A-5B provide a description of an exemplary device for performing techniques for managing event notifications. Fig. 6A-6K illustrate exemplary user interfaces for tracking sleep behavior. Fig. 7 is a flow chart illustrating a method for tracking sleep behavior according to some embodiments. The user interfaces in fig. 6A to 6K are used to illustrate a process including the process in fig. 7 described below.

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

Furthermore, in a method described herein in which one or more steps are dependent on one or more conditions having been met, it should be understood that the method may be repeated in multiple iterations such that during the iteration, all conditions that determine steps in the method have been met in different iterations of the method. For example, if a method requires performing a first step (if a condition is met) and performing a second step (if a condition is not met), one of ordinary skill will know that the stated steps are repeated until both the condition and the condition are not met (not sequentially). Thus, a method described as having one or more steps depending on one or more conditions having been met may be rewritten as a method that repeats until each of the conditions described in the method have been met. However, this does not require the system or computer-readable medium to claim that the system or computer-readable medium contains instructions for performing the contingent operation based on the satisfaction of the corresponding condition or conditions, and thus is able to determine whether the contingent situation has been met without explicitly repeating the steps of the method until all conditions to decide on steps in the method have been met. It will also be appreciated by those of ordinary skill in the art that, similar to a method with optional steps, a system or computer readable storage medium may repeat the steps of the method as many times as necessary to ensure that all optional steps have been performed.

Although the following description uses the terms "first," "second," etc. to describe various elements, these elements should not be limited by the terms. In some embodiments, these terms are used to distinguish one element from another element. For example, a first touch may be named a second touch and similarly a second touch may be named a first touch without departing from the scope of the various described embodiments. In some embodiments, the first touch and the second touch are two separate references to the same touch. In some implementations, both the first touch and the second touch are touches, but they are not the same touch.

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 in the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will also be understood that the term "and/or" as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items. It will be further understood that the terms "comprises" and/or "comprising," when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.

The term "if" is optionally interpreted to mean "when..once", "at..once..once.," or "in response to a determination" or "in response to detection", depending on the context. Similarly, the phrase "if determined" or "if detected [ stated condition or event ]" is optionally interpreted to mean "upon determination" or "in response to determination" or "upon detection of [ stated condition or event ]" or "in response to detection of [ stated condition or event ]" depending on the context.

Embodiments of electronic devices, user interfaces for such devices, and associated processes for using such devices are described herein. In some embodiments, the device is a portable communication device, such as a mobile phone, that also includes other functions, such as PDA and/or music player functions. Exemplary embodiments of the portable multifunction device include, but are not limited to, those from Apple inc (Cupertino, california)Equipment, iPodApparatus and method for controlling the operation of a deviceAn apparatus. Other portable electronic devices, such as a laptop or tablet computer having a touch-sensitive surface (e.g., a touch screen display and/or a touchpad), may alternatively be used. It should also be appreciated that in some embodiments, the device is not a portable communication device, but rather a desktop computer having a touch-sensitive surface (e.g., a touch screen display and/or a touch pad). In some embodiments, the electronic device is a computer system in communication (e.g., via wireless communication, via wired communication) with the display generation component. The display generation component is configured to provide visual output, such as display via a CRT display, display via an LED display, or display via image projection. In some embodiments, the display generation component is integrated with the computer system. In some embodiments, the display generation component is separate from the computer system. As used herein, "displaying" content includes displaying content (e.g., video data rendered or decoded by display controller 156) by transmitting data (e.g., image data or video data) to an integrated or external display generation component via a wired or wireless connection to visually produce the content.

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

The device typically supports various applications such as one or more of a drawing application, a presentation application, a word processing application, a website creation application, a disk editing application, a spreadsheet application, a gaming application, a telephone application, a video conferencing application, an email application, an instant messaging application, a fitness support application, a photograph management application, a digital camera application, a digital video camera application, a web browsing application, a digital music player application, and/or a digital video player application.

The various applications executing on the device optionally use at least one generic physical user interface device, such as a touch-sensitive surface. One or more functions of the touch-sensitive surface and corresponding information displayed on the device may optionally be adjusted and/or changed for different applications and/or within the respective applications. In this way, the common physical architecture of the devices (such as the touch-sensitive surface) optionally supports various applications with a user interface that is intuitive and transparent to the user.

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

As used in this specification and the claims, the term "intensity" of a contact on a touch-sensitive surface refers to the force or pressure (force per unit area) of the contact on the touch-sensitive surface (e.g., finger contact), or to an alternative to the force or pressure of the contact on the touch-sensitive surface (surrogate). The intensity of the contact has a range of values that includes at least four different values and more typically includes hundreds of different values (e.g., at least 256). The intensity of the contact is optionally determined (or measured) using various methods and various sensors or combinations of sensors. For example, one or more force sensors below or adjacent to the touch-sensitive surface may optionally be used to measure forces at different points on the touch-sensitive surface. In some implementations, force measurements from multiple force sensors are combined (e.g., weighted average) to determine an estimated contact force. Similarly, the pressure sensitive tip of the stylus is optionally used to determine the pressure of the stylus on the touch sensitive surface. Alternatively, the size of the contact area and/or its variation detected on the touch-sensitive surface, the capacitance of the touch-sensitive surface and/or its variation in the vicinity of the contact and/or the resistance of the touch-sensitive surface and/or its variation in the vicinity of the contact may optionally be used as a substitute for the force or pressure of the contact on the touch-sensitive surface. In some implementations, surrogate measurements of contact force or pressure are directly used to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is described in units corresponding to surrogate measurements). In some implementations, surrogate measurements of contact force or pressure are converted to an estimated force or pressure, and the estimated force or pressure is used to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is a pressure threshold measured in units of pressure). The intensity of the contact is used as an attribute of the user input, allowing the user to access additional device functions that are not otherwise accessible to the user on a smaller sized device of limited real estate for displaying affordances and/or receiving user input (e.g., via a touch-sensitive display, touch-sensitive surface, or physical/mechanical control, such as a knob or button).

As used in this specification and in the claims, the term "haptic output" refers to a previously positioned physical displacement of a device relative to the device, a physical displacement of a component of the device (e.g., a touch-sensitive surface) relative to another component of the device (e.g., a housing), or a displacement of a component relative to the centroid of the device, to be detected by a user with the user's feel. For example, in the case where the device or component of the device is in contact with a touch-sensitive surface of the user (e.g., a finger, palm, or other portion of the user's hand), the haptic output generated by the physical displacement will be interpreted by the user as a haptic sensation corresponding to a perceived change in a physical characteristic of the device or component of the device. For example, movement of a touch-sensitive surface (e.g., a touch-sensitive display or touch pad) is optionally interpreted by a user as a "press click" or "click-down" of a physically actuated button. In some cases, the user will feel a tactile sensation, such as "press click" or "click down", even when the physical actuation button associated with the touch-sensitive surface that is physically pressed (e.g., displaced) by the user's movement is not moved. As another example, movement of the touch-sensitive surface may be optionally interpreted or sensed by a user as "roughness" of the touch-sensitive surface, even when the smoothness of the touch-sensitive surface is unchanged. While such interpretation of touches by a user will be limited by the user's individualized sensory perception, many sensory perceptions of touches are common to most users. Thus, when a haptic output is described as corresponding to a particular sensory perception of a user (e.g., "click down," "click up," "roughness"), unless stated otherwise, the haptic output generated corresponds to a physical displacement of the device or component thereof that would generate that sensory perception of a typical (or ordinary) user.

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

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

Peripheral interface 118 may be used to couple input and output peripherals of the device to CPU 120 and memory 102. The one or more processors 120 run or execute various software programs, such as computer programs (e.g., including instructions), and/or sets of instructions stored in the memory 102 to perform various functions of the device 100 and process data. In some embodiments, peripheral interface 118, CPU 120, and memory controller 122 are optionally implemented on a single chip, such as chip 104. In some other embodiments, they are optionally implemented on separate chips.

The RF (radio frequency) circuit 108 receives and transmits RF signals, also referred to as electromagnetic signals. RF circuitry 108 converts/converts electrical signals to/from electromagnetic signals and communicates with communication networks and other communication devices via electromagnetic signals. RF circuitry 108 optionally includes well known circuitry for performing these functions including, but not limited to, an antenna system, an RF transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a codec chipset, a Subscriber Identity Module (SIM) card, memory, and so forth. RF circuitry 108 may optionally communicate 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 via wireless communications. The RF circuitry 108 optionally includes well-known circuitry for detecting a Near Field Communication (NFC) field, such as by a short-range communication radio. Wireless communications may optionally use any of a variety of communication standards, protocols, and technologies including, but not limited to, global system for mobile communications (GSM), enhanced Data GSM Environment (EDGE), high Speed Downlink Packet Access (HSDPA), high Speed Uplink Packet Access (HSUPA), evolution, pure data (EV-DO), HSPA, hspa+, dual element HSPA (DC-HSPDA), long Term Evolution (LTE), near Field Communications (NFC), wideband code division multiple access (W-CDMA), code Division Multiple Access (CDMA), time Division Multiple Access (TDMA), bluetooth low energy (BTLE), wireless fidelity (Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11n, and/or IEEE 802.11 ac), voice over internet protocol (VoIP), wi-MAX, email protocols (e.g., internet Message Access Protocol (IMAP) and/or post protocol (POP)), messages (e.g., extensible messaging and presence protocol (XMPP), protocols for instant messaging and presence with extended session initiation (sime), messages and presence (pls), and/or other communication protocols not yet being properly addressed or at any other date.

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 to electrical signals, and transmits the electrical signals to speaker 111. The speaker 111 converts electrical signals into sound waves that are audible to humans. The audio circuit 110 also receives electrical signals converted from sound waves by the microphone 113. The audio circuitry 110 converts the electrical signals into audio data and transmits the audio data to the peripheral interface 118 for processing. The audio data is optionally retrieved from and/or transmitted to the memory 102 and/or the RF circuitry 108 by the peripheral interface 118. In some embodiments, the audio circuit 110 also includes a headset jack (e.g., 212 in fig. 2). The headset jack provides an interface between the audio circuit 110 and removable audio input/output peripherals such as output-only headphones or a headset having both an output (e.g., a monaural or binaural) and an input (e.g., a microphone).

I/O subsystem 106 couples input/output peripheral devices on device 100, such as touch screen 112 and other input control devices 116, to peripheral interface 118. The I/O subsystem 106 optionally includes a display controller 156, an optical sensor controller 158, a depth camera controller 169, an intensity sensor controller 159, a haptic feedback controller 161, and one or more input controllers 160 for other input or control devices. The one or more input controllers 160 receive electrical signals from/transmit electrical signals to other input control devices 116. The other input control devices 116 optionally include physical buttons (e.g., push buttons, rocker buttons, etc.), dials, slider switches, joysticks, click wheels, and the like. In some implementations, the input controller 160 is optionally coupled to (or not coupled to) any of a keyboard, an infrared port, a USB port, and a pointing device such as a mouse. One or more of the buttons (e.g., 208 in fig. 2) optionally includes an up/down button for volume control of the speaker 111 and/or microphone 113. The one or more buttons optionally include a push button (e.g., 206 in fig. 2). In some embodiments, the electronic device is a computer system that communicates (e.g., via wireless communication, via wired communication) with one or more input devices. In some implementations, the one or more input devices include a touch-sensitive surface (e.g., a touch pad as part of a touch-sensitive display). In some implementations, the one or more input devices include one or more camera sensors (e.g., one or more optical sensors 164 and/or one or more depth camera sensors 175) such as for tracking gestures (e.g., hand gestures and/or air gestures) of the user as input. In some embodiments, one or more input devices are integrated with the computer system. In some embodiments, one or more input devices are separate from the computer system. In some embodiments, the air gesture is a gesture that is detected without the user touching an input element that is part of the device (or independent of an input element that is part of the device) and based on a detected movement of a portion of the user's body through the air, including a movement of the user's body relative to an absolute reference (e.g., an angle of the user's arm relative to the ground or a distance of the user's hand relative to the ground), a movement relative to another portion of the user's body (e.g., a movement of the user's hand relative to the user's shoulder, a movement of the user's hand relative to the other hand of the user, and/or a movement of the user's finger relative to the other finger or part of the hand of the user), and/or an absolute movement of a portion of the user's body (e.g., a flick gesture that includes the hand moving a predetermined amount and/or speed in a predetermined gesture that includes a predetermined gesture of speed or a shake of a predetermined amount of rotation of a portion of the user's body).

The quick press of the push button optionally disengages the lock of touch screen 112 or optionally initiates the process of unlocking the device using gestures on the touch screen, as described in U.S. patent application 11/322,549 (i.e., U.S. patent No. 7,657,849) entitled "Unlocking a Device by Performing Gestures on an Unlock Image," filed on even date 23, 12, 2005, which is hereby incorporated by reference in its entirety. A long press of the button (e.g., 206) optionally causes the device 100 to power on or off. The function of the one or more buttons is optionally customizable by the user. Touch screen 112 is used to implement virtual buttons or soft buttons and one or more soft keyboards.

The touch sensitive display 112 provides an input interface and an output interface between the device and the user. The display controller 156 receives electrical signals from and/or transmits electrical signals to the touch screen 112. Touch screen 112 displays visual output to a user. Visual output optionally includes graphics, text, icons, video, and any combination thereof (collectively, "graphics"). In some embodiments, some or all of the visual output optionally corresponds to a user interface object.

Touch screen 112 has a touch-sensitive surface, sensor or set of sensors that receives input from a user based on haptic and/or tactile contact. Touch screen 112 and display controller 156 (along with any associated modules and/or sets of instructions in memory 102) detect contact (and any movement or interruption of the contact) on touch screen 112 and translate the detected contact into interactions with user interface objects (e.g., one or more soft keys, icons, web pages, or images) displayed on touch screen 112. In an exemplary embodiment, the point of contact between touch screen 112 and the user corresponds to a user's finger.

Touch screen 112 optionally uses LCD (liquid crystal display) technology, LPD (light emitting polymer display) technology, or LED (light emitting diode) technology, but in other embodiments other display technologies are used. Touch screen 112 and display controller 156 optionally detect contact and any movement or interruption thereof using any of a variety of touch sensing technologies now known or later developed, including but not limited to capacitive, resistive, infrared, and surface acoustic wave technologies, as well as other proximity sensor arrays or other elements for determining one or more points of contact with touch screen 112. In an exemplary embodiment, a projected mutual capacitance sensing technique is used, such as that described in the text from Apple inc (Cupertino, california)And iPodTechniques used in the above.

The touch-sensitive display in some embodiments of touch screen 112 may optionally be similar to the multi-touch-sensitive touch pad described in U.S. Pat. No. 6,323,846 (Westerman et al), 6,570,557 (Westerman et al), and/or 6,677,932 (Westerman et al) and/or U.S. patent publication 2002/0015024A1, each of which is hereby incorporated by reference in its entirety. However, touch screen 112 displays visual output from device 100, while touch sensitive touchpads do not provide visual output.

Touch-sensitive displays in some embodiments of touch screen 112 are described in (1) U.S. patent application Ser. No. 11/381,313, "Multipoint Touch Surface Controller" filed on month 5 and month 2, (2) U.S. patent application Ser. No. 10/840,862, "Multipoint Touchscreen" filed on month 6 and month 5, (3) U.S. patent application Ser. No. 10/903,964, "Gestures For Touch Sensitive Input Devices" filed on month 7 and month 30, (4) U.S. patent application Ser. No. 11/048,264, "Gestures For Touch Sensitive Input Devices" filed on month 1 and month 31, (5) U.S. patent application Ser. No. 11/038,590, "Mode-Based Graphical User Interfaces For Touch Sensitive Input Devices" filed on month 18 and (6) U.S. patent application Ser. No. 11/228,758, "Virtual Input DEVICE PLACEMENT On A Touch Screen User Interface" filed on month 9 and month 16, and (7) U.S. patent application Ser. No. 11/228,700, "Operation Of A Computer With ATouch SCREEN INTERFACE" filed on month 9 and month 16, and (8) U.S. patent application Ser. No. 11/228,7 "to month 16, and" 3-35 "how" 35-35 ". All of these applications are incorporated by reference herein in their entirety.

Touch screen 112 optionally has a video resolution in excess of 100 dpi. In some implementations, the touch screen has a video resolution of about 160 dpi. The user may optionally use any suitable object or appendage, such as a stylus, finger, or the like, to make contact with touch screen 112. In some embodiments, the user interface is designed to work primarily through finger-based contact and gestures, which may not be as accurate as stylus-based input due to the large contact area of the finger on the touch screen. In some embodiments, the device translates the finger-based coarse input into a precise pointer/cursor location or command for performing the action desired by the user.

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

The apparatus 100 also includes a power system 162 for powering the various components. The power system 162 optionally includes a power management system, one or more power sources (e.g., battery, alternating Current (AC)), a recharging system, a power failure detection circuit, a power converter or inverter, a power status indicator (e.g., light Emitting Diode (LED)), and any other components associated with the generation, management, and distribution of power in the portable device.

The device 100 optionally further comprises one or more optical sensors 164. FIG. 1A shows an optical sensor coupled to an optical sensor controller 158 in the I/O subsystem 106. The optical sensor 164 optionally includes a Charge Coupled Device (CCD) or a Complementary Metal Oxide Semiconductor (CMOS) phototransistor. The optical sensor 164 receives light projected through one or more lenses from the environment and converts the light into data representing an image. In conjunction with an imaging module 143 (also called a camera module), the optical sensor 164 optionally captures still images or video. In some embodiments, the optical sensor is located on the rear of the device 100, opposite the touch screen display 112 on the front of the device, so that the touch screen display can be used as a viewfinder for still image and/or video image acquisition. In some embodiments, the optical sensor is located on the front of the device such that the user's image is optionally acquired for video conferencing as the user views other video conference participants on the touch screen display. In some implementations, the positioning of the optical sensor 164 can be changed by the user (e.g., by rotating the lenses and sensors in the device housing) such that a single optical sensor 164 is used with the touch screen display for both video conferencing and still image and/or video image acquisition.

The device 100 optionally further includes one or more depth camera sensors 175. FIG. 1A shows a depth camera sensor coupled to a depth camera controller 169 in the I/O subsystem 106. The depth camera sensor 175 receives data from the environment to create a three-dimensional model of objects (e.g., faces) within the scene from a point of view (e.g., depth camera sensor). In some implementations, in conjunction with the imaging module 143 (also referred to as a camera module), the depth camera sensor 175 is optionally used to determine a depth map of different portions of the image captured by the imaging module 143. In some embodiments, a depth camera sensor is located at the front of the device 100 such that user images with depth information are optionally acquired for video conferencing while the user views other video conferencing participants on a touch screen display, and self-timer with depth map data is captured. In some embodiments, the depth camera sensor 175 is located at the back of the device, or at the back and front of the device 100. In some implementations, the positioning of the depth camera sensor 175 can be changed by the user (e.g., by rotating lenses and sensors in the device housing) such that the depth camera sensor 175 is used with a touch screen display for both video conferencing and still image and/or video image acquisition.

The device 100 optionally further comprises one or more contact strength sensors 165. FIG. 1A shows a contact intensity sensor coupled to an intensity sensor controller 159 in the I/O subsystem 106. The contact strength sensor 165 optionally includes one or more piezoresistive strain gauges, capacitive force sensors, electrical force sensors, piezoelectric force sensors, optical force sensors, capacitive touch-sensitive surfaces, or other strength sensors (e.g., sensors for measuring force (or pressure) of a contact on a touch-sensitive surface). The contact strength sensor 165 receives contact strength information (e.g., pressure information or a surrogate for pressure information) from the environment. In some implementations, at least one contact intensity sensor is juxtaposed or adjacent to a touch-sensitive surface (e.g., touch-sensitive display system 112). In some embodiments, at least one contact intensity sensor is located on the rear of the device 100, opposite the touch screen display 112 located on the front of the device 100.

The device 100 optionally further includes one or more proximity sensors 166. Fig. 1A shows a proximity sensor 166 coupled to the peripheral interface 118. Alternatively, the proximity sensor 166 is optionally coupled to the input controller 160 in the I/O subsystem 106. The proximity sensor 166 may alternatively perform as described in U.S. patent application Ser. No. 11/241,839, entitled "Proximity Detector IN HANDHELD DEVICE", 11/240,788, entitled "Proximity Detector IN HANDHELD DEVICE", 11/620,702, entitled "Using Ambient Light Sensor To Augment Proximity Sensor Output", 11/586,862, entitled "Automated Response To AND SENSING Of User ACTIVITY IN Portable Devices", and 11/638,251, entitled "Methods AND SYSTEMS For Automatic Configuration Of Peripherals", which are incorporated herein by reference in their entirety. In some embodiments, the proximity sensor is turned off and the touch screen 112 is disabled when the multifunction device is placed near the user's ear (e.g., when the user is making a telephone call).

The device 100 optionally further comprises one or more tactile output generators 167. FIG. 1A shows a haptic output generator coupled to a haptic feedback controller 161 in the I/O subsystem 106. The tactile output generator 167 optionally includes one or more electroacoustic devices such as speakers or other audio components, and/or electromechanical devices for converting energy into linear motion such as motors, solenoids, electroactive polymers, piezoelectric actuators, electrostatic actuators, or other tactile output generating components (e.g., components for converting electrical signals into tactile outputs on a device). The contact intensity sensor 165 receives haptic feedback generation instructions from the haptic feedback module 133 and generates a haptic output on the device 100 that can be perceived by a user of the device 100. In some embodiments, at least one tactile output generator is juxtaposed or adjacent to a touch-sensitive surface (e.g., touch-sensitive display system 112), and optionally generates tactile output by moving the touch-sensitive surface vertically (e.g., inward/outward of the surface of device 100) or laterally (e.g., backward and forward 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 the touch screen display 112 located on the front of the device 100.

The device 100 optionally further includes one or more accelerometers 168. Fig. 1A shows accelerometer 168 coupled to peripheral interface 118. Alternatively, accelerometer 168 is optionally coupled to input controller 160 in I/O subsystem 106. Accelerometer 168 may alternatively perform as described in U.S. patent publication nos. 20050190059, entitled "acceletion-based Theft Detection System for Portable Electronic Devices" and 20060017692, entitled "Methods And Apparatuses For Operating A Portable Device Based On An Accelerometer," both of which are incorporated herein by reference in their entirety. In some implementations, information is displayed in a portrait view or a landscape view on a touch screen display based on analysis of data received from one or more accelerometers. The device 100 optionally includes a magnetometer and a GPS (or GLONASS or other global navigation system) receiver in addition to the accelerometer 168 for obtaining information regarding the position and orientation (e.g., longitudinal or lateral) of the device 100.

In some embodiments, the software components stored in memory 102 include an operating system 126, a communication module (or instruction set) 128, a contact/motion module (or instruction set) 130, a graphics module (or instruction set) 132, a text input module (or instruction set) 134, a Global Positioning System (GPS) module (or instruction set) 135, and an application (or instruction set) 136. Furthermore, in some embodiments, memory 102 (fig. 1A) or 370 (fig. 3) stores device/global internal state 157, as shown in fig. 1A and 3. The device/global internal state 157 includes one or more of an active application state indicating which applications (if any) are currently active, a display state indicating what applications, views, or other information occupy various areas of the touch screen display 112, sensor states including information obtained from various sensors of the device and the input control device 116, and location information relating to the device's location and/or attitude.

Operating system 126 (e.g., darwin, RTXC, LINUX, UNIX, OS X, iOS, 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 control, power management, etc.), and facilitates communication between the various hardware components and software components.

The communication module 128 facilitates communication with other devices through one or more external ports 124 and also includes various software components for processing data received by the RF circuitry 108 and/or the external ports 124. External port 124 (e.g., universal Serial Bus (USB), firewire, etc.) is adapted to be coupled directly to other devices or indirectly via a network (e.g., the internet, wireless LAN, etc.). In some embodiments, the external port is in communication withThe 30-pin connector used on the (Apple inc. Trademark) device is the same or similar and/or compatible with a multi-pin (e.g., 30-pin) connector.

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

In some implementations, the contact/motion module 130 uses a set of one or more intensity thresholds to determine whether an operation has been performed by a user (e.g., to determine whether the user has "clicked" on an icon). In some implementations, at least a subset of the intensity thresholds are determined according to software parameters (e.g., the intensity thresholds are not determined by activation thresholds of particular physical actuators and may be adjusted without changing the physical hardware of the device 100). For example, without changing the touchpad or touch screen display hardware, the mouse "click" threshold of the touchpad or touch screen may be set to any of a wide range of predefined thresholds. Additionally, in some implementations, a user of the device is provided with software settings for adjusting one or more intensity thresholds of a set of intensity thresholds (e.g., by adjusting individual intensity thresholds and/or by adjusting multiple intensity thresholds at once with a system-level click on an "intensity" parameter).

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

Graphics module 132 includes various known software components for rendering and displaying graphics on touch screen 112 or other display, including components for changing the visual impact (e.g., brightness, transparency, saturation, contrast, or other visual attribute) of the displayed graphics. As used herein, the term "graphic" includes any object that may be displayed to a user, including but not limited to text, web pages, icons (such as user interface objects including soft keys), digital images, video, animation, and the like.

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

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

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

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

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

● A contacts module 137 (sometimes referred to as an address book or contact list);

● A telephone module 138;

● A video conference module 139;

● An email client module 140;

● An Instant Messaging (IM) module 141;

● A fitness support module 142;

● A camera module 143 for still and/or video images;

● An image management module 144;

● A video player module;

● A music player module;

● A browser module 147;

● A calendar module 148;

● A gadget module 149 optionally including one or more of a weather gadget 149-1, a stock market gadget 149-2, a calculator gadget 149-3, an alarm gadget 149-4, a dictionary gadget 149-5, and other gadgets acquired by a user, and a user-created gadget 149-6;

● A gadget creator module 150 for forming a user-created gadget 149-6;

● A search module 151;

● A video and music player module 152 that incorporates a video player module and a music player module;

● A note module 153;

● Map module 154, and/or

● An online video module 155.

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

In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, contacts module 137 may optionally be used to manage an address book or list of contacts (e.g., in application internal state 192 of contacts module 137 stored in memory 102 or memory 370), including adding names to the address book, deleting names from the address book, associating telephone numbers, email addresses, physical addresses, or other information with names, associating images with names, categorizing and classifying names, providing telephone numbers or email addresses to initiate and/or facilitate communication through telephone module 138, videoconferencing module 139, email client module 140, or IM module 141, and so forth.

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

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch screen 112, display controller 156, optical sensor 164, optical sensor controller 158, contact/motion module 130, graphics module 132, text input module 134, contacts module 137, and telephony module 138, videoconferencing module 139 includes executable instructions to initiate, conduct, and terminate a videoconference between a user and one or more other participants according to user instructions.

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

In conjunction with the RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, the instant message module 141 includes executable instructions for inputting a sequence of characters corresponding to an instant message, modifying previously entered characters, transmitting the corresponding instant message (e.g., using a Short Message Service (SMS) or Multimedia Message Service (MMS) protocol for phone-based instant messages or using XMPP, SIMPLE, or IMPS for internet-based instant messages), receiving the instant message, and viewing the received instant message. In some embodiments, the transmitted and/or received instant message optionally includes graphics, photographs, audio files, video files, and/or other attachments supported in an MMS and/or Enhanced Messaging Service (EMS). As used herein, "instant message" refers to both telephony-based messages (e.g., messages sent using SMS or MMS) and internet-based messages (e.g., messages sent using XMPP, SIMPLE, or IMPS).

In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, GPS module 135, map module 154, and music player module, workout support module 142 includes executable instructions for creating workouts (e.g., having time, distance, and/or calorie burning goals), communicating with workout sensors (exercise devices), receiving workout sensor data, calibrating sensors for monitoring workouts, selecting and playing music for workouts, and displaying, storing, and transmitting workout data.

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

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

In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, browser module 147 includes executable instructions for browsing the internet according to user instructions, including searching, linking to, receiving, and displaying web pages or portions thereof, as well as attachments and other files linked to web pages.

In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion 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 data associated with calendars (e.g., calendar entries, to-do items, etc.) according to user instructions.

In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, and browser module 147, gadget module 149 is a mini-application (e.g., weather gadget 149-1, stock gadget 149-2, calculator gadget 149-3, alarm gadget 149-4, and dictionary gadget 149-5) or a mini-application created by a user (e.g., user created gadget 149-6) that is optionally downloaded and used by a user. In some embodiments, gadgets include HTML (hypertext markup language) files, CSS (cascading style sheet) files, and JavaScript files. In some embodiments, gadgets include XML (extensible markup language) files and JavaScript files (e.g., yahoo | gadgets).

In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, and browser module 147, gadget creator module 150 is optionally used by a user to create gadgets (e.g., to transform user-specified portions of a web page into gadgets).

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

In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, audio circuit 110, speaker 111, RF circuit 108, and browser module 147, video and music player module 152 includes executable instructions that allow a user to download and playback 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, rendering, or otherwise playing back video (e.g., on touch screen 112 or on an external display connected via external port 124). In some embodiments, the device 100 optionally includes the functionality of an MP3 player such as an iPod (trademark of Apple inc.).

In conjunction with the touch screen 112, the display controller 156, the contact/movement module 130, the graphics module 132, and the text input module 134, the notes module 153 includes executable instructions for creating and managing notes, backlog, and the like according to user instructions.

In conjunction with the RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, GPS module 135, and browser module 147, map module 154 is optionally configured to receive, display, modify, and store maps and data associated with maps (e.g., driving directions, data related to shops and other points of interest at or near a particular location, and other location-based data) according to user instructions.

In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, audio circuit 110, speaker 111, RF circuit 108, text input module 134, email client module 140, and browser module 147, online video module 155 includes instructions for allowing a user to access, browse, receive (e.g., by streaming and/or downloading), play back (e.g., on a touch screen or on an external display connected via external port 124), send email with a link to a particular online video, and otherwise manage online video in one or more file formats such as h.264. In some embodiments, the instant messaging module 141 is used to send links to particular online videos instead of the email client module 140. Additional description of online video applications can be found in U.S. provisional patent application Ser. No. 60/936,562, entitled "Portable Multifunction Device, method, AND GRAPHICAL User Interface for Playing Online Videos," filed on even 20 th 6 th 2007, and U.S. patent application Ser. No. 11/968,067, entitled "Portable Multifunction Device, method, AND GRAPHICAL User Interface for Playing Online Videos," filed on even 31 th 12 th 2007, the contents of both of which are hereby incorporated by reference in their entirety.

Each of the modules and applications described above corresponds to a set of executable instructions for performing one or more of the functions described above as well as the methods described in this patent application (e.g., the computer-implemented methods and other information processing methods described herein). These modules (e.g., sets of instructions) need not be implemented in a separate software program, such as a computer program (e.g., including instructions), process, or module, and thus various subsets of these modules may optionally be combined or otherwise rearranged in various embodiments. For example, the video player module may optionally be combined with the music player module into a single module (e.g., video and music player module 152 in FIG. 1A). In some embodiments, memory 102 optionally stores a subset of the modules and data structures described above. Further, the memory 102 optionally stores additional modules and data structures not described above.

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

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

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

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

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

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

In some embodiments, event monitor 171 sends requests to peripheral interface 118 at predetermined intervals. In response, the peripheral interface 118 transmits event information. In other embodiments, the peripheral interface 118 transmits event information only if there is a significant event (e.g., receiving an input above a predetermined noise threshold and/or receiving an input exceeding a predetermined duration).

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

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

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 respective application) in which the touch is detected optionally corresponds to a level of programming within the application's programming or view hierarchy. For example, the lowest horizontal view in which a touch is detected is optionally referred to as a hit view, and the set of events that are recognized as being correctly entered is optionally determined based at least in part on the hit view of the initial touch that begins a touch-based gesture.

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

The activity event recognizer determination module 173 determines which view or views within the view hierarchy should receive a particular sequence of sub-events. In some implementations, the active event identifier determination module 173 determines that only the hit view should receive a particular sequence of sub-events. In other embodiments, the activity event recognizer determination module 173 determines that all views that include the physical location of a sub-event are actively engaged views, and thus determines that all actively engaged views should receive a particular sequence of sub-events. In other embodiments, even if the touch sub-event is completely localized to an area associated with one particular view, the higher view in the hierarchy will remain the actively engaged view.

The event dispatcher module 174 dispatches event information to an event recognizer (e.g., event recognizer 180). In embodiments that include an active event recognizer determination module 173, the event dispatcher module 174 delivers event information to the event recognizers determined by the active event recognizer determination module 173. In some embodiments, the event dispatcher module 174 stores event information in an event queue that is retrieved by the corresponding event receiver 182.

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

In some embodiments, the application 136-1 includes a plurality of event handlers 190 and one or more application views 191, each of which includes instructions for processing touch events that occur within a respective view of the user interface of the application. Each application view 191 of the application 136-1 includes one or more event recognizers 180. Typically, the respective application view 191 includes a plurality of event recognizers 180. In other embodiments, one or more of the event recognizers 180 are part of a separate module that is a higher level object from which methods and other properties are inherited, such as the user interface toolkit or application 136-1. In some implementations, the respective event handler 190 includes one or more of a data updater 176, an object updater 177, a GUI updater 178, and/or event data 179 received from the event classifier 170. Event handler 190 optionally utilizes or invokes data updater 176, object updater 177, or GUI updater 178 to update the application internal state 192. Alternatively, one or more of application views 191 include one or more corresponding event handlers 190. Additionally, in some implementations, one or more of the data updater 176, the object updater 177, and the GUI updater 178 are included in a respective application view 191.

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

Event receiver 182 receives event information from event sorter 170. The event information includes information about sub-events such as touches or touch movements. The event information also includes additional information, such as the location of the sub-event, according to the sub-event. When the sub-event relates to movement of a touch, the event information optionally also includes the rate and direction of the sub-event. In some embodiments, the event includes rotation of the device from one orientation to another orientation (e.g., from a portrait orientation to a landscape orientation, or vice versa), and the event information includes corresponding information about a current orientation of the device (also referred to as a device pose).

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

In some implementations, the event definitions 186 include definitions of events for respective user interface objects. In some implementations, the event comparator 184 performs a hit test to determine which user interface object is associated with a sub-event. For example, in an application view that displays three user interface objects on touch-sensitive display 112, when a touch is detected on touch-sensitive display 112, event comparator 184 performs a hit test to determine which of the three user interface objects is associated with the touch (sub-event). If each displayed object is associated with a respective event handler 190, the event comparator uses the results of the hit test to determine which event handler 190 should be activated. For example, event comparator 184 selects an event handler associated with the sub-event and the object that triggered the hit test.

In some embodiments, the definition of the respective event (187) further includes a delay action that delays delivery of the event information until it has been determined that the sequence of sub-events does or does not correspond to an event type of the event recognizer.

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

In some embodiments, the respective event recognizer 180 includes metadata 183 with configurable properties, flags, and/or lists that indicate how the event delivery system should perform sub-event delivery to the actively engaged event recognizer. In some embodiments, metadata 183 includes configurable attributes, flags, and/or lists that indicate how event recognizers interact or are able to interact with each other. In some embodiments, metadata 183 includes configurable properties, flags, and/or lists that indicate whether sub-events are delivered to different levels in a view or programmatic hierarchy.

In some embodiments, when one or more particular sub-events of an event are identified, the corresponding event recognizer 180 activates an event handler 190 associated with the event. In some implementations, the respective event identifier 180 delivers event information associated with the event to the event handler 190. The activate event handler 190 is different from sending (and deferring) sub-events to the corresponding hit view. In some embodiments, event recognizer 180 throws a marker associated with the recognized event, and event handler 190 associated with the marker retrieves the marker and performs a predefined process.

In some implementations, the event delivery instructions 188 include sub-event delivery instructions that deliver event information about the sub-event without activating the event handler. Instead, the sub-event delivery instructions deliver the event information to an event handler associated with the sub-event sequence or to an actively engaged view. Event handlers associated with the sequence of sub-events or with the actively engaged views receive the event information and perform a predetermined process.

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

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

It should be appreciated that the above discussion regarding event handling of user touches on a touch sensitive display also applies to other forms of user inputs that utilize an input device to operate the multifunction device 100, not all of which are initiated on a touch screen. For example, mouse movements and mouse button presses, optionally in conjunction with single or multiple keyboard presses or holds, contact movements on a touch pad, such as taps, drags, scrolls, etc., stylus inputs, movements of a device, verbal instructions, detected eye movements, biometric inputs, and/or any combination thereof, are optionally used as inputs corresponding to sub-events defining the event to be distinguished.

Fig. 2 illustrates a portable multifunction device 100 with a touch screen 112 in accordance with some embodiments. The touch screen optionally displays one or more graphics within a User Interface (UI) 200. In this and other embodiments described below, a user can select one or more of these graphics by making a gesture on the graphics, for example, with 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 will occur when a user breaks contact with the one or more graphics. In some embodiments, the gesture may optionally include one or more taps, one or more swipes (left to right, right to left, up and/or down), and/or scrolling of a finger that has been in contact with the device 100 (right to left, left to right, up and/or down). In some implementations or in some cases, inadvertent contact with the graphic does not select the graphic. For example, when the gesture corresponding to the selection is a tap, a swipe gesture that swipes over an application icon optionally does not select the corresponding application.

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

In some embodiments, the device 100 includes a touch screen 112, menu buttons 204, a press button 206 for powering the device on/off and for locking the device, one or more volume adjustment buttons 208, a Subscriber Identity Module (SIM) card slot 210, a headset jack 212, and a docking/charging external port 124. Pressing button 206 is optionally used to turn the device on/off by pressing the button and holding the button in the pressed state for a predefined time interval, to lock the device by pressing the button and releasing the button before the predefined time interval has elapsed, and/or to unlock the device or initiate an unlocking process. In an alternative embodiment, the device 100 also accepts voice input through the microphone 113 for activating or deactivating certain functions. The device 100 also optionally includes one or more contact intensity sensors 165 for detecting the intensity of contacts on the touch screen 112, and/or one or more haptic output generators 167 for generating haptic outputs for a user of the device 100.

FIG. 3 is a block diagram of an exemplary multifunction device with a display and a touch-sensitive surface in accordance with some embodiments. The device 300 need not be portable. In some embodiments, the device 300 is a laptop computer, a desktop computer, a tablet computer, a multimedia player device, a navigation device, an educational device (such as a child learning toy), a gaming system, or a control device (e.g., a home controller or an industrial controller). The device 300 generally 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. Communication bus 320 optionally includes circuitry (sometimes referred to as a chipset) that interconnects and controls communications between system components. The device 300 includes an input/output (I/O) interface 330 with a display 340, typically a touch screen display. The I/O interface 330 also optionally includes a keyboard and/or mouse (or other pointing device) 350 and a touchpad 355, a tactile output generator 357 (e.g., similar to the tactile output generator 167 described above with reference to fig. 1A), sensors 359 (e.g., optical sensors, acceleration sensors, proximity sensors, touch sensitive sensors, and/or contact intensity sensors (similar to the contact intensity sensor 165 described above with reference to fig. 1A)) for generating tactile outputs on the device 300. Memory 370 includes high-speed random access memory, such as DRAM, SRAM, DDR RAM, or other random access solid state memory devices, and optionally nonvolatile memory, such as one or more magnetic disk storage devices, optical disk storage devices, flash memory storage devices, or other nonvolatile solid state memory devices. Memory 370 optionally includes one or more storage devices located remotely from CPU 310. In some embodiments, memory 370 stores programs, modules, and data structures, or a subset thereof, similar to those stored in memory 102 of portable multifunction device 100 (fig. 1A). Further, the memory 370 optionally stores additional programs, modules, and data structures not present in the memory 102 of the portable multifunction device 100. For example, memory 370 of device 300 optionally stores drawing module 380, presentation module 382, word processing module 384, website creation module 386, disk editing module 388, and/or spreadsheet module 390, while memory 102 of portable multifunction device 100 (FIG. 1A) optionally does not store these modules.

Each of the above elements in fig. 3 may optionally be stored in one or more of the previously mentioned memory devices. Each of the above-described modules corresponds to a set of instructions for performing the functions described above. The above-described modules or computer programs (e.g., sets of instructions or instructions) need not be implemented in a separate software program (such as a computer program (e.g., instructions), process or module, and thus various subsets of these modules may optionally be combined or otherwise rearranged in various embodiments. In some embodiments, memory 370 optionally stores a subset of the modules and data structures described above. Further, memory 370 optionally stores additional modules and data structures not described above.

Attention is now directed to embodiments of user interfaces that may optionally be implemented on, for example, portable multifunction device 100.

Fig. 4A illustrates an exemplary user interface of an application menu on the portable multifunction device 100 in accordance with some embodiments. A similar user interface is optionally implemented on device 300. In some embodiments, the user interface 400 includes the following elements, or a subset or superset thereof:

● A signal strength indicator 402 for wireless communications, such as cellular signals and Wi-Fi signals;

● Time 404;

● A bluetooth indicator 405;

● A battery status indicator 406;

● A tray 408 with icons for commonly used applications such as:

an icon 416 labeled "phone" of phone module 138, optionally including an indicator 414 of the number of missed calls or voice mails;

an icon 418 of email client module 140 marked "mail" optionally including an indicator 410 of the number of unread emails;

Icon 420 labeled "browser" of browser module 147, and

The video and music player module 152 (also known as iPod (apple inc.)

(Trademark of Apple Inc.) module 152) icon 422 labeled "iPod"

● Icons of other applications, such as:

icon 424 marked "message" for IM module 141;

icon 426 of calendar module 148 marked "calendar";

icon 428 marked "photo" of image management module 144;

icon 430 marked "camera" for camera module 143;

icon 432 of online video module 155 marked "online video";

icon 434 labeled "stock market" for stock market gadget 149-2;

icon 436 marked "map" of map module 154;

icon 438 labeled "weather" for weather gadget 149-1;

icon 440 labeled "clock" for alarm clock gadget 149-4;

Icon 442 labeled "fitness support" for fitness support module 142;

Icon 444 marked "note" of the note module 153, and

The "set" marked icon 446 of a set application or module provides access to the settings of the device 100 and its various applications 136.

It should be noted that the iconic labels illustrated in fig. 4A are merely exemplary. For example, the icon 422 of the video and music player module 152 is labeled "music" or "music player". Other labels may optionally be used for various application icons. In some embodiments, the label of the respective application icon includes a name of the application corresponding to the respective application icon. In some embodiments, the label of a particular application icon is different from the name of the application corresponding to the particular application icon.

Fig. 4B illustrates an exemplary user interface on a device (e.g., device 300 of fig. 3) having a touch-sensitive surface 451 (e.g., tablet or touchpad 355 of fig. 3) separate from a display 450 (e.g., touch screen display 112). The device 300 also optionally includes one or more contact intensity sensors (e.g., one or more of the sensors 359) for detecting the intensity of the contact on the touch-sensitive surface 451 and/or one or more tactile output generators 357 for generating tactile outputs for a user of the device 300.

While some of the examples below will be given with reference to inputs on touch screen display 112 (where the touch sensitive surface and the display are combined), in some embodiments the device detects inputs on a touch sensitive surface separate from the display, as shown in fig. 4B. In some implementations, the touch-sensitive surface (e.g., 451 in fig. 4B) has a primary axis (e.g., 452 in fig. 4B) that corresponds to the primary axis (e.g., 453 in fig. 4B) on the display (e.g., 450). According to these embodiments, the device detects contact (e.g., 460 and 462 in fig. 4B) with the touch-sensitive surface 451 at a location corresponding to a respective location on the display (e.g., 460 corresponds to 468 and 462 corresponds to 470 in fig. 4B). In this way, when the touch-sensitive surface (e.g., 451 in FIG. 4B) is separated from the display (e.g., 450 in FIG. 4B) of the multifunction device, user inputs (e.g., contacts 460 and 462 and movement thereof) detected by the device on the touch-sensitive surface are used by the device to manipulate the user interface on the display. It should be appreciated that similar approaches may alternatively be used for other user interfaces described herein.

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

Fig. 5A illustrates an exemplary personal electronic device 500. The device 500 includes a body 502. In some embodiments, device 500 may include some or all of the features described with respect to devices 100 and 300 (e.g., fig. 1A-4B). In some implementations, the device 500 has a touch sensitive display 504, hereinafter referred to as a touch screen 504. Alternatively, or in addition to touch screen 504, device 500 also has a display and a touch-sensitive surface. As with devices 100 and 300, in some implementations, touch screen 504 (or touch-sensitive surface) optionally includes one or more intensity sensors for detecting the intensity of an applied contact (e.g., touch). One or more intensity sensors of the touch screen 504 (or touch sensitive surface) may provide output data representative of the intensity of the touch. The user interface of the device 500 may respond to touches based on the intensity of the touches, meaning that touches of different intensities may invoke different user interface operations on the device 500.

Exemplary techniques for detecting and processing touch strength are found, for example, in related patent applications, international patent application serial number PCT/US2013/040061, filed on 5 months 8 days 2013, entitled "Device,Method,and Graphical User Interface for Displaying User Interface Objects Corresponding to an Application", published as WIPO patent publication number WO/2013/169849, and international patent application serial number PCT/US2013/069483, filed on 11 months 11 days 2013, entitled "Device,Method,and Graphical User Interface for Transitioning Between Touch Input to Display Output Relationships", published as WIPO patent publication number WO/2014/105276, each of which is hereby incorporated by reference in its entirety.

In some embodiments, the device 500 has one or more input mechanisms 506 and 508. The input mechanisms 506 and 508 (if included) may be in physical form. Examples of physical input mechanisms include push buttons and rotatable mechanisms. In some embodiments, the device 500 has one or more attachment mechanisms. Such attachment mechanisms, if included, may allow for attachment of the device 500 with, for example, a hat, glasses, earrings, necklace, shirt, jacket, bracelet, watchband, bracelet, pants, leash, shoe, purse, backpack, or the like. These attachment mechanisms allow the user to wear the device 500.

Fig. 5B depicts an exemplary personal electronic device 500. In some embodiments, the apparatus 500 may include some or all of the components described with respect to fig. 1A, 1B, and 3. The device 500 has a bus 512 that operatively couples an I/O section 514 with one or more computer processors 516 and memory 518. The I/O portion 514 may be connected to a display 504, which may have a touch sensitive component 522 and optionally an intensity sensor 524 (e.g., a contact intensity sensor). In addition, the I/O portion 514 may be connected to a communication unit 530 for receiving application and operating system data using Wi-Fi, bluetooth, near Field Communication (NFC), cellular, and/or other wireless communication technologies. The device 500 may include input mechanisms 506 and/or 508. For example, the input mechanism 506 may alternatively be a rotatable input device or a depressible input device and a rotatable input device. In some examples, the input mechanism 508 is optionally a button.

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

The memory 518 of the personal electronic device 500 may include one or more non-transitory computer-readable storage media for storing computer-executable instructions that, when executed by the one or more computer processors 516, for example, may cause the computer processors to perform techniques described below, including process 700 (fig. 7). A computer-readable storage medium may be any medium that can tangibly contain or store computer-executable instructions for use by or in connection with an instruction execution system, apparatus, and device. In some examples, the storage medium is a transitory computer-readable storage medium. In some examples, the storage medium is a non-transitory computer-readable storage medium. The non-transitory computer readable storage medium may include, but is not limited to, magnetic storage devices, optical storage devices, and/or semiconductor storage devices. Examples of such storage devices include magnetic disks, optical disks based on CD, DVD, or blu-ray technology, and persistent solid state memories such as flash memory, solid state drives, etc. The personal electronic device 500 is not limited to the components and configuration of fig. 5B, but may include other components or additional components in a variety of configurations.

As used herein, the term "affordance" refers to a user-interactive graphical user interface object that is optionally displayed on a display screen of device 100, 300, and/or 500 (fig. 1A, 3, and 5A-5B). For example, an image (e.g., an icon), a button, and text (e.g., a hyperlink) optionally each constitute an affordance.

As used herein, the term "focus selector" refers to an input element for indicating the current portion of a user interface with which a user is interacting. In some implementations that include a cursor or other position marker, the cursor acts as a "focus selector" such that when the cursor detects an input (e.g., presses an input) on a touch-sensitive surface (e.g., touch pad 355 in fig. 3 or touch-sensitive surface 451 in fig. 4B) above a particular user interface element (e.g., a button, window, slider, or other user interface element), the particular user interface element is adjusted according to the detected input. In some implementations including a touch screen display (e.g., touch sensitive display system 112 in fig. 1A or touch screen 112 in fig. 4A) that enables direct interaction with user interface elements on the touch screen display, the contact detected on the touch screen acts as a "focus selector" such that when an input (e.g., a press input by a contact) is detected on the touch screen display at the location of a particular user interface element (e.g., a button, window, slider, or other user interface element), the particular user interface element is adjusted in accordance with the detected input. In some implementations, the focus is moved from one region of the user interface to another region of the user interface without a corresponding movement of the cursor or movement of contact on the touch screen display (e.g., by moving the focus from one button to another using a tab key or arrow key). In these implementations, the focus selector moves according to movement of the focus between different regions of the user interface. Regardless of the particular form that the focus selector takes, the focus selector is typically controlled by the user in order to deliver a user interface element (or contact on the touch screen display) that is interactive with the user of the user interface (e.g., by indicating to the device the element with which the user of the user interface desires to interact). For example, upon detection of a press input on a touch-sensitive surface (e.g., a touchpad or touch screen), the position of a focus selector (e.g., a cursor, contact, or selection box) over a respective button will indicate that the user desires to activate the respective button (rather than other user interface elements shown on the device display).

As used in the specification and claims, the term "characteristic intensity" of a contact refers to the characteristic of a contact based on one or more intensities of the contact. In some embodiments, the characteristic intensity is based on a plurality of intensity samples. The characteristic intensity is optionally based on a predefined number of intensity samples or a set of intensity samples acquired during a predetermined period of time (e.g., 0.05 seconds, 0.1 seconds, 0.2 seconds, 0.5 seconds, 1 second, 2 seconds, 5 seconds, 10 seconds) relative to a predefined event (e.g., after detection of contact, before detection of lift-off of contact, before or after detection of start of movement of contact, before or after detection of end of contact, before or after detection of an increase in intensity of contact and/or before or after detection of a decrease in intensity of contact). The characteristic intensity of the contact is optionally based on one or more of a maximum value of the intensity of the contact, a mean value of the intensity of the contact, a value at the first 10% of the intensity of the contact, a half maximum value of the intensity of the contact, a 90% maximum value of the intensity of the contact, and the like. In some embodiments, the duration of the contact is used in determining the characteristic intensity (e.g., when the characteristic intensity is an average of the intensity of the contact over time). In some embodiments, the characteristic intensity is compared to a set of one or more intensity thresholds to determine whether the user has performed an operation. For example, the set of one or more intensity thresholds optionally includes a first intensity threshold and a second intensity threshold. In this example, contact of the feature strength that does not exceed the first threshold results in a first operation, contact of the feature strength that exceeds the first strength threshold but does not exceed the second strength threshold results in a second operation, and contact of the feature strength that exceeds the second threshold results in a third operation. In some implementations, a comparison between the feature strength and one or more thresholds is used to determine whether to perform one or more operations (e.g., whether to perform or forgo performing the respective operations) rather than for determining whether to perform the first or second operations.

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

Fig. 6A-6K illustrate exemplary user interfaces for tracking sleep behavior according to some embodiments. The user interfaces in these figures are used to illustrate the processes described below, including the process in fig. 7.

In fig. 6A, device 600 displays a sleep interface 610 on display 602. In general, sleep interface 610 includes information regarding various aspects of sleep corresponding to a user of device 600. As an example, the sleep interface 610 includes a sleep schedule 612 that indicates an amount of sleep of a user acquired in each of a plurality of intervals (e.g., nights) over a period of time (e.g., a week). As another example, the sleep interface 610 includes a sleep stage portion 614 that illustrates sleep stages experienced by a user over a period of time (e.g., day, night). As yet another example, sleep interface 610 includes a data affordance 618 that, when selected, enables device 600 to display sleep data for one or more sleep periods, as described in further detail below.

In some embodiments, the information included in the sleep interface 610 is provided based on sleep data received by the device 600. In some embodiments, device 600 receives sleep data from one or more input devices, including, but not limited to, a wearable device (e.g., a smart watch) and a biometric sensor (e.g., a heart rate monitor, an oxygen monitor).

Sleep interface 610 includes a detailed affordance 616 that, when selected, causes device 600 to provide additional information regarding sleep aspects corresponding to a user of device 600. For example, when the sleep interface 610 is displayed, the device 600 detects selection of the detail affordance 616. The selection is a tap gesture 605a on a detail affordance 616. As shown in fig. 6B, in response to detecting a flick gesture 605a (and optionally one or more additional inputs), device 600 displays a sleep stage interface 620.

In general, sleep stage interface 620 includes information regarding various aspects of sleep stages detected for one or more sleep periods. For example, sleep interface 620 includes sleep structure diagram 622. Sleep structure diagram 622 graphically illustrates sleep stages experienced by a user for a sleep period. In some embodiments, the sleep period may be any period of time defined by the device 600, such as a day or a night. In some embodiments, the sleep period is determined by the device 600 based on the detected user behavior. For example, the sleep period may be defined by determining when the user falls asleep and/or wakes up. Additionally or alternatively, a sleep period may be defined as determining when a user is lying in and/or getting up from the bed.

In some embodiments, sleep structure map 622 is generated based on sleep data received by device 600. For example, device 600 determines from the sleep data which sleep stages (and when), if any, the user has undergone during the sleep period. For example, indications 622a and 622b of sleep structure diagram 622 are shown to correspond to "core" and "awake" (e.g., awake in sleep) sleep stages, respectively, indicating that device 600 determines from sleep data that the user initially began a sleep period with a core sleep stage and transitioned to an awake sleep stage.

In some embodiments, the device 600 determines that the sleep data is ambiguous for a particular sub-period of the sleep period. For example, device 600 may not be able to determine which sleep stage the user has undergone based on the sleep data. In some embodiments, the sleep data for a sub-period is ambiguous when the sleep data for the sub-period is lost or erroneous. In some embodiments, when the sleep data for a sub-period is ambiguous, the sleep data for the sub-period is ambiguous (e.g., the sleep data is not sufficiently distinct such that the sleep data for the sub-period may be exclusively associated with a particular sleep stage).

In some embodiments, the device 600 indicates which subintervals of the sleep period correspond to ambiguous sleep data. As an example, indicator 622c of sleep structure diagram 622 is shown as corresponding to a plurality of sleep stages (e.g., core, fast eye movement, depth), indicating that sleep data for the sub-period corresponding to indicator 622c is ambiguous. As another example, indicator 622d of sleep structure diagram 622 is shown as corresponding to a plurality of sleep stages, indicating that sleep data for the sub-period corresponding to indicator 622d is ambiguous. In some embodiments, the indicators corresponding to ambiguous sleep data correspond to three sleep stages, as shown. In some embodiments, the indicators corresponding to ambiguous sleep data may correspond to other numbers of sleep stages (e.g., 2, 4).

Sleep stage interface 620 also includes sleep stage affordances 624a-624d. Sleep stage affordance 624a indicates a total amount of time the user has experienced awake sleep stages during a sleep period. Sleep stage affordance 624b indicates a total amount of time the user has experienced core sleep stages during the sleep period. Sleep stage affordance 624c indicates a total amount of time the user has experienced a fast eye-movement sleep stage during the sleep period. Sleep stage affordance 624d indicates a total amount of time the user has experienced deep sleep stages during a sleep period.

In some embodiments, the total amount of time indicated by the sleep stage affordances 624a-624d includes an ambiguous sub-period. For example, if a sleep stage cannot be determined within a sub-period of time (e.g., sleep data for the sub-period of time is ambiguous), device 600 assigns the amount of time (or a portion of the amount of time) to each sleep stage. In some embodiments, time is allocated to all sleep stages except the awake stage. In some embodiments, the total amount of time indicated by the sleep stage affordances 624a-624d does not include an ambiguous sub-period.

In some embodiments, each sleep stage affordance 624a-624d, when selected, causes the corresponding sleep stage to be highlighted in sleep structure diagram 622. As an example, selection of sleep stage affordances 624a causes device 600 to visually emphasize (e.g., highlight) all indicators of sleep structure diagram 622 corresponding to awake sleep stages (e.g., 622 b) and/or visually de-emphasize indicators corresponding to other sleep stages (e.g., 622 a). In some embodiments, indicators corresponding to multiple sleep stages (e.g., indicators of sub-periods corresponding to ambiguous sleep data, such as 622 c) are not visually emphasized or de-emphasized in response to selection of the sleep stage affordances 624a-624 d. In some embodiments, indicators corresponding to multiple sleep stages are visually emphasized in response to selection of sleep stage affordances 624a-624d (e.g., 622c may be emphasized when sleep stage affordances 624c are selected).

In some implementations, the sleep stage interface 620 is displayed according to a particular time frame. As shown in fig. 6B, for example, the time frame indicator 626 indicates that the current time frame of the sleep stage interface 620 is one day ("D"). In some embodiments, the time frame of sleep stage interface 620 is modified. For example, when sleep stage interface 620 is displayed, device 600 detects a selection of a new time frame (e.g., one week, "W") on time frame indicator 626. The selection is a flick gesture 605b on a time frame indicator 626. As shown in fig. 6C, in response to detecting the flick gesture 605b, the device 600 modifies the time frame of the sleep stage interface 620 from one day to one week.

In some embodiments, modifying the time frame of sleep stage interface 620 may cause device 600 to modify (e.g., remove) the display of sleep structure map 622. For example, as shown in fig. 6C, modifying the time frame from one day to one week may cause device 600 to replace the display of sleep structure diagram 622 with sleep stage diagram 628 (for reference, fig. 6C includes an enlarged version of sleep stage diagram 628). Sleep stage diagram 628 includes a set of columns, each of which may be used as a sleep structure map for a corresponding day of the week. For example, each column includes a "stack" of indicators that indicate the order and duration of sleep stages that the user has experienced on the respective day of the week. As an example, column 630 and sleep structure map 622 may correspond to the same sleep period. Thus, column 630 includes indicators 622a-622d. In some implementations, the indicators are visually distinguished within each column using one or more visual characteristics (e.g., color, brightness).

In some embodiments, sleep stages are compared to one or more other health indicators. For example, when the sleep stage interface 620 is displayed, the device 600 detects a selection of the comparative affordance 634. The selection is a flick gesture 605c on the comparative affordance 634. As shown in fig. 6D, in response to detecting tap gesture 605c, device 600 displays comparison interface 640. In the example shown, the time frame of sleep stage interface 620 reverts to the time frame of the day in response to selection of tap gesture 605c. In some embodiments, the time frame of sleep stage interface 620 is maintained (e.g., the time frame is not modified and remains for one week).

The comparison interface 640 includes a sleep stage portion 642 and a health metrics portion 644. Sleep stage section 642 includes a sleep structure diagram 643, which in some embodiments corresponds to sleep structure diagram 622. Thus, sleep structure diagram 643 includes indicators 642a-642d, which in some embodiments correspond to indicators 622a-622d. The health metric portion 644 illustrates the value of a health metric (e.g., heart rate) of the user during a sleep period. In some embodiments, both sleep stage portion 642 and health metrics portion 644 are aligned with the same x-axis such that sleep structure map 643 and health metrics displayed in health metrics portion 644 are aligned with respect to time (e.g., allowing a user to easily view sleep stages and/or compare sleep stages to health metrics over a sleep period).

The comparison interface 640 also includes metric affordances 646a-646c, each metric affordance corresponding to a respective health metric. In some embodiments, metric affordance 646a corresponds to heart rate, metric affordance 646b corresponds to respiration rate, and metric affordance 646c corresponds to wrist temperature. As shown, the metric affordance 646a is visually emphasized, indicating that the metric corresponding to the metric affordance 646a is selected (e.g., by default) for display. Accordingly, the value of the heart rate is displayed in the health measurement section 644.

In some embodiments, values of other health metrics may be displayed in health metrics section 644. For example, when the comparison interface 640 is displayed, the device 600 detects a selection of the metric affordance 646 c. The selection is a flick gesture 605d on a metric affordance 646 c. As shown in fig. 6E, in response to detecting the flick gesture 605d, the device 600 visually emphasizes the metric affordance 646c (and optionally visually de-emphasizes the metric affordance 646 a) and displays a value of the wrist temperature in the health metrics portion 644 (recall that in some embodiments the metric affordance 646c corresponds to the wrist temperature).

Referring again to fig. 6A, the data affordance 618 or the sleep interface 610, when selected, causes the device 600 to display sleep data. For example, when the sleep interface 610 is displayed, the device 600 detects a selection of the data affordance 618. The selection is a flick gesture 607a on the data affordance 618. As shown in fig. 6F, in response to detecting the flick gesture 607a, the device 600 displays a sleep data interface 650.

Generally, sleep data interface 650 includes information regarding sleep data received by device 600. As shown, in some embodiments, sleep data interface 650 includes information 652 corresponding to sleep data for a first sleep period (e.g., 3 months, 17 days, to 18 days) and information 654 corresponding to sleep data for a second sleep period (e.g., 3 months, 16 days, to 17 days). It should be appreciated that the sleep data interface 650 may include information for any number of sleep periods.

In some embodiments, the information of sleep periods is organized by sleep stage. For example, information 652 may include a sleep stage affordance 652a corresponding to awake sleep stages, a sleep stage affordance 652b corresponding to core sleep stages, a sleep stage affordance 652c corresponding to fast-eye sleep stages, and a sleep stage affordance 652d corresponding to deep sleep stages. Each sleep stage affordance 652a-652d may indicate a number of times a respective stage is reached during a sleep period and a total amount of time a user has experienced the sleep stage during the sleep period.

While sleep data interface 650 is displayed, device 600 detects a selection of sleep stage affordance 652 c. The selection is a flick gesture 605f on the sleep stage affordance 652 c. As shown in fig. 6G, in response to detecting the flick gesture 605f, the device 600 displays a sleep period interface 660.

Sleep period interface 660 includes information corresponding to particular sleep stages during a sleep period. For example, the sleep period interface includes sleep period affordances 662a-662c, each sleep period affordance corresponding to a respective period of time that a user experiences a particular sleep stage (e.g., rapid eye movement). In some embodiments, each sleep period affordance 662a-662c indicates an amount of time that the user has experienced a particular sleep stage, and optionally indicates a start time and an end time of a period that the user has experienced the sleep stage.

While sleep period interface 660 is displayed, device 600 detects a selection of sleep period affordance 662 a. The selection is a flick gesture 605g on a sleep period affordance 662 a. As shown in fig. 6H, in response to detecting tap gesture 605g, device 600 displays details interface 670. The details interface 670 includes information 672 about the selected sleep stage period corresponding to the affordance 662 a. As shown, the information 672 provided in the sleep session detail interface 670 includes, but is not limited to, the sleep session type (e.g., rapid eye movement), the start time of the sleep session, the end time of the sleep session, the source of the sleep data, and the date the sleep data was received.

Although described herein with respect to device 600 displaying sleep stage interface 620 in response to selection of detailed affordance 616, in some embodiments sleep stage interface 620 is displayed in response to selection of one or more other affordances. For example, in FIG. 6I, device 600 displays a main interface 680 that includes various affordances corresponding to respective applications on device 600. Main interface 680 includes a sleep stage affordance 682 that, when selected (e.g., selected with tap gesture 605 i), causes device 600 to display sleep stage interface 620.

In some implementations, information regarding various aspects of sleep stages experienced by a user during sleep is provided on an external device (e.g., a smart watch). As an example, in fig. 6J, device 601 displays notification interface 690 on display 603. As shown, notification interface 690 includes a sleep structure map 692 corresponding to sleep structure map 622 (e.g., based on the same data), and indicators 691a-691d indicating the amount of time a user has experienced a respective sleep stage during a sleep period. In some embodiments, notification interface 690 is displayed in response to completion of a sleep period.

As another example, in fig. 6K, device 601 displays a sleep stage interface 695 on display 603. As shown, sleep stage interface 695 includes a sleep structure map 697 corresponding to sleep structure map 622 (e.g., based on the same data), and indicators 691a-691d indicating the amount of time a user has experienced a corresponding sleep stage during a sleep period. In some embodiments, notification interface 695 is displayed in response to opening a sleep application on device 601.

Fig. 7 is a flowchart illustrating a method for tracking sleep behavior using a computer system, in accordance with some embodiments. The method 700 is performed at a computer system (e.g., 100, 300, 500) (e.g., a smartwatch, a smartphone, a head mounted display, a robot, a personal auxiliary device, an automaton device, and/or a personal computer) in communication with a display generation component (e.g., an integrated display and/or a display controller) and one or more input devices (e.g., a wearable device (e.g., a smartwatch) or a biometric sensor (e.g., a heart rate monitor, an oxygen monitor)). Some operations in method 700 may optionally be combined, the order of some operations may optionally be changed, and some operations may optionally be omitted.

As described below, the method 700 provides an intuitive way for tracking sleep behavior. The method reduces the cognitive burden of the user to track sleep behavior, thereby creating a more efficient human-machine interface. For battery-powered electronic devices, enabling a user to track sleep behavior faster and more efficiently saves power and increases the time interval between battery charges.

The computer system (e.g., 600) receives (702) sleep data corresponding to a sleep period (e.g., overnight sleep) from one or more input devices (e.g., 602). In some embodiments, the sleep data includes first data corresponding to a first sub-period (e.g., one hour block; consecutive time blocks classified in the same manner (e.g., same classification with respect to sleep stage classification)) of the sleep period.

The computer system displays (704), via a display generation component (e.g., 602), a sleep representation (e.g., 622, 628, 630, 642) that classifies (704) the sleep period into a plurality of sleep stages (e.g., sleep stages shown in sleep structure diagram 622) based on the sleep data (e.g., a sleep structure diagram (e.g., a graph or map that maps one or more sleep stages over time)). In some embodiments, the sleep representation is displayed based on data generated using a wearable electronic device (e.g., 601), such as a smart watch. In some embodiments, the wearable electronic device is worn by the user while sleeping such that the wearable electronic device can generate data (e.g., sleep data) indicative of one or more biological characteristics of the user (e.g., heart rate, respiration rate, physical activity, heart rate variability). In some embodiments, the sleep representation is displayed using data generated in this manner. In some embodiments, the sleep period is night. In some embodiments, the sleep period is a period in which the user is determined to be in bed, in some embodiments, the sleep period is a period in which the user is determined to be asleep, in some embodiments, the sleep period begins when the user is determined to be asleep and/or ends when the user is determined to be awake for a predetermined amount of time and/or no longer in bed. In some embodiments, sleep stages included in the sleep representation include "awake", "fast eye movement", "core" and "depth". In some embodiments, "core" sleep may alternatively be referred to as "light sleep". In some embodiments, the sleep representation is indicated based on sleep data. In some embodiments, displaying the sleep representation includes displaying a first indication corresponding to a first subinterval of the sleep period.

In some embodiments, in accordance with a determination that the first data corresponds exclusively to a first sleep stage of the plurality of sleep stages (e.g., is identified as only the first sleep stage and is not identified as any other sleep stage), the first indication (e.g., any of the indicators 622a-622d, 642a-642 d) indicates (706) that the first sub-period is a first type of sleep period (e.g., is not any other type of sleep period) that corresponds to (e.g., corresponds exclusively to) the first sleep stage. In some embodiments, the computer system (e.g., 600) determines whether the sleep data corresponds to (e.g., exclusively corresponds to) a particular sleep stage. In some embodiments, determining whether the sleep data corresponds to a particular sleep stage includes determining whether the sleep data is ambiguous. In some embodiments, sleep data is considered ambiguous when the computer system is unable to identify sleep stages based on the sleep data (e.g., analysis of the sleep data is ambiguous, sleep data is lost and/or corrupted). In some embodiments, the computer system determines whether the sleep data is ambiguous for one or more portions (e.g., subsets) of the sleep period. In some embodiments, if the sleep data for the subset of sleep periods is determined to correspond to a particular sleep stage (e.g., the data is explicit), the computer system displays the sleep representation such that a portion of the sleep representation associated with (e.g., corresponding to) the subset of sleep periods corresponds to the particular sleep stage. In some embodiments, displaying the sleep representation in this manner includes displaying a plot of the sleep representation at locations corresponding to a subset of specific sleep stages and sleep periods (and not at locations corresponding to a subset of other sleep stages and sleep periods).

In some embodiments, in accordance with a determination that the first data does not exclusively correspond to a single sleep stage of the plurality of sleep stages (e.g., the first data is not identified as corresponding to any sleep stage (but is identified as corresponding to sleep) or to the plurality of sleep stages (e.g., because exclusive correspondence to a single sleep stage has not been identified), for example, the first data is ambiguous), the first indication (e.g., any of indicators 622a-622d, 642a-642 d) indicates (708) that the first sub-period corresponds to at least a second sleep stage of the plurality of sleep stages (e.g., a sleep stage that is the same as or different from the first sleep stage) and a third sleep stage that is different from the second sleep stage (e.g., a portion of the sleep representation associated with the sub-period of the sleep period is displayed as being associated with the plurality of (at least two) sleep stages). In some embodiments, portions of the sleep representation (e.g., 622, 642) are shown as being associated with all sleep stages. In some embodiments, associating the sleep representation in this manner includes displaying a plot of the sleep representation at (1) locations corresponding to a subset of the first sleep stage and sleep period, and (2) locations corresponding to a subset of the second sleep stage and sleep period. In some embodiments, associating the sleep representation in this manner includes discarding the plot displaying the sleep representation for the subset of sleep periods, and optionally visually emphasizing locations corresponding to the first sleep stage and the subset of sleep periods and (2) locations corresponding to the second sleep stage and the subset of sleep periods. In some embodiments, visually emphasizing a location in this manner includes "graying" the location. Displaying a sleep representation comprising an indicator corresponding to a first stage in the case of sleep data corresponding exclusively to the first stage or to a plurality of stages in the case of sleep data not corresponding exclusively to the first stage provides intuitive feedback to the user regarding sleep stages experienced during a sleep period, thereby providing improved feedback to the user.

In some embodiments, the computer system displays, via a display generation component (e.g., 602), a first affordance (e.g., any of affordances 624a-624 d) corresponding to a first sleep stage (e.g., affordances corresponding to core sleep stages) and a second affordance (e.g., any of affordances 624a-624 d) corresponding to a second sleep stage (e.g., affordances corresponding to fast-eye sleep stages). In some implementations, the computer system detects user input (e.g., a tap on any of affordances 624a-624 d) via one or more input devices while displaying the first affordance and the second affordance (e.g., a tap gesture on either the first affordance or the second affordance). In some embodiments, the computer system visually emphasizes a set of indicators (e.g., 622a-622 d) (e.g., one or more indicators) of the sleep representation corresponding to the first sleep stage in accordance with a determination that the user input is a selection of the first affordance when displaying the first affordance and the second affordance. In some embodiments, visually emphasizing the set of indicators of the sleep representation corresponding to the first sleep stage includes highlighting and/or otherwise modifying a display of the set of indicators of the sleep representation corresponding to the first sleep stage. In some embodiments, visually emphasizing the set of indicators includes visually de-emphasizing indicators of the sleep representation that correspond to stages other than the first sleep stage. In some embodiments, the computer system visually emphasizes a set of indicators of the sleep representation corresponding to the second sleep stage in accordance with a determination that the user input is a selection of the second affordance when displaying the first affordance and the second affordance. In some embodiments, visually emphasizing the set of indicators of the sleep representation corresponding to the first sleep stage includes highlighting and/or otherwise modifying a display of the set of indicators of the sleep representation corresponding to the second sleep stage. In some embodiments, visually emphasizing the set of indicators includes visually de-emphasizing indicators of the sleep representation that correspond to stages other than the second sleep stage. Displaying an indicator of a sleep representation corresponding to a particular sleep stage in response to selection of an affordance corresponding to the sleep stage may allow a user to more easily and easily view the indicator of the sleep stage, thereby providing improved visual feedback to the user.

In some embodiments, the set of indicators corresponding to the first sleep stage that visually emphasizes the sleep representation includes the set of indicators corresponding to the second sleep stage that visually de-emphasizes the sleep representation (e.g., in response to selection of the affordance 624a, all indicators except the indicator corresponding to the awake sleep stage (e.g., 622 b) and optionally the indicators corresponding to the plurality of sleep stages (e.g., 622c, 662 d)) are visually de-emphasized. In some embodiments, visually de-emphasizing the set of indicators of the sleep representation corresponding to the second sleep stage includes removing any previously applied visual intensity and/or reducing the brightness and/or color of the set of indicators of the sleep representation corresponding to the second sleep stage. In some embodiments, visually de-emphasizing the set of indicators of the sleep representation corresponding to the second sleep stage includes displaying the set of indicators of the sleep representation corresponding to the second sleep stage in grayscale.

In some embodiments, the set of indicators corresponding to the second sleep stage that visually emphasizes the sleep representation includes visually de-emphasizing the set of indicators corresponding to the first sleep stage of the sleep representation (e.g., in response to selection of the affordance 624a, all indicators except the indicator corresponding to the awake sleep stage (e.g., 622 b) and optionally the indicators corresponding to the plurality of sleep stages (e.g., 622c, 662 d)) are visually de-emphasized. In some embodiments, visually de-emphasizing the set of indicators of the sleep representation corresponding to the first sleep stage includes removing any previously applied visual intensity and/or reducing the brightness and/or color of the set of indicators of the sleep representation corresponding to the first sleep stage. In some embodiments, visually de-emphasizing the set of indicators of the sleep representation corresponding to the first sleep stage includes displaying the set of indicators of the sleep representation corresponding to the first sleep stage in grayscale. Visually de-emphasizing indicators of sleep representations that do not correspond to a particular sleep stage in response to selection of an affordance corresponding to the sleep stage may allow a user to more easily and easily view the indicators of sleep stages, thereby providing improved visual feedback to the user.

In some implementations, the first affordance (e.g., any of affordances 624a-624 d) indicates an amount (e.g., an amount of time and/or a percentage) of sleep periods corresponding to the first sleep stage. In some embodiments, the computer system determines how much of the sleep period corresponds to the first sleep stage based on the sleep data. In some embodiments, the amount is displayed as a total amount of time (e.g., 1 hour, 30 minutes). In some embodiments, the amount is displayed as a percentage. In some embodiments, the percentage represents an amount of sleep periods corresponding to the first sleep stage relative to the total sleep period. In some embodiments, the percentage represents an amount of sleep periods corresponding to the first sleep stage relative to a total sleep period determined to be explicit. In some embodiments, the second affordance (e.g., any of affordances 624a-624 d) indicates an amount (e.g., an amount of time and/or a percentage) of sleep periods corresponding to the second sleep stage. In some embodiments, the computer system determines how much of the sleep period corresponds to the second sleep stage based on the sleep data. In some embodiments, the amount is displayed as a total amount of time (e.g., 1 hour, 30 minutes). In some embodiments, the amount is displayed as a percentage. In some embodiments, the percentage represents an amount of sleep periods corresponding to the second sleep stage relative to the total sleep period. In some embodiments, the percentage represents an amount of sleep periods corresponding to the second sleep stage relative to the total sleep period determined to be explicit. Displaying an affordance indicating a total amount of time that a particular sleep stage has been experienced during a sleep period may provide visual feedback to a user regarding the distribution of sleep stages during the sleep period, thereby providing improved visual feedback to the user.

In some embodiments, determining that the first data corresponds exclusively to the first sleep stage includes determining that the first data corresponding to the first sub-period of the sleep period corresponds in part to the first sleep stage and in part to a fourth sleep stage different from the first sleep stage (e.g., a sleep stage that is the same as or different from the first sleep stage, the second sleep stage, or the third sleep stage, a sleep stage to which the sleeper transitions from the first stage). In some embodiments, the sleep data for the sub-period may be ambiguous, but the computer system may identify a subset of sleep stages in the plurality of sleep stages to which the sleep data for the sub-period may correspond (e.g., partially correspond) (e.g., the first sleep stage is a fast-eye sleep stage and the fourth sleep stage is a core sleep stage or a deep sleep stage). In some embodiments, determining that the first data corresponds exclusively to the first sleep stage includes determining that the first data corresponding to the first subinterval of the sleep period corresponds primarily to the first sleep stage (e.g., is considered to be a first sleep stage with a higher confidence than is considered to be a fourth sleep stage). In some embodiments, the computer system determines that the first data corresponds primarily to a particular sleep stage in the event that the first data is determined to correspond more strongly to the particular sleep stage. In some embodiments, the computer system selects which sleep stage the first data is most likely to correspond to and associates the second data with the identified sleep stage, e.g., based on a confidence value. Determining that the first sleep data corresponds primarily to a particular stage may allow the computer system to assign the sleep data to the particular sleep stage, even when the sleep data corresponds to multiple stages. In this way, the number of ambiguous sub-periods of the sleep representation may be reduced and improved feedback regarding the nature of the sleep data provided to the user.

In some embodiments, the first indication (e.g., 622c, 622 d) includes a first portion (e.g., a first portion of 622c, a first portion of 622 d) and a second portion (e.g., a second portion of 622c, a second portion of 622 d). In some embodiments, in accordance with a determination that the first data does not exclusively correspond to a single sleep stage of the plurality of sleep stages, a first portion of the first indication is displayed at a first location of the sleep representation corresponding to the second sleep stage (e.g., a location corresponding to the core sleep stage). In some embodiments, in accordance with a determination that the first data does not exclusively correspond to a single sleep stage of the plurality of sleep stages, a second portion of the first indication is displayed at a second location of the sleep representation corresponding to the third sleep stage (e.g., a location corresponding to the fast-eye movement sleep stage). In some embodiments, if the first indication corresponds to a plurality of sleep stages, the first indication is displayed as a single graphical object spanning the plurality of stages of the sleep representation. In some embodiments, the first indication spans all sleep stages. In some embodiments, the first indication spans multiple but less than all sleep stages. In some embodiments, the first indication spans all sleep stages except the awake sleep stage. In some embodiments, the first indication has different visual characteristics than indications dedicated to other sub-periods corresponding to sleep stages. The first indication may differ in color, shape, size, transparency, or any combination thereof. In some embodiments, the first indication is displayed in grayscale.

In some embodiments, the computer system displays a sleep stage user interface (e.g., 620) that includes a comparison affordance (e.g., 634). In some embodiments, the sleep stage interface is displayed in response to selection of the affordance of the sleep interface. In some implementations, when the sleep stage user interface is displayed, the computer system detects a selection (e.g., 605 c) of the comparative affordance (e.g., a flick gesture) via one or more input devices. In some embodiments, in response to detecting selection of the comparative affordance, the computer system displays a comparison interface (e.g., 640) that includes a compressed sleep representation (e.g., 642) corresponding to the sleep representation (e.g., 622) and a first health metric chart (e.g., 644) corresponding to a first health metric (e.g., heart rate, respiration rate, or wrist temperature; not a sleep health metric). In some embodiments, the compressed sleep representation is a compressed sleep structure diagram. In some embodiments, the compressed sleep structure map is a sleep structure map displayed as a single column displayed as a function of time, wherein each sub-period is visually distinguished (e.g., by color) from adjacent sub-periods. In some embodiments, the compressed sleep representation and the health metric chart are aligned (e.g., aligned in time and/or graphically) (e.g., each of the compressed sleep representation and the health metric chart is displayed relative to a common time frame). In some embodiments, the comparison interface includes one or more time frame affordances that can be used to alter the time frames in which the compressed sleep representation and the representation of the health metric chart are displayed. In some embodiments, the comparison interface is displayed according to a particular time frame (e.g., day, week, month, 6 months). In some embodiments, the manner in which the comparison interface is displayed is based on the current time frame of the comparison interface. In some embodiments, when the comparison interface is displayed according to a non-daily time frame, the value corresponding to the compressed sleep representation and/or the health metric is displayed as an average of the time frames. Simultaneously displaying the compressed sleep representation and the first health metric chart corresponding to the sleep representation may provide visual feedback to the user regarding how the compressed sleep representation and the first health metric compare as a function of time, thereby providing improved visual feedback to the user.

In some implementations, the comparison interface includes a third affordance (e.g., any of affordances 646a, 646b, 646 c) corresponding to a first health metric (e.g., an affordance corresponding to a heart rate) and a fourth affordance (e.g., any of affordances 646a, 646b, 646 c) corresponding to a second health metric different from the first health metric (e.g., an affordance corresponding to a wrist temperature). In some embodiments, when the third affordance and the fourth affordance are displayed, the computer system detects a second user input (e.g., 605 d) via one or more input devices (e.g., a flick gesture on the first affordance or the second affordance). In some embodiments, when the third affordance and the fourth affordance are displayed, in response to detecting the second user input, in accordance with a determination that the second user input is a selection of the third affordance, the computer system maintains display of the first health metric chart. In some embodiments, when the third affordance and the fourth affordance are displayed, in response to detecting the second user input, in accordance with a determination that the second user input is a selection of the fourth affordance, the computer system displays a second health metric chart corresponding to the second health metric. In some embodiments, displaying the second health metric chart includes replacing the first health metric chart. In some embodiments, sleep applications may be used to view sleep data. For example, the sleep interface of the sleep application may include a data affordance that, when selected, causes the computer system to display sleep data. In some embodiments, the sleep data, when displayed, indicates for the sleep period the number of times each stage was experienced during the sleep period. In some embodiments, the sleep data also indicates the length of each time period that the sleep stage is experiencing, and optionally indicates the start time and end time of each time period. In some embodiments, the sleep stage interface includes an information affordance that, when selected, causes information describing each sleep stage to be displayed. Displaying a comparison interface that includes an affordance for the second health metric may enable a user to quickly and efficiently initiate display of different health metrics in the comparison interface without requiring further input to specify the type of health metric desired, thereby reducing the number of inputs required.

In some implementations, the one or more input devices include a wearable device (e.g., 601) (e.g., smart watch, biometric sensor). In some embodiments, the sleep data is received from a wearable device.

In some embodiments, the wearable device includes a display (e.g., 603). In some embodiments, the computer system displays a user interface (e.g., 690) including a sleep representation (e.g., 692) via a display generation component. In some embodiments, the user interface is a notification interface. In some embodiments, the notification interface is displayed in response to one or more detected events, such as completion of a sleep period. In some embodiments, the notification interface includes various sleep information including, but not limited to, a total duration of the sleep period, a time range of the sleep period (e.g., a start time and an end time of the sleep period), a sleep representation, and an indication of how many of the sleep period correspond to each of the plurality of sleep stages. In some embodiments, the user interface is a user interface of a sleep application on a wearable device. In some embodiments, the sleep interface includes one or more elements of the notification interface, and optionally one or more user-specific sleep parameters (e.g., pre-sleep schedule). In some embodiments, the sleep interface includes an analysis of recently completed sleep periods. In some embodiments, the computer system displays a sleep gadget for a sleep application in the main interface. In some embodiments, the sleep gadget indicates sleep data including a most recently completed sleep period of the sleep representation. In some embodiments, the sleep gadget indicates the total duration of the sleep period, and optionally whether sleep data is available for one or more sub-periods of the sleep period and/or the entire sleep period.

The foregoing description, for purposes of explanation, has been described with reference to specific embodiments. However, the illustrative discussions above are not intended to be exhaustive or to limit the invention to the precise forms disclosed. Many modifications and variations are possible in light of the above teaching. The embodiments were chosen and described in order to best explain the principles of the technology and its practical application. Those skilled in the art will be able to best utilize the techniques and various embodiments with various modifications as are suited to the particular use contemplated.

While the present disclosure and examples have been fully described with reference to the accompanying drawings, it is to be noted that various changes and modifications will become apparent to those skilled in the art. It should be understood that such variations and modifications are considered to be included within the scope of the disclosure and examples as defined by the claims.

As described above, one aspect of the present technology is to collect and use data from various sources to track and/or provide data corresponding to a user's sleep. The present disclosure contemplates that in some instances, such collected data may include personal information data that uniquely identifies or may be used to contact or locate a particular person. Such personal information data may include demographic data, location-based data, telephone numbers, email addresses, tweet IDs, home addresses, data or records related to the user's health or fitness level (e.g., vital sign measurements, medication information, exercise information), date of birth, or any other identification or personal information.

The present disclosure recognizes that the use of such personal information data in the present technology may be used to benefit users. For example, personal information data may be used to provide a sleep representation that classifies a user's sleep into various sleep stages. In addition, the present disclosure contemplates other uses for personal information data that are beneficial to the user. For example, health and fitness data may be used to provide insight into the overall health of a user, or may be used as positive feedback to individuals using technology to pursue health goals.

The present disclosure contemplates that entities responsible for the collection, analysis, disclosure, transmission, storage, or other use of such personal information data will adhere to sophisticated privacy policies and/or privacy measures. In particular, such entities should exercise and adhere to privacy policies and practices that are recognized as meeting or exceeding industry or government requirements for maintaining the privacy and security of personal information data. Such policies should be convenient for the user to access and should be updated as the collection and/or use of data changes. Personal information from users should be collected for legitimate and reasonable physical uses and must not be shared or sold outside of these legitimate uses. Further, such collection/sharing should be performed after receiving the user's informed consent. In addition, such entities should consider taking any necessary steps for protecting and securing access to such personal information data and ensuring that other entities having access to the personal information data adhere to their privacy policies and procedures. Furthermore, such entities may themselves be subject to third party evaluations to prove compliance with widely accepted privacy policies and practices. In addition, policies and practices should be adapted to the particular type of personal information data collected and/or accessed, and to applicable laws and standards including consideration of particular jurisdictions. For example, in the united states, the collection or acquisition of certain health data may be governed by federal and/or state law, such as the health insurance circulation and liability act (HIPAA), while health data in other countries may be subject to other regulations and policies and should be treated accordingly. Thus, different privacy measures should be claimed for different personal data types in each country.

Regardless of the foregoing, the present disclosure also contemplates embodiments in which a user selectively prevents use or access to personal information data. That is, the present disclosure contemplates hardware elements and/or software elements to prevent or block access to such personal information data. For example, with respect to sleep data captured by multiple devices, the present techniques may be configured to allow a user to choose to "opt-in" or "opt-out" to participate in the collection of personal information data during or at any time after registration with a service. In addition to providing the "opt-in" and "opt-out" options, the present disclosure contemplates providing notifications related to accessing or using personal information. For example, the user may be notified that his personal information data will be accessed when the application is downloaded, and then be reminded again just before the personal information data is accessed by the application.

Furthermore, it is intended that personal information data should be managed and processed in a manner that minimizes the risk of inadvertent or unauthorized access or use. Once the data is no longer needed, risk can be minimized by limiting data collection and data deletion. In addition, and when applicable, included in certain health-related applications, data de-identification may be used to protect the privacy of the user. De-identification may be facilitated by removing specific identifiers (e.g., date of birth, etc.), controlling the amount or specificity of stored data (e.g., collecting location data at a city level instead of at an address level), controlling how data is stored (e.g., aggregating data among users), and/or other methods, as appropriate.

Thus, while the present disclosure broadly covers the use of personal information data to implement one or more of the various disclosed embodiments, the present disclosure also contemplates that the various embodiments may be implemented without accessing such personal information data. That is, various embodiments of the present technology do not fail to function properly due to the lack of all or a portion of such personal information data. For example, sleep habits and/or sleep stages of a user's sleep may be determined based on non-personal information data or a minimum amount of personal information.

Claims

1. A method, comprising:

At a computer system in communication with a display generation component and one or more input devices:

receiving, from the one or more input devices, sleep data corresponding to a sleep period, wherein the sleep data includes first data corresponding to a first sub-period of the sleep period; and

Based on the sleep data, displaying, via the display generation component, a sleep representation that classifies the sleep period into a plurality of sleep stages, wherein displaying the sleep representation comprises displaying a first indication corresponding to the first sub-period of the sleep period, wherein the first indication:

In response to determining that the first data corresponds exclusively to a first sleep stage among the plurality of sleep stages, indicating that the first sub-period is a first type of sleep period corresponding to the first sleep stage; and

Based on determining that the first data does not exclusively correspond to a single sleep stage among the plurality of sleep stages, indicating that the first sub-period corresponds to at least a second sleep stage and a third sleep stage different from the second sleep stage among the plurality of sleep stages.

2. The method according to claim 1, further comprising:

Displayed via the display generation component:

a first affordance corresponding to said first sleep stage; and

a second affordance corresponding to said second sleep stage; and

When the first affordance and the second affordance are displayed:

detecting user input via the one or more input devices;

Based on determining that the user input is a selection of the first affordance, visually emphasizing a set of indicators of the sleep representation that correspond to the first sleep stage; and

Based on determining that the user input is a selection of the second affordance, a set of indicators of the sleep representation corresponding to the second sleep stage are visually emphasized.

3. The method according to claim 2, wherein:

visually emphasizing the set of indicators corresponding to the first sleep stage of the sleep representation includes visually de-emphasizing the set of indicators corresponding to the second sleep stage of the sleep representation; and

Visually emphasizing the set of indicators corresponding to the second sleep stage of the sleep representation includes visually de-emphasizing the set of indicators corresponding to the first sleep stage of the sleep representation.

4. The method according to any one of claims 2 to 3, wherein:

The first affordance indicates an amount corresponding to the first sleep stage of the sleep period; and

The second indicator indicates a quantity corresponding to the second sleep stage of the sleep period.

5. The method according to any one of claims 1 to 4, wherein determining that the first data corresponds exclusively to the first sleep stage comprises:

determining that the first data corresponding to the first sub-period of the sleep period corresponds partially to the first sleep stage and partially to a fourth sleep stage different from the first sleep stage; and

It is determined that the first data corresponding to the first sub-period of the sleep period primarily corresponds to the first sleep stage.

6. The method according to any one of claims 1 to 5, wherein:

The first indication includes a first part and a second part, and

Based on determining that the first data does not exclusively correspond to a single sleep stage of the plurality of sleep stages:

displaying the first portion of the first indication at a first location of the sleep representation corresponding to the second sleep stage; and

The second portion of the first indication is displayed at a second location of the sleep representation corresponding to the third sleep stage.

7. The method according to any one of claims 1 to 6, further comprising:

displaying a sleep stage user interface including a comparison affordance representation;

detecting, via the one or more input devices, a selection of the comparison affordance while displaying the sleep stages user interface; and

In response to detecting a selection of the comparison affordance, displaying a comparison interface, the comparison interface comprising:

a compressed sleep representation corresponding to the sleep representation; and

A first health metric graph corresponding to the first health metric.

8. The method according to claim 7, wherein:

The comparison interface includes:

a third affordance corresponding to said first health metric; and

a fourth affordance corresponding to a second health metric different from the first health metric, and

The method further comprises:

When the third indication and the fourth indication are displayed:

detecting a second user input via the one or more input devices; and

In response to detecting the second user input:

Based on determining that the second user input is a selection of the third affordance, maintaining display of the first health metric graph; and

Based on determining that the second user input is a selection of the fourth affordance, a second health metric chart corresponding to the second health metric is displayed.

9. The method according to any one of claims 1 to 8, wherein:

The one or more input devices include a wearable device, and

The sleep data is received from the wearable device.

10. The method of claim 9, wherein the wearable device comprises a display, the method further comprising:

A user interface including the sleep representation is displayed via the display generation component.

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

12. A computer system configured to communicate with a display generation component and one or more input devices, the computer system comprising:

one or more processors; and

A memory storing one or more programs, wherein 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 executing the method according to any one of claims 1 to 10.

13. A computer system configured to communicate with a display generation component and one or more input devices, the computer system comprising:

Device for carrying out the method according to any one of claims 1 to 10.

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

15. A non-transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of a computer system in communication with a display generation component and one or more input devices, the one or more programs comprising instructions for:

16. A computer system configured to communicate with a display generation component and one or more input devices, the computer system comprising:

one or more processors; and

A memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for:

17. A computer system configured to communicate with a display generation component and one or more input devices, the computer system comprising:

means for receiving sleep data corresponding to a sleep period from the one or more input devices, wherein the sleep data includes first data corresponding to a first sub-period of the sleep period; and

Means for displaying, via the display generation component, a sleep representation that categorizes the sleep period into a plurality of sleep stages based on the sleep data, wherein displaying the sleep representation comprises displaying a first indication corresponding to the first sub-period of the sleep period, wherein the first indication:

18. A computer program product, the computer program product comprising one or more programs configured to be executed by one or more processors of a computer system in communication with a display generation component and one or more input devices, the one or more programs comprising instructions for: