Patent Grant
12143784
The present disclosure relates generally to computer user interfaces, and more specifically to user interfaces and techniques for managing audio exposure.
An electronic device can be used to manage an amount of audio that is exposed to a user of the electronic device. Information concerning audio exposure can be presented to the user on the electronic device.
Some techniques for managing audio exposure using electronic devices, however, are generally cumbersome and inefficient. For example, some existing techniques use a complex and time-consuming user interface, which may include multiple key presses or keystrokes. Existing techniques require more time than necessary, wasting user time and device energy. This latter consideration is particularly important in battery-operated devices.
Accordingly, the present technique provides electronic devices with faster, more efficient methods and interfaces for managing audio exposure. Such methods and interfaces optionally complement or replace other methods for managing audio exposure. Such methods and interfaces reduce the cognitive burden on a user and produce a more efficient human-machine interface. For battery-operated computing devices, such methods and interfaces conserve power and increase the time between battery charges.
In accordance with some embodiments, a method performed at an electronic device including a display device is described. The method comprises: displaying, via the display device, a first user interface including a graphical object that varies in appearance based on a noise level; receiving first noise level data corresponding to a first noise level, the first noise level below a threshold noise level; in response to receiving the first noise level data, displaying the graphical object with an active portion of a first size based on the first noise data and in a first color; while maintaining display of the first user interface, receiving second noise level data corresponding to a second noise level different from the first noise level; and in response to receiving the second noise level data: displaying the active portion in a second size based on the second noise level that that is different from the first size; in accordance with a determination that the second noise level exceeds the threshold noise level, displaying the active portion in a second color different from the first color; and in accordance with a determination that the second noise level does not exceed the threshold noise level, maintaining display of the graphical object in the first color.
In accordance with some embodiments, a non-transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of an electronic device with a display device is described. The one or more programs include instructions for: displaying, via the display device, a first user interface including a graphical object that varies in appearance based on a noise level; receiving first noise level data corresponding to a first noise level, the first noise level below a threshold noise level; in response to receiving the first noise level data, displaying the graphical object with an active portion of a first size based on the first noise data and in a first color; while maintaining display of the first user interface, receiving second noise level data corresponding to a second noise level different from the first noise level; and in response to receiving the second noise level data: displaying the active portion in a second size based on the second noise level that that is different from the first size; in accordance with a determination that the second noise level exceeds the threshold noise level, displaying the active portion in a second color different from the first color; and in accordance with a determination that the second noise level does not exceed the threshold noise level, maintaining display of the graphical object in the first color.
In accordance with some embodiments, a transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of an electronic device with a display device is described. The one or more programs include instructions for: displaying, via the display device, a first user interface including a graphical object that varies in appearance based on a noise level; receiving first noise level data corresponding to a first noise level, the first noise level below a threshold noise level; in response to receiving the first noise level data, displaying the graphical object with an active portion of a first size based on the first noise data and in a first color; while maintaining display of the first user interface, receiving second noise level data corresponding to a second noise level different from the first noise level; and in response to receiving the second noise level data: displaying the active portion in a second size based on the second noise level that that is different from the first size; in accordance with a determination that the second noise level exceeds the threshold noise level, displaying the active portion in a second color different from the first color; and in accordance with a determination that the second noise level does not exceed the threshold noise level, maintaining display of the graphical object in the first color.
In accordance with some embodiments, an electronic device is described. The electronic device comprises a display device; one or more processors; and memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for: displaying, via the display device, a first user interface including a graphical object that varies in appearance based on a noise level; receiving first noise level data corresponding to a first noise level, the first noise level below a threshold noise level; in response to receiving the first noise level data, displaying the graphical object with an active portion of a first size based on the first noise data and in a first color; while maintaining display of the first user interface, receiving second noise level data corresponding to a second noise level different from the first noise level; and in response to receiving the second noise level data: displaying the active portion in a second size based on the second noise level that that is different from the first size; in accordance with a determination that the second noise level exceeds the threshold noise level, displaying the active portion in a second color different from the first color; and in accordance with a determination that the second noise level does not exceed the threshold noise level, maintaining display of the graphical object in the first color.
In accordance with some embodiments, an electronic device is described. The electronic device comprises a display device; means for displaying, via the display device, a first user interface including a graphical object that varies in appearance based on a noise level; means for receiving first noise level data corresponding to a first noise level, the first noise level below a threshold noise level; means for, in response to receiving the first noise level data, displaying the graphical object with an active portion of a first size based on the first noise data and in a first color; means for, while maintaining display of the first user interface, receiving second noise level data corresponding to a second noise level different from the first noise level; and means for, in response to receiving the second noise level data: displaying the active portion in a second size based on the second noise level that that is different from the first size; in accordance with a determination that the second noise level exceeds the threshold noise level, displaying the active portion in a second color different from the first color; and in accordance with a determination that the second noise level does not exceed the threshold noise level, maintaining display of the graphical object in the first color.
In accordance with some embodiments, a method performed at an electronic device including a display device and a touch sensitive surface is described. The method comprises: receiving: first noise level data attributable to a first device type; and second noise level data attributable to a second device type different from the first device type; displaying, via the display device, a first user interface, the first user interface including: a first representation of received noise level data that is based on the first noise level data and the second noise level data; and a first device type data filtering affordance; while displaying the first user interface, detecting a first user input corresponding to selection of the first device type data filtering affordance; and in response detecting the first user input, displaying a second representation of received noise level data that is based on the second noise level data and that is not based on the first noise level data.
In accordance with some embodiments, a non-transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of an electronic device with a display device and a touch sensitive surface is described. The one or more programs include instructions for: receiving: first noise level data attributable to a first device type; and second noise level data attributable to a second device type different from the first device type; displaying, via the display device, a first user interface, the first user interface including: a first representation of received noise level data that is based on the first noise level data and the second noise level data; and a first device type data filtering affordance; while displaying the first user interface, detecting a first user input corresponding to selection of the first device type data filtering affordance; and in response detecting the first user input, displaying a second representation of received noise level data that is based on the second noise level data and that is not based on the first noise level data.
In accordance with some embodiments, a transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of an electronic device with a display device and a touch sensitive surface is described. The one or more programs include instructions for: receiving: first noise level data attributable to a first device type; and second noise level data attributable to a second device type different from the first device type; displaying, via the display device, a first user interface, the first user interface including: a first representation of received noise level data that is based on the first noise level data and the second noise level data; and a first device type data filtering affordance; while displaying the first user interface, detecting a first user input corresponding to selection of the first device type data filtering affordance; and in response detecting the first user input, displaying a second representation of received noise level data that is based on the second noise level data and that is not based on the first noise level data.
In accordance with some embodiments, an electronic device is described. The electronic device comprises a display device; a touch sensitive surface; one or more processors; and 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: first noise level data attributable to a first device type; and second noise level data attributable to a second device type different from the first device type; displaying, via the display device, a first user interface, the first user interface including: a first representation of received noise level data that is based on the first noise level data and the second noise level data; and a first device type data filtering affordance; while displaying the first user interface, detecting a first user input corresponding to selection of the first device type data filtering affordance; and in response detecting the first user input, displaying a second representation of received noise level data that is based on the second noise level data and that is not based on the first noise level data.
In accordance with some embodiments, an electronic device is described. The electronic device comprises a display device; a touch sensitive surface; means for receiving: first noise level data attributable to a first device type; and second noise level data attributable to a second device type different from the first device type; means for displaying, via the display device, a first user interface, the first user interface including: a first representation of received noise level data that is based on the first noise level data and the second noise level data; and a first device type data filtering affordance; means for, while displaying the first user interface, detecting a first user input corresponding to selection of the first device type data filtering affordance; and means for, in response detecting the first user input, displaying a second representation of received noise level data that is based on the second noise level data and that is not based on the first noise level data.
In accordance with some embodiments, a method performed at a computer system that is in communication with a display generation component, an audio generation component, and one or more input devices is described. The method comprises: displaying, via the display generation component, an audio preference interface, including concurrently displaying: a representation of a first audio sample, wherein the first audio sample has a first set of audio characteristics; and a representation of a second audio sample, wherein the second audio sample has a second set of audio characteristics that is different from the first set of audio characteristics; while displaying the audio preference interface: outputting, via the audio generation component, at least a portion of the first audio sample; and receiving, via the one or more input devices, a set of one or more user inputs; and after receiving the set of one or more inputs: recording a selection of the first audio sample as a preferred sample or a selection of the second audio sample as a preferred sample; and outputting, via the audio generation component, a first audio data, wherein: in accordance with the first audio sample having been recorded as the preferred sample, the output of the first audio data is based on at least one audio characteristic of the first set of audio characteristics; and in accordance with the second audio sample having been recorded as the preferred sample, the output of the first audio data is based on at least one audio characteristic of the second set of audio characteristics.
In accordance with some embodiments, 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 that is in communication with a display generation component, an audio generation component, and one or more input devices is described. The one or more programs include instructions for: displaying, via the display generation component, an audio preference interface, including concurrently displaying: a representation of a first audio sample, wherein the first audio sample has a first set of audio characteristics; and a representation of a second audio sample, wherein the second audio sample has a second set of audio characteristics that is different from the first set of audio characteristics; while displaying the audio preference interface: outputting, via the audio generation component, at least a portion of the first audio sample; and receiving, via the one or more input devices, a set of one or more user inputs; and after receiving the set of one or more inputs: recording a selection of the first audio sample as a preferred sample or a selection of the second audio sample as a preferred sample; and outputting, via the audio generation component, a first audio data, wherein: in accordance with the first audio sample having been recorded as the preferred sample, the output of the first audio data is based on at least one audio characteristic of the first set of audio characteristics; and in accordance with the second audio sample having been recorded as the preferred sample, the output of the first audio data is based on at least one audio characteristic of the second set of audio characteristics.
In accordance with some embodiments, a transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of a computer system that is in communication with a display generation component, an audio generation component, and one or more input devices is described. The one or more programs include instructions for: displaying, via the display generation component, an audio preference interface, including concurrently displaying: a representation of a first audio sample, wherein the first audio sample has a first set of audio characteristics; and a representation of a second audio sample, wherein the second audio sample has a second set of audio characteristics that is different from the first set of audio characteristics; while displaying the audio preference interface: outputting, via the audio generation component, at least a portion of the first audio sample; and receiving, via the one or more input devices, a set of one or more user inputs; and after receiving the set of one or more inputs: recording a selection of the first audio sample as a preferred sample or a selection of the second audio sample as a preferred sample; and outputting, via the audio generation component, a first audio data, wherein: in accordance with the first audio sample having been recorded as the preferred sample, the output of the first audio data is based on at least one audio characteristic of the first set of audio characteristics; and in accordance with the second audio sample having been recorded as the preferred sample, the output of the first audio data is based on at least one audio characteristic of the second set of audio characteristics.
In accordance with some embodiments, a computer system that is in communication with a display generation component, an audio generation component, and one or more input devices is described. The computer system that is in communication with a display generation component, an audio generation component, and one or more input devices comprises: means for displaying, via the display generation component, an audio preference interface, including concurrently displaying: a representation of a first audio sample, wherein the first audio sample has a first set of audio characteristics; and a representation of a second audio sample, wherein the second audio sample has a second set of audio characteristics that is different from the first set of audio characteristics; means for, while displaying the audio preference interface: outputting, via the audio generation component, at least a portion of the first audio sample; and receiving, via the one or more input devices, a set of one or more user inputs; and means for, after receiving the set of one or more inputs: recording a selection of the first audio sample as a preferred sample or a selection of the second audio sample as a preferred sample; and outputting, via the audio generation component, a first audio data, wherein: in accordance with the first audio sample having been recorded as the preferred sample, the output of the first audio data is based on at least one audio characteristic of the first set of audio characteristics; and in accordance with the second audio sample having been recorded as the preferred sample, the output of the first audio data is based on at least one audio characteristic of the second set of audio characteristics.
In accordance with some embodiments, a method performed at a computer system that is in communication with an audio generation component is described. The method comprises: while causing, via the audio generation component, output of audio data at a first volume, detecting that an audio exposure threshold criteria has been met; and in response to detecting that the audio exposure threshold criteria has been met: while continuing to cause output of audio data, reducing the volume of output of audio data to a second volume, lower than the first volume.
In accordance with some embodiments, 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 that is in communication with an audio generation component is described. The one or more programs include instructions for: while causing, via the audio generation component, output of audio data at a first volume, detecting that an audio exposure threshold criteria has been met; and in response to detecting that the audio exposure threshold criteria has been met: while continuing to cause output of audio data, reducing the volume of output of audio data to a second volume, lower than the first volume.
In accordance with some embodiments, a transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of a computer system that is in communication with an audio generation component is described. The one or more programs include instructions for: while causing, via the audio generation component, output of audio data at a first volume, detecting that an audio exposure threshold criteria has been met; and in response to detecting that the audio exposure threshold criteria has been met: while continuing to cause output of audio data, reducing the volume of output of audio data to a second volume, lower than the first volume.
In accordance with some embodiments, a computer system that is in communication with an audio generation component is described. The computer system that is in communication with an audio generation component comprises one or more processors, and memory storing one or more programs configured to be executed by the one or more processors. The one or more programs include instructions for: while causing, via the audio generation component, output of audio data at a first volume, detecting that an audio exposure threshold criteria has been met; and in response to detecting that the audio exposure threshold criteria has been met: while continuing to cause output of audio data, reducing the volume of output of audio data to a second volume, lower than the first volume.
In accordance with some embodiments, a computer system is described. The computer system comprises a display generation component; an audio generation component; one or more input devices; means for, while causing, via the audio generation component, output of audio data at a first volume, detecting that an audio exposure threshold criteria has been met; and means for, in response to detecting that the audio exposure threshold criteria has been met: while continuing to cause output of audio data, reducing the volume of output of audio data to a second volume, lower than the first volume.
In accordance with some embodiments, a method performed at a computer system that is in communication with a display generation component and one or more input devices is described. The method comprises: receiving, via the one or more input devices, an input corresponding to a request to display audio exposure data; and in response to receiving the input corresponding to the request to display audio exposure data, displaying, via the display generation component, an audio exposure interface including, concurrently displaying: an indication of audio exposure data over a first period of time; and a first visual indication of a first alert provided as a result of a first audio exposure value exceeding an audio exposure threshold, the first visual indication of the first alert including an indication of a time at which the first alert was provided.
In accordance with some embodiments, 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 is described. The one or more programs include instructions for: receiving, via the one or more input devices, an input corresponding to a request to display audio exposure data; and in response to receiving the input corresponding to the request to display audio exposure data, displaying, via the display generation component, an audio exposure interface including, concurrently displaying: an indication of audio exposure data over a first period of time; and a first visual indication of a first alert provided as a result of a first audio exposure value exceeding an audio exposure threshold, the first visual indication of the first alert including an indication of a time at which the first alert was provided.
In accordance with some embodiments, a 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 is described. The one or more programs include instructions for: receiving, via the one or more input devices, an input corresponding to a request to display audio exposure data; and in response to receiving the input corresponding to the request to display audio exposure data, displaying, via the display generation component, an audio exposure interface including, concurrently displaying: an indication of audio exposure data over a first period of time; and a first visual indication of a first alert provided as a result of a first audio exposure value exceeding an audio exposure threshold, the first visual indication of the first alert including an indication of a time at which the first alert was provided.
In accordance with some embodiments, a computer system in communication with a display generation component and one or more input devices is described. The computer system in communication with a display generation component and one or more input devices comprises one or more processors, and memory storing one or more programs configured to be executed by the one or more processors. The one or more programs include instructions for: receiving, via the one or more input devices, an input corresponding to a request to display audio exposure data; and in response to receiving the input corresponding to the request to display audio exposure data, displaying, via the display generation component, an audio exposure interface including, concurrently displaying: an indication of audio exposure data over a first period of time; and a first visual indication of a first alert provided as a result of a first audio exposure value exceeding an audio exposure threshold, the first visual indication of the first alert including an indication of a time at which the first alert was provided.
In accordance with some embodiments, a computer system in communication with a display generation component and one or more input devices is described. The computer system in communication with a display generation component and one or more input devices comprises means for receiving, via the one or more input devices, an input corresponding to a request to display audio exposure data; and means for, in response to receiving the input corresponding to the request to display audio exposure data, displaying, via the display generation component, an audio exposure interface including, concurrently displaying: an indication of audio exposure data over a first period of time; and a first visual indication of a first alert provided as a result of a first audio exposure value exceeding an audio exposure threshold, the first visual indication of the first alert including an indication of a time at which the first alert was provided.
In accordance with some embodiments, a method performed at a computer system that is in communication with an audio generation component is described. The method comprises: receiving output audio data associated with output audio generated using the audio generation component, the output audio comprising a first audio signal and a second audio signal, the output audio data including a first anticipated output audio volume for the first audio signal and a second anticipated output audio volume for the second audio signal; in accordance with a determination that the output audio data satisfies a first set of criteria, wherein the first set of criteria is satisfied when the first anticipated output audio volume for the first audio signal exceeds an output audio volume threshold: causing output of the first audio signal at a reduced output audio volume that is below the first anticipated output audio volume; and causing output of the second audio signal at the second anticipated output audio volume; and in accordance with a determination that the output audio data does not satisfy the first set of criteria: causing output of the first audio signal at the first anticipated output audio volume; and causing output of the second audio signal at the second anticipated output audio volume.
In accordance with some embodiments, 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 that is in communication with an audio generation component is described. The one or more programs include instructions for: receiving output audio data associated with output audio generated using the audio generation component, the output audio comprising a first audio signal and a second audio signal, the output audio data including a first anticipated output audio volume for the first audio signal and a second anticipated output audio volume for the second audio signal; in accordance with a determination that the output audio data satisfies a first set of criteria, wherein the first set of criteria is satisfied when the first anticipated output audio volume for the first audio signal exceeds an output audio volume threshold: causing output of the first audio signal at a reduced output audio volume that is below the first anticipated output audio volume; and causing output of the second audio signal at the second anticipated output audio volume; and in accordance with a determination that the output audio data does not satisfy the first set of criteria: causing output of the first audio signal at the first anticipated output audio volume; and causing output of the second audio signal at the second anticipated output audio volume.
In accordance with some embodiments, a transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of a computer system that is in communication with an audio generation component is described. The one or more programs include instructions for: receiving output audio data associated with output audio generated using the audio generation component, the output audio comprising a first audio signal and a second audio signal, the output audio data including a first anticipated output audio volume for the first audio signal and a second anticipated output audio volume for the second audio signal; in accordance with a determination that the output audio data satisfies a first set of criteria, wherein the first set of criteria is satisfied when the first anticipated output audio volume for the first audio signal exceeds an output audio volume threshold: causing output of the first audio signal at a reduced output audio volume that is below the first anticipated output audio volume; and causing output of the second audio signal at the second anticipated output audio volume; and in accordance with a determination that the output audio data does not satisfy the first set of criteria: causing output of the first audio signal at the first anticipated output audio volume; and causing output of the second audio signal at the second anticipated output audio volume.
In accordance with some embodiments, a computer system that is in communication with an audio generation component is described. The computer system that is in communication with an audio generation component comprises one or more processors, and memory storing one or more programs configured to be executed by the one or more processors. The one or more programs include instructions for: receiving output audio data associated with output audio generated using the audio generation component, the output audio comprising a first audio signal and a second audio signal, the output audio data including a first anticipated output audio volume for the first audio signal and a second anticipated output audio volume for the second audio signal; in accordance with a determination that the output audio data satisfies a first set of criteria, wherein the first set of criteria is satisfied when the first anticipated output audio volume for the first audio signal exceeds an output audio volume threshold: causing output of the first audio signal at a reduced output audio volume that is below the first anticipated output audio volume; and causing output of the second audio signal at the second anticipated output audio volume; and in accordance with a determination that the output audio data does not satisfy the first set of criteria: causing output of the first audio signal at the first anticipated output audio volume; and causing output of the second audio signal at the second anticipated output audio volume.
In accordance with some embodiments, a computer system that is in communication with an audio generation component is described. The computer system that is in communication with an audio generation component comprises: means for receiving output audio data associated with output audio generated using the audio generation component, the output audio comprising a first audio signal and a second audio signal, the output audio data including a first anticipated output audio volume for the first audio signal and a second anticipated output audio volume for the second audio signal; means for in accordance with a determination that the output audio data satisfies a first set of criteria, wherein the first set of criteria is satisfied when the first anticipated output audio volume for the first audio signal exceeds an output audio volume threshold: causing output of the first audio signal at a reduced output audio volume that is below the first anticipated output audio volume; and causing output of the second audio signal at the second anticipated output audio volume; and means for in accordance with a determination that the output audio data does not satisfy the first set of criteria: causing output of the first audio signal at the first anticipated output audio volume; and causing output of the second audio signal at the second anticipated output audio volume.
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, devices are provided with faster, more efficient methods and interfaces for managing audio exposure, thereby increasing the effectiveness, efficiency, and user satisfaction with such devices. Such methods and interfaces may complement or replace other methods for managing audio exposure.
For a better understanding of the various described embodiments, reference should be made to the Description of Embodiments below, in conjunction with the following drawings in which like reference numerals refer to corresponding parts throughout the figures.
The following description sets forth exemplary methods, parameters, and the like. It should be recognized, however, 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.
In some implementations, an example electronic device provides efficient methods and interfaces for managing audio exposure. For example, the example electronic device can provide a user with information about the level of noise the user is exposed to in an easily understandable and convenient manner. In another example, the example electronic device can effectively alert the user of the electronic device when the noise level that the user is exposed to exceeds a certain threshold level. In another example, the example electronic device can customize audio settings based on a user's preferences. In another example, the example electronic device can provide a user with information about the amount of audio the user is exposed to in an easily understandable and convenient manner. In another example, the example electronic device can effectively alert the user of the electronic device when the amount of audio that the user is exposed to exceeds a certain threshold level. In another example, the example electronic device can effectively adjust the amount of audio that the user is exposed to in order to protect the health of the user's auditory system. Such techniques of the example electronic device can reduce the cognitive burden on a user who monitors noise exposure levels, thereby enhancing productivity. Further, such techniques can reduce processor and battery power otherwise wasted on redundant user inputs.
Although the following description uses terms “first,” “second,” etc. to describe various elements, these elements should not be limited by the terms. These terms are only used to distinguish one element from another. For example, a first touch could be termed a second touch, and, similarly, a second touch could be termed a first touch, without departing from the scope of the various described embodiments. The first touch and the second touch are both 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 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 “includes,” “including,” “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, construed to mean “when” or “upon” or “in response to determining” or “in response to detecting,” depending on the context. Similarly, the phrase “if it is determined” or “if [a stated condition or event] is detected” is, optionally, construed to mean “upon determining” or “in response to determining” or “upon detecting [the stated condition or event]” or “in response to detecting [the 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. In some embodiments, the device is a portable communications device, such as a mobile telephone, that also contains other functions, such as PDA and/or music player functions. Exemplary embodiments of portable multifunction devices include, without limitation, the iPhone®, iPod Touch®, and iPad® devices from Apple Inc. of Cupertino, California Other portable electronic devices, such as laptops or tablet computers with touch-sensitive surfaces (e.g., touch screen displays and/or touchpads), are, optionally, used. It should also be understood that, in some embodiments, the device is not a portable communications device, but is a desktop computer with a touch-sensitive surface (e.g., a touch screen display and/or a touchpad). In some embodiments, the electronic device is a computer system that is in communication (e.g., via wireless communication, via wired communication) with a 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 causing to display the content (e.g., video data rendered or decoded by display controller 156) by transmitting, via a wired or wireless connection, data (e.g., image data or video data) to an integrated or external display generation component to visually produce the content.
In the discussion that follows, an electronic device that includes a display and a touch-sensitive surface is described. It should be understood, however, that the electronic device optionally includes one or more other physical user-interface devices, such as a physical keyboard, a mouse, and/or a joystick.
The device typically supports a variety of applications, such as one or more of the following: a drawing application, a presentation application, a word processing application, a website creation application, a disk authoring application, a spreadsheet application, a gaming application, a telephone application, a video conferencing application, an e-mail application, an instant messaging application, a workout support application, a photo management application, a digital camera application, a digital video camera application, a web browsing application, a digital music player application, and/or a digital video player application.
The various applications that are executed on the device optionally use at least one common physical user-interface device, such as the touch-sensitive surface. One or more functions of the touch-sensitive surface as well as corresponding information displayed on the device are, optionally, adjusted and/or varied from one application to the next and/or within a respective application. In this way, a common physical architecture (such as the touch-sensitive surface) of the device optionally supports the variety of applications with user interfaces that are intuitive and transparent to the user.
Attention is now directed toward embodiments of portable devices with touch-sensitive displays.
As used in the specification and claims, the term “intensity” of a contact on a touch-sensitive surface refers to the force or pressure (force per unit area) of a contact (e.g., a finger contact) on the touch-sensitive surface, or to a substitute (proxy) for the force or pressure of a contact on the touch-sensitive surface. The intensity of a contact has a range of values that includes at least four distinct values and more typically includes hundreds of distinct values (e.g., at least 256). Intensity of a contact is, optionally, determined (or measured) using various approaches and various sensors or combinations of sensors. For example, one or more force sensors underneath or adjacent to the touch-sensitive surface are, optionally, used to measure force at various points on the touch-sensitive surface. In some implementations, force measurements from multiple force sensors are combined (e.g., a weighted average) to determine an estimated force of a contact. Similarly, a pressure-sensitive tip of a stylus is, optionally, used to determine a pressure of the stylus on the touch-sensitive surface. Alternatively, the size of the contact area detected on the touch-sensitive surface and/or changes thereto, the capacitance of the touch-sensitive surface proximate to the contact and/or changes thereto, and/or the resistance of the touch-sensitive surface proximate to the contact and/or changes thereto are, optionally, used as a substitute for the force or pressure of the contact on the touch-sensitive surface. In some implementations, the substitute measurements for contact force or pressure are used directly to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is described in units corresponding to the substitute measurements). In some implementations, the substitute measurements for 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). Using the intensity of a contact as an attribute of a user input allows for user access to additional device functionality that may otherwise not be accessible by the user on a reduced-size device with limited real estate for displaying affordances (e.g., on a touch-sensitive display) and/or receiving user input (e.g., via a touch-sensitive display, a touch-sensitive surface, or a physical/mechanical control such as a knob or a button).
As used in the specification and claims, the term “tactile output” refers to physical displacement of a device relative to a previous position of the device, physical displacement of a component (e.g., a touch-sensitive surface) of a device relative to another component (e.g., housing) of the device, or displacement of the component relative to a center of mass of the device that will be detected by a user with the user's sense of touch. For example, in situations where the device or the component of the device is in contact with a surface of a user that is sensitive to touch (e.g., a finger, palm, or other part of a user's hand), the tactile output generated by the physical displacement will be interpreted by the user as a tactile sensation corresponding to a perceived change in physical characteristics of the device or the component of the device. For example, movement of a touch-sensitive surface (e.g., a touch-sensitive display or trackpad) is, optionally, interpreted by the user as a “down click” or “up click” of a physical actuator button. In some cases, a user will feel a tactile sensation such as an “down click” or “up click” even when there is no movement of a physical actuator button associated with the touch-sensitive surface that is physically pressed (e.g., displaced) by the user's movements. As another example, movement of the touch-sensitive surface is, optionally, interpreted or sensed by the user as “roughness” of the touch-sensitive surface, even when there is no change in smoothness of the touch-sensitive surface. While such interpretations of touch by a user will be subject to the individualized sensory perceptions of the user, there are many sensory perceptions of touch that are common to a large majority of users. Thus, when a tactile output is described as corresponding to a particular sensory perception of a user (e.g., an “up click,” a “down click,” “roughness”), unless otherwise stated, the generated tactile output corresponds to physical displacement of the device or a component thereof that will generate the described sensory perception for a typical (or average) user.
It should be appreciated that device 100 is only one example of a portable multifunction device, and that device 100 optionally has more or fewer components than shown, optionally combines two or more components, or optionally has a different configuration or arrangement of the components. The various components shown in
Memory 102 optionally includes high-speed random access memory and optionally also 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.
Peripherals interface 118 can 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 and/or sets of instructions stored in memory 102 to perform various functions for device 100 and to process data. In some embodiments, peripherals 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.
RF (radio frequency) circuitry 108 receives and sends RF signals, also called electromagnetic signals. RF circuitry 108 converts electrical signals to/from electromagnetic signals and communicates with communications networks and other communications devices via the 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 optionally communicates with networks, such as the Internet, also referred to as the World Wide Web (WWW), an intranet and/or a wireless network, such as a cellular telephone network, a wireless local area network (LAN) and/or a metropolitan area network (MAN), and other devices by wireless communication. The RF circuitry 108 optionally includes well-known circuitry for detecting near field communication (NFC) fields, such as by a short-range communication radio. The wireless communication optionally uses any of a plurality of communications standards, protocols, and technologies, including but not limited to Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), high-speed downlink packet access (HSDPA), high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO), HSPA, HSPA+, Dual-Cell HSPA (DC-HSPDA), long term evolution (LTE), near field communication (NFC), wideband code division multiple access (W-CDMA), code division multiple access (CDMA), time division multiple access (TDMA), Bluetooth, Bluetooth Low Energy (BTLE), Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11n, and/or IEEE 802.11ac), voice over Internet Protocol (VoIP), Wi-MAX, a protocol for e-mail (e.g., Internet message access protocol (IMAP) and/or post office protocol (POP)), instant messaging (e.g., extensible messaging and presence protocol (XMPP), Session Initiation Protocol for Instant Messaging and Presence Leveraging Extensions (SIMPLE), Instant Messaging and Presence Service (IMPS)), and/or Short Message Service (SMS), or any other suitable communication protocol, including communication protocols not yet developed as of the filing date of this document.
Audio circuitry 110, speaker 111, and microphone 113 provide an audio interface between a user and device 100. Audio circuitry 110 receives audio data from peripherals interface 118, converts the audio data to an electrical signal, and transmits the electrical signal to speaker 111. Speaker 111 converts the electrical signal to human-audible sound waves. Audio circuitry 110 also receives electrical signals converted by microphone 113 from sound waves. Audio circuitry 110 converts the electrical signal to audio data and transmits the audio data to peripherals interface 118 for processing. Audio data is, optionally, retrieved from and/or transmitted to memory 102 and/or RF circuitry 108 by peripherals interface 118. In some embodiments, audio circuitry 110 also includes a headset jack (e.g., 212,
I/O subsystem 106 couples input/output peripherals on device 100, such as touch screen 112 and other input control devices 116, to peripherals interface 118. I/O subsystem 106 optionally includes display controller 156, optical sensor controller 158, depth camera controller 169, intensity sensor controller 159, 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/send electrical signals from/to other input control devices 116. The other input control devices 116 optionally include physical buttons (e.g., push buttons, rocker buttons), dials, slider switches, joysticks, click wheels, and so forth. In some embodiments, input controller(s) 160 are, optionally, coupled to any (or none) of the following: a keyboard, an infrared port, a USB port, and a pointer device such as a mouse. The one or more buttons (e.g., 208,
A quick press of the push button optionally disengages a lock of touch screen 112 or optionally begins a process that uses gestures on the touch screen to unlock the device, as described in U.S. patent application Ser. No. 11/322,549, “Unlocking a Device by Performing Gestures on an Unlock Image,” filed Dec. 23, 2005, U.S. Pat. No. 7,657,849, which is hereby incorporated by reference in its entirety. A longer press of the push button (e.g., 206) optionally turns power to device 100 on or off. The functionality of one or more of the buttons are, optionally, user-customizable. Touch screen 112 is used to implement virtual or soft buttons and one or more soft keyboards.
Touch-sensitive display 112 provides an input interface and an output interface between the device and a user. Display controller 156 receives and/or sends electrical signals from/to touch screen 112. Touch screen 112 displays visual output to the user. The visual output optionally includes graphics, text, icons, video, and any combination thereof (collectively termed “graphics”). In some embodiments, some or all of the visual output optionally corresponds to user-interface objects.
Touch screen 112 has a touch-sensitive surface, sensor, or set of sensors that accepts input from the 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 breaking of the contact) on touch screen 112 and convert the detected contact into interaction with user-interface objects (e.g., one or more soft keys, icons, web pages, or images) that are displayed on touch screen 112. In an exemplary embodiment, a point of contact between touch screen 112 and the user corresponds to a finger of the user.
Touch screen 112 optionally uses LCD (liquid crystal display) technology, LPD (light emitting polymer display) technology, or LED (light emitting diode) technology, although other display technologies are used in other embodiments. Touch screen 112 and display controller 156 optionally detect contact and any movement or breaking thereof using any of a plurality 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, projected mutual capacitance sensing technology is used, such as that found in the iPhone® and iPod Touch® from Apple Inc. of Cupertino, California.
A touch-sensitive display in some embodiments of touch screen 112 is, optionally, analogous to the multi-touch sensitive touchpads described in the following U.S. Pat. No. 6,323,846 (Westerman et al.), U.S. Pat. No. 6,570,557 (Westerman et al.), and/or U.S. Pat. No. 6,677,932 (Westerman), 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, whereas touch-sensitive touchpads do not provide visual output.
A touch-sensitive display in some embodiments of touch screen 112 is described in the following applications: (1) U.S. patent application Ser. No. 11/381,313, “Multipoint Touch Surface Controller,” filed May 2, 2006; (2) U.S. patent application Ser. No. 10/840,862, “Multipoint Touchscreen,” filed May 6, 2004; (3) U.S. patent application Ser. No. 10/903,964, “Gestures For Touch Sensitive Input Devices,” filed Jul. 30, 2004; (4) U.S. patent application Ser. No. 11/048,264, “Gestures For Touch Sensitive Input Devices,” filed Jan. 31, 2005; (5) U.S. patent application Ser. No. 11/038,590, “Mode-Based Graphical User Interfaces For Touch Sensitive Input Devices,” filed Jan. 18, 2005; (6) U.S. patent application Ser. No. 11/228,758, “Virtual Input Device Placement On A Touch Screen User Interface,” filed Sep. 16, 2005; (7) U.S. patent application Ser. No. 11/228,700, “Operation Of A Computer With A Touch Screen Interface,” filed Sep. 16, 2005; (8) U.S. patent application Ser. No. 11/228,737, “Activating Virtual Keys Of A Touch-Screen Virtual Keyboard,” filed Sep. 16, 2005; and (9) U.S. patent application Ser. No. 11/367,749, “Multi-Functional Hand-Held Device,” filed Mar. 3, 2006. 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 embodiments, the touch screen has a video resolution of approximately 160 dpi. The user optionally makes contact with touch screen 112 using any suitable object or appendage, such as a stylus, a finger, and so forth. In some embodiments, the user interface is designed to work primarily with finger-based contacts and gestures, which can be less precise than stylus-based input due to the larger area of contact of a finger on the touch screen. In some embodiments, the device translates the rough finger-based input into a precise pointer/cursor position or command for performing the actions desired by the user.
In some embodiments, in addition to the touch screen, device 100 optionally includes a touchpad for activating or deactivating particular functions. In some embodiments, the touchpad is a touch-sensitive area of the device that, unlike the touch screen, does not display visual output. The touchpad is, optionally, a touch-sensitive surface that is separate from touch screen 112 or an extension of the touch-sensitive surface formed by the touch screen.
Device 100 also includes power system 162 for powering the various components. 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., a light-emitting diode (LED)) and any other components associated with the generation, management and distribution of power in portable devices.
Device 100 optionally also includes one or more optical sensors 164.
Device 100 optionally also includes one or more depth camera sensors 175.
Device 100 optionally also includes one or more contact intensity sensors 165.
Device 100 optionally also includes one or more proximity sensors 166.
Device 100 optionally also includes one or more tactile output generators 167.
Device 100 optionally also includes one or more accelerometers 168.
In some embodiments, the software components stored in memory 102 include operating system 126, communication module (or set of instructions) 128, contact/motion module (or set of instructions) 130, graphics module (or set of instructions) 132, text input module (or set of instructions) 134, Global Positioning System (GPS) module (or set of instructions) 135, and applications (or sets of instructions) 136. Furthermore, in some embodiments, memory 102 (
Operating system 126 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, iOS, WINDOWS, or an embedded operating system such as VxWorks) includes various software components and/or drivers for controlling and managing general system tasks (e.g., memory management, storage device control, power management, etc.) and facilitates communication between various hardware and software components.
Communication module 128 facilitates communication with other devices over one or more external ports 124 and also includes various software components for handling data received by RF circuitry 108 and/or external port 124. External port 124 (e.g., Universal Serial Bus (USB), FIREWIRE, etc.) is adapted for coupling directly to other devices or indirectly over a network (e.g., the Internet, wireless LAN, etc.). In some embodiments, the external port is a multi-pin (e.g., 30-pin) connector that is the same as, or similar to and/or compatible with, the 30-pin connector used on iPod® (trademark of Apple Inc.) devices.
Contact/motion module 130 optionally detects contact with touch screen 112 (in conjunction with display controller 156) and other touch-sensitive devices (e.g., a touchpad or physical click wheel). Contact/motion module 130 includes various software components for performing various operations related to detection of contact, such as determining if contact has occurred (e.g., detecting a finger-down event), determining an intensity of the contact (e.g., the force or pressure of the contact or a substitute for the force or pressure of the contact), determining if there is movement of the contact and tracking the movement across the touch-sensitive surface (e.g., detecting one or more finger-dragging events), and determining if the contact has ceased (e.g., detecting a finger-up event or a break in contact). Contact/motion module 130 receives contact data from the touch-sensitive surface. Determining movement of the point of contact, which is represented by a series of contact data, optionally includes determining speed (magnitude), velocity (magnitude and direction), and/or an acceleration (a change in magnitude and/or direction) of the point of contact. These operations are, optionally, applied to single contacts (e.g., one finger contacts) or to multiple simultaneous contacts (e.g., “multitouch”/multiple finger contacts). In some embodiments, contact/motion module 130 and display controller 156 detect contact on a touchpad.
In some embodiments, contact/motion module 130 uses a set of one or more intensity thresholds to determine whether an operation has been performed by a user (e.g., to determine whether a user has “clicked” on an icon). In some embodiments, at least a subset of the intensity thresholds are determined in accordance with software parameters (e.g., the intensity thresholds are not determined by the activation thresholds of particular physical actuators and can be adjusted without changing the physical hardware of device 100). For example, a mouse “click” threshold of a trackpad or touch screen display can be set to any of a large range of predefined threshold values without changing the trackpad or touch screen display hardware. Additionally, in some implementations, a user of the device is provided with software settings for adjusting one or more of the set of intensity thresholds (e.g., by adjusting individual intensity thresholds and/or by adjusting a plurality of intensity thresholds at once with a system-level click “intensity” parameter).
Contact/motion module 130 optionally detects a gesture input by a user. Different gestures on the touch-sensitive surface have different contact patterns (e.g., different motions, timings, and/or intensities of detected contacts). Thus, a gesture is, optionally, detected by detecting a particular contact pattern. For example, detecting a finger tap gesture includes detecting a finger-down event followed by detecting a finger-up (liftoff) event at the same position (or substantially the same position) as the finger-down event (e.g., at the position of an icon). As another example, detecting a finger swipe gesture on the touch-sensitive surface includes detecting a finger-down event followed by detecting one or more finger-dragging events, and subsequently followed by detecting a finger-up (liftoff) 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 property) of graphics that are displayed. As used herein, the term “graphics” includes any object that can be displayed to a user, including, without limitation, text, web pages, icons (such as user-interface objects including soft keys), digital images, videos, animations, and the like.
In some embodiments, graphics module 132 stores data representing graphics to be used. Each graphic is, optionally, assigned a corresponding code. Graphics module 132 receives, from applications etc., one or more codes specifying graphics to be displayed along with, if necessary, coordinate data and other graphic property data, and then generates screen image data to output to display controller 156.
Haptic feedback module 133 includes various software components for generating instructions used by tactile output generator(s) 167 to produce tactile outputs at one or more locations on device 100 in response to user interactions with device 100.
Text input module 134, which is, optionally, a component of graphics module 132, provides soft keyboards for entering text in various applications (e.g., contacts 137, e-mail 140, IM 141, browser 147, and any other application that needs text input).
GPS module 135 determines the location of the device and provides this information for use in various applications (e.g., to telephone 138 for use in location-based dialing; to camera 143 as picture/video metadata; and to applications that provide location-based services such as weather widgets, local yellow page widgets, and map/navigation widgets).
Applications 136 optionally include the following modules (or sets of instructions), or a subset or superset thereof:
Examples of other applications 136 that are, 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 are, optionally, used to manage an address book or contact list (e.g., stored in application internal state 192 of contacts module 137 in memory 102 or memory 370), including: adding name(s) to the address book; deleting name(s) from the address book; associating telephone number(s), e-mail address(es), physical address(es) or other information with a name; associating an image with a name; categorizing and sorting names; providing telephone numbers or e-mail addresses to initiate and/or facilitate communications by telephone 138, video conference module 139, e-mail 140, or IM 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 are optionally, used to enter a sequence of characters corresponding to a telephone number, access one or more telephone numbers in contacts module 137, modify a telephone number that has been entered, dial a respective telephone number, conduct a conversation, and disconnect or hang up when the conversation is completed. As noted above, the wireless communication optionally uses any of a plurality of communications 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 telephone module 138, video conference module 139 includes executable instructions to initiate, conduct, and terminate a video conference between a user and one or more other participants in accordance with 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, e-mail client module 140 includes executable instructions to create, send, receive, and manage e-mail in response to user instructions. In conjunction with image management module 144, e-mail client module 140 makes it very easy to create and send e-mails with still or video images taken with camera module 143.
In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, the instant messaging module 141 includes executable instructions to enter a sequence of characters corresponding to an instant message, to modify previously entered characters, to transmit a respective instant message (for example, using a Short Message Service (SMS) or Multimedia Message Service (MMS) protocol for telephony-based instant messages or using XMPP, SIMPLE, or IMPS for Internet-based instant messages), to receive instant messages, and to view received instant messages. In some embodiments, transmitted and/or received instant messages optionally include graphics, photos, audio files, video files and/or other attachments as are supported in an MMS and/or an Enhanced Messaging Service (EMS). As used herein, “instant messaging” 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 to create workouts (e.g., with time, distance, and/or calorie burning goals); communicate with workout sensors (sports devices); receive workout sensor data; calibrate sensors used to monitor a workout; select and play music for a workout; and display, store, and transmit workout data.
In conjunction with touch screen 112, display controller 156, optical sensor(s) 164, optical sensor controller 158, contact/motion module 130, graphics module 132, and image management module 144, camera module 143 includes executable instructions to capture still images or video (including a video stream) and store them into memory 102, modify characteristics of a still image or video, or delete a still image 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 to arrange, modify (e.g., edit), or otherwise manipulate, label, delete, present (e.g., in a digital slide show or album), and store still 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 to browse the Internet in accordance with user instructions, including searching, linking to, receiving, and displaying web pages or portions thereof, as well as attachments and other files linked to web pages.
In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, e-mail client module 140, and browser module 147, calendar module 148 includes executable instructions to create, display, modify, and store calendars and data associated with calendars (e.g., calendar entries, to-do lists, etc.) in accordance with 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, widget modules 149 are mini-applications that are, optionally, downloaded and used by a user (e.g., weather widget 149-1, stocks widget 149-2, calculator widget 149-3, alarm clock widget 149-4, and dictionary widget 149-5) or created by the user (e.g., user-created widget 149-6). In some embodiments, a widget includes an HTML (Hypertext Markup Language) file, a CSS (Cascading Style Sheets) file, and a JavaScript file. In some embodiments, a widget includes an XML (Extensible Markup Language) file and a JavaScript file (e.g., Yahoo! Widgets).
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, the widget creator module 150 are, optionally, used by a user to create widgets (e.g., turning a user-specified portion of a web page into a widget).
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 to search for text, music, sound, image, video, and/or other files in memory 102 that match one or more search criteria (e.g., one or more user-specified search terms) in accordance with user instructions.
In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, and browser module 147, video and music player module 152 includes executable instructions that allow the user to download and play back recorded music and other sound files stored in one or more file formats, such as MP3 or AAC files, and executable instructions to display, present, or otherwise play back videos (e.g., on touch screen 112 or on an external, connected display via external port 124). In some embodiments, device 100 optionally includes the functionality of an MP3 player, such as an iPod (trademark of Apple Inc.).
In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, notes module 153 includes executable instructions to create and manage notes, to-do lists, and the like in accordance with 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, GPS module 135, and browser module 147, map module 154 are, optionally, used to receive, display, modify, and store maps and data associated with maps (e.g., driving directions, data on stores and other points of interest at or near a particular location, and other location-based data) in accordance with user instructions.
In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, text input module 134, e-mail client module 140, and browser module 147, online video module 155 includes instructions that allow the user to access, browse, receive (e.g., by streaming and/or download), play back (e.g., on the touch screen or on an external, connected display via external port 124), send an e-mail with a link to a particular online video, and otherwise manage online videos in one or more file formats, such as H.264. In some embodiments, instant messaging module 141, rather than e-mail client module 140, is used to send a link to a particular online video. Additional description of the online video application can be found in U.S. Provisional Patent Application No. 60/936,562, “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos,” filed Jun. 20, 2007, and U.S. patent application Ser. No. 11/968,067, “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos,” filed Dec. 31, 2007, the contents of which are hereby incorporated by reference in their entirety.
Each of the above-identified modules and applications corresponds to a set of executable instructions for performing one or more functions described above and the methods described in this application (e.g., the computer-implemented methods and other information processing methods described herein). These modules (e.g., sets of instructions) need not be implemented as separate software programs, procedures, or modules, and thus various subsets of these modules are, optionally, combined or otherwise rearranged in various embodiments. For example, video player module is, optionally, combined with music player module into a single module (e.g., video and music player module 152,
In some embodiments, device 100 is a device where operation of a predefined set of functions on the device is performed exclusively through a touch screen and/or a touchpad. By using a touch screen and/or a touchpad as the primary input control device for operation of device 100, the number of physical input control devices (such as push buttons, dials, and the like) on device 100 is, optionally, reduced.
The predefined set of functions that are performed exclusively through a touch screen and/or a touchpad optionally include navigation between user interfaces. In some embodiments, the touchpad, when touched by the user, navigates device 100 to a main, home, or root menu from any user interface that is displayed on device 100. In such embodiments, a “menu button” is implemented using a touchpad. In some other embodiments, the menu button is a physical push button or other physical input control device instead of a touchpad.
Event sorter 170 receives event information and determines the application 136-1 and application view 191 of application 136-1 to which to deliver the event information. Event sorter 170 includes event monitor 171 and event dispatcher module 174. In some embodiments, application 136-1 includes application internal state 192, which indicates the current application view(s) displayed on touch-sensitive display 112 when the application is active or executing. In some embodiments, device/global internal state 157 is used by event sorter 170 to determine which application(s) is (are) currently active, and application internal state 192 is used by event sorter 170 to determine application views 191 to which to deliver event information.
In some embodiments, application internal state 192 includes additional information, such as one or more of: resume information to be used when application 136-1 resumes execution, user interface state information that indicates information being displayed or that is ready for display by application 136-1, a state queue for enabling the user to go back to a prior state or view of application 136-1, and a redo/undo queue of previous actions taken by the user.
Event monitor 171 receives event information from peripherals interface 118. Event information includes information about a sub-event (e.g., a user touch on touch-sensitive display 112, as part of a multi-touch gesture). Peripherals interface 118 transmits information it receives from I/O subsystem 106 or a sensor, such as proximity sensor 166, accelerometer(s) 168, and/or microphone 113 (through audio circuitry 110). Information that peripherals interface 118 receives from I/O subsystem 106 includes information from touch-sensitive display 112 or a touch-sensitive surface.
In some embodiments, event monitor 171 sends requests to the peripherals interface 118 at predetermined intervals. In response, peripherals interface 118 transmits event information. In other embodiments, peripherals interface 118 transmits event information only when there is a significant event (e.g., receiving an input above a predetermined noise threshold and/or for more than a predetermined duration).
In some embodiments, event sorter 170 also includes a hit view determination module 172 and/or an active event recognizer determination module 173.
Hit view determination module 172 provides software procedures for determining where a sub-event has taken place within one or more views when touch-sensitive display 112 displays more than one view. Views are made up of controls and other elements that a user can see on the display.
Another aspect of the user interface associated with an application is a set of views, sometimes herein called application views or user interface windows, in which information is displayed and touch-based gestures occur. The application views (of a respective application) in which a touch is detected optionally correspond to programmatic levels within a programmatic or view hierarchy of the application. For example, the lowest level view in which a touch is detected is, optionally, called the hit view, and the set of events that are recognized as proper inputs are, 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 a touch-based gesture. When an application has multiple views organized in a hierarchy, hit view determination module 172 identifies a hit view as the lowest view in the hierarchy which should handle the sub-event. In most circumstances, the hit view is the lowest level view in which an initiating sub-event occurs (e.g., the first sub-event in the sequence of sub-events that form an event or potential event). 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 the hit view.
Active event recognizer determination module 173 determines which view or views within a view hierarchy should receive a particular sequence of sub-events. In some embodiments, active event recognizer determination module 173 determines that only the hit view should receive a particular sequence of sub-events. In other embodiments, active event recognizer determination module 173 determines that all views that include the physical location of a sub-event are actively involved views, and therefore determines that all actively involved views should receive a particular sequence of sub-events. In other embodiments, even if touch sub-events were entirely confined to the area associated with one particular view, views higher in the hierarchy would still remain as actively involved views.
Event dispatcher module 174 dispatches the event information to an event recognizer (e.g., event recognizer 180). In embodiments including active event recognizer determination module 173, event dispatcher module 174 delivers the event information to an event recognizer determined by active event recognizer determination module 173. In some embodiments, event dispatcher module 174 stores in an event queue the event information, which is retrieved by a respective event receiver 182.
In some embodiments, operating system 126 includes event sorter 170. Alternatively, application 136-1 includes event sorter 170. In yet other embodiments, event sorter 170 is a stand-alone module, or a part of another module stored in memory 102, such as contact/motion module 130.
In some embodiments, application 136-1 includes a plurality of event handlers 190 and one or more application views 191, each of which includes instructions for handling touch events that occur within a respective view of the application's user interface. Each application view 191 of the application 136-1 includes one or more event recognizers 180. Typically, a respective application view 191 includes a plurality of event recognizers 180. In other embodiments, one or more of event recognizers 180 are part of a separate module, such as a user interface kit or a higher level object from which application 136-1 inherits methods and other properties. In some embodiments, a respective event handler 190 includes one or more of: data updater 176, object updater 177, GUI updater 178, and/or event data 179 received from event sorter 170. Event handler 190 optionally utilizes or calls data updater 176, object updater 177, or GUI updater 178 to update the application internal state 192. Alternatively, one or more of the application views 191 include one or more respective event handlers 190. Also, in some embodiments, one or more of data updater 176, object updater 177, and GUI updater 178 are included in a respective application view 191.
A respective event recognizer 180 receives event information (e.g., event data 179) from event sorter 170 and identifies an event from the event information. Event recognizer 180 includes event receiver 182 and event comparator 184. In some embodiments, event recognizer 180 also 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 a sub-event, for example, a touch or a touch movement. Depending on the sub-event, the event information also includes additional information, such as location of the sub-event. When the sub-event concerns motion of a touch, the event information optionally also includes speed and direction of the sub-event. In some embodiments, events include rotation of the device from one orientation to another (e.g., from a portrait orientation to a landscape orientation, or vice versa), and the event information includes corresponding information about the current orientation (also called device attitude) of the device.
Event comparator 184 compares the event information to predefined event or sub-event definitions and, based on the comparison, determines an event or sub-event, or determines or updates the state of an event or sub-event. In some embodiments, event comparator 184 includes event definitions 186. Event definitions 186 contain definitions of events (e.g., predefined sequences of sub-events), for example, event 1 (187-1), event 2 (187-2), and others. In some embodiments, sub-events in an event (187) include, for example, touch begin, touch end, touch movement, touch cancellation, and multiple touching. In one example, the definition for event 1 (187-1) is a double tap on a displayed object. The double tap, for example, comprises a first touch (touch begin) on the displayed object for a predetermined phase, a first liftoff (touch end) for a predetermined phase, a second touch (touch begin) on the displayed object for a predetermined phase, and a second liftoff (touch end) for a predetermined phase. In another example, the definition for event 2 (187-2) is a dragging on a displayed object. The dragging, for example, comprises a touch (or contact) on the displayed object for a predetermined phase, a movement of the touch across touch-sensitive display 112, and liftoff of the touch (touch end). In some embodiments, the event also includes information for one or more associated event handlers 190.
In some embodiments, event definition 187 includes a definition of an event for a respective user-interface object. In some embodiments, event comparator 184 performs a hit test to determine which user-interface object is associated with a sub-event. For example, in an application view in which three user-interface objects are displayed on touch-sensitive display 112, when a touch is detected on touch-sensitive display 112, event comparator 184 performs a hit test to determine which of the three user-interface objects is associated with the touch (sub-event). If each displayed object is associated with a respective event handler 190, the event comparator uses the result of the hit test to determine which event handler 190 should be activated. For example, event comparator 184 selects an event handler associated with the sub-event and the object triggering the hit test.
In some embodiments, the definition for a respective event (187) also includes delayed actions that delay delivery of the event information until after it has been determined whether the sequence of sub-events does or does not correspond to the event recognizer's event type.
When a respective event recognizer 180 determines that the series of sub-events do not match any of the events in event definitions 186, the respective event recognizer 180 enters an event impossible, event failed, or event ended state, after which it disregards subsequent sub-events of the touch-based gesture. In this situation, other event recognizers, if any, that remain active for the hit view continue to track and process sub-events of an ongoing touch-based gesture.
In some embodiments, a 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 actively involved event recognizers. In some embodiments, metadata 183 includes configurable properties, flags, and/or lists that indicate how event recognizers interact, or are enabled to interact, with one another. In some embodiments, metadata 183 includes configurable properties, flags, and/or lists that indicate whether sub-events are delivered to varying levels in the view or programmatic hierarchy.
In some embodiments, a respective event recognizer 180 activates event handler 190 associated with an event when one or more particular sub-events of an event are recognized. In some embodiments, a respective event recognizer 180 delivers event information associated with the event to event handler 190. Activating an event handler 190 is distinct from sending (and deferred sending) sub-events to a respective hit view. In some embodiments, event recognizer 180 throws a flag associated with the recognized event, and event handler 190 associated with the flag catches the flag and performs a predefined process.
In some embodiments, event delivery instructions 188 include sub-event delivery instructions that deliver event information about a sub-event without activating an event handler. Instead, the sub-event delivery instructions deliver event information to event handlers associated with the series of sub-events or to actively involved views. Event handlers associated with the series of sub-events or with actively involved views receive the event information and perform a predetermined process.
In some embodiments, data updater 176 creates and updates data used in application 136-1. For example, data updater 176 updates the telephone number used in contacts module 137, or stores a video file used in video player module. In some embodiments, object updater 177 creates and updates objects used in application 136-1. For example, object updater 177 creates a new user-interface object or updates the position of a user-interface object. GUI updater 178 updates the GUI. For example, GUI updater 178 prepares display information and sends it to graphics module 132 for display on a touch-sensitive display.
In some embodiments, event handler(s) 190 includes or has access to data updater 176, object updater 177, and GUI updater 178. In some embodiments, data updater 176, object updater 177, and GUI updater 178 are included in a single module of a respective application 136-1 or application view 191. In other embodiments, they are included in two or more software modules.
It shall be understood that the foregoing discussion regarding event handling of user touches on touch-sensitive displays also applies to other forms of user inputs to operate multifunction devices 100 with input devices, not all of which are initiated on touch screens. For example, mouse movement and mouse button presses, optionally coordinated with single or multiple keyboard presses or holds; contact movements such as taps, drags, scrolls, etc. on touchpads; pen stylus inputs; movement of the device; oral instructions; detected eye movements; biometric inputs; and/or any combination thereof are optionally utilized as inputs corresponding to sub-events which define an event to be recognized.
Device 100 optionally also include one or more physical buttons, such as “home” or menu button 204. As described previously, 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 button is implemented as a soft key in a GUI displayed on touch screen 112.
In some embodiments, device 100 includes touch screen 112, menu button 204, push button 206 for powering the device on/off and locking the device, volume adjustment button(s) 208, subscriber identity module (SIM) card slot 210, headset jack 212, and docking/charging external port 124. Push button 206 is, optionally, used to turn the power on/off on the device by depressing the button and holding the button in the depressed state for a predefined time interval; to lock the device by depressing the button and releasing the button before the predefined time interval has elapsed; and/or to unlock the device or initiate an unlock process. In an alternative embodiment, device 100 also accepts verbal input for activation or deactivation of some functions through microphone 113. Device 100 also, optionally, includes one or more contact intensity sensors 165 for detecting intensity of contacts on touch screen 112 and/or one or more tactile output generators 167 for generating tactile outputs for a user of device 100.
Each of the above-identified elements in
Attention is now directed towards embodiments of user interfaces that are, optionally, implemented on, for example, portable multifunction device 100.
It should be noted that the icon labels illustrated in
Although some of the examples that follow 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 that is separate from the display, as shown in
Additionally, while the following examples are given primarily with reference to finger inputs (e.g., finger contacts, finger tap gestures, finger swipe gestures), it should be understood that, in some embodiments, one or more of the finger inputs are replaced with input from another input device (e.g., a mouse-based input or stylus input). For example, a swipe gesture is, optionally, replaced with a mouse click (e.g., instead of a contact) followed by movement of the cursor along the path of the swipe (e.g., instead of movement of the contact). As another example, a tap gesture is, optionally, replaced with a mouse click while the cursor is located over the location of the tap gesture (e.g., instead of detection of the contact followed by ceasing to detect the contact). Similarly, when multiple user inputs are simultaneously detected, it should be understood that multiple computer mice are, optionally, used simultaneously, or a mouse and finger contacts are, optionally, used simultaneously.
Exemplary techniques for detecting and processing touch intensity are found, for example, in related applications: International Patent Application Serial No. PCT/US2013/040061, titled “Device, Method, and Graphical User Interface for Displaying User Interface Objects Corresponding to an Application,” filed May 8, 2013, published as WIPO Publication No. WO/2013/169849, and International Patent Application Serial No. PCT/US2013/069483, titled “Device, Method, and Graphical User Interface for Transitioning Between Touch Input to Display Output Relationships,” filed Nov. 11, 2013, published as WIPO Publication No. WO/2014/105276, each of which is hereby incorporated by reference in their entirety.
In some embodiments, device 500 has one or more input mechanisms 506 and 508. Input mechanisms 506 and 508, if included, can be physical. Examples of physical input mechanisms include push buttons and rotatable mechanisms. In some embodiments, device 500 has one or more attachment mechanisms. Such attachment mechanisms, if included, can permit attachment of device 500 with, for example, hats, eyewear, earrings, necklaces, shirts, jackets, bracelets, watch straps, chains, trousers, belts, shoes, purses, backpacks, and so forth. These attachment mechanisms permit device 500 to be worn by a user.
Input mechanism 508 is, optionally, a microphone, in some examples. Personal electronic device 500 optionally includes various sensors, such as GPS sensor 532, accelerometer 534, directional sensor 540 (e.g., compass), gyroscope 536, motion sensor 538, and/or a combination thereof, all of which can be operatively connected to I/O section 514.
Memory 518 of personal electronic device 500 can include one or more non-transitory computer-readable storage mediums, for storing computer-executable instructions, which, when executed by one or more computer processors 516, for example, can cause the computer processors to perform the techniques described below, including processes 700, 1000, 1300, 1500, 1600, and 1800 (
As used here, the term “affordance” refers to a user-interactive graphical user interface object that is, optionally, displayed on the display screen of devices 100, 300, and/or 500 (
As used herein, the term “focus selector” refers to an input element that indicates a current part of a user interface with which a user is interacting. In some implementations that include a cursor or other location marker, the cursor acts as a “focus selector” so that when an input (e.g., a press input) is detected on a touch-sensitive surface (e.g., touchpad 355 in
As used in the specification and claims, the term “characteristic intensity” of a contact refers to a characteristic of the contact based on one or more intensities of the contact. In some embodiments, the characteristic intensity is based on multiple intensity samples. The characteristic intensity is, optionally, based on a predefined number of intensity samples, or a set of intensity samples collected during a predetermined time period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10 seconds) relative to a predefined event (e.g., after detecting the contact, prior to detecting liftoff of the contact, before or after detecting a start of movement of the contact, prior to detecting an end of the contact, before or after detecting an increase in intensity of the contact, and/or before or after detecting a decrease in intensity of the contact). A characteristic intensity of a contact is, optionally, based on one or more of: a maximum value of the intensities of the contact, a mean value of the intensities of the contact, an average value of the intensities of the contact, a top 10 percentile value of the intensities of the contact, a value at the half maximum of the intensities of the contact, a value at the 90 percent maximum of the intensities of the contact, or 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 an operation has been performed by a user. For example, the set of one or more intensity thresholds optionally includes a first intensity threshold and a second intensity threshold. In this example, a contact with a characteristic intensity that does not exceed the first threshold results in a first operation, a contact with a characteristic intensity that exceeds the first intensity threshold and does not exceed the second intensity threshold results in a second operation, and a contact with a characteristic intensity that exceeds the second threshold results in a third operation. In some embodiments, a comparison between the characteristic intensity and one or more thresholds is used to determine whether or not to perform one or more operations (e.g., whether to perform a respective operation or forgo performing the respective operation), rather than being used to determine whether to perform a first operation or a second operation.
In some embodiments, a portion of a gesture is identified for purposes of determining a characteristic intensity. For example, a touch-sensitive surface optionally receives a continuous swipe contact transitioning from a start location and reaching an end location, at which point the intensity of the contact increases. In this example, the characteristic intensity of the contact at the end location is, optionally, based on only a portion of the continuous swipe contact, and not the entire swipe contact (e.g., only the portion of the swipe contact at the end location). In some embodiments, a smoothing algorithm is, optionally, applied to the intensities of the swipe contact prior to determining the characteristic intensity of the contact. For example, the smoothing algorithm optionally includes one or more of: an unweighted sliding-average smoothing algorithm, a triangular smoothing algorithm, a median filter smoothing algorithm, and/or an exponential smoothing algorithm. In some circumstances, these smoothing algorithms eliminate narrow spikes or dips in the intensities of the swipe contact for purposes of determining a characteristic intensity.
The intensity of a contact on the touch-sensitive surface is, optionally, characterized relative to one or more intensity thresholds, such as a contact-detection intensity threshold, a light press intensity threshold, a deep press intensity threshold, and/or one or more other intensity thresholds. In some embodiments, the light press intensity threshold corresponds to an intensity at which the device will perform operations typically associated with clicking a button of a physical mouse or a trackpad. In some embodiments, the deep press intensity threshold corresponds to an intensity at which the device will perform operations that are different from operations typically associated with clicking a button of a physical mouse or a trackpad. In some embodiments, when a contact is detected with a characteristic intensity below the light press intensity threshold (e.g., and above a nominal contact-detection intensity threshold below which the contact is no longer detected), the device will move a focus selector in accordance with movement of the contact on the touch-sensitive surface without performing an operation associated with the light press intensity threshold or the deep press intensity threshold. Generally, unless otherwise stated, these intensity thresholds are consistent between different sets of user interface figures.
An increase of characteristic intensity of the contact from an intensity below the light press intensity threshold to an intensity between the light press intensity threshold and the deep press intensity threshold is sometimes referred to as a “light press” input. An increase of characteristic intensity of the contact from an intensity below the deep press intensity threshold to an intensity above the deep press intensity threshold is sometimes referred to as a “deep press” input. An increase of characteristic intensity of the contact from an intensity below the contact-detection intensity threshold to an intensity between the contact-detection intensity threshold and the light press intensity threshold is sometimes referred to as detecting the contact on the touch-surface. A decrease of characteristic intensity of the contact from an intensity above the contact-detection intensity threshold to an intensity below the contact-detection intensity threshold is sometimes referred to as detecting liftoff of the contact from the touch-surface. In some embodiments, the contact-detection intensity threshold is zero. In some embodiments, the contact-detection intensity threshold is greater than zero.
In some embodiments described herein, one or more operations are performed in response to detecting a gesture that includes a respective press input or in response to detecting the respective press input performed with a respective contact (or a plurality of contacts), where the respective press input is detected based at least in part on detecting an increase in intensity of the contact (or plurality of contacts) above a press-input intensity threshold. In some embodiments, the respective operation is performed in response to detecting the increase in intensity of the respective contact above the press-input intensity threshold (e.g., a “down stroke” of the respective press input). In some embodiments, the press input includes an increase in intensity of the respective contact above the press-input intensity threshold and a subsequent decrease in intensity of the contact below the press-input intensity threshold, and the respective operation is performed in response to detecting the subsequent decrease in intensity of the respective contact below the press-input threshold (e.g., an “up stroke” of the respective press input).
In some embodiments, the display of representations 578A-578C includes an animation. For example, representation 578A is initially displayed in proximity of application icon 572B, as shown in
In some embodiments, the device employs intensity hysteresis to avoid accidental inputs sometimes termed “jitter,” where the device defines or selects a hysteresis intensity threshold with a predefined relationship to the press-input intensity threshold (e.g., the hysteresis intensity threshold is X intensity units lower than the press-input intensity threshold or the hysteresis intensity threshold is 75%, 90%, or some reasonable proportion of the press-input intensity threshold). Thus, in some embodiments, the press input includes an increase in intensity of the respective contact above the press-input intensity threshold and a subsequent decrease in intensity of the contact below the hysteresis intensity threshold that corresponds to the press-input intensity threshold, and the respective operation is performed in response to detecting the subsequent decrease in intensity of the respective contact below the hysteresis intensity threshold (e.g., an “up stroke” of the respective press input). Similarly, in some embodiments, the press input is detected only when the device detects an increase in intensity of the contact from an intensity at or below the hysteresis intensity threshold to an intensity at or above the press-input intensity threshold and, optionally, a subsequent decrease in intensity of the contact to an intensity at or below the hysteresis intensity, and the respective operation is performed in response to detecting the press input (e.g., the increase in intensity of the contact or the decrease in intensity of the contact, depending on the circumstances).
For ease of explanation, the descriptions of operations performed in response to a press input associated with a press-input intensity threshold or in response to a gesture including the press input are, optionally, triggered in response to detecting either: an increase in intensity of a contact above the press-input intensity threshold, an increase in intensity of a contact from an intensity below the hysteresis intensity threshold to an intensity above the press-input intensity threshold, a decrease in intensity of the contact below the press-input intensity threshold, and/or a decrease in intensity of the contact below the hysteresis intensity threshold corresponding to the press-input intensity threshold. Additionally, in examples where an operation is described as being performed in response to detecting a decrease in intensity of a contact below the press-input intensity threshold, the operation is, optionally, performed in response to detecting a decrease in intensity of the contact below a hysteresis intensity threshold corresponding to, and lower than, the press-input intensity threshold.
As used herein, an “installed application” refers to a software application that has been downloaded onto an electronic device (e.g., devices 100, 300, and/or 500) and is ready to be launched (e.g., become opened) on the device. In some embodiments, a downloaded application becomes an installed application by way of an installation program that extracts program portions from a downloaded package and integrates the extracted portions with the operating system of the computer system.
As used herein, the terms “open application” or “executing application” refer to a software application with retained state information (e.g., as part of device/global internal state 157 and/or application internal state 192). An open or executing application is, optionally, any one of the following types of applications:
As used herein, the term “closed application” refers to software applications without retained state information (e.g., state information for closed applications is not stored in a memory of the device). Accordingly, closing an application includes stopping and/or removing application processes for the application and removing state information for the application from the memory of the device. Generally, opening a second application while in a first application does not close the first application. When the second application is displayed and the first application ceases to be displayed, the first application becomes a background application.
Attention is now directed towards embodiments of user interfaces (“UI”) and associated processes that are implemented on an electronic device, such as portable multifunction device 100, device 300, or device 500.
As depicted in
As depicted in
As depicted in
As depicted in
Noise meter indicator 636 provides a graphical indication of a second noise level (e.g., measured by device 600 via microphone 606). In some embodiments, the second noise level and the first noise are the same noise level. In some embodiments, the first noise level and the second noise level are determined based on common noise data sampled at different time periods and/or rates (e.g., 1-second and 0.1-seconds, respectively). Noise meter indicator 638 includes active portion 638A (e.g., a visually emphasized portion) that varies in size and/or color according to a second noise level. As illustrate by the following figures, the size of active portion 638A increases as a noise level increases and the color of the active portion 638A changes relative to a second threshold level. In some embodiments, size includes a number of visually emphasized segments, a relative area occupied by a set of visually emphasized segments, or a position of the right-most edge of a set of visually emphasized segments relative to a scale. In some embodiments, each emphasized segment in active portion 638A represents a predetermined number of decibels (e.g., 10 DB). In some embodiments, the first threshold level and the second threshold level are the same level (e.g., 80 DB).
The noise levels (e.g., values, amplitudes) indicated by the appearance of noise level indicator 636, noise meter indicator 638, and noise status indicator 640 (e.g., as described below), are updated in response to device 600 determining one or more noise levels based on received noise data (e.g., the indications update as ambient noise levels are continuously determined or measured by device 600). In some embodiments, noise levels are measured or detected by a device external to device 600 (e.g., device 600 receives data representing a current noise level from a remote device communicatively coupled with device 600).
As described above, the appearance of noise level indicator 636 and noise status indicator 640 vary with a first noise level (e.g., a noise level based on a longer 1-second period of noise level data) and the appearance of noise meter indicator 638 varies based on a second noise level (e.g., a noise level based on a shorter 0.1-second period of noise level data). Consequently, the graphical meter changes more quickly (e.g., instantaneously) than noise level indicator 636 (and noise status indicator 640) in response to sudden changes in ambient noise level. This lagging effect is illustrated by the difference between the noise levels represented by noise level indicator 636 and noise status indicator 640 and noise meter 638. In some embodiments, the slower update makes it easier to for a user to decipher (e.g., read) a displayed noise level, while the faster update behavior of noise meter indicator 638 provides the user with more timely (e.g., responsive) visual feedback.
In response to a determination that a noise level exceeds a notification level threshold (e.g., 80 DB, 85 DB, 90 DB) for a period of time (e.g., 3-minutes), device 600 emits haptic alert 642 as depicted in
Subsequent to outputting haptic alert 642, device 600 displays the noise notification user interface 608D of
As depicted in
As depicted in
As depicted in
In some embodiments, the electronic device (e.g., 100, 300, 500, 600, 601, 800, 900, 1100, 1200, 1400, 1401, and 1700) is a computer system. The computer system is optionally in communication (e.g., wired communication, wireless communication) with a display generation component and with one or more input devices. 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. The one or more input devices are configured to receive input, such as a touch-sensitive surface receiving user input. In some embodiments, the one or more input devices are integrated with the computer system. In some embodiments, the one or more input devices are separate from the computer system. Thus, the computer system can transmit, via a wired or wireless connection, data (e.g., image data or video data) to an integrated or external display generation component to visually produce the content (e.g., using a display device) and can receive, a wired or wireless connection, input from the one or more input devices.
As described below, method 700 provides an intuitive way for monitoring noise exposure levels. The method reduces the cognitive burden on a user seeking to monitor noise levels (e.g., environment noise levels) the user is exposed to and experiencing during a day, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a user to monitor noise exposure levels faster and more efficiently conserves power and increases the time between battery charges.
The electronic device (e.g., 600) displays (712), via the display device, a first user interface (e.g., a clock face user interface or user interface of an application) including a graphical object (e.g., a meter) that varies in appearance based on a noise level.
In some embodiments, at a first time point prior to displaying the first user interface (e.g., 608A, 608C) and in accordance with a determination that a set of noise notification criteria are met, the noise notification criteria including a criterion that is met when a current noise level over a third period of time (e.g., an average value of the current noise level over the third period of time) exceeds a third threshold noise level (e.g., 80 dB, 85 dB, 90 dB) (e.g., the average noise level exceeds the threshold for at least 3 minutes), the electronic device displays (702) a noise level notification (608D) that includes: an indication of the current noise level over the third period of time (e.g., text indicating that a current noise level over the third period of time has exceeded the third threshold noise level; text indicating the amount of time that the current noise level has exceeded the third threshold noise level) (704), and a third affordance (e.g., “Open Noise”) (e.g., 644) (706). In some embodiments, the third threshold level is the same as the first or second threshold levels. In some embodiments, the set of noise notification criteria includes a second criterion that is met when the current noise level exceeds the third threshold noise level for at least a third period of time. In some embodiments, while displaying the third affordance (e.g., 644), the electronic device receives (708) a user input corresponding to the third affordance. In some embodiments, in response to receiving the user input corresponding to the third affordance, the electronic device displays (710) the first user interface (e.g., 608C) (e.g., opening the noise app). Displaying (e.g., automatically) the noise level notification in accordance with the determination that the set of noise notification criteria are met provides a user with quick and easy access to information concerning a current noise exposure level. Performing an operation when a set of conditions has been met without requiring further user input enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
In some embodiments, the set of noise notification criteria are not satisfied when a second noise notification level was displayed within a predetermined time (e.g., 30 minutes) before the first time point (e.g., 10:17 as depicted in
In some embodiments, the noise level notification (e.g., 608D) further includes a fourth affordance (e.g., 646) associated with a second predetermined period and the electronic device receives an input corresponding to the fourth affordance and in response to receiving the input corresponding to the fourth affordance, the electronic device forgoes display of (e.g., suppressing display of) further instances of noise level notifications for the second predetermined time period (e.g., 1 hour, ½ hour, reminder of the day). Providing the fourth affordance in the noise level notification that enables a user to cause the electronic device to forgo displaying further instances of noise level notifications enables the user to quickly and easily suppress further noise level notifications on the electronic device. Providing additional control options without cluttering the UI with additional displayed controls enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
The electronic device receives (714) first noise level data (e.g., noise level data corresponding to the noise level over a first period of time; an average value over the first period of time or multiple data points representing the noise level over the first period of time) (e.g., noise level “34 DB” of
In response to receiving the first noise level data, the electronic device displays (716) the graphical object (e.g., 622, 638) with an active portion (e.g., emphasized or visually distinct portion based on appearance) (e.g., 622A, 638A) of a first size (e.g., a number of segments, a length, or an area relative to the object's overall size that is proportional to the noise level) based on the first noise data and in a first color (e.g., green). In some embodiments, the active portion extends from the left-most edge of the graphical object to a location between the left-most edge and right-most edge of the graphical object. In some embodiments, the graphical object includes an indication of the first noise level data other than a size of the active portion (e.g., a numeric value, a position of a point or a line along the axis of a graph). Displaying the graphical object with the active portion of the first size based on the first noise data and in the first color provides a user with easily recognizable and understandable noise exposure level information. Providing improved visual feedback to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
While maintaining display of the first user interface, the electronic device receives (718) second noise level data corresponding to a second noise level different from the first noise level (e.g., the second is either lower or higher than the first) (e.g., noise level “113 DB” of
In response to receiving the second noise level data (720), the electronic device displays (722) the active portion in a second size based on the second noise level that that is different from the first size (e.g., the active portion grows or shrinks corresponding the difference between the first noise level and the second noise level) (e.g., 638A in
In response to receiving the second noise level data (720), in accordance with a determination that the second noise level exceeds the threshold noise level (e.g., the noise level has increased beyond the 80 dB threshold), the electronic device displays (724) the active portion (e.g., 638A in
In response to receiving the second noise level data (720), in accordance with a determination that the second noise level does not exceed the threshold noise level (e.g., the noise level remains below the 80 dB threshold), the electronic device maintains (726) display of the graphical object in the first color (e.g., maintain as green).
In some embodiments, while displaying the graphical object with the active portion at the second size and in the second color (e.g., yellow), the electronic device receives (728) third noise level data corresponding to a third noise level that is below the threshold noise level (e.g., the noise level has decreased to below the 80 dB threshold). In some embodiments, in response to receiving the third noise level data, the electronic device displays (730) the active portion at a third size based on the third noise level data that is smaller than the second size and in the first color (e.g., the active portion shrinks corresponding the difference between the second noise level and the third noise level and changes from yellow to green) (e.g., 638A in
In some embodiments, the graphical object varies based on noise level over a first period of time (e.g., an average of noise level over a 0.1-second window) and the first user interface further includes a second graphical object (e.g., a text indication; a graphical indication) (e.g., 620, 624, 636, 640) that varies in appearance based on the noise level over a second period of time that is different from the first period of time (e.g., averaged over a 1-second window).
In some embodiments, displaying the first user interface includes displaying a first affordance that, when selected, displays a second user interface (e.g., an interface with information about the threshold noise level) (e.g., 640) in accordance with a determination that a current noise level (e.g., based on noise data for the first period of time or noise data for the second period of time) is below a second threshold noise level (e.g., a user-selected threshold). In some embodiments, the first affordance includes “OK” or a graphical element (e.g., a checkmark) when the noise level is below the threshold (e.g., 640 in
In some embodiments, displaying the first user interface includes displaying a second affordance (e.g., without displaying the first affordance), different from the first affordance, that, when selected, displays a third user interface (e.g., the same as the second user interface; different than the first user interface and with information about the threshold noise level) in accordance with a determination that a current noise level is above the second threshold noise level. In some embodiments, the first affordance includes “LOUD” or a graphical element (e.g., an exclamation point) when the noise level is at or above the threshold.
In some embodiments, the electronic device includes one or more noise sensors (e.g., one or more pressure sensing devices such as a microphone or microphone array) (e.g., 606), and the first noise level data and the second noise level data are received from the one or more noise sensors. In some embodiments, the display device and the one or more noise sensors are located within a common housing or body of the electronic device and the first noise level data and the second noise level data represent the noise level of the physical environment where the electronic device is located.
In some embodiments, the first noise level data and the second noise level data are received from a second electronic device that is different from the first electronic device (e.g., noise level data is received at the electronic device displaying the UI from a device external to the electronic device displaying the UI).
In some embodiments, while the first user interface is displayed (e.g., 608A, 608C), the electronic device samples noise level data at a first sampling rate (e.g., receiving new noise level data at a first rate). In some embodiments, while the first user interface is not displayed (e.g., 608B, 608D, and as generally depicted by
Note that details of the processes described above with respect to method 700 (e.g.,
As depicted in
As depicted in
A depicted by
A depicted by
As depicted in
Chart 905 includes an overlay line corresponding the average audio level indicated by average affordance 914 (e.g. overlay 912). In some embodiments, the average audio level is not an average of the displayed data but rather a time-based average of underlying data (e.g., an average based on how long a user was exposed to each level (e.g., sound pressure level) depicted by the data in chart 905). In some embodiments, the data depicted by chart 905 represents the audio amplitudes levels a device user has been exposed to over the course of a day or other period of time (e.g., hour, week, year, month). As depicted in
As depicted in
As depicted in
In addition to emphasizing audio data in response to user input 906C, device 900 updates overlay 912 to depict an average audio level (e.g., 72 DB) based on the emphasized set of noise amplitude values (e.g., the average audio level attributable to earbud device types).
As depicted in
As depicted in
As depicted in
As depicted in
In some embodiments, the electronic device (e.g., 100, 300, 500, 600, 601, 800, 900, 1100, 1200, 1400, 1401, and 1700) is a computer system. The computer system is optionally in communication (e.g., wired communication, wireless communication) with a display generation component and with one or more input devices. 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. The one or more input devices are configured to receive input, such as a touch-sensitive surface receiving user input. In some embodiments, the one or more input devices are integrated with the computer system. In some embodiments, the one or more input devices are separate from the computer system. Thus, the computer system can transmit, via a wired or wireless connection, data (e.g., image data or video data) to an integrated or external display generation component to visually produce the content (e.g., using a display device) and can receive, a wired or wireless connection, input from the one or more input devices.
As described below, method 700 provides an intuitive way for monitoring noise exposure levels. The method reduces the cognitive burden on a user to monitor noise exposure levels, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a user to monitor noise exposure levels faster and more efficiently conserves power and increases the time between battery charges.
The electronic device receives (1002) first noise level data attributable to a first device type (e.g., uncalibrated devices, such as wired headphones connected to the electronic device via a port (e.g., a headphone jack) or uncalibrated wireless headphones). The electronic device receives (1002) second noise level data attributable to a second device type (e.g., calibrated devices, such as calibrated wireless headphones) different from the first device type. In some embodiments, the electronic device identifies the first and second noise level data based on one or more output signals (e.g., voltages, digital audio data) sent by the electronic device to an output device of the first type.).
The electronic device displays (1004), via the display device (e.g., 902), a first user interface (e.g., 904A). In some embodiments, the first user interface is displayed in response to a user request (e.g., request to view a UI of noise application through search feature of health app or notifications in discover tab of health app). The first user interface includes a first representation of received noise level data that is based on the first noise level data and the second noise level data (e.g., a graph showing combined data or concurrently showing separate data for each of the first and second noise level data) (1006) (e.g., 905 in
While displaying the first user interface, the electronic device detects (1012) a first user input corresponding to selection of the first device type data filtering affordance (e.g., 916, 918, 926).
In response detecting the first user input, the electronic device displays (1014) a second representation of received noise level data that is based on the second noise level data and that is not based on the first noise level data (e.g., a second representation (e.g., a separate graph, a visual emphasis on the first representation) that emphasizes noise level data from calibrated devices compared to the depiction of noise level data in the first representation) (e.g., 905 in
In some embodiments, as part of displaying the second representation of received noise level data, the electronic device maintains (1016) display of the first representation of received noise level data (e.g., 905 in
In some embodiments, the second noise level data corresponds to noise level data attributable to a single device. In some embodiments, a single device includes a pair of linked devices (e.g., wirelessly linked left and right headphones).
In some embodiments, the first noise level data corresponds to noise level data attributable to a plurality of devices (e.g., a plurality of sets of linked devices (e.g., pairs of linked wireless headphones).
In some embodiments, the second noise level data includes third noise level data attributable to a third device type (e.g., data from an additional calibrated device). In some embodiments, the first user interface includes a second device type filtering affordance corresponding to the third noise level data (e.g., an additional calibrated device affordance in additions to the first calibrated device affordance) (e.g., 918). In some embodiments, while displaying the first user interface (e.g., 904C), the electronic device detects a user input corresponding to selection of the second device type filtering affordance (e.g., 906C). In some embodiments, in response detecting the user input corresponding to a selection of the second device type filtering affordance, the electronic device displays a third representation of the third noise level data (e.g., 905 in
In some embodiments, the first user interface includes, prior to detecting the first user input, an average noise exposure level indicator (e.g., 912, 914) indicating an average noise exposure level corresponding to the first noise level data and the second noise level data for a first time period (e.g., a day, a week) (1010). In some embodiments, the average noise level indicator includes a check mark or exclamation point, ‘LOUD’ or ‘OK’ (e.g., 922). In some embodiments, the average noise level indicator is an overlay line (e.g., 912), textual description, or icon (e.g., 922). Providing an average noise exposure level indicator indicating the average noise exposure level provides a user with a simple and easily recognizable metric to understand the overall noise exposure level. Providing improved visual feedback to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
In some embodiments, in response detecting the user input corresponding to a selection of the first device type filtering affordance (e.g., 916), the electronic device updates (1018) the average noise exposure level indicator to indicate an average noise level corresponding to the second noise level data (e.g., that does not correspond to the first noise level data) (e.g., indicating the average based on only the calibrated data associated with the second device type) (e.g., 912 in
In some embodiments, the second noise level data is based, at least in part, on one or more signals transmitted from the electronic device to one or more devices of the second type (e.g., noise levels are not based on incoming signals or data (e.g., audio levels measured via a microphone). In some embodiments, noise levels are estimated based on a volume setting (e.g., volume at 100%) and a known output device response (e.g., headphones of a first type output 87 dB at 100% for the particular signal being played).
In some embodiments, the first representation of received noise level data includes an indication of the maximum value of the noise level data (e.g., 908) and the minimum value of the noise level data (e.g., values representing the highest and lowest noise levels within the combined first noise level data and second noise level data) for a second time period (e.g., a day, a week) (e.g., 910). In some embodiments, the first representation includes more than one pair of maximum and minimum noise level values (e.g., maximum and minimum values for each day within a week).
Note that details of the processes described above with respect to method 1000 (e.g.,
In
In
In
In
As shown in
In
In
In some embodiments, slider 1216 can have a different appearance than that shown in headphone audio settings interface 1205. For example, slider 1216 can have additional setting positions such as “none,” “very slight,” or “very strong,” or intermediate positions between “slight” and “moderate” and between “moderate” and “strong.” In some embodiments, slider 1216 can be modified to include the ability to set a range of values. For example, slider 1216 can have two notches to set a high end of the range and a low end of the range. Additionally, in some embodiments, slider 1216 can be replaced or supplemented with other user interface objects for indicating a boost setting such as, for example, a field for entering a range of values (e.g., a numerical range) or a value (e.g., a numerical value) within a range of values.
As shown in
In
Referring now to
In
Audiogram interface 1232 includes option 1234 for choosing to use a selected audiogram to customize the audio settings and option 1236 for choosing not to use an audiogram to customize the audio settings. In
In
In
In
In
In some embodiments, the custom audio setup process includes two phases: 1) an amplification phase, and 2) a tone adjustment phase. In some embodiments, device 1200 uses the amplification phase to determine what volume a user can hear. In some embodiments, device 1200 uses the tone adjustment phase to determine what audio tones are preferred by a user. In some embodiments, device 1200 recommends one or more adjustments to the audio settings (e.g., tone balance, vocal clarity, brightness) based on the results of the two phases of the custom audio setup process. For example, device 1200 can recommend boosting tone balance slightly, moderately, or strongly. As another example, device 1200 can recommend boosting vocal clarity slightly, moderately, or strongly. As yet another example, device 1200 can recommend boosting brightness slightly, moderately, or strongly. In some embodiments, device 1200 can recommend adjustments to any combination of tone balance, vocal clarity, and brightness. In some embodiments, the tone adjustment phase determines whether adjustments are recommended for tone balance, vocal clarity, and/or brightness, based on the user's preferences. In some embodiments, the results of the amplification phase affect the tone adjustment phase. For example, in some embodiments, results of the amplification phase dictate whether a recommended tone adjustment is slight, moderate, or strong.
In
In
In the embodiment depicted in
In
In
In
In some embodiments, the setting of toggle selector 1246 persists until it is changed by a selection of the unselected toggle. For example, in
In
In response to detecting input 1254 in
Interface 1255-1 also includes volume slider 1258 for adjusting a volume of the audio being played at headphones device 1245. In some embodiments, the volume setting in interface 1255-1 is determined based on the results of the amplification phase. For example, if the amplification is moderate, the tab of volume slider 1258 is positioned in the middle as shown in
Each comparison interface includes a waveform providing a visual representation of the audio sample being produced at headphones device 1245. For example, in first comparison interface 1255-1, waveform 1260-1 represents the first version of the audio sample in the first comparison, and waveform 1260-2 (shown in
In
In
Device 1200 continues to produce music at headphones 1245 when displaying second comparison interface 1255-2. Second comparison interface 1255-2 is similar to first comparison interface 1255-1, but featuring at least one different audio sample. In
In some embodiments, the version of the audio selected in a previous comparison interface becomes one of the versions of the audio in a current comparison interface. For example, in second comparison interface 1255-2, the first version of the audio is the same as the first version of the audio selected in first comparison interface 1255-1. Alternatively, if the second version was selected in first comparison interface 1255-1, the selected version would be one of the options (e.g., the second version) in second comparison interface 1255-2.
In
In the embodiment illustrated in
Referring to
In
In
In some embodiments, the setting of toggle selector 1257 persists across different comparison interfaces. For example, in the embodiment shown in
Referring again to
In
In
In
In
In
In
Recommendation interface 1280 includes recommendation toggle selector 1282, which includes custom toggle 1282-1 and standard toggle 1282-2. When custom toggle 1282-1 is selected, device 1200 produces audio at headphones device 1245 having the recommended audio adjustments, as shown in
In
Recommendation toggle selector 1282 permits the user to toggle between the custom audio setting and the standard audio settings, to hear a preview of audio that features the custom or standard settings, helping the user to more efficiently decide whether they wish to apply the recommended customized audio settings, or instead use the standard audio settings.
Recommendation interface 1280 further includes custom settings affordance 1284-1 and standard settings affordance 1284-2. Custom settings affordance 1284-1 is selectable to apply the recommended custom audio settings and, in some embodiments, create a custom audio settings profile that can be used to apply the custom audio settings to other connected headphone devices. Standard settings affordance 1284-2 is selectable to apply the standard audio settings. In
Referring now to
Transparency mode interface 1286 also includes option 1286-4 for applying any setting changes that were made using sliders 1286-1, 1286-2, and 1286-3. In
Referring now to
In
In
In
In
As described below, method 1300 provides an intuitive way for customizing audio settings based on user preferences. The method reduces the cognitive burden on a user for customizing audio settings based on user preferences, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a user to customize audio settings faster and more efficiently conserves power and increases the time between battery charges.
In method 1300, the computer system (e.g., 1200) displays (1302), via the display generation component (e.g., 1202), an audio preference interface (e.g., 1255 (e.g., 1255-1; 1255-2; 1255-3); 1247; 1252), including concurrently displaying (1304) a representation (e.g., 1257-1) (e.g., an interface object (e.g., a selectable user interface object (e.g., an affordance))) of a first audio sample (e.g., 1260-1 in interface 1255-1 (e.g.,
While displaying (1308) (in some embodiments, subsequent to displaying) the audio preference interface (e.g., 1255 (e.g., 1255-1; 1255-2; 1255-3); 1247; 1252), the computer system (e.g., 1200) outputs (1310), via the audio generation component (e.g., 1245), at least a portion of the first audio sample (e.g., 1260-1 in interface 1255-1 (e.g.,
At 1314 of method 1300, after receiving the set of one or more inputs (e.g., 1266; 1268; 1272; 1273; 1274; 1275-1; 1275-2; 1276; 1277; 1278; 1283; 1285), the computer system (e.g., 1200) records (1316) (e.g., stores (e.g., locally and/or at a server)) (e.g., in response to receiving the set of one or more user inputs) a selection of the first audio sample as a preferred sample (e.g., input 1266 results in selection of the audio sample represented with waveform 1260-1 in interface 1255-1 (e.g.,
After receiving the one or more inputs (e.g., 1266; 1268; 1272; 1273; 1274; 1275-1; 1275-2; 1276; 1277; 1278; 1283; 1285), the computer system (e.g., 1200) outputs (1318), via the audio generation component (e.g., 1245), a first audio data (e.g., audio produced at headphones device 1245 (e.g., represented in some embodiments by the presence of sound graphic 1245-1)) (e.g., audio media (e.g., music, a voice recording, an audio component of audiovisual media)).
In accordance with the first audio sample (e.g., 1260-1 in interface 1255-1 (e.g.,
In accordance with the second audio sample (e.g., 1260-2 in interface 1255-1 (e.g.,
In some embodiments, after recording a selection of the first audio sample (e.g., 1260-1 in interface 1255-1 (e.g.,
In some embodiments, the third audio sample is the first audio sample (e.g., 1260-3 in interface 1255-2 (e.g.,
In some embodiments, the representation of the first audio sample (e.g., 1257-1), when selected while the first audio sample is not being outputted (e.g., see
In some embodiments, the first audio sample (e.g., audio associated with version one toggle 1257-1) and the second audio sample (e.g., audio associated with version two toggle 1257-2) are both based on a second audio data (e.g., audio produced at headphones device 1245 in, for example,
In some embodiments, at least one of the first audio sample or the second audio sample includes a spoken audio sample (e.g., audio that includes recorded human speech). In some embodiments, the audio preference interface includes a volume control interface when one or more of the audio samples include a spoken audio recording. In some embodiments, the audio preference interface does not include a volume control interface when one or more of the audio samples include a spoken audio recording.
In some embodiments, after recording the selection of the first audio sample as a preferred audio sample or the selection of the second audio sample as the preferred audio sample (in some embodiments, before outputting the first audio data), the computer system (e.g., 1200) displays, via the display generation component (e.g., 1202), a recommended audio adjustment interface (e.g., 1270; 1280) (e.g., the recommended audio adjustments are based, at least in part, on the recorded selection of the first or second audio sample as the preferred sample), including concurrently displaying a first audio preview interface object (e.g., 1282-1) corresponding to a recommended set of audio characteristics (in some embodiments, the recommended set of audio characteristics is selected based on at least the preferred sample recorded in response to the set of one or more inputs) and a second audio preview interface object (e.g., 1282-2) corresponding to a fifth set of audio characteristics, different than the recommended set of audio characteristics. In some embodiments, the fifth set of audio characteristics is a predefined set of audio characteristics (e.g., default or standard audio characteristics) that is not based on selections recorded using the audio preference interface. In some embodiments, the computer system receives, via the one or more input devices, a third set of one or more inputs (e.g., an input on 1282-1; 1283; 1285). In some embodiments, in response to receiving the third set of one or more inputs, and in accordance with a determination that the third set of one or more inputs includes a selection of the first audio preview interface object (e.g., an input on 1282-1; input 1285), the computer system outputs (in some embodiments, continues to output if output is already occurring based on the recommended set of audio characteristics) a third audio data (e.g., audio represented by waveform 1260-5) (e.g., a preview of output audio) based on (e.g., using) the recommended set of audio characteristics (e.g., the preview of output audio includes the recommended audio adjustments; the preview of output audio has customized audio settings applied to it). In some embodiments, in response to receiving the third set of one or more inputs, and in accordance with a determination that the third set of one or more inputs includes a selection of the second audio preview interface object (e.g., 1283), the computer system outputs (in some embodiments, continues to output if output is already occurring based on the fifth set of audio characteristics) the third audio data based on (e.g., using) the fifth set of audio characteristics (e.g., audio represented by waveform 1260-6) (e.g., the preview of output audio does not include the recommended audio adjustments; the preview of output audio has standard audio settings applied to it). Outputting the third audio data based on the recommended set of audio characteristics or the fifth set of audio characteristics, in response to the selection of the respective first or second audio preview interface object, permits the user to compare and contrast audio settings based on the recommended or fifth sets of audio characteristics without having to accept, decline, or modify the audio settings to compare playback of audio with the different characteristics, thereby reducing the number of inputs needed to set the audio settings. Reducing the number of inputs needed to perform an operation enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently. In some embodiments, the recommended audio adjustment interface permits the user to preview output audio having the recommended/customized audio settings enabled or disabled. In some embodiments, the recommended audio adjustment interface further includes a recommended interface object that, when selected, sets the recommended set of audio characteristics as the set of audio characteristics for later playback of audio data of at least a first type (e.g., audio media such as music or videos). In some embodiments, the recommended audio adjustment interface further includes an interface object that, when selected, sets the fifth set of audio characteristics as the set of audio characteristics for later playback of audio data of at least a first type (e.g., audio media such as music or videos). In some embodiments, the recommended audio adjustment interface includes an indication that no audio adjustments are recommended or needed (e.g., that the fifth set of audio characteristics will be used for later playback).
In some embodiments, the computer system (e.g., 1200) displays, via the display generation component (e.g., 1202), a selectable ambient sound amplification control (e.g., 1286; 1289). In some embodiments, the computer system receives an input (e.g., 1287; 1289-1; 1291-1; 1291-2; 1291-3; 1292; 1293) corresponding to the selectable ambient sound amplification control. In some embodiments, in response to the input corresponding to the selectable ambient sound amplification control, the computer system adjusts an audio characteristic (e.g., 1286-1; 1286-2; 1286-3; 1290-1; 1290-2; 1290-3; a noise control feature) (e.g., a volume, a balance, vocal clarity, brightness) of an ambient sound amplification function of the computer system (e.g., modifying a setting that affects future operation of the sound amplification function). In some embodiments, the audio generation component is a set of headphones (e.g., 1245) (e.g., over-the-ear or in-the-ear headphones) and the computer system is in communication with a microphone (e.g., integrated in the headphones) for detecting ambient sounds and is configured to amplify the detected ambient sounds using the audio generation component. In some embodiments, amplifying the ambient noise can permit the user to better hear the ambient sounds of the environment (e.g., without having to remove their headphones). In some embodiments, the audio characteristic of the ambient sound amplification function of the computer system is selected from the group consisting of amplification, balance, brightness, and a combination thereof.
In some embodiments, the computer system (e.g., 1200) displays (e.g., before or after display of the audio preference interface (e.g., 1255)), via the display generation component (e.g., 1202), a representation of an existing audio profile (e.g., 1233-1; 1233-2; 1215-4) (e.g., an audiogram, a record produced by a previous audiometry test). In some embodiments, the audiogram was provided by a medical institution. In some embodiments, the process for modifying output of audio playback based on an existing audio profile includes customizing audio settings based on the existing audio profile. In some embodiments, this includes displaying one or more representations of prior audiogram tests, receiving a selection of one of the representations of a prior audiogram test, and applying audio settings that are recommended based on the results of an audiogram test associated with the selected representation of a prior audiogram test. In some embodiments, the computer system receives a set of one or more inputs including an input corresponding to (e.g., a selection of) the representation of the existing audio profile. In some embodiments, in response to the set of one or more inputs including an input corresponding to the representation of the existing audio profile, the computer system initiates a process for configuring, based on the existing audio profile, one or more audio characteristics of audio playback (e.g., future audio playback of audio data). Initiating a process for configuring one or more audio characteristics of audio playback based on the existing audio profile allows a user to select custom audio settings that have been optimized based on the user's hearing capabilities without having to initiate the custom audio setup process, thereby reducing the number of inputs needed to create custom audio settings. Reducing the number of inputs needed to perform an operation enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
In some embodiments, the audio generation component (e.g., 1245) is a first external audio output device (e.g., a first set of headphones 1245). In some embodiments, after receiving the set of one or more user inputs, the computer system (e.g., 1200) generates a first audio settings profile (e.g., custom audio settings shown in
In some embodiments, the computer system (e.g., 1200) displays, via the display generation component (e.g., 1202), a set of one or more audio type controls (e.g., 1224) (e.g., toggle switches for different audio types (e.g., phone calls, media)). In some embodiments, the computer system receives a set of one or more inputs including an input directed to the set of one or more audio type controls (e.g., 1224-1; 1224-2) (e.g., a selection of a toggle switch for phone calls). In some embodiments, in response to receiving the set of one or more inputs including an input directed to the set of one or more audio type controls, and in accordance with a determination that the set of one or more inputs including an input directed to the set of one or more audio type controls includes a first input (e.g., the input corresponds to an activation of a first audio playback type control) (e.g., the input corresponds to an activation of the phone calls toggle switch), the computer system configures one or more audio characteristics of audio playback (e.g., future playback) of a first type (e.g., a first category of audio, a format of audio, a source of audio (e.g., phone calls, media, ambient sound amplification audio)) of audio (e.g., without configuring one or more audio characteristics of audio playback of a second type of audio (e.g., a different audio type)) (e.g., configuring one or more audio characteristics of audio playback for phone calls, without affecting/adjusting the audio characteristics of audio playback for other audio types (e.g., media, ambient sound amplification audio)). In some embodiments, in response to receiving the set of one or more inputs including an input directed to the set of one or more audio type controls, and in accordance with a determination that the set of one or more inputs including an input directed to the set of one or more audio type controls includes a second input different from the first input (e.g., the input is directed to a media toggle switch, rather than the phone calls toggle switch), the computer system configures one or more audio characteristics of audio playback of a second type of audio different from the first type of audio, without configuring one or more audio characteristics of audio playback of the first type of audio.
In some embodiments, the at least one audio characteristic of the first set of audio characteristics includes a volume amplification characteristic (e.g., a boosting of volume across all frequency ranges), and the at least one audio characteristic of the second set of audio characteristics includes the volume amplification characteristic (e.g., see amplification phase in
In some embodiments, the at least one audio characteristic of the first set of audio characteristics includes a frequency-specific volume amplification characteristic (e.g., 1215-1; 1215-2; 1215-3) (e.g., amplifying the volume of different frequency ranges differently), and the at least one audio characteristic of the second set of audio characteristics includes the frequency-specific volume amplification characteristic (e.g., see tone adjustment phase in
Note that details of the processes described above with respect to method 1300 (e.g.,
Referring briefly to
In
In
Referring to
In
In
In some embodiments, device 1400 displays the volume reduction of
After reducing the volume setting, device 1400 generates an alert that notifies the user that the volume of the output audio was reduced.
In
In some embodiments, the aggregate audio exposure limit (also referred to herein as an aggregate audio exposure threshold) represents a maximum amount of aggregated audio exposure that is not harmful to a user's hearing (e.g., the user's auditory system) when measured over a specific time period (e.g., a rolling seven-day window). In some embodiments, the aggregate audio exposure threshold is determined for a rolling seven-day window based on a combination of two primary factors: the volume of the audio a user is listening to using headphones (e.g., headphones device 1405), and the duration for which the user is exposed to the audio during the seven-day period (e.g., 24 minutes of the seven days). Accordingly, the louder the volume of the audio played at the headphones, the shorter the amount of time the user can be exposed to the audio without damaging their hearing. Similarly, the longer a user is exposed to headphone audio, the lower the volume at which the user can safely listen to the audio without damaging their hearing. For example, over a seven-day period, a user can safely listen to audio at 75 dB for a total of 127 hours. As another example, over a seven-day period, a user can safely listen to audio at 90 dB for a total of 4 hours. As yet another example, over a seven-day period, a user can safely listen to audio at 100 dB for a total of 24 minutes. As yet another example, over a seven-day period, a user can safely listen to audio at 110 dB for a total of 2 minutes. It should be recognized that other metrics may be used for the aggregate audio exposure threshold.
In
In
In
In
In
In
In
When the sound reduction feature is enabled, device 1400 displays maximum sound level user interface 1436 and applies a corresponding volume limit to the output volume for audio generated at headphones device 1405. Maximum sound level user interface 1436 includes slider 1436-1, numerical limit description 1436-2, and textual limit description 1436-3. Slider 1436-1 is adjustable to set the maximum sound level. Numerical limit description 1436-2 provides a numerical identification of the limit. Textual limit description 1436-3 provides a non-numerical description of the limit. In the example depicted in
Because the sound reduction feature is enabled, audio chart 1435 is modified to depict output limit 1438 having the 100 dB maximum sound level value set by slider 1436-1. Audio chart 1435 is also modified to depict the corresponding changes to the output volume of the audio signals generated at headphones device 1405. As shown in
In
In
Audio chart 1435 is also modified to depict the changed value of output limit 438 and the corresponding changes to the output volumes of the audio signals generated at headphones device 1405. As shown in
In
In
In
In some embodiments, device 1400 displays notification 1475 only the first time the connected device is recognized as being connected (e.g., if the device has a built-in identifier). In some embodiments, device 1400 displays notification 1475 each time the connected device is recognized as being connected (e.g., if the device does not have a built-in identifier). In some embodiments, device 1400 displays notification 1475 any time a connected device has not been explicitly identified as something other than headphones. In some embodiments, device 1400 automatically detects audio as being from a non-headphone speaker if a microphone of device 1400 detects audio that matches the audio being played on the connected device.
Referring now to
Referring now to
In
As described below, method 1500 provides an intuitive way for managing audio exposure by, for example, displaying audio exposure limit alerts. The method reduces the cognitive burden on a user for managing audio exposure, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a user to manage audio exposure faster and more efficiently conserves power and increases the time between battery charges.
In method 1500, while causing, via the audio generation component (e.g., 1405), output of audio data at a first volume (e.g., 1410-2) (e.g., volume setting 1414-1 in
In response (1504) to detecting that the audio exposure threshold criteria (e.g., 1410-1) has been met, the computer system (e.g., 1400; 1401), while continuing to cause output of audio data (e.g., at the audio generation component), reduces (1506) the volume of output of audio data to a second volume, lower than the first volume (e.g., volume 1410-2 decreases as shown in
In some embodiments, further in response to detecting that the audio exposure threshold criteria (e.g., 1410-1) has been met, the computer system (e.g., 1400; 1401) causes, via the audio generation component (e.g., 1405), output of an audible indication (e.g., a spoken indication, speech output) (in some embodiments, from a virtual assistant) indicating that the volume of output of audio data has been reduced. Causing output of an audible indication that the volume of output of audio data has been reduced provides feedback to the user that the change in output volume is intentional, rather than an error caused, for example, by poor connection quality of the headphones. Providing improved feedback enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
In some embodiments of method 1500, the computer system (e.g., 1400; 1401) outputs (1508) an alert (e.g., 1416; 1418) (e.g., a notification, a haptic response, an audio response, a banner) indicating that the volume of output of audio data has been reduced (e.g., the alert indicates that the volume has been reduced for recently output audio data). Outputting an alert indicating that the volume of output of audio data has been reduced provides feedback to the user that the change in output volume is intentional, rather than an error caused, for example, by poor connection quality of the headphones. Providing improved feedback enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
In some embodiments, the audio data (e.g., the volume of the audio data is represented using graph 1410) is generated from an application (e.g., a media application associated with media user interface 1408) (e.g., application 136 (a music application, a video application, a gaming application); a non-operating system software application) operating at the computer system (e.g., 1400; 1401), and the alert (e.g., 1416; 1418) is generated from a system-controlled (e.g., operating system-controlled) component of the computer system (e.g., operating system 126; haptic feedback module 133; graphics module 132) (e.g.,
In some embodiments, the computer system (e.g., 1400; 1401) is in communication with a display generation component (e.g., 1402; 1403) (e.g., a visual output device, a 3D display, a transparent display, a projector, a heads-up display, a display controller, a display device). In some embodiments, the computer system further comprises the display generation component. In some embodiments, outputting the alert (e.g., 1416; 1418) further includes that, in accordance with a determination that the audio exposure threshold criteria (e.g., 1410-1) is of a first type, (e.g., an instantaneous audio exposure threshold associated with toggle 1446), the computer system displays, via the display generation component, a first notification (e.g., 1416) corresponding to the audio exposure threshold of the first type (e.g., a notification containing text indicating the instantaneous audio exposure threshold was reached). In some embodiments, outputting the alert further includes that, in accordance with a determination that the audio exposure threshold criteria is of a second type different from the first type (e.g., an aggregate audio exposure threshold associated with toggle 1448), the computer system displays, via the display generation component, a second notification (e.g., 1418) corresponding to the audio exposure threshold of the second type and different from the first notification (e.g., a notification containing text indicating the aggregate audio exposure threshold was reached). Outputting the alert including displayed notifications corresponding to the type of audio exposure threshold provides feedback to the user indicating why the volume was reduced for different conditions, allowing the user to more easily and quickly understand and appreciate the purpose of the volume reduction. This potentially dissuades the user from raising the volume, thereby eliminating or reducing inputs associated with a command for subsequent volume increases. Reducing inputs and providing improved feedback enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently. In some embodiments, the first or second notification is displayed after or concurrently with reducing the volume of the output of audio data. In some embodiments, outputting the alert includes producing an audible chime (e.g., 1413). In some embodiments, the chime is output before or concurrently with the respective first or second notification.
In some embodiments, the computer system (e.g., 1400; 1401) is in communication with a display generation component (e.g., 1402; 1403) (e.g., a visual output device, a 3D display, a transparent display, a projector, a heads-up display, a display controller, a display device). In some embodiments, the computer system further comprises the display generation component. In some embodiments, the computer system receives an input directed to the alert (e.g., input 1420 on alert 1416) (e.g., an input on alert 1418) (e.g., a touch input on a notification displayed on the display generation component (e.g., input 1450 on notification 1451)) and, after (e.g., in response to) receiving the input directed to the alert, the computer system displays, via the display generation component, volume limit controls (e.g. 1422; 1430) corresponding to controlling output of audio data (e.g., output of current and/or future (anticipated) audio data) (e.g., a settings interface; a “Reduce Loud Sounds” user interface (a sound reduction interface)). In some embodiments, the alert includes displaying an aggregate audio exposure limit notification (e.g., 1418) or an instantaneous audio exposure limit notification (e.g., 1416). In some embodiments, after detecting an input on the aggregate or instantaneous audio exposure limit notification, the computer system displays, via display generation component, volume settings UI including the volume controls. In some embodiments, the alert includes displaying a tip banner (e.g., after two alerts have been previously generated). In some embodiments, after detecting an input on the tip banner, the computer system displays volume limit controls, including a “Reduce Loud Sounds” toggle affordance (e.g., 1432).
In some embodiments, the volume limit controls (e.g., 1430) include an affordance (e.g., 1432) (e.g., a graphical user interface object) (e.g., reduce loud sounds affordance; reduce sound levels menu option) that, when selected, toggles (e.g., enables or disables) a state of a process for reducing an anticipated output volume (e.g., a future output volume (e.g., the volume 1410-2 is reduced when compared to its anticipated volume 1410-3)) of output audio signals that exceed a selectable threshold value (e.g., 1410-1) (e.g., a volume limit set using the computer system or set by an external computer system such as a wearable device or a master device (e.g., a parent device that is authorized to set volume limits for the computer system)). In some embodiments, the audio exposure threshold criteria is met when the output of the audio data at the first volume exceeds the selectable threshold value (e.g., see
In some embodiments, displaying the volume limit controls (e.g., 1422) includes displaying at least one of: 1) a notification of an aggregate sound pressure limit (e.g., 1424-2) (e.g., a notification indicating that the aggregate audio exposure limit was reached), and 2) a notification of an instantaneous sound pressure limit (e.g., 1424-1) (e.g., a notification indicating that the instantaneous audio exposure limit was reached). Displaying volume limit controls including a notification of an aggregate sound pressure limit or instantaneous sound pressure limit provides feedback to the user indicating why the volume was reduced for different conditions, allowing the user to more easily and quickly understand and appreciate the purpose of the volume reduction. This potentially dissuades the user from raising the volume, thereby eliminating or reducing inputs associated with a command for subsequent volume increases. Reducing inputs and providing improved feedback enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
In some embodiments, displaying the volume limit controls (e.g., 1422) further includes displaying an affordance (e.g., 1478) (e.g., speaker toggle affordance) that, when selected, initiates a process for classifying (e.g., identifying) the audio generation component (e.g., 1405) as an audio generation component other than headphones (e.g., non-headphones (e.g., non-in-ear external speakers; stand-alone speakers)). In some embodiments, the affordance is displayed when the audio generation component is coupled (e.g., physically coupled) to the computer system (e.g., the audio generation component is plugged into the computer system), and is not displayed if the audio generation component is not coupled to the computer system. Displaying an affordance for classifying the audio generation component as an audio device other than headphones, depending on whether or not the device is coupled to the computer system, provides additional controls for identifying the audio generation component without cluttering the user interface with additional controls when they are not needed. Providing additional control options without cluttering the user interface with additional controls enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
In some embodiments, the volume limit controls (e.g., 1430) include an affordance (e.g., slider 1436-1) that, when selected, initiates a process for adjusting the audio exposure threshold criteria (e.g., a selectable threshold value that is used to determine when the audio exposure threshold criteria is met) (e.g., a volume limit set using the computer system or set by an external computer system such as a wearable device or a master device (e.g., a parent device that is authorized to set volume limits for the computer system)). Displaying an affordance for adjusting the audio exposure threshold criteria allows a user to quickly and easily adjust the audio threshold without having to navigate multiple user interfaces. Reducing the number of inputs needed to perform an operation enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently. In some embodiments, the slider is displayed when the “Reduce Loud Sounds” affordance (e.g., 1432) is activated. In some embodiments, the selectable threshold value sets a volume limit for audio signals comprising the output audio data, such that individual audio signals that are anticipated to exceed the volume limit are compressed at their peaks so as not to exceed the selected threshold value, without adjusting the remaining audio signals comprising the output audio data, as discussed in greater detail below with respect to
In some embodiments, the audio exposure threshold criteria is met when output of audio data (e.g., audio output at headphones device 1405 associated with graph 1410) (e.g., current output of the audio data and/or expected output of the audio data) (e.g., an average value of the output of audio data over a period of time) at the first volume exceeds an instantaneous sound pressure value (e.g., volume 1410-2 exceeds threshold 1410-1 in
In some embodiments, the audio exposure threshold criteria is met when an aggregate sound pressure value of output of audio data (e.g., audio output at headphones device 1405 associated with graph 1410) (e.g., current output of the audio data and/or expected output of the audio data) exceeds a threshold value (e.g., a dB limit; an aggregate sound pressure limit) for a duration (e.g., twenty-four minutes, when the volume is 100 dB) (e.g., a duration of time for which the threshold value is safe for a user's hearing health, when measured over a predetermined period of time (e.g., twenty-four minutes of a seven-day period)) measured over a predetermined period of time (e.g., seven days) (e.g., a day; a week; a period of time substantially greater than the amount of time used to determine the instantaneous exposure limit). In some embodiments, the audio exposure threshold is an aggregate audio exposure threshold, and the audio exposure criteria is criteria for determining an aggregate audio exposure limit (e.g., an aggregate exposure to a volume of output audio measured over a period of time such as, for example, a day or a week) has been reached. In some embodiments, the audio exposure threshold criteria (e.g., aggregate audio exposure limit) is met when the aggregate sound pressure level (volume) of the audio data output at the audio generation component (or a collection of audio generation components including the audio generation component) exceeds a first threshold level for a first duration (e.g., period of time) or exceeds a second threshold level (lower than the first threshold level) for a second duration (longer than the first duration). For example, the aggregate audio exposure limit is reached when the aggregate volume of the output audio data includes a volume of 90 dB for a duration of four hours measured over a seven-day period, or if the aggregate volume of the output audio data includes a volume of 100 dB for a duration of twenty-four minutes measured over the seven-day period. In some embodiments, the aggregated sound pressure value can be an aggregation of averaged values, such as an aggregation of instantaneous sound pressure values.
In some embodiments, after detecting that the audio exposure threshold criteria has been met, the computer system (e.g., 1400; 1401) performs the following. While causing, via the audio generation component (e.g., 1405), output of second audio data (e.g., audio produced at headphones device 1405) at a third volume, the computer system detects that an aggregate sound pressure value of output of second audio data (e.g., current output of the second audio data and/or expected output of the second audio data) exceeds a predetermined multiplier (e.g., 1×, 2×) of the aggregate audio exposure threshold value over the predetermined period of time (e.g., 200%, 300% of the aggregate exposure limit for the predetermined period of time (e.g., a day; a week)). In response to detecting that the aggregate sound pressure value of output of second audio data exceeds the predetermined multiplier of the aggregate audio exposure threshold value over the predetermined period of time, the computer system performs the following: 1) while continuing to cause output of second audio data, reducing the volume of output of the second audio data to a fourth volume (e.g., volume 1410-2 is reduced in
In some embodiments, reducing the volume of output of audio data (e.g., see
In some embodiments, the computer system (e.g., 1400; 1401) is in communication with a display generation component (e.g., 1402; 1403) (e.g., a visual output device, a 3D display, a transparent display, a projector, a heads-up display, a display controller, a display device). In some embodiments, the computer system further comprises the display generation component. In some embodiments, in response to detecting that the audio exposure threshold criteria (e.g., 1410-1) has been met, the computer system displays, via the display generation component, a representation of volume (e.g., volume interface 1414) of output of audio data (e.g., audio produced at headphones device 1405) (e.g., having a first volume setting corresponding to the first volume (e.g., 1414-1 in
In some embodiments, the representation of volume of output of audio data (e.g., 1414) includes a graphical element (e.g., 1414-2) indicating a volume that exceeds predetermined safety criteria (e.g., loud) output volume (e.g., 1410-1). Displaying the representation of the volume including a graphical element indicating the volume exceeds predetermined safety criteria for the output volume provides feedback to the user indicating why the volume was reduced, allowing the user to more easily and quickly understand and appreciate the purpose of the volume reduction. This potentially dissuades the user from subsequently raising the volume, thereby eliminating or reducing inputs associated with a command for subsequent volume increases. Reducing inputs and providing improved feedback enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently. In some embodiments, the graphical element is displayed above the volume indicator. In some embodiments, the graphical element is displayed when the current output volume is at a maximum volume setting represented with the volume indicator and the volume of the output audio is greater than a threshold volume (e.g., 80 dB).
In some embodiments, displaying the representation of volume of output of audio data (e.g., 1414) includes displaying an animation of the representation of volume of output of audio data transitioning from a first visual state that corresponds to the first volume (e.g., 1414-1 in
In some embodiments, the computer system (e.g., 1400; 1401) is in communication with a second audio generation component (e.g., 1405-1 in
In some embodiments, in accordance with a determination that the computer system (e.g., 1400; 1401) is in communication with (e.g., coupled to; the second audio generation component is plugged into the computer system) the second audio generation component (e.g., 1405-1) a first time, the computer system prompts (e.g., 1475) a user of the computer system to indicate an audio generation component type of the second audio generation component (e.g., display a notification requesting the user to identify the second audio generation component as speaker or not a speaker). In some embodiments, in accordance with a determination that the computer system is in communication with the second audio generation component a subsequent time, the computer system forgoes prompting a user of the computer system to indicate the audio generation component type of the second audio generation component. Prompting the user to indicate an audio generation component type of the audio generation component when it is in communication with the computer system a first time, but not a subsequent time, allows the user to indicate the device type without excessively prompting the user, thereby eliminating inputs to subsequent prompts. Reducing the number of inputs enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently. In some embodiments, the computer system prompts the user to indicate whether an audio generation component is a headphone or non-headphone speaker the first time the audio generation component is connected to the computer system, but not thereafter, if the audio generation component has a built-in identifier.
In some embodiments, in response to establishing the communication (e.g., coupling; the second audio generation component is plugged into the computer system) with the second audio generation component (e.g., 1405-1), the computer system (e.g., 1400; 1401) prompts (e.g., 1475) a user of the computer system to indicate an audio device type for the second audio generation component (e.g., display a notification requesting the user to identify the second audio generation component as speaker or not a speaker). In some embodiments, the computer system prompts the user to indicate whether an audio generation component is a headphone or non-headphone speaker every time the audio generation component is connected to the computer system, if the audio generation component does not have a built-in identifier.
In some embodiments, the computer system (e.g., 1400; 1401) includes an audio input device (e.g. 1406) (e.g., a microphone). In some embodiments, the computer system detects an audio generation component type for the second audio generation component (e.g., 1405-1) based on an input received at the audio input device while the computer system is causing output of audio data via the second audio generation component. In some embodiments, the computer system automatically detects an audio generation component is a speaker if a microphone of the computer system detects audio that matches the audio the computer system is causing to be output at the audio generation component.
In some embodiments, while the computer system (e.g., 1400; 1401) is in communication with the second audio generation component (e.g., 1405-1), the computer system detects a first input (e.g., 1476; an input on 1469) corresponding to a request to display an audio settings interface and, in response to detecting the first input, the computer system displays the audio settings interface (e.g., 1422 in
In some embodiments, in accordance with a determination that the second audio generation component (e.g., 1405-1) is not identified as an audio generation component of the second type (e.g., the second audio generation component is identified as potentially not headphones; the audio generation component has not been explicitly identified as something other than headphones (e.g., a speaker)), the computer system (e.g., 1400; 1401) prompts (e.g., 1475; 1477) a user of the computer system to indicate whether the second audio generation component is an audio generation component of the second type (e.g., display a notification requesting the user to identify the second audio generation component as headphones or not headphones).
In some embodiments, in accordance with a determination that the second audio generation component (e.g., 1405-1) is indicated as an audio generation component of the first type (e.g., non-headphones (e.g., non-in-ear external speakers; stand-alone speakers)), the computer system (e.g., 1400; 1401) prompts (e.g., 1475; 1477) the user to confirm the second audio generation component is an audio generation component of the first type after a predetermined period of time. In some embodiments, if the user indicates the second audio generation component is not headphones, the computer system prompts the user to confirm this indication after a period of time has passed such as, for example, two weeks.
In some embodiments, the audio exposure threshold criteria includes a criterion that is met when the audio generation component (e.g., 1405) is a headphones device (e.g., in-ear or over-ear headphones). In some embodiments, only audio output via headphones is subject to the audio exposure limits. In some embodiments, the headphones device is configured to have an output volume limit (e.g., 1438) that is less than a maximum output volume of the headphones device (e.g., a measure of loudness, a sound pressure level (e.g., 100 dB)). Configuring the headphones device to have an output volume limit that is less than a maximum output volume of the headphones device provides safety measures to protect a user's sense of hearing by implementing volume limits, which are generally less than the maximum volume limits of a headphones device and can vary to meet safety requirements based on the user's listening habits. Providing these safety measures when a set of conditions has been met without requiring further user input enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
In some embodiments, while (in some embodiments, after) the computer system (e.g., 1400; 1401) causes output of audio data at the second volume, (and, in some embodiments, while the audio exposure threshold criteria is met), the computer system receives an input corresponding to a request to increase the volume of output of audio data and, in response to receiving the input corresponding to the request to increase the volume of output of audio data, the computer system increases the volume of output of audio data to a seventh volume, greater than the second volume. In some embodiments, the seventh volume is the first volume. In some embodiments, by increasing the volume of output audio in response to an input received after the volume was reduced, the computer system permits the user to override the volume reduction that was caused in response to detecting that the audio exposure criteria was met.
In some embodiments, the audio exposure threshold criteria includes a criterion that is met when the audio data is media playback (e.g., music, games, videos). In some embodiments, the audio exposure limits apply to media playback, but not to other sound sources of the computer system such as, for example, system sounds, phone audio, and video chat audio.
In some embodiments, the computer system (e.g., 1400; 1401) is in communication with a display generation component (e.g., 1402; 1403) (e.g., a visual output device, a 3D display, a transparent display, a projector, a heads-up display, a display controller, a display device). In some embodiments, the computer system further comprises the display generation component. In some embodiments, while the computer system causes output of audio data, the computer system displays, via the display generation component, an audio controls user interface (e.g., 1480). In some embodiments, the audio controls user interface includes an audio exposure indicator (e.g., 1482) indicative of an audio exposure level (e.g., the sound pressure level (e.g., volume)) associated with a current volume of output of audio data. In some embodiments, the current volume of the output audio is indicated (e.g., by an icon and/or color) to be a safe, loud, or hazardous audio exposure level. Displaying an audio controls user interface including an audio exposure indicator indicative of an audio exposure level associated with a current volume of output of audio data provides feedback to the user whether the current audio levels are safe or potentially hazardous. Providing improved feedback enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
In some embodiments, displaying the audio controls user interface (e.g., 1480) includes, in accordance with a determination that the current volume of output of audio data does not exceed a first volume threshold (e.g., a low noise threshold), displaying the audio exposure indicator (e.g., 1482) having a first color (e.g., see
In some embodiments, the computer system (e.g., 1400; 1401) detects an input (e.g., 1484) directed to the audio exposure indicator (e.g., 1482) and, in response to detecting the input directed to the audio exposure indicator, the computer system displays, via the display generation component (e.g., 1402; 1403), an audio exposure user interface (e.g., 1485). In some embodiments, the audio exposure user interface includes a measurement of audio exposure data associated with output of audio data (e.g., 1485-3) (e.g., current output of audio data). In some embodiments, the audio exposure UI includes an audio exposure meter that illustrates a real time measurement of the current audio exposure caused by the headphones currently outputting the audio. Displaying an audio exposure interface including a measurement of audio exposure data associated with output of audio data provides feedback to the user of whether the current audio levels are safe or hazardous. Providing improved feedback enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
In some embodiments, the audio exposure user interface (e.g., 1485) further includes an identification (e.g., 1485-1) (e.g., a device name) of the audio generation component (e.g. 1405).
In some embodiments, the audio exposure user interface (e.g., 1485) further includes an affordance (e.g., 1485-2) that, when selected, initiates a process for causing output of ambient audio at the audio generation component (e.g., 1405). In some embodiments, the output of ambient audio includes enabling a microphone at the computer system, receiving ambient audio at the microphone, amplifying the ambient audio, and outputting the amplified ambient audio at the audio generation component. This permits the user to hear audio from their environment, without having to remove their headphones.
Note that details of the processes described above with respect to method 1500 (e.g.,
As described below, method 1600 provides an intuitive way for managing audio exposure by, for example, setting and adjusting audio settings. The method reduces the cognitive burden on a user for managing audio exposure, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a user to manage audio exposure faster and more efficiently conserves power and increases the time between battery charges.
In method 1600, the computer system (e.g., 1400) receives (1602) (e.g., detects) output audio data (e.g., signals S1, S2, S3) (e.g., data indicating an output volume) associated with output audio generated using the audio generation component (e.g., 1405) (e.g., the headphones are currently generating output audio (e.g., music, videogame audio, video playback audio)). The output audio comprises a first audio signal (e.g., signal S1; signal S3 in some embodiments) (e.g., a first sound) and a second audio signal (e.g., signal S2) (e.g., a second sound different from the first sound; a set of signals/sounds different from the first audio signal). The output audio data includes a first anticipated output audio volume for the first audio signal (e.g., S1 and S1A in audio chart 1435) and a second anticipated output audio volume for the second audio signal (e.g., S2 and S2A in audio chart 1435).
In method 1600, in accordance with a determination (1604) that the output audio data (e.g., signals S1, S2, S3) satisfies a first set of criteria, the computer system (e.g., 1400) causes (1606) (e.g., reduces) output of the first audio signal (e.g., S1) at a reduced output audio volume (e.g., in
In some embodiments, the output audio volume threshold (e.g., 1438) corresponds to a volume control setting (e.g., 1436; 1432; 1430) (e.g., a “reduce loud sounds” setting) associated with a user account (e.g., John's account), and the volume control setting is applied at the computer system (e.g., 1400) (e.g., a smartphone associated with the user account (e.g., John's phone)) and an external computer system (e.g., 1401) (e.g., an electronic device separate from the computer system; e.g., a wearable device) associated with the user account (e.g., John's watch). In some embodiments, the volume control setting applies across multiple devices such as, for example, different electronic devices linked with a user account. Applying the volume control setting at the computer system and an external computer system associated with the user account reduces the number of inputs needed to efficiently apply a volume control setting across multiple devices. Reducing the number of inputs needed to perform an operation enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
In some embodiments, the computer system (e.g., 1400; 1401) is associated with a first user account (e.g., John's account) (e.g., a child account) and the output audio volume threshold (e.g., 1438) is determined (e.g., set) by a second user account (e.g., Mom's account) (e.g., a parent account) (e.g., a user account different than the first user account) associated with an external computer system (e.g., 1400A) (e.g., an electronic device separate from the computer system; e.g., a parent device) and authorized (e.g., by the child account) to enable the output audio volume threshold at the computer system. In some embodiments, the volume control settings are accessible from a different user account (e.g., a parent account) than that which is associated with using the computer system (e.g., a child account).
In some embodiments, the first set of criteria includes a criterion that is satisfied when the output audio (e.g., signals S1, S2, S3) is media playback (e.g., music, games, videos). In some embodiments, the volume reduction limits apply to media playback, but not to other sound sources of the computer system (e.g., 1400) such as, for example, system sounds, phone audio, and video chat audio.
In method 1600, in accordance with a determination (1610) that the output audio data (e.g., signals S1, S2, S3) does not satisfy the first set of criteria (e.g., neither the output audio volume for the first audio signal, nor the output audio volume for the second audio signal (e.g., the output audio data does not satisfy a second set of criteria), exceeds the predefined output audio volume (e.g., 1438) (e.g., the maximum output volume limit)), the computer system (e.g., 1400; 1401) causes (1612) output of the first audio signal at the first anticipated output audio volume and causes (1614) output of the second audio signal at the second anticipated output audio volume (e.g., in
In some embodiments, in accordance with a determination that the output audio data (e.g., signals S1, S2, S3) satisfies a second set of criteria (e.g., while the output audio data does not satisfy the first set of criteria), the computer system (e.g., 1400; 1401) causes output of the first audio signal (e.g., signal S3) at the first anticipated output audio volume (e.g., the first audio signal is played at the requested (anticipated) output audio volume for the first audio signal, while the output audio volume for the second audio signal (e.g., S2) is limited (e.g., capped) at the maximum output volume limit) and causes (e.g., reducing) output of the second audio signal (e.g., S2) at a reduced output audio volume (e.g., S2 is capped at 90 dB in audio chart 1435 of
In some embodiments, the computer system (e.g., 1400; 1401) includes a display generation component (e.g., 1402; 1403) (e.g., a display controller, a touch-sensitive display system) and one or more input devices (e.g., a touch-sensitive surface of 1402; a touch-sensitive surface of 1403). In some embodiments, the computer system displays, via the display generation component, a volume control interface object (e.g., 1436) (e.g., slider 1436-1) representing a range of threshold values (e.g., 75-100 dB) for the output audio volume threshold (e.g., 1438) and detects, via the one or more input devices, an input (e.g., 1440) corresponding to the volume control interface object. In some embodiments, in response to detecting the input corresponding to the volume control interface object, the computer system adjusts the output audio volume threshold (e.g., 1438) (e.g., the maximum output volume limit) from a first threshold value (e.g., 100 dB in
In some embodiments, while displaying the volume control interface object (e.g., 1436) (e.g., slider 1436-1) representing the output audio volume threshold (e.g., 1438) having the first threshold value (e.g., 100 dB in
In some embodiments, the first set of criteria further includes a first criterion that is satisfied when a volume control setting (e.g., 1432) (e.g., a “reduce loud sounds” setting) is enabled. In some embodiments, the volume control setting is set/enabled/disabled using the computer system (e.g., 1400) (e.g., an electronic device) or using an external computer system (e.g., an external electronic device such as a wearable device (e.g., 1401) or a master device (e.g., 1400A) (e.g., a parent device that is authorized to set/enable/disable volume limits for the computer system). In some embodiments, in accordance with a determination that the output audio data (e.g., signals S1, S2, S3; audio produced at headphones device 1405 in
In some embodiments, the output audio (e.g., signal S1, S2, S3) further comprises a fifth audio signal and the output audio data further includes a fifth anticipated output audio volume (e.g., a low volume) for the fifth audio signal. In some embodiments, in accordance with a determination that the output audio data satisfies the first set of criteria, the computer system (e.g., 1400; 1401) causes output of the fifth audio signal at an increased output audio volume that is greater than the fifth anticipated output audio volume (e.g., the fifth audio signal is output at an increased volume, while the first audio signal is output at a reduced volume and the second audio signal is output at the requested (anticipated) volume). In some embodiments, the lower the output audio volume threshold, the more the quiet sounds are increased.
In some embodiments, the output audio volume threshold (e.g., 1438) is a first value (e.g., 100 dB in
In some embodiments, the second reduced output audio volume for the first audio signal is the same as the first reduced output audio volume for the first audio signal. In some embodiments, the second reduced output audio volume for the first audio signal is different than the first reduced output audio volume for the first audio signal.
In some embodiments, the output audio volume threshold (e.g., 1438) is a third value (e.g., 90 dB in
Note that details of the processes described above with respect to method 1600 (e.g.,
In some embodiments, audio exposure data is recorded at device 1700 based on detected output volume of audio that is output at device 1700 (e.g., output to a headphones device) or a headphones device (e.g., headphones 1405 as described above) that is in communication with (e.g., playing audio from) device 1700 or an external device (e.g., device 1401 as described above). In some embodiments, audio exposure data is recorded at device 1700 based on ambient sound detected by a sensor such as a microphone (e.g., microphone 1406). In some embodiments, audio exposure data is noise level data, such as that discussed above with respect to
In
Audio exposure graph 1708 provides a simple illustration of the audio exposure data to indicate the audio conditions that triggered the instantaneous audio exposure alert. In the embodiment shown in
As shown in
Exposure indicator 1716 indicates whether the aggregate of the audio exposure data in graph 1714 is safe (e.g., not accumulating loud audio), loud (e.g., accumulating loud audio, but currently not too loud), or hazardous (e.g., too loud). In some embodiments, indicator 1716 is shown with a green checkmark when the exposure level is safe, with a yellow warning sign when the exposure level is loud, and with a red warning sign when the exposure level is hazardous.
Instantaneous filter option 1718 is associated with an instantaneous audio exposure threshold of 100 dB, and is selectable to modify the appearance of audio exposure data 1714-1 in order to highlight instances in which a notification or alert was generated in response to the audio exposure data exceeding the 100 dB threshold. Instantaneous filter option 1718 includes notification count 1718-1, indicating that one instantaneous audio exposure notification was generated based on audio exposure data 1714-1. In some embodiments, audio exposure interface 1712 includes various filter options that are shown when the displayed audio exposure data includes data corresponding to the various filter options. Conversely, these various filter options are not shown when they do not apply to the displayed audio exposure data. For example, if no instantaneous audio exposure alerts were generated for audio exposure data 1714-1, instantaneous filter option 1718 would not be displayed.
As shown in
As shown in
As shown in
As discussed in greater detail below, aggregate filter option 1728 can be selected to update audio exposure data 1714-2 with an indication of when audio exposure data 1714-2 exceeded the aggregate audio exposure limit and a corresponding aggregate audio exposure alert was generated.
In
Audio status text 1736 indicates a status of aggregate audio exposure for the user represented by aggregate audio exposure graph 1738. In the current embodiment, audio status text 1736 indicates that an aggregate of the user's audio exposure is approaching an aggregate audio exposure limit for a seven-day period.
Audio exposure graph 1738 represents an aggregate of recent audio exposure (e.g., measured from recent audio exposure data) over a current seven-day period (e.g., a rolling seven day window). Audio exposure graph 1738 includes aggregate audio exposure measurement 1738-1, aggregate audio exposure threshold 1738-2, and date range 1738-3 indicating the seven-day period during which the aggregate of the audio exposure data is measured. Aggregate audio exposure measurement 1738-1 is shown relative to aggregate audio exposure threshold 1738-2. Audio exposure graph 1738 provides a simple illustration of the aggregate audio exposure measured over the seven-day period, relative to the aggregate audio exposure limit.
In some embodiments, aggregate audio exposure measurement 1738-1 is calculated over a rolling seven-day period. As the user is exposed to headphone audio (e.g., the user is listening to audio using headphones) over the seven-day period, the measured aggregate audio exposure fluctuates based on the amount of audio exposure being added in the frontend of the rolling-seven day window (e.g., audio exposure measured today), and the amount of audio exposure dropping off the backend of the rolling window (e.g., audio exposure measured May 21). In some embodiments, the rolling seven-day window is measured in fifteen-minute increments. In some embodiments, the aggregate audio exposure measurement 1738-1 calculates exposure from audio produced at headphones (e.g., across all sets of headphone devices that are used with device 1700). Accordingly, the aggregate audio exposure does not factor in audio exposure from a non-headphone audio device such as, for example, an external speaker.
Aggregate audio exposure threshold 1738-2 represents a threshold amount of aggregated audio exposure measured over a seven-day window that is not harmful to a user's hearing (e.g., the user's auditory system). In some embodiments, aggregate audio exposure threshold 1738-2 is determined for the rolling seven-day window based on a combination of two primary factors: the volume of the audio a user is listening to using headphones (represented herein as the audio exposure data (e.g., audio exposure data 1744-1, discussed below)), and the duration for which the user is exposed to the audio. Accordingly, the louder the volume of the audio played at the headphones, the shorter the amount of time the user can be exposed to the audio without damaging their hearing. Similarly, the longer a user is exposed to headphone audio, the lower the volume at which the user can safely listen to the audio without damaging their hearing. For example, over a seven-day period, a user can safely listen to audio at 75 dB for a total of 127 hours. As another example, over a seven-day period, a user can safely listen to audio at 90 dB for a total of 4 hours. As yet another example, over a seven-day period, a user can safely listen to audio at 100 dB for a total of 24 minutes. As yet another example, over a seven-day period, a user can safely listen to audio at 110 dB for a total of 2 minutes.
The state of the user's aggregate audio exposure relative to this threshold is represented by aggregate audio exposure graph 1738. In the embodiment shown in
Referring now to
As shown in
Audio exposure interface 1742 is similar to audio exposure interface 1712 shown in
Graph 1744 illustrates headphone audio exposure data 1744-1 over a selectable period of time. In
Audio exposure data 1744-1 includes audio exposure data that triggered four aggregate audio exposure alerts (e.g., 1418) by exceeding the seven-day aggregate exposure threshold four times from Apr. 29, 2019 to May 28, 2019. Accordingly, aggregate filter option 1748 is shown with notification count 1748-1 having a value of four.
As shown in
Alert indicator 1751 indicates that an aggregate audio exposure alert was generated on approximately May 12, 2019, based on an aggregate of the audio exposure data from that date, and the previous six days, exceeding the aggregate audio exposure threshold. Alert indicator 1752 indicates that an aggregate audio exposure alert was generated on approximately May 19, 2019, based on an aggregate of the audio exposure data from that date, and the previous six days, exceeding the aggregate audio exposure threshold. Alert indicator 1753 indicates that an aggregate audio exposure alert was generated on approximately May 22, 2019, based on an aggregate of the audio exposure data from that date, and the previous six days, exceeding the aggregate audio exposure threshold. Alert indicator 1754 indicates that an aggregate audio exposure alert was generated on approximately May 28, 2019, based on an aggregate of the audio exposure data from that date, and the previous six days, exceeding the aggregate audio exposure threshold.
Because the aggregate audio exposure is measured over a rolling seven-day period, in some instances audio exposure data 1744-1 can include a subset of audio exposure data that triggers more than one aggregate audio exposure alert. For example, subset 1744-1a is a subset of the audio exposure data that triggered an aggregate audio exposure alert represented by alert indicator 1752. Subset 1744-1a is also a subset of the audio exposure data that triggered an aggregate audio exposure alert represented by alert indicator 1753.
In
As shown in
Hearing interface 1764 includes various options for accessing audio data. For example, as shown in
As shown in
Alert listing 1770 is a list of items 1771 representing the alerts device 1700 generated during the past twelve months. Each item 1771 includes date 1772 indicating when the respective alert was generated and alert type 1774 indicating whether the respective alert was an instantaneous audio exposure alert (e.g., a 100 dB limit alert) or an aggregate audio exposure alert (e.g., a seven-day aggregate limit alert).
As shown in
Sound data interface 1780 includes a listing of recorded sound levels and alerts, and a timestamp for the respective item. For example, item 1780-1 represents an 84 dB sound recorded at 8:46 PM on May 28th. Item 1780-2 represents a seven-day aggregate limit alert generated at 8:16 PM on May 28th. Item 1780-3 represents a 100 dB limit alert generated at 7:46 PM on May 28th.
As shown in
Audio details interface 1784 displays various details associated with the item selected from sound data interface 1780. For example, in the present embodiment, item 1780-3 corresponding to a 100 dB limit alert was selected from interface 1780. Accordingly, audio details interface 1784 includes audio sample details 1785 related to the alert, and device details 1786 related to the alert. Audio sample details 1785 include, for example, a start and stop time of the audio sample that triggered the alert, the source of the audio sample that triggered the alert, the date item 1780-3 was added to interface 1780, and details of the alert such as the notification sound level and an indication of whether this was the first, second, third, iteration of the respective alert. For example, if the alert was an aggregate exposure limit alert, audio sample details 1785 can indicate whether the respective alert was the alert generated at the first multiple of the aggregate audio exposure threshold (e.g., 1×), second multiple of the threshold (e.g., 2×), or third multiple of the threshold (e.g., 3×). Data interface 1780 also includes device details 1786 indicating details for the device that generated the alert.
As shown in
In
In
Settings interface 1795 includes option 1795-1, which can be selected to change a duration for storing headphone audio exposure data. As shown in
Settings interface 1795 also includes option 1795-2, which can be selected to delete audio exposure data older than eight days. Selecting this option preserves the current rolling seven-day window of audio exposure data, while deleting audio exposure data that is outside this window.
Settings interface 1795 also includes option 1795-3, which can be selected to delete all audio exposure data, including the audio exposure data within the current rolling seven-day window. As shown in
As described below, method 1800 provides an intuitive way for managing audio exposure data. The method reduces the cognitive burden on a user for managing audio exposure data, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a user to manage audio exposure data faster and more efficiently conserves power and increases the time between battery charges.
In method 1800, the computer system receives (1802), via the one or more input devices, an input corresponding to a request to display audio exposure data (e.g., in the Health app from the Summary tab; in the Hearing user interface accessed from the Browse tab).
In response to receiving the input corresponding to the request to display audio exposure data, the computer system displays (1804) (e.g., concurrently displaying), via the display generation component, an audio exposure interface including, concurrently displaying: (1806) an indication of audio exposure data (e.g., a graphical representation of data indicating an output volume generated at an audio generation component (e.g., headphones) over a period of time (e.g., hour, day, week, month, year); e.g., a graphical representation of noise level data (e.g. data from a sensor of the computer system; data from an external computer system), as discussed above with respect to any of
In some embodiments, the audio exposure interface further includes a second visual indication of a second alert provided as a result of a second audio exposure value (e.g., different from the first audio exposure value) exceeding the audio exposure threshold (e.g., an instantaneous exposure threshold; an aggregate exposure threshold). The second visual indication of the second alert includes an indication of a time at which the second alert was provided (e.g., different from the time at which the first alert was provided), wherein the second visual indication is different from the first visual indication.
In some embodiments, displaying the indication of audio exposure data over the first period of time (e.g., a week) includes: 1) displaying a first subset of the audio exposure data corresponding to a first subset of the first period of time (e.g., audio data for a first day of the week) and including the first audio exposure value (e.g., the first audio exposure value exceeded the audio exposure threshold on the first day of the week), and 2) displaying a second subset of the audio exposure data corresponding to a second subset of the first period of time (e.g., audio data for a second day of the week) that includes the second audio exposure value (e.g., the second audio exposure value exceeded the audio exposure threshold on the second day of the week). In some embodiments, the first visual indication of the first alert is displayed with (e.g., as a part of) the first subset of the audio exposure data (e.g., the first visual indication of the first alert is positioned on the audio exposure data for the first day of the week). In some embodiments, the second visual indication of the second alert is displayed with (e.g., as a part of) the second subset of the audio exposure data (e.g., the second visual indication of the second alert is positioned on the audio exposure data for the second day of the week).
In some embodiments, the audio exposure interface includes an indication of one or more days that the first alert (e.g., an alert generated in response to output audio exceeding an instantaneous audio exposure limit or an aggregate audio exposure limit; an alert generated in response to noise level data exceeding an audio exposure limit (e.g., a noise level limit)) was provided (e.g., received at the computer system). In some embodiments, the indication of the time at which the first alert was provided is an indication of a day at which the first alert was provided (e.g., received at the computer system).
In some embodiments, the indication of audio exposure data includes a representation of audio exposure data aggregated over the first period of time. In some embodiments, the representation of aggregate audio exposure is a graph illustrating the aggregate audio exposure for a seven-day period.
In some embodiments, the representation of audio exposure data aggregated over the first period of time includes a graphical representation of the aggregated audio exposure data displayed over the first period of time (e.g., seven days) relative to an indication of the audio exposure threshold (e.g., an indication of the aggregate audio exposure limit). In some embodiments, the graphical representation of the aggregated audio exposure data is displayed without regard to whether an alert has been provided for exceeding an aggregated audio exposure limit (e.g., the graphical representation is displayed even if no alerts have been provided for exceeding the aggregated audio exposure limit). In some embodiments, the graphical representation includes an indication of the aggregate audio exposure limit. In some embodiments, the graphical representation provides a snapshot view of the aggregated audio exposure data relative to the aggregate audio exposure limit. For example, the snapshot view may show the aggregated audio exposure data is below the aggregate audio exposure limit. As another example, the snapshot view may show the aggregated audio exposure data is above the aggregate audio exposure limit. In some embodiments, the aggregated audio exposure data is updated in real time and calculated on a rolling basis (e.g., every fifteen minutes).
In some embodiments, the aggregated audio exposure data is calculated on a repeating schedule (e.g., calculated every fifteen minutes for the predetermined period of time). In some embodiments, the audio exposure data is aggregated every fifteen minutes for a seven-day period. Accordingly, the seven-day period is comprised of approximately 672 fifteen-minute intervals over which the audio exposure data is aggregated. As a new fifteen-minute interval is added to the seven-day window, the oldest fifteen-minute interval is removed, and the audio exposure data is recalculated (e.g., aggregated) for the seven-day window. For example, if the audio exposure data for the most recent fifteen-minute interval indicates a greater audio exposure level than the audio exposure data for the oldest fifteen-minute interval that is no longer included in the seven-day window, the aggregated audio exposure data indicates an increase in aggregated audio exposure during the seven-day window. Accordingly, the aggregated audio exposure data adjusts/updates (e.g., increases, decreases, remains constant) every fifteen minutes based on the audio exposure levels that are being added to, and removed from, the seven-day window.
In some embodiments, the first audio exposure value corresponds to an aggregate audio exposure value over a period of time. In some embodiments, the first visual indication includes an indication of the period of time of the aggregate audio exposure that corresponds to the first alert. In some embodiments, when the alert is generated in response to exceeding an aggregate audio exposure limit, the audio exposure UI displays the seven-day period of audio exposure data that triggered the alert. In some embodiments, the audio exposure interface is displayed as a notification that the audio exposure data is approaching or has exceeded the seven-day aggregate audio exposure limit.
In some embodiments, displaying the audio exposure interface further includes displaying a user interface object including an indication of a sum of alerts (e.g., alerts of a first or second type) (e.g., alerts generated in response to exceeding an instantaneous audio exposure limit, or alerts generated in response to exceeding an aggregate audio exposure limit) provided during the first period of time. In some embodiments, the user interface object is an affordance (e.g., a filter affordance) that, when selected, alters the appearance of the audio exposure data to include the visual indications of the alerts generated during the first period of time (e.g., hour, day, week, month, year). In some embodiments the affordance indicates the number of alerts that were generated during the first period of time.
In some embodiments, the sum of alerts includes a sum of alerts generated in response to exceeding an aggregate audio exposure limit (e.g., the audio exposure threshold). In some embodiments, the user interface object further includes an indication of a type of alert associated with the sum of alerts provided during the first period of time (e.g., wherein the type of alert is an alert generated in response to exceeding an aggregate audio exposure limit).
In some embodiments, the computer system receives, via the one or more input devices, an input corresponding to a request to display a listing of audio exposure alerts and, in response to receiving the input corresponding to the request to display a listing of audio exposure alerts, the computer system displays a list that includes (e.g., as part of the audio exposure interface; separate from the audio exposure interface): 1) an indication of a first audio exposure alert (e.g., the first alert) provided as a result of one or more audio exposure values (e.g., including the first audio exposure value) exceeding one or more audio exposure thresholds (e.g., including the audio exposure threshold) (e.g., an instantaneous exposure threshold; an aggregate exposure threshold), the indication of the first audio exposure alert including first audio sample data (e.g., audio metadata; an indication of a start and stop time of the audio that triggered the corresponding audio exposure alert; an indication of whether the corresponding audio exposure alert is a first/second/third occurrence of the alert over a predetermined period of time) corresponding to the first audio exposure alert, and 2) an indication of a second audio exposure alert provided as a result of one or more audio exposure values exceeding one or more audio exposure thresholds, the indication of the second audio exposure alert including second audio sample data corresponding to the second audio exposure alert.
In some embodiments, during the first time period, the computer system caused output of audio data that met an instantaneous audio exposure threshold criteria (e.g., criteria that is met when the output of the audio data exceeds an instantaneous sound pressure value (e.g., 90 dB)). In some embodiments, displaying the audio exposure interface includes, in accordance with a determination that a volume limit setting (e.g., “Reduce Loud Sounds”) was disabled at the time the computer system caused output of the audio data that met the instantaneous audio exposure threshold criteria, displaying a second visual indication of a second alert provided as a result of a second audio exposure value exceeding an instantaneous audio exposure threshold (e.g., an instantaneous audio exposure limit). In some embodiments, displaying the audio exposure interface includes, in accordance with a determination that the volume limit setting was enabled at the time the computer system caused output of the audio data that met the instantaneous audio exposure threshold criteria, forgoing displaying the second visual indication (e.g., the second visual indication is not displayed because the volume limit setting was enabled and, therefore, the audio exposure data did not exceed the instantaneous audio exposure limit, which would have triggered the second alert). In some embodiments, the first alert corresponds to an audio exposure threshold that is of a different type than the instantaneous audio exposure threshold criteria (e.g., an aggregate audio exposure threshold) and is displayed irrespective of whether the volume limit setting is enabled or disabled. In some embodiments, the volume limit is set/enabled/disabled using the computer system or using an external computer system such as a wearable device or a master device (e.g., a parent device that is authorized to set/enable/disable volume limits for the computer system). In some embodiments, when the volume limit is disabled, the audio exposure threshold can be an aggregate audio exposure limit or an instantaneous audio exposure limit. Accordingly, resulting alerts can be an alert that the aggregate audio exposure limit is reached or an alert that the instantaneous audio exposure limit is reached. However, when the volume limit is enabled, audio at an audio generation component (e.g., headphones) is limited such that the maximum volume permitted for the output audio data is less than the instantaneous audio exposure limit, as discussed in greater detail with respect to
In some embodiments, the computer system concurrently displays: 1) an affordance that, when selected, initiates a process for deleting the audio exposure data, and 2) a notification regarding availability of audio exposure alerts (e.g., text warning a user that audio exposure alerts (e.g., the first alert) may be deleted or missing if the audio exposure data is deleted).
In some embodiments, the audio exposure data corresponds to ambient sound (e.g., noise). (e.g., the audio exposure data is noise level data). In some embodiments the audio exposure data represents audio that is external to the computer system, rather than audio that is generated (e.g., at an audio generation component) by the computer system. For example, the audio exposure data represents the noise level of the physical environment where the computer system (e.g., a sensor or microphone in communication with the computer system) is located. In some embodiments, the computer system is in communication with a microphone (e.g., integrated in the headphones) for detecting ambient sounds, and the audio exposure data represents the detected ambient sounds.
In some embodiments, the audio exposure data corresponds to audio output generated by the computer system (e.g., via the audio generation component). In some embodiments, the audio exposure data represents audio data that is generated (e.g., at an audio generation component) by the computer system. For example, the audio exposure data represents the volume of audio output at a headphones device that is coupled to the computer system.
Note that details of the processes described above with respect to method 1800 (e.g.,
The foregoing description, for purpose 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 view of the above teachings. The embodiments were chosen and described in order to best explain the principles of the techniques and their practical applications. Others skilled in the art are thereby enabled to best utilize the techniques and various embodiments with various modifications as are suited to the particular use contemplated.
Although the 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. Such changes and modifications are to be understood as being included within the scope of the disclosure and examples as defined by the claims.
As described above, one aspect of the present technology is the gathering and use of data (e.g., sound recordings, audiograms) available from various sources to more effectively monitor personal sound exposure levels. The present disclosure contemplates that in some instances, this gathered data may include personal information data that uniquely identifies or can be used to contact or locate a specific person. Such personal information data can include demographic data, location-based data, telephone numbers, email addresses, twitter IDs, home addresses, data or records relating to a user's health or level of fitness (e.g., vital signs measurements, medication information, exercise information), date of birth, or any other identifying or personal information.
The present disclosure recognizes that the use of such personal information data, in the present technology, can be used to the benefit of users. For example, the personal information data can be used to provide a user with an accurate assessment of personal noise exposure throughout the day. Further, other uses for personal information data that benefit the user are also contemplated by the present disclosure. For instance, health and fitness data may be used to provide insights into a user's general wellness, or may be used as positive feedback to individuals using technology to pursue wellness goals.
The present disclosure contemplates that the entities responsible for the collection, analysis, disclosure, transfer, storage, or other use of such personal information data will comply with well-established privacy policies and/or privacy practices. In particular, such entities should implement and consistently use privacy policies and practices that are generally recognized as meeting or exceeding industry or governmental requirements for maintaining personal information data private and secure. Such policies should be easily accessible by users, and should be updated as the collection and/or use of data changes. Personal information from users should be collected for legitimate and reasonable uses of the entity and not shared or sold outside of those legitimate uses. Further, such collection/sharing should occur after receiving the informed consent of the users. Additionally, such entities should consider taking any needed steps for safeguarding and securing access to such personal information data and ensuring that others with access to the personal information data adhere to their privacy policies and procedures. Further, such entities can subject themselves to evaluation by third parties to certify their adherence to widely accepted privacy policies and practices. In addition, policies and practices should be adapted for the particular types of personal information data being collected and/or accessed and adapted to applicable laws and standards, including jurisdiction-specific considerations. For instance, in the US, collection of or access to certain health data may be governed by federal and/or state laws, such as the Health Insurance Portability and Accountability Act (HIPAA); whereas health data in other countries may be subject to other regulations and policies and should be handled accordingly. Hence different privacy practices should be maintained for different personal data types in each country.
Despite the foregoing, the present disclosure also contemplates embodiments in which users selectively block the use of, or access to, personal information data. That is, the present disclosure contemplates that hardware and/or software elements can be provided to prevent or block access to such personal information data. For example, in the case of monitoring noise exposure levels, the present technology can be configured to allow users to select to “opt in” or “opt out” of participation in the collection of personal information data during registration for services or anytime thereafter. In another example, users can select not to provide sound recording data for monitoring noise exposure levels. In yet another example, users can select to limit the length of time sound recording data is maintained or entirely prohibit the development of a noise exposure profile. In addition to providing “opt in” and “opt out” options, the present disclosure contemplates providing notifications relating to the access or use of personal information. For instance, a user may be notified upon downloading an app that their personal information data will be accessed and then reminded again just before personal information data is accessed by the app.
Moreover, it is the intent of the present disclosure that personal information data should be managed and handled in a way to minimize risks of unintentional or unauthorized access or use. Risk can be minimized by limiting the collection of data and deleting data once it is no longer needed. In addition, and when applicable, including in certain health related applications, data de-identification can be used to protect a user's privacy. De-identification may be facilitated, when appropriate, by removing specific identifiers (e.g., date of birth), controlling the amount or specificity of data stored (e.g., collecting location data a city level rather than at an address level), controlling how data is stored (e.g., aggregating data across users), and/or other methods.
Therefore, although the present disclosure broadly covers use of personal information data to implement one or more various disclosed embodiments, the present disclosure also contemplates that the various embodiments can also be implemented without the need for accessing such personal information data. That is, the various embodiments of the present technology are not rendered inoperable due to the lack of all or a portion of such personal information data. For example, noise exposure data can be selected and delivered to users by inferring preferences based on non-personal information data or a bare minimum amount of personal information, such as the content being requested by the device associated with a user, other non-personal or publicly available information.
This application is a continuation of U.S. application Ser. No. 16/880,552, filed May 21, 2020, entitled “USER INTERFACES FOR MANAGING AUDIO EXPOSURE,” which claims priority to U.S. Provisional Application No. 63/023,023, filed May 11, 2020, entitled “USER INTERFACES FOR MANAGING AUDIO EXPOSURE,” and U.S. Provisional Application No. 62/856,016, filed Jun. 1, 2019, entitled “USER INTERFACES FOR MONITORING NOISE EXPOSURE LEVELS,” the contents of each of which are hereby incorporated by reference in their entirety.
| Number | Name | Date | Kind |
|---|---|---|---|
| 5515344 | Ng | May 1996 | A |
| 5642731 | Kehr | Jul 1997 | A |
| 6298314 | Blackadar et al. | Oct 2001 | B1 |
| 6416471 | Kumar et al. | Jul 2002 | B1 |
| 6475115 | Candito et al. | Nov 2002 | B1 |
| 6600696 | Lynn | Jul 2003 | B1 |
| 6705972 | Takano et al. | Mar 2004 | B1 |
| 6873709 | Hou | Mar 2005 | B2 |
| 6950839 | Green et al. | Sep 2005 | B1 |
| 7111157 | Hooper | Sep 2006 | B1 |
| 7128693 | Brown et al. | Oct 2006 | B2 |
| 7166078 | Saini et al. | Jan 2007 | B2 |
| 7313435 | Nakada et al. | Dec 2007 | B2 |
| 7739148 | Suzuki et al. | Jun 2010 | B2 |
| 7771320 | Riley et al. | Aug 2010 | B2 |
| 8045739 | Paludan-Mueller | Oct 2011 | B2 |
| 8152694 | Srinivasan et al. | Apr 2012 | B2 |
| 8200323 | Dibenedetto et al. | Jun 2012 | B2 |
| 8321006 | Snyder et al. | Nov 2012 | B1 |
| 8475339 | Hwang et al. | Jul 2013 | B2 |
| 8676170 | Porrati et al. | Mar 2014 | B2 |
| 8725527 | Kahn et al. | May 2014 | B1 |
| 8758262 | Rhee et al. | Jun 2014 | B2 |
| 8784115 | Chuang | Jul 2014 | B1 |
| 8888707 | Shirasaki et al. | Nov 2014 | B2 |
| 9011292 | Weast et al. | Apr 2015 | B2 |
| 9026927 | Brumback et al. | May 2015 | B2 |
| 9224291 | Moll-Carrillo et al. | Dec 2015 | B2 |
| 9490763 | Taniguchi et al. | Nov 2016 | B2 |
| 9579060 | Lisy et al. | Feb 2017 | B1 |
| 9589445 | White et al. | Mar 2017 | B2 |
| 9606695 | Matas | Mar 2017 | B2 |
| 9672715 | Roberts et al. | Jun 2017 | B2 |
| 9712629 | Molettiere et al. | Jul 2017 | B2 |
| 9721066 | Funaro et al. | Aug 2017 | B1 |
| 9730621 | Cohen et al. | Aug 2017 | B2 |
| 9801562 | Host-Madsen | Oct 2017 | B1 |
| 9808206 | Zhao et al. | Nov 2017 | B1 |
| 9813642 | Chen et al. | Nov 2017 | B1 |
| 9940682 | Hoffman et al. | Apr 2018 | B2 |
| 10004451 | Proud | Jun 2018 | B1 |
| 10024711 | Sanchez et al. | Jul 2018 | B1 |
| 10068451 | Werner et al. | Sep 2018 | B1 |
| 10150002 | Kass et al. | Dec 2018 | B2 |
| 10175781 | Karagozler et al. | Jan 2019 | B2 |
| 10226195 | Briante et al. | Mar 2019 | B2 |
| 10254911 | Yang | Apr 2019 | B2 |
| 10275262 | Bull et al. | Apr 2019 | B1 |
| 10339830 | Han et al. | Jul 2019 | B2 |
| 10365811 | Robinson et al. | Jul 2019 | B2 |
| 10437962 | Soni et al. | Oct 2019 | B2 |
| 10445702 | Hunt | Oct 2019 | B1 |
| 10565894 | Jain et al. | Feb 2020 | B1 |
| 10568533 | Soli et al. | Feb 2020 | B2 |
| 10576327 | Kim et al. | Mar 2020 | B2 |
| 10592088 | Robinson et al. | Mar 2020 | B2 |
| 10602964 | Kerber | Mar 2020 | B2 |
| 10635267 | Williams | Apr 2020 | B2 |
| 10674942 | Williams et al. | Jun 2020 | B2 |
| 10685090 | Petterson et al. | Jun 2020 | B2 |
| 10762990 | Schilling et al. | Sep 2020 | B1 |
| 10764700 | Felton | Sep 2020 | B1 |
| 10796549 | Roberts et al. | Oct 2020 | B2 |
| 11073942 | Lee et al. | Jul 2021 | B2 |
| 11103161 | Williams et al. | Aug 2021 | B2 |
| 11107580 | Felton et al. | Aug 2021 | B1 |
| 11209957 | Dryer et al. | Dec 2021 | B2 |
| 20020095292 | Mittal et al. | Jul 2002 | A1 |
| 20030181291 | Ogawa | Sep 2003 | A1 |
| 20030191609 | Bernardi et al. | Oct 2003 | A1 |
| 20030200483 | Sutton | Oct 2003 | A1 |
| 20030216971 | Sick et al. | Nov 2003 | A1 |
| 20030226695 | Mault | Dec 2003 | A1 |
| 20040017300 | Kotzin et al. | Jan 2004 | A1 |
| 20040077958 | Kato et al. | Apr 2004 | A1 |
| 20040081024 | Weng | Apr 2004 | A1 |
| 20040190729 | Yonovitz et al. | Sep 2004 | A1 |
| 20040193069 | Takehara | Sep 2004 | A1 |
| 20040210117 | Ueno et al. | Oct 2004 | A1 |
| 20040236189 | Hawthorne et al. | Nov 2004 | A1 |
| 20050010117 | Agutter et al. | Jan 2005 | A1 |
| 20050027208 | Shiraishi et al. | Feb 2005 | A1 |
| 20050075214 | Brown et al. | Apr 2005 | A1 |
| 20050079905 | Martens | Apr 2005 | A1 |
| 20050149362 | Peterson et al. | Jul 2005 | A1 |
| 20050228735 | Duquette | Oct 2005 | A1 |
| 20050244013 | Battenberg et al. | Nov 2005 | A1 |
| 20050272564 | Pyles et al. | Dec 2005 | A1 |
| 20060094969 | Nissila | May 2006 | A1 |
| 20060098109 | Ooki | May 2006 | A1 |
| 20060106741 | Janarthanan | May 2006 | A1 |
| 20060136173 | Case, Jr. et al. | Jun 2006 | A1 |
| 20060149144 | Lynn et al. | Jul 2006 | A1 |
| 20060152372 | Stout | Jul 2006 | A1 |
| 20060182287 | Schulein et al. | Aug 2006 | A1 |
| 20060205564 | Peterson | Sep 2006 | A1 |
| 20060210096 | Stokes | Sep 2006 | A1 |
| 20060235319 | Belohlavek et al. | Oct 2006 | A1 |
| 20060274908 | Choi | Dec 2006 | A1 |
| 20070016440 | Stroup | Jan 2007 | A1 |
| 20070056727 | Newman | Mar 2007 | A1 |
| 20070179434 | Weinert et al. | Aug 2007 | A1 |
| 20070250505 | Yang et al. | Oct 2007 | A1 |
| 20070250613 | Gulledge | Oct 2007 | A1 |
| 20070274531 | Camp | Nov 2007 | A1 |
| 20080012701 | Kass et al. | Jan 2008 | A1 |
| 20080058626 | Miyata et al. | Mar 2008 | A1 |
| 20080133742 | Southiere et al. | Jun 2008 | A1 |
| 20080146892 | Leboeuf et al. | Jun 2008 | A1 |
| 20080159547 | Schuler et al. | Jul 2008 | A1 |
| 20080200312 | Tagliabue | Aug 2008 | A1 |
| 20080205660 | Goldstein | Aug 2008 | A1 |
| 20080228045 | Gao et al. | Sep 2008 | A1 |
| 20080240519 | Nagamitsu | Oct 2008 | A1 |
| 20080300110 | Smith et al. | Dec 2008 | A1 |
| 20090007596 | Goldstein et al. | Jan 2009 | A1 |
| 20090052677 | Smith | Feb 2009 | A1 |
| 20090065578 | Peterson et al. | Mar 2009 | A1 |
| 20090118100 | Oliver et al. | May 2009 | A1 |
| 20090180631 | Michael et al. | Jul 2009 | A1 |
| 20090210078 | Crowley | Aug 2009 | A1 |
| 20090216556 | Martin et al. | Aug 2009 | A1 |
| 20090235253 | Hope | Sep 2009 | A1 |
| 20090245537 | Morin | Oct 2009 | A1 |
| 20090259134 | Levine | Oct 2009 | A1 |
| 20090262088 | Moll-Carrillo et al. | Oct 2009 | A1 |
| 20090267776 | Glenn et al. | Oct 2009 | A1 |
| 20090287103 | Pillai | Nov 2009 | A1 |
| 20090287327 | Hsu et al. | Nov 2009 | A1 |
| 20090290721 | Goldstein et al. | Nov 2009 | A1 |
| 20100003951 | Ray et al. | Jan 2010 | A1 |
| 20100010832 | Boute et al. | Jan 2010 | A1 |
| 20100014682 | Shin | Jan 2010 | A1 |
| 20100017489 | Birnbaum et al. | Jan 2010 | A1 |
| 20100027807 | Jeon | Feb 2010 | A1 |
| 20100046767 | Bayley et al. | Feb 2010 | A1 |
| 20100062905 | Rottler et al. | Mar 2010 | A1 |
| 20100073162 | Johnson et al. | Mar 2010 | A1 |
| 20100076331 | Chan et al. | Mar 2010 | A1 |
| 20100099539 | Haataja | Apr 2010 | A1 |
| 20100119093 | Uzuanis et al. | May 2010 | A1 |
| 20100121700 | Wigder et al. | May 2010 | A1 |
| 20100145220 | Van Vliet | Jun 2010 | A1 |
| 20100150378 | Lee et al. | Jun 2010 | A1 |
| 20100222645 | Nadler et al. | Sep 2010 | A1 |
| 20100292600 | Dibenedetto et al. | Nov 2010 | A1 |
| 20100312138 | Regas | Dec 2010 | A1 |
| 20110057799 | Taneff | Mar 2011 | A1 |
| 20110066051 | Moon et al. | Mar 2011 | A1 |
| 20110071765 | Yodfat et al. | Mar 2011 | A1 |
| 20110093481 | Hussam | Apr 2011 | A1 |
| 20110098928 | Hoffman et al. | Apr 2011 | A1 |
| 20110152656 | Weinert et al. | Jun 2011 | A1 |
| 20110166631 | Breining | Jul 2011 | A1 |
| 20110195383 | Weiss | Aug 2011 | A1 |
| 20110214162 | Brakensiek et al. | Sep 2011 | A1 |
| 20110218407 | Haberman et al. | Sep 2011 | A1 |
| 20110245623 | Chutani et al. | Oct 2011 | A1 |
| 20110307821 | Martens | Dec 2011 | A1 |
| 20120002510 | Berman, Jr. | Jan 2012 | A1 |
| 20120029303 | Shaya | Feb 2012 | A1 |
| 20120033827 | Murata et al. | Feb 2012 | A1 |
| 20120038651 | Case et al. | Feb 2012 | A1 |
| 20120041767 | Hoffman et al. | Feb 2012 | A1 |
| 20120051555 | Schevciw et al. | Mar 2012 | A1 |
| 20120059664 | Georgiev et al. | Mar 2012 | A1 |
| 20120065480 | Badilini et al. | Mar 2012 | A1 |
| 20120071770 | Grey et al. | Mar 2012 | A1 |
| 20120112908 | Prykaeri et al. | May 2012 | A1 |
| 20120116550 | Hoffman et al. | May 2012 | A1 |
| 20120203124 | Lim | Aug 2012 | A1 |
| 20120215115 | Takahashi | Aug 2012 | A1 |
| 20120245447 | Karan et al. | Sep 2012 | A1 |
| 20120283524 | Kiani et al. | Nov 2012 | A1 |
| 20120283587 | Gosh et al. | Nov 2012 | A1 |
| 20120283855 | Hoffman et al. | Nov 2012 | A1 |
| 20120311585 | Gruber et al. | Dec 2012 | A1 |
| 20120316455 | Rahman et al. | Dec 2012 | A1 |
| 20120317167 | Rahman et al. | Dec 2012 | A1 |
| 20120321094 | Schiller et al. | Dec 2012 | A1 |
| 20130002425 | Hatch et al. | Jan 2013 | A1 |
| 20130007155 | Moore et al. | Jan 2013 | A1 |
| 20130011819 | Horseman | Jan 2013 | A1 |
| 20130012788 | Horseman | Jan 2013 | A1 |
| 20130013331 | Horseman | Jan 2013 | A1 |
| 20130033376 | Seyed et al. | Feb 2013 | A1 |
| 20130065569 | Leipzig et al. | Mar 2013 | A1 |
| 20130072765 | Kahn et al. | Mar 2013 | A1 |
| 20130073933 | Eppolito | Mar 2013 | A1 |
| 20130073960 | Eppolito et al. | Mar 2013 | A1 |
| 20130095459 | Tran | Apr 2013 | A1 |
| 20130110264 | Weast et al. | May 2013 | A1 |
| 20130114100 | Torii et al. | May 2013 | A1 |
| 20130115583 | Gordon et al. | May 2013 | A1 |
| 20130144653 | Poe et al. | Jun 2013 | A1 |
| 20130151285 | Mclaren et al. | Jun 2013 | A1 |
| 20130158416 | Hatlestad et al. | Jun 2013 | A1 |
| 20130197679 | Balakrishnan et al. | Aug 2013 | A1 |
| 20130202121 | Georgiou et al. | Aug 2013 | A1 |
| 20130215042 | Messerschmidt et al. | Aug 2013 | A1 |
| 20130231575 | Erkkila et al. | Sep 2013 | A1 |
| 20130231947 | Shusterman | Sep 2013 | A1 |
| 20130268398 | Agami et al. | Oct 2013 | A1 |
| 20130274628 | Fausti et al. | Oct 2013 | A1 |
| 20130304616 | Raleigh et al. | Nov 2013 | A1 |
| 20130317380 | Liley et al. | Nov 2013 | A1 |
| 20130325396 | Yuen et al. | Dec 2013 | A1 |
| 20130332286 | Medelius et al. | Dec 2013 | A1 |
| 20140005947 | Jeon et al. | Jan 2014 | A1 |
| 20140037107 | Marino et al. | Feb 2014 | A1 |
| 20140038781 | Foley et al. | Feb 2014 | A1 |
| 20140073486 | Ahmed et al. | Mar 2014 | A1 |
| 20140081118 | Reinhold et al. | Mar 2014 | A1 |
| 20140088995 | Damani | Mar 2014 | A1 |
| 20140127996 | Park et al. | May 2014 | A1 |
| 20140129007 | Utter | May 2014 | A1 |
| 20140129243 | Utter | May 2014 | A1 |
| 20140135592 | Ohnemus et al. | May 2014 | A1 |
| 20140142403 | Brumback et al. | May 2014 | A1 |
| 20140143678 | Mistry et al. | May 2014 | A1 |
| 20140164611 | Molettiere et al. | Jun 2014 | A1 |
| 20140173521 | Mayor | Jun 2014 | A1 |
| 20140176335 | Brumback et al. | Jun 2014 | A1 |
| 20140176475 | Myers et al. | Jun 2014 | A1 |
| 20140180595 | Brumback et al. | Jun 2014 | A1 |
| 20140184422 | Mensinger et al. | Jul 2014 | A1 |
| 20140189510 | Ozcan | Jul 2014 | A1 |
| 20140197946 | Park et al. | Jul 2014 | A1 |
| 20140200426 | Taub et al. | Jul 2014 | A1 |
| 20140240122 | Roberts et al. | Aug 2014 | A1 |
| 20140240349 | Tuukkanen | Aug 2014 | A1 |
| 20140266776 | Miller et al. | Sep 2014 | A1 |
| 20140267543 | Kerger et al. | Sep 2014 | A1 |
| 20140275852 | Hong et al. | Sep 2014 | A1 |
| 20140275856 | Kohlrausch et al. | Sep 2014 | A1 |
| 20140278220 | Yuen | Sep 2014 | A1 |
| 20140288390 | Hong et al. | Sep 2014 | A1 |
| 20140297217 | Yuen | Oct 2014 | A1 |
| 20140327527 | Goldstein et al. | Nov 2014 | A1 |
| 20140336796 | Agnew | Nov 2014 | A1 |
| 20140344687 | Durham et al. | Nov 2014 | A1 |
| 20140354494 | Katz | Dec 2014 | A1 |
| 20140358012 | Richards et al. | Dec 2014 | A1 |
| 20140371887 | Hoffman et al. | Dec 2014 | A1 |
| 20150032451 | Gunn et al. | Jan 2015 | A1 |
| 20150057942 | Self et al. | Feb 2015 | A1 |
| 20150073285 | Albert et al. | Mar 2015 | A1 |
| 20150081210 | Yeh et al. | Mar 2015 | A1 |
| 20150089536 | Byerley | Mar 2015 | A1 |
| 20150099991 | Yamaguchi et al. | Apr 2015 | A1 |
| 20150100348 | Connery et al. | Apr 2015 | A1 |
| 20150106025 | Keller et al. | Apr 2015 | A1 |
| 20150110277 | Pidgeon et al. | Apr 2015 | A1 |
| 20150110279 | Tejerina | Apr 2015 | A1 |
| 20150120633 | Norlander et al. | Apr 2015 | A1 |
| 20150124067 | Bala et al. | May 2015 | A1 |
| 20150125832 | Tran | May 2015 | A1 |
| 20150127365 | Rizvi et al. | May 2015 | A1 |
| 20150142689 | Squires | May 2015 | A1 |
| 20150164349 | Gopalakrishnan et al. | Jun 2015 | A1 |
| 20150173686 | Furuta et al. | Jun 2015 | A1 |
| 20150179186 | Swierk et al. | Jun 2015 | A1 |
| 20150181314 | Swanson | Jun 2015 | A1 |
| 20150182843 | Esposito et al. | Jul 2015 | A1 |
| 20150185967 | Ly et al. | Jul 2015 | A1 |
| 20150193217 | Xiang et al. | Jul 2015 | A1 |
| 20150196804 | Koduri et al. | Jul 2015 | A1 |
| 20150205947 | Berman et al. | Jul 2015 | A1 |
| 20150216448 | Lotan et al. | Aug 2015 | A1 |
| 20150217163 | Amis et al. | Aug 2015 | A1 |
| 20150220883 | Bfar et al. | Aug 2015 | A1 |
| 20150230717 | Wan | Aug 2015 | A1 |
| 20150261918 | Thombury, Jr. | Sep 2015 | A1 |
| 20150262499 | Wicka et al. | Sep 2015 | A1 |
| 20150286800 | Kanagala et al. | Oct 2015 | A1 |
| 20150287421 | Benway et al. | Oct 2015 | A1 |
| 20150288797 | Vincent | Oct 2015 | A1 |
| 20150288944 | Nistico et al. | Oct 2015 | A1 |
| 20150289823 | Rack-gomer et al. | Oct 2015 | A1 |
| 20150297134 | Albert et al. | Oct 2015 | A1 |
| 20150324751 | Orenstein et al. | Nov 2015 | A1 |
| 20150347690 | Keen et al. | Dec 2015 | A1 |
| 20150347711 | Soli et al. | Dec 2015 | A1 |
| 20150350799 | Schnaare et al. | Dec 2015 | A1 |
| 20150350861 | Soli et al. | Dec 2015 | A1 |
| 20160000379 | Pougatchev et al. | Jan 2016 | A1 |
| 20160019360 | Pahwa et al. | Jan 2016 | A1 |
| 20160055420 | Karanam et al. | Feb 2016 | A1 |
| 20160058313 | Sato | Mar 2016 | A1 |
| 20160058336 | Blahnik et al. | Mar 2016 | A1 |
| 20160058337 | Blahnik et al. | Mar 2016 | A1 |
| 20160062540 | Yang et al. | Mar 2016 | A1 |
| 20160062572 | Yang et al. | Mar 2016 | A1 |
| 20160062582 | Wilson et al. | Mar 2016 | A1 |
| 20160063215 | Zamer | Mar 2016 | A1 |
| 20160066842 | Kokkoneva et al. | Mar 2016 | A1 |
| 20160085937 | Dettinger et al. | Mar 2016 | A1 |
| 20160086500 | Kaleal | Mar 2016 | A1 |
| 20160089569 | Blahnik | Mar 2016 | A1 |
| 20160098522 | Weinstein | Apr 2016 | A1 |
| 20160103985 | Shim et al. | Apr 2016 | A1 |
| 20160106398 | Kuppuswami | Apr 2016 | A1 |
| 20160109961 | Parshionikar | Apr 2016 | A1 |
| 20160119709 | Beurton et al. | Apr 2016 | A1 |
| 20160132046 | Beoughter et al. | May 2016 | A1 |
| 20160135719 | Von Kraus et al. | May 2016 | A1 |
| 20160135731 | Drennan | May 2016 | A1 |
| 20160150978 | Yuen et al. | Jun 2016 | A1 |
| 20160166181 | Shennib | Jun 2016 | A1 |
| 20160166195 | Radecka et al. | Jun 2016 | A1 |
| 20160174857 | Eggers et al. | Jun 2016 | A1 |
| 20160180026 | Kim et al. | Jun 2016 | A1 |
| 20160189051 | Mahmood | Jun 2016 | A1 |
| 20160196635 | Cho et al. | Jul 2016 | A1 |
| 20160210099 | Hampapuram et al. | Jul 2016 | A1 |
| 20160235325 | Chou | Aug 2016 | A1 |
| 20160235374 | Miller et al. | Aug 2016 | A1 |
| 20160249857 | Choi et al. | Sep 2016 | A1 |
| 20160250517 | Tilvis et al. | Sep 2016 | A1 |
| 20160256082 | Ely et al. | Sep 2016 | A1 |
| 20160263435 | Venkatraman et al. | Sep 2016 | A1 |
| 20160270717 | Luna et al. | Sep 2016 | A1 |
| 20160270740 | Raisoni et al. | Sep 2016 | A1 |
| 20160275990 | Vassort | Sep 2016 | A1 |
| 20160285985 | Molettiere et al. | Sep 2016 | A1 |
| 20160287177 | Huppert et al. | Oct 2016 | A1 |
| 20160292373 | Spors et al. | Oct 2016 | A1 |
| 20160296210 | Matsushima | Oct 2016 | A1 |
| 20160299769 | Hunter et al. | Oct 2016 | A1 |
| 20160301761 | Sanchez-sandoval et al. | Oct 2016 | A1 |
| 20160301794 | Schlakman et al. | Oct 2016 | A1 |
| 20160302666 | Shaya | Oct 2016 | A1 |
| 20160313869 | Jang et al. | Oct 2016 | A1 |
| 20160314670 | Roberts et al. | Oct 2016 | A1 |
| 20160314683 | Felch et al. | Oct 2016 | A1 |
| 20160317341 | Galvan | Nov 2016 | A1 |
| 20160324457 | Dagum | Nov 2016 | A1 |
| 20160324488 | Olsen | Nov 2016 | A1 |
| 20160328991 | Simpson et al. | Nov 2016 | A1 |
| 20160332025 | Repka | Nov 2016 | A1 |
| 20160346607 | Rapfogel | Dec 2016 | A1 |
| 20160357616 | Yu et al. | Dec 2016 | A1 |
| 20160360100 | Kim et al. | Dec 2016 | A1 |
| 20160360972 | Kusakabe et al. | Dec 2016 | A1 |
| 20160367138 | Kim et al. | Dec 2016 | A1 |
| 20170000348 | Karsten et al. | Jan 2017 | A1 |
| 20170000359 | Kohli et al. | Jan 2017 | A1 |
| 20170007159 | Dieffenderfer et al. | Jan 2017 | A1 |
| 20170007167 | Kostic et al. | Jan 2017 | A1 |
| 20170032168 | Kim | Feb 2017 | A1 |
| 20170039327 | Bitran et al. | Feb 2017 | A1 |
| 20170042485 | Chung et al. | Feb 2017 | A1 |
| 20170043214 | Higashi | Feb 2017 | A1 |
| 20170046024 | Dascola et al. | Feb 2017 | A1 |
| 20170046052 | Lee et al. | Feb 2017 | A1 |
| 20170053542 | Wilson et al. | Feb 2017 | A1 |
| 20170070833 | Shennib | Mar 2017 | A1 |
| 20170071551 | Jain et al. | Mar 2017 | A1 |
| 20170075551 | Robinson et al. | Mar 2017 | A1 |
| 20170084196 | Nusbaum et al. | Mar 2017 | A1 |
| 20170086693 | Peterson et al. | Mar 2017 | A1 |
| 20170091567 | Wang et al. | Mar 2017 | A1 |
| 20170127997 | Hyde et al. | May 2017 | A1 |
| 20170132395 | Futch | May 2017 | A1 |
| 20170136297 | Penie | May 2017 | A1 |
| 20170147197 | Yang et al. | May 2017 | A1 |
| 20170150917 | Brief et al. | Jun 2017 | A1 |
| 20170156593 | Ferber et al. | Jun 2017 | A1 |
| 20170161014 | Kikugawa et al. | Jun 2017 | A1 |
| 20170172522 | Insler et al. | Jun 2017 | A1 |
| 20170177797 | Kurniawan et al. | Jun 2017 | A1 |
| 20170181645 | Mahalingam et al. | Jun 2017 | A1 |
| 20170181678 | Newberry | Jun 2017 | A1 |
| 20170188841 | Ma et al. | Jul 2017 | A1 |
| 20170188893 | Venkatraman et al. | Jul 2017 | A1 |
| 20170188979 | Volpe | Jul 2017 | A1 |
| 20170202496 | Ramanathan | Jul 2017 | A1 |
| 20170215811 | Newberry | Aug 2017 | A1 |
| 20170225034 | Kass et al. | Aug 2017 | A1 |
| 20170230788 | Simonides et al. | Aug 2017 | A1 |
| 20170235443 | Suzuki | Aug 2017 | A1 |
| 20170237694 | Choudhary et al. | Aug 2017 | A1 |
| 20170243508 | Cheng et al. | Aug 2017 | A1 |
| 20170258455 | Qi | Sep 2017 | A1 |
| 20170274149 | Aeschlimann | Sep 2017 | A1 |
| 20170274267 | Blahnik | Sep 2017 | A1 |
| 20170287313 | Park et al. | Oct 2017 | A1 |
| 20170293727 | Klaassen et al. | Oct 2017 | A1 |
| 20170294174 | Albadawi et al. | Oct 2017 | A1 |
| 20170300186 | Kuhar et al. | Oct 2017 | A1 |
| 20170303844 | Baker et al. | Oct 2017 | A1 |
| 20170319184 | Sano | Nov 2017 | A1 |
| 20170329933 | Brust et al. | Nov 2017 | A1 |
| 20170330297 | Cronin et al. | Nov 2017 | A1 |
| 20170332980 | Fifield et al. | Nov 2017 | A1 |
| 20170348562 | Jung et al. | Dec 2017 | A1 |
| 20170354845 | Williams et al. | Dec 2017 | A1 |
| 20170357329 | Park et al. | Dec 2017 | A1 |
| 20170357520 | De Vries et al. | Dec 2017 | A1 |
| 20170364637 | Kshepakaran et al. | Dec 2017 | A1 |
| 20180000426 | Li | Jan 2018 | A1 |
| 20180001184 | Tran et al. | Jan 2018 | A1 |
| 20180011686 | Zhao et al. | Jan 2018 | A1 |
| 20180014121 | Lawrence | Jan 2018 | A1 |
| 20180032234 | Michalske | Feb 2018 | A1 |
| 20180039410 | Kim et al. | Feb 2018 | A1 |
| 20180042559 | Cabrera et al. | Feb 2018 | A1 |
| 20180047277 | Thyroff | Feb 2018 | A1 |
| 20180049659 | Briante et al. | Feb 2018 | A1 |
| 20180049696 | Eom et al. | Feb 2018 | A1 |
| 20180055490 | Lee et al. | Mar 2018 | A1 |
| 20180056130 | Bitran et al. | Mar 2018 | A1 |
| 20180060522 | Petterson et al. | Mar 2018 | A1 |
| 20180064356 | Mendenhall et al. | Mar 2018 | A1 |
| 20180064388 | Heneghan et al. | Mar 2018 | A1 |
| 20180065025 | Toda et al. | Mar 2018 | A1 |
| 20180070861 | Eastman et al. | Mar 2018 | A1 |
| 20180074462 | Helder et al. | Mar 2018 | A1 |
| 20180074464 | Essery et al. | Mar 2018 | A1 |
| 20180081918 | Gravenites et al. | Mar 2018 | A1 |
| 20180096739 | Sano | Apr 2018 | A1 |
| 20180107962 | Lundin et al. | Apr 2018 | A1 |
| 20180110465 | Naima | Apr 2018 | A1 |
| 20180117414 | Miyasaka et al. | May 2018 | A1 |
| 20180120985 | Wallace et al. | May 2018 | A1 |
| 20180122214 | Freedman et al. | May 2018 | A1 |
| 20180129994 | Fowler et al. | May 2018 | A1 |
| 20180132768 | Sasahara et al. | May 2018 | A1 |
| 20180137937 | Gass et al. | May 2018 | A1 |
| 20180140211 | Nakazawa et al. | May 2018 | A1 |
| 20180140927 | Kito et al. | May 2018 | A1 |
| 20180154212 | Park et al. | Jun 2018 | A1 |
| 20180189077 | Gupta et al. | Jul 2018 | A1 |
| 20180189343 | Embiricos et al. | Jul 2018 | A1 |
| 20180211020 | Fukuda | Jul 2018 | A1 |
| 20180226150 | Hayter et al. | Aug 2018 | A1 |
| 20180239869 | Laing et al. | Aug 2018 | A1 |
| 20180255159 | Cohen et al. | Sep 2018 | A1 |
| 20180256036 | Kogure et al. | Sep 2018 | A1 |
| 20180256078 | Vaterlaus | Sep 2018 | A1 |
| 20180256095 | Arnold et al. | Sep 2018 | A1 |
| 20180263510 | Cronin et al. | Sep 2018 | A1 |
| 20180263517 | Kubo | Sep 2018 | A1 |
| 20180279885 | Bulut | Oct 2018 | A1 |
| 20180329584 | Williams et al. | Nov 2018 | A1 |
| 20180336530 | Johnson et al. | Nov 2018 | A1 |
| 20180350451 | Ohnemus et al. | Dec 2018 | A1 |
| 20180368814 | R. Kudtarkar | Dec 2018 | A1 |
| 20180376107 | Shibaev et al. | Dec 2018 | A1 |
| 20190012898 | Wittrup | Jan 2019 | A1 |
| 20190014205 | Miloseski et al. | Jan 2019 | A1 |
| 20190018588 | Debates et al. | Jan 2019 | A1 |
| 20190034050 | Williams et al. | Jan 2019 | A1 |
| 20190034494 | Bradley et al. | Jan 2019 | A1 |
| 20190043337 | Liu et al. | Feb 2019 | A1 |
| 20190073618 | Kanukurthy et al. | Mar 2019 | A1 |
| 20190090800 | Bosworth et al. | Mar 2019 | A1 |
| 20190090816 | Horseman | Mar 2019 | A1 |
| 20190104951 | Valys et al. | Apr 2019 | A1 |
| 20190108908 | Faulks et al. | Apr 2019 | A1 |
| 20190122523 | Roberts et al. | Apr 2019 | A1 |
| 20190138696 | Carpenter et al. | May 2019 | A1 |
| 20190150854 | Chung et al. | May 2019 | A1 |
| 20190192086 | Menon et al. | Jun 2019 | A1 |
| 20190206538 | Xing et al. | Jul 2019 | A1 |
| 20190223843 | Vitti | Jul 2019 | A1 |
| 20190228179 | Rakshit et al. | Jul 2019 | A1 |
| 20190228640 | Freedman et al. | Jul 2019 | A1 |
| 20190240534 | Black | Aug 2019 | A1 |
| 20190252054 | Dirani et al. | Aug 2019 | A1 |
| 20190274562 | Soli et al. | Sep 2019 | A1 |
| 20190274563 | Soli et al. | Sep 2019 | A1 |
| 20190274564 | Soli et al. | Sep 2019 | A1 |
| 20190274565 | Soli et al. | Sep 2019 | A1 |
| 20190278556 | Usher et al. | Sep 2019 | A1 |
| 20190298230 | Nicholson et al. | Oct 2019 | A1 |
| 20190302995 | Robinson et al. | Oct 2019 | A1 |
| 20190313180 | Kadiwala | Oct 2019 | A1 |
| 20190333614 | Burger et al. | Oct 2019 | A1 |
| 20190336044 | Williams et al. | Nov 2019 | A1 |
| 20190336045 | Williams et al. | Nov 2019 | A1 |
| 20190339849 | Williams et al. | Nov 2019 | A1 |
| 20190341027 | Vescovi et al. | Nov 2019 | A1 |
| 20190365332 | Fedichev et al. | Dec 2019 | A1 |
| 20190380624 | Ota et al. | Dec 2019 | A1 |
| 20190385708 | Hong et al. | Dec 2019 | A1 |
| 20200000441 | Lafon et al. | Jan 2020 | A1 |
| 20200054931 | Martin et al. | Feb 2020 | A1 |
| 20200069258 | Grinberg | Mar 2020 | A1 |
| 20200100693 | Velo | Apr 2020 | A1 |
| 20200126673 | Tanabe et al. | Apr 2020 | A1 |
| 20200203012 | Kamath et al. | Jun 2020 | A1 |
| 20200214650 | Lee et al. | Jul 2020 | A1 |
| 20200245928 | Kang et al. | Aug 2020 | A1 |
| 20200261011 | Seppänen et al. | Aug 2020 | A1 |
| 20200273566 | Bhowmik et al. | Aug 2020 | A1 |
| 20200297249 | Williams et al. | Sep 2020 | A1 |
| 20200315544 | Levine | Oct 2020 | A1 |
| 20200323441 | Deno et al. | Oct 2020 | A1 |
| 20200350052 | Saint et al. | Nov 2020 | A1 |
| 20200356687 | Salzman et al. | Nov 2020 | A1 |
| 20200374682 | Newman et al. | Nov 2020 | A1 |
| 20200379611 | Dryer et al. | Dec 2020 | A1 |
| 20200381099 | Crowley et al. | Dec 2020 | A1 |
| 20200381123 | Dryer et al. | Dec 2020 | A1 |
| 20200382866 | Felton | Dec 2020 | A1 |
| 20200382867 | Felton | Dec 2020 | A1 |
| 20200382868 | Felton | Dec 2020 | A1 |
| 20200384314 | Lee et al. | Dec 2020 | A1 |
| 20210019713 | Vangala et al. | Jan 2021 | A1 |
| 20210068714 | Crowley et al. | Mar 2021 | A1 |
| 20210113137 | Soli et al. | Apr 2021 | A1 |
| 20210204815 | Koskela et al. | Jul 2021 | A1 |
| 20210225482 | Crowley et al. | Jul 2021 | A1 |
| 20210257091 | Spang et al. | Aug 2021 | A1 |
| 20210287520 | Maeda et al. | Sep 2021 | A1 |
| 20210369130 | Felton et al. | Dec 2021 | A1 |
| 20210373746 | Felton et al. | Dec 2021 | A1 |
| 20210373747 | Felton et al. | Dec 2021 | A1 |
| 20210373748 | Felton et al. | Dec 2021 | A1 |
| 20210375157 | Sundstrom et al. | Dec 2021 | A1 |
| 20210375450 | Felton et al. | Dec 2021 | A1 |
| 20210401378 | Pho et al. | Dec 2021 | A1 |
| 20220047250 | Clements et al. | Feb 2022 | A1 |
| 20220066902 | Narra et al. | Mar 2022 | A1 |
| 20220142515 | Crowley | May 2022 | A1 |
| 20220157143 | Panneer Selvam et al. | May 2022 | A1 |
| 20220160258 | Williams et al. | May 2022 | A1 |
| 20220273204 | Kamath et al. | Sep 2022 | A1 |
| 20230016144 | Dryer et al. | Jan 2023 | A1 |
| 20230020517 | Narra et al. | Jan 2023 | A1 |
| 20230101625 | Soli et al. | Mar 2023 | A1 |
| 20230114054 | Crowley et al. | Apr 2023 | A1 |
| 20230367542 | Felton et al. | Nov 2023 | A1 |
| 20240013889 | Crowley et al. | Jan 2024 | A1 |
| 20240050016 | Soli et al. | Feb 2024 | A1 |
| 20240053862 | Narra et al. | Feb 2024 | A1 |
| 20240079130 | Maratta et al. | Mar 2024 | A1 |
| Number | Date | Country |
|---|---|---|
| 2815518 | May 2012 | CA |
| 102448555 | May 2012 | CN |
| 103191557 | Jul 2013 | CN |
| 103250158 | Aug 2013 | CN |
| 103403627 | Nov 2013 | CN |
| 103474080 | Dec 2013 | CN |
| 103561640 | Feb 2014 | CN |
| 103927175 | Jul 2014 | CN |
| 103986813 | Aug 2014 | CN |
| 104584020 | Apr 2015 | CN |
| 104680459 | Jun 2015 | CN |
| 104720765 | Jun 2015 | CN |
| 105260078 | Jan 2016 | CN |
| 105283840 | Jan 2016 | CN |
| 105388998 | Mar 2016 | CN |
| 105632508 | Jun 2016 | CN |
| 105721667 | Jun 2016 | CN |
| 105980008 | Sep 2016 | CN |
| 106164808 | Nov 2016 | CN |
| 106371816 | Feb 2017 | CN |
| 106415559 | Feb 2017 | CN |
| 106510719 | Mar 2017 | CN |
| 106537397 | Mar 2017 | CN |
| 106709235 | May 2017 | CN |
| 106725384 | May 2017 | CN |
| 106901720 | Jun 2017 | CN |
| 107278138 | Oct 2017 | CN |
| 107361755 | Nov 2017 | CN |
| 107454831 | Dec 2017 | CN |
| 107469327 | Dec 2017 | CN |
| 107508995 | Dec 2017 | CN |
| 107591211 | Jan 2018 | CN |
| 107713981 | Feb 2018 | CN |
| 108604327 | Sep 2018 | CN |
| 109287140 | Jan 2019 | CN |
| 109670007 | Apr 2019 | CN |
| 111344796 | Jun 2020 | CN |
| 202017002874 | Sep 2017 | DE |
| 1077046 | Feb 2001 | EP |
| 2391004 | Nov 2011 | EP |
| 2568409 | Mar 2013 | EP |
| 2921899 | Sep 2015 | EP |
| 3042606 | Jul 2016 | EP |
| 3096235 | Nov 2016 | EP |
| 3101882 | Dec 2016 | EP |
| 3255897 | Dec 2017 | EP |
| 3557590 | Oct 2019 | EP |
| 2004-80496 | Mar 2004 | JP |
| 2004-318503 | Nov 2004 | JP |
| 2005079814 | Mar 2005 | JP |
| 2008-011865 | Jan 2008 | JP |
| 2009-232301 | Oct 2009 | JP |
| 2009-538571 | Nov 2009 | JP |
| 2010-517725 | May 2010 | JP |
| 2010-122901 | Jun 2010 | JP |
| 2010-162297 | Jul 2010 | JP |
| 2010-181280 | Aug 2010 | JP |
| 2011-197992 | Oct 2011 | JP |
| 2011-200575 | Oct 2011 | JP |
| 2012-502343 | Jan 2012 | JP |
| 2012-45373 | Mar 2012 | JP |
| 2012-174055 | Sep 2012 | JP |
| 2012-524640 | Oct 2012 | JP |
| 2012-239808 | Dec 2012 | JP |
| 2013-17631 | Jan 2013 | JP |
| 2013-192608 | Sep 2013 | JP |
| 2013-207323 | Oct 2013 | JP |
| 2013-544140 | Dec 2013 | JP |
| 2014-168685 | Sep 2014 | JP |
| 2015-28686 | Feb 2015 | JP |
| 2015-73590 | Apr 2015 | JP |
| 2015-213686 | Dec 2015 | JP |
| 2016-502875 | Feb 2016 | JP |
| 2016-528016 | Sep 2016 | JP |
| 2016-177151 | Oct 2016 | JP |
| 2016-202751 | Dec 2016 | JP |
| 2016-538926 | Dec 2016 | JP |
| 2017-40981 | Feb 2017 | JP |
| 2017-117265 | Jun 2017 | JP |
| 2017-515520 | Jun 2017 | JP |
| 2017-134689 | Aug 2017 | JP |
| 2017-526073 | Sep 2017 | JP |
| 2017-182393 | Oct 2017 | JP |
| 2017-529880 | Oct 2017 | JP |
| 2017-211994 | Nov 2017 | JP |
| 2017-532069 | Nov 2017 | JP |
| 2018-504660 | Feb 2018 | JP |
| 6382433 | Aug 2018 | JP |
| 2018-191122 | Nov 2018 | JP |
| 2019-28806 | Feb 2019 | JP |
| 2019-32461 | Feb 2019 | JP |
| 2019-505035 | Feb 2019 | JP |
| 2019-36226 | Mar 2019 | JP |
| 2019-55076 | Apr 2019 | JP |
| 2019-207536 | Dec 2019 | JP |
| 2020-651 | Jan 2020 | JP |
| 2021-512429 | May 2021 | JP |
| 10-2002-0060421 | Jul 2002 | KR |
| 10-2008-0051460 | Jun 2008 | KR |
| 10-2009-0010287 | Jan 2009 | KR |
| 10-2012-0023657 | Mar 2012 | KR |
| 10-2013-0056646 | May 2013 | KR |
| 10-2013-0111569 | Oct 2013 | KR |
| 10-2013-0111570 | Oct 2013 | KR |
| 10-2015-0115385 | Oct 2015 | KR |
| 10-1594486 | Feb 2016 | KR |
| 10-2016-0028351 | Mar 2016 | KR |
| 10-2016-0076264 | Jun 2016 | KR |
| 10-2016-0077199 | Jul 2016 | KR |
| 10-2017-0003608 | Jan 2017 | KR |
| 10-2017-0019040 | Feb 2017 | KR |
| 10-2017-0019745 | Feb 2017 | KR |
| 10-2017-0029014 | Mar 2017 | KR |
| 10-2018-0018761 | Feb 2018 | KR |
| 10-2018-0129188 | Dec 2018 | KR |
| 102019-0094795 | Aug 2019 | KR |
| 2003067202 | Aug 2003 | WO |
| 2006046648 | May 2006 | WO |
| 2008073359 | Jun 2008 | WO |
| 2009095908 | Aug 2009 | WO |
| 2010028320 | Mar 2010 | WO |
| 2010047035 | Apr 2010 | WO |
| 2010126825 | Nov 2010 | WO |
| 2012048832 | Apr 2012 | WO |
| 2012060588 | May 2012 | WO |
| 2012061438 | May 2012 | WO |
| 2012061440 | May 2012 | WO |
| 2013103570 | Jul 2013 | WO |
| 2013109916 | Jul 2013 | WO |
| 2014015378 | Jan 2014 | WO |
| 2014033673 | Mar 2014 | WO |
| 2014197339 | Dec 2014 | WO |
| 2014207875 | Dec 2014 | WO |
| 2015009430 | Jan 2015 | WO |
| 2015027133 | Feb 2015 | WO |
| 2015084353 | Jun 2015 | WO |
| 2015153803 | Oct 2015 | WO |
| 2015164845 | Oct 2015 | WO |
| 2015183828 | Dec 2015 | WO |
| 2015187799 | Dec 2015 | WO |
| 2015198488 | Dec 2015 | WO |
| 2016036472 | Mar 2016 | WO |
| 2016036582 | Mar 2016 | WO |
| 2016151479 | Sep 2016 | WO |
| 2016161152 | Oct 2016 | WO |
| 2016164475 | Oct 2016 | WO |
| 2016179559 | Nov 2016 | WO |
| 2016207745 | Dec 2016 | WO |
| 2017003045 | Jan 2017 | WO |
| 2017037242 | Mar 2017 | WO |
| 2017054277 | Apr 2017 | WO |
| 2017062621 | Apr 2017 | WO |
| 2017087642 | May 2017 | WO |
| 2017090810 | Jun 2017 | WO |
| 2017172046 | Oct 2017 | WO |
| 2017213962 | Dec 2017 | WO |
| 2017215203 | Dec 2017 | WO |
| 2018132507 | Jul 2018 | WO |
| 2018148356 | Aug 2018 | WO |
| 2018213401 | Nov 2018 | WO |
| 2019020977 | Jan 2019 | WO |
| 2019099553 | May 2019 | WO |
| 2019168956 | Sep 2019 | WO |
| 2019177769 | Sep 2019 | WO |
| 2019217005 | Nov 2019 | WO |
| 2019236217 | Dec 2019 | WO |
| 2019240513 | Dec 2019 | WO |
| 2020247289 | Dec 2020 | WO |
| 2021011837 | Jan 2021 | WO |
| 2021212112 | Oct 2021 | WO |
| 2022010573 | Jan 2022 | WO |
| Entry |
|---|
| Final Office Action received for U.S. Appl. No. 17/952,182, mailed on Jan. 4, 2024, 9 pages. |
| Office Action received for European Patent Application No. 20760607.0, mailed on Jan. 3, 2024, 7 pages. |
| Office Action received for Japanese Patent Application No. 2022-573764, mailed on Dec. 25, 2023, 8 pages (4 pages of English Translation and 4 pages of Official Copy). |
| Notice of Allowance received for Japanese Patent Application No. 2022-078280, mailed on Sep. 4, 2023, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for U.S. Appl. No. 18/078,444, mailed on Aug. 31, 2023, 6 pages. |
| Office Action received for Australian Patent Application No. 2023212604, mailed on Sep. 4, 2023, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2023212604, mailed on Oct. 12, 2023, 3 pages. |
| Office Action received for Australian Patent Application No. 2021283914, mailed on Sep. 25, 2023, 5 pages. |
| Supplemental Notice of Allowance received for U.S. Appl. No. 18/078,444, mailed on Oct. 16, 2023, 4 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/031,723, mailed on Jan. 23, 2023, 4 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/952,053, mailed on Jan. 12, 2023, 12 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/317,084, mailed on Jan. 6, 2023, 6 pages. |
| Office Action received for Australian Patent Application No. 2021261861, mailed on Jan. 12, 2023, 4 pages. |
| Office Action received for Australian Patent Application No. 2022202459, mailed on Jan. 6, 2023, 3 pages. |
| Supplemental Notice of Allowance received for U.S. Appl. No. 17/317,084, mailed on Jan. 19, 2023, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 17/135,710, mailed on Aug. 18, 2023, 4 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/888,780, mailed on Aug. 17, 2023, 12 pages. |
| Office Action received for European Patent Application No. 20760607.0, mailed on Aug. 17, 2023, 7 pages. |
| Alivecor Kardiab., “How to Record a Clean EKG With Kardiaband”, Available Online at: https://www.youtube.com/watch?v =_Vlc9VE6VO4&t=2s, Nov. 30, 2017, 2 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/584,190, mailed on Dec. 4, 2023, 5 pages. |
| Decision on Appeal received for Korean Patent Application No. 10-2020-0124134, mailed on Oct. 20, 2023, 24 pages (4 pages of English Translation and 20 pages of Official Copy). |
| Hardwick Tim, “AliveCor ‘Kardia Band’ Medical Grade EKG Analyzer for Apple Watch Receives FDA Approval”, MacRumors, Available online at: https://www.macrumors.com/2017/11/30/alivecor-kardia-ekg-band-medical-fda-apple-watch/, Nov. 30, 2017, 3 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2023/021923, mailed on Oct. 4, 2023, 38 pages. |
| Invitation to Pay Additional Fee received for PCT Patent Application No. PCT/US2023/021923, mailed on Aug. 25, 2023, 18 pages. |
| Luo et al., “Detection and Prediction of Ovulation From Body Temperature Measured by an In-Ear Wearable Thermometer”, IEEE Transactions on Biomedical Engineering, Available online at:10.1109/TBME.2019.2916823, vol. 67, No. 2, May 15, 2019, pp. 512-522. |
| Notice of Allowance received for Korean Patent Application No. 10-2020-0124134, mailed on Nov. 21, 2023, 8 pages (2 pages of English Translation and 6 pages of Official Copy). |
| Office Action received for Danish Patent Application No. PA202070395, mailed on Nov. 3, 2023, 3 pages. |
| Prasad et al., “Understanding Sharing Preferences and Behavior for Mhealth Devices”, Proceedings of the 2012 ACM workshop on Privacy in the electronic society, Available online at: https://dl.acm.org/doi/10.1145/2381966.2381983, Oct. 15, 2012, pp. 117-128. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/888,780, mailed on Dec. 14, 2023, 3 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2022-131993, mailed on Dec. 18, 2023, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2022-7012608, mailed on Dec. 5, 2023, 12 pages (5 pages of English Translation and 7 pages of Official Copy). |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/031,723, mailed on Mar. 21, 2021, 5 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/031,779, mailed on Mar. 10, 2022, 2 pages. |
| Brief Communication Regarding Oral Proceedings received for European Patent Application No. 20180581.9, mailed on Jan. 26, 2022, 1 page. |
| Brief Communication regarding Oral Proceedings received for European Patent Application No. 20180592.6, mailed on Jan. 26, 2022, 2 pages. |
| Brief Communication Regarding Oral Proceedings received for European Patent Application No. 20182116.2, mailed on Apr. 13, 2022, 3 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/990,846, mailed on Feb. 9, 2022, 3 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 17/031,717, mailed on Apr. 15, 2022, 3 pages. |
| Decision to Refuse received for European Patent Application No. 20180581.9, mailed on Apr. 13, 2022, 16 pages. |
| Intention to Grant received for Danish Patent Application No. PA202070619, mailed on Jan. 17, 2022, 2 pages. |
| Intention to Grant received for European Patent Application No. 20180592.6, mailed on Apr. 20, 2022, 21 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2020/042439, mailed on Jan. 27, 2022, 10 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2020/070280, mailed on Mar. 17, 2022, 15 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2021/048568, mailed on Jan. 7, 2022, 14 pages. |
| Minutes of the Oral Proceedings received for European Patent Application No. 20180581.9, mailed on Apr. 13, 2022, 10 pages. |
| Minutes of the Oral Proceedings received for European Patent Application No. 20180592.6, mailed on Apr. 7, 2022, 10 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/888,780, mailed on Apr. 20, 2022, 22 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/031,723, mailed on Jan. 24, 2022, 17 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/031,779, mailed on Feb. 16, 2022, 17 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/041,415, mailed on Mar. 29, 2022, 11 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2020239692, mailed on Apr. 6, 2022, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2020239740, mailed on Feb. 22, 2022., 3 pages. |
| Notice of Allowance received for Chinese Patent Application No. 202010606407.4, mailed on Jan. 24, 2022, 2 pages (1 page of English Translation and 1 page of Official Copy). |
| Notice of Allowance received for Japanese Patent Application No. 2018-184532, mailed on Jan. 17, 2022, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for Japanese Patent Application No. 2020-160023, mailed on Apr. 11, 2022, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for Japanese Patent Application No. 2021-571467, mailed on Apr. 11, 2022, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for Korean Patent Application No. 10-2021-7042504, mailed on Jan. 17, 2022, 6 pages (1 page of English Translation and 5 pages of Official Copy). |
| Notice of Allowance received for U.S. Appl. No. 16/894,309, mailed on Feb. 25, 2022, 9 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/990,846, mailed on Jan. 20, 2022, 6 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/031,717, mailed on Mar. 16, 2022, 12 pages. |
| Office Action received for Australian Patent Application No. 2020239692, mailed on Jan. 27, 2022, 3 pages. |
| Office Action received for Chinese Patent Application No. 201910858933.7, mailed on Dec. 30, 2021, 9 pages (4 pages of English Translation and 5 pages of Official Copy). |
| Office Action received for Japanese Patent Application No. 2020-160023, mailed on Jan. 17, 2022, 11 pages (6 pages of English Translation and 5 pages of Official Copy). |
| Result of Consultation received for European Patent Application No. 20180581.9, mailed on Jan. 21, 2022, 14 pages. |
| Result of Consultation received for European Patent Application No. 20180592.6, mailed on Jan. 26, 2022, 18 pages. |
| Supplemental Notice of Allowance received for U.S. Appl. No. 16/894,309, mailed on Apr. 8, 2022, 3 pages. |
| Supplemental Notice of Allowance received for U.S. Appl. No. 16/894,309, mailed on Jan. 25, 2022, 2 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2021/048568, mailed on Mar. 9, 2023, 11 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/851,451, mailed on Feb. 24, 2023, 28 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/337,147, mailed on Feb. 21, 2023, 15 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/953,781, mailed on Feb. 27, 2023, 5 pages. |
| Office Action received for Australian Patent Application No. 2022204568, mailed on Mar. 11, 2023, 4 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/031,723, mailed on Oct. 31, 2023, 4 pages. |
| Final Office Action received for U.S. Appl. No. 17/337,147, mailed on Oct. 31, 2023, 17 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2022-078277, mailed on Oct. 27, 2023, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for U.S. Appl. No. 17/135,710, mailed on Nov. 6, 2023, 7 pages. |
| Office Action received for Chinese Patent Application No. 202180053264.1, mailed on Sep. 23, 2023, 17 pages (9 pages of English Translation and 8 pages of Official Copy). |
| Office Action received for European Patent Application No. 20746438.9, mailed on Oct. 31, 2023, 9 pages. |
| Office Action received for European Patent Application No. 20751022.3, mailed on Oct. 19, 2023, 8 pages. |
| Office Action received for European Patent Application No. 20753659.0, mailed on Oct. 26, 2023, 9 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/953,781, mailed on Oct. 31, 2022, 12 pages. |
| Brief Communication Regarding Oral Proceedings received for European Patent Application No. 20746438.9, mailed on Nov. 7, 2022, 1 page. |
| Notice of Allowance received for U.S. Appl. No. 16/953,781, mailed on Nov. 9, 2022, 7 pages. |
| Office Action received for European Patent Application No. 20746438.9, mailed on Oct. 31, 2022, 7 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/851,451, mailed on Aug. 5, 2022, 3 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/888,780, mailed on Aug. 2, 2022, 4 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/953,781, mailed on Jul. 26, 2022, 9 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2020-551585, mailed on Jul. 22, 2022, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2020-0124134, mailed on Jul. 28, 2022, 22 pages (11 pages of English Translation and 11 pages of Official Copy). |
| Intention to Grant received for European Patent Application No. 20182116.2, mailed on Jun. 2, 2022, 8 pages. |
| Minutes of the Oral Proceedings received for European Patent Application No. 20182116.2, mailed on May 24, 2022, 7 pages. |
| Notice of Allowance received for Korean Patent Application No. 10-2022-7008569, mailed on May 19, 2022, 5 pages (2 pages of English Translation and 3 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 202011220489.5, mailed on Apr. 25, 2022, 15 pages (9 pages of English Translation and 6 pages of Official Copy). |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/031,723, mailed on Aug. 30, 2022, 4 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/031,779, mailed on Aug. 29, 2022, 2 pages. |
| Decision to Grant received for European Patent Application No. 20180592.6, mailed on Sep. 1, 2022, 3 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/041,415, mailed on Aug. 31, 2022, 7 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/317,084, mailed on Aug. 29, 2022, 10 pages. |
| Office Action received for Korean Patent Application No. 10-2020-7033395, mailed on Aug. 29, 2022, 11 pages (4 pages of English Translation and 7 pages of Official Copy). |
| Notice of Allowance received for Chinese Patent Application No. 202111611270.2, mailed on Sep. 21, 2022, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Supplemental Notice of Allowance received for U.S. Appl. No. 17/041,415, mailed on Sep. 20, 2022, 2 pages. |
| Supplemental Notice of Allowance received for U.S. Appl. No. 17/317,084, mailed on Sep. 20, 2022, 2 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2022204568, mailed on Jul. 27, 2023, 3 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/135,710, mailed on Jul. 27, 2023, 9 pages. |
| Office Action received for Japanese Patent Application No. 2022-078280, mailed on Jul. 24, 2023, 8 pages (4 pages of English Translation and 4 pages of Official Copy). |
| Corrected Notice of Allowance received for U.S. Appl. No. 17/031,717, mailed on May 19, 2022, 3 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/851,451, mailed on May 9, 2022, 26 pages. |
| Decision to Grant received for Danish Patent Application No. PA202070619, mailed on Aug. 11, 2022, 2 pages. |
| Office Action received for Japanese Patent Application No. 2021-167557, mailed on Aug. 15, 2022, 5 pages (3 pages of English Translation and 2 pages of Official Copy). |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2021/035227, mailed on Dec. 15, 2022, 10 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2021/035504, mailed on Dec. 15, 2022, 8 pages. |
| Office Action received for Australian Patent Application No. 2020313970, mailed on Dec. 22, 2022, 3 pages. |
| Brief Communication Regarding Oral Proceedings received for European Patent Application No. 20203526.7, mailed on Dec. 23, 2022, 4 pages. |
| Brief Communication Regarding Oral Proceedings received for European Patent Application No. 20203526.7, mailed on Jan. 18, 2023, 1 page. |
| Intention to Grant received for European Patent Application No. 20203526.7, mailed on Feb. 10, 2023, 9 pages. |
| Notice of Allowance received for Chinese Patent Application No. 202210238202.4, mailed on Jan. 13, 2023, 7 pages (3 pages of English Translation and 4 pages of Official Copy). |
| Notice of Allowance received for Japanese Patent Application No. 2021-167557, mailed on Jan. 27, 2023, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for U.S. Appl. No. 17/031,779, mailed on Feb. 1, 2023, 11 pages. |
| Office Action received for European Patent Application No. 20746438.9, mailed on Feb. 1, 2023, 9 pages. |
| Office Action received for European Patent Application No. 20760607.0, mailed on Feb. 1, 2023, 13 pages. |
| Result of Consultation received for European Patent Application No. 20203526.7, mailed on Jan. 13, 2023, 3 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/031,717, mailed on Nov. 4, 2021, 5 pages. |
| Brief Communication Regarding Oral Proceedings received for European Patent Application No. 20180581.9, mailed on Nov. 30, 2021, 1 page. |
| Brief Communication regarding Oral Proceedings received for European Patent Application No. 20180592.6, mailed on Dec. 21, 2021, 1 page. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/143,997, mailed on Nov. 16, 2021, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/921,312, mailed on Dec. 7, 2021, 2 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2020/035164, mailed on Dec. 16, 2021, 19 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2020/035462, mailed on Dec. 16, 2021, 16 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2020/025768, mailed on Dec. 16, 2021, 8 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2020/035474, mailed on Dec. 16, 2021, 11 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2021/035504, mailed on Sep. 16, 2021, 12 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2020288147, mailed on Dec. 22, 2021, 3 pages. |
| Notice of Allowance received for Chinese Patent Application No. 202010618569.X, mailed on Jan. 7, 2022, 2 pages (1 page of English Translation and 1 page of Official Copy). |
| Notice of Allowance received for Korean Patent Application No. 10-2021-7038005, mailed on Dec. 14, 2021, 4 pages (2 pages of English Translation and 2 pages of Official Copy). |
| Notice of Allowance received for U.S. Appl. No. 16/586,154, mailed on Oct. 15, 2021, 8 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/894,309, mailed on Nov. 5, 2021, 12 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/921,312, mailed on Nov. 29, 2021, 5 pages. |
| Office Action received for Australian Patent Application No. 2019234289, mailed on Nov. 1, 2021, 4 pages. |
| Office Action received for Australian Patent Application No. 2020230340, mailed on Oct. 11, 2021, 4 pages. |
| Office Action received for Chinese Patent Application No. 202010606407.4, mailed on Nov. 18, 2021, 6 pages (3 pages of English Translation and 3 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 202010618240.3, mailed on Dec. 3, 2021, 23 pages (14 pages of English Translation and 9 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 202011220489.5, mailed on Dec. 1, 2021, 19 pages (11 pages of English Translation and 8 pages of Official Copy). |
| Office Action received for Danish Patent Application No. PA202070395, mailed on Dec. 15, 2021, 5 pages. |
| Office Action received for Danish Patent Application No. PA202070620, mailed on Nov. 19, 2021, 2 pages. |
| Office Action received for European Patent Application No. 20203526.7, mailed on Nov. 23, 2021, 9 pages. |
| Office Action received for Indian Patent Application No. 202014041484, mailed on Dec. 8, 2021, 8 pages. |
| Office Action received for Japanese Patent Application No. 2020-551585, mailed on Jan. 6, 2022, 11 pages (5 pages of English Translation and 6 pages of Official Copy). |
| Summons to Attend Oral Proceedings received for European Patent Application No. 20182116.2, mailed on Dec. 21, 2021, 7 pages. |
| Supplemental Notice of Allowance received for U.S. Appl. No. 16/894,309, mailed on Dec. 24, 2021, 2 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/041,415, mailed on Jun. 29, 2022, 2 pages. |
| Final Office Action received for U.S. Appl. No. 17/031,723, mailed on Jul. 12, 2022, 25 pages. |
| Final Office Action received for U.S. Appl. No. 17/031,779, mailed on Jul. 14, 2022, 19 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/031,717, mailed on Jul. 7, 2022, 12 pages. |
| Summons to Attend Oral Proceedings received for European Patent Application No. 20203526.7, mailed on Jun. 23, 2022, 9 pages. |
| Office Action received for Chinese Patent Application No. 202010618240.3, mailed on May 25, 2022, 20 pages (11 pages of English Translation and 9 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 202111611270.2, mailed on May 10, 2022, 16 pages (8 pages of English Translation and 8 pages of Official Copy). |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/851,451, mailed on Apr. 20, 2023, 4 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/031,723, mailed on Jun. 22, 2023, 2 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/952,053, mailed on Apr. 5, 2023, 6 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/953,781, mailed on Mar. 30, 2023, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 17/031,779, mailed on Jun. 14, 2023, 2 pages. |
| Decision to Grant received for European Patent Application No. 20203526.7, mailed on Jun. 22, 2023, 4 pages. |
| Final Office Action received for U.S. Appl. No. 16/851,451, mailed on Jun. 1, 2023, 35 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/031,723, mailed on Jun. 2, 2023, 23 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/952,182, mailed on Mar. 28, 2023, 9 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2020313970, mailed on Jun. 22, 2023, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2022202459, mailed on May 11, 2023, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2022203508, mailed on Jun. 27, 2023, 3 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2022-502594, mailed on Jul. 7, 2023, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for U.S. Appl. No. 17/031,779, mailed on May 26, 2023, 9 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/952,053, mailed on April 17, 2023, 6 pages. |
| Notice of Allowance received for U.S. Appl. No. 18/078,444, mailed on May 12, 2023, 9 pages. |
| Office Action received for Australian Patent Application No. 2020313970, mailed on Mar. 22, 2023, 4 pages. |
| Office Action received for Australian Patent Application No. 2021261861, mailed on May 3, 2023, 4 pages. |
| Office Action received for Australian Patent Application No. 2022202459, mailed on Mar. 27, 2023, 5 pages. |
| Office Action received for Australian Patent Application No. 2022203508, mailed on May 19, 2023, 2 pages. |
| Office Action received for Australian Patent Application No. 2022204568, mailed on May 22, 2023, 4 pages. |
| Office Action received for Chinese Patent Application No. 202210004176.9, mailed on Apr. 28, 2023, 12 pages (6 pages of English Translation and 6 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 202210004176.9, mailed on Feb. 19, 2023, 23 pages (14 pages of English Translation and 9 pages of Official Copy). |
| Office Action received for Danish Patent Application No. PA202070395, mailed on Jul. 5, 2023, 6 pages. |
| Office Action received for Danish Patent Application No. PA202070395, mailed on Mar. 31, 2023, 3 pages. |
| Office Action received for European Patent Application No. 20746438.9, mailed on Jul. 4, 2023, 7 pages. |
| Office Action received for German Patent Application No. 112020002566.7, mailed on Mar. 24, 2023, 32 pages (14 pages of English Translation and 18 pages of official copy). |
| Office Action received for Indian Patent Application No. 202215032692, mailed on Jun. 15, 2023, 3 pages. |
| Office Action received for Japanese Patent Application No. 2022-078277, mailed on Jun. 9, 2023, 11 pages (6 pages of English Translation and 5 pages of Official Copy). |
| Office Action received for Japanese Patent Application No. 2022-502594, mailed on Mar. 20, 2023, 10 pages (5 pages of English Translation and 5 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2020-0124134, mailed on Jun. 23, 2023, 8 pages (4 pages of English Translation and 4 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2020-0124134, mailed on Mar. 28, 2023, 9 pages (4 pages of English Translation and 5 pages of Official Copy). |
| Supplemental Notice of Allowance received for U.S. Appl. No. 18/078,444, mailed on Jun. 15, 2023, 2 pages. |
| Levy et al., “A good little tool to get to know yourself a bit better”, a qualitative study on users' experiences of app-supported menstrual tracking in Europe., In: BMC Public Health, vol. 19, 2019, pp. 1-11. |
| Advisory Action received for U.S. Appl. No. 16/144,864, mailed on Jul. 29, 2019, 6 pages. |
| Advisory Action received for U.S. Appl. No. 16/143,909, mailed on Nov. 7, 2019, 5 pages. |
| Advisory Action received for U.S. Appl. No. 16/143,997, mailed on Dec. 26, 2019, 7 pages. |
| Advisory Action received for U.S. Appl. No. 16/144,849, mailed on Aug. 12, 2019, 5 pages. |
| Advisory Action received for U.S. Appl. No. 16/144,864, mailed on Jul. 6, 2020, 6 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/143,997, mailed on Aug. 13, 2020, 3 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/144,849, mailed on Jan. 21, 2020, 6 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/144,864, mailed on Apr. 29, 2020, 4 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/586,154, mailed on Mar. 11, 2020, 4 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/894,309, mailed on Jan. 26, 2021, 3 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/138,809, mailed on Dec. 16, 2020, 7 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/138,809, mailed on Jun. 9, 2020, 4 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/143,997, mailed on May 3, 2021, 4 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/144,864, mailed on Jun. 22, 2020, 3 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/584,186, mailed on Feb. 3, 2020, 4 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/586,154, mailed on Apr. 14, 2021, 4 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/586,154, mailed on Dec. 11, 2020, 5 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/586,154, mailed on Sep. 3, 2021, 4 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/880,552, mailed on Apr. 21, 2021, 3 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/880,552, mailed on Dec. 16, 2020, 6 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/880,552, mailed on Oct. 20, 2020, 6 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/880,714, mailed on Feb. 26, 2021, 5 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/894,309, mailed on Jun. 25, 2021, 4 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/907,261, mailed on Dec. 16, 2020, 6 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/907,261, mailed on Jul. 16, 2021, 10 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/907,261, mailed on Mar. 25, 2021, 2 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/031,704, mailed on Feb. 9, 2021, 3 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/031,704, mailed on Jun. 25, 2021, 3 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/031,717, mailed on Jan. 29, 2021, 5 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/031,717, mailed on May 17, 2021, 5 pages. |
| Certificate of Examination received for Australian Patent Application No. 2019100222, mailed on Aug. 29, 2019, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/143,909, mailed on Feb. 20, 2020, 3 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/143,909, mailed on Mar. 18, 2020, 3 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/143,959, mailed on Dec. 13, 2019, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/143,997, mailed on Jul. 2, 2021, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/143,997, mailed on Jun. 4, 2021, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/143,997, mailed on Oct. 21, 2021, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/584, 186, mailed on Jul. 31, 2020, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/586,154, mailed on Oct. 27, 2021, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/880,552, mailed on Dec. 22, 2021, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/880,552, mailed on Dec. 23, 2020, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/880,552, mailed on Jul. 7, 2021, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/921,312, mailed on Sep. 24, 2021, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 17/031,704, mailed on Nov. 2, 2021, 7 pages. |
| Decision on Appeal received for Korean Patent Application No. 10-2019-7025538, mailed on Feb. 24, 2021, 20 pages. |
| Decision to Grant received for Danish Patent Application No. PA201870379, mailed on Jul. 5, 2019, 2 pages. |
| Decision to Grant received for Danish Patent Application No. PA201870600, mailed on Oct. 17, 2019, 2 pages. |
| Decision to Grant received for Danish Patent Application No. PA201870601, mailed on Aug. 17, 2020, 2 pages. |
| Decision to Grant received for Danish Patent Application No. PA201870602, mailed on Aug. 18, 2020, 2 pages. |
| European Search Report received for European Patent Application No. 20182116.2, mailed on Oct. 21, 2020, 4 pages. |
| Extended European Search Report received for European Patent Application No. 20180581.9, mailed on Aug. 12, 2020, 9 pages. |
| Extended European Search Report received for European Patent Application No. 20180592.6, mailed on Aug. 11, 2020, 10 pages. |
| Extended European Search Report received for European Patent Application No. 20203526.7, mailed on Jan. 29, 2021, 13 pages. |
| Final Office Action received for U.S. Appl. No. 16/138,809, mailed on Aug. 27, 2020, 24 pages. |
| Final Office Action received for U.S. Appl. No. 16/143,909, mailed on Aug. 28, 2019, 20 pages. |
| Final Office Action received for U.S. Appl. No. 16/143,997, mailed on Feb. 9, 2021, 16 pages. |
| Final Office Action received for U.S. Appl. No. 16/143,997, mailed on Sep. 30, 2019, 16 pages. |
| Final Office Action received for U.S. Appl. No. 16/144,030, mailed on Feb. 13, 2020, 11 pages. |
| Final Office Action received for U.S. Appl. No. 16/144,030, mailed on Oct. 1, 2019, 13 pages. |
| Final Office Action received for U.S. Appl. No. 16/144,849, mailed on Jun. 7, 2019, 29 pages. |
| Final Office Action received for U.S. Appl. No. 16/144,864, mailed on May 17, 2019, 24 pages. |
| Final Office Action received for U.S. Appl. No. 16/144,864, mailed on May 28, 2020, 29 pages. |
| Final Office Action received for U.S. Appl. No. 16/586,154, mailed on Jul. 6, 2020, 27 pages. |
| Final Office Action received for U.S. Appl. No. 16/586, 154, mailed on May 24, 2021, 29 pages. |
| Final Office Action received for U.S. Appl. No. 16/894,309, mailed on Feb. 24, 2021, 30 pages. |
| Final Office Action received for U.S. Appl. No. 16/907,261, mailed on Mar. 18, 2021, 20 pages. |
| Final Office Action received for U.S. Appl. No. 17/031,704, mailed on Apr. 1, 2021, 31 pages. |
| Final Office Action received for U.S. Appl. No. 17/031,717, mailed on Feb. 24, 2021, 23 pages. |
| Fitbit App, Available online at: <http://web.archive.org/web/20180114083150/https://www.fitbit.com/au/app>, Jan. 14, 2018, 8 pages. |
| Graphs and Charts, online available at: <https://www.teachervision.com/lesson-planning/graph-chart-teacher-resources, retrieved on Dec. 12, 2018, 4 pages. |
| Intention to Grant received for Danish Patent Application No. PA201870379, mailed on May 2, 2019, 2 pages. |
| Intention to Grant received for Danish Patent Application No. PA201870600, mailed on Jul. 10, 2019, 2 pages. |
| Intention to Grant received for Danish Patent Application No. PA201870601, mailed on Apr. 24, 2020, 2 pages. |
| Intention to Grant received for Danish Patent Application No. PA201870602, mailed on Apr. 24, 2020, 2 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2019/019694, mailed on Sep. 24, 2020, 12 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2019/024570, mailed on Nov. 19, 2020, 10 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2019/019694, mailed on Sep. 2, 2019, 17 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2019/024570, mailed on Aug. 8, 2019, 18 pages. |
| International Search Report and written Opinion received for PCT Patent Application No. PCT/US2020/025768, mailed on Aug. 10, 2020, 11 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2020/035164, mailed on Feb. 8, 2021, 26 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2020/035462, mailed on Sep. 11, 2020, 17 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2020/035474, mailed on Nov. 26, 2020, 16 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2020/042439, mailed on Oct. 9, 2020, 14 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2020/070280, mailed on Nov. 30, 2020, 20 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2021/035227, mailed on Oct. 6, 2021, 17 pages. |
| Invitation to Pay Addition Fees received for PCT Patent Application No. PCT/US2020/035474, mailed on Oct. 2, 2020, 11 pages. |
| Invitation to Pay Additional Fees and Partial International Search Report received for PCT Patent Application No. PCT/US2020/035164, mailed on Oct. 16, 2020, 14 pages. |
| Invitation to Pay Additional Fees received for PCT Patent Application No. PCT/US2019/019694, mailed on Jul. 10, 2019, 12 pages. |
| Invitation to Pay Additional Fees received for PCT Patent Application No. PCT/US2020/070280, mailed on Oct. 7, 2020, 12 pages. |
| Invitation to Pay Search Fees received for European Patent Application No. 19726205.8, mailed on Feb. 14, 2020, 5 pages. |
| Multi-Set Bar Chart, The Data Visualization Catalogue, Available Online at: https://datavizcatalogue.com/methods/multiset_barchart.html, Feb. 8, 2014, 3 pages. |
| Non-Final Office Action Received for U.S. Appl. No. 16/144,864, mailed on Dec. 18, 2018, 19 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/138,809, mailed on Feb. 28, 2020, 22 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/143,909, mailed on Apr. 19, 2019, 16 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/143,959, mailed on Apr. 17, 2019, 15 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/143,997, mailed on Jul. 27, 2020, 15 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/143,997, mailed on May 21, 2019, 15 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/144,030, mailed on Apr. 12, 2019, 8 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/144,030, mailed on Nov. 5, 2020, 5 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/144,849, mailed on Dec. 31, 2018, 28 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/144,849, mailed on Sep. 17, 2019, 9 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/144,864, mailed on Jan. 31, 2020, 29 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/584,186, mailed on Dec. 6, 2019, 13 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/586,154, mailed on Dec. 9, 2019, 23 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/586,154, mailed on Dec. 28, 2020, 26 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/880,552, mailed on Feb. 19, 2021, 11 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/880,552, mailed on Jul. 23, 2020, 19 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/880,714, mailed on Oct. 28, 2020, 11 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/894,309, mailed on Oct. 15, 2020, 24 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/907,261, mailed on Sep. 30, 2020, 22 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/990,846, mailed on May 10, 2021, 16 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/031,704, mailed on Dec. 10, 2020, 30 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/031,717, mailed on Nov. 19, 2020, 22 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/031,717, mailed on Sep. 14, 2021, 35 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2019222943, mailed on May 5, 2020, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2020204153, mailed on Jul. 6, 2020, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2020256383, mailed on Aug. 3, 2021, 3 pages. |
| Notice of Allowance received for Chinese Patent Application No. 201910972529.2, mailed on Sep. 14, 2020, 6 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2019-162293, mailed on Apr. 9, 2021, 4 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2020-104679, mailed on Jan. 4, 2021, 4 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2020-153166, mailed on Sep. 13, 2021, 4 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2020-547369, mailed on Jul. 16, 2021, 4 pages. |
| Notice of Allowance received for Korean Patent Application No. 10-2019-7025538, mailed on Mar. 10, 2021, 5 pages. |
| Notice of Allowance received for Korean Patent Application No. 10-2020-7026035, mailed on Aug. 23, 2021, 4 pages. |
| Notice of Allowance received for Korean Patent Application No. 10-2020-7026391, mailed on May 11, 2021, 3 pages. |
| Notice of Allowance received for Korean Patent Application No. 10-2020-7026453, mailed on May 11, 2021, 3 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/138,809, mailed on Apr. 16, 2021, 11 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/138,809, mailed on Jul. 20, 2021, 6 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/143,909, mailed on Jan. 21, 2020, 9 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/143,959, mailed on Oct. 31, 2019, 10 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/143,997, mailed on May 13, 2021, 10 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/143,997, mailed on Sep. 30, 2021, 8 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/144,030, mailed on Apr. 5, 2021, 8 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/144,849, mailed on Apr. 17, 2020, 2 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/144,849, mailed on Mar. 6, 2020, 9 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/144,864, mailed on Feb. 9, 2021, 13 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/144,864, mailed on Jul. 28, 2020, 27 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/144,864, mailed on Mar. 12, 2021, 2 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/144,864, mailed on Mar. 30, 2021, 2 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/144,864, mailed on Sep. 10, 2020, 3 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/144,864, mailed on Sep. 16, 2020, 2 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/144,864, mailed on Sep. 29, 2020, 2 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/584,186, mailed on Mar. 24, 2020, 10 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/880,552, mailed on Dec. 1, 2020, 7 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/880,552, mailed on Jul. 23, 2021, 5 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/880,552, mailed on May 12, 2021, 7 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/880,552, mailed on Nov. 24, 2021, 5 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/880,714, mailed on Jun. 9, 2021, 6 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/880,714, mailed on Mar. 19, 2021, 7 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/907,261, mailed on Aug. 13, 2021, 8 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/907,261, mailed on Sep. 28, 2021, 6 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/921,312, mailed on Sep. 14, 2021, 9 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/990,846, mailed on Sep. 22, 2021, 9 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/031,704, mailed on Jul. 21, 2021, 10 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/031,727, mailed on Dec. 24, 2020, 12 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/031,727, mailed on Jun. 25, 2021, 6 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/031,727, mailed on Mar. 12, 2021, 7 pages. |
| Office Action received for Australian Patent Application No. 2019100222, mailed on May 24, 2019, 6 pages. |
| Office Action received for Australian Patent Application No. 2019100495, mailed on Mar. 6, 2020, 3 pages. |
| Office Action received for Australian Patent Application No. 2019100495, mailed on Mar. 16, 2020, 3 pages. |
| Office Action received for Australian Patent Application No. 2019100495, mailed on Sep. 17, 2019, 7 pages. |
| Office Action received for Australian Patent Application No. 2019222943, mailed on Oct. 3, 2019, 3 pages. |
| Office Action received for Australian Patent Application No. 2019234289, mailed on Jul. 20, 2021, 4 pages. |
| Office Action received for Australian Patent Application No. 2019234289, mailed on Mar. 16, 2021, 8 pages. |
| Office Action received for Australian Patent Application No. 2019234289, mailed on Nov. 2, 2020, 6 pages. |
| Office Action received for Australian Patent Application No. 2020230340, mailed on Mar. 2, 2021, 6 pages. |
| Office Action received for Australian Patent Application No. 2020230340, mailed on May 27, 2021, 5 pages. |
| Office Action received for Australian Patent Application No. 2020230340, mailed on Nov. 2, 2020, 5 pages. |
| Office Action received for Australian Patent Application No. 2020239692, mailed on Jul. 20, 2021, 5 pages. |
| Office Action received for Australian Patent Application No. 2020239740, mailed on Jul. 9, 2021, 4 pages. |
| Office Action received for Australian Patent Application No. 2020239740, mailed on Sep. 28, 2021, 5 pages. |
| Office Action received for Australian Patent Application No. 2020256383, mailed on Jun. 4, 2021, 3 pages. |
| Office Action received for Chinese Patent Application No. 201910858933.7, mailed on Aug. 18, 2020, 14 pages. |
| Office Action received for Chinese Patent Application No. 201910858933.7, mailed on Jun. 29, 2021, 8 pages. |
| Office Action received for Chinese Patent Application No. 201910972529.2, mailed on Jun. 28, 2020, 8 pages. |
| Office Action received for Chinese Patent Application No. 202010606407.4, mailed on Jan. 27, 2021, 16 pages. |
| Office Action received for Chinese Patent Application No. 202010606407.4, mailed on Jun. 2, 2021, 12 pages. |
| Office Action received for Chinese Patent Application No. 202010618240.3, mailed on Mar. 29, 2021, 21 pages. |
| Office Action received for Chinese Patent Application No. 202010618569.X, mailed on Mar. 12, 2021, 14 pages. |
| Office Action received for Chinese Patent Application No. 202010618569.X, mailed on Sep. 7, 2021, 7 pages. |
| Office Action received for Chinese Patent Application No. 202011220489.5, mailed on Jun. 1, 2021, 12 pages. |
| Office Action received for Danish Patent Application No. PA201870378, mailed on Feb. 25, 2019, 3 pages. |
| Office Action received for Danish Patent Application No. PA201870378, mailed on Jan. 6, 2020, 3 pages. |
| Office Action received for Danish Patent Application No. PA201870379, mailed on Feb. 28, 2019, 3 pages. |
| Office Action received for Danish Patent Application No. PA201870380, mailed on Mar. 5, 2020, 2 pages. |
| Office Action received for Danish Patent Application No. PA201870380, mailed on Mar. 27, 2019, 4 pages. |
| Office Action received for Danish Patent Application No. PA201870380, mailed on Sep. 11, 2018, 9 pages. |
| Office Action received for Danish Patent Application No. PA201870599, mailed on Dec. 20, 2019, 5 pages. |
| Office Action received for Danish Patent Application No. PA201870600, mailed on May 8, 2019, 3 pages. |
| Office Action received for Danish Patent Application No. PA201870601, mailed on Dec. 13, 2018, 8 pages. |
| Office Action received for Danish Patent Application No. PA201870601, mailed on Jan. 14, 2020, 3 pages. |
| Office Action received for Danish Patent Application No. PA201870601, mailed on Jun. 25, 2019, 3 pages. |
| Office Action received for Danish Patent Application No. PA201870602, mailed on Feb. 5, 2020, 3 pages. |
| Office Action received for Danish Patent Application No. PA201870602, mailed on Jun. 26, 2019, 3 pages. |
| Office Action received for Danish Patent Application No. PA201970534, mailed on Feb. 16, 2021, 2 pages. |
| Office Action received for Danish Patent Application No. PA201970534, mailed on Jun. 29, 2020, 2 pages. |
| Office Action received for Danish Patent Application No. PA202070335, mailed on Jun. 11, 2021, 4 pages. |
| Office Action received for Danish Patent Application No. PA202070335, mailed on Nov. 17, 2021, 6 pages. |
| Office Action received for Danish Patent Application No. PA202070619, mailed on Aug. 27, 2021, 12 pages. |
| Office Action received for Danish Patent Application No. PA202070619, mailed on Oct. 14, 2021, 3 pages. |
| Office Action received for Danish Patent Application No. PA202070620, mailed on May 10, 2021, 5 pages. |
| Office Action received for European Patent Application No. 19721883.7, mailed on Jan. 10, 2020, 4 pages. |
| Office Action received for European Patent Application No. 19721883.7, mailed on Jun. 15, 2021, 9 pages. |
| Office Action received for European Patent Application No. 19721883.7, mailed on May 28, 2020, 11 pages. |
| Office Action received for European Patent Application No. 19726205.8, mailed on Jun. 26, 2020, 9 pages. |
| Office Action received for European Patent Application No. 20180581.9, mailed on Apr. 1, 2021, 11 pages. |
| Office Action received for European Patent Application No. 20180592.6, mailed on Apr. 1, 2021, 11 pages. |
| Office Action received for European Patent Application No. 20182116.2, mailed on May 25, 2021, 9 pages. |
| Office Action received for European Patent Application No. 20182116.2, mailed on Nov. 6, 2020, 9 pages. |
| Office Action received for Japanese Patent Application No. 2018-184532, mailed on Mar. 1, 2021, 11 pages. |
| Office Action received for Japanese Patent Application No. 2019-162293, mailed on Jan. 31, 2020, 8 pages. |
| Office Action received for Japanese Patent Application No. 2019-162293, mailed on Jul. 27, 2020, 9 pages. |
| Office Action received for Japanese Patent Application No. 2020-104679, mailed on Sep. 18, 2020, 13 pages. |
| Office Action received for Japanese Patent Application No. 2020-153166, mailed on May 31, 2021, 6 pages. |
| Office Action received for Japanese Patent Application No. 2020-547369, mailed on Apr. 9, 2021, 4 pages. |
| Office Action received for Korean Patent Application No. 10-2019-7025538, mailed on Aug. 15, 2020, 8 pages. |
| Office Action received for Korean Patent Application No. 10-2019-7025538, mailed on Feb. 17, 2020, 12 pages. |
| Office Action received for Korean Patent Application No. 10-2020-7026035, mailed on Feb. 19, 2021, 13 pages. |
| Office Action received for Korean Patent Application No. 10-2020-7026391, mailed on Jan. 27, 2021, 5 pages. |
| Office Action received for Korean Patent Application No. 10-2020-7026453, mailed on Jan. 27, 2021, 5 pages. |
| Result of Consultation received for European Patent Application No. 19721883.7, mailed on Oct. 7, 2020, 3 pages. |
| Result of Consultation received for European Patent Application No. 19726205.8, mailed on Mar. 15, 2021, 19 pages. |
| Search Report and Opinion received for Danish Patent Application No. PA201870378, mailed on Sep. 10, 2018, 9 pages. |
| Search Report and Opinion received for Danish Patent Application No. PA201870379, mailed on Sep. 14, 2018, 9 pages. |
| Search Report and Opinion received for Danish Patent Application No. PA201870599, mailed on Dec. 21, 2018, 9 pages. |
| Search Report and Opinion received for Danish Patent Application No. PA201870600, mailed on Jan. 31, 2019, 8 pages. |
| Search Report and Opinion received for Danish Patent Application No. PA201870602, mailed on Dec. 19, 2018, 8 pages. |
| Search Report and Opinion received for Danish Patent Application No. PA201970534, mailed on Sep. 23, 2019, 6 pages. |
| Search Report and Opinion received for Danish Patent Application No. PA202070335, mailed on Nov. 27, 2020, 10 pages. |
| Search Report and Opinion received for Danish Patent Application No. PA202070395, mailed on Nov. 24, 2020, 10 pages. |
| Search Report and Opinion received for Danish Patent Application No. PA202070619, mailed on Dec. 2, 2020, 11 pages. |
| Search Report and Opinion received for Danish Patent Application No. PA202070620, mailed on Dec. 11, 2020, 9 pages. |
| Summons to Attend Oral Proceedings received for European Patent Application No. 19726205.8, mailed on Oct. 29, 2020, 13 pages. |
| Summons to Attend Oral Proceedings received for European Patent Application No. 20180581.9, mailed on Aug. 18, 2021, 15 pages. |
| Summons to Attend Oral Proceedings received for European Patent Application No. 20180592.6, mailed on Aug. 11, 2021, 16 pages. |
| Supplemental Notice of Allowance received for U.S. Appl. No. 16/144,849, mailed on Mar. 31, 2020, 2 pages. |
| Supplemental Notice of Allowance received for U.S. Appl. No. 16/880,714, mailed on Sep. 16, 2021, 2 pages. |
| Supplemental Notice of Allowance received for U.S. Appl. No. 17/031,727, mailed on Jan. 15, 2021, 2 pages. |
| Suunto Spartan Trainer Wrist HR 1.12, Online Available at: https://web.archive.org/web/20180127155200/https://ns.suunto.com/Manuals/Spartan_Trainer_WristHR/Userguides/Suunto_Spartan_Trainer_WristHR_UserGuide_EN.pdf, Jan. 17, 2018, 47 pages. |
| Visual Pace Alarm app, Available Online at: https://apps.garmin.com/en-US/apps/3940f3a2-4847-4078-a911-d77422966c82, Oct. 19, 2016, 1 page. |
| Casella Cel Casella, “The Casella dBadge2—World's First Truly Wireless Noise Dosimeter and Airwave App!”, Retrieved from URL: <https://www.youtube.com/watch?v=Xvy2fl3cgYo>, May 27, 2015, 3 pages. |
| Chatrzarrin Hanieh, “Feature Extraction for the Differentiation of Dry and Wet Cough Sounds”, Carleton University, Sep. 2011, 144 pages. |
| CNET, “Google Fit's automatic activity tracking is getting smarter on Android Wear”, Available online at: https://www.youtube.com/watch?v=IttzlCid_d8, May 18, 2016, 1 page. |
| Cook James, “German Period Tracking App Clue Has Over 2.5 Million Active Users—But It's Still Not Sure How It's Going to Make Money”, Available online at: https://www.businessinsider.in/tech/german-period-tracking-app-clue-has-over-2-5-million-active-users-but-its-still-not-sure-how-its-going-to-make-money/articleshow/50511307.cms, Jan. 9, 2016, 9 pages. |
| Dc Rainmaker, “Garmin Fenix3 New Auto Climb Functionality”, Available online at: https://www.youtube.com/watch?v=iuavOSNpVRc, Feb. 19, 2015, 1 page. |
| Epstein et al., “Examining Menstrual Tracking to Inform the Design of Personal Informatics Tools”, Proceedings of the 2017 CHI Conference on Human Factors in Computing Systems, CHI '17, ACM Press, Denver, CO, USA, May 6-11, 2017, pp. 6876-6888. |
| Evergreen et al., “Bar Chart”, Better Evaluation, Available Online at: https://www.betterevaluation.org/en/evaluation-options/BarChart, Oct. 31, 2014, 8 pages. |
| Garmin, “Fenix 5x Owner's Manual”, Online Available at: https://web.archive.org/web/20180127170640/https://static.garmin.com/pumac/fenix5x_OM_EN.pdf, Jan. 27, 2018, 42 pages. |
| Gupta Rajat, “Disable High vol. Warning (no root) in Samsung S7, S8 / Android 7.0”, Online available at :<https://www.youtube.com/watch?v=9fKwRBtk-x8>, Retrieved on Nov. 26, 2020; esp. 2:04, Aug. 6, 2017, 1 page. |
| Haslam Oliver, “Stop Coronavirus in its Tracks by Using This Apple Watch App to Time Hand Washes”, Available Online at: <https://www.imore.com/stop-coronavirus-its-tracks-using-apple-watch-app-time-hand-washes>, Mar. 12, 2020, 12 pages. |
| Liaqat et al., “Challenges with Real-World Smartwatch based Audio Monitoring”, WearSys'18, Munich, Germany, Available Online at: <https://doi.org/10.1145/3211960.3211977>, Jun. 10, 2018, 6 pages. |
| Lovejoy Ben, “Apple Watch blood sugar measurement coming in Series 7, claims report”, Available Online at: https://9to5mac.com/2021/01/25/apple-watch-blood-sugar-measurement/, Jan. 25, 2021, 6 pages. |
| Lyles Taylor, “Wear OS Smartwatches are Now Sending Reminders to Wash Your Hands”, Available Online at: <https://www.theverge.com/2020/4/14/21221294/google-wear-os-smartwatches-reminders-wash-your-hands>, Apr. 14, 2020, 2 pages. |
| Megadepot, “Casella dBadge2 Noise Dosimeter”, Retrieved from URL: <https://www.youtube.com/watch?v=pHiHLiYCD08>, Jun. 12, 2018, 3 pages. |
| Moglia et al., “Evaluation of Smartphone Menstrual Cycle Tracking Applications Using an Adapted Applications Scoring System”, Obstetrics and Gynecology, vol. 127. No. 6, Jun. 2016, pp. 1153-1160. |
| Myflo App, “Functional Medicine Period Tracker and Hormone Balancing App”, Available online at <https://web.archive.org/web/20170127104125/https://myflotracker.com/>, Jan. 2017, 14 pages. |
| Myflo Tutorial, “How to change the start date of your current period”, Available online at <https://www.youtube.com/watch?v=uQQ-odIBJB4>, Jan. 23, 2017, 3 pages. |
| Myflo Tutorial, “Setting and changing the end date of your period”, Available online at <https://www.youtube.com/watch?v=UvAA4OgqL3E>, Jan. 23, 2017, 3 pages. |
| Peters Jay, “Samsung's Smartwatches Get a Hand-Washing Reminder and Timer App”, Available Online at: <https://www.theverge.com/2020/4/17/21225205/samsung-smartwatch-galaxy-active-hand-washing-timer-reminder-app>, Apr. 17, 2020, 2 pages. |
| Rizknows, “TomTom Multisport Cardio Review”, Online available at: https://www.youtube.com/watch?v=WoVCzLrSN9A, Sep. 4, 2015, 1 page. |
| Schoon Ben, “Wear OS Now Sends a Reminder to Wash Your Hands Every Few Hours”, Available Online at: <https://9to5google.com/2020/04/14/wear-os-wash-hands-reminder-coronavirus/>, Apr. 14, 2020, 7 pages. |
| Smith, “Garmin Fenix 5 Activity/Smart Watch Review”, Online Available at: https://www.youtube.com/watch?v=6PkQxXQxpoU, Sep. 2, 2017, 1 page. |
| Sportstechguides, “Garmin Fenix 5: How to Add Power Data Fields”, Online Available at: —https://www.youtube.com/watch?v=ZkPptnnXEiQ, Apr. 29, 2017, 2 pages. |
| Sportstechguides, “Garmin Fenix 5: How To Set Up Run Alerts”, Online Available at: https://www.youtube.com/watch?v=gSMwv8vlhB4, May 13, 2017, 2 pages. |
| Studiosixdigital, “Dosimeter”, Retrieved from URL: <https://studiosixdigital.com/audiotools-modules-2/spl-modules/dosimeter.html>, Mar. 3, 2017, 6 pages. |
| Suunto, “Suunto Spartan-Heart Rate Zones”, Online Available at: https://www.youtube.com/watch?v=aixfoCnS0OU, Mar. 19, 2018, 2 page. |
| Tech, Kalyani, “I See Some problems in Honor Band 5”, Retrieved from: https://www.youtube.com/watch?v=5XPnYJFqajl, May 19, 2020, 1 page. |
| Teunmo, “Data field: Visual Pace Alarm”, Garmin Forum; Available online at: https://forums.garmin.com/forum/developers/connect-iq/connect-iq-showcase/115996-data-field-visual-pace-alarm, Nov. 17, 2015, 10 pages. |
| Ticks, Smartwatch, “Senbono S10 IP67 Waterproof Multi-Function Blood Pressure Sports Smartwatch: One Minute Overview”, Retrieved from: https://www.youtube.com/watch?v=rMxLJvKIVBs, Oct. 30, 2019, 1 page. |
| Tomtom, “TomTom Runner & Multi-Sport Reference Guide”, Online available at: —https://web.archive.org/web/20150908075934/http://download.tomtom.com/open/manuals/Runner_Multi-Sport/refman/TomTom-Runner-Multi-Sport-RG-en-GB.pdf, Sep. 8, 2015, 44 pages. |
| Wesley, “Apple Watch Series 1”, online available at: —http://tool-box.info/blog/archives/1737-unknown.html, May 28, 2015, 5 pages. |
| Youtube, “Apple Watch Series 3”, Online available at: —https://www.youtube.com/watch?v=iBPr9gEfkK8, Nov. 21, 2017, 15 pages. |
| Zlelik, “Garmin Fenix 5 Open Water Swimming Activity Demo”, Online Available at: https://www.youtube.com/watch?v=iSVhdvw2dcs, Jun. 9, 2017, 1 page. |
| Advisory Action received for U.S. Appl. No. 17/031,779, mailed on Oct. 20, 2022, 5 pages. |
| Final Office Action received for U.S. Appl. No. 16/851,451, mailed on Oct. 20, 2022, 31 pages. |
| Office Action received for Australian Patent Application No. 2021261861, mailed on Oct. 14, 2022, 5 pages. |
| Office Action received for Chinese Patent Application No. 202010618240.3, mailed on Sep. 21, 2022, 16 pages (9 pages of English Translation and 7 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 202210004176.9, mailed on Sep. 28, 2022, 12 pages (6 pages of English Translation and 6 pages of Official Copy). |
| Office Action received for Danish Patent Application No. PA202070395, mailed on Oct. 7, 2022, 4 pages. |
| Supplemental Notice of Allowance received for U.S. Appl. No. 17/041,415, mailed on Oct. 13, 2022, 2 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/851,451, mailed on Nov. 29, 2022, 4 pages. |
| Extended European Search Report received for European Patent Application No. 22190169.7, mailed on Nov. 23, 2022, 11 pages. |
| Final Office Action received for U.S. Appl. No. 16/888,780, mailed on Nov. 25, 2022, 10 pages. |
| Intention to Grant received for European Patent Application No. 20182116.2, mailed on Nov. 11, 2022, 9 pages. |
| Invitation to Pay Search Fees received for European Patent Application No. 20746438.9, mailed on Dec. 2, 2022, 4 pages. |
| Invitation to Pay Search Fees received for European Patent Application No. 20760607.0, mailed on Nov. 21, 2022, 3 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/031,723, mailed on Dec. 5, 2022, 27 pages. |
| Office Action received for Australian Patent Application No. 2021266294, mailed on Nov. 11, 2022, 3 pages. |
| Creating Charts in SQL Developer 4.0, Online available at: https://web.archive.org/web/20130905014633/https://www.oracle.com/webfolder/technetwork/tutorials/obe/db/sqldev/r40/Chart/12cChart.html, Sep. 5, 2013, 6 pages. |
| Final Office Action received for U.S. Appl. No. 17/031,723, mailed on Oct. 4, 2023, 13 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/584,190, mailed on Oct. 5, 2023, 17 pages. |
| Office Action received for Australian Patent Application No. 2021261861, mailed on Sep. 22, 2023, 5 pages. |
| Office Action received for Japanese Patent Application No. 2022-131993, mailed on Sep. 15, 2023, 6 pages (3 pages of English Translation and 3 pages of Official Copy). |
| Select (SQL)—Wikipedia, online available at: https://en.wikipedia.org/w/index.php?title=Select_(SQL)&direction=prev&oldid=489205430, Mar. 9, 2012, 5 pages. |
| Gertz Michael, “Oracle/SQL Tutorial”, Online available at: http://www.db.cs.ucdavis.edu/teaching/sqltutorial/tutorial.pdf, Jan. 1, 2000, 5 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/851,451, mailed on Feb. 20, 2024, 3 pages. |
| Non-Final Office Action received for U.S. Appl. No. 18/195,331, mailed on Feb. 8, 2024, 13 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/135,710, mailed on Feb. 14, 2024, 4 pages. |
| Office Action received for Indian Patent Application No. 202315061713, mailed on Feb. 14, 2024, 8 pages. |
| Office Action received for Indian Patent Application No. 202315061718, mailed on Feb. 14, 2024, 8 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/135,710, mailed on Jan. 23, 2024, 7 pages. |
| Office Action received for Australian Patent Application No. 2021283914, mailed on Dec. 13, 2023, 5 pages. |
| Final Office Action received for U.S. Appl. No. 17/584,190, mailed on Mar. 13, 2024, 20 pages. |
| Intention to Grant received for European Patent Application No. 20746438.9, mailed on Mar. 21, 2024, 15 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2023/031421, mailed on Feb. 9, 2024, 22 pages. |
| Invitation to Pay Additional Fees and Partial International Search Report received for PCT Patent Application No. PCT/US2023/031421, mailed on Dec. 1, 2023, 10 pages. |
| Office Action received for Australian Patent Application No. 2021283914, mailed on Mar. 14, 2024, 5 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 17/952,053, mailed on Jan. 25, 2024, 6 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/851,451, mailed on Jan. 31, 2024, 13 pages. |
| Office Action received for Korean Patent Application No. 10-2023-7018399, mailed on Jan. 24, 2024, 11 pages (4 pages of English Translation and 7 pages of Official Copy). |
| Final Office Action received for U.S. Appl. No. 17/952,182, mailed on Jun. 6, 2024, 12 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/584,190, mailed on Jun. 20, 2024, 9 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/337,147, mailed on Apr. 26, 2024, 20 pages. |
| Office Action received for Chinese Patent Application No. 202210346306.7, mailed on Apr. 10, 2024, 18 pages (10 pages of English Translation and 8 pages of Official Copy). |
| Office Action received for European Patent Application No. 21787524.4, mailed on Apr. 12, 2024, 10 pages. |
| Extended European Search Report received for European Patent Application No. 23200361.6, mailed on Mar. 28, 2024, 10 pages. |
| Notice of Allowance received for U.S. Appl. No. 18/195,331, mailed on Apr. 2, 2024, 8 pages. |
| Office Action received for Japanese Patent Application No. 2023-028769, mailed on Apr. 1, 2024, 8 pages (4 pages of English Translation and 4 pages of Official Copy). |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/584,190, mailed on May 29, 2024, 5 pages. |
| Office Action received for Korean Patent Application No. 10-2021-7020689, mailed on May 14, 2024, 13 pages (6 pages of English Translation and 7 pages of Official Copy). |
| Final Office Action received for U.S. Appl. No. 16/888,780, mailed on Feb. 29, 2024, 12 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2022-573764, mailed on Feb. 26, 2024, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 202180053264.1, mailed on Jan. 18, 2024, 14 pages (8 pages of English Translation and 6 pages of Official Copy). |
| Decision to Grant received for European Patent Application No. 20746438.9, mailed on Aug. 22, 2024, 4 pages. |
| Notice of Allowance received for Korean Patent Application No. 10-2022-7012608, mailed on Aug. 22, 2024, 9 pages (2 pages of English Translation and 7 pages of Official Copy). |
| 10-2009-0010287, Korean Patent Office in an Office Action released Patent Application No. 10-2022-7012608 on Aug. 22, 2024. |
| 10-2018-0018761, Korean Patent Office in an Office Action released Patent Application No. 10-2022-7012608 on Aug. 22, 2024. |
| Number | Date | Country | |
|---|---|---|---|
| 20220109932 A1 | Apr 2022 | US |
| Number | Date | Country | |
|---|---|---|---|
| 63023023 | May 2020 | US | |
| 62856016 | Jun 2019 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 16880552 | May 2020 | US |
| Child | 17554678 | US |
