The present disclosure relates generally to computer user interfaces, and more specifically to techniques for managing health monitoring.
Monitoring health, such as heart health using heart rhythm and heart rate information, using electronic devices is a convenient and effective method of providing and maintaining awareness of one's health. Using electronic devices enable a user to quickly and easily capture biometric information used to monitor the user's health.
Some techniques for managing health monitoring 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 health monitoring. Such methods and interfaces optionally complement or replace other methods for managing health monitoring. 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. Such methods and interfaces enable a user to quickly and easily capture health information (thereby also incentivizing the user to frequently monitor his or her health) and to conveniently view and manage recorded health information (thereby raising awareness of the user's current health status to the user).
In accordance with some embodiments, a method performed at a first electronic device with a display and one or more input devices, wherein the first electronic device is paired with a second electronic device, is described. The method comprises: displaying, on the display, a first portion of a tutorial for using a function of the second electronic device; detecting, via the one or more input devices, a request to proceed with the tutorial; in response to detecting the request to proceed with the tutorial, displaying, on the display, instructions to perform an operation on the second electronic device that involves the function of the second electronic device; receiving, from the second electronic device, an indication that the instructions have been carried out; and in response to receiving the indication that the instructions have been carried out, displaying, on the display, a second portion of the tutorial that is different from the first portion.
In accordance with some embodiments, a non-transitory computer-readable storage medium is described. The non-transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of a first electronic device with a display and one or more input devices, wherein the first electronic device is paired with a second electronic device, the one or more programs including instructions for: displaying, on the display, a first portion of a tutorial for using a function of the second electronic device; detecting, via the one or more input devices, a request to proceed with the tutorial; in response to detecting the request to proceed with the tutorial, displaying, on the display, instructions to perform an operation on the second electronic device that involves the function of the second electronic device; receiving, from the second electronic device, an indication that the instructions have been carried out; and in response to receiving the indication that the instructions have been carried out, displaying, on the display, a second portion of the tutorial that is different from the first portion.
In accordance with some embodiments, a transitory computer-readable storage medium is described. The transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of a first electronic device with a display and one or more input devices, wherein the first electronic device is paired with a second electronic device, the one or more programs including instructions for: displaying, on the display, a first portion of a tutorial for using a function of the second electronic device; detecting, via the one or more input devices, a request to proceed with the tutorial; in response to detecting the request to proceed with the tutorial, displaying, on the display, instructions to perform an operation on the second electronic device that involves the function of the second electronic device; receiving, from the second electronic device, an indication that the instructions have been carried out; and in response to receiving the indication that the instructions have been carried out, displaying, on the display, a second portion of the tutorial that is different from the first portion.
In accordance with some embodiments, a first electronic device is described. The first electronic device, wherein the first electronic device is paired with a second electronic device, comprises: a display, one or more input devices; 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, on the display, a first portion of a tutorial for using a function of the second electronic device; detecting, via the one or more input devices, a request to proceed with the tutorial; in response to detecting the request to proceed with the tutorial, displaying, on the display, instructions to perform an operation on the second electronic device that involves the function of the second electronic device; receiving, from the second electronic device, an indication that the instructions have been carried out; and in response to receiving the indication that the instructions have been carried out, displaying, on the display, a second portion of the tutorial that is different from the first portion.
In accordance with some embodiments, a first electronic device is described. The first electronic device, wherein the first electronic device is paired with a second electronic device, comprises: a display, one or more input devices; means for displaying, on the display, a first portion of a tutorial for using a function of the second electronic device; means for detecting, via the one or more input devices, a request to proceed with the tutorial; means, in response to detecting the request to proceed with the tutorial, for displaying, on the display, instructions to perform an operation on the second electronic device that involves the function of the second electronic device; means for receiving, from the second electronic device, an indication that the instructions have been carried out; and means, in response to receiving the indication that the instructions have been carried out, for displaying, on the display, a second portion of the tutorial that is different from the first portion.
In accordance with some embodiments, a method performed at a first electronic device with a display and one or more input devices including a biometric sensor is described. The method comprises: displaying, on the display, a first user interface indicating that the first electronic device is ready to detect biometric information; detecting a first input with the biometric sensor that satisfies first criteria; in response to detecting the first input with the biometric sensor: starting to record biometric information detected by the biometric sensor; and displaying, on the display, a second user interface that is different from the first user interface, wherein the second user interface includes an indication of progress in recording the biometric information; after recording at least a portion of the biometric information, detecting, via the one or more input devices, that the first criteria are no longer met; in response to detecting that the first criteria are no longer met for a first period of time, resetting the indication of progress in recording the biometric information and maintaining display of the second user interface; and in response to detecting that the first criteria are no longer met for a second period of time that is longer than the first period of time, replacing display of the second user interface with the first user interface.
In accordance with some embodiments, a non-transitory computer-readable storage medium is described. The non-transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of a first electronic device with a display and one or more input devices including a biometric sensor, the one or more programs including instructions for: displaying, on the display, a first user interface indicating that the first electronic device is ready to detect biometric information; detecting a first input with the biometric sensor that satisfies first criteria; in response to detecting the first input with the biometric sensor: starting to record biometric information detected by the biometric sensor; and displaying, on the display, a second user interface that is different from the first user interface, wherein the second user interface includes an indication of progress in recording the biometric information; after recording at least a portion of the biometric information, detecting, via the one or more input devices, that the first criteria are no longer met; in response to detecting that the first criteria are no longer met for a first period of time, resetting the indication of progress in recording the biometric information and maintaining display of the second user interface; and in response to detecting that the first criteria are no longer met for a second period of time that is longer than the first period of time, replacing display of the second user interface with the first user interface.
In accordance with some embodiments, a transitory computer-readable storage medium is described. The transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of a first electronic device with a display and one or more input devices including a biometric sensor, the one or more programs including instructions for: displaying, on the display, a first user interface indicating that the first electronic device is ready to detect biometric information; detecting a first input with the biometric sensor that satisfies first criteria; in response to detecting the first input with the biometric sensor: starting to record biometric information detected by the biometric sensor; and displaying, on the display, a second user interface that is different from the first user interface, wherein the second user interface includes an indication of progress in recording the biometric information; after recording at least a portion of the biometric information, detecting, via the one or more input devices, that the first criteria are no longer met; in response to detecting that the first criteria are no longer met for a first period of time, resetting the indication of progress in recording the biometric information and maintaining display of the second user interface; and in response to detecting that the first criteria are no longer met for a second period of time that is longer than the first period of time, replacing display of the second user interface with the first user interface.
In accordance with some embodiments, a first electronic device is described. The first electronic device comprises: a display; one or more input devices including a biometric sensor; 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, on the display, a first user interface indicating that the first electronic device is ready to detect biometric information; detecting a first input with the biometric sensor that satisfies first criteria; in response to detecting the first input with the biometric sensor: starting to record biometric information detected by the biometric sensor; and displaying, on the display, a second user interface that is different from the first user interface, wherein the second user interface includes an indication of progress in recording the biometric information; after recording at least a portion of the biometric information, detecting, via the one or more input devices, that the first criteria are no longer met; in response to detecting that the first criteria are no longer met for a first period of time, resetting the indication of progress in recording the biometric information and maintaining display of the second user interface; and in response to detecting that the first criteria are no longer met for a second period of time that is longer than the first period of time, replacing display of the second user interface with the first user interface.
In accordance with some embodiments, a first electronic device is described. The first electronic device comprises: a display; one or more input devices including a biometric sensor; means for displaying, on the display, a first user interface indicating that the first electronic device is ready to detect biometric information; means for detecting a first input with the biometric sensor that satisfies first criteria; means, in response to detecting the first input with the biometric sensor, for: starting to record biometric information detected by the biometric sensor; and displaying, on the display, a second user interface that is different from the first user interface, wherein the second user interface includes an indication of progress in recording the biometric information; means, after recording at least a portion of the biometric information, for detecting, via the one or more input devices, that the first criteria are no longer met; means, in response to detecting that the first criteria are no longer met for a first period of time, for resetting the indication of progress in recording the biometric information and maintaining display of the second user interface; and means, in response to detecting that the first criteria are no longer met for a second period of time that is longer than the first period of time, for replacing display of the second user interface with the first user interface.
In accordance with some embodiments, a method performed at a first electronic device with a display and one or more input devices including a first input device with an integrated biometric sensor is described. The method comprises: displaying, on the display, a user interface of an application for capturing biometric information from the biometric sensor; while displaying the user interface of the application for capturing biometric information from the biometric sensor, detecting a first activation of the first input device; in response to detecting the first activation of the first input device and while capturing biometric information from the biometric sensor: in accordance with a determination that the first activation of the first input device was detected when first criteria are met, wherein the first criteria are based on progress toward capturing biometric information with the biometric sensor, performing a predefined operation associated with the first input device that interrupts capture of the biometric information; and in accordance with a determination that the first activation of the first input device was detected when the first criteria are not met, continuing to capture the biometric information without performing the predefined operation associated with the first input device.
In accordance with some embodiments, a non-transitory computer-readable storage medium is described. The non-transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of a first electronic device with a display and one or more input devices including a first input device with an integrated biometric sensor, the one or more programs including instructions for: displaying, on the display, a user interface of an application for capturing biometric information from the biometric sensor; while displaying the user interface of the application for capturing biometric information from the biometric sensor, detecting a first activation of the first input device; in response to detecting the first activation of the first input device and while capturing biometric information from the biometric sensor: in accordance with a determination that the first activation of the first input device was detected when first criteria are met, wherein the first criteria are based on progress toward capturing biometric information with the biometric sensor, performing a predefined operation associated with the first input device that interrupts capture of the biometric information; and in accordance with a determination that the first activation of the first input device was detected when the first criteria are not met, continuing to capture the biometric information without performing the predefined operation associated with the first input device.
In accordance with some embodiments, a transitory computer-readable storage medium is described. The transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of a first electronic device with a display and one or more input devices including a first input device with an integrated biometric sensor, the one or more programs including instructions for: displaying, on the display, a user interface of an application for capturing biometric information from the biometric sensor; while displaying the user interface of the application for capturing biometric information from the biometric sensor, detecting a first activation of the first input device; in response to detecting the first activation of the first input device and while capturing biometric information from the biometric sensor: in accordance with a determination that the first activation of the first input device was detected when first criteria are met, wherein the first criteria are based on progress toward capturing biometric information with the biometric sensor, performing a predefined operation associated with the first input device that interrupts capture of the biometric information; and in accordance with a determination that the first activation of the first input device was detected when the first criteria are not met, continuing to capture the biometric information without performing the predefined operation associated with the first input device.
In accordance with some embodiments, a first electronic device is described. The first electronic device comprises: a display; one or more input devices including a first input device with an integrated biometric sensor; 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, on the display, a user interface of an application for capturing biometric information from the biometric sensor; while displaying the user interface of the application for capturing biometric information from the biometric sensor, detecting a first activation of the first input device; in response to detecting the first activation of the first input device and while capturing biometric information from the biometric sensor: in accordance with a determination that the first activation of the first input device was detected when first criteria are met, wherein the first criteria are based on progress toward capturing biometric information with the biometric sensor, performing a predefined operation associated with the first input device that interrupts capture of the biometric information; and in accordance with a determination that the first activation of the first input device was detected when the first criteria are not met, continuing to capture the biometric information without performing the predefined operation associated with the first input device.
In accordance with some embodiments, a first electronic device is described. The first electronic device comprises: a display; one or more input devices including a first input device with an integrated biometric sensor; means for displaying, on the display, a user interface of an application for capturing biometric information from the biometric sensor; means, while displaying the user interface of the application for capturing biometric information from the biometric sensor, for detecting a first activation of the first input device; means, in response to detecting the first activation of the first input device and while capturing biometric information from the biometric sensor, for: in accordance with a determination that the first activation of the first input device was detected when first criteria are met, wherein the first criteria are based on progress toward capturing biometric information with the biometric sensor, performing a predefined operation associated with the first input device that interrupts capture of the biometric information; and in accordance with a determination that the first activation of the first input device was detected when the first criteria are not met, continuing to capture the biometric information without performing the predefined operation associated with the first input device.
In accordance with some embodiments, a method performed at a first electronic device with a display and one or more input devices is described. The method comprises: capturing biometric information with a biometric sensor that is in communication with the first electronic device; displaying, on the display, a representation of an evaluation of a medical characteristic determined based on the biometric information captured by the biometric sensor; while displaying the representation of the evaluation of the medical characteristic, detecting, via the one or more input devices, a sequence of one or more inputs to add user-specified symptoms to the evaluation of the medical characteristic; in response to detecting the sequence of one or more inputs: in accordance with a determination that at least one of the user-specified symptoms meet respective criteria, displaying, on the display, a first user interface that includes an affordance that, when activated, initiates a process for seeking immediate medical attention; and in accordance with a determination that the user-specified symptoms do not meet the respective criteria, displaying, on the display, the representation of the evaluation of the medical characteristic and one or more representations of user-specified symptoms without displaying the first user interface.
In accordance with some embodiments, a non-transitory computer-readable storage medium is described. The non-transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of a first electronic device with a display and one or more input devices, the one or more programs including instructions for: capturing biometric information with a biometric sensor that is in communication with the first electronic device; displaying, on the display, a representation of an evaluation of a medical characteristic determined based on the biometric information captured by the biometric sensor; while displaying the representation of the evaluation of the medical characteristic, detecting, via the one or more input devices, a sequence of one or more inputs to add user-specified symptoms to the evaluation of the medical characteristic; in response to detecting the sequence of one or more inputs: in accordance with a determination that at least one of the user-specified symptoms meet respective criteria, displaying, on the display, a first user interface that includes an affordance that, when activated, initiates a process for seeking immediate medical attention; and in accordance with a determination that the user-specified symptoms do not meet the respective criteria, displaying, on the display, the representation of the evaluation of the medical characteristic and one or more representations of user-specified symptoms without displaying the first user interface.
In accordance with some embodiments, a transitory computer-readable storage medium is described. The transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of a first electronic device with a display and one or more input devices, the one or more programs including instructions for: capturing biometric information with a biometric sensor that is in communication with the first electronic device; displaying, on the display, a representation of an evaluation of a medical characteristic determined based on the biometric information captured by the biometric sensor; while displaying the representation of the evaluation of the medical characteristic, detecting, via the one or more input devices, a sequence of one or more inputs to add user-specified symptoms to the evaluation of the medical characteristic; in response to detecting the sequence of one or more inputs: in accordance with a determination that at least one of the user-specified symptoms meet respective criteria, displaying, on the display, a first user interface that includes an affordance that, when activated, initiates a process for seeking immediate medical attention; and in accordance with a determination that the user-specified symptoms do not meet the respective criteria, displaying, on the display, the representation of the evaluation of the medical characteristic and one or more representations of user-specified symptoms without displaying the first user interface.
In accordance with some embodiments, a first electronic device is described. The first electronic device comprises: a display; one or more input devices; 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: capturing biometric information with a biometric sensor that is in communication with the first electronic device; displaying, on the display, a representation of an evaluation of a medical characteristic determined based on the biometric information captured by the biometric sensor; while displaying the representation of the evaluation of the medical characteristic, detecting, via the one or more input devices, a sequence of one or more inputs to add user-specified symptoms to the evaluation of the medical characteristic; in response to detecting the sequence of one or more inputs: in accordance with a determination that at least one of the user-specified symptoms meet respective criteria, displaying, on the display, a first user interface that includes an affordance that, when activated, initiates a process for seeking immediate medical attention; and in accordance with a determination that the user-specified symptoms do not meet the respective criteria, displaying, on the display, the representation of the evaluation of the medical characteristic and one or more representations of user-specified symptoms without displaying the first user interface.
In accordance with some embodiments, a first electronic device is described. The first electronic device comprises: a display; one or more input devices; means for capturing biometric information with a biometric sensor that is in communication with the first electronic device; means for displaying, on the display, a representation of an evaluation of a medical characteristic determined based on the biometric information captured by the biometric sensor; means, while displaying the representation of the evaluation of the medical characteristic, for detecting, via the one or more input devices, a sequence of one or more inputs to add user-specified symptoms to the evaluation of the medical characteristic; means, in response to detecting the sequence of one or more inputs, for: in accordance with a determination that at least one of the user-specified symptoms meet respective criteria, displaying, on the display, a first user interface that includes an affordance that, when activated, initiates a process for seeking immediate medical attention; and in accordance with a determination that the user-specified symptoms do not meet the respective criteria, displaying, on the display, the representation of the evaluation of the medical characteristic and one or more representations of user-specified symptoms without displaying the first user interface.
In accordance with some embodiments, a method performed at an electronic device with a display and one or more input devices, the electronic device operably connected to a plurality of biometric sensors, is described. The method comprises: receiving first biometric information from a first biometric sensor of the plurality of biometric sensors; in response to receiving the first biometric information and in accordance with a determination that the first biometric information satisfies first criteria, displaying, on the display, an alert including a first affordance for detecting additional biometric information; receiving, via the one or more input devices, user activation of the first affordance; and subsequent to receiving the user activation of the first affordance, receiving second biometric information associated with the first biometric information from a second biometric sensor of the plurality of biometric sensors that is different from the first biometric sensor.
In accordance with some embodiments, a non-transitory computer-readable storage medium is described. The 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 and one or more input devices, the electronic device operably connected to a plurality of biometric sensors, the one or more programs including instructions for: receiving first biometric information from a first biometric sensor of the plurality of biometric sensors; in response to receiving the first biometric information and in accordance with a determination that the first biometric information satisfies first criteria, displaying, on the display, an alert including a first affordance for detecting additional biometric information; receiving, via the one or more input devices, user activation of the first affordance; and subsequent to receiving the user activation of the first affordance, receiving second biometric information associated with the first biometric information from a second biometric sensor of the plurality of biometric sensors that is different from the first biometric sensor.
In accordance with some embodiments, a transitory computer-readable storage medium is described. The 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 and one or more input devices, the electronic device operably connected to a plurality of biometric sensors, the one or more programs including instructions for: receiving first biometric information from a first biometric sensor of the plurality of biometric sensors; in response to receiving the first biometric information and in accordance with a determination that the first biometric information satisfies first criteria, displaying, on the display, an alert including a first affordance for detecting additional biometric information; receiving, via the one or more input devices, user activation of the first affordance; and subsequent to receiving the user activation of the first affordance, receiving second biometric information associated with the first biometric information from a second biometric sensor of the plurality of biometric sensors that is different from the first biometric sensor.
In accordance with some embodiments, an electronic device is described. The electronic device comprises: a display; one or more input devices; is operably connected to a plurality of biometric sensors; 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 biometric information from a first biometric sensor of the plurality of biometric sensors; in response to receiving the first biometric information and in accordance with a determination that the first biometric information satisfies first criteria, displaying, on the display, an alert including a first affordance for detecting additional biometric information; receiving, via the one or more input devices, user activation of the first affordance; and subsequent to receiving the user activation of the first affordance, receiving second biometric information associated with the first biometric information from a second biometric sensor of the plurality of biometric sensors that is different from the first biometric sensor.
In accordance with some embodiments, an electronic device is described. The electronic device comprises: a display; one or more input devices; is operably connected to a plurality of biometric sensors; means for receiving first biometric information from a first biometric sensor of the plurality of biometric sensors; means, in response to receiving the first biometric information and in accordance with a determination that the first biometric information satisfies first criteria, for displaying, on the display, an alert including a first affordance for detecting additional biometric information; means for receiving, via the one or more input devices, user activation of the first affordance; and means, subsequent to receiving the user activation of the first affordance, for receiving second biometric information associated with the first biometric information from a second biometric sensor of the plurality of biometric sensors that is different from the first biometric sensor.
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 health monitoring, thereby increasing the effectiveness, efficiency, and user satisfaction with such devices. Such methods and interfaces may complement or replace other methods for managing health monitoring.
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.
There is a need for electronic devices that provide efficient methods and interfaces for managing health monitoring. For example, there is a need for electronic devices that quickly and conveniently capture biometric information from a user to enable the user to easily monitor his or her health. For another example, there is a need for electronic devices that manage captured biometric information from the user such that the user can easily and conveniently access and view monitoring and evaluation results. For another example, there is a need for electronic devices that efficiently present evaluation results to the user to enable the user to easily understand and properly respond to the results. Such techniques can reduce the cognitive burden on a user who accesses health monitoring features, thereby enhancing productivity. Further, such techniques can reduce processor and battery power otherwise wasted on redundant user inputs.
Below,
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 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, 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, etc.), dials, slider switches, joysticks, click wheels, and so forth. In some alternate 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 (not shown) 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 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 (e.g., heart rate or heart rhythm 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 (not shown) 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 (
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 one or more electronic device(s), such as portable multifunction device 100, device 300, or device 500.
In
In some embodiments, first electronic device 600A detects (e.g., via a touch input) a user activation 601 of icon 610A corresponding to a health application, which includes features concerning management of recordings of biometric information, including ECG information. In response to detecting user activation 601, first electronic device 600A launches the health application (e.g., by replacing display of homescreen user interface 610 with a user interface of the health application).
In some embodiments, the health application includes an ECG affordance for viewing and managing existing ECG recordings on the device, where the ECG information is recorded using a related ECG application on a second electronic device (e.g., second electronic device 600B described with reference to
In some embodiments, homescreen user interface 610 includes a paired device application corresponding to icon 610B and associated with a device paired with first electronic device 600A (e.g., second electronic device 600B). In some embodiments, while displaying homescreen user interface 610, first electronic device 600A detects (e.g., via a tap input) a user activation 641 of icon 610B, as shown in
In some embodiments, in response to detecting user activation 641, first electronic device 600A displays, on display 602, a main user interface 643 of the paired device application, as shown in
In some embodiments, in response to detecting user activation 647 of heart application setting affordance 645G, first electronic device 600A displays, on display 602, an application settings page 649 for changing and/or configuring application settings of the corresponding heart application (e.g., the ECG application) on second electronic device 600B, as shown in
In some embodiments, notification 612 indicates that initial setup (e.g., onboarding) of the ECG management features of the health application need to be performed in order to utilize ECG features of the application. In some embodiments, while displaying notification 612, first electronic device 600A detects (e.g., via a touch input) a user selection 603 of notification 612. In response to detecting user selection 603, first electronic device 600A launches a first page of a tutorial for performing initial setup of the ECG management features and associated ECG application.
In some embodiments, first page 614 of the tutorial includes a date of birth entry field 614C for receiving a user input corresponding to the user's date of birth, where the user's date of birth is used to determine whether the user meets a minimum age requirement (e.g., 22 years of age) to use the features of the ECG application. In some embodiments, date of birth entry field 614C includes scrollable month, day, and year fields. In some embodiments, first page 614 of the tutorial does not include date of birth entry field 614C. In some embodiments, first page 614 of the tutorial includes (e.g., in addition to or alternatively to date of birth entry field 614C) an age restriction message (e.g., stating “You must be 22 years or older”) indicating to the user that the user must meet the minimum age requirement.
In some embodiments, first page 614 of the tutorial includes an affordance 614D for proceeding with the tutorial. In
In some embodiments, in response to detecting user activation 605 (and in accordance with a determination that the minimum age requirement is met), first electronic device 600A displays, on display 602 (e.g., replaces display of first page 614 with), a second page 616 of the tutorial, as shown in
In
In some embodiments, the plurality of representations of possible evaluation results shown in possible results page 618 of the tutorial include possible evaluation results corresponding to heart rhythm and heart rate that are captured from an ECG recording. In some embodiments, a first possible evaluation result is a “regular rhythm” result (or a “normal result”), which corresponds to a result where no abnormal signs were determined from the ECG recording of the user. In some embodiments, a second possible evaluation result is an “abnormal heart rhythm” result (e.g., an “Atrial Fibrillation” result) that corresponds to a result where abnormal heart rhythm signs (and, in some cases, high/low heart rate signs) were determined from the ECG recording of the user. In some embodiments, a third possible evaluation result is an “abnormal heart rate” result (e.g., a “high or low heart rate” result), which corresponds to a result where an unusually (or abnormally) high or low heart rate was determined from the ECG recording of the user (e.g., above 150 BPM or below 50 BPM). In some embodiments, a fourth possible evaluation result is an “inconclusive” result, which corresponds to a result where no evaluation result could be determined from the ECG recording of the user (e.g., because of a poor reading).
In some embodiments, as shown in
In some embodiments, as shown in
In
In some embodiments, a representation of a possible evaluation result also includes an expand affordance (e.g., a “show more” affordance) for displaying the full text description of the respective evaluation result (e.g., by expanding the text region). In
In
In
In
In
In
In some embodiments, as mentioned, the animations (of animations regions 620A-626A) of the plurality of representations 620-626 of possible evaluation results on possible results page 618 comprise a beating heart animation and a tachogram-like animation that in combination illustrate a rhythm and rate of heartbeats. In some embodiments, the animations are synchronized. In some examples, each animation comprises repeating loops, where each loop consists of an object (e.g., a circular object) leaving the beating heart animation and moving across the screen while tracking the tachogram-like animation. The repeating loops of the plurality of animations (of representations 620-626) are synchronized to begin and end at the on synched time intervals.
In
In some embodiments, limitations page 630 indicates to the user (e.g., via a text description) some limitations of evaluation results determined from ECG recordings taken on the second electronic device (e.g., second electronic device 600B). In some examples, limitations page 630 includes a list 630A of one or more medical characteristics that cannot be determined from recorded ECG information (e.g., heart attack, blood clots/stroke). In some embodiments, limitations page 630 includes (e.g., at the bottom of the page), an affordance 630B for proceeding with the tutorial.
In
In some embodiments, one or more of pages 614, 616, 618, and/or 632 of the tutorial (as shown in
In some embodiments, instructions page 632 includes a postpone affordance 632C (e.g., showing “Take a recording later”) that enables a user to postpone taking the first ECG recording to a later time (and thus allows the user to complete the initial setup process without performing a first ECG recording). In some embodiments, while displaying instructions page 632, first electronic device 600A detects (e.g., via a touch input) a user activation 631 of postpone affordance 632C.
In some embodiments, in response to detecting user activation 631 of postpone affordance 632C, first electronic device 600A displays, on display 602, a confirmation notification 633, as shown in
In
In
In some embodiments, user interface 644 of the ECG application includes an animation 646 (e.g., a fluid animation) that depicts a particular shape (e.g., a heart). In some examples, as shown in
In some embodiments, after a predetermined amount of time (e.g., 5 seconds) has passed from the launch and display of the ECG application on second electronic device 600B (but the device has not detected any additional inputs from the user), second electronic device 600B displays, on user interface 644 (and while maintaining display of animation 646), a notification message 648 indicating to the user that an action must be performed (by the user) to proceed with recording ECG information using the device (e.g., “Hold your finger on the crown”), as shown in
In some embodiments, (immediately) after completing the ECG recording, first electronic device 600A displays a summary page 695 of the tutorial, where summary page 695 includes a representation 693 of the completed recording. In some embodiments, representation 693 includes the evaluation result (e.g., “Regular Rhythm”), the heart rate reading (e.g., in BPM), and a graphical depiction (e.g., a tachogram) of the recording. In some embodiments, summary page 695 of the tutorial includes an affordance 693 for leaving the summary page. In some embodiments, summary page 695 of first electronic device 600A includes a completion button 691 for exiting the tutorial (after having completed the tutorial). In some embodiments, when the tutorial is completed without the user having taken a first ECG recording, as described with reference to
In some embodiments, (immediately) after completing the ECG recording, second electronic device 600B displays at least a portion of a corresponding summary page 689 (e.g., over user interface 644 of the ECG application with animation 646 in its initial pattern (e.g., a fluid heart-shaped pattern, as shown in
In some embodiments, the user can perform a plurality of ECG recordings using the ECG application on second electronic device 600B. In some embodiments, the plurality of ECG recordings are transmitted from second electronic device 600B to first electronic device 600A (or to an external server accessible by first electronic device 600A) for viewing and management via the ECG management features of the health application on first electronic device 600A.
In some embodiments, health data user interface 650 of the health application includes an affordance 650A (e.g., stating “Heart”) for viewing and managing heart health information. In
In some embodiments, heart data user interface 652 of the health application on first electronic device 600A includes a heart rate affordance 654. In some embodiments, heart rate affordance 654 includes an indication of a range of the user's heart rate measured (e.g., via second electronic device 600B) during a certain period of time (e.g., today). In some embodiments, in response to detecting a user selection on heart rate affordance 654, heart data user interface 652 displays a graphical depiction of the heart rate information summarized by heart rate affordance 654 within a graphical depiction region 656 of the user interface (and further highlights the affordance with a particular visual characteristic, such as a different color, to indicate to the user that the heart rate affordance is currently selected by the user).
In some embodiments, heart data user interface 652 of the health application on first electronic device 600A includes an ECG affordance 658. In some embodiments, ECG affordance 658 includes a summary of a heart health evaluation result (e.g., a “regular” result, a “Atrial Fibrillation” result, a “high or low heart rate” result, an “inconclusive” result) determined from one or more ECG recordings performed during a certain time period (e.g., today), and a number of recordings taken during the time period (e.g., “2 readings”). In some embodiments, ECG affordance 658 includes an information affordance 658A for viewing and managing information about existing ECG recordings (e.g., previously performed by the user on second electronic device 600B).
In
In some embodiments, ECG management user interface 660 (initially) displays a predetermined number (e.g., three) of representations of the most-recent evaluation result determined from corresponding most-recent ECG recordings performed on second electronic device 600B. In some embodiments, the representations of the most-recent evaluation results include a graphical portion (e.g., a tachogram) that graphically depicts the recording and a text portion that indicates the type of evaluation result (e.g., a “regular” result, an “Atrial Fibrillation” result, a “high or low heart rate” result, an “inconclusive” result) and a measured heart rate (e.g., in BPM). In some embodiments, the representations of the most-recent evaluation results include an indication of one or more user-specified symptoms associated with the result and/or the number of user-specified symptoms associated with the result. In some embodiments, if the user specified that there are no symptoms to be associated with a result, then a “no symptoms” indication is showed in the corresponding representation of the result. In some embodiments, if the user did not specify any symptoms for a result (or indicate that there are no symptoms for the result), then a symptoms indication is not shown in the corresponding representation of the result. Features related to user selection of symptoms for a respective evaluation result is described in greater detail with reference to
In some embodiments, first electronic device 600A detects a user activation of ECG affordance 658 at a location on the affordance that does not correspond to information affordance 658A. In some embodiments, in response to the user activation, first electronic device 600A replaces display of the heart rate information shown in graphical depiction region 656 of
In
In some embodiments, ECG management user interface 660 also includes a plurality of affordances for viewing additional/different representations of additional/different past evaluation results and sorting/filtering the existing evaluation results. In some examples, ECG management user interface 660 includes a “show all results” affordance 664A (e.g., which also indicates the number of associated existing recordings) for displaying representations of all past ECG recordings performed by the user. In some examples, ECG management user interface 660 includes a first filter affordance 664B for displaying (e.g., filtering the existing recordings to show) representations of all of the existing ECG recordings corresponding to a “regular” result (e.g., representation 662A). In some examples, ECG management user interface 660 includes a second filter affordance 664C for displaying (e.g., filtering the existing recordings to show) representations of all of the existing ECG recordings corresponding to a “Atrial Fibrillation” result (e.g., representation 662C). In some examples, ECG management user interface 660 includes a second filter affordance 664C for displaying (e.g., filtering the existing recordings to show) representations of all of the existing ECG recordings corresponding to a “Atrial Fibrillation” result (e.g., representation 662C). In some examples, ECG management user interface 660 includes a third filter affordance 664D for displaying (e.g., filtering the existing recordings to show) representations of all of the existing ECG recordings corresponding to both a “Atrial Fibrillation” result and a “high heart rate” (e.g., a heart rate over 150 BPM) result. In some examples, ECG management user interface 660 includes a fourth filter affordance 664E for displaying (e.g., filtering the existing recordings to show) representations of all of the existing ECG recordings corresponding to both a “high heart rate” (e.g., a heart rate over 150 BPM) result and a “low heart rate” (e.g., a heart rate below 50 BPM) result. In some examples, ECG management user interface 660 includes a fifth filter affordance 664F for displaying (e.g., filtering the existing recordings to show) representations of all of the existing ECG recordings corresponding to a “high heart rate” (e.g., a heart rate over 150 BPM) result. In some examples, ECG management user interface 660 includes a sixth filter affordance 664G for displaying (e.g., filtering the existing recordings to show) representations of all of the existing ECG recordings corresponding to a “low heart rate” (e.g., a heart rate below 50 BPM) result. In some examples, ECG management user interface 660 includes a seventh filter affordance 664H for displaying (e.g., filtering the existing recordings to show) representations of all of the existing ECG recordings corresponding to an “inconclusive” result (e.g., because the measured heart rate was too high or too low to determine an evaluation result, because the captured ECG information was incomplete and/or unreadable to determine an evaluation result).
In
In some embodiments, a details page includes one or more descriptive items (e.g., a tachogram, a type of evaluation result, a measured BPM of the result, a presence of lack of presence of Atrial Fibrillation, one or more selected symptoms) associated with the selected evaluation result. Details page 666 corresponds to the evaluation result of representation 662A (from
In some embodiments, a details page (e.g., details page 666) includes an information affordance 670 which causes display of a text description explaining general medical characteristics of the corresponding evaluation result. In some examples, the text description corresponds to the full text description displayed in an expanded text region of possible results page 618 of the tutorial, as described above with reference to
In some embodiments, a details page (e.g., details page 666) includes a share affordance 672 for sharing a document (e.g., a PDF document) summarizing the corresponding ECG recording with an indicated external source (e.g., transmitting the document to an email account). An exemplary document generated for transmittal to the indicated external source is shown in
In some embodiments, a details page (e.g., details page 666) includes an emergency contact affordance 674 (e.g., for seeking immediate medical care, for contacting 911). In some embodiments, in response to detecting a user selection of emergency contact affordance 674, first electronic device 600A initiates a phone call to an emergency contact (e.g., 911).
In some embodiments, a details page (e.g., details page 666) includes a metadata list 676 indicating one or more information items related to the ECG recording (e.g., the device used to perform the recording, the time of the recording, an operating system of the device used to perform the recording).
In some embodiments, a details page (e.g., details page 666) includes a delete affordance 678 for deleting the ECG recording (e.g., from local storage on first electronic device 600A, from local storage on the second electronic device used to perform the recording, such as second electronic device 600B, from remote storage on an external server).
In some embodiments, first electronic device 600A can enable and disable (e.g., via the health application and/or the paired device application described with reference to
As described below, method 700 provides an intuitive way for managing health monitoring. The method reduces the cognitive burden on a user for managing health monitoring, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a user to manage health monitoring faster and more efficiently conserves power and increases the time between battery charges.
The first electronic device (e.g., 600A) displays (706), on the display (e.g., 602), a first portion of a tutorial (e.g., 614, 616, 618, 630, 632) for using a function (e.g., measuring heart rhythm information (an electrocardiogram) or heart rate information (BPM)) of the second electronic device (e.g., 600B) (e.g., a function performed using one or more biometric sensors of the second electronic device). Displaying the first portion of the tutorial for using the function of the second electronic device reduces the number of inputs needed by the user to initialize the first electronic device (e.g., 600A) and the second electronic device (e.g., 600B) for using the function by providing guidance on how to successfully complete the initialization process and providing important background information about using the function (e.g., without forcing the user to, without any guidance, test the function in order to learn how to use the function). 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, prior to displaying, on the display (e.g., 602), the first portion of the tutorial (e.g., 614, 616, 618, 630, 632) for using the function of the second electronic device (e.g., 600B), the first electronic device (e.g., 600A) receives (702) (e.g., via a wireless communication radio of the first electronic device), from the second electronic device (e.g., 600B), a second indication that an application configured to control the use of the function on the second electronic device (e.g., 600B) is opened (e.g., launched, initiated) on the second electronic device (e.g., 600B). Displaying the second indication that the application configured to control the use of the function on the second device (e.g., 600B) is opened provides the user with feedback about the current state of the second electronic device and visually indicates to the user that the second electronic device is ready for the operation that uses the function. 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 to receiving the second indication that the application configured to control the use of the function on the second electronic device (e.g., 600B) is opened, the first electronic device (e.g., 600A) displays (704), on the display (e.g., 602), a notification (e.g., 612) corresponding to the tutorial for using the function of the second electronic device. Displaying, on the display (e.g., 602), the notification corresponding to the tutorial for using the function of the second electronic device provides the user with feedback about the current state of the second electronic device and visually indicates to the user a tutorial is available on the first electronic device (e.g., 600A) to proceed with configuring the use of the function on the second electronic device. 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, the notification (e.g., 612) informs the user that the application has launched on the second electronic device (e.g., 600B) and that the user can view the tutorial for using the function of the second electronic device (e.g., 600B) that relates to the launched application. In some embodiments, the first electronic device (e.g., 600A) displays, on the display (e.g., 602), the tutorial in response to detecting user selection (e.g., a tap gesture) of the notification (e.g., 612). Displaying, on the display (e.g., 602), the tutorial in response to detecting the user selection of the notification (e.g., 612) improves visual feedback by indicating to the user that the tutorial corresponding to the displayed notification has launched on the first electronic device (e.g., 600A). 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, the first electronic device (e.g., 600A) displays the first portion of the tutorial (e.g., 614, 616, 618, 630, 632) in response to an input received while displaying a user interface (e.g., 643) configured to modify one or more settings of the second electronic device (e.g., 600B). Displaying the first portion of the tutorial in response to an input received while displaying a user interface configured to modify one or more settings of the second electronic device improves visual feedback by indicating to the user that the displayed tutorial is associated with an application that can be used on the second electronic device. 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.
The first electronic device (e.g., 600A) detects (708), via the one or more input devices, a request to proceed with the tutorial (e.g., a user's tap input on one or more “continue” buttons, 614C, 616C, 628, 630B).
In response to detecting the request to proceed with the tutorial, the first electronic device (e.g., 600A) displays (710), on the display (e.g., 602), instructions to perform an operation (e.g., capturing/recording biometric data) on the second electronic device (e.g., 600B) that involves the function of the second electronic device (e.g., 600B). Displaying, on the display (e.g., 602) of the first electronic device (e.g., 600A), instructions to perform the operation on the second electronic device (e.g., 600B) that involves the function of the second electronic device improves visual feedback to the user indicating that the operation corresponding to the tutorial needs to be performed on the second electronic device (e.g., and not on the first electronic device). 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, the operation on the second electronic device (e.g., 600B) includes capturing biometric data (e.g., using a biometric sensor of the second electronic device). In some embodiments, the biometric data that is captured by the second electronic device (e.g., 600b) is heart-related data (e.g., ECG data, BPM data).
In some embodiments, the first portion of the tutorial includes a plurality of graphical indications of possible results (e.g., 620, 622, 624, 626, heart rhythm evaluation results, heart rate measurements) of the operation (e.g., an ECG recording operation, a BPM measurement operation) performed on the second electronic device (e.g., 600b).
In some embodiments, the operation is evaluating a medical characteristic (of the user) including a heart rhythm evaluation (e.g., an electrocardiogram reading) and a heart rate evaluation (e.g., a BPM reading), and the possible results are selected from the group consisting of: a normal result (e.g., for the heart rhythm evaluation and/or for the heart rate evaluation), an abnormal heart rhythm pattern result (e.g., signs of Atrial Fibrillation), an abnormal heart rate result (e.g., BPM above a high threshold or below a low threshold, such as BPM over 150 or BPM below 50), and an inconclusive result (e.g., based on a poor reading).
In some embodiments, while displaying at least a first possible result (e.g., 624) of the possible results, where the first possible result includes a portion of (the text of) a first result summary (e.g., 624B, text summarizing medical characteristics related to the respective result), the first electronics device (e.g., 600A) detects, via the one or more input devices, a user activation of an expand affordance (e.g., 624C) associated with the first result summary. Providing the expand affordance while displaying at least the first possible result of the possible results, where the first possible result includes the portion of the first result summary improves visual feedback by indicating to the user that only a portion of the first result summary is not currently displayed, and that the expand affordance can be selected to cause all of the first result summary to be displayed. 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 to detecting the user activation of the expand affordance (e.g., 624C), the first electronic device (e.g., 600A) displays, on the display (e.g., 602), all of (the text of) the first result summary.
In some embodiments, the plurality of graphical indications of possible results (e.g., 620, 622, 624, 626) include a first graphical indication (e.g., 620) that includes display of a first animation (e.g., 620A) related to a first possible result and a second graphical indication (e.g., 622) that includes a second animation (e.g., 622A) related to a second possible result, and the first animation and the second animation are synchronized. In some embodiments, the first animation and the second animations are dynamic animations that include a beating heart animation and tachogram-like features that depict a rhythm and rate of a heartbeat.
In some embodiments, while displaying, on the display (e.g., 602), the plurality of graphical indications (e.g., 620, 622, 624, 626) of possible results, the first electronic device (e.g., 600A) detects, via the one or more input devices, a scrolling gesture (e.g., a scroll on the touch layer of the display). In some embodiments, in response to detecting the scrolling gesture, the first electronic device (e.g., 600A) scrolls the plurality of graphical indications (e.g., 620, 622, 624, 626). In some embodiments, the first electronic device (e.g., 600A) displays, on the display (e.g., 602), a third graphical indication (e.g., 624) that includes a third animation (e.g., 624A) related to a third possible result, where the third animation is synchronized with the first animation (e.g., 620A) and the second animation (e.g., 622A).
In some embodiments, the first animation (e.g., 620A) includes a first portion of the animation (e.g., beating heart) that is animated at a fixed location and a second portion of the animation (e.g., dot) that animatedly moves from the fixed location to a second location. In some embodiments, the object follows a tachogram-like pattern when leaving the heart-shaped animation. In some embodiments, a first object of the first dynamic animation and a second object of the second dynamic animation repeatedly (continuously) leave their respective heart-shaped animations synchronously. Providing an animation (e.g., first animation 620A) for a graphical indication (e.g., one of 620, 622, 624, 626) of possible results improves visual feedback by indicating to the user that the operation discussed by the tutorial relates to heart monitoring, as shown in the animation, and providing visual guidance as to how each possible result derived from the heart monitoring operation differ. 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, the first portion of the tutorial (e.g., 614, 616, 618, 630, 632) includes a limitations indication (e.g., 630, explaining to the user the limits of the operation, showing a list of medical characteristics that cannot be determined by the operation) that includes one or more medical characteristics that cannot be derived from the operation. Providing the limitations indication (e.g., 630) in the first portion of the tutorial improves visual feedback by visually indicating to the user, during the setup process (such that the user is more likely to be made aware), the one or more medical characteristics that cannot be derived from the operation. 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.
The first electronic device 600A receives (716) (e.g., after the user has carried out the instructions on the second electronic device (e.g., 600B), via a wireless radio communication between the devices), from the second electronic device (e.g., 600B), an indication that the instructions have been carried out (on the second electronic device).
In some embodiments, prior to receiving (e.g., via a wireless radio communication between the devices), from the second electronic device (e.g., 600B), the indication that the instructions have been carried out, the first electronic device (e.g., 600A) receives (712), from the second electronic device (e.g., 600B) (e.g., via the wireless radio communication between the devices), an indication that the instructions have begun to be carried out (on the second electronic device). In some embodiments, in response to receiving the indication that the instructions have begun to be carried out, the first electronic device (e.g., 600A) displays (714), on the display (e.g., 602), an indication (e.g., 820, a “recording in progress” page of the tutorial) that the instructions are being carried out on the second electronic device. Displaying, on the display (e.g., 602), the indication that the instructions are being carried out on the second electronic device (e.g., 600B) in response to receiving the indication that the instructions have begun to be carried out enhances visual feedback by visually indicating to the user that the operation is being successfully carried out on the second electronic device (and thus that the setup process is proceeding along as intended). 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 response to receiving the indication that the instructions have been carried out, the first electronic device (e.g., 600A) displays (718), on the display (e.g., 602), a second portion of the tutorial (e.g., 828, a “completion” page) that is different from the first portion. Displaying, on the display (e.g., 602), the second portion of the tutorial that is different from the first portion in response to receiving the indication that the instructions have been carried out improves visual feedback by indicating to the user that the operation performed on the second electronic device has been completed (e.g., and thus that the setup process has been successfully completed and that the operation is available for future use). 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, the second portion of the tutorial (e.g., 828, a “completion” page) includes a graphical animation (e.g., a tachogram-like animation) that represents (biometric) information obtained from the operation on the second electronic device.
In some embodiments, after displaying, on the display (e.g., 602), the second portion of the tutorial (e.g., 828), the first electronic device (e.g., 600A) displays (720), on the display (e.g., 602), a user interface of a health application (e.g., 650, 656, 660).
In some embodiments, the first electronic device (e.g., 600A) detects (722), via the one or more input devices, a user activation of an affordance (e.g., 658A, an ECG affordance) for viewing recorded biometric information (e.g., recorded ECG and BPM readings). In some embodiments, the affordance (e.g., 658A) for viewing existing recordings of biometric information includes an indication of a number of existing recordings of biometric information (e.g., a number of recorded ECG and/or BPM readings). Providing the indication of the number of existing recordings of biometric information in the affordance for viewing existing recordings of biometric information improves visual feedback by conveniently conveying to the user the number of existing recordings that can be viewed in the health application. 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 to detecting the user activation of the affordance (e.g., 658A) for viewing existing recordings of biometric information, the first electronic device (e.g., 600A) displays (724), on the display (e.g., 602), a first plurality of representations (e.g., 662A-662C) corresponding to existing recordings of biometric information. In some embodiments, a representation of an existing recording of biometric information (e.g., 662A-66C) includes a tachogram corresponding to the recording, an evaluation result of the recording, the number of symptoms (if any) associated with the recording, and a heart rate (BPM) recorded by the recording. Displaying, on the display (e.g., 602), the first plurality of representations (e.g., 662A-662C) corresponding to existing recordings of biometric information in response to detecting the user activation of the affordance for viewing existing recordings of biometric information improves visual feedback by conveniently providing to the user representations of some existing recordings (e.g., some of the most recent recordings) that may be of most relevance to the user. 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, the first plurality of representations of existing recordings of biometric information (e.g., 662A-66C) include a first representation (e.g., 662C) corresponding to a first existing recording with an abnormal evaluation result (e.g., an abnormal heart rhythm, such as a Atrial Fibrillation condition), where the first representation (e.g., 662C) includes an indication of the abnormal evaluation result that is displayed with a first visual characteristic (e.g., highlighted with a warning color, such as yellow). In some embodiments, the plurality of representations of existing recordings of biometric information (e.g., 662A-66C) include a fourth representation (e.g., 662A) corresponding to a fourth existing recording with a normal evaluation result, and the fourth representation includes an indication of the normal evaluation result that is displayed with a second visual characteristic (e.g., a default color) different from the first visual characteristic.
In some embodiments, the first plurality of representations of existing recordings of biometric information (e.g., 662A-66C) include a second representation (e.g., 662A, 662B) corresponding to a second existing recording associated with user-specified symptoms, where the second representation includes an indication of the number of user-specified symptoms associated with the second existing recording (e.g., “2 Symptoms,” “No Symptoms”). In some embodiments, the first plurality of representations of existing recordings of biometric information (e.g., 662A-66C) include a third representation (e.g., 662C) corresponding to a third existing recording not associated with any user-specified symptoms (e.g., because the user did not specify any symptoms for the recording), where the third representation does not include an indication of user-specified symptoms associated with the third existing recording. Providing the second representation (e.g., 662A, 662B) corresponding to the second existing recording associated with user-specified symptoms improves visual feedback by conveniently indicating to the user whether or not (and if yes, how many) symptoms were previously selected by the user for the recording (e.g., thereby allowing the user to quickly recognize whether a particular recording by correspond to a more serious reading, if there are many user-specified symptoms associated with the recording). 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, the user-specified symptoms cannot be modified after the symptoms have been specified and saved (by the user on the second electronic device).
In some embodiments, further in response to detecting the user activation of the affordance (e.g., 658A) for viewing recorded biometric information, the first electronic device (e.g., 600A) displays (726), on the display (e.g., 602), a plurality of sort affordances (e.g., 664A-664H, to filter visible recordings by the type of evaluation results, such as normal results, abnormal heart rhythm results, or abnormal heart rate results) including a first sort affordance and a second sort affordance. In some embodiments, the first sort affordance includes an indication of a number of existing recordings of biometric information associated with the first type of evaluation result, and the second sort affordance includes an indication of a number of existing recordings of biometric information associated with the second type of evaluation result. In some embodiments, the first electronic device (e.g., 600A) detects (728), via the one or more input devices, a user activation of the first sort affordance.
In some embodiments, in response to detecting the user activation of the first sort affordance, the first electronic device (e.g., 600A) displays (730), on the display (e.g., 602), a second plurality of representations (e.g., by replacing the first plurality of representations) corresponding to existing recordings of biometric information, where the second plurality of representations correspond to existing recordings associated with a first type of evaluation result (e.g., a normal result, an abnormal heart rhythm result, an abnormal heart rate result, an inconclusive result). In some embodiments, the first electronic device (e.g., 600A) detects (732), via the one or more input devices, a user activation of the second sort affordance.
In some embodiments, in response to detecting user activation of the second sort affordance, the first electronic device (e.g., 600A) displays (734), on the display (e.g., 602), a third plurality of representations (e.g., by replacing the first plurality of representations) corresponding to existing recordings of biometric information, where the third plurality of representations correspond to existing recordings associated with a second type of evaluation result. In some embodiments, the second and third plurality of representations have corresponding overlapping existing recordings, if one or more existing recordings are associated with both the first type of evaluation result and the second type of evaluation result.
In some embodiments, the first electronic device (e.g., 600A) detects, via the one or more input devices, a user selection of a first representation (e.g., 662A) of the first plurality of representations (e.g., 662A-66C) corresponding to a first existing recording corresponding to a first evaluation result. In some embodiments, in response to detecting the user selection of the first representation, the first electronic device (e.g., 600A) displays a first details view (e.g., 666) of the first existing recording.
In some embodiments, while displaying the first details view (e.g., 666) of the first existing recording, the first electronic device (e.g., 600A) detects, via the one or more input devices, a user activation of an information affordance (e.g., 670, an “i” icon). In some embodiments, in response to detecting the user activation of the information affordance (e.g., 670), the first electronic device (e.g., 600A) displays, on the display (e.g., 602), a result summary (e.g., text summarizing medical characteristics related to the respective result) and an animation from a corresponding possible result from the first portion of the tutorial (e.g., where the possible result from the tutorial corresponds to the evaluation result of the first existing recording).
In some embodiments, while displaying the first details view (e.g., 666) of the first existing recording corresponding to a first evaluation result, the first electronic device (e.g., 600A) detects, via the one or more input devices, a user activation of an export affordance (e.g., 672, marked as “share as a PDF”). In some embodiments, in response to detecting user activation of the export affordance (e.g., 672), the first electronic device (e.g., 600A) creates (and subsequently transmitting to an intended recipient) a document that includes information concerning the first existing recording (e.g., information about the user, date and time of the recording, a tachogram of the (ECG) recording, the evaluation result of the recording). In some embodiments, the biometric data (e.g., ECG data) of the recording is included in the document without any filtering (of the data from the recording). (Automatically) generating and (automatically) transmitting the document (to an intended recipient) in response to detecting the user activation of the information affordance reduces the number of inputs needed from the user to create a transmittal document summarized a recording and subsequently transmitting the document to an intended recipient. 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 user-specified symptoms cannot be modified after the symptoms have been specified and saved (by the user on the second electronic device).
Note that details of the processes described above with respect to method 700 (e.g.,
In some embodiments, similar to user interface 644, user interface 806 includes an animation 808 (e.g., a fluid animation, corresponding to animation 646 of user interface 644) that depicts a particular shape (e.g., a heart). In some examples, as shown in
In some embodiments, while displaying animation 808 in the particular shape (e.g., a heart), user interface 806 displays a notification message 810 (e.g., corresponding to notification message 648 of user interface 644) indicating to the user that an action must be performed (by the user) on the device to proceed with an ECG recording (to capture heart rhythm and heart rate information). In some embodiments, notification message 810 instructs the user of the type of input (e.g., a touch or contact on the input device that is below a threshold amount such that the input does not “click” the input device) and that the input must be maintained on the input device (e.g., for the duration of the recording).
In some embodiments, prior to displaying user interface 806 of the ECG application (e.g., while first electronic device 800A is displaying a user interface of a different application or the display is off), the device detects (e.g., using a second biometric sensor that measures heart rate information without user input) heart rate information of the user for a period of time (e.g., 1 minute) and determines that the detected heart rate is above a threshold rate (e.g., above 150 BPM). In some embodiments, upon detecting that the detected heart rate is above the threshold rate for at least the period of time, the device displays, on display 802, a notification informing the user of the (continuous) high heart rate and requests that the user monitor his or her heart health using the ECG application.
In
In some embodiments, if the user input on input device 804 is not restored within a time limit (e.g., 5 seconds), first electronic device 800A (automatically) terminates the recording and transitions back to the initial user interface of
In
In some embodiments, (immediately) after completing the ECG recording, first electronic device 800A displays, on display 802, user interface 806 of the ECG application with animation 808 in its initial pattern (e.g., a fluid heart-shaped pattern) and at least a portion of a summary page 826 that includes an evaluation result (e.g., “Regular Result”) and other related information about the completed recording. In some embodiments, summary page 826 slides onto the display from an edge of the display (e.g., a bottom edge of the display).
In some embodiments, (immediately) after completing the ECG recording, second electronic device 800B displays, in the health application, a summary page 828 of the health application associated with the ECG application on second electronic device 800A, where summary page 828 includes a representation 830 of the completed recording. In some embodiments, representation 830 includes the evaluation result (e.g., “Regular Rhythm”), the heart rate reading (e.g., in BPM), and a graphical depiction (e.g., a tachogram) of the recording. In some embodiments, summary page 828 includes an affordance 832 for leaving the summary page.
In
In
In
In
In some embodiments (e.g., after resetting the recording), upon detecting that the user input on input device 804 has not been restored for a at least a predetermined period of time (e.g., 2.5 seconds), first electronic device 800A displays, in user interface 806 of the ECG application, a notification message 852 (e.g., stating “Hold your finger on the crown”) requesting that the user restore the input on input device 804, as shown in
In some embodiments (e.g., after resetting the recording), upon detecting that the user input on input device 804 has not been restored for at least the predetermined period of time (e.g., 2.5 seconds), first electronic device 800A alternatively displays, in user interface 806 of the ECG application, animation 808 in its initial pattern (e.g., a heart shape) but forgoes displaying notification message 852, as shown in
In some embodiments, first electronic device 800A first transitions form the user interface of
As described below, method 900 provides an intuitive way for managing health monitoring. The method reduces the cognitive burden on a user for managing health monitoring, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a user to manage health monitoring faster and more efficiently conserves power and increases the time between battery charges.
The first electronic device (e.g., 800A) displays (908), on the display (e.g., 802), a first user interface (e.g., of a health monitoring application or a health data measurement application, main user interface 806 of the ECG application, as shown in
In some embodiments, prior to displaying the first user interface (e.g., 806 of
In some embodiments, a (text) notification (e.g., 810) requesting the first input on the biometric sensor (e.g., 804) is displayed in the first user interface (e.g., 806 of
In some embodiments, the recorded biometric information includes an electrocardiogram recording derived from the biometric information detected by the biometric sensor (e.g., 804). In some embodiments, the biometric sensor (e.g., 804) is a contact-based sensor, and the first input with the biometric sensor (e.g., 804) satisfies the first criteria when a contact (e.g., from a finger of a user) is detected on the biometric sensor (e.g., 804).
The first electronic device (e.g., 800A) detects (910) a first input with the biometric sensor (e.g., 804) that satisfies first criteria (e.g., user contact with the biometric sensor, movement below a threshold, electrical interference below a threshold).
In response to detecting the first input with the biometric sensor (e.g., 804), the first electronics device (e.g., 800A) starts (912) to record biometric information detected by the biometric sensor (e.g., 804). Also in response to detecting the first input with the biometric sensor (e.g., 804), the first electronic device (e.g., 800A) displays (914), on the display (e.g., 802), a second user interface (e.g., 806 of
After recording at least a portion of the biometric information, the first electronic device (e.g., 800A) detects (912), via the one or more input devices, that the first criteria are no longer met (e.g., user contact with the biometric sensor 804 is lost).
In response to detecting that the first criteria are no longer met for a first period of time (e.g., 5 seconds), the first electronic device (e.g., 800A) resets (918) the indication of progress (e.g., 810) in recording the biometric information and maintaining display of the second user interface (e.g., 806 of
In response to detecting that the first criteria are no longer met for a second period of time that is longer than the first period of time (e.g., longer than 5 seconds), the first electronic device (e.g., 800A) replaces (920) display of the second user interface (e.g., 806 of
In some embodiments, the first user interface (e.g., 806 of
In some embodiments, the plurality of moving objects (e.g., 808) of the graphical animation transitions from the first shape (e.g., a heart shape) to a second shape (e.g., a grid shape) different from the first shape as the display transitions from the first user interface to the second user interface.
In some embodiments, further in response to detecting that the first criteria are no longer met for the first period of time, the first electronic device (e.g., 800A) transitions the plurality of moving objects (e.g., 808) of the graphical animation to an interstitial shape between the first shape (e.g., a heart shape) and the second shape (e.g., a grid shape).
In some embodiments, while displaying the second user interface (e.g., 806 of
In some embodiments, the second user interface (e.g., 806 of
In some embodiments, while recording the biometric information, the first electronic device (e.g., 800A) detects, via the one or more input devices, that second criteria are met. In some embodiments, in response to detecting that the second criteria are met, the first electronic device (e.g., 800A) displays, in the second user interface (e.g., 806 of
In some embodiments, the second criteria is met when an amount of movement (of the device caused by the user) above a threshold is detected, and the notification (e.g., 844) indicates (to the user) that the amount of movement should be decreased. In some embodiments, the notification (e.g., 844) notifies the user that too much movement is detected. In some embodiments, the notification (e.g., 844) further notifies the user to constrain his/her movements.
In some embodiments, the second criteria is met when the amount of movement (of the device caused by the user) above the threshold is detected for at least a third period of time, and the notification (e.g., 846) indicates (to the user) that the first electronic device should be moved to a resting position (e.g., on a table). In some embodiments, if the first electronic device is a smartwatch, the notification (e.g., 846) instructs the user to rest his/her arm on a table.
In some embodiments, the second criteria is met when a second input (e.g., a press input, a click input) having a type that is different from the type of the first input is detected on a first input device (e.g., 804, a crown, a mechanical button, a rotating button), and the notification (e.g., 848) indicates (to the user) that the second input should not be repeated on the first input device. In some embodiments, the biometric sensor includes one or more electrodes integrated in the first input device (e.g., 804) (e.g., operating in conjunction with one or more electrodes integrated in a housing portion (e.g., backplate) of the first electronic device (e.g., 800A). In some embodiments, the second input is a press/click input on the first input device (e.g., 804), and the notification (e.g., 848) notifies that the user should not press/click the first input device (e.g., 804).
In some embodiments, the second criteria is met when the first input is no longer detected (e.g., discontinued, interrupted) by the biometric sensor (e.g., 804) when recording of the biometric information is not yet completed, and the notification (e.g., 850) indicates (to the user) that the first input should be maintained on the biometric sensor (e.g., 804). In some embodiments, the first electronic device (e.g., 800A) detects that the first input is no longer detected when the user discontinues contact with the biometric sensor (e.g., 804) while recording of the biometric information is still ongoing. In some embodiments, the notification (e.g., 850) instructs the user to re-establish contact with (e.g., by placing his/her finger back on) the biometric sensor (e.g., 804).
In some embodiments, after taking a first recording of first biometric information and a second recording of second biometric information different from the first biometric information (e.g., where the first recording and the second recording are different recordings that were taken at different times), the first electronic device (e.g., 800A) transmits (922), to a second electronic device (e.g., 800B, a smartphone paired with the smartwatch), the recorded first biometric information and the recorded second biometric information.
In some embodiments, (e.g., while not displaying the application corresponding to the first and second user interfaces on the display) the first electronic device (e.g., 800A) detects (924) (e.g., via a second biometric sensor that measures heart rate information without user input) heart rate information (of the user) for a predetermined amount of time. In some embodiments, in accordance with a determination that the detected heart rate information meets a first condition (e.g., above a threshold, such as 150 BPM, above a threshold for a certain amount of time), the first electronic device (e.g., 800A) displays (926), on the display (e.g., 802), a notification indicating a high heart rate. Displaying, on the display (e.g., 802), the notification indicating the high heart rate in accordance with the determination that the detected heart rate information meets the first condition improves visual feedback by quickly informing the user of the high heart rate. 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, the first electronic device (e.g., 800A) detects (928), via the one or more input devices, a user activation of the notification. In some embodiments, in response to detecting the user activation of the notification, the first electronic device (e.g., 800A) displays (930), on the display (e.g., 802), the first user interface (e.g., 806 of
Note that details of the processes described above with respect to method 900 (e.g.,
A.
In some embodiments, first electronic device 1000 is configured to detect and respond to activation of input device 1004 (e.g., respond by performing a first predefined operation or a second predefined operation), where the activation is different from and independent of the capture of biometric information (e.g., ECG information).
In some embodiments, user interface 1006 includes an animation 1008 (e.g., a fluid animation, corresponding to animation 646 of user interface 644 and animation 808 of user interface 806) that depicts a particular shape (e.g., a heart). In some examples, as shown in
In some embodiments, while displaying animation 1008 in the particular shape (e.g., a heart), user interface 1006 displays a notification message 1010 (e.g., corresponding to notification message 648 of user interface 644 and notification message 810 of user interface 806, stating “Hold your finger on the crown”) indicating to the user that an action must be performed (by the user) on the device to proceed with recording the user's ECG information. In some embodiments, notification message 1010 instructs the user of the type of input (e.g., a touch or contact on input device 1004 that is below a threshold amount such that the input does not “click” input device 1004) and that the input must be maintained on input device 1004 (e.g., for the duration of the recording).
In some embodiments, while displaying user interface 1006 of the ECG application as shown in
In some embodiments, in response to detecting press input 1001 while displaying user interface 1006 of the ECG application as shown in
In some embodiments, after detecting press input 1007 on input device 1004 after the initial threshold time period (e.g., 5 seconds) has passed, in response to which first electronic device 1000 does not terminate the recording, the device detects a second press input (e.g., similar to press input 1007) after detecting press input 1007 but before a predetermined amount of time (e.g., 2.5 seconds) has passed since detecting press input 1007. In some embodiments, in response to detecting the second press input after detecting press input 1007 but before the predetermined amount of time (e.g., 2.5 seconds) has passed since detecting press input 1007, first electronic device 1000 (automatically) terminates the recording and displays user interface 1006 of the ECG application as shown in
In some embodiments, after detecting press input 1007 on input device 1004 after the initial threshold time period (e.g., 5 seconds) has passed, in response to which first electronic device 1000 does not terminate the recording, the device detects a second press input (e.g., similar to press input 1007) after detecting press input 1007 and after a predetermined amount of time (e.g., 2.5 seconds) has passed since detecting press input 1007. In some embodiments, (instead of terminating the recording) first electronic device 1000 displays, in user interface 1006, a notification message 1020 (e.g., stating “You do not need to click the crown”) indicating that there is no need to “click” input device 1004 during the recording or to successfully complete the recording. In summary, in some embodiments and while recording is underway, termination of recording occurs if two inputs are received within a predetermined period (e.g., within rapid succession (e.g., within 2.5 seconds)). In contrast, in some embodiments, if two inputs are received but spaced apart by more than the predetermined period (e.g., within 2.5 seconds) the recording is not cancelled.
In some embodiments, at least a predetermined amount of time (e.g., 5 seconds) after detecting user input 1009, first electronic device 1000 detects a press a press-and-hold input 1011 on input device 1004, where the press-and-hold input is an input on input device 1004 with a pressing force above a threshold amount such that the input “clicks” input device 1004, and input device 1004 is “clicked” for at least a threshold period of time (e.g., 1 second). In some embodiments, in response to detecting press-and-hold input 1011 on input device 1004 while the initial threshold time period has not yet passed, first electronic device 1000 (automatically) displays, on display 1002 (e.g., replaces display of user interface 1006 of the ECG application with), a user interface 1022 of a virtual assistant (e.g., a virtual assistant controlled by the operating system of the device), as shown in
In some embodiments, upon (or prior to) beginning an ECG recording, first electronic device 1000 automatically disables a wireless communication radio (e.g., a LTE connection) of the device. In some embodiments, upon (or in response to) completing the ECG recording, first electronic device 1000 automatically re-enables the wireless communication radio on the device.
In some embodiments, upon (or prior to) beginning an ECG recording, first electronic device 1000 automatically disables a haptic feedback controller (e.g., a haptic actuator) of the device. In some embodiments, upon (or in response to) completing the ECG recording, first electronic device 1000 automatically re-enables the haptic feedback controller of the device.
As described below, method 1100 provides an intuitive way for managing health monitoring. The method reduces the cognitive burden on a user for managing health monitoring, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a user to manage health monitoring faster and more efficiently conserves power and increases the time between battery charges.
The first electronic device (e.g., 1000) displays (1102), on the display (e.g., 1002), a user interface (e.g., 1006 of
In some embodiments, the first electronic device (e.g., 1000) is configured to detect and respond to activation of the first input device (e.g., 1004, respond by performing the predefined operation or a second predefined operation), where the activation is different from and independent of the capture of biometric information.
In some embodiments, the application is configured to cause the first electronic device (e.g., 1000) to capture the biometric information without detecting the activation of the first input device (e.g., 1004).
While displaying the user interface (e.g., 1006 of
In response to detecting the first activation of the first input device (e.g., 1004, a press on the first input device) and while capturing biometric information from the biometric sensor (e.g., 1004), in accordance with a determination that the first activation of the first input device (e.g., 1004) was detected when first criteria are met (e.g., the device has captured less than a predetermined amount of biometric information and/or the first input device has been activated within at least a threshold amount of time, such as 5 seconds), where the first criteria are based on progress toward capturing biometric information with the biometric sensor (e.g., 1004), the first electronic device (e.g., 1000) performs (1106) a predefined operation associated with the first input device (e.g., 1004) that interrupts capture of the biometric information (e.g., scrolling of a displayed content, exiting a currently active application, activation of a digital assistant function). Performing the predefined operation associated with the first input device (e.g., 1004) that interrupts the capture of biometric information in accordance with the determination that the first activation of the first input device (e.g., 1004) was detected when the first criteria are met provides the user with more control of the device by enabling the user to interrupt the capture of biometric information in certain situations through an input on the first input 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.
Also in response to detecting the first activation of the first input device (e.g., 1004, a press on the first input device) and while capturing biometric information from the biometric sensor (e.g., 1004), in accordance with a determination that the first activation of the first input device (e.g., 1004) was detected when the first criteria are not met, the first electronic device (e.g., 1000) continues (1108) to capture the biometric information without performing the predefined operation associated with the first input device (e.g., 1004). Continuing to capture the biometric information without performing the predefined operation associated with the first input device (e.g., 1004) in accordance with the determination that the first activation of the first input device was detected when the first criteria are not met provides the user with more control of the device by enabling the user continue with the capturing of the biometric information in certain situations without having to manually re-initiate the recording process. 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.
In some embodiments, prior to capturing the biometric information (e.g., while displaying an introductory animation, such as animation 808 of main user interface 806 as shown in
In some embodiments, the predefined operation includes displaying, on the display (e.g., 1002), a predefined user interface (e.g., 1012, a homescreen that includes one or more affordances for launching an application). In some embodiments, displaying the predefined user interface (e.g., 1012) includes closing or suspending any currently active or running application (e.g., the application for capturing biometric information).
In some embodiments, the predefined operation includes displaying, on the display (e.g., 1002), a user interface (e.g., 1022) of a digital virtual assistant (e.g., by replacing display of the user interface (e.g., 1006) of the application for capturing biometric information).
In some embodiments, the first criteria are met when capturing the biometric information has occurred for less than a first threshold amount of time (e.g., 5 seconds).
In some embodiments, after continuing to capture the biometric information without performing the predefined operation associated with the first input device (e.g., 1004), the first electronic device (e.g., 1000) detects (1110) a second activation of the first input device (e.g., 1004). In some embodiments, in response to detecting the second activation of the first input device (e.g., 1004), in accordance with a determination that the second activation of the first input device (e.g., 1004) was detected within a predetermined time (e.g., 5 seconds) after detecting the first activation of the first input device (e.g., 1004), the first electronic device (e.g., 1000) performs (1112) the predefined operation associated with the first input device (e.g., 1004) that interrupts capture of the biometric information. Performing the predefined operation associated with the first input device (e.g., 1004) that interrupts the capture of the biometric information in accordance with the determination that the second activation of the first input device was detected within the predetermined time after detecting the first activation of the first input device provides the user with more control of the device and reduces the number of inputs needed to interrupt the capturing of the biometric information by allowing the user to quickly and easily interrupt the capturing of biometric information using the first input device. Providing additional control of the device and 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, in response to detecting the second activation of the first input device (e.g., 1004), in accordance with a determination that the second activation of the first input device (e.g., 1004) was detected after the predetermined time after detecting the first activation of the first input device (e.g., 1004), the first electronic device (e.g., 1000) continues (1114) to capture the biometric information without performing the predefined operation associated with the first input device (e.g., 1004). Continuing to capture the biometric information without performing the predefined operation associated with the first input device (e.g., 1004) in accordance with the determination that the second activation of the first input device was detected after the predetermined time after detecting the first activation of the first input device provides the user with more control of the device by helping the user avoid unintentionally interrupting the capturing of the biometric information and simultaneously allowing the user to recognize that another and/or different input is required to interrupt the capturing of the biometric information. Providing additional control of the device (without cluttering the user interface 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.
In some embodiments, upon (or prior to) capturing the biometric information (e.g., heart rhythm information, heart rate information) from the biometric sensor (e.g., 1004), the first electronic device (e.g., 1000) automatically disables a haptic feedback controller (e.g., a haptic actuator associated with the first input device) of the first electronic device (e.g., 1000). In some embodiments, upon (or in response to) completing capturing the biometric information, the first electronic device (e.g., 1000) automatically re-enables the haptic feedback controller.
In some embodiments, upon (or prior to) capturing the biometric information (e.g., heart rhythm information, heart rate information) from the biometric sensor, the first electronic device (e.g., 1000) automatically disables a wireless communication radio (e.g., LTE connection) of the first electronic device (e.g., 1000) and prevents a first type of notification (e.g., 1026, of a message, of an alert, a type of notification other than a timer notification) from being displayed, where the first type of notification includes a notification corresponding to an electronic communication (e.g., a text message, an email, a phone call) received while the capturing the biometric information. In some embodiments, the notifications that are prevented from being displayed do not include a timer notification. In some embodiments, upon (or in response to) completing capturing the biometric information, the first electronic device (e.g., 1000) automatically re-enables the wireless communication radio and allows the first type of notification (e.g., 1030) to be displayed.
Note that details of the processes described above with respect to method 1100 (e.g.,
In
In some embodiments, summary region 1208 also includes a information affordance 1210 for viewing a detailed description about the respective evaluation result. In some embodiments, while displaying summary page 1206, first electronic device 1200 detects (e.g., via a touch input) a user activation 1201 of information affordance 1210.
In
In some embodiments, as shown in
In
In some embodiments, symptoms page 1222 includes a selectable symptoms list 1224 that includes a plurality of symptoms options, of which one or more of the listed symptoms can be selected by the user from the list. In some examples, a symptom option of selectable symptoms list 1224 is a “Light headed or dizzy” option. In some examples, a symptom option of selectable symptoms list 1224 is a “Fainting or near fainting spells” option. In some examples, a symptom option of selectable symptoms list 1224 is a “Shortness of breath” option. In some examples, a symptom option of selectable symptoms list 1224 is a “Chest pain” option. In some examples, a symptom option of selectable symptoms list 1224 is an “Other” option (e.g., for indicating one or more symptoms that are not listed in the selectable symptoms list). In some examples, a symptom option of selectable symptoms list 1224 is a “None” option (e.g., for indicating that the user is not experiencing (or was not experiencing during the time of the ECG recording) any abnormal symptoms).
In
In some embodiments, first electronic device 1200 detects a scrolling gesture (e.g., via a scrolling touch gesture, via a rotating input on input device 1204, a rotating crown) on symptoms page 1222 and, in response to the scrolling gesture, scrolls the page to reveal a bottom portion of the page. In some embodiments, as shown in
In some embodiments, in response to detecting user activation 1215 of return affordance 1228, if at least one of the user-specified symptoms are determined to be “serious” symptoms (e.g., symptoms that may require immediate medical attention), first electronic device 1200 displays, on the display 1202, an alert page 1230, as shown in
In some embodiments, in response to detecting user activation 1215 of return affordance 1228, if none of the user-specified symptoms are determined to be “serious” symptoms (e.g., symptoms that may require immediate medical attention), first electronic device 1200 (automatically) displays summary page 1206 without displaying alert page 1230.
In
In some embodiments, updated symptoms region 1236 further includes an edit affordance 1238 for returning to symptoms page 1222 to modify the user-specified symptoms from selectable symptoms list 1224. In some embodiments, the user-specified symptoms of an ECG recording cannot be modified (either at first electronic device 1200 or at a second electronic device paired to first electronic device 1200, such as a smartphone) upon leaving the ECG application while on that recording.
In
In some embodiments, within a summary region (e.g., 1248) of a summary page (e.g., 1206), an indication of the evaluation result of an ECG recording (e.g., “regular,” “Atrial Fibrillation,” “high heart rate,” “low heart rate,” “inconclusive”) is highlighted with a warning visual characteristic (e.g., a warning color, such as yellow) if the result is an abnormal result (e.g., “Atrial Fibrillation,” “high heart rate,” “low heart rate”) different from a default visual characteristic (e.g., a default color). Similarly, in some embodiments, within a summary region of a summary page, an indication of the heart rate measurement of an ECG recording (e.g., the BPM) is highlighted with the warning visual characteristic (e.g., a warning color, such as yellow) if the heart rate is abnormal high (e.g., above 100 BPM) or abnormally low (e.g., below 50 BPM). In some embodiments, if one of the evaluation result or heart rate measurement is abnormal, both the indication of the evaluation result and the indication of the heart rate measurement are displayed with warning visual characteristic
In some embodiments, as indicated by an alternate summary region 1261, if the heart rhythm result is a normal result (e.g., a non-Atrial Fibrillation result) and the heart rate result is an abnormal result (e.g., a high or low heart rate result), evaluation result 1261A of summary region 1261 indicates the abnormal heart rate result (e.g., by stating “Heart rate over 100,” “Heart rate over 150,” “Heart rate below 50”) while BPM indication 1261B is maintained. In some embodiments, evaluation result indication 1261A is highlighted with the warning visual characteristic (e.g., text “Heart rate over 100” is displayed in a warning color, such as yellow) and BPM indication 1261B is highlighted with the warning visual characteristic (e.g., text “120 BPM” is displayed in the warning color, such as yellow).
As described below, method 1300 provides an intuitive way for managing health monitoring. The method reduces the cognitive burden on a user for managing health monitoring, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a user to manage health monitoring faster and more efficiently conserves power and increases the time between battery charges.
The first electronic device (e.g., 1200) captures (1302) biometric information with a biometric sensor that is in communication with the first electronic device (e.g., comprising one or more electrodes integrated an input device (e.g., 1204) operating in conjunction with one or more electrodes of a housing portion (e.g., backplate) of the first electronic device).
The first electronic device (e.g., 1200) displays (1304), on the display (e.g., 1202), a representation (e.g., 1208) of an evaluation of a medical characteristic (e.g., related to heart health) determined based on the biometric information (e.g., ECG data, BPM data, heart-related data) captured by the biometric sensor. Displaying, on the display (e.g., 1202), the representation of the evaluation of the medical characteristic improves visual feedback by enabling the user to quickly and easily see the result of the evaluation based on the captured biometric 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.
In some embodiments, upon (or prior to) capturing the biometric information with the biometric sensor, the first electronic device (e.g., 1200) automatically disables a wireless communication radio (e.g., RF circuitry 108, a LTE connection) of the first electronic device and prevents notifications (e.g., of a message, of an alert) from being displayed. Automatically disabling the wireless communication radio of the first electronic device (e.g., 1200) and preventing notifications from being displayed enables the user to perform more accurate recordings of biometric information without manually disabling certain other functions of the device that may interrupt or interfere with the capturing of the biometric information. Performing an operation without requiring 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 notifications that are prevented from being displayed do not include a timer notification.
In some embodiments, upon (or in response to) completing capture of the biometric information, the first electronic device (e.g., 1200) automatically re-enables the wireless communication radio (e.g., RF circuitry 108, a LTE connection) and allows notifications to be displayed. Automatically re-enabling the wireless communication radio and allowing notifications to be displayed upon completing capture of the biometric information reduces the number of inputs required from the user to control the device by enabling the user to bypass having to manually re-enable the wireless communication radio and allow notifications to be displayed. 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 medical characteristic includes a heart rhythm characteristic (e.g., a characteristic corresponding to 1208A) and a heart rate characteristic (e.g., a characteristic corresponding to 1208B), and the displayed representation of the evaluation of the medical characteristic includes a heart rhythm evaluation (e.g., a electrocardiogram evaluation, 1208a) summary and a heart rate evaluation (e.g., a BPM reading, 1208B) summary.
In some embodiments, the heart rhythm evaluation summary (e.g., 1252A) is displayed with a first visual characteristic (e.g., a first color, a warning color such as yellow) and the heart rate evaluation summary (e.g., 1252B) is displayed with the first visual characteristic when the heart rhythm evaluation corresponds to an abnormal result and the heart rate evaluation corresponds to an abnormal result. Displaying the heart rhythm evaluation summary (e.g., 1252A) with the first visual characteristic and the heart rate evaluation summary (e.g., 1252B) with the first visual characteristic when the heart rhythm evaluation corresponds to an abnormal result and the heart rate evaluation corresponds to an abnormal result improves visual feedback by enabling the user to quickly and easily recognize the out of the evaluation result and whether the evaluation result should be paid closer attention to (e.g., for further medical attention). 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, the heart rhythm analysis evaluation (e.g., 1252A) corresponds to an abnormal result if an abnormal rhythm pattern is detected (e.g., signs of Atrial Fibrillation). In some embodiments, the heart rate evaluation (e.g., 1252B) corresponds to an abnormal result if the rate is greater than a high limit number (e.g., 100 BPM).
In some embodiments, the heart rhythm evaluation summary (e.g., 1248A) is displayed with the first visual characteristic and the heart rate evaluation summary (e.g., 1248B) is not displayed with the first visual characteristic when the heart rhythm evaluation corresponds to an abnormal result (e.g., signs of Atrial Fibrillation) and the heart rate evaluation corresponds to a normal result (e.g., 60-100 BPM). Displaying the heart rhythm evaluation summary (e.g., 1248A) with the first visual characteristic and not displaying the heart rate evaluation summary (e.g., 1248B) with the first visual characteristic when the heart rhythm evaluation corresponds to an abnormal result and the heart rate evaluation corresponds to a normal result improves visual feedback by enabling the user to quickly and easily recognize and differentiate between an abnormal result and a normal result, and whether an evaluation result should be paid closer attention to (e.g., for further medical attention). 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, the heart rate evaluation summary (e.g., 1260A) is displayed with the first visual characteristic and the heart rhythm evaluation summary (e.g., 1260B) is not displayed with the first visual characteristic when the heart rate evaluation corresponds to an abnormal result (e.g., BPM below 50 or above 100) and the heart rhythm evaluation (e.g., 1260A) corresponds to a normal result. Displaying heart rate evaluation summary (e.g., 1260A) with the first visual characteristic and not displaying the heart rhythm evaluation summary (e.g., 1260B) with the first visual characteristic when the heart rate evaluation corresponds to an abnormal result (e.g., BPM below 50 or above 100) and the heart rhythm evaluation corresponds to a normal result improves visual feedback by enabling the user to quickly and easily recognize and differentiate between an abnormal result and a normal result, and whether an evaluation result should be paid closer attention to (e.g., for further medical attention). 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, the heart rate evaluation summary (e.g., 1264A) is displayed with a first visual characteristic and the heart rhythm evaluation summary (e.g., 1264B) is displayed with the first visual characteristic when the heart rate evaluation corresponds to a highly abnormal result (e.g., BPM over 150 or below 50) such that a determination cannot be made on the heart rhythm evaluation. Displaying the heart rate evaluation summary (e.g., 1264A) and the heart rhythm evaluation summary (e.g., 1264B) with the first visual characteristic when the heart rate evaluation corresponds to a highly abnormal result (e.g., BPM over 150 or below 50) such that a determination cannot be made on the heart rhythm evaluation improves visual feedback by enabling the user to quickly and easily recognize that the result corresponds to a highly abnormal result and that the evaluation result should be paid closer attention to (e.g., for further medical attention). 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 accordance with a determination that the evaluation of the medical characteristic cannot be determined (e.g., because the biometric information captured by the biometric sensor is incomplete or is of poor quality), the first electronic device (e.g., 1200) displays (1306), in the representation of the evaluation, an indication that the evaluation was inconclusive (e.g., 1272A). In some embodiments, the evaluation also includes a text description (e.g., 1270) explaining to the user why the evaluation was inconclusive (e.g., due to a poor reading from the biometric sensor). Providing the text description explaining to the user why the evaluation result was inconclusive improves visual feedback and provides the user with more control of the device by enabling the user to easily understand why the evaluation result and inconclusive (e.g., such that the user can take a new recording that addresses a reason for the inconclusive result). Improving visual feedback to the user and providing additional control of the device (without cluttering the user interface 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.
While displaying the representation (e.g., 1208) of the evaluation of the medical characteristic, the first electronic device (e.g., 1200) detects (1308), via the one or more input devices, a sequence of one or more inputs (e.g., a sequence of one or more touch inputs on a touchscreen of the display (e.g., 1209, 1211, 1213)) to add user-specified symptoms (e.g., 1224) to the evaluation of the medical characteristic. In some embodiments, one or more symptoms are displayed in a list for user selection. Providing one or more symptoms as a list for user selection reduces the number of inputs required from the user to provide the one or more symptoms (e.g., allows the user to not have to type the one or more symptoms). 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 user selects one or more symptoms from the provided list of symptoms.
In some embodiments, while displaying, on the display (e.g. 1202), the representation (e.g., 1208) of the evaluation of the medical characteristic (e.g., a result of the evaluation, data from the evaluation, such as BPM), the first electronic device (e.g., 1200) detects, via a first input device (e.g., 1204), a scrolling input (e.g., 1207). In some embodiments, the first input device is a rotating crown (e.g., 1204) and the scrolling input is a rotation of the rotating crown (e.g., 1207). In some embodiments, the first input device is the touch layer of the display and the scrolling input is a scrolling touch gesture on the display (e.g., 1202). Further in such embodiments, in response to detecting the scrolling input, the first electronic device (e.g., 1200) scrolls a second user interface (e.g., 1206) that includes the representation of the evaluation of the medical characteristic. Additionally in such embodiments, the first electronic device (e.g., 1200) displays, on the display (e.g., 1202), an add-symptoms affordance (e.g., 1216) for adding the user-specified symptoms to the evaluation. Displaying, on the display (e.g., 1202), the add-symptoms affordance for adding the user-specified symptoms to the evaluation provides visual feedback by allowing the user to quickly recognize how to add one or more symptoms to an evaluation result. 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, the user-specified symptoms include a first symptom (e.g., 1226B) corresponding to a serious symptom (e.g., a symptom that may require immediate medical attention), and a first representation of the one or more representations of user-specified symptoms corresponding to the first symptom is displayed with a first visual characteristic (e.g., a warning color, such as yellow). In some embodiments, the user-specified symptoms include a second symptom (e.g., 1226A) corresponding to a non-serious symptom, and a second representation of the one or more representations of user-specified symptoms corresponding to the second symptom is displayed with a second visual characteristic (e.g., a non-warning color, a default color) that is different from the first visual characteristic.
In some embodiments, the evaluation of the medical characteristic is a normal result (no abnormalities detected, e.g., a normal result as discussed above with respect to method 700 and
In some embodiments, while displaying the representation (e.g., 1208) of the evaluation of the medical characteristic, the first electronic device (e.g., 1200) detects, via the one or more input devices (e.g., 1202), a user activation of an information affordance (e.g., 1210). In such embodiments, in response to detecting the user activation of the information affordance, the first electronic device (e.g., 1200) displays, on the display (e.g., 1202), text information (e.g., 1212) related to the evaluation. Displaying, on the display (e.g., 1202), the text information (e.g., 1212) related to the evaluation in response to detecting the user activation of the information affordance provides more control of the device by enabling the user to easily access more information related to the evaluation result. Providing additional control options (without cluttering the user interface 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. In some embodiments, the displayed text information related to the evaluation corresponds to the text information presented for the same type of evaluation during the onboarding process, as described in method 700 (e.g.,
In response to detecting the sequence of one or more inputs (e.g., 1209, 1211, 1213), in accordance with a determination that at least one of the user-specified symptoms meet respective criteria, the first electronic device (e.g., 1200) displays (1310), on the display (e.g., 1202), a first user interface (e.g., a Symptom Alert user interface 1230) that includes an affordance (e.g., 1232) that, when activated, initiates a process for seeking immediate medical attention (e.g., initiating an emergency call, initiating a 911 call). Displaying, on the display (e.g., 1202), the first user interface (e.g., 1230) that includes the affordance that, when activated, initiates the process for seeking immediate medical attention improves user control of the device by enabling the user to quickly and easily recognize that immediate medical attention may be necessary and enables the user to easily and conveniently initiate a process for seeking immediate medical attention. Providing additional control options and 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 response to detecting the sequence of one or more inputs (e.g., 1209, 1211, 1213), in accordance with a determination that (all of) the user-specified symptoms do not meet the respective criteria, the first electronic device (e.g., 1200) displays (1312), on the display (e.g., 1202), the representation of the evaluation of the medical characteristic and one or more representations of user-specified symptoms without displaying the first user interface (e.g., without displaying interface 1230). Displaying, on the display (e.g., 1202), the representation of the evaluation of the medical characteristic and the one or more representations of the user-specified symptoms without displaying the first user interface (e.g., 1230) improves visual feedback by enabling the user to easily view the evaluation and the user-specified symptoms upon user selection of the symptoms. 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, further in accordance with a determination that (all of) the user-specified symptoms do not meet the respective criteria, the first electronic device (e.g., 1200) detects (1312), via the one or more input devices (e.g., 1204), a scrolling gesture (e.g., a rotation of a rotating crow (e.g., 1219), a scrolling input on the touch layer of the display). In some embodiments, in response to detecting, via the one or more input devices, the scrolling gesture, the first electronic device (e.g., 1200) displays (1314), on the display (e.g., 1202), an option for seeking medical attention (e.g., a selectable text allowing the user to initiate a process for contacting 911 (e.g., 1240)). Displaying, on the display (e.g., 1202), the option for seeking medical attention in response to detecting the scrolling gesture improves user control of the device by providing the user with a quick and easy method for seeking medical attention, if the user determines that medical attention is needed. Providing additional control options (without cluttering the user interface 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.
In some embodiments, subsequent to detecting the sequence of one or more inputs (e.g., 1209, 1211, 1213), the first electronic device (e.g., 1200) detects (1316) a user activation (e.g., 1221) of a confirmation button (e.g., 1242). In such embodiments, in response to (or subsequent to) detecting the user activation of the confirmation button, the first electronic device (e.g., 1200) transmits (1318) (e.g., via a wireless communication radio of the device) the evaluation of the medical characteristic from the first electronic device (e.g., 1200) to a second electronic device (e.g., 100, 300, 500, 600A), a smartphone that is paired with the first electronic device) for display of a corresponding representation of the evaluation of the medical characteristic on the second electronic device.
In some embodiments, the user-specified symptoms (e.g., 1226A, 1226B) cannot be modified after detecting the user activation of the confirmation button.
Note that details of the processes described above with respect to method 1300 (e.g.,
In some embodiments, first page 1410 of the setup process includes a date of birth entry field 1410C for receiving a user input corresponding to the user's date of birth, where the user's date of birth is used to determine whether the user meets a minimum age requirement (e.g., 22 years of age) to use the Atrial Fibrillation-detection management features. In some embodiments, date of birth entry field 1410C indicates (e.g., by stating “Required”) that the user's date of birth must be entered in order to proceed with the setup process. In some embodiments, date of birth entry field 1410C includes scrollable month, day, and year fields.
In some embodiments, first page 1410 of the setup process does not include date of birth entry field 1410C. In some embodiments, first page 1410 of the setup process includes (e.g., in addition to or alternatively to date of birth entry field 1410C) an age restriction message (e.g., stating “You must be 22 years or older”) indicating to the user that the user must meet the minimum age requirement.
In some embodiments, first page 1410 of the setup process includes an affordance 1410D for proceeding with the tutorial. In
In some embodiments, in accordance with a determination that the minimum age requirement is not met (e.g., a determination made in response to detecting user activation 1401), first electronic device 1400A displays, on display 1402, an error notification (e.g., stating “The Atrial Fibrillation-detection management features are not intended for use by people under 22”) indicating that the user does not meet the requisite minimum age requirement. In some embodiments, the error notification is overlaid on first page 1410 of the setup process. In some embodiments, while displaying the error notification, the background of the display (displaying first page 1410) is dimmed (thereby emphasizing the displayed error notification).
In some embodiments, in response to detecting user activation 1401 (and in accordance with a determination that the minimum age requirement is met), first electronic device 1400A displays, on display 1402 (e.g., replaces display of first page 1410 with), a second page 1412 of the setup process, as shown in
In
In some embodiments, third page 1414 of the setup process indicates to the user (e.g., via a text description) one or more limitations of Atrial-Fibrillation evaluation results that are determined from heart-related information captured using the second electronic device (e.g., second electronic device 1400B) (e.g., using a biometric sensor of the second electronic device comprising one or more photodiode sensors). In some examples, third page 1414 of the setup process includes a list 1414A of one or more functional characteristics of the Atrial Fibrillation-detection features and/or medical characteristics that cannot be determined from the captured heart-related information (e.g., heart attack, blood clots/stroke). In some embodiments, third page 1414 of the setup process includes (e.g., at the bottom of the page), an affordance 1414B for proceeding with the tutorial.
In
In some embodiments, fourth page 1416 of the setup process includes a notification activation affordance 1416C (e.g., showing “Turn on AFib Notifications”) for enabling notifications on first electronic device 1400A and/or second electronic device 1400B when Atrial Fibrillation is determined (using heart-related information captured using the second electronic device). In some embodiments, while displaying fourth page 1416 of the setup process, first electronic device 1400A detects (e.g., via a touch input) a user activation 1407 of notification activation affordance 1416C. In some embodiments, in response to detecting user activation 1407, first electronic device 1400A activates notifications to be displayed on first electronic device 1400A and/or second electronic device 1400B when Atrial Fibrillation is determined.
In some embodiments, heart data user interface 1418 of the health application includes a heart rate affordance 1420. In some embodiments, heart rate affordance 1420 includes an indication of a range of the user's heart rate measured (e.g., via second electronic device 1400B) during a certain period of time (e.g., today). In some embodiments, in response to detecting a user selection on heart rate affordance 1420, heart data user interface 1418 displays a graphical depiction of the heart rate information summarized by heart rate affordance 1420 within a graphical depiction region 1422 of the user interface (and further highlights the affordance with a particular visual characteristic, such as a different color, to indicate to the user that the heart rate affordance is currently selected by the user).
In some embodiments, heart data user interface 1418 of the health application includes an Atrial Fibrillation affordance 1424. In some embodiments, Atrial Fibrillation affordance 1424 includes an indication of the number of heart-related readings taken during a certain period of time (e.g., “Today (4 Readings)”) by the second electronic device (e.g., second electronic device 1400B) (e.g., using a biometric sensor comprising one or more photodiode sensors of the second electronic device). In some embodiments, Atrial Fibrillation affordance 1424 includes an information affordance 1424A for viewing and managing information about existing heart-related recordings taken by the second electronic device (e.g., using a biometric sensor comprising one or more photodiode sensors) to detect Atrial Fibrillation.
In
In some embodiments, Atrial Fibrillation management user interface 1426 includes a recent analysis indication 1426B indicating the time(s) of one or more most recent measurements of heart-related information made by the second electronic device (e.g., second electronic device 1400B) (e.g., using a biometric sensor comprising one or more photodiode sensors of the second electronic device). In some embodiments, the one or more recent measurements shown in recent analysis indication 1426B only include heart-related information captured after an Atrial Fibrillation alert has been presented (if any) by first electronic device 1400A and/or second electronic device 1400B.
In some embodiments, Atrial Fibrillation management user interface 1426 includes a show all affordance 1426C for viewing a record of all past measurements of heart-related information using the second electronic device (e.g., second electronic device 1400B) (e.g., using a biometric sensor comprising one or more photodiode sensors of the second electronic device).
In some embodiments, Atrial Fibrillation management user interface 1426 includes an indication 1426D (e.g., a brief textual description) of how Atrial Fibrillation is detected by the second electronic device (e.g., second electronic device 1400B). In some embodiments, Atrial Fibrillation management user interface 1426 includes a learn more affordance 1426E for viewing additional information (e.g., expounding upon the description shown in indication 1426D) about the Atrial Fibrillation-detection features.
In some embodiments, Atrial Fibrillation management user interface 1426 includes a disable notifications affordance 1426F for disabling notifications from being presented (on first electronic device 1400A and/or second electronic device 1400B) when Atrial Fibrillation is detected.
In some embodiments, an alert log (e.g., first alert log 1428A and second alert log 1428B) includes a time at which the alert was generated. In some embodiments, in response to detecting a user activation of an alert log, first electronic device 1400A displays, on display 1402, a detailed alert log page that includes more detailed information about the captured heart-related information corresponding to the alert log (e.g., heart rate information, separate non-contiguous number of times during which the heart-related information was captured).
In some embodiments, Atrial Fibrillation alert 1434 includes an indication 1434A (e.g., a textual description) describing the reason for the alert (e.g., a detection of Atrial Fibrillation) and an explanation of the medical condition (e.g., Atrial Fibrillation) associated with the alert. In some embodiments, Atrial Fibrillation alert 1434 includes an indication 1434B listing the one or more times (corresponding to measurements of heart-related information taken by second electronic device 1400B (e.g., using a biometric sensor comprising one or more photodiode sensors)) during which Atrial Fibrillation was detected by the device. In some embodiments, indication 1434B includes (not shown in
In some embodiments, Atrial Fibrillation alert 1434 includes an ECG affordance 1436 for taking more detailed heart-related information using an ECG application of second electronic device 1400B (e.g., corresponding to the ECG application discussed above with respect to
As described below, method 1500 provides an intuitive way for providing a health condition alert. The method reduces the cognitive burden on a user for managing a health condition, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a user to manage health monitoring faster and more efficiently conserves power and increases the time between battery charges.
The electronic device (e.g., 1400B) receives (1502) (e.g., via an internal connection from an integrated sensor of the electronic device (e.g., 1400), via a wireless connection from a discrete sensor) first biometric information from a first biometric sensor of the plurality of biometric sensors. In some embodiments, the first biometric sensor comprises one or more photodiode sensors (e.g., enclosed in a housing of the electronic device). In some embodiments, the first biometric information comprises biometric information recorded at a first time and biometric information recorded at a second time different from (e.g., spaced apart from, non-contiguous with) the first time (e.g., a common time on a different day of the week).
In response to receiving the first biometric information and in accordance with a determination that the first biometric information satisfies first criteria (e.g., because the first biometric information includes heart rate or rhythm information that is abnormal and, optionally, because during a predetermined period of time (e.g., 48 hours), the electronic device (e.g., 1400B) has detected a threshold number of readings (e.g., five readings) having indications of irregular heart rate or rhythm), the electronic device (e.g., 1400B) displays (1504), on the display (e.g., 1430), an alert (e.g., 1434) including a first affordance (e.g., 1436) for detecting additional biometric information (e.g., using an ECG application on the electronic device). Displaying an alert that includes a first affordance for detecting additional biometric information in response to receiving the first biometric information and in accordance with a determination that the first biometric information satisfies first criteria improves visual feedback by quickly (and in an easily-recognizable method) indicating to the user that an action (e.g., measuring additional biometric information) can be taken on the device. 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, the biometric information relates to heart-related information. In some embodiments, the first criteria comprises abnormal heart rhythm information.
In some embodiments, the alert (e.g., 1434) includes one or more times (e.g., 1434B) during which the first biometric information was recorded by the electronic device. In some embodiments, the alert includes an indication (e.g., 1434A, a text description) of a medical condition (e.g., abnormal heart rhythm, Atrial Fibrillation) identified based on the first biometric information. In some embodiments, the alert includes an indication (e.g., 1434C, a text description) to seek medical attention. Including an indication to seek medical attention enhances the operability of the device by quickly and efficiently indicating to the user an action relating to information provided by the device can be taken. Enhancing the operability of the device 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 (e.g., 1400B) receives (1506), via the one or more input devices, user activation of the first affordance (e.g., 1436).
Subsequent to receiving the user activation of the first affordance (e.g., 1436), the electronic device (e.g., 1400B) receives (1512) (e.g., using the ECG application) second biometric information (e.g., more detailed heart rhythm information, ECG information) associated with the first biometric information from (at least) a second biometric sensor (e.g., a biometric sensor integrated with an input device (e.g., 636, 804, 1004, 1204, such as a rotatable input device) of the plurality of biometric sensors that is different from the first biometric sensor. In some embodiments, the second biometric sensor is integrated with a first input device (e.g., 636, 804, 1004, 1204, a rotatable and depressible input device) of the one or more input devices. In some embodiments, a first type of input on the first input device (e.g., 629, 801, 1005, such as a non-press input or a contact input, activates a feature(s) associated with activation of the second biometric sensor but does not activate a feature(s) associated with activation of the first input device.
In some embodiments, in response to receiving the user activation of the first affordance (e.g., 1436) and prior to receiving the second biometric information, the electronic device (e.g., 1400B) displays (1508), on the display (e.g., 1430), a first application (e.g., 806, 1006, an ECG application) associated with receiving the second biometric information. Displaying the first application associated with receiving the second biometric information in response to receiving the user activation of the first affordance and prior to receiving the second biometric information improves visual feedback by enabling the user to quickly and easily recognize that the second biometric information to be captured relates to features of the first application. 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, subsequent to displaying the first application (e.g., 806, 1006, an ECG application) and prior to receiving the second biometric information, the electronic device (e.g., 1400B) detects (1510) a user input (e.g., 629, 801, 1005, a non-press input, a contact input) on a first input device (e.g., 636, 804, 1004, 1204, a rotatable and depressible input device) of the one or more input devices, where the second biometric sensor is integrated with the first input device. In some embodiments, in response to detecting the user input, the electronic device receives the second biometric information from the second biometric sensor.
In some embodiments, the second biometric information is received from the second biometric sensor while the user input (e.g., 629, 801, 1005, a non-press input, a contact input) is maintained on the first input device (e.g., 636, 804, 1004, 1204, a rotatable and depressible input device). In some embodiments, in response to detecting that the user input is no longer maintained on the first input device, the electronic device (e.g., 1400B) ceases receiving the second biometric information from the second biometric sensor. In some embodiments, if the user input is restored within a predetermined period of time, the electronic device resumes receiving the second biometric information from the second biometric sensor.
Note that details of the processes described above with respect to method 1500 (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 available from various sources to improve the delivery to users of invitational content or any other content that may be of interest to them. 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, home addresses, or any other identifying 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 deliver targeted content that is of greater interest to the user. Accordingly, use of such personal information data enables calculated control of the delivered content. Further, other uses for personal information data that benefit the user are also contemplated by the present disclosure.
The present disclosure further 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. For example, 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 should occur only after receiving the informed consent of the users. Additionally, such entities would take 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.
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 advertisement delivery services, 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. In another example, users can select not to provide location information for targeted content delivery services. In yet another example, users can select to not provide precise location information, but permit the transfer of location zone information.
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, content 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 information available to the content delivery services, or publically available information.
This application is a continuation of U.S. patent application Ser. No. 16/144,030, entitled “USER INTERFACES FOR HEALTH MONITORING,” filed Sep. 27, 2018, which claims priority to: U.S. Provisional Patent Application Ser. No. 62/657,881, entitled “USER INTERFACES FOR HEALTH MONITORING,” filed Apr. 15, 2018; U.S. Provisional Patent Application Ser. No. 62/657,870, entitled “USER INTERFACES FOR HEALTH MONITORING,” filed Apr. 15, 2018; U.S. Provisional Patent Application Ser. No. 62/643,699, entitled “USER INTERFACES FOR HEALTH MONITORING,” filed Mar. 15, 2018; and U.S. Provisional Patent Application Ser. No. 62/641,994, entitled “USER INTERFACES FOR HEALTH MONITORING,” filed Mar. 12, 2018. The contents of each of these applications are hereby incorporated by reference in their entireties. This application relates to U.S. Provisional Patent Application Ser. No. 62/554,196, entitled “WEARABLE DEVICE WITH ELECTRODES FOR SENSING BIOLOGICAL PARAMETERS,” filed Sep. 5, 2017, the contents of which are hereby incorporated by reference in their entirety and are also included in their entirety as Appendix A.
Number | Name | Date | Kind |
---|---|---|---|
4205628 | Null | Jun 1980 | A |
4842266 | Sweeney et al. | Jun 1989 | A |
5423863 | Felblinger et al. | Jun 1995 | A |
5458548 | Crossing et al. | Oct 1995 | A |
5474077 | Suga | Dec 1995 | A |
5515344 | Ng | May 1996 | A |
5642731 | Kehr | Jul 1997 | A |
5788655 | Yoshimura et al. | Aug 1998 | A |
6013008 | Fukushima | Jan 2000 | A |
6095949 | Arai | Aug 2000 | A |
6095984 | Amano et al. | Aug 2000 | A |
6097371 | Siddiqui et al. | Aug 2000 | A |
6097385 | Robinson | Aug 2000 | A |
6244988 | Delman | Jun 2001 | B1 |
6302789 | Harada et al. | Oct 2001 | B2 |
6416471 | Kumar et al. | Jul 2002 | B1 |
6600696 | Lynn | Jul 2003 | B1 |
6603477 | Tittle | Aug 2003 | B1 |
6639584 | Li | Oct 2003 | B1 |
6705972 | Takano et al. | Mar 2004 | B1 |
6837827 | Lee | Jan 2005 | B1 |
6866613 | Brown et al. | Mar 2005 | B1 |
6950839 | Green et al. | Sep 2005 | B1 |
7020514 | Wiesel | Mar 2006 | B1 |
7111157 | Hooper | Sep 2006 | B1 |
7128693 | Brown et al. | Oct 2006 | B2 |
7166078 | Saini et al. | Jan 2007 | B2 |
7251454 | White | Jul 2007 | B2 |
7302272 | Ackley | Nov 2007 | B2 |
7313435 | Nakada et al. | Dec 2007 | B2 |
7662065 | Kahn et al. | Feb 2010 | B1 |
7695406 | Waters | Apr 2010 | B2 |
7739148 | Suzuki et al. | Jun 2010 | B2 |
7771320 | Riley et al. | Aug 2010 | B2 |
8060229 | Gupta et al. | Nov 2011 | B2 |
8105208 | Oleson et al. | Jan 2012 | B2 |
8152694 | Srinivasan et al. | Apr 2012 | B2 |
8200323 | Dibenedetto et al. | Jun 2012 | B2 |
8321006 | Snyder et al. | Nov 2012 | B1 |
8341557 | Pisula et al. | Dec 2012 | B2 |
8475339 | Hwang et al. | Jul 2013 | B2 |
8496563 | Komatsu 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 |
8825445 | Hoffman et al. | Sep 2014 | B2 |
8888707 | Shirasaki et al. | Nov 2014 | B2 |
8934963 | Farazi | Jan 2015 | B1 |
8990006 | Wallace et al. | Mar 2015 | B1 |
9011292 | Weast et al. | Apr 2015 | B2 |
9020538 | White et al. | Apr 2015 | B1 |
9026927 | Brumback et al. | May 2015 | B2 |
9224291 | Moll-carrillo et al. | Dec 2015 | B2 |
9230076 | King et al. | Jan 2016 | B2 |
9490763 | Taniguchi et al. | Nov 2016 | B2 |
9557881 | Jain et al. | Jan 2017 | B1 |
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 |
9854653 | Ackmann et al. | Dec 2017 | B1 |
9940682 | Hoffman et al. | Apr 2018 | B2 |
10004451 | Proud | Jun 2018 | B1 |
10056006 | Hsu-hoffman et al. | Aug 2018 | B1 |
10150002 | Kass et al. | Dec 2018 | B2 |
10175781 | Karagozler et al. | Jan 2019 | B2 |
10220258 | Gu et al. | Mar 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 |
10398381 | Heneghan et al. | Sep 2019 | B1 |
10437962 | Soni et al. | Oct 2019 | B2 |
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 |
10736543 | Chen et al. | Aug 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 |
11107569 | Devoto | Aug 2021 | B1 |
11107580 | Felton et al. | Aug 2021 | B1 |
11209957 | Dryer et al. | Dec 2021 | B2 |
20010049470 | Mault et al. | Dec 2001 | A1 |
20020045960 | Phillips et al. | Apr 2002 | A1 |
20020086774 | Warner | Jul 2002 | A1 |
20020095292 | Mittal et al. | Jul 2002 | A1 |
20020118121 | Lehrman et al. | Aug 2002 | A1 |
20030023178 | Bischoff et al. | Jan 2003 | A1 |
20030064860 | Yamashita et al. | Apr 2003 | A1 |
20030134714 | Oishi et al. | Jul 2003 | A1 |
20030179229 | Van et al. | Sep 2003 | 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 |
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 |
20050113650 | Pacione et al. | May 2005 | A1 |
20050124324 | Thomas et al. | Jun 2005 | A1 |
20050149362 | Peterson et al. | Jul 2005 | A1 |
20050165627 | Fotsch et al. | Jul 2005 | A1 |
20050228735 | Duquette | Oct 2005 | A1 |
20050244013 | Battenberg et al. | Nov 2005 | A1 |
20050272564 | Pyles et al. | Dec 2005 | A1 |
20060052727 | Palestrant | Mar 2006 | 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 |
20060160090 | Macina et al. | Jul 2006 | A1 |
20060182287 | Schulein et al. | Aug 2006 | A1 |
20060184800 | Rosenberg | Aug 2006 | A1 |
20060195039 | Panken et al. | Aug 2006 | A1 |
20060205564 | Peterson | Sep 2006 | A1 |
20060235319 | Belohlavek et al. | Oct 2006 | A1 |
20060240959 | Huang | Oct 2006 | A1 |
20060250524 | Roche | Nov 2006 | A1 |
20060274908 | Choi | Dec 2006 | A1 |
20070016440 | Stroup | Jan 2007 | A1 |
20070032733 | Burton | Feb 2007 | A1 |
20070033069 | Rao et al. | Feb 2007 | A1 |
20070056727 | Newman | Mar 2007 | A1 |
20070071256 | Ito | Mar 2007 | A1 |
20070143433 | Daigle | Jun 2007 | A1 |
20070169614 | Sasaki et al. | Jul 2007 | A1 |
20070179434 | Weinert et al. | Aug 2007 | A1 |
20070249949 | Hadley | Oct 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 |
20080020803 | Rios et al. | Jan 2008 | A1 |
20080027673 | Trumm | Jan 2008 | A1 |
20080051919 | Sakai et al. | Feb 2008 | A1 |
20080052945 | Matas et al. | Mar 2008 | A1 |
20080058626 | Miyata et al. | Mar 2008 | A1 |
20080077073 | Keenan et al. | Mar 2008 | A1 |
20080082145 | Skwarek et al. | Apr 2008 | A1 |
20080096726 | Riley et al. | Apr 2008 | A1 |
20080133742 | Southiere et al. | Jun 2008 | A1 |
20080146892 | Leboeuf et al. | Jun 2008 | A1 |
20080159547 | Schuler et al. | Jul 2008 | A1 |
20080161161 | Pipinich et al. | Jul 2008 | A1 |
20080161707 | Farringdon et al. | Jul 2008 | A1 |
20080200312 | Tagliabue | Aug 2008 | A1 |
20080205660 | Goldstein | Aug 2008 | A1 |
20080228045 | Gao et al. | Sep 2008 | A1 |
20080229226 | Rowbottom et al. | Sep 2008 | A1 |
20080240519 | Nagamitsu | Oct 2008 | A1 |
20080254767 | Jin | Oct 2008 | A1 |
20080300110 | Smith et al. | Dec 2008 | A1 |
20090007017 | Anzures et al. | Jan 2009 | A1 |
20090007596 | Goldstein et al. | Jan 2009 | A1 |
20090012988 | Brown | Jan 2009 | A1 |
20090052677 | Smith | Feb 2009 | A1 |
20090065578 | Peterson et al. | Mar 2009 | A1 |
20090118100 | Oliver et al. | May 2009 | A1 |
20090170532 | Lee et al. | Jul 2009 | A1 |
20090180631 | Michael et al. | Jul 2009 | A1 |
20090210078 | Crowley | Aug 2009 | A1 |
20090216556 | Martin et al. | Aug 2009 | A1 |
20090222056 | Lindh et al. | Sep 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 |
20100017489 | Birnbaum et al. | Jan 2010 | A1 |
20100027807 | Jeon | Feb 2010 | A1 |
20100046767 | Bayley et al. | Feb 2010 | A1 |
20100060586 | Pisula et al. | Mar 2010 | A1 |
20100062905 | Rottler et al. | Mar 2010 | A1 |
20100064255 | 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 |
20100125306 | Mccabe et al. | May 2010 | A1 |
20100137106 | Oshima et al. | Jun 2010 | A1 |
20100145209 | Lee et al. | Jun 2010 | A1 |
20100145220 | Van | Jun 2010 | A1 |
20100150378 | Lee et al. | Jun 2010 | A1 |
20100222645 | Nadler et al. | Sep 2010 | A1 |
20100264097 | Sun et al. | Oct 2010 | A1 |
20100292600 | Dibenedetto et al. | Nov 2010 | A1 |
20100298899 | Donnelly et al. | Nov 2010 | A1 |
20100312138 | Regas | Dec 2010 | A1 |
20110032105 | Hoffman et al. | Feb 2011 | A1 |
20110057799 | Taneff | Mar 2011 | A1 |
20110066051 | Moon et al. | Mar 2011 | A1 |
20110071765 | Yodfat et al. | Mar 2011 | A1 |
20110071869 | Obrien et al. | Mar 2011 | A1 |
20110093481 | Hussam | Apr 2011 | A1 |
20110098928 | Hoffman et al. | Apr 2011 | A1 |
20110106553 | Tanaka et al. | May 2011 | A1 |
20110112418 | Feild et al. | May 2011 | A1 |
20110125041 | Fischell et al. | May 2011 | A1 |
20110137678 | Williams | Jun 2011 | A1 |
20110152656 | Weinert et al. | Jun 2011 | A1 |
20110159469 | Hwang et al. | Jun 2011 | A1 |
20110166631 | Breining | Jul 2011 | A1 |
20110167369 | Van | Jul 2011 | A1 |
20110195383 | Weiss | Aug 2011 | A1 |
20110214162 | Brakensiek et al. | Sep 2011 | A1 |
20110218407 | Haberman et al. | Sep 2011 | A1 |
20110230169 | Ohki | Sep 2011 | A1 |
20110245623 | Chutani et al. | Oct 2011 | A1 |
20110261079 | Ingrassia et al. | Oct 2011 | A1 |
20110275940 | Nims et al. | Nov 2011 | A1 |
20110306389 | Nagayama | Dec 2011 | A1 |
20110307821 | Martens | Dec 2011 | A1 |
20120002510 | Berman, Jr. | Jan 2012 | A1 |
20120015778 | Lee et al. | Jan 2012 | A1 |
20120015779 | Powch et al. | Jan 2012 | A1 |
20120029303 | Shaya | Feb 2012 | A1 |
20120034897 | Kreitzer et al. | Feb 2012 | A1 |
20120038651 | Case et al. | Feb 2012 | A1 |
20120041767 | Hoffman et al. | Feb 2012 | A1 |
20120042039 | Mark | Feb 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 |
20120150759 | Tarjan | Jun 2012 | A1 |
20120159380 | Kocienda et al. | Jun 2012 | A1 |
20120179319 | Gilman et al. | Jul 2012 | A1 |
20120203124 | Lim | Aug 2012 | A1 |
20120215115 | Takahashi | Aug 2012 | A1 |
20120232414 | Mollicone et al. | Sep 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 |
20120290109 | Engelberg et al. | Nov 2012 | A1 |
20120302843 | Otsubo 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 |
20130011819 | Horseman | Jan 2013 | A1 |
20130012788 | Horseman | Jan 2013 | A1 |
20130013331 | Horseman | Jan 2013 | A1 |
20130033376 | Seyed et al. | Feb 2013 | A1 |
20130054150 | Sacks et al. | Feb 2013 | A1 |
20130054720 | Kang et al. | Feb 2013 | A1 |
20130065569 | Leipzig et al. | Mar 2013 | A1 |
20130067050 | Kotteri 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 |
20130138734 | Crivello et al. | May 2013 | A1 |
20130144653 | Poe et al. | Jun 2013 | A1 |
20130151285 | Mclaren et al. | Jun 2013 | A1 |
20130158367 | Pacione et al. | Jun 2013 | A1 |
20130158416 | Hatlestad et al. | Jun 2013 | A1 |
20130185097 | Saria et al. | Jul 2013 | A1 |
20130197679 | Balakrishnan et al. | Aug 2013 | A1 |
20130202121 | Georgiou et al. | Aug 2013 | A1 |
20130215042 | Messerschmidt et al. | Aug 2013 | A1 |
20130215119 | Vanhoecke | Aug 2013 | A1 |
20130231575 | Erkkila et al. | Sep 2013 | A1 |
20130231711 | Kaib | Sep 2013 | A1 |
20130231947 | Shusterman | Sep 2013 | A1 |
20130263719 | Watterson et al. | Oct 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 |
20130324210 | Doig et al. | Dec 2013 | A1 |
20130325358 | Oshima et al. | Dec 2013 | A1 |
20130325396 | Yuen et al. | Dec 2013 | A1 |
20130330694 | Watterson | 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 |
20140039840 | Yuen et al. | Feb 2014 | A1 |
20140073486 | Ahmed et al. | Mar 2014 | A1 |
20140081118 | Reinhold et al. | Mar 2014 | A1 |
20140088995 | Damani | Mar 2014 | A1 |
20140089836 | Damani et al. | Mar 2014 | A1 |
20140108998 | Chaudhri et al. | Apr 2014 | A1 |
20140127996 | Park et al. | May 2014 | A1 |
20140129007 | Utter | May 2014 | A1 |
20140129243 | Utter, II | 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 |
20140180786 | Sullivan | 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 |
20140200691 | Lee et al. | Jul 2014 | A1 |
20140240122 | Roberts et al. | Aug 2014 | A1 |
20140240349 | Tuukkanen | Aug 2014 | A1 |
20140266776 | Miller et al. | Sep 2014 | A1 |
20140274413 | Chelst | Sep 2014 | A1 |
20140275852 | Hong et al. | Sep 2014 | A1 |
20140275854 | Venkatraman 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 |
20140310598 | Sprague et al. | Oct 2014 | A1 |
20140310643 | Karmanenko et al. | Oct 2014 | A1 |
20140327527 | Goldstein et al. | Nov 2014 | A1 |
20140331314 | Fujioka | Nov 2014 | A1 |
20140336796 | Agnew | Nov 2014 | A1 |
20140337041 | Madden et al. | Nov 2014 | A1 |
20140344687 | Durham et al. | Nov 2014 | A1 |
20140354494 | Katz | Dec 2014 | A1 |
20140358012 | Richards et al. | Dec 2014 | A1 |
20140358473 | Goel et al. | Dec 2014 | A1 |
20140358584 | Worden et al. | Dec 2014 | A1 |
20140371887 | Hoffman et al. | Dec 2014 | A1 |
20150004578 | Gilley et al. | Jan 2015 | A1 |
20150018632 | Khair | Jan 2015 | A1 |
20150046814 | Haughay et al. | Feb 2015 | A1 |
20150057942 | Self et al. | Feb 2015 | A1 |
20150058263 | Landers | Feb 2015 | A1 |
20150065095 | Seo et al. | Mar 2015 | A1 |
20150067513 | Zambetti et al. | Mar 2015 | A1 |
20150073285 | Albert et al. | Mar 2015 | A1 |
20150081060 | Hwang et al. | Mar 2015 | A1 |
20150081210 | Yeh et al. | Mar 2015 | A1 |
20150081529 | Lee 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 |
20150113553 | Pan | 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 |
20150130830 | Nagasaki 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 |
20150180746 | Day 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 |
20150205930 | Shaanan 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 |
20150251053 | Hoffman et al. | Sep 2015 | A1 |
20150261918 | Thornbury, Jr. | Sep 2015 | A1 |
20150262499 | Wicka et al. | Sep 2015 | A1 |
20150269848 | Yuen 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 |
20150343709 | Gerstle et al. | Dec 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 |
20150351655 | Coleman | Dec 2015 | A1 |
20150374310 | Lee | Dec 2015 | A1 |
20160000379 | Pougatchev et al. | Jan 2016 | A1 |
20160004432 | Bernstein et al. | Jan 2016 | A1 |
20160015275 | Samadani et al. | Jan 2016 | A1 |
20160019360 | Pahwa et al. | Jan 2016 | A1 |
20160027282 | Lee | 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 |
20160062582 | Wilson et al. | Mar 2016 | A1 |
20160063215 | Zamer | Mar 2016 | A1 |
20160066842 | Kokkoneva et al. | Mar 2016 | A1 |
20160070275 | Anderson et al. | Mar 2016 | A1 |
20160072896 | Petersen et al. | Mar 2016 | A1 |
20160085937 | Dettinger et al. | Mar 2016 | A1 |
20160086500 | Kaleal, III | Mar 2016 | A1 |
20160098522 | Weinstein | Apr 2016 | A1 |
20160103985 | Shim et al. | Apr 2016 | A1 |
20160106398 | Kuppuswami | Apr 2016 | A1 |
20160107031 | Palatsi et al. | Apr 2016 | A1 |
20160109961 | Parshionikar | Apr 2016 | A1 |
20160132046 | Beoughter et al. | May 2016 | A1 |
20160135719 | Von Kraus et al. | May 2016 | A1 |
20160135731 | Drennan | May 2016 | A1 |
20160140828 | Deforest | May 2016 | A1 |
20160150978 | Yuen et al. | Jun 2016 | A1 |
20160156584 | Hum 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 |
20160220225 | Wang et al. | Aug 2016 | A1 |
20160235325 | Chou | Aug 2016 | A1 |
20160235374 | Miller et al. | Aug 2016 | A1 |
20160246880 | Battiah et al. | Aug 2016 | A1 |
20160249857 | Choi et al. | Sep 2016 | A1 |
20160249864 | Kang et al. | Sep 2016 | A1 |
20160250517 | Tilvis et al. | Sep 2016 | A1 |
20160256082 | Ely et al. | Sep 2016 | A1 |
20160256741 | Holma 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 |
20160278659 | Kaib et al. | Sep 2016 | A1 |
20160278667 | Villard et al. | Sep 2016 | A1 |
20160279475 | Aragones et al. | Sep 2016 | A1 |
20160285985 | Molettiere et al. | Sep 2016 | A1 |
20160287177 | Huppert et al. | Oct 2016 | A1 |
20160292373 | Spors et al. | 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 |
20160302717 | Tawa et al. | 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 |
20160328736 | Wang et al. | 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 |
20160371464 | Bricker | Dec 2016 | A1 |
20160375306 | Gu et al. | Dec 2016 | A1 |
20170000348 | Karsten et al. | Jan 2017 | A1 |
20170000359 | Kohli et al. | Jan 2017 | A1 |
20170001073 | Krueger et al. | Jan 2017 | A1 |
20170007159 | Dieffenderfer et al. | Jan 2017 | A1 |
20170007167 | Kostic et al. | Jan 2017 | A1 |
20170014037 | Coppola et al. | Jan 2017 | A1 |
20170021184 | Pavel et al. | Jan 2017 | A1 |
20170024399 | Boyle et al. | Jan 2017 | A1 |
20170024539 | Webb 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 |
20170065224 | Rahko et al. | Mar 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 |
20170095695 | Mangusson et al. | Apr 2017 | A1 |
20170127997 | Hyde et al. | May 2017 | A1 |
20170132395 | Futch | May 2017 | A1 |
20170136297 | Penie | May 2017 | A1 |
20170143262 | Kurunmäki et al. | 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 | Kumniawan 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 |
20170235443 | Suzuki | Aug 2017 | A1 |
20170237694 | Choudhary et al. | Aug 2017 | A1 |
20170239524 | Lee et al. | Aug 2017 | A1 |
20170243508 | Cheng et al. | Aug 2017 | A1 |
20170258455 | Qi | Sep 2017 | A1 |
20170266494 | Crankson et al. | Sep 2017 | A1 |
20170269792 | Xu et al. | Sep 2017 | A1 |
20170274149 | Aeschlimann | Sep 2017 | A1 |
20170274267 | Blahnik | Sep 2017 | A1 |
20170281026 | Nick et al. | Oct 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 |
20170301039 | Dyer et al. | Oct 2017 | A1 |
20170303844 | Baker et al. | Oct 2017 | A1 |
20170319184 | Sano | Nov 2017 | A1 |
20170319941 | Smith et al. | Nov 2017 | A1 |
20170329933 | Brust et al. | Nov 2017 | A1 |
20170330297 | Cronin et al. | Nov 2017 | A1 |
20170332980 | Fifield et al. | Nov 2017 | A1 |
20170337033 | Duyan 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 |
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 |
20180053200 | Cronin 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 |
20180078182 | Chen et al. | Mar 2018 | A1 |
20180081918 | Gravenites et al. | Mar 2018 | A1 |
20180096739 | Sano | Apr 2018 | A1 |
20180107962 | Lundin et al. | Apr 2018 | A1 |
20180117414 | Miyasaka et al. | May 2018 | A1 |
20180120985 | Wallace et al. | May 2018 | A1 |
20180122214 | Freedman 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 |
20180140903 | Poure 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 |
20180206766 | Blahnik 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 |
20180272190 | Miura et al. | Sep 2018 | A1 |
20180279885 | Bulut | Oct 2018 | A1 |
20180294053 | Runyon et al. | Oct 2018 | A1 |
20180318647 | Foley et al. | Nov 2018 | A1 |
20180329584 | Williams et al. | Nov 2018 | A1 |
20180336530 | Johnson et al. | Nov 2018 | A1 |
20180339195 | Bernotas | Nov 2018 | A1 |
20180345078 | Blahnik et al. | Dec 2018 | A1 |
20180350451 | Ohnemus et al. | Dec 2018 | A1 |
20180368814 | R. Kudtarkar | Dec 2018 | A1 |
20180376107 | Shibaev et al. | Dec 2018 | A1 |
20190008467 | Averina et al. | Jan 2019 | A1 |
20190012898 | Wittrup | Jan 2019 | A1 |
20190014205 | Miloseski et al. | Jan 2019 | A1 |
20190018588 | Debates et al. | Jan 2019 | A1 |
20190025995 | Williams | Jan 2019 | A1 |
20190034049 | Williams 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 |
20190089701 | Mercury 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 |
20190184234 | Packles et al. | Jun 2019 | A1 |
20190192086 | Menon et al. | Jun 2019 | A1 |
20190206538 | Xing et al. | Jul 2019 | A1 |
20190209777 | O'connell et al. | Jul 2019 | A1 |
20190223843 | Vitti | Jul 2019 | A1 |
20190228179 | Rakshit et al. | Jul 2019 | A1 |
20190228640 | Freedman et al. | Jul 2019 | A1 |
20190232111 | Williams et al. | Aug 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 |
20190279520 | Wilson et al. | Sep 2019 | A1 |
20190298230 | Nicholson et al. | Oct 2019 | A1 |
20190302995 | Robinson et al. | Oct 2019 | A1 |
20190333614 | Burger et al. | Oct 2019 | A1 |
20190336044 | Williams et al. | Nov 2019 | A1 |
20190336045 | Williams et al. | Nov 2019 | A1 |
20190336827 | Intonato et al. | Nov 2019 | A1 |
20190339849 | Williams et al. | Nov 2019 | A1 |
20190342616 | Domm 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 |
20190387982 | Buller | Dec 2019 | A1 |
20200000441 | Lafon et al. | Jan 2020 | A1 |
20200014967 | Putnam | Jan 2020 | A1 |
20200054931 | Martin et al. | Feb 2020 | A1 |
20200069258 | Grinberg | Mar 2020 | A1 |
20200098278 | Doti et al. | Mar 2020 | A1 |
20200100693 | Velo | Apr 2020 | A1 |
20200101365 | Wilson et al. | 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 |
20200356242 | Wilson 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 |
20200384314 | Lee et al. | Dec 2020 | A1 |
20210019713 | Vangala et al. | Jan 2021 | A1 |
20210068714 | Crowley et al. | Mar 2021 | A1 |
20210110908 | Blahnik et al. | Apr 2021 | A1 |
20210191584 | Williams et al. | Jun 2021 | A1 |
20210204815 | Koskela et al. | Jul 2021 | A1 |
20210225482 | Crowley et al. | Jul 2021 | A1 |
20210255826 | Devine 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 |
20220047250 | Clements et al. | Feb 2022 | A1 |
20220047918 | Williams et al. | Feb 2022 | A1 |
20220066902 | Narra et al. | Mar 2022 | A1 |
20220109932 | Felton et al. | Apr 2022 | A1 |
20220142515 | Crowley | May 2022 | A1 |
20220157143 | 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 |
20230136700 | Williams et al. | May 2023 | A1 |
20230389806 | Felton et al. | Dec 2023 | A1 |
Number | Date | Country |
---|---|---|
2013201390 | May 2015 | AU |
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 |
104720765 | Jun 2015 | CN |
105260078 | Jan 2016 | CN |
105320454 | Feb 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 |
111344796 | Jun 2020 | CN |
202017002874 | Sep 2017 | DE |
2391004 | Nov 2011 | EP |
2529663 | Dec 2012 | EP |
2568409 | Mar 2013 | EP |
2921899 | Sep 2015 | EP |
3042606 | Jul 2016 | EP |
3096235 | Nov 2016 | EP |
3101882 | Dec 2016 | EP |
3117767 | Jan 2017 | EP |
3557590 | Oct 2019 | EP |
5-288869 | Nov 1993 | JP |
2004-80496 | Mar 2004 | JP |
2004-174006 | Jun 2004 | JP |
2004-318503 | Nov 2004 | JP |
2005-79814 | Mar 2005 | JP |
3635663 | Apr 2005 | JP |
2007-330513 | Dec 2007 | JP |
2008-011865 | Jan 2008 | JP |
2009-78134 | Apr 2009 | 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 |
2010-182287 | Aug 2010 | JP |
2011-197992 | Oct 2011 | JP |
2011-200575 | Oct 2011 | JP |
2012-502343 | Jan 2012 | JP |
2012-35071 | Feb 2012 | JP |
2012-45373 | Mar 2012 | JP |
2012-86088 | May 2012 | JP |
2012-524640 | Oct 2012 | JP |
2012-239808 | Dec 2012 | JP |
2013-17631 | Jan 2013 | JP |
2013-530776 | Aug 2013 | JP |
2013-192608 | Sep 2013 | JP |
2013-207323 | Oct 2013 | JP |
2013-544140 | Dec 2013 | JP |
2015-28686 | Feb 2015 | JP |
2015-73590 | Apr 2015 | JP |
2015-213686 | Dec 2015 | JP |
2016-502875 | Feb 2016 | JP |
2016-158867 | Sep 2016 | JP |
2016-528016 | Sep 2016 | JP |
2016-177151 | Oct 2016 | JP |
2016-185288 | 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-2012-0023657 | Mar 2012 | KR |
10-2012-0098854 | Sep 2012 | KR |
10-2012-0132732 | Dec 2012 | KR |
10-2013-0111569 | Oct 2013 | KR |
10-2013-0111570 | Oct 2013 | KR |
10-2015-0026635 | Mar 2015 | KR |
10-2015-0115385 | Oct 2015 | KR |
10-1594486 | Feb 2016 | KR |
10-2016-0027943 | Mar 2016 | KR |
10-2016-0028351 | Mar 2016 | KR |
10-2016-0076264 | Jun 2016 | KR |
10-2016-0077199 | Jul 2016 | KR |
10-2016-0105129 | Sep 2016 | KR |
10-2016-0142418 | Dec 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-2017-0032471 | Mar 2017 | KR |
10-2018-0129188 | Dec 2018 | KR |
10-2019-0094795 | Aug 2019 | KR |
9738626 | Oct 1997 | WO |
2003067202 | Aug 2003 | WO |
2005029242 | Mar 2005 | WO |
2006046648 | May 2006 | WO |
2008073359 | Jun 2008 | WO |
2009095908 | Aug 2009 | WO |
2010028320 | Mar 2010 | WO |
2010126825 | Nov 2010 | WO |
2011072111 | Jun 2011 | 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 |
2013169870 | Nov 2013 | WO |
2014015378 | Jan 2014 | WO |
2014207875 | Dec 2014 | WO |
2015027133 | Feb 2015 | WO |
2015084353 | Jun 2015 | WO |
2015089484 | Jun 2015 | WO |
2015131065 | Sep 2015 | WO |
2015153803 | Oct 2015 | WO |
2015164845 | Oct 2015 | WO |
2015183828 | Dec 2015 | WO |
2015187799 | Dec 2015 | WO |
2015198488 | Dec 2015 | WO |
2016022203 | Feb 2016 | 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 |
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 |
2019240513 | Dec 2019 | WO |
2022010573 | Jan 2022 | WO |
Entry |
---|
Notice of Acceptance received for Australian Patent Application No. 2022202459, dated May 11, 2023, 3 pages. |
Notice of Allowance received for Korean Patent Application No. 10-2022-7031866, dated May 1, 2023, 7 pages (2 pages of English Translation and 5 pages of Official Copy). |
Notice of Allowance received for U.S. Appl. No. 18/078,444, dated May 12, 2023, 9 pages. |
Office Action received for Australian Patent Application No. 2021261861, dated May 3, 2023, 4 pages. |
Office Action received for German Patent Application No. 112020002566.7, dated Mar. 24, 2023, 32 pages (14 pages of English Translation and 18 pages of official copy). |
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. |
Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/031,723, dated Jan. 23, 2023, 4 pages. |
Non-Final Office Action received for U.S. Appl. No. 17/952,053, dated Jan. 12, 2023, 12 pages. |
Notice of Allowance received for U.S. Appl. No. 17/317,084, dated Jan. 6, 2023, 6 pages. |
Office Action received for Australian Patent Application No. 2021261861, dated Jan. 12, 2023, 4 pages. |
Office Action received for Australian Patent Application No. 2022202459, dated Jan. 6, 2023, 3 pages. |
Supplemental Notice of Allowance received for U.S. Appl. No. 17/317,084, dated Jan. 19, 2023, 2 pages. |
Applicant-Initiated interview Summary received for U.S. Appl. No. 16/851,451, dated Nov. 29, 2022, 4 pages. |
Extended European Search Report received for European Patent Application No. 22190169.7, dated Nov. 23. 2022, 11 pages. |
Final Office Action received for U.S. Appl. No. 16/888,780, dated Nov. 25, 2022, 10 pages. |
Invitation to Pay Search Fees received for European Patent Application No. 20746438.9, dated Dec. 2, 2022, 4 pages. |
Non-Final Office Action received for U.S. Appl. No. 17/031,723, dated Dec. 5, 2022, 27 pages. |
Office Action received for Japanese Patent Application No. 2021-153558, dated Nov. 21, 2022, 8 pages (4 pages of English Translation and 4 pages of Official Copy). |
Office Action received for Korean Patent Application No. 10-2022-7031866, dated Nov. 18, 2022, 11 pages (5 pages of English Translation and 6 pages of Official Copy). |
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. 17/031,717, dated Apr. 15, 2022, 3 pages. |
Decision to Refuse received for European Patent Application No. 20180581.9, dated Apr. 13, 2022, 16 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, dated Apr. 20, 2022, 22 pages. |
Notice of Acceptance received for Australian Patent Application No. 2020239692, dated Apr. 6, 2022, 3 pages. |
Notice of Allowance received for Japanese Patent Application No. 2020-160023, dated 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. 2021571467, dated 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-7031939, dated Apr. 5, 2022, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
Supplemental Notice of Allowance received for U.S. Appl. No. 16/894,309, dated Apr. 8, 2022, 3 pages. |
Brief Communication Regarding Oral Proceedings received for European Patent Application No. 20746438.9, mailed on Nov. 7, 2022, 1 page. |
Invitation to Pay Search Fees received for European Patent Application No. 20760607.0, dated Nov. 21, 2022, 3 pages. |
Notice of Acceptance received for Australian Patent Application No. 2020288147, dated Dec. 22, 2021, 3 pages. |
Notice of Allowance received for Chinese Patent Application No. 202010618569.X, dated Jan. 7, 2022, 2 pages (1 page of English Translation and 1 page of Official Copy). |
Notice of Allowance received for U.S. Appl. No. 16/990,846, dated Jan. 20, 2022, 6 pages. |
Office Action received for Chinese Patent Application No. 202011220489.5, dated Dec. 1, 2021, 19 pages (11 pages of English Translation and 8 pages of Official Copy). |
Office Action received for Japanese Patent Application No. 2020-551585, dated Jan. 6, 2022, 11 pages (5 pages of English Translation and 6 pages of Official Copy). |
Corrected Notice of Allowance received for U.S. Appl. No. 17/197,628, dated Apr. 27, 2022, 3 pages. |
Intention to Grant received for European Patent Application No. 20180592.6, dated Apr. 20, 2022, 21 pages. |
Extended European Search Report received for European Patent Application No. 20203526.7, dated Jan. 29, 2021, 13 pages. |
Final Office Action received for U.S. Appl. No. 16/143,997, dated Feb. 9, 2021, 16 pages. |
Notice of Allowance received for U.S. Appl. No. 16/144,753, dated Feb. 10, 2021, 8 pages. |
Notice of Allowance received for U.S. Appl. No. 16/144,864, dated Feb. 9, 2021, 13 pages. |
Office Action received for Korean Patent Application No. 10-2019-7033834, dated Jan. 22, 2021, 13 pages (6 pages of English Translation and 7 pages of Official Copy). |
Office Action received for Korean Patent Application No. 10-2020-7026391, dated Jan. 27, 2021, 5 pages (2 pages of English Translation and 3 pages of Official Copy). |
Office Action received for Korean Patent Application No. 10-2020-7026453, dated Jan. 27, 2021, 5 pages (2 pages of English Translation and 3 pages of Official Copy). |
Corrected Notice of Allowance received for U.S. Appl. No. 17/031,717, dated May 19, 2022, 3 pages. |
Non-Final Office Action received for U.S. Appl. No. 16/851,451, dated May 9, 2022, 26 pages. |
Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/907,261, dated Jul. 16, 2021, 10 pages. |
Notice of Allowance received for Korean Patent Application No. 10-2019-7033834, dated Jul. 3, 2021, 4 pages (2 pages of English Translation and 2 pages of Official Copy). |
Notice of Allowance received for U.S. Appl. No. 16/138,809, dated Jul. 20, 2021, 6 pages. |
Office Action received for Chinese Patent Application No. 201910858933.7, dated Jun. 29, 2021, 8 pages (3 pages of English Translation and 5 pages of Official Copy). |
Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/143,997, dated May 3, 2021, 4 pages. |
Non-Final Office Action received for U.S. Appl. No. 16/990,846, dated May 10, 2021, 16 pages. |
Notice of Allowance received for U.S. Appl. No. 16/143,997, dated May 13, 2021, 10 pages. |
Notice of Allowance received for U.S. Appl. No. 16/880,552, dated May 12, 2021, 7 pages. |
Office Action received for Chinese Patent Application No. 202010618240.3, dated Mar. 29, 2021, 21 pages (11 pages of English Translation and 10 pages of Official Copy). |
Office Action received for Danish Patent Application No. PA202070620, dated May 10, 2021, 5 pages. |
Office Action received for Japanese Patent Application No. 2020-547369, dated Apr. 9, 2021, 4 pages (2 pages of English Translation and 2 pages of Official Copy). |
Brief Communication Regarding Oral Proceedings received for European Patent Application No. 20203526.7, mailed on Dec. 23, 2022, 4 pages. |
International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2021/035227, dated Dec. 15, 2022, 10 pages. |
International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2021/035504, dated Dec. 15, 2022, 8 pages. |
Office Action received for Australian Patent Application No. 2020313970, dated Dec. 22, 2022, 3 pages. |
Office Action received for Chinese Patent Application No. 201880032190.1, dated Nov. 14, 2022, 23 pages (12 pages of English Translation and 11 pages of Official Copy). |
Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/907,261, dated Mar. 25, 2021, 2 pages. |
Decision on Appeal received for Korean Patent Application No. 10-2019-7025538, dated Feb. 24, 2021, 20 pages (4 pages of English Translation and 16 pages of Official Copy). |
Final Office Action received for U.S. Appl. No. 16/907,261, dated Mar. 18, 2021, 20 pages. |
Notice of Allowance received for Korean Patent Application No. 10-2019-7025538, dated Mar. 10, 2021, 5 pages (2 pages of English Translation and 3 pages of Official Copy). |
Notice of Allowance received for U.S. Appl. No. 16/144,864, dated Mar. 30, 2021, 2 pages. |
Notice of Allowance received for U.S. Appl. No. 16/880,714, dated Mar. 19, 2021, 7 pages. |
Office Action received for Australian Patent Application No. 2019234289, dated Mar. 16, 2021, 8 pages. |
Office Action received for European Patent Application No. 18727543.3, dated Mar. 26, 2021, 7 pages. |
Result of Consultation received for European Patent Application No. 19726205.8, dated Mar. 15, 2021, 19 pages. |
Advisory Action received for U.S. Appl. No. 17/031,779, dated Oct. 20, 2022, 5 pages. |
Final Office Action received for U.S. Appl. No. 16/851,451, dated Oct. 20, 2022, 31 pages. |
Office Action received for Australian Patent Application No. 2021261861, dated Oct. 14, 2022, 5 pages. |
Office Action received for Chinese Patent Application No. 202010618240.3, dated 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, dated 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, dated Oct. 7, 2022, 4 pages. |
Supplemental Notice of Allowance received for U.S. Appl. No. 17/041,415, dated Oct. 13, 2022, 2 pages. |
Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/586,154, dated Sep. 3, 2021, 4 pages. |
Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/031,704, dated Feb. 9, 2021, 3 pages. |
Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/031,704, dated Jun. 25, 2021, 3 pages. |
Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/031,717, dated Jan. 29, 2021, 5 pages. |
Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/031,717, dated May 17, 2021, 5 pages. |
Final Office Action received for U.S. Appl. No. 17/031,704, dated Apr. 1, 2021, 31 pages. |
Final Office Action received for U.S. Appl. No. 17/031,717, dated Feb. 24, 2021, 23 pages. |
Non-Final Office Action received for U.S. Appl. No. 17/031,704, dated Dec. 10, 2020, 30 pages. |
Non-Final Office Action received for U.S. Appl. No. 17/031,717, dated Nov. 19, 2020, 22 pages. |
Notice of Allowance received for Japanese Patent Application No. 2019-563407, dated Aug. 20, 2021, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
Notice of Allowance received for Korean Patent Application No. 10-2020-7026035, dated Aug. 23, 2021, 4 pages (2 page of English Translation and 2 pages of Official Copy). |
Notice of Allowance received for U.S. Appl. No. 17/031,704, dated Jul. 21, 2021, 10 pages. |
Notice of Allowance received for U.S. Appl. No. 17/031,727, dated Dec. 24, 2020, 12 pages. |
Notice of Allowance received for U.S. Appl. No. 17/031,727, dated Jun. 25, 2021, 6 pages. |
Notice of Allowance received for U.S. Appl. No. 17/031,727, dated Mar. 12, 2021, 7 pages. |
Office Action received for Australian Patent Application No. 2020239740, dated Jul. 9, 2021, 4 pages. |
Office Action received for Danish Patent Application No. PA202070619, dated Aug. 27, 2021, 12 pages. |
Search Report and Opinion received for Danish Patent Application No. PA202070619, dated Dec. 2, 2020, 11 pages. |
Supplemental Notice of Allowance received for U.S. Appl. No. 17/031,727, dated Jan. 15, 2021, 2 pages. |
Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/880,714, dated Feb. 26, 2021, 5 pages. |
Final Office Action received for U.S. Appl. No. 16/894,309, dated Feb. 24, 2021, 30 pages. |
International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2020/035164, dated Feb. 8, 2021, 26 pages. |
Non-Final Office Action received for U.S. Appl. No. 16/880,552, dated Feb. 19, 2021, 11 pages. |
Office Action received for Danish Patent Application No. PA201970534, dated Feb. 16, 2021, 2 pages. |
Office Action received for Korean Patent Application No. 10-2020-7026035, dated Feb. 19, 2021, 13 pages (6 pages of English Translation and 7 pages of Official Copy). |
Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/031,723, dated Aug. 30, 2022, 4 pages. |
Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/031,779, dated Aug. 29, 2022, 2 pages. |
Decision to Grant received for European Patent Application No. 20180592.6, dated Sep. 1, 2022, 3 pages. |
Notice of Allowance received for U.S. Appl. No. 17/041,415, dated Aug. 31, 2022, 7 pages. |
Notice of Allowance received for U.S. Appl. No. 17/317,084, dated Aug. 29, 2022, 10 pages. |
Office Action received for Korean Patent Application No. 10-2020-7033395, dated Aug. 29, 2022, 11 pages (4 pages of English Translation and 7 pages of Official Copy). |
Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/041,415, dated Jun. 29, 2022, 2 pages. |
Final Office Action received for U.S. Appl. No. 17/031,723, dated Jul. 12, 2022, 25 pages. |
Final Office Action received for U.S. Appl. No. 17/031,779, dated Jul. 14, 2022, 19 pages. |
Notice of Allowance received for U.S. Appl. No. 17/031,717, dated Jul. 7, 2022, 12 pages. |
Notice of Allowance received for U.S. Appl. No. 17/197,628, dated Jun. 24, 2022, 8 pages. |
Summons to Attend Oral Proceedings received for European Patent Application No. 20203526.7, mailed on Jun. 23, 2022, 9 pages. |
Notice of Allowance received for Japanese Patent Application No. 2020-547369, dated Jul. 16, 2021, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
Notice of Allowance received for U.S. Appl. No. 16/880,552, dated Jul. 23, 2021, 5 pages. |
Office Action received for Australian Patent Application No. 2019234289, dated Jul. 20, 2021, 4 pages. |
Office Action received for Australian Patent Application No. 2020239692, dated Jul. 20, 2021, 5 pages. |
Notice of Acceptance received for Australian Patent Application No. 2021200787, dated Mar. 19, 2021, 3 pages. |
Notice of Allowance received for U.S. Appl. No. 16/144,030, dated Apr. 5, 2021, 8 pages. |
Office Action received for European Patent Application No. 20180581.9, dated Apr. 1, 2021, 11 pages. |
Office Action received for European Patent Application No. 20180592.6, dated Apr. 1, 2021, 11 pages. |
Office Action received for Japanese Patent Application No. 2018-184532, dated Mar. 1, 2021, 11 pages (6 pages of English Translation and 5 pages of Official Copy). |
Corrected Notice of Allowance received for U.S. Appl. No. 16/143,997, dated Jun. 4, 2021, 2 pages. |
Notice of Allowance received for U.S. Appl. No. 16/880,714, dated Jun. 9, 2021, 6 pages. |
Office Action received for Australian Patent Application No. 2020256383, dated Jun. 4, 2021, 3 pages. |
Office Action received for Danish Patent Application No. PA202070335, dated Jun. 11, 2021, 4 pages. |
Office Action received for European Patent Application No. 19721883.7, dated Jun. 15, 2021, 9 pages. |
Notice of Allowance received for Korean Patent Application No. 10-2022-7017918, dated Jun. 13, 2022, 6 pages (2 pages of English Translation and 4 pages of Official Copy). |
Office Action received for Chinese Patent Application No. 202010618240.3, dated 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, dated 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/586,154, dated Mar. 11, 2020, 4 pages. |
Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/138,809, dated Dec. 16, 2020, 7 pages. |
Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/586,154, dated Dec. 11, 2020, 5 pages. |
Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/880,552, dated Dec. 16, 2020, 6 pages. |
Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/894,309, dated Jan. 26, 2021, 3 pages. |
Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/907,261, dated Dec. 16, 2020, 6 pages. |
Final Office Action received for U.S. Appl. No. 16/586,154, dated Jul. 6, 2020, 27 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. |
International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2020/035462, dated Sep. 11, 2020, 17 pages. |
International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2020/035474, dated Nov. 26, 2020, 16 pages. |
International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2020/042439, dated Oct. 9, 2020, 14 pages. |
Invitation to Pay Additional Fees and Partial International Search Report received for PCT Patent Application No. PCT/US2020/035164, dated Oct. 16, 2020, 14 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. |
Non-Final Office Action received for U.S. Appl. No. 16/586,154, dated Dec. 9, 2019, 23 pages. |
Non-Final Office Action received for U.S. Appl. No. 16/880,714, dated Oct. 28, 2020, 11 pages. |
Notice of Acceptance received for Australian Patent Application No. 2018268972, dated Dec. 18, 2020, 3 pages. |
Notice of Allowance received for Japanese Patent Application No. 2020-104679, dated Jan. 4, 2021, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
Notice of Allowance received for U.S. Appl. No. 16/144,753, dated Dec. 4, 2020, 22 pages. |
Notice of Allowance received for U.S. Appl. No. 16/880,552, dated Dec. 1, 2020, 7 pages. |
Search Report and Opinion received for Danish Patent Application No. PA202070335, dated Nov. 27, 2020, 10 pages. |
Search Report and Opinion received for Danish Patent Application No. PA202070395, dated Nov. 24, 2020, 10 pages. |
Tech, Kalyani,“I See Some problems in Honor Band 5”, Retrieved from: https://www.youtube.com/watch?v=5XPnYJFqajl, May 19, 2020, 1 page. |
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. |
Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/851,451, dated Apr. 20, 2023, 4 pages. |
Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/952,053, dated Apr. 5, 2023, 6 pages. |
Intention to Grant received for European Patent Application No. 18727543.3, dated Apr. 12, 2023, 9 pages. |
Notice of Allowance received for U.S. Appl. No. 17/952,053, dated Apr. 17, 2023, 6 pages. |
Office Action received for Chinese Patent Application No. 202210004176.9, dated Feb. 19, 2023, 23 pages (14 pages of English Translation and 9 pages of Official Copy). |
Office Action received for Korean Patent Application No. 10-2020-0124134, dated Mar. 28, 2023, 9 pages (4 pages of English Translation and 5 pages of Official Copy). |
Brief Communication Regarding Oral Proceedings received for European Patent Application No. 20180581.9, mailed on Nov. 30, 2021, 1 page. |
Corrected Notice of Allowance received for U.S. Appl. No. 16/880,552, dated Dec. 22, 2021, 2 pages. |
Corrected Notice of Allowance received for U.S. Appl. No. 16/921,312, dated Dec. 7, 2021, 2 pages. |
International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2020/035164, dated Dec. 16, 2021, 19 pages. |
International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2020/035462, dated Dec. 16, 2021, 16 pages. |
International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2020/025768, dated Dec. 16, 2021, 8 pages. |
International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2020/035474, dated Dec. 16, 2021, 11 pages. |
Office Action received for Danish Patent Application No. PA202070395, dated Dec. 15, 2021, 5 pages. |
Office Action received for Indian Patent Application No. 202014041484, dated Dec. 8, 2021, 8 pages. |
Brief Communication Regarding Oral Proceedings received for European Patent Application No. 18727543.3, mailed on Mar. 23, 2023, 1 page. |
Corrected Notice of Allowance received for U.S. Appl. No. 16/953,781, dated Mar. 30, 2023, 2 pages. |
Non-Final Office Action received for U.S. Appl. No. 17/952,182, dated Mar. 28, 2023, 9 pages. |
Office Action received for Australian Patent Application No. 2020313970, dated Mar. 22, 2023, 4 pages. |
Office Action received for Australian Patent Application No. 2022202459, dated Mar. 27, 2023, 5 pages. |
Office Action received for Danish Patent Application No. PA202070395, dated Mar. 31, 2023, 3 pages. |
Office Action received for Japanese Patent Application No. 2022-502594, dated Mar. 20, 2023, 10 pages (5 pages of English Translation and 5 pages of Official Copy). |
Result of Consultation received for European Patent Application No. 18727543.3, dated Mar. 15, 2023, 6 pages. |
Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/953,781, dated Oct. 31, 2022, 12 pages. |
Notice of Allowance received for U.S. Appl. No. 16/953,781, dated Nov. 9, 2022, 7 pages. |
Office Action received for European Patent Application No. 20746438.9, dated Oct. 31, 2022, 7 pages. |
Summons to Attend Oral Proceedings received for European Patent Application No. 18727543.3, mailed on Oct. 25, 2022, 8 pages. |
International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2020/070280, dated Nov. 30, 2020, 20 pages. |
Invitation to Pay Additional Fees received for PCT Patent Application No. PCT/US2020/070280, dated Oct. 7, 2020, 12 pages. |
Notice of Allowance received for U.S. Appl. No. 16/144,864, dated Mar. 12, 2021, 2 pages. |
Office Action received for Australian Patent Application No. 2020230340, dated Mar. 2, 2021, 6 pages. |
Office Action received for Chinese Patent Application No. 202010606407.4, dated Jan. 27, 2021, 16 pages (7 pages of English Translation and 9 pages of Official Copy). |
Office Action received for Japanese Patent Application No. 2019-563407, dated Feb. 5, 2021, 5 pages (2 pages of English Translation and 3 pages of Official Copy). |
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. |
Final Office Action received for U.S. Appl. No. 16/586,154, dated May 24, 2021, 29 pages. |
Notice of Allowance received for Korean Patent Application No. 10-2020-7026391, dated May 11, 2021, 3 pages (1 page of English Translation and 2 pages of Official Copy). |
Notice of Allowance received for Korean Patent Application No. 10-2020-7026453, dated May 11, 2021, 3 pages (1 page of English Translation and 2 pages of Official Copy). |
Office Action received for European Patent Application No. 20182116.2, dated May 25, 2021, 9 pages. |
Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/894,309, dated Jun. 25, 2021, 4 pages. |
Corrected Notice of Allowance received for U.S. Appl. No. 16/143,997, dated Jul. 2, 2021, 2 pages. |
Corrected Notice of Allowance received for U.S. Appl. No. 16/880,552, dated Jul. 7, 2021, 2 pages. |
Office Action received for Australian Patent Application No. 2020230340, dated May 27, 2021, 5 pages. |
Office Action received for Chinese Patent Application No. 202010606407.4, dated Jun. 2, 2021, 12 pages (5 pages of English Translation and 7 pages of Official Copy). |
Office Action received for Chinese Patent Application No. 202011220489.5, dated Jun. 1, 2021, 12 pages (6 pages of English Translation and 6 pages of Official Copy). |
Office Action received for Japanese Patent Application No. 2020-153166, dated May 31, 2021, 6 pages (3 pages of English Translation and 3 pages of Official Copy). |
Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/031,717, dated Nov. 4, 2021, 5 pages. |
Corrected Notice of Allowance received for U.S. Appl. No. 16/143,997, dated Nov. 16, 2021, 2 pages. |
Corrected Notice of Allowance received for U.S. Appl. No. 17/031,704, dated Nov. 2, 2021, 7 pages. |
Notice of Allowance received for U.S. Appl. No. 16/894,309, dated Nov. 5, 2021, 12 pages. |
Office Action received for Australian Patent Application No. 2019234289, dated Nov. 1, 2021, 4 pages. |
Notice of Acceptance received for Australian Patent Application No. 2020256383, dated Aug. 3, 2021, 3 pages. |
Notice of Allowance received for U.S. Appl. No. 16/907,261, dated Aug. 13, 2021, 8 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. |
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. |
Intention to Grant received for Danish Patent Application No. PA202070619, dated Jan. 17, 2022, 2 pages. |
International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2020/042439, dated Jan. 27, 2022, 10 pages. |
Non-Final Office Action received for U.S. Appl. No. 17/031,723, dated Jan. 24, 2022, 17 pages. |
Notice of Allowance received for Chinese Patent Application No. 202010606407.4, dated 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, dated Jan. 17, 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, dated Jan. 17, 2022, 6 pages (1 page of English Translation and 5 pages of Official Copy). |
Office Action received for Japanese Patent Application No. 2020-160023, dated Jan. 17, 2022, 11 pages (06 pages of English Translation and 05 pages of Official Copy). |
Result of Consultation received for European Patent Application No. 20180581.9, dated Jan. 21, 2022, 14 pages. |
Result of Consultation received for European Patent Application No. 20180592.6, dated Jan. 26, 2022, 18 pages. |
Supplemental Notice of Allowance received for U.S. Appl. No. 16/894,309, dated Jan. 25, 2022, 2 pages. |
Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/586,154, dated Apr. 14, 2021, 4 pages. |
Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/880,552, dated Apr. 21, 2021, 3 pages. |
Notice of Allowance received for Japanese Patent Application No. 2019-162293, dated Apr. 9, 2021, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
Notice of Allowance received for U.S. Appl. No. 16/138,809, dated Apr. 16, 2021, 11 pages. |
Office Action received for Chinese Patent Application No. 202010618569.X, dated Mar. 12, 2021, 14 pages (7 pages of English Translation and 7 pages of Official Copy). |
Corrected Notice of Allowance received for U.S. Appl. No. 16/921,312, dated Sep. 24, 2021, 2 pages. |
Non-Final Office Action received for U.S. Appl. No. 17/031,717, dated Sep. 14, 2021, 35 pages. |
Notice of Allowance received for Japanese Patent Application No. 2020-153166, dated Sep. 13, 2021, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
Notice of Allowance received for U.S. Appl. No. 16/907,261, dated Sep. 28, 2021, 6 pages. |
Notice of Allowance received for U.S. Appl. No. 16/921,312, dated Sep. 14, 2021, 9 pages. |
Notice of Allowance received for U.S. Appl. No. 16/990,846, dated Sep. 22, 2021, 9 pages. |
Office Action received for Chinese Patent Application No. 202010618569.X, dated Sep. 7, 2021, 7 pages (4 pages of English Translation and 3 pages of Official Copy). |
Supplemental Notice of Allowance received for U.S. Appl. No. 16/880,714, dated Sep. 16, 2021, 2 pages. |
Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/031,723, dated Mar. 21, 2021, 5 pages. |
International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2020/070280, dated Mar. 17, 2022, 15 pages. |
Non-Final Office Action received for U.S. Appl. No. 17/041,415, dated Mar. 29, 2022, 11 pages. |
Notice of Allowance received for U.S. Appl. No. 17/031,717, dated Mar. 16, 2022, 12 pages. |
Notice of Allowance received for U.S. Appl. No. 17/197,628, dated Mar. 23, 2022, 35 pages. |
Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/031,779, dated Mar. 10, 2022, 2 pages. |
International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2021/048568, dated Jan. 7, 2022, 14 pages. |
Notice of Acceptance received for Australian Patent Application No. 2020239740, dated Feb. 22, 2022., 3 pages. |
Notice of Allowance received for U.S. Appl. No. 16/894,309, dated Feb. 25, 2022, 9 pages. |
Corrected Notice of Allowance received for U.S. Appl. No. 17/031,779, dated Jun. 14, 2023, 2 pages. |
Non-Final Office Action received for U.S. Appl. No. 17/031,723, dated Jun. 2, 2023, 23 pages. |
Notice of Allowance received for Japanese Patent Application No. 2021-153558, dated Jun. 9, 2023, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
Office Action received for Chinese Patent Application No. 201880032190.1, dated May 31, 2023, 20 pages (12 pages of English Translation and 8 pages of Official Copy). |
Office Action received for Chinese Patent Application No. 202210004176.9, dated Apr. 28, 2023, 12 pages (6 pages of English Translation and 6 pages of Official Copy). |
Office Action received for Indian Patent Application No. 202215032692, dated Jun. 15, 2023, 3 pages. |
Office Action received for Japanese Patent Application No. 2022-078277, dated Jun. 9, 2023, 11 pages (6 pages of English Translation and 5 pages of Official Copy). |
Supplemental Notice of Allowance received for U.S. Appl. No. 18/078,444, dated Jun. 15, 2023, 2 pages. |
Brief Communication regarding Oral Proceedings received for European Patent Application No. 20180592.6, mailed on Dec. 21, 2021, 1 page. |
Notice of Allowance received for Korean Patent Application No. 10-2021-7038005, dated Dec. 14, 2021, 4 pages (2 pages of English Translation and 2 pages of Official Copy). |
Office Action received for Chinese Patent Application No. 202010606407.4, dated 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, dated Dec. 3, 2021, 23 pages (14 pages of English Translation and 9 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, dated Dec. 24, 2021, 2 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, dated Feb. 10, 2023, 9 pages. |
Notice of Allowance received for Chinese Patent Application No. 202210238202.4, dated 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, dated 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, dated Feb. 1, 2023, 11 pages. |
Office Action received for European Patent Application No. 20746438.9, dated Feb. 1, 2023, 9 pages. |
Office Action received for European Patent Application No. 20760607.0, dated Feb. 1, 2023, 13 pages. |
Result of Consultation received for European Patent Application No. 20203526.7, dated Jan. 13, 2023, 3 pages. |
Notice of Allowance received for U.S. Appl. No. 16/143,997, dated Sep. 30, 2021, 8 pages. |
Office Action received for Australian Patent Application No. 2020239740, dated Sep. 28, 2021, 5 pages. |
Notice of Allowance received for U.S. Appl. No. 16/586,154, dated Oct. 15, 2021, 8 pages. |
Office Action received for Australian Patent Application No. 2020230340, dated Oct. 11, 2021, 4 pages. |
Intention to Grant received for European Patent Application No. 20182116.2, dated 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, dated May 19, 2022, 5 pages (2 pages of English Translation and 3 pages of Official Copy). |
Office Action received for Australian Patent Application No. 2021204422, dated May 31, 2022, 2 pages. |
Office Action received for Chinese Patent Application No. 202011220489.5, dated 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, dated Jun. 22, 2023, 2 pages. |
Notice of Acceptance received for Australian Patent Application No. 2020313970, dated Jun. 22, 2023, 3 pages. |
Notice of Acceptance received for Australian Patent Application No. 2022203508, dated Jun. 27, 2023, 3 pages. |
Office Action received for Korean Patent Application No. 10-2020-0124134, dated Jun. 23, 2023, 8 pages (4 pages of English Translation and 4 pages of Official Copy). |
Final Office Action received for U.S. Appl. No. 16/851,451, dated Jun. 1, 2023, 35 pages. |
Notice of Allowance received for U.S. Appl. No. 17/031,779, dated May 26, 2023, 9 pages. |
Office Action received for Australian Patent Application No. 2022203508, dated May 19, 2023, 2 pages. |
Office Action received for Australian Patent Application No. 2022204568, dated May 22, 2023, 4 pages. |
Office Action received for Australian Patent Application No. 2022235614, dated May 9, 2023, 2 pages. |
International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2021/035504, dated Sep. 16, 2021, 12 pages. |
Notice of Allowance received for U.S. Appl. No. 16/880,552, dated Nov. 24, 2021, 5 pages. |
Notice of Allowance received for U.S. Appl. No. 16/921,312, dated Nov. 29, 2021, 5 pages. |
Office Action received for Danish Patent Application No. PA202070335, dated Nov. 17, 2021, 6 pages. |
Office Action received for Danish Patent Application No. PA202070620, dated Nov. 19, 2021, 2 pages. |
Office Action received for European Patent Application No. 20203526.7, dated Nov. 23, 2021, 9 pages. |
Corrected Notice of Allowance received for U.S. Appl. No. 16/990,846, dated Feb. 9, 2022, 3 pages. |
Non-Final Office Action received for U.S. Appl. No. 17/031,779, dated Feb. 16, 2022, 17 pages. |
Office Action received for Australian Patent Application No. 2020239692, dated Jan. 27, 2022, 3 pages. |
Office Action received for Chinese Patent Application No. 201910858933.7, dated Dec. 30, 2021, 9 pages (4 pages of English Translation and 5 pages of Official Copy). |
Advisory Action received for U.S. Appl. No. 16/144,864, dated Jul. 29, 2019, 6 pages. |
Advisory Action received for U.S. Appl. No. 16/143,909, dated Nov. 7, 2019, 5 pages. |
Advisory Action received for U.S. Appl. No. 16/143,997, dated Dec. 26, 2019, 7 pages. |
Advisory Action received for U.S. Appl. No. 16/144,849, dated Aug. 12, 2019, 5 pages. |
Advisory Action received for U.S. Appl. No. 16/144,864, dated Jul. 6, 2020, 6 pages. |
Applicant Initiated Interview Summary received for U.S. Appl. No. 16/143,997, dated Aug. 13, 2020, 3 pages. |
Applicant Initiated Interview Summary received for U.S. Appl. No. 16/144,735, dated Jun. 18, 2020, 3 pages. |
Applicant Initiated Interview Summary received for U.S. Appl. No. 16/144,753, dated Jun. 18, 2020, 3 pages. |
Applicant Initiated Interview Summary received for U.S. Appl. No. 16/144,849, dated Jan. 21, 2020, 6 pages. |
Applicant Initiated Interview Summary received for U.S. Appl. No. 16/144,864, dated Apr. 29, 2020, 4 pages. |
Applicant-Initiated Interview Summary received for U.S. Appl. No. 15/705,849, dated Feb. 14, 2020, 3 pages. |
Applicant-Initiated Interview Summary received for U.S. Appl. No. 15/705,849, dated Jun. 29, 2020, 3 pages. |
Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/138,809, dated Jun. 9, 2020, 4 pages. |
Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/144,753, dated Nov. 4, 2020, 3 pages. |
Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/144,864, dated Jun. 22, 2020, 3 pages. |
Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/584,186, dated Feb. 3, 2020, 4 pages. |
Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/880,552, dated Oct. 20, 2020, 6 pages. |
Certificate of Examination received for Australian Patent Application No. 2019100222, dated Aug. 29, 2019, 2 pages. |
Corrected Notice of Allowance received for U.S. Appl. No. 16/143,909, dated Feb. 20, 2020, 3 pages. |
Corrected Notice of Allowance received for U.S. Appl. No. 16/143,909, dated Mar. 18, 2020, 3 pages. |
Corrected Notice of Allowance received for U.S. Appl. No. 16/143,959, dated Dec. 13, 2019, 2 pages. |
Corrected Notice of Allowance received for U.S. Appl. No. 16/584,186, dated Jul. 31, 2020, 2 pages. |
Corrected Notice of Allowance received for U.S. Appl. No. 16/880,552, dated Dec. 23, 2020, 2 pages. |
Decision to Grant received for Danish Patent Application No. PA201870379, dated Jul. 5, 2019, 2 pages. |
Decision to Grant received for Danish Patent Application No. PA201870600, dated Oct. 17, 2019, 2 pages. |
Decision to Grant received for Danish Patent Application No. PA201870601, dated Aug. 17, 2020, 2 pages. |
Decision to Grant received for Danish Patent Application No. PA201870602, dated Aug. 18, 2020, 2 pages. |
European Search Report received for European Patent Application No. 20182116.2, dated Oct. 21, 2020, 4 pages. |
Extended European Search Report received for European Patent Application No. 20180581.9, dated Aug. 12, 2020, 9 pages. |
Extended European Search Report received for European Patent Application No. 20180592.6, dated Aug. 11, 2020, 10 pages. |
Final Office Action received for U.S. Appl. No. 15/705,849, dated May 1, 2020, 17 pages. |
Final Office Action received for U.S. Appl. No. 16/138,809, dated Aug. 27, 2020, 24 pages. |
Final Office Action received for U.S. Appl. No. 16/143,909, dated Aug. 28, 2019, 20 pages. |
Final Office Action received for U.S. Appl. No. 16/143,997, dated Sep. 30, 2019, 16 pages. |
Final Office Action received for U.S. Appl. No. 16/144,030, dated Feb. 13, 2020, 11 pages. |
Final Office Action received for U.S. Appl. No. 16/144,030, dated Oct. 1, 2019, 13 pages. |
Final Office Action received for U.S. Appl. No. 16/144,735, dated May 4, 2020, 12 pages. |
Final Office Action received for U.S. Appl. No. 16/144,753, dated Sep. 22, 2020, 9 pages. |
Final Office Action received for U.S. Appl. No. 16/144,849, dated Jun. 7, 2019, 29 pages. |
Final Office Action received for U.S. Appl. No. 16/144,864, dated May 17, 2019, 24 pages. |
Final Office Action received for U.S. Appl. No. 16/144,864, dated May 28, 2020, 29 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, dated May 2, 2019, 2 pages. |
Intention to Grant received for Danish Patent Application No. PA201870600, dated Jul. 10, 2019, 2 pages. |
Intention to Grant received for Danish Patent Application No. PA201870601, dated Apr. 24, 2020, 2 pages. |
Intention to Grant received for Danish Patent Application No. PA201870602, dated Apr. 24, 2020, 2 pages. |
International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2018/031662, dated Nov. 28, 2019, 12 pages. |
International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2019/019694, dated Sep. 24, 2020, 12 pages. |
International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2019/024570, dated Nov. 19, 2020, 10 pages. |
International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2018/031662, dated Sep. 27, 2018, 17 pages. |
International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2019/019694, dated Sep. 2, 2019, 17 pages. |
International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2019/024570, dated Aug. 8, 2019, 18 pages. |
International Search Report and written Opinion received for PCT Patent Application No. PCT/US2020/025768, dated Aug. 10, 2020, 11 pages. |
Invitation to Pay Addition Fees and Partial International Search Report received for PCT Patent Application No. PCT/US2018/031662, dated Jul. 16, 2018, 13 pages. |
Invitation to Pay Addition Fees received for PCT Patent Application No. PCT/US2020/035474, dated Oct. 2, 2020, 11 pages. |
Invitation to Pay Additional Fees received for PCT Patent Application No. PCT/US2019/019694, dated Jul. 10, 2019, 12 pages. |
Invitation to Pay Search Fees received for European Patent Application No. 19726205.8, dated 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, dated Dec. 18, 2018, 19 pages. |
Non-Final Office Action received for U.S. Appl. No. 15/705,849, dated Nov. 12, 2019, 15 pages. |
Non-Final Office Action received for U.S. Appl. No. 16/138,809, dated Feb. 28, 2020, 22 pages. |
Non-Final Office Action received for U.S. Appl. No. 16/143,909, dated Apr. 19, 2019, 16 pages. |
Non-Final Office Action received for U.S. Appl. No. 16/143,959, dated Apr. 17, 2019, 15 pages. |
Non-Final Office Action received for U.S. Appl. No. 16/143,997, dated Jul. 27, 2020, 15 pages. |
Non-Final Office Action received for U.S. Appl. No. 16/143,997, dated May 21, 2019, 15 pages. |
Non-Final Office Action received for U.S. Appl. No. 16/144,030, dated Apr. 12, 2019, 8 pages. |
Non-Final Office Action received for U.S. Appl. No. 16/144,030, dated Nov. 5, 2020, 5 pages. |
Non-Final Office Action received for U.S. Appl. No. 16/144,735, dated Feb. 19, 2020, 10 pages. |
Non-Final Office Action received for U.S. Appl. No. 16/144,753, dated Mar. 5, 2020, 9 pages. |
Non-Final Office Action received for U.S. Appl. No. 16/144,849, dated Dec. 31, 2018, 28 pages. |
Non-Final Office Action received for U.S. Appl. No. 16/144,849, dated Sep. 17, 2019, 9 pages. |
Non-Final Office Action received for U.S. Appl. No. 16/144,864, dated Jan. 31, 2020, 29 pages. |
Non-Final Office Action received for U.S. Appl. No. 16/584,186, dated Dec. 6, 2019, 13 pages. |
Non-Final Office Action received for U.S. Appl. No. 16/586,154, dated Dec. 28, 2020, 26 pages. |
Non-Final Office Action received for U.S. Appl. No. 16/880,552, dated Jul. 23, 2020, 19 pages. |
Non-Final Office Action received for U.S. Appl. No. 16/894,309, dated Oct. 15, 2020, 24 pages. |
Non-Final Office Action received for U.S. Appl. No. 16/907,261, dated Sep. 30, 2020, 22 pages. |
Notice of Acceptance received for Australian Patent Application No. 2019222943, dated May 5, 2020, 3 pages. |
Notice of Acceptance received for Australian Patent Application No. 2020204153, dated Jul. 6, 2020, 3 pages. |
Notice of Allowance received for Chinese Patent Application No. 201910972529.2, dated Sep. 14, 2020, 6 pages. |
Notice of Allowance received for U.S. Appl. No. 15/705,849, dated Jul. 28, 2020, 10 pages. |
Notice of Allowance received for U.S. Appl. No. 15/705,849, dated Oct. 16, 2020, 14 pages. |
Notice of Allowance received for U.S. Appl. No. 16/143,909, dated Jan. 21, 2020, 9 pages. |
Notice of Allowance received for U.S. Appl. No. 16/143,959, dated Oct. 31, 2019, 10 pages. |
Notice of Allowance received for U.S. Appl. No. 16/144,671, dated Feb. 10, 2020, 17 pages. |
Notice of Allowance received for U.S. Appl. No. 16/144,735, dated Jul. 21, 2020, 13 pages. |
Notice of Allowance received for U.S. Appl. No. 16/144,735, dated Oct. 28, 2020, 13 pages. |
Notice of Allowance received for U.S. Appl. No. 16/144,849, dated Apr. 17, 2020, 2 pages. |
Notice of Allowance received for U.S. Appl. No. 16/144,849, dated Mar. 6, 2020, 9 pages. |
Notice of Allowance received for U.S. Appl. No. 16/144,864, dated Jul. 28, 2020, 27 pages. |
Notice of Allowance received for U.S. Appl. No. 16/144,864, dated Sep. 10, 2020, 3 pages. |
Notice of Allowance received for U.S. Appl. No. 16/144,864, dated Sep. 16, 2020, 2 pages. |
Notice of Allowance received for U.S. Appl. No. 16/144,864, dated Sep. 29, 2020, 2 pages. |
Notice of Allowance received for U.S. Appl. No. 16/584,186, dated Mar. 24, 2020, 10 pages. |
Office Action received for Australian Patent Application No. 2018268972, dated Jul. 9, 2020, 4 pages. |
Office Action received for Australian Patent Application No. 2019100222, dated May 24, 2019, 6 pages. |
Office Action received for Australian Patent Application No. 2019100495, dated Mar. 6, 2020, 3 pages. |
Office Action received for Australian Patent Application No. 2019100495, dated Mar. 16, 2020, 3 pages. |
Office Action received for Australian Patent Application No. 2019100495, dated Sep. 17, 2019, 7 pages. |
Office Action received for Australian Patent Application No. 2019222943, dated Oct. 3, 2019, 3 pages. |
Office Action received for Australian Patent Application No. 2019234289, dated Nov. 2, 2020, 6 pages. |
Office Action received for Australian Patent Application No. 2020230340, dated Nov. 2, 2020, 5 pages. |
Office Action received for Chinese Patent Application No. 201910858933.7, dated Aug. 18, 2020, 14 pages. |
Office Action received for Chinese Patent Application No. 201910972529.2, dated Jun. 28, 2020, 8 pages. |
Office Action received for Danish Patent Application No. PA201870378, dated Feb. 25, 2019, 3 pages. |
Office Action received for Danish Patent Application No. PA201870378, dated Jan. 6, 2020, 3 pages. |
Office Action received for Danish Patent Application No. PA201870379, dated Feb. 28, 2019, 3 pages. |
Office Action received for Danish Patent Application No. PA201870380, dated Mar. 5, 2020, 2 pages. |
Office Action received for Danish Patent Application No. PA201870380, dated Mar. 27, 2019, 4 pages. |
Office Action received for Danish Patent Application No. PA201870380, dated Sep. 11, 2018, 9 pages. |
Office Action received for Danish Patent Application No. PA201870599, dated Dec. 20, 2019, 5 pages. |
Office Action received for Danish Patent Application No. PA201870600, dated May 8, 2019, 3 pages. |
Office Action received for Danish Patent Application No. PA201870601, dated Dec. 13, 2018, 8 pages. |
Office Action received for Danish Patent Application No. PA201870601, dated Jan. 14, 2020, 3 pages. |
Office Action received for Danish Patent Application No. PA201870601, dated Jun. 25, 2019, 3 pages. |
Office Action received for Danish Patent Application No. PA201870602, dated Feb. 5, 2020, 3 pages. |
Office Action received for Danish Patent Application No. PA201870602, dated Jun. 26, 2019, 3 Pages. |
Office Action received for Danish Patent Application No. PA201970534, dated Jun. 29, 2020, 2 pages. |
Office Action received for European Patent Application No. 19721883.7, dated Jan. 10, 2020, 4 pages. |
Office Action received for European Patent Application No. 19721883.7, dated May 28, 2020, 11 pages. |
Office Action received for European Patent Application No. 19726205.8, dated Jun. 26, 2020, 9 pages. |
Office Action received for European Patent Application No. 20182116.2, dated Nov. 6, 2020, 9 pages. |
Office Action received for Japanese Patent Application No. 2019-162293, dated Jan. 31, 2020, 8 pages. |
Office Action received for Japanese Patent Application No. 2019-162293, dated Jul. 27, 2020, 9 pages. |
Office Action received for Japanese Patent Application No. 2020-104679, dated Sep. 18, 2020, 13 pages. |
Office Action received for Korean Patent Application No. 10-2019-7025538, dated Aug. 15, 2020, 8 pages. |
Office Action received for Korean Patent Application No. 10-2019-7025538, dated Feb. 17, 2020, 12 pages. |
Result of Consultation received for European Patent Application No. 19721883.7, dated Oct. 7, 2020, 3 pages. |
Search Report and Opinion received for Danish Patent Application No. PA201870378, dated Sep. 10, 2018, 9 pages. |
Search Report and Opinion received for Danish Patent Application No. PA201870379, dated Sep. 14, 2018, 9 pages. |
Search Report and Opinion received for Danish Patent Application No. PA201870599, dated Dec. 21, 2018, 9 pages. |
Search Report and Opinion received for Danish Patent Application No. PA201870600, dated Jan. 31, 2019, 8 pages. |
Search Report and Opinion received for Danish Patent Application No. PA201870602, dated Dec. 19, 2018, 8 pages. |
Search Report and Opinion received for Danish Patent Application No. PA201970534, dated Sep. 23, 2019, 6 pages. |
Search Report and Opinion received for Danish Patent Application No. PA202070620, dated Dec. 11, 2020, 9 pages. |
Summons to Attend Oral Proceedings received for European Patent Application No. 19726205.8, dated Oct. 29, 2020, 13 pages. |
Supplemental Notice of Allowance received for U.S. Appl. No. 16/144,849, dated Mar. 31, 2020, 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. |
DC Rainmaker, “Garmin Fenix3 New Auto Climb Functionality”, Available online at: https://www.youtube.com/watch?v=iuavOSNpVRc, Feb. 19, 2015, 1 page. |
Evergreen et al., “Bar Chart”, Better Evaluation, Available Online at: https://www.betterevaluation.org/en/evaluation-options/BarChart, Oct. 31, 2014, 8 pages. |
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. |
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. |
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. |
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=aixfoCnSOOU, Mar. 19, 2018, 2 pages. |
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. |
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. |
Decision to Grant received for Danish Patent Application No. PA202070619, dated Aug. 11, 2022, 2 pages. |
Notice of Acceptance received for Australian Patent Application No. 2021204422, dated Aug. 15, 2022, 3 pages. |
Office Action received for Japanese Patent Application No. 2021-167557, dated Aug. 15, 2022, 5 pages (3 pages of English Translation and 2 pages of Official Copy). |
Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/851,451, dated Aug. 5, 2022, 3 pages. |
Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/888,780, dated Aug. 2, 2022, 4 pages. |
Corrected Notice of Allowance received for U.S. Appl. No. 17/197,628, dated Jul. 29, 2022, 2 pages. |
Non-Final Office Action received for U.S. Appl. No. 16/953,781, dated Jul. 26, 2022, 9 pages. |
Notice of Allowance received for Japanese Patent Application No. 2020-551585, dated 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, dated Jul. 28, 2022, 22 pages (11 pages of English Translation and 11 pages of Official Copy). |
International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2021/048568, dated Mar. 9, 2023, 11 pages. |
Non-Final Office Action received for U.S. Appl. No. 16/851,451, dated Feb. 24, 2023, 28 pages. |
Non-Final Office Action received for U.S. Appl. No. 17/337,147, dated Feb. 21, 2023, 15 pages. |
Notice of Allowance received for U.S. Appl. No. 16/953,781, dated Feb. 27, 2023, 5 pages. |
Office Action received for Australian Patent Application No. 2022204568, dated Mar. 11, 2023, 4 pages. |
Notice of Allowance received for Chinese Patent Application No. 202111611270.2, dated 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, dated Sep. 20, 2022, 2 pages. |
Supplemental Notice of Allowance received for U.S. Appl. No. 17/317,084, dated Sep. 20, 2022, 2 pages. |
Corrected Notice of Allowance received for U.S. Appl. No. 16/143,997, dated Oct. 21, 2021, 2 pages. |
Corrected Notice of Allowance received for U.S. Appl. No. 16/586,154, dated Oct. 27, 2021, 2 pages. |
International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2021/035227, dated Oct. 6, 2021, 17 pages. |
Office Action received for Danish Patent Application No. PA202070619, dated Oct. 14, 2021, 3 pages. |
Office Action received for Korean Patent Application No. 10-2021-7031939, dated Oct. 19, 2021. 11 pages (5 pages of English Translation and 6 pages of Official Copy). |
Notice of Acceptance received for Australian Patent Application No. 2022235614, dated Jul. 6, 2023, 3 pages. |
Notice of Allowance received for Japanese Patent Application No. 2022-502594, dated Jul. 7, 2023, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
Office Action received for Danish Patent Application No. PA202070395, dated Jul. 5, 2023, 6 pages. |
Office Action received for European Patent Application No. 20746438.9, dated Jul. 4, 2023, 7 pages. |
Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/896,791, dated Oct. 12, 2023, 2 pages. |
Non-Final Office Action received for U.S. Appl. No. 17/584,190, dated Oct. 5, 2023, 17 pages. |
Notice of Acceptance received for Australian Patent Application No. 2023212604, dated Oct. 12, 2023, 3 pages. |
Notice of Allowance received for Chinese Patent Application No. 201880032190.1, dated Oct. 7, 2023, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
Office Action received for Australian Patent Application No. 2021283914, dated Sep. 25, 2023, 5 pages. |
Supplemental Notice of Allowance received for U.S. Appl. No. 18/078,444, dated Oct. 16, 2023, 4 pages. |
Decision to Grant received for European Patent Application No. 18727543.3, dated Aug. 18, 2023, 2 pages. |
Examiner-Initiated Interview received for U.S. Appl. No. 17/896,791, dated Sep. 1, 2023, 2 pages. |
Final Office Action received for U.S. Appl. No. 17/031,723, dated Oct. 4, 2023, 13 pages. |
Non-Final Office Action received for U.S. Appl. No. 16/888,780, dated Aug. 17, 2023, 12 pages. |
Non-Final Office Action received for U.S. Appl. No. 17/896,791, dated Aug. 30, 2023, 11 pages. |
Notice of Acceptance received for Australian Patent Application No. 2022204568, dated Jul. 27, 2023, 3 pages. |
Notice of Allowance received for Japanese Patent Application No. 2022-078280, dated 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, dated Aug. 31, 2023, 6 pages. |
Office Action received for Australian Patent Application No. 2021261861, dated Sep. 22, 2023, 5 pages. |
Office Action received for Australian Patent Application No. 2023212604, dated Sep. 4, 2023, 3 pages. |
Office Action received for European Patent Application No. 20760607.0, dated Aug. 17, 2023, 7 pages. |
Office Action received for Japanese Patent Application No. 2022-078280, dated Jul. 24, 2023, 8 pages (4 pages of English Translation and 4 pages of Official Copy). |
Office Action received for Japanese Patent Application No. 2022-131993, dated Sep. 15, 2023, 6 pages (3 pages of English Translation and 3 pages of Official Copy). |
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. |
Alivecor Kardia By , “How to Record a Clean EKG With Kardiaband”, Available Online at: https://www.youtube.com/watch?v =_VIc9VE6VO4&t=2s, Nov. 30, 2017, 2 pages. |
Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/031,723, dated Oct. 31, 2023, 4 pages. |
Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/584,190, dated Dec. 4, 2023, 5 pages. |
Decision on Appeal received for Korean Patent Application No. 10-2020-0124134, dated Oct. 20, 2023, 24 pages (4 pages of English Translation and 20 pages of Official Copy). |
Extended European Search Report received for European Patent Application No. 23189089.8, dated Nov. 23, 2023, 11 pages. |
Final Office Action received for U.S. Appl. No. 17/337,147, dated Oct. 31, 2023, 17 pages. |
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. |
Notice of Allowance received for Japanese Patent Application No. 2022-078277, dated Oct. 27, 2023, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
Notice of Allowance received for Korean Patent Application No. 10-2020-0124134, dated Nov. 21, 2023, 8 pages (2 pages of English Translation and 6 pages of Official Copy). |
Office Action received for Chinese Patent Application No. 202180053264.1, dated Sep. 23, 2023, 17 pages (9 pages of English Translation and 8 pages of Official Copy). |
Office Action received for Danish Patent Application No. PA202070395, dated Nov. 3, 2023, 3 pages. |
Office Action received for European Patent Application No. 20746438.9, dated Oct. 31, 2023, 9 pages. |
Office Action received for European Patent Application No. 20751022.3, dated Oct. 19, 2023, 8 pages. |
Office Action received for European Patent Application No. 20753659.0, dated Oct. 26, 2023, 9 pages. |
Office Action received for Japanese Patent Application No. 2023-110196, dated Nov. 6, 2023, 4 pages (2 pages of English Translation and 2 pages of Official Copy). |
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. |
Corrected Notice of Allowance received for U.S. Appl. No. 17/896,791, dated Jan. 2, 2024, 2 pages. |
Final Office Action received for U.S. Appl. No. 17/952,182, dated Jan. 4, 2024, 9 pages. |
Office Action received for European Patent Application No. 20760607.0, dated Jan. 3, 2024, 7 pages. |
Office Action received for Japanese Patent Application No. 2022-573764, dated Dec. 25, 2023, 8 pages (4 pages of English Translation and 4 pages of Official Copy). |
Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/888,780, dated Dec. 14, 2023, 3 pages. |
International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2023/022549, dated Aug. 1, 2023, 13 pages. |
Notice of Allowance received for Japanese Patent Application No. 2022-131993, dated Dec. 18, 2023, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
Notice of Allowance received for U.S. Appl. No. 17/896,791, dated Dec. 15, 2023, 9 pages. |
Office Action received for Korean Patent Application No. 10-2022-7012608, dated Dec. 5, 2023, 12 pages (5 pages of English Translation and 7 pages of Official Copy). |
Number | Date | Country | |
---|---|---|---|
20210113137 A1 | Apr 2021 | US |
Number | Date | Country | |
---|---|---|---|
62657870 | Apr 2018 | US | |
62657881 | Apr 2018 | US | |
62643699 | Mar 2018 | US | |
62641994 | Mar 2018 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 16144030 | Sep 2018 | US |
Child | 17135710 | US |