Patent Grant
12164748
The present disclosure relates generally to computer user interfaces, and more specifically to techniques for logging user activities during a subset of a recurring time period.
Computer systems can include applications for logging user activities during a subset of a recurring time period. Such systems can receive user input using user interfaces that include one or more graphical elements adapted for use with logging user activities during a subset of a recurring time period.
Some techniques for logging user activities during a subset of a recurring time period 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 logging user activities during a subset of a recurring time period. Such methods and interfaces optionally complement or replace other methods for logging user activities during a subset of a recurring time period. Such methods and interfaces reduce the cognitive burden on a user and produce a more efficient human-machine interface. For battery-operated computing devices, such methods and interfaces conserve power and increase the time between battery charges.
In accordance with some embodiments, a method, performed at a computer system that is in communication with a display generation component and one or more input devices is described. The method includes: displaying, via the display generation component, a task selection user interface with a set of one or more selectable task user interface objects, the set of one or more selectable task user interface objects includes: in accordance with a determination that physiological data for a first subset of a recurring time period meets a first set of criteria, a first selectable task user interface object that corresponds to a first type of user activity to be performed during the first subset of the recurring time period; and in accordance with a determination that physiological data for a second subset of the recurring time period, different from the first subset of the recurring time period, meets the first set of criteria, a second selectable task user interface object that corresponds to a second type of user activity to be performed during the second subset of the recurring time period; while displaying the task selection user interface, receiving, via the one or more input devices, a first set of one or more inputs; and in response to the receiving the first set of one or more inputs: in accordance with a determination that the first set of one or more inputs includes an input selecting the first selectable task user interface object, enabling logging of the first type of user activity during the first subset of the recurring time period; and in accordance with a determination that the first set of one or more inputs includes an input selecting the second selectable task user interface object, enabling logging of the second type of user activity during the second subset of the recurring time period.
In accordance with some embodiments, a non-transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of a computer system that is in communication with a display generation component and one or more input devices is described. The one or more programs include instructions for: displaying, via the display generation component, a task selection user interface with a set of one or more selectable task user interface objects, the set of one or more selectable task user interface objects includes: in accordance with a determination that physiological data for a first subset of a recurring time period meets a first set of criteria, a first selectable task user interface object that corresponds to a first type of user activity to be performed during the first subset of the recurring time period; and in accordance with a determination that physiological data for a second subset of the recurring time period, different from the first subset of the recurring time period, meets the first set of criteria, a second selectable task user interface object that corresponds to a second type of user activity to be performed during the second subset of the recurring time period; while displaying the task selection user interface, receiving, via the one or more input devices, a first set of one or more inputs; and in response to the receiving the first set of one or more inputs: in accordance with a determination that the first set of one or more inputs includes an input selecting the first selectable task user interface object, enabling logging of the first type of user activity during the first subset of the recurring time period; and in accordance with a determination that the first set of one or more inputs includes an input selecting the second selectable task user interface object, enabling logging of the second type of user activity during the second subset of the recurring time period.
In accordance with some embodiments, a transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of a computer system that is in communication with a display generation component and one or more input devices is described. The one or more programs include instructions for: displaying, via the display generation component, a task selection user interface with a set of one or more selectable task user interface objects, the set of one or more selectable task user interface objects includes: in accordance with a determination that physiological data for a first subset of a recurring time period meets a first set of criteria, a first selectable task user interface object that corresponds to a first type of user activity to be performed during the first subset of the recurring time period; and in accordance with a determination that physiological data for a second subset of the recurring time period, different from the first subset of the recurring time period, meets the first set of criteria, a second selectable task user interface object that corresponds to a second type of user activity to be performed during the second subset of the recurring time period; while displaying the task selection user interface, receiving, via the one or more input devices, a first set of one or more inputs; and in response to the receiving the first set of one or more inputs: in accordance with a determination that the first set of one or more inputs includes an input selecting the first selectable task user interface object, enabling logging of the first type of user activity during the first subset of the recurring time period; and in accordance with a determination that the first set of one or more inputs includes an input selecting the second selectable task user interface object, enabling logging of the second type of user activity during the second subset of the recurring time period.
In accordance with some embodiments, a computer system is described. The computer system includes: a display generation component; 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 include instructions for: displaying, via the display generation component, a task selection user interface with a set of one or more selectable task user interface objects, the set of one or more selectable task user interface objects includes: in accordance with a determination that physiological data for a first subset of a recurring time period meets a first set of criteria, a first selectable task user interface object that corresponds to a first type of user activity to be performed during the first subset of the recurring time period; and in accordance with a determination that physiological data for a second subset of the recurring time period, different from the first subset of the recurring time period, meets the first set of criteria, a second selectable task user interface object that corresponds to a second type of user activity to be performed during the second subset of the recurring time period; while displaying the task selection user interface, receiving, via the one or more input devices, a first set of one or more inputs; and in response to the receiving the first set of one or more inputs: in accordance with a determination that the first set of one or more inputs includes an input selecting the first selectable task user interface object, enabling logging of the first type of user activity during the first subset of the recurring time period; and in accordance with a determination that the first set of one or more inputs includes an input selecting the second selectable task user interface object, enabling logging of the second type of user activity during the second subset of the recurring time period.
In accordance with some embodiments, a computer system, including a display generation component and one or more input devices is described. The computer system also includes: means for displaying, via the display generation component, a task selection user interface with a set of one or more selectable task user interface objects, the set of one or more selectable task user interface objects includes: in accordance with a determination that physiological data for a first subset of a recurring time period meets a first set of criteria, a first selectable task user interface object that corresponds to a first type of user activity to be performed during the first subset of the recurring time period; and in accordance with a determination that physiological data for a second subset of the recurring time period, different from the first subset of the recurring time period, meets the first set of criteria, a second selectable task user interface object that corresponds to a second type of user activity to be performed during the second subset of the recurring time period; means for, while displaying the task selection user interface, receiving, via the one or more input devices, a first set of one or more inputs; and means for, in response to the receiving the first set of one or more inputs: in accordance with a determination that the first set of one or more inputs includes an input selecting the first selectable task user interface object, enabling logging of the first type of user activity during the first subset of the recurring time period; and in accordance with a determination that the first set of one or more inputs includes an input selecting the second selectable task user interface object, enabling logging of the second type of user activity during the second subset of the recurring time period.
In accordance with some embodiments, a method, performed at a computer system that is in communication with a display generation component and one or more input devices is described. The method includes: displaying, via the display generation component, a goal creation user interface with a set of one or more selectable goal creation user interface objects, the set of one or more selectable goal creation user interface objects includes: in accordance with a determination that a first type of user activity performed for a first subset of a recurring time period meets a first set of criteria, a first selectable goal creation user interface object that corresponds to the first type of user activity to be performed during the first subset of the recurring time period; and in accordance with a determination that a second type of user activity performed for a second subset of a recurring time period, different from the first subset of the recurring time period, meets a first set of criteria, a second selectable goal creation user interface object that corresponds to the second type of user activity to be performed during the second subset of the recurring time period; while displaying the goal creation user interface, receiving a first set of one or more inputs; and in response to the receiving the first set of one or more inputs: in accordance with a determination that the first set of one or more inputs includes an input selecting the first selectable goal creation user interface object, enabling logging of the first type of user activity during the first subset of the recurring time period for a predetermined duration of time; and in accordance with a determination that the first set of one or more inputs includes an input selecting the second selectable goal creation user interface object, enabling logging of the second type of user activity during the second subset of the recurring time period for the predetermined duration of time.
In accordance with some embodiments, a non-transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of a computer system that is in communication with a display generation component and one or more input devices is described. The one or more programs include instructions for: displaying, via the display generation component, a goal creation user interface with a set of one or more selectable goal creation user interface objects, the set of one or more selectable goal creation user interface objects includes: in accordance with a determination that a first type of user activity performed for a first subset of a recurring time period meets a first set of criteria, a first selectable goal creation user interface object that corresponds to the first type of user activity to be performed during the first subset of the recurring time period; and in accordance with a determination that a second type of user activity performed for a second subset of a recurring time period, different from the first subset of the recurring time period, meets a first set of criteria, a second selectable goal creation user interface object that corresponds to the second type of user activity to be performed during the second subset of the recurring time period; while displaying the goal creation user interface, receiving a first set of one or more inputs; and in response to the receiving the first set of one or more inputs: in accordance with a determination that the first set of one or more inputs includes an input selecting the first selectable goal creation user interface object, enabling logging of the first type of user activity during the first subset of the recurring time period for a predetermined duration of time; and in accordance with a determination that the first set of one or more inputs includes an input selecting the second selectable goal creation user interface object, enabling logging of the second type of user activity during the second subset of the recurring time period for the predetermined duration of time.
In accordance with some embodiments, a transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of a computer system that is in communication with a display generation component and one or more input devices is described. The one or more programs include instructions for: displaying, via the display generation component, a goal creation user interface with a set of one or more selectable goal creation user interface objects, the set of one or more selectable goal creation user interface objects includes: in accordance with a determination that a first type of user activity performed for a first subset of a recurring time period meets a first set of criteria, a first selectable goal creation user interface object that corresponds to the first type of user activity to be performed during the first subset of the recurring time period; and in accordance with a determination that a second type of user activity performed for a second subset of a recurring time period, different from the first subset of the recurring time period, meets a first set of criteria, a second selectable goal creation user interface object that corresponds to the second type of user activity to be performed during the second subset of the recurring time period; while displaying the goal creation user interface, receiving a first set of one or more inputs; and in response to the receiving the first set of one or more inputs: in accordance with a determination that the first set of one or more inputs includes an input selecting the first selectable goal creation user interface object, enabling logging of the first type of user activity during the first subset of the recurring time period for a predetermined duration of time; and in accordance with a determination that the first set of one or more inputs includes an input selecting the second selectable goal creation user interface object, enabling logging of the second type of user activity during the second subset of the recurring time period for the predetermined duration of time.
In accordance with some embodiments, a computer system is described. The computer system includes: a display generation component; 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 include instructions for: displaying, via the display generation component, a goal creation user interface with a set of one or more selectable goal creation user interface objects, the set of one or more selectable goal creation user interface objects includes: in accordance with a determination that a first type of user activity performed for a first subset of a recurring time period meets a first set of criteria, a first selectable goal creation user interface object that corresponds to the first type of user activity to be performed during the first subset of the recurring time period; and in accordance with a determination that a second type of user activity performed for a second subset of a recurring time period, different from the first subset of the recurring time period, meets a first set of criteria, a second selectable goal creation user interface object that corresponds to the second type of user activity to be performed during the second subset of the recurring time period; while displaying the goal creation user interface, receiving a first set of one or more inputs; and in response to the receiving the first set of one or more inputs: in accordance with a determination that the first set of one or more inputs includes an input selecting the first selectable goal creation user interface object, enabling logging of the first type of user activity during the first subset of the recurring time period for a predetermined duration of time; and in accordance with a determination that the first set of one or more inputs includes an input selecting the second selectable goal creation user interface object, enabling logging of the second type of user activity during the second subset of the recurring time period for the predetermined duration of time.
In accordance with some embodiments, a computer system including a display generation component and one or more input devices is described. The computer system also includes: means for displaying, via the display generation component, a goal creation user interface with a set of one or more selectable goal creation user interface objects, the set of one or more selectable goal creation user interface objects includes: in accordance with a determination that a first type of user activity performed for a first subset of a recurring time period meets a first set of criteria, a first selectable goal creation user interface object that corresponds to the first type of user activity to be performed during the first subset of the recurring time period; and in accordance with a determination that a second type of user activity performed for a second subset of a recurring time period, different from the first subset of the recurring time period, meets a first set of criteria, a second selectable goal creation user interface object that corresponds to the second type of user activity to be performed during the second subset of the recurring time period; means for, while displaying the goal creation user interface, receiving a first set of one or more inputs; and means for, in response to the receiving the first set of one or more inputs: in accordance with a determination that the first set of one or more inputs includes an input selecting the first selectable goal creation user interface object, enabling logging of the first type of user activity during the first subset of the recurring time period for a predetermined duration of time; and in accordance with a determination that the first set of one or more inputs includes an input selecting the second selectable goal creation user interface object, enabling logging of the second type of user activity during the second subset of the recurring time period for the predetermined duration of time.
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 logging user activities during a subset of a recurring time period, thereby increasing the effectiveness, efficiency, and user satisfaction with such devices. Such methods and interfaces may complement or replace other methods for logging user activities during a subset of a recurring time period.
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 logging user activities during a subset of a recurring time period. Further, electronic devices should provide displays of logged user activities during a subset of a recurring time period along with other user data in order for a user to determine the effects of performing user activities. Such techniques can reduce the cognitive burden on a user who log user activities during a subset of a recurring time period, 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 some embodiments, the electronic device is a computer system that is in communication (e.g., via wireless communication, via wired communication) with a display generation component. The display generation component is configured to provide visual output, such as display via a CRT display, display via an LED display, or display via image projection. In some embodiments, the display generation component is integrated with the computer system. In some embodiments, the display generation component is separate from the computer system. As used herein, “displaying” content includes causing to display the content (e.g., video data rendered or decoded by display controller 156) by transmitting, via a wired or wireless connection, data (e.g., image data or video data) to an integrated or external display generation component to visually produce the content.
In the discussion that follows, an electronic device that includes a display and a touch-sensitive surface is described. It should be understood, however, that the electronic device optionally includes one or more other physical user-interface devices, such as a physical keyboard, a mouse, and/or a joystick.
The device typically supports a variety of applications, such as one or more of the following: a drawing application, a presentation application, a word processing application, a website creation application, a disk authoring application, a spreadsheet application, a gaming application, a telephone application, a video conferencing application, an e-mail application, an instant messaging application, a workout support application, a photo management application, a digital camera application, a digital video camera application, a web browsing application, a digital music player application, and/or a digital video player application.
The various applications that are executed on the device optionally use at least one common physical user-interface device, such as the touch-sensitive surface. One or more functions of the touch-sensitive surface as well as corresponding information displayed on the device are, optionally, adjusted and/or varied from one application to the next and/or within a respective application. In this way, a common physical architecture (such as the touch-sensitive surface) of the device optionally supports the variety of applications with user interfaces that are intuitive and transparent to the user.
Attention is now directed toward embodiments of portable devices with touch-sensitive displays.
As used in the specification and claims, the term “intensity” of a contact on a touch-sensitive surface refers to the force or pressure (force per unit area) of a contact (e.g., a finger contact) on the touch-sensitive surface, or to a substitute (proxy) for the force or pressure of a contact on the touch-sensitive surface. The intensity of a contact has a range of values that includes at least four distinct values and more typically includes hundreds of distinct values (e.g., at least 256). Intensity of a contact is, optionally, determined (or measured) using various approaches and various sensors or combinations of sensors. For example, one or more force sensors underneath or adjacent to the touch-sensitive surface are, optionally, used to measure force at various points on the touch-sensitive surface. In some implementations, force measurements from multiple force sensors are combined (e.g., a weighted average) to determine an estimated force of a contact. Similarly, a pressure-sensitive tip of a stylus is, optionally, used to determine a pressure of the stylus on the touch-sensitive surface. Alternatively, the size of the contact area detected on the touch-sensitive surface and/or changes thereto, the capacitance of the touch-sensitive surface proximate to the contact and/or changes thereto, and/or the resistance of the touch-sensitive surface proximate to the contact and/or changes thereto are, optionally, used as a substitute for the force or pressure of the contact on the touch-sensitive surface. In some implementations, the substitute measurements for contact force or pressure are used directly to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is described in units corresponding to the substitute measurements). In some implementations, the substitute measurements for contact force or pressure are converted to an estimated force or pressure, and the estimated force or pressure is used to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is a pressure threshold measured in units of pressure). Using the intensity of a contact as an attribute of a user input allows for user access to additional device functionality that may otherwise not be accessible by the user on a reduced-size device with limited real estate for displaying affordances (e.g., on a touch-sensitive display) and/or receiving user input (e.g., via a touch-sensitive display, a touch-sensitive surface, or a physical/mechanical control such as a knob or a button).
As used in the specification and claims, the term “tactile output” refers to physical displacement of a device relative to a previous position of the device, physical displacement of a component (e.g., a touch-sensitive surface) of a device relative to another component (e.g., housing) of the device, or displacement of the component relative to a center of mass of the device that will be detected by a user with the user's sense of touch. For example, in situations where the device or the component of the device is in contact with a surface of a user that is sensitive to touch (e.g., a finger, palm, or other part of a user's hand), the tactile output generated by the physical displacement will be interpreted by the user as a tactile sensation corresponding to a perceived change in physical characteristics of the device or the component of the device. For example, movement of a touch-sensitive surface (e.g., a touch-sensitive display or trackpad) is, optionally, interpreted by the user as a “down click” or “up click” of a physical actuator button. In some cases, a user will feel a tactile sensation such as an “down click” or “up click” even when there is no movement of a physical actuator button associated with the touch-sensitive surface that is physically pressed (e.g., displaced) by the user's movements. As another example, movement of the touch-sensitive surface is, optionally, interpreted or sensed by the user as “roughness” of the touch-sensitive surface, even when there is no change in smoothness of the touch-sensitive surface. While such interpretations of touch by a user will be subject to the individualized sensory perceptions of the user, there are many sensory perceptions of touch that are common to a large majority of users. Thus, when a tactile output is described as corresponding to a particular sensory perception of a user (e.g., an “up click,” a “down click,” “roughness”), unless otherwise stated, the generated tactile output corresponds to physical displacement of the device or a component thereof that will generate the described sensory perception for a typical (or average) user.
It should be appreciated that device 100 is only one example of a portable multifunction device, and that device 100 optionally has more or fewer components than shown, optionally combines two or more components, or optionally has a different configuration or arrangement of the components. The various components shown in
Memory 102 optionally includes high-speed random access memory and optionally also includes non-volatile memory, such as one or more magnetic disk storage devices, flash memory devices, or other non-volatile solid-state memory devices. Memory controller 122 optionally controls access to memory 102 by other components of device 100.
Peripherals interface 118 can be used to couple input and output peripherals of the device to CPU 120 and memory 102. The one or more processors 120 run or execute various software programs and/or sets of instructions stored in memory 102 to perform various functions for device 100 and to process data. In some embodiments, peripherals interface 118, CPU 120, and memory controller 122 are, optionally, implemented on a single chip, such as chip 104. In some other embodiments, they are, optionally, implemented on separate chips.
RF (radio frequency) circuitry 108 receives and sends RF signals, also called electromagnetic signals. RF circuitry 108 converts electrical signals to/from electromagnetic signals and communicates with communications networks and other communications devices via the electromagnetic signals. RF circuitry 108 optionally includes well-known circuitry for performing these functions, including but not limited to an antenna system, an RF transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a CODEC chipset, a subscriber identity module (SIM) card, memory, and so forth. RF circuitry 108 optionally communicates with networks, such as the Internet, also referred to as the World Wide Web (WWW), an intranet and/or a wireless network, such as a cellular telephone network, a wireless local area network (LAN) and/or a metropolitan area network (MAN), and other devices by wireless communication. The RF circuitry 108 optionally includes well-known circuitry for detecting near field communication (NFC) fields, such as by a short-range communication radio. The wireless communication optionally uses any of a plurality of communications standards, protocols, and technologies, including but not limited to Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), high-speed downlink packet access (HSDPA), high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO), HSPA, HSPA+, Dual-Cell HSPA (DC-HSPDA), long term evolution (LTE), near field communication (NFC), wideband code division multiple access (W-CDMA), code division multiple access (CDMA), time division multiple access (TDMA), Bluetooth, Bluetooth Low Energy (BTLE), Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11n, and/or IEEE 802.11ac), voice over Internet Protocol (VoIP), Wi-MAX, a protocol for e-mail (e.g., Internet message access protocol (IMAP) and/or post office protocol (POP)), instant messaging (e.g., extensible messaging and presence protocol (XMPP), Session Initiation Protocol for Instant Messaging and Presence Leveraging Extensions (SIMPLE), Instant Messaging and Presence Service (IMPS)), and/or Short Message Service (SMS), or any other suitable communication protocol, including communication protocols not yet developed as of the filing date of this document.
Audio circuitry 110, speaker 111, and microphone 113 provide an audio interface between a user and device 100. Audio circuitry 110 receives audio data from peripherals interface 118, converts the audio data to an electrical signal, and transmits the electrical signal to speaker 111. Speaker 111 converts the electrical signal to human-audible sound waves. Audio circuitry 110 also receives electrical signals converted by microphone 113 from sound waves. Audio circuitry 110 converts the electrical signal to audio data and transmits the audio data to peripherals interface 118 for processing. Audio data is, optionally, retrieved from and/or transmitted to memory 102 and/or RF circuitry 108 by peripherals interface 118. In some embodiments, audio circuitry 110 also includes a headset jack (e.g., 212,
I/O subsystem 106 couples input/output peripherals on device 100, such as touch screen 112 and other input control devices 116, to peripherals interface 118. I/O subsystem 106 optionally includes display controller 156, optical sensor controller 158, depth camera controller 169, intensity sensor controller 159, haptic feedback controller 161, and one or more input controllers 160 for other input or control devices. The one or more input controllers 160 receive/send electrical signals from/to other input control devices 116. The other input control devices 116 optionally include physical buttons (e.g., push buttons, rocker buttons, etc.), dials, slider switches, joysticks, click wheels, and so forth. In some embodiments, input controller(s) 160 are, optionally, coupled to any (or none) of the following: a keyboard, an infrared port, a USB port, and a pointer device such as a mouse. The one or more buttons (e.g., 208,
A quick press of the push button optionally disengages a lock of touch screen 112 or optionally begins a process that uses gestures on the touch screen to unlock the device, as described in U.S. patent application Ser. No. 11/322,549, “Unlocking a Device by Performing Gestures on an Unlock Image,” filed Dec. 23, 2005, U.S. Pat. No. 7,657,849, which is hereby incorporated by reference in its entirety. A longer press of the push button (e.g., 206) optionally turns power to device 100 on or off. The functionality of one or more of the buttons are, optionally, user-customizable. Touch screen 112 is used to implement virtual or soft buttons and one or more soft keyboards.
Touch-sensitive display 112 provides an input interface and an output interface between the device and a user. Display controller 156 receives and/or sends electrical signals from/to touch screen 112. Touch screen 112 displays visual output to the user. The visual output optionally includes graphics, text, icons, video, and any combination thereof (collectively termed “graphics”). In some embodiments, some or all of the visual output optionally corresponds to user-interface objects.
Touch screen 112 has a touch-sensitive surface, sensor, or set of sensors that accepts input from the user based on haptic and/or tactile contact. Touch screen 112 and display controller 156 (along with any associated modules and/or sets of instructions in memory 102) detect contact (and any movement or breaking of the contact) on touch screen 112 and convert the detected contact into interaction with user-interface objects (e.g., one or more soft keys, icons, web pages, or images) that are displayed on touch screen 112. In an exemplary embodiment, a point of contact between touch screen 112 and the user corresponds to a finger of the user.
Touch screen 112 optionally uses LCD (liquid crystal display) technology, LPD (light emitting polymer display) technology, or LED (light emitting diode) technology, although other display technologies are used in other embodiments. Touch screen 112 and display controller 156 optionally detect contact and any movement or breaking thereof using any of a plurality of touch sensing technologies now known or later developed, including but not limited to capacitive, resistive, infrared, and surface acoustic wave technologies, as well as other proximity sensor arrays or other elements for determining one or more points of contact with touch screen 112. In an exemplary embodiment, projected mutual capacitance sensing technology is used, such as that found in the iPhone® and iPod Touch® from Apple Inc. of Cupertino, California.
A touch-sensitive display in some embodiments of touch screen 112 is, optionally, analogous to the multi-touch sensitive touchpads described in the following U.S. Pat. No. 6,323,846 (Westerman et al.), U.S. Pat. No. 6,570,557 (Westerman et al.), and/or U.S. Pat. No. 6,677,932 (Westerman), and/or U.S. Patent Publication 2002/0015024A1, each of which is hereby incorporated by reference in its entirety. However, touch screen 112 displays visual output from device 100, whereas touch-sensitive touchpads do not provide visual output.
A touch-sensitive display in some embodiments of touch screen 112 is described in the following applications: (1) U.S. patent application Ser. No. 11/381,313, “Multipoint Touch Surface Controller,” filed May 2, 2006; (2) U.S. patent application Ser. No. 10/840,862, “Multipoint Touchscreen,” filed May 6, 2004; (3) U.S. patent application Ser. No. 10/903,964, “Gestures For Touch Sensitive Input Devices,” filed Jul. 30, 2004; (4) U.S. patent application Ser. No. 11/048,264, “Gestures For Touch Sensitive Input Devices,” filed Jan. 31, 2005; (5) U.S. patent application Ser. No. 11/038,590, “Mode-Based Graphical User Interfaces For Touch Sensitive Input Devices,” filed Jan. 18, 2005; (6) U.S. patent application Ser. No. 11/228,758, “Virtual Input Device Placement On A Touch Screen User Interface,” filed Sep. 16, 2005; (7) U.S. patent application Ser. No. 11/228,700, “Operation Of A Computer With A Touch Screen Interface,” filed Sep. 16, 2005; (8) U.S. patent application Ser. No. 11/228,737, “Activating Virtual Keys Of A Touch-Screen Virtual Keyboard,” filed Sep. 16, 2005; and (9) U.S. patent application Ser. No. 11/367,749, “Multi-Functional Hand-Held Device,” filed Mar. 3, 2006. All of these applications are incorporated by reference herein in their entirety.
Touch screen 112 optionally has a video resolution in excess of 100 dpi. In some embodiments, the touch screen has a video resolution of approximately 160 dpi. The user optionally makes contact with touch screen 112 using any suitable object or appendage, such as a stylus, a finger, and so forth. In some embodiments, the user interface is designed to work primarily with finger-based contacts and gestures, which can be less precise than stylus-based input due to the larger area of contact of a finger on the touch screen. In some embodiments, the device translates the rough finger-based input into a precise pointer/cursor position or command for performing the actions desired by the user.
In some embodiments, in addition to the touch screen, device 100 optionally includes a touchpad for activating or deactivating particular functions. In some embodiments, the touchpad is a touch-sensitive area of the device that, unlike the touch screen, does not display visual output. The touchpad is, optionally, a touch-sensitive surface that is separate from touch screen 112 or an extension of the touch-sensitive surface formed by the touch screen.
Device 100 also includes power system 162 for powering the various components. Power system 162 optionally includes a power management system, one or more power sources (e.g., battery, alternating current (AC)), a recharging system, a power failure detection circuit, a power converter or inverter, a power status indicator (e.g., a light-emitting diode (LED)) and any other components associated with the generation, management and distribution of power in portable devices.
Device 100 optionally also includes one or more optical sensors 164.
Device 100 optionally also includes one or more depth camera sensors 175.
Device 100 optionally also includes one or more contact intensity sensors 165.
Device 100 optionally also includes one or more proximity sensors 166.
Device 100 optionally also includes one or more tactile output generators 167.
Device 100 optionally also includes one or more accelerometers 168.
In some embodiments, the software components stored in memory 102 include operating system 126, communication module (or set of instructions) 128, contact/motion module (or set of instructions) 130, graphics module (or set of instructions) 132, text input module (or set of instructions) 134, Global Positioning System (GPS) module (or set of instructions) 135, and applications (or sets of instructions) 136. Furthermore, in some embodiments, memory 102 (
Operating system 126 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, iOS, WINDOWS, or an embedded operating system such as VxWorks) includes various software components and/or drivers for controlling and managing general system tasks (e.g., memory management, storage device control, power management, etc.) and facilitates communication between various hardware and software components.
Communication module 128 facilitates communication with other devices over one or more external ports 124 and also includes various software components for handling data received by RF circuitry 108 and/or external port 124. External port 124 (e.g., Universal Serial Bus (USB), FIREWIRE, etc.) is adapted for coupling directly to other devices or indirectly over a network (e.g., the Internet, wireless LAN, etc.). In some embodiments, the external port is a multi-pin (e.g., 30-pin) connector that is the same as, or similar to and/or compatible with, the 30-pin connector used on iPod® (trademark of Apple Inc.) devices.
Contact/motion module 130 optionally detects contact with touch screen 112 (in conjunction with display controller 156) and other touch-sensitive devices (e.g., a touchpad or physical click wheel). Contact/motion module 130 includes various software components for performing various operations related to detection of contact, such as determining if contact has occurred (e.g., detecting a finger-down event), determining an intensity of the contact (e.g., the force or pressure of the contact or a substitute for the force or pressure of the contact), determining if there is movement of the contact and tracking the movement across the touch-sensitive surface (e.g., detecting one or more finger-dragging events), and determining if the contact has ceased (e.g., detecting a finger-up event or a break in contact). Contact/motion module 130 receives contact data from the touch-sensitive surface. Determining movement of the point of contact, which is represented by a series of contact data, optionally includes determining speed (magnitude), velocity (magnitude and direction), and/or an acceleration (a change in magnitude and/or direction) of the point of contact. These operations are, optionally, applied to single contacts (e.g., one finger contacts) or to multiple simultaneous contacts (e.g., “multitouch”/multiple finger contacts). In some embodiments, contact/motion module 130 and display controller 156 detect contact on a touchpad.
In some embodiments, contact/motion module 130 uses a set of one or more intensity thresholds to determine whether an operation has been performed by a user (e.g., to determine whether a user has “clicked” on an icon). In some embodiments, at least a subset of the intensity thresholds are determined in accordance with software parameters (e.g., the intensity thresholds are not determined by the activation thresholds of particular physical actuators and can be adjusted without changing the physical hardware of device 100). For example, a mouse “click” threshold of a trackpad or touch screen display can be set to any of a large range of predefined threshold values without changing the trackpad or touch screen display hardware. Additionally, in some implementations, a user of the device is provided with software settings for adjusting one or more of the set of intensity thresholds (e.g., by adjusting individual intensity thresholds and/or by adjusting a plurality of intensity thresholds at once with a system-level click “intensity” parameter).
Contact/motion module 130 optionally detects a gesture input by a user. Different gestures on the touch-sensitive surface have different contact patterns (e.g., different motions, timings, and/or intensities of detected contacts). Thus, a gesture is, optionally, detected by detecting a particular contact pattern. For example, detecting a finger tap gesture includes detecting a finger-down event followed by detecting a finger-up (liftoff) event at the same position (or substantially the same position) as the finger-down event (e.g., at the position of an icon). As another example, detecting a finger swipe gesture on the touch-sensitive surface includes detecting a finger-down event followed by detecting one or more finger-dragging events, and subsequently followed by detecting a finger-up (liftoff) event.
Graphics module 132 includes various known software components for rendering and displaying graphics on touch screen 112 or other display, including components for changing the visual impact (e.g., brightness, transparency, saturation, contrast, or other visual property) of graphics that are displayed. As used herein, the term “graphics” includes any object that can be displayed to a user, including, without limitation, text, web pages, icons (such as user-interface objects including soft keys), digital images, videos, animations, and the like.
In some embodiments, graphics module 132 stores data representing graphics to be used. Each graphic is, optionally, assigned a corresponding code. Graphics module 132 receives, from applications etc., one or more codes specifying graphics to be displayed along with, if necessary, coordinate data and other graphic property data, and then generates screen image data to output to display controller 156.
Haptic feedback module 133 includes various software components for generating instructions used by tactile output generator(s) 167 to produce tactile outputs at one or more locations on device 100 in response to user interactions with device 100.
Text input module 134, which is, optionally, a component of graphics module 132, provides soft keyboards for entering text in various applications (e.g., contacts module 137, e-mail client module 140, IM module 141, browser module 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 module 138 for use in location-based dialing; to camera module 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 module 138, video conference module 139, e-mail client module 140, or IM module 141; and so forth.
In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, telephone module 138 are optionally, used to enter a sequence of characters corresponding to a telephone number, access one or more telephone numbers in contacts module 137, modify a telephone number that has been entered, dial a respective telephone number, conduct a conversation, and disconnect or hang up when the conversation is completed. As noted above, the wireless communication optionally uses any of a plurality of communications standards, protocols, and technologies.
In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch screen 112, display controller 156, optical sensor 164, optical sensor controller 158, contact/motion module 130, graphics module 132, text input module 134, contacts module 137, and telephone module 138, video conference module 139 includes executable instructions to initiate, conduct, and terminate a video conference between a user and one or more other participants in accordance with user instructions.
In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, e-mail client module 140 includes executable instructions to create, send, receive, and manage e-mail in response to user instructions. In conjunction with image management module 144, e-mail client module 140 makes it very easy to create and send e-mails with still or video images taken with camera module 143.
In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, the instant messaging module 141 includes executable instructions to enter a sequence of characters corresponding to an instant message, to modify previously entered characters, to transmit a respective instant message (for example, using a Short Message Service (SMS) or Multimedia Message Service (MMS) protocol for telephony-based instant messages or using XMPP, SIMPLE, or IMPS for Internet-based instant messages), to receive instant messages, and to view received instant messages. In some embodiments, transmitted and/or received instant messages optionally include graphics, photos, audio files, video files and/or other attachments as are supported in an MMS and/or an Enhanced Messaging Service (EMS). As used herein, “instant messaging” refers to both telephony-based messages (e.g., messages sent using SMS or MMS) and Internet-based messages (e.g., messages sent using XMPP, SIMPLE, or IMPS).
In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, GPS module 135, map module 154, and music player module, workout support module 142 includes executable instructions to create workouts (e.g., with time, distance, and/or calorie burning goals); communicate with workout sensors (sports devices); receive workout sensor data; calibrate sensors used to monitor a workout; select and play music for a workout; and display, store, and transmit workout data.
In conjunction with touch screen 112, display controller 156, optical sensor(s) 164, optical sensor controller 158, contact/motion module 130, graphics module 132, and image management module 144, camera module 143 includes executable instructions to capture still images or video (including a video stream) and store them into memory 102, modify characteristics of a still image or video, or delete a still image or video from memory 102.
In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, and camera module 143, image management module 144 includes executable instructions to arrange, modify (e.g., edit), or otherwise manipulate, label, delete, present (e.g., in a digital slide show or album), and store still and/or video images.
In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, browser module 147 includes executable instructions to browse the Internet in accordance with user instructions, including searching, linking to, receiving, and displaying web pages or portions thereof, as well as attachments and other files linked to web pages.
In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, e-mail client module 140, and browser module 147, calendar module 148 includes executable instructions to create, display, modify, and store calendars and data associated with calendars (e.g., calendar entries, to-do lists, etc.) in accordance with user instructions.
In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, and browser module 147, widget modules 149 are mini-applications that are, optionally, downloaded and used by a user (e.g., weather widget 149-1, stocks widget 149-2, calculator widget 149-3, alarm clock widget 149-4, and dictionary widget 149-5) or created by the user (e.g., user-created widget 149-6). In some embodiments, a widget includes an HTML (Hypertext Markup Language) file, a CSS (Cascading Style Sheets) file, and a JavaScript file. In some embodiments, a widget includes an XML (Extensible Markup Language) file and a JavaScript file (e.g., Yahoo! Widgets).
In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, and browser module 147, the widget creator module 150 are, optionally, used by a user to create widgets (e.g., turning a user-specified portion of a web page into a widget).
In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, search module 151 includes executable instructions to search for text, music, sound, image, video, and/or other files in memory 102 that match one or more search criteria (e.g., one or more user-specified search terms) in accordance with user instructions.
In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, and browser module 147, video and music player module 152 includes executable instructions that allow the user to download and play back recorded music and other sound files stored in one or more file formats, such as MP3 or AAC files, and executable instructions to display, present, or otherwise play back videos (e.g., on touch screen 112 or on an external, connected display via external port 124). In some embodiments, device 100 optionally includes the functionality of an MP3 player, such as an iPod (trademark of Apple Inc.).
In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, notes module 153 includes executable instructions to create and manage notes, to-do lists, and the like in accordance with user instructions.
In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, GPS module 135, and browser module 147, map module 154 are, optionally, used to receive, display, modify, and store maps and data associated with maps (e.g., driving directions, data on stores and other points of interest at or near a particular location, and other location-based data) in accordance with user instructions.
In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, text input module 134, e-mail client module 140, and browser module 147, online video module 155 includes instructions that allow the user to access, browse, receive (e.g., by streaming and/or download), play back (e.g., on the touch screen or on an external, connected display via external port 124), send an e-mail with a link to a particular online video, and otherwise manage online videos in one or more file formats, such as H.264. In some embodiments, instant messaging module 141, rather than e-mail client module 140, is used to send a link to a particular online video. Additional description of the online video application can be found in U.S. Provisional Patent Application No. 60/936,562, “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos,” filed Jun. 20, 2007, and U.S. patent application Ser. No. 11/968,067, “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos,” filed Dec. 31, 2007, the contents of which are hereby incorporated by reference in their entirety.
Each of the above-identified modules and applications corresponds to a set of executable instructions for performing one or more functions described above and the methods described in this application (e.g., the computer-implemented methods and other information processing methods described herein). These modules (e.g., sets of instructions) need not be implemented as separate software programs, procedures, or modules, and thus various subsets of these modules are, optionally, combined or otherwise rearranged in various embodiments. For example, video player module is, optionally, combined with music player module into a single module (e.g., video and music player module 152,
In some embodiments, device 100 is a device where operation of a predefined set of functions on the device is performed exclusively through a touch screen and/or a touchpad. By using a touch screen and/or a touchpad as the primary input control device for operation of device 100, the number of physical input control devices (such as push buttons, dials, and the like) on device 100 is, optionally, reduced.
The predefined set of functions that are performed exclusively through a touch screen and/or a touchpad optionally include navigation between user interfaces. In some embodiments, the touchpad, when touched by the user, navigates device 100 to a main, home, or root menu from any user interface that is displayed on device 100. In such embodiments, a “menu button” is implemented using a touchpad. In some other embodiments, the menu button is a physical push button or other physical input control device instead of a touchpad.
Event sorter 170 receives event information and determines the application 136-1 and application view 191 of application 136-1 to which to deliver the event information. Event sorter 170 includes event monitor 171 and event dispatcher module 174. In some embodiments, application 136-1 includes application internal state 192, which indicates the current application view(s) displayed on touch-sensitive display 112 when the application is active or executing. In some embodiments, device/global internal state 157 is used by event sorter 170 to determine which application(s) is (are) currently active, and application internal state 192 is used by event sorter 170 to determine application views 191 to which to deliver event information.
In some embodiments, application internal state 192 includes additional information, such as one or more of: resume information to be used when application 136-1 resumes execution, user interface state information that indicates information being displayed or that is ready for display by application 136-1, a state queue for enabling the user to go back to a prior state or view of application 136-1, and a redo/undo queue of previous actions taken by the user.
Event monitor 171 receives event information from peripherals interface 118. Event information includes information about a sub-event (e.g., a user touch on touch-sensitive display 112, as part of a multi-touch gesture). Peripherals interface 118 transmits information it receives from I/O subsystem 106 or a sensor, such as proximity sensor 166, accelerometer(s) 168, and/or microphone 113 (through audio circuitry 110). Information that peripherals interface 118 receives from I/O subsystem 106 includes information from touch-sensitive display 112 or a touch-sensitive surface.
In some embodiments, event monitor 171 sends requests to the peripherals interface 118 at predetermined intervals. In response, peripherals interface 118 transmits event information. In other embodiments, peripherals interface 118 transmits event information only when there is a significant event (e.g., receiving an input above a predetermined noise threshold and/or for more than a predetermined duration).
In some embodiments, event sorter 170 also includes a hit view determination module 172 and/or an active event recognizer determination module 173.
Hit view determination module 172 provides software procedures for determining where a sub-event has taken place within one or more views when touch-sensitive display 112 displays more than one view. Views are made up of controls and other elements that a user can see on the display.
Another aspect of the user interface associated with an application is a set of views, sometimes herein called application views or user interface windows, in which information is displayed and touch-based gestures occur. The application views (of a respective application) in which a touch is detected optionally correspond to programmatic levels within a programmatic or view hierarchy of the application. For example, the lowest level view in which a touch is detected is, optionally, called the hit view, and the set of events that are recognized as proper inputs are, optionally, determined based, at least in part, on the hit view of the initial touch that begins a touch-based gesture.
Hit view determination module 172 receives information related to sub-events of a touch-based gesture. When an application has multiple views organized in a hierarchy, hit view determination module 172 identifies a hit view as the lowest view in the hierarchy which should handle the sub-event. In most circumstances, the hit view is the lowest level view in which an initiating sub-event occurs (e.g., the first sub-event in the sequence of sub-events that form an event or potential event). Once the hit view is identified by the hit view determination module 172, the hit view typically receives all sub-events related to the same touch or input source for which it was identified as the hit view.
Active event recognizer determination module 173 determines which view or views within a view hierarchy should receive a particular sequence of sub-events. In some embodiments, active event recognizer determination module 173 determines that only the hit view should receive a particular sequence of sub-events. In other embodiments, active event recognizer determination module 173 determines that all views that include the physical location of a sub-event are actively involved views, and therefore determines that all actively involved views should receive a particular sequence of sub-events. In other embodiments, even if touch sub-events were entirely confined to the area associated with one particular view, views higher in the hierarchy would still remain as actively involved views.
Event dispatcher module 174 dispatches the event information to an event recognizer (e.g., event recognizer 180). In embodiments including active event recognizer determination module 173, event dispatcher module 174 delivers the event information to an event recognizer determined by active event recognizer determination module 173. In some embodiments, event dispatcher module 174 stores in an event queue the event information, which is retrieved by a respective event receiver 182.
In some embodiments, operating system 126 includes event sorter 170. Alternatively, application 136-1 includes event sorter 170. In yet other embodiments, event sorter 170 is a stand-alone module, or a part of another module stored in memory 102, such as contact/motion module 130.
In some embodiments, application 136-1 includes a plurality of event handlers 190 and one or more application views 191, each of which includes instructions for handling touch events that occur within a respective view of the application's user interface. Each application view 191 of the application 136-1 includes one or more event recognizers 180. Typically, a respective application view 191 includes a plurality of event recognizers 180. In other embodiments, one or more of event recognizers 180 are part of a separate module, such as a user interface kit or a higher level object from which application 136-1 inherits methods and other properties. In some embodiments, a respective event handler 190 includes one or more of: data updater 176, object updater 177, GUI updater 178, and/or event data 179 received from event sorter 170. Event handler 190 optionally utilizes or calls data updater 176, object updater 177, or GUI updater 178 to update the application internal state 192. Alternatively, one or more of the application views 191 include one or more respective event handlers 190. Also, in some embodiments, one or more of data updater 176, object updater 177, and GUI updater 178 are included in a respective application view 191.
A respective event recognizer 180 receives event information (e.g., event data 179) from event sorter 170 and identifies an event from the event information. Event recognizer 180 includes event receiver 182 and event comparator 184. In some embodiments, event recognizer 180 also includes at least a subset of: metadata 183, and event delivery instructions 188 (which optionally include sub-event delivery instructions).
Event receiver 182 receives event information from event sorter 170. The event information includes information about a sub-event, for example, a touch or a touch movement. Depending on the sub-event, the event information also includes additional information, such as location of the sub-event. When the sub-event concerns motion of a touch, the event information optionally also includes speed and direction of the sub-event. In some embodiments, events include rotation of the device from one orientation to another (e.g., from a portrait orientation to a landscape orientation, or vice versa), and the event information includes corresponding information about the current orientation (also called device attitude) of the device.
Event comparator 184 compares the event information to predefined event or sub-event definitions and, based on the comparison, determines an event or sub-event, or determines or updates the state of an event or sub-event. In some embodiments, event comparator 184 includes event definitions 186. Event definitions 186 contain definitions of events (e.g., predefined sequences of sub-events), for example, event 1 (187-1), event 2 (187-2), and others. In some embodiments, sub-events in an event (187) include, for example, touch begin, touch end, touch movement, touch cancellation, and multiple touching. In one example, the definition for event 1 (187-1) is a double tap on a displayed object. The double tap, for example, comprises a first touch (touch begin) on the displayed object for a predetermined phase, a first liftoff (touch end) for a predetermined phase, a second touch (touch begin) on the displayed object for a predetermined phase, and a second liftoff (touch end) for a predetermined phase. In another example, the definition for event 2 (187-2) is a dragging on a displayed object. The dragging, for example, comprises a touch (or contact) on the displayed object for a predetermined phase, a movement of the touch across touch-sensitive display 112, and liftoff of the touch (touch end). In some embodiments, the event also includes information for one or more associated event handlers 190.
In some embodiments, event definition 187 includes a definition of an event for a respective user-interface object. In some embodiments, event comparator 184 performs a hit test to determine which user-interface object is associated with a sub-event. For example, in an application view in which three user-interface objects are displayed on touch-sensitive display 112, when a touch is detected on touch-sensitive display 112, event comparator 184 performs a hit test to determine which of the three user-interface objects is associated with the touch (sub-event). If each displayed object is associated with a respective event handler 190, the event comparator uses the result of the hit test to determine which event handler 190 should be activated. For example, event comparator 184 selects an event handler associated with the sub-event and the object triggering the hit test.
In some embodiments, the definition for a respective event (187) also includes delayed actions that delay delivery of the event information until after it has been determined whether the sequence of sub-events does or does not correspond to the event recognizer's event type.
When a respective event recognizer 180 determines that the series of sub-events do not match any of the events in event definitions 186, the respective event recognizer 180 enters an event impossible, event failed, or event ended state, after which it disregards subsequent sub-events of the touch-based gesture. In this situation, other event recognizers, if any, that remain active for the hit view continue to track and process sub-events of an ongoing touch-based gesture.
In some embodiments, a respective event recognizer 180 includes metadata 183 with configurable properties, flags, and/or lists that indicate how the event delivery system should perform sub-event delivery to actively involved event recognizers. In some embodiments, metadata 183 includes configurable properties, flags, and/or lists that indicate how event recognizers interact, or are enabled to interact, with one another. In some embodiments, metadata 183 includes configurable properties, flags, and/or lists that indicate whether sub-events are delivered to varying levels in the view or programmatic hierarchy.
In some embodiments, a respective event recognizer 180 activates event handler 190 associated with an event when one or more particular sub-events of an event are recognized. In some embodiments, a respective event recognizer 180 delivers event information associated with the event to event handler 190. Activating an event handler 190 is distinct from sending (and deferred sending) sub-events to a respective hit view. In some embodiments, event recognizer 180 throws a flag associated with the recognized event, and event handler 190 associated with the flag catches the flag and performs a predefined process.
In some embodiments, event delivery instructions 188 include sub-event delivery instructions that deliver event information about a sub-event without activating an event handler. Instead, the sub-event delivery instructions deliver event information to event handlers associated with the series of sub-events or to actively involved views. Event handlers associated with the series of sub-events or with actively involved views receive the event information and perform a predetermined process.
In some embodiments, data updater 176 creates and updates data used in application 136-1. For example, data updater 176 updates the telephone number used in contacts module 137, or stores a video file used in video player module. In some embodiments, object updater 177 creates and updates objects used in application 136-1. For example, object updater 177 creates a new user-interface object or updates the position of a user-interface object. GUI updater 178 updates the GUI. For example, GUI updater 178 prepares display information and sends it to graphics module 132 for display on a touch-sensitive display.
In some embodiments, event handler(s) 190 includes or has access to data updater 176, object updater 177, and GUI updater 178. In some embodiments, data updater 176, object updater 177, and GUI updater 178 are included in a single module of a respective application 136-1 or application view 191. In other embodiments, they are included in two or more software modules.
It shall be understood that the foregoing discussion regarding event handling of user touches on touch-sensitive displays also applies to other forms of user inputs to operate multifunction devices 100 with input devices, not all of which are initiated on touch screens. For example, mouse movement and mouse button presses, optionally coordinated with single or multiple keyboard presses or holds; contact movements such as taps, drags, scrolls, etc. on touchpads; pen stylus inputs; movement of the device; oral instructions; detected eye movements; biometric inputs; and/or any combination thereof are optionally utilized as inputs corresponding to sub-events which define an event to be recognized.
Device 100 optionally also include one or more physical buttons, such as “home” or menu button 204. As described previously, menu button 204 is, optionally, used to navigate to any application 136 in a set of applications that are, optionally, executed on device 100. Alternatively, in some embodiments, the menu button is implemented as a soft key in a GUI displayed on touch screen 112.
In some embodiments, device 100 includes touch screen 112, menu button 204, push button 206 for powering the device on/off and locking the device, volume adjustment button(s) 208, subscriber identity module (SIM) card slot 210, headset jack 212, and docking/charging external port 124. Push button 206 is, optionally, used to turn the power on/off on the device by depressing the button and holding the button in the depressed state for a predefined time interval; to lock the device by depressing the button and releasing the button before the predefined time interval has elapsed; and/or to unlock the device or initiate an unlock process. In an alternative embodiment, device 100 also accepts verbal input for activation or deactivation of some functions through microphone 113. Device 100 also, optionally, includes one or more contact intensity sensors 165 for detecting intensity of contacts on touch screen 112 and/or one or more tactile output generators 167 for generating tactile outputs for a user of device 100.
Each of the above-identified elements in
Attention is now directed towards embodiments of user interfaces that are, optionally, implemented on, for example, portable multifunction device 100.
It should be noted that the icon labels illustrated in
Although some of the examples that follow will be given with reference to inputs on touch screen display 112 (where the touch-sensitive surface and the display are combined), in some embodiments, the device detects inputs on a touch-sensitive surface that is separate from the display, as shown in
Additionally, while the following examples are given primarily with reference to finger inputs (e.g., finger contacts, finger tap gestures, finger swipe gestures), it should be understood that, in some embodiments, one or more of the finger inputs are replaced with input from another input device (e.g., a mouse-based input or stylus input). For example, a swipe gesture is, optionally, replaced with a mouse click (e.g., instead of a contact) followed by movement of the cursor along the path of the swipe (e.g., instead of movement of the contact). As another example, a tap gesture is, optionally, replaced with a mouse click while the cursor is located over the location of the tap gesture (e.g., instead of detection of the contact followed by ceasing to detect the contact). Similarly, when multiple user inputs are simultaneously detected, it should be understood that multiple computer mice are, optionally, used simultaneously, or a mouse and finger contacts are, optionally, used simultaneously.
Exemplary techniques for detecting and processing touch intensity are found, for example, in related applications: International Patent Application Serial No. PCT/US2013/040061, titled “Device, Method, and Graphical User Interface for Displaying User Interface Objects Corresponding to an Application,” filed May 8, 2013, published as WIPO Publication No. WO/2013/169849, and International Patent Application Serial No. PCT/US2013/069483, titled “Device, Method, and Graphical User Interface for Transitioning Between Touch Input to Display Output Relationships,” filed Nov. 11, 2013, published as WIPO Publication No. WO/2014/105276, each of which is hereby incorporated by reference in their entirety.
In some embodiments, device 500 has one or more input mechanisms 506 and 508. Input mechanisms 506 and 508, if included, can be physical. Examples of physical input mechanisms include push buttons and rotatable mechanisms. In some embodiments, device 500 has one or more attachment mechanisms. Such attachment mechanisms, if included, can permit attachment of device 500 with, for example, hats, eyewear, earrings, necklaces, shirts, jackets, bracelets, watch straps, chains, trousers, belts, shoes, purses, backpacks, and so forth. These attachment mechanisms permit device 500 to be worn by a user.
Input mechanism 508 is, optionally, a microphone, in some examples. Personal electronic device 500 optionally includes various sensors, such as GPS sensor 532, accelerometer 534, directional sensor 540 (e.g., compass), gyroscope 536, motion sensor 538, and/or a combination thereof, all of which can be operatively connected to I/O section 514.
Memory 518 of personal electronic device 500 can include one or more non-transitory computer-readable storage mediums, for storing computer-executable instructions, which, when executed by one or more computer processors 516, for example, can cause the computer processors to perform the techniques described below, including processes 700-800 (
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 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.
Attention is now directed towards embodiments of user interfaces (“UI”) and associated processes that are implemented on an electronic device, such as portable multifunction device 100, device 300, or device 500.
Hourly log user interface 610 further includes log region 614. Log region 614 includes meal logging affordance 614a, activity logging affordance 614b, and mood logging affordance 614c. Hourly log user interface 610 also includes hours tab affordance 616a and settings tab affordance 616b. In some embodiments, selection of setting tab affordance 616b causes device 600 to display a settings user interface. In some embodiments, the settings user interface includes a variety of options, some of which could be reviewing collected data, adjusting time frames, viewing policies, customizing measurement units.
As shown by time indication 604 in
In
Log entry creation user interface 618 includes item selection region 620. In this example, item selection region 620 displays common foods that a user can select for logging. In some embodiments, when logging an activity, item selection region 620 includes selectable affordances corresponding to various activities (e.g., walking, biking, meditating). In some embodiments, when logging a mood, item selection region 620 includes selectable affordances corresponding to various moods/sentiments (e.g., feelings (e.g., anxious, excited, tired)). Device 600 receives tap inputs 622a and 622b corresponding to selection of bread affordance 620a and salad affordance 620b, respectively. In some embodiments, only one selectable affordance within the item selection region 620 can be selected while creating a log entry. In some embodiments, one or more selectable affordance within the item selection region 620 can be selected while creating a log entry. As shown in
In
In
In addition to generating log entry 614d, device 600 displays meal glyph 612d along chart line 612c. Meal glyph 612d is displayed at a time, e.g., 12:00, along chart region 612b, corresponding to the time that the meal was consumed. In some embodiments, if the log entry was an activity or mood log entry, a corresponding activity or mood glyph would be displayed along chart line 612c. In some embodiments, meal, activity, and mood glyphs are selectable user interface objects, that, when selected, causes device 600 to display a log detail user interface corresponding to the log entry.
Turning now to
Ten days after onboarding, on August 11, as shown in
As shown in
Baseline summary user interface 630 of
As shown in
In
Baseline summary user interface 630 further includes a portion of overnight baseline affordance 636, which in analogous to morning baseline affordance 632 and evening baseline affordance 634. Overnight baseline affordance 636 corresponds to physiological data (e.g., blood glucose measurements) received by device 600 during the overnight quadrant (e.g., period of time overnight (e.g., from 22:00 to 04:00)) of the baseline phase. In some embodiments, after receiving a scroll input, device 600 displays baseline summary user interface 630 showing the entire overnight baseline affordance 636 and a selectable view all overnight data affordance, analogous to selectable view all morning data affordance 632c and selectable view all evening data affordance 634c.
In the example described, device 600 displays affordances corresponding to physiological data received during the morning, evening, and overnight quadrants during the baseline phase (e.g., an initial period of time (e.g., ten days, a week)) and does not display an affordance corresponding to physiological data received during the afternoon quadrant (e.g., period of time in the afternoon (e.g., from 10:00 to 16:00)). In some embodiments, device 600 determines, based on the received physiological data, the one or more portions of the day having the most elevated blood glucose measurements (e.g., during the baseline phase) and displays baseline affordances accordingly. In some embodiments, the portions of the day having the most elevated blood glucose measurements, and therefore are displayed by device 600, contain the highest measurements (e.g., the three highest measurements as between the four quadrants of the day). In some embodiments, the portions of the day that are displayed by device 600 have the highest elevation values. In some embodiments, the portions of the day that are displayed by device 600 have more time spent in an elevated measurement state. Therefore, in some embodiments, device 600 displays a combination of the morning, afternoon, evening, and overnight quadrants. In some embodiments, device 600 displays affordances corresponding to each quadrant (e.g., morning, afternoon, evening, overnight).
As shown in
In response to detecting swipe input 650, device 600 displays another portion of task selection user interface 642, as shown in
In
In response to receiving tap input 654 to complete action phase set up, device 600 displays progress user interface 656, as shown in
Progress user interface 656 of
In
In response to receiving tap input 664 at activity logging affordance 614b, device 600 initiates logging of an activity, as shown by log entry creation user interface 618 in
In the example detailed in
As shown in
As shown in
In
As shown in
Device 600 receives tap input 676 corresponding to selection of “BIKING” log entry 614h. As shown in
In
Log detail user interface 678 includes selectable exit affordance 678c. Device 600 detects tap input 680 corresponding to selection of exit affordance 678c, and in response, device 600 ceases display of log detail user interface 678 and displays progress user interface 656, as shown in
In
As shown in
As shown in
Turning now to
As shown in
In
In
In
In
In this example, in
Turning now to
As shown in
At the end of the week, on August 24 as shown in
In
As shown in
In
As shown in
In some embodiments, the electronic device (e.g., 600) is a computer system. The computer system is optionally in communication (e.g., wired communication, wireless communication) with a display generation component (e.g., 602) and with one or more input devices (e.g., 112, 160, 602). The display generation component is configured to provide visual output, such as display via a CRT display, display via an LED display, or display via image projection. In some embodiments, the display generation component is integrated with the computer system. In some embodiments, the display generation component is separate from the computer system. The one or more input devices are configured to receive input, such as a touch-sensitive surface receiving user input. In some embodiments, the one or more input devices are integrated with the computer system. In some embodiments, the one or more input devices are separate from the computer system. Thus, the computer system can transmit, via a wired or wireless connection, data (e.g., image data or video data) to an integrated or external display generation component to visually produce the content (e.g., using a display device) and can receive, a wired or wireless connection, input from the one or more input devices.
As described below, method 700 provides an intuitive way for logging user activities during a subset of a recurring time period. The method reduces the cognitive burden on a user for logging user activities during a subset of a recurring time period, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a user to logging user activities during a subset of a recurring time period faster and more efficiently conserves power and increases the time between battery charges.
The computer system displays (706), via the display generation component (e.g., 602), a task selection user interface (e.g., 642) with a set of one or more selectable task user interface objects (e.g., 644, 646, 648). The set of one or more selectable task user interface objects includes, in accordance with a determination (708) that physiological data (e.g., 634a) (e.g., data pertaining to blood glucose levels (e.g., a quantification of elevated blood glucose levels for a duration of time); baseline blood glucose measurements) for a first subset of a recurring time period (e.g., the time of day that device 600 received data to display line chart 634a) (e.g., a particular quadrant of time each day (e.g., 6 hours of a day, morning, afternoon, evening, overnight); a day (e.g., Monday, Tuesday) within a week)) meets a first set of criteria (e.g., as illustrated by the elevation value scale of 630a, 634b). In some embodiments, the first set of criteria includes a criterion that is met when the physiological data exceeds a threshold value (e.g., a blood glucose level exceeds a threshold blood glucose level)), a first selectable task user interface object (e.g., 646a-646c) that corresponds to a first type of user activity (e.g., 646a (“TRY AN ACTIVITY”), 646b (“EAT CARBS”), 646c (“AVOID SNACKS”)) to be performed during the first subset of the recurring time period (e.g., the time period specified in 658 of
The computer system, while displaying the task selection user interface (e.g., 642), receives (712), via the one or more input devices (e.g., 112, 160), a first set of one or more inputs (e.g., 652a, 652b, 654) (e.g., tap inputs).
The computer system, in response to the receiving (714) the first set of one or more inputs and in accordance with a determination that the first set of one or more inputs includes an input (e.g., 652a) selecting the first selectable task user interface object (e.g., 646a), enables (716) logging of (e.g., recording; tracking; logging via user inputs) the first type of user activity (e.g., 646a) during the first subset of the recurring time period (e.g., the time periods specified in 646 and 660 of
The computer system, prior to displaying the task selection user interface (e.g., 642), receives (702) (e.g., via one or more physiological sensors in communication with the computer system (e.g., integrated into the computer system; in communication with the computer system); a data transfer from another computer system)) a first set of physiological data (e.g., as represented by 612c) for a first predetermined period of time (e.g., from August 1 to August 10 as described with reference to
The computer system, after receiving the first set of physiological data for the first predetermined period of time (e.g., in response to completing receiving of the first set of physiological data for a predetermined period of time (e.g., at the end of the predetermined time period)), displays (704) a data summary user interface (e.g., 630) that includes a first representation (e.g., 632a, 632a) (e.g., a graphical user interface object; a representation in a graph; a numerical value) of physiological data of the first set of physiological data for the first predetermined period of time that exceeded a first threshold value (e.g., a value below 632a and 634b). In some embodiments, the first representation of physiological data includes an indication of the subset of a recurring time period (e.g., the 6-hour quadrant of the day) during which the physiological data was obtained). In some embodiments, the data summary user interface includes a second representation of physiological data of the first set of physiological data for the predetermined period of time that exceeded the threshold value. In some embodiments, the second representation of physiological data corresponds to data from a different subset of the recurring time period (e.g., from a different quadrant of the day) than the data that corresponds to the first representation of physiological data). Displaying a first representation of physiological data that exceeded a threshold value provides the user with additional feedback as a subset of the received data. 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 computer system, wherein prior to receiving (e.g., prior to receiving all of) the first set of physiological data for the first predetermined period of time, the task selection user interface (e.g., 642) is not available for display (e.g., is locked; is not available for display at the request of a user), in response to receiving (e.g., receiving all of) the first set of physiological data for the first predetermined period of time, provides the task selection user interface (e.g., 642) for display (e.g., by displaying notification 626) (e.g., making the task selection user interface available for display (e.g., from a previously unavailable state)). In some embodiments, in response to receiving the first set of physiological data for the predetermined period of time, displaying at least a first interface of a set of user interfaces that includes the task selection user interface. Providing the task selection user interface for display in response to the receipt of data controls access to an interface that operates based on whether that data is available yet. Performing an optimized operation when a set of conditions has been met without requiring further user input enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
In some embodiments, the first type of user activity to be performed during the first subset of the recurring time period is performance of a physical activity (e.g., 614g, 614h) (e.g., exercise) or consumption of a food or beverage (e.g., the log entries listed below 648a in
The computer system, after enabling logging of the first type of user activity during the first subset of the recurring time period and after enabling logging of the second type of user activity during the second subset of the recurring time period, displays a progress user interface (e.g., 656) (e.g., an interface that includes representations of completed user activity(s) that have been enabled for logging) that includes, in accordance with a determination that a first instance (e.g., “WALKING” of 614g, “BIKING” of 614h) of the first type of user activity (e.g., 646a) (e.g., physical activity (e.g., exercise); consumption of food or beverage (e.g., eating carbs last)) has been logged during the first subset of the recurring time period (e.g., the time period specified in 658 of
The computer system, after enabling logging of the first type of user activity during the first subset of the recurring time period and after enabling logging of the second type of user activity during the second subset of the recurring time period, displays a progress user interface (e.g., 656) (e.g., an interface that includes representations of completed user activity(s) that have been enabled for logging) that includes, in accordance with a determination that a first instance (e.g., “SUGAR FREE CHEESECAKE” of
The computer system, after enabling logging of the first type of user activity during the first subset of the recurring time period, displays a first representation (e.g., 614h) (e.g., a user interface object (e.g., a selectable interface object (e.g., an affordance)) of a logged instance (e.g., “BIKING” at 18:30) of the first type of user activity (e.g., 646a).
The computer system receives a first input (e.g., 676) (e.g., a tap) that corresponds to the representation of the logged instance of the first type of user activity.
The computer system, in response to receiving the first user input, displays a comparison user interface (e.g., 678) that includes the first representation (e.g., a graphical user interface object; a representation in a graph; a numerical value) of physiological data of the first set of physiological data for the first predetermined period of time that exceeded the first threshold value (e.g., 634a).
The computer system, in response to receiving the first user input, displays a comparison user interface (e.g., 678) that includes a second representation (e.g., a graphical user interface object; a representation in a graph) of physiological data of a second set of physiological data (e.g., data collected during the action phase; data different than the first set of physiological data) that corresponds to (e.g., that was collected in a period of time during which the logged instance of the first type of activity was performed) the logged instance of the first type of user activity (e.g., 678b).
The computer system, in response to receiving the first user input, displays a comparison user interface (e.g., 678) that includes a second representation (e.g., that is graphical similar or identical to the first representation) of the logged instance of the first type of user activity (e.g., the activity glyph along 678b of
The computer system, after the first type of user activity has been logged a number of times that exceeds a second threshold value (e.g., the three logged entries listed below 648a in
The computer system receives, via the one or more input devices (e.g., 112, 160), a second set of one or more inputs (e.g., 682, 686a, 686b) (e.g., tap inputs), wherein the second set of one or more inputs includes an input (e.g., 682) corresponding to the first selectable user interface object (e.g., a tap on the plus button). In some embodiments, the second set of one or inputs includes one or more inputs identifying a type of user activity to be performed during the first subset of the recurring time period.
The computer system, in response to receiving the second set of one or more inputs, enables logging of a third type of user activity (e.g., 648c) during the first subset of the recurring time period (e.g., the time period specified in 660 of
The computer system, after enabling logging of the first type of user activity during the first subset of the recurring time period, receives a third set of one or more inputs (e.g., 664, 666a, 666b, 670a, 670b), wherein the third set of one or more inputs includes an input (e.g., 664) to initiate a log entry (e.g., in response to 664 at 614b in
The computer system, after receiving the input to initiate the log entry, displays a selectable confirmation user interface object (e.g., 646a, 648a as shown on 668 of
The computer system, after receiving the input to initiate the log entry and in response to receiving the third set of one or more inputs, in accordance with a determination that the third set of one or more inputs includes selection (e.g., 670a) of the selectable confirmation user interface object for the first type of user activity, logs an instance of the first type of user activity (e.g., 614g).
The computer system, after receiving the input to initiate the log entry and in response to receiving the third set of one or more inputs, in accordance with a determination that the third set of one or more inputs does not include selection selectable confirmation user interface object for the first type of user activity, logs an event that is not an instance of the first type of user activity (e.g., similar to the “BAGEL” log entry of
In some embodiments, enabling logging of the first type of user activity during the first subset of the recurring time period includes enabling logging of the first type of user activity during the first subset of the recurring time period for a second predetermined period of time (e.g., as represented by “DAYS REMAINING” in 656a, from August 11 to August 18 as described with reference to
The computer system, after the second predetermined time period ends, provides a goal creation user interface (e.g., 692) for display (e.g., making a goal creation user interface available for display (e.g., from a previously unavailable state)), wherein the goal creation user interface is unavailable for display prior to completion of the second predetermined period of time. In some embodiments, the goal creation user interface is an interface that corresponds to method 800. Providing a goal creation user interface for display after a predetermined time period ends permits access to the interface at a point in time when the function of the interface is relevant. Performing an optimized operation when a set of conditions has been met without requiring further user input enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
Note that details of the processes described above with respect to method 700 (e.g.,
As described below, method 800 provides an intuitive way for logging user activities during a subset of a recurring time period. The method reduces the cognitive burden on a user for logging user activities during a subset of a recurring time period, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a user to logging user activities during a subset of a recurring time period faster and more efficiently conserves power and increases the time between battery charges.
The computer system displays (802), via the display generation component (e.g., 602), a goal creation user interface (e.g., 692, 696) with a set of one or more selectable goal creation user interface objects (e.g., 646a, 648a, 648c). The set of one or more selectable user interface objects includes, in accordance with a determination (804) that a first type of user activity (e.g., the activity described with respect to 646a) (e.g., physical activity (e.g., exercise); eating or drinking certain foods) performed for a first subset of a recurring time period (e.g., the time period specified in 658 of
The computer system, while displaying the goal creation user interface (e.g., 692), receives (818) a first set of one or more inputs (e.g., 694a, 694b, 698a, 698b, 698c) (e.g., taps).
The computer system, in response to the receiving (820) the first set of one or more inputs and in accordance with a determination that the first set of one or more inputs includes an input (e.g., 646a) selecting the first selectable goal creation user interface object (e.g., 646a), enables (822) logging (e.g., recording; tracking; logging via user inputs) of the first type of user activity during the first subset of the recurring time period (e.g., during future occurrences of the first subset of the recurring time period) for a predetermined duration of time (e.g., 656c) (e.g., a week, 10 days).
The computer system, in response to the receiving (820) the first set of one or more inputs and in accordance with a determination that the first set of one or more inputs includes an input selecting the second selectable goal creation user interface object (e.g., a tap at 648a in
In some embodiments, the goal creation user interface (e.g., 696) includes (808) (e.g., concurrently, non-concurrently) a set (810) of one or more selectable user interface objects (e.g., 696a) (e.g., a text field; selectable predefined options) that, when selected, configure (e.g., identify; detail; set) a subtype (e.g., “YOGA” as discussed at
In some embodiments, the goal creation user interface includes (808) a set (816) of one or more selectable user interface objects (e.g., 696c) (e.g., a text field; selectable predefined options) that, when selected, configure (e.g., identify; detail; set) a target number of times (e.g., “5 TIMES” as discussed at
In some embodiments, the first set of criteria is satisfied when a user activity of a given type has been performed (e.g., performed and logged) at least once during a preceding predetermined period of time (e.g., 614g, 614h, the log entries listed within 660) (e.g., an action phase). In some embodiments, the first set of criteria are met when physiological data indicates that a user activity of a given type had a target (e.g., positive) effect on a physiological parameter (e.g., blood glucose levels). In some embodiments, the goal creation user interface (e.g., 692) includes, for each given type of activity that met the first set of criteria, a selectable goal creation user interface object (e.g., 646a, 648a, 648c as discussed at
The computer system, after enabling logging of the first type of user activity (e.g., 6102) during the first subset of the recurring time for the predetermined duration of time, displays a representation (e.g., 6102a-6102e) (e.g., an indication; a graphical user interface object) of the target number of times (e.g., “5 TIMES” as discussed at
The computer system, after enabling logging of the first type of user activity (e.g., 6102) during the first subset of the recurring time for the predetermined duration of time and after the end of the predetermined duration of time (e.g., on August 24 at
The computer system, after receiving the first set of one or more user inputs (e.g., after selection of 696g) and, in some embodiments, in accordance with a determination that the feedback regarding the first type of user activity satisfies a first set of feedback criteria (e.g., the feedback is of a first type (e.g., negative feedback), displays a set of one or more selectable user interface objects (e.g., analogous to 696a, 696b, and 696c at
The computer system, after enabling logging of the first type of user activity during the first subset of the recurring time for the predetermined duration of time and after the end of the predetermined duration of time (e.g., on August 24 at
The computer system, after receiving the second set of one or more user inputs (e.g., after selection of 696e) and, in some embodiments, in accordance with a determination that the feedback regarding the first type of user activity satisfies a first set of feedback criteria (e.g., the feedback is of a first type (e.g., negative feedback), displays a set of one or more selectable user interface objects (e.g., analogous to 648a and 648b at
The computer system, after enabling logging of the first type of user activity during the first subset of the recurring time for the predetermined duration of time, displays a progress user interface (e.g., 656) (e.g., an interface that includes representations of completed user activity(s) that have been enabled for logging), wherein the progress user interface includes: a first selectable user interface object (e.g., 656b) that corresponds to the preceding predetermined period of time (e.g., the action phase), that when selected, displays representations of logged instances of the first type of user activity for the preceding predetermined period of time (e.g., 614g, 614h, the log entries listed within 660 at
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 logged user activities during a subset of a recurring time period 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, twitter IDs, home addresses, data or records relating to a user's health or level of fitness (e.g., vital signs measurements, medication information, exercise information), date of birth, or any other identifying or personal information.
The present disclosure recognizes that the use of such personal information data, in the present technology, can be used to the benefit of users. For example, the personal information data can be used to deliver targeted content based on the logged user activities during a subset of a recurring time period that is of greater interest to the user. Accordingly, use of such personal information data enables users to have calculated control of the delivered content. Further, other uses for personal information data that benefit the user are also contemplated by the present disclosure. For instance, health and fitness data may be used to provide insights into a user's general wellness, or may be used as positive feedback to individuals using technology to pursue wellness goals.
The present disclosure contemplates that the entities responsible for the collection, analysis, disclosure, transfer, storage, or other use of such personal information data will comply with well-established privacy policies and/or privacy practices. In particular, such entities should implement and consistently use privacy policies and practices that are generally recognized as meeting or exceeding industry or governmental requirements for maintaining personal information data private and secure. Such policies should be easily accessible by users, and should be updated as the collection and/or use of data changes. Personal information from users should be collected for legitimate and reasonable uses of the entity and not shared or sold outside of those legitimate uses. Further, such collection/sharing should occur after receiving the informed consent of the users. Additionally, such entities should consider taking any needed steps for safeguarding and securing access to such personal information data and ensuring that others with access to the personal information data adhere to their privacy policies and procedures. Further, such entities can subject themselves to evaluation by third parties to certify their adherence to widely accepted privacy policies and practices. In addition, policies and practices should be adapted for the particular types of personal information data being collected and/or accessed and adapted to applicable laws and standards, including jurisdiction-specific considerations. For instance, in the US, collection of or access to certain health data may be governed by federal and/or state laws, such as the Health Insurance Portability and Accountability Act (HIPAA); whereas health data in other countries may be subject to other regulations and policies and should be handled accordingly. Hence different privacy practices should be maintained for different personal data types in each country.
Despite the foregoing, the present disclosure also contemplates embodiments in which users selectively block the use of, or access to, personal information data. That is, the present disclosure contemplates that hardware and/or software elements can be provided to prevent or block access to such personal information data. For example, in the case of logging user activities during a subset of a recurring time period, the present technology can be configured to allow users to select to “opt in” or “opt out” of participation in the collection of personal information data during registration for services or anytime thereafter. In another example, users can select not to provide data for logging user activities during a subset of a recurring time period. In yet another example, users can select to limit the length of time data is maintained or entirely prohibit the development of a baseline profile. In addition to providing “opt in” and “opt out” options, the present disclosure contemplates providing notifications relating to the access or use of personal information. For instance, a user may be notified upon downloading an app that their personal information data will be accessed and then reminded again just before personal information data is accessed by the app.
Moreover, it is the intent of the present disclosure that personal information data should be managed and handled in a way to minimize risks of unintentional or unauthorized access or use. Risk can be minimized by limiting the collection of data and deleting data once it is no longer needed. In addition, and when applicable, including in certain health related applications, data de-identification can be used to protect a user's privacy. De-identification may be facilitated, when appropriate, by removing specific identifiers (e.g., date of birth, etc.), controlling the amount or specificity of data stored (e.g., collecting location data a city level rather than at an address level), controlling how data is stored (e.g., aggregating data across users), and/or other methods.
Therefore, although the present disclosure broadly covers use of personal information data to implement one or more various disclosed embodiments, the present disclosure also contemplates that the various embodiments can also be implemented without the need for accessing such personal information data. That is, the various embodiments of the present technology are not rendered inoperable due to the lack of all or a portion of such personal information data. For example, 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 publicly available information.
This application is a continuation of U.S. patent application Ser. No. 17/952,053, filed Sep. 23, 2022, entitled “USER INTERFACES FOR LOGGING USER ACTIVITIES,” which is a continuation of U.S. patent application Ser. No. 16/953,781, now U.S. Pat. No. 11,698,710, filed Nov. 20, 2020, entitled “USER INTERFACES FOR LOGGING USER ACTIVITIES,” which claims priority to U.S. Provisional Application Ser. No. 63/072,889, filed Aug. 31, 2020, entitled “USER INTERFACES FOR LOGGING USER ACTIVITIES,” the contents of which are hereby incorporated by reference in their entirety.
| Number | Name | Date | Kind |
|---|---|---|---|
| 5515344 | Ng | May 1996 | A |
| 5515344 | Ng | May 1996 | A |
| 5642731 | Kehr | Jul 1997 | A |
| 5642731 | Kehr | Jul 1997 | A |
| 6416471 | Kumar et al. | Jul 2002 | B1 |
| 6416471 | Kumar et al. | Jul 2002 | B1 |
| 6600696 | Lynn | Jul 2003 | B1 |
| 6600696 | Lynn | Jul 2003 | B1 |
| 6705972 | Takano et al. | Mar 2004 | B1 |
| 6705972 | Takano et al. | Mar 2004 | B1 |
| 6873709 | Hou | Mar 2005 | B2 |
| 6950839 | Green et al. | Sep 2005 | B1 |
| 6950839 | Green et al. | Sep 2005 | B1 |
| 7111157 | Hooper | Sep 2006 | B1 |
| 7128693 | Brown et al. | Oct 2006 | B2 |
| 7128693 | Brown et al. | Oct 2006 | B2 |
| 7166078 | Saini et al. | Jan 2007 | B2 |
| 7166078 | Saini et al. | Jan 2007 | B2 |
| 7313435 | Nakada et al. | Dec 2007 | B2 |
| 7739148 | Suzuki et al. | Jun 2010 | B2 |
| 7739148 | Suzuki et al. | Jun 2010 | B2 |
| 7771320 | Riley et al. | Aug 2010 | B2 |
| 8045739 | Paludan-Mueller et al. | Oct 2011 | B2 |
| 8152694 | Srinivasan et al. | Apr 2012 | B2 |
| 8200323 | Dibenedetto et al. | Jun 2012 | B2 |
| 8321006 | Snyder et al. | Nov 2012 | B1 |
| 8321006 | Snyder et al. | Nov 2012 | B1 |
| 8475339 | Hwang et al. | Jul 2013 | B2 |
| 8475339 | Hwang et al. | Jul 2013 | B2 |
| 8676170 | Porrati et al. | Mar 2014 | B2 |
| 8676170 | Porrati et al. | Mar 2014 | B2 |
| 8725527 | Kahn et al. | May 2014 | B1 |
| 8725527 | Kahn et al. | May 2014 | B1 |
| 8758262 | Rhee et al. | Jun 2014 | B2 |
| 8758262 | Rhee et al. | Jun 2014 | B2 |
| 8784115 | Chuang | Jul 2014 | B1 |
| 8784115 | Chuang | Jul 2014 | B1 |
| 8888707 | Shirasaki et al. | Nov 2014 | B2 |
| 8888707 | Shirasaki et al. | Nov 2014 | B2 |
| 9011292 | Weast et al. | Apr 2015 | B2 |
| 9026927 | Brumback et al. | May 2015 | B2 |
| 9026927 | Brumback et al. | May 2015 | B2 |
| 9224291 | Moll-carrillo et al. | Dec 2015 | B2 |
| 9224291 | Moll-carrillo et al. | Dec 2015 | B2 |
| 9490763 | Taniguchi et al. | Nov 2016 | B2 |
| 9579060 | Lisy et al. | Feb 2017 | B1 |
| 9579060 | Lisy et al. | Feb 2017 | B1 |
| 9589445 | White et al. | Mar 2017 | B2 |
| 9589445 | White et al. | Mar 2017 | B2 |
| 9606695 | Matas | Mar 2017 | B2 |
| 9672715 | Roberts et al. | Jun 2017 | B2 |
| 9672715 | Roberts et al. | Jun 2017 | B2 |
| 9712629 | Molettiere et al. | Jul 2017 | B2 |
| 9712629 | Molettiere et al. | Jul 2017 | B2 |
| 9721066 | Funaro et al. | Aug 2017 | B1 |
| 9721066 | Funaro et al. | Aug 2017 | B1 |
| 9730621 | Cohen et al. | Aug 2017 | B2 |
| 9730621 | Cohen et al. | Aug 2017 | B2 |
| 9740825 | Sansale et al. | Aug 2017 | B2 |
| 9801562 | Host-madsen | Oct 2017 | B1 |
| 9801562 | Host-madsen | Oct 2017 | B1 |
| 9808206 | Zhao et al. | Nov 2017 | B1 |
| 9808206 | Zhao et al. | Nov 2017 | B1 |
| 9813642 | Chen et al. | Nov 2017 | B1 |
| 9813642 | Chen et al. | Nov 2017 | B1 |
| 9940682 | Hoffman et al. | Apr 2018 | B2 |
| 9940682 | Hoffman et al. | Apr 2018 | B2 |
| 10004451 | Proud | Jun 2018 | B1 |
| 10010750 | Tropper | Jul 2018 | B2 |
| 10150002 | Kass et al. | Dec 2018 | B2 |
| 10175781 | Karagozler et al. | Jan 2019 | B2 |
| 10226195 | Briante et al. | Mar 2019 | B2 |
| 10254911 | Yang | Apr 2019 | B2 |
| 10275262 | Bull et al. | Apr 2019 | B1 |
| 10339830 | Han et al. | Jul 2019 | B2 |
| 10365811 | Robinson et al. | Jul 2019 | B2 |
| 10437962 | Soni et al. | Oct 2019 | B2 |
| 10445702 | Hunt | Oct 2019 | B1 |
| 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 |
| 10692593 | Young et al. | Jun 2020 | B1 |
| 10762990 | Schilling et al. | Sep 2020 | B1 |
| 10764700 | Felton | Sep 2020 | B1 |
| 10796549 | Roberts et al. | Oct 2020 | B2 |
| 11073942 | Lee et al. | Jul 2021 | B2 |
| 11103161 | Williams et al. | Aug 2021 | B2 |
| 11107580 | Felton et al. | Aug 2021 | B1 |
| 11209957 | Dryer et al. | Dec 2021 | B2 |
| 20010039503 | Chan et al. | Nov 2001 | A1 |
| 20020095292 | Mittal et al. | Jul 2002 | A1 |
| 20030126114 | Tedesco | Jul 2003 | A1 |
| 20030130867 | Coelho et al. | Jul 2003 | A1 |
| 20030140044 | Mok et al. | Jul 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 |
| 20040034288 | Hennessy et al. | Feb 2004 | A1 |
| 20040077958 | Kato et al. | Apr 2004 | A1 |
| 20040081024 | Weng | Apr 2004 | A1 |
| 20040190729 | Yonovitz et al. | Sep 2004 | A1 |
| 20040193069 | Takehara | Sep 2004 | A1 |
| 20040210117 | Ueno et al. | Oct 2004 | A1 |
| 20040236189 | Hawthorne et al. | Nov 2004 | A1 |
| 20050010117 | Agutter et al. | Jan 2005 | A1 |
| 20050027208 | Shiraishi et al. | Feb 2005 | A1 |
| 20050075214 | Brown et al. | Apr 2005 | A1 |
| 20050079905 | Martens | Apr 2005 | A1 |
| 20050149362 | Peterson et al. | Jul 2005 | A1 |
| 20050165627 | Fotsch et al. | Jul 2005 | A1 |
| 20050187794 | Kimak | Aug 2005 | A1 |
| 20050228735 | Duquette | Oct 2005 | A1 |
| 20050244013 | Battenberg et al. | Nov 2005 | A1 |
| 20050272564 | Pyles et al. | Dec 2005 | A1 |
| 20060074863 | Kishore et al. | Apr 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 |
| 20060182287 | Schulein et al. | Aug 2006 | A1 |
| 20060205564 | Peterson | Sep 2006 | A1 |
| 20060210096 | Stokes et al. | Sep 2006 | A1 |
| 20060235319 | Belohlavek et al. | Oct 2006 | A1 |
| 20060274908 | Choi | Dec 2006 | A1 |
| 20070016440 | Stroup | Jan 2007 | A1 |
| 20070033066 | Ammer et al. | Feb 2007 | A1 |
| 20070056727 | Newman | Mar 2007 | A1 |
| 20070179434 | Weinert et al. | Aug 2007 | A1 |
| 20070250505 | Yang et al. | Oct 2007 | A1 |
| 20070250613 | Gulledge | Oct 2007 | A1 |
| 20070274531 | Camp | Nov 2007 | A1 |
| 20080005106 | Schumacher et al. | Jan 2008 | A1 |
| 20080012701 | Kass et al. | Jan 2008 | A1 |
| 20080021884 | Jones et al. | Jan 2008 | A1 |
| 20080058626 | Miyata et al. | Mar 2008 | A1 |
| 20080133742 | Southiere et al. | Jun 2008 | A1 |
| 20080146892 | Leboeuf et al. | Jun 2008 | A1 |
| 20080159547 | Schuler et al. | Jul 2008 | A1 |
| 20080172361 | Wong et al. | Jul 2008 | A1 |
| 20080200312 | Tagliabue | Aug 2008 | A1 |
| 20080205660 | Goldstein | Aug 2008 | A1 |
| 20080228045 | Gao et al. | Sep 2008 | A1 |
| 20080240519 | Nagamitsu | Oct 2008 | A1 |
| 20080243885 | Harger et al. | Oct 2008 | A1 |
| 20080300110 | Smith et al. | Dec 2008 | A1 |
| 20090007596 | Goldstein et al. | Jan 2009 | A1 |
| 20090052677 | Smith | Feb 2009 | A1 |
| 20090065578 | Peterson et al. | Mar 2009 | A1 |
| 20090105552 | Nishiyama et al. | Apr 2009 | A1 |
| 20090118100 | Oliver et al. | May 2009 | A1 |
| 20090172773 | Moore | Jul 2009 | A1 |
| 20090180631 | Michael et al. | Jul 2009 | A1 |
| 20090210078 | Crowley | Aug 2009 | A1 |
| 20090216556 | Martin et al. | Aug 2009 | A1 |
| 20090235253 | Hope | Sep 2009 | A1 |
| 20090240521 | Simons et al. | 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 |
| 20090307105 | Lemay et al. | Dec 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 |
| 20100062905 | Rottler et al. | Mar 2010 | A1 |
| 20100073162 | Johnson et al. | Mar 2010 | A1 |
| 20100076331 | Chan et al. | Mar 2010 | A1 |
| 20100094658 | Mok et al. | Apr 2010 | A1 |
| 20100099539 | Haataja | Apr 2010 | A1 |
| 20100119093 | Uzuanis et al. | May 2010 | A1 |
| 20100121700 | Wigder et al. | May 2010 | A1 |
| 20100132044 | Kogan et al. | May 2010 | A1 |
| 20100145220 | Van | Jun 2010 | A1 |
| 20100150378 | Lee et al. | Jun 2010 | A1 |
| 20100161353 | Mayaud | Jun 2010 | A1 |
| 20100222645 | Nadler et al. | Sep 2010 | A1 |
| 20100292600 | Dibenedetto et al. | Nov 2010 | A1 |
| 20100312138 | Regas | Dec 2010 | A1 |
| 20110010195 | Cohn | Jan 2011 | A1 |
| 20110057799 | Taneff | Mar 2011 | A1 |
| 20110066051 | Moon et al. | Mar 2011 | A1 |
| 20110071765 | Yodfat et al. | Mar 2011 | A1 |
| 20110093481 | Hussam | Apr 2011 | A1 |
| 20110098928 | Hoffman et al. | Apr 2011 | A1 |
| 20110106557 | Gazula | May 2011 | A1 |
| 20110119088 | Gunn et al. | May 2011 | A1 |
| 20110152656 | Weinert et al. | Jun 2011 | A1 |
| 20110166631 | Breining | Jul 2011 | A1 |
| 20110195383 | Weiss | Aug 2011 | A1 |
| 20110214162 | Brakensiek et al. | Sep 2011 | A1 |
| 20110218407 | Haberman et al. | Sep 2011 | A1 |
| 20110245623 | Chutani et al. | Oct 2011 | A1 |
| 20110307821 | Martens | Dec 2011 | A1 |
| 20120002510 | Berman, Jr. | Jan 2012 | A1 |
| 20120023586 | Flickner et al. | Jan 2012 | A1 |
| 20120029303 | Shaya | Feb 2012 | A1 |
| 20120038651 | Case et al. | Feb 2012 | A1 |
| 20120041767 | Hoffman et al. | 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 |
| 20120185267 | Kamen et al. | Jul 2012 | A1 |
| 20120203124 | Lim | Aug 2012 | A1 |
| 20120215115 | Takahashi | Aug 2012 | A1 |
| 20120232929 | Experton | 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 |
| 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 |
| 20130065569 | Leipzig et al. | Mar 2013 | A1 |
| 20130072765 | Kahn et al. | Mar 2013 | A1 |
| 20130073933 | Eppolito | Mar 2013 | A1 |
| 20130073960 | Eppolito et al. | Mar 2013 | A1 |
| 20130095459 | Tran | Apr 2013 | A1 |
| 20130110264 | Weast et al. | May 2013 | A1 |
| 20130114100 | Torii et al. | May 2013 | A1 |
| 20130115583 | Gordon et al. | May 2013 | A1 |
| 20130144653 | Poe et al. | Jun 2013 | A1 |
| 20130151285 | Mclaren et al. | Jun 2013 | A1 |
| 20130158416 | Hatlestad et al. | Jun 2013 | A1 |
| 20130191647 | Ferrara 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 |
| 20130231575 | Erkkila et al. | Sep 2013 | A1 |
| 20130231947 | Shusterman | Sep 2013 | A1 |
| 20130262155 | Hinkamp | Oct 2013 | A1 |
| 20130268398 | Agami et al. | Oct 2013 | A1 |
| 20130274628 | Fausti et al. | Oct 2013 | A1 |
| 20130304510 | Chen et al. | Nov 2013 | A1 |
| 20130304616 | Raleigh et al. | Nov 2013 | A1 |
| 20130317380 | Liley et al. | Nov 2013 | A1 |
| 20130325396 | Yuen et al. | Dec 2013 | A1 |
| 20130325493 | Wong et al. | Dec 2013 | A1 |
| 20130325511 | Neagle et al. | Dec 2013 | A1 |
| 20130332286 | Medelius et al. | Dec 2013 | A1 |
| 20140005947 | Jeon et al. | Jan 2014 | A1 |
| 20140019162 | Skowronski et al. | Jan 2014 | A1 |
| 20140037107 | Marino et al. | Feb 2014 | A1 |
| 20140038781 | Foley et al. | Feb 2014 | A1 |
| 20140046926 | Walton | Feb 2014 | A1 |
| 20140073486 | Ahmed et al. | Mar 2014 | A1 |
| 20140081118 | Reinhold et al. | Mar 2014 | A1 |
| 20140088995 | Damani | Mar 2014 | A1 |
| 20140100885 | Stern | Apr 2014 | A1 |
| 20140127996 | Park et al. | May 2014 | A1 |
| 20140129007 | Utter, II | 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 |
| 20140184422 | Mensinger et al. | Jul 2014 | A1 |
| 20140189510 | Ozcan | Jul 2014 | A1 |
| 20140197946 | Park et al. | Jul 2014 | A1 |
| 20140200426 | Taub et al. | Jul 2014 | A1 |
| 20140240122 | Roberts et al. | Aug 2014 | A1 |
| 20140240349 | Tuukkanen | Aug 2014 | A1 |
| 20140266776 | Miller et al. | Sep 2014 | A1 |
| 20140275852 | Hong et al. | Sep 2014 | A1 |
| 20140275856 | Kohlrausch et al. | Sep 2014 | A1 |
| 20140278220 | Yuen | Sep 2014 | A1 |
| 20140288390 | Hong et al. | Sep 2014 | A1 |
| 20140297217 | Yuen | Oct 2014 | A1 |
| 20140327527 | Goldstein et al. | Nov 2014 | A1 |
| 20140336796 | Agnew | Nov 2014 | A1 |
| 20140344687 | Durham et al. | Nov 2014 | A1 |
| 20140354494 | Katz | Dec 2014 | A1 |
| 20140358012 | Richards et al. | Dec 2014 | A1 |
| 20140371887 | Hoffman et al. | Dec 2014 | A1 |
| 20150057942 | Self et al. | Feb 2015 | A1 |
| 20150073285 | Albert et al. | Mar 2015 | A1 |
| 20150081210 | Yeh et al. | Mar 2015 | A1 |
| 20150089536 | Byerley | Mar 2015 | A1 |
| 20150099991 | Yamaguchi et al. | Apr 2015 | A1 |
| 20150100348 | Connery et al. | Apr 2015 | A1 |
| 20150106025 | Keller et al. | Apr 2015 | A1 |
| 20150110277 | Pidgeon et al. | Apr 2015 | A1 |
| 20150110279 | Tejerina | Apr 2015 | A1 |
| 20150120633 | Norlander et al. | Apr 2015 | A1 |
| 20150124067 | Bala et al. | May 2015 | A1 |
| 20150125832 | Tran | May 2015 | A1 |
| 20150127365 | Rizvi et al. | May 2015 | A1 |
| 20150142689 | Squires | May 2015 | A1 |
| 20150164349 | Gopalakrishnan et al. | Jun 2015 | A1 |
| 20150173686 | Furuta et al. | Jun 2015 | A1 |
| 20150179186 | Swierk et al. | Jun 2015 | A1 |
| 20150181314 | Swanson | Jun 2015 | A1 |
| 20150182843 | Esposito et al. | Jul 2015 | A1 |
| 20150185967 | Ly et al. | Jul 2015 | A1 |
| 20150193217 | Xiang et al. | Jul 2015 | A1 |
| 20150196804 | Koduri et al. | Jul 2015 | A1 |
| 20150205947 | Berman et al. | Jul 2015 | A1 |
| 20150216448 | Lotan et al. | Aug 2015 | A1 |
| 20150217163 | Amis et al. | Aug 2015 | A1 |
| 20150220883 | Bfar et al. | Aug 2015 | A1 |
| 20150230717 | Wan | Aug 2015 | A1 |
| 20150261918 | Thornbury, Jr. | Sep 2015 | A1 |
| 20150262499 | Wicka et al. | Sep 2015 | A1 |
| 20150286800 | Kanagala et al. | Oct 2015 | A1 |
| 20150287421 | Benway et al. | Oct 2015 | A1 |
| 20150288797 | Vincent | Oct 2015 | A1 |
| 20150288944 | Nistico et al. | Oct 2015 | A1 |
| 20150289823 | Rack-gomer et al. | Oct 2015 | A1 |
| 20150297134 | Albert et al. | Oct 2015 | A1 |
| 20150324751 | Orenstein et al. | Nov 2015 | A1 |
| 20150347690 | Keen et al. | Dec 2015 | A1 |
| 20150347711 | Soli et al. | Dec 2015 | A1 |
| 20150350799 | Schnaare et al. | Dec 2015 | A1 |
| 20150350861 | Soli et al. | Dec 2015 | A1 |
| 20160000379 | Pougatchev et al. | Jan 2016 | A1 |
| 20160019360 | Pahwa et al. | Jan 2016 | A1 |
| 20160055420 | Karanam et al. | Feb 2016 | A1 |
| 20160058313 | Sato | Mar 2016 | A1 |
| 20160058336 | Blahnik et al. | Mar 2016 | A1 |
| 20160058337 | Blahnik et al. | Mar 2016 | A1 |
| 20160062540 | Yang et al. | Mar 2016 | A1 |
| 20160062572 | Yang et al. | Mar 2016 | A1 |
| 20160062582 | Wilson et al. | Mar 2016 | A1 |
| 20160063215 | Zamer | Mar 2016 | A1 |
| 20160066842 | Kokkoneva et al. | Mar 2016 | A1 |
| 20160085937 | Dettinger et al. | Mar 2016 | A1 |
| 20160086500 | Kaleal, III | Mar 2016 | A1 |
| 20160089569 | Blahnik | Mar 2016 | A1 |
| 20160098522 | Weinstein | Apr 2016 | A1 |
| 20160103985 | Shim et al. | Apr 2016 | A1 |
| 20160106398 | Kuppuswami | Apr 2016 | A1 |
| 20160109961 | Parshionikar | Apr 2016 | A1 |
| 20160110523 | Francois | Apr 2016 | A1 |
| 20160132046 | Beoughter et al. | May 2016 | A1 |
| 20160132645 | Charpentier et al. | May 2016 | A1 |
| 20160135719 | Von Kraus et al. | May 2016 | A1 |
| 20160135731 | Drennan | May 2016 | A1 |
| 20160150978 | Yuen et al. | Jun 2016 | A1 |
| 20160166181 | Shennib | Jun 2016 | A1 |
| 20160166195 | Radecka et al. | Jun 2016 | A1 |
| 20160174857 | Eggers et al. | Jun 2016 | A1 |
| 20160180026 | Kim et al. | Jun 2016 | A1 |
| 20160189051 | Mahmood | Jun 2016 | A1 |
| 20160196635 | Cho et al. | Jul 2016 | A1 |
| 20160210099 | Hampapuram et al. | Jul 2016 | A1 |
| 20160210434 | Al-Sharif | Jul 2016 | A1 |
| 20160235325 | Chou | Aug 2016 | A1 |
| 20160235374 | Miller et al. | Aug 2016 | A1 |
| 20160249857 | Choi et al. | Sep 2016 | A1 |
| 20160250517 | Tilvis et al. | Sep 2016 | A1 |
| 20160256082 | Ely et al. | Sep 2016 | A1 |
| 20160263435 | Venkatraman et al. | Sep 2016 | A1 |
| 20160270717 | Luna et al. | Sep 2016 | A1 |
| 20160270740 | Raisoni et al. | Sep 2016 | A1 |
| 20160275310 | Edwards et al. | Sep 2016 | A1 |
| 20160275990 | Vassort | Sep 2016 | A1 |
| 20160285985 | Molettiere et al. | Sep 2016 | A1 |
| 20160287177 | Huppert et al. | Oct 2016 | A1 |
| 20160292373 | Spors et al. | Oct 2016 | A1 |
| 20160296210 | Matsushima | Oct 2016 | A1 |
| 20160299769 | Hunter et al. | Oct 2016 | A1 |
| 20160301761 | Sanchez-sandoval et al. | Oct 2016 | A1 |
| 20160301794 | Schlakman et al. | Oct 2016 | A1 |
| 20160302666 | Shaya | Oct 2016 | A1 |
| 20160313869 | Jang et al. | Oct 2016 | A1 |
| 20160314670 | Roberts et al. | Oct 2016 | A1 |
| 20160314683 | Felch et al. | Oct 2016 | A1 |
| 20160317341 | Galvan | Nov 2016 | A1 |
| 20160324457 | Dagum | Nov 2016 | A1 |
| 20160324488 | Olsen | Nov 2016 | A1 |
| 20160328991 | Simpson et al. | Nov 2016 | A1 |
| 20160332025 | Repka | Nov 2016 | A1 |
| 20160346607 | Rapfogel | Dec 2016 | A1 |
| 20160357403 | Chang et al. | Dec 2016 | A1 |
| 20160357616 | Yu et al. | Dec 2016 | A1 |
| 20160360100 | Kim et al. | Dec 2016 | A1 |
| 20160360972 | Kusakabe et al. | Dec 2016 | A1 |
| 20160367138 | Kim et al. | Dec 2016 | A1 |
| 20170000348 | Karsten et al. | Jan 2017 | A1 |
| 20170000359 | Kohli et al. | Jan 2017 | A1 |
| 20170007159 | Dieffenderfer et al. | Jan 2017 | A1 |
| 20170007167 | Kostic et al. | Jan 2017 | A1 |
| 20170032168 | Kim | Feb 2017 | A1 |
| 20170039327 | Bitran et al. | Feb 2017 | A1 |
| 20170042485 | Chung et al. | Feb 2017 | A1 |
| 20170043214 | Higashi | Feb 2017 | A1 |
| 20170046024 | Dascola et al. | Feb 2017 | A1 |
| 20170046052 | Lee et al. | Feb 2017 | A1 |
| 20170053542 | Wilson et al. | Feb 2017 | A1 |
| 20170070833 | Shennib | Mar 2017 | A1 |
| 20170071551 | Jain et al. | Mar 2017 | A1 |
| 20170075551 | Robinson et al. | Mar 2017 | A1 |
| 20170084196 | Nusbaum et al. | Mar 2017 | A1 |
| 20170086693 | Peterson et al. | Mar 2017 | A1 |
| 20170091567 | Wang et al. | Mar 2017 | A1 |
| 20170127997 | Hyde et al. | May 2017 | A1 |
| 20170132395 | Futch | May 2017 | A1 |
| 20170136297 | Penie | May 2017 | A1 |
| 20170147197 | Yang et al. | May 2017 | A1 |
| 20170150917 | Brief et al. | Jun 2017 | A1 |
| 20170156593 | Ferber et al. | Jun 2017 | A1 |
| 20170161014 | Kikugawa et al. | Jun 2017 | A1 |
| 20170172522 | Insler et al. | Jun 2017 | A1 |
| 20170177797 | Kurniawan et al. | Jun 2017 | A1 |
| 20170181645 | Mahalingam et al. | Jun 2017 | A1 |
| 20170181678 | Newberry | Jun 2017 | A1 |
| 20170188841 | Ma et al. | Jul 2017 | A1 |
| 20170188893 | Venkatraman et al. | Jul 2017 | A1 |
| 20170188979 | Volpe | Jul 2017 | A1 |
| 20170202496 | Ramanathan | Jul 2017 | A1 |
| 20170215811 | Newberry | Aug 2017 | A1 |
| 20170225034 | Kass et al. | Aug 2017 | A1 |
| 20170235443 | Suzuki | Aug 2017 | A1 |
| 20170237694 | Choudhary et al. | Aug 2017 | A1 |
| 20170243508 | Cheng et al. | Aug 2017 | A1 |
| 20170258455 | Qi | Sep 2017 | A1 |
| 20170274149 | Aeschlimann | Sep 2017 | A1 |
| 20170274267 | Blahnik | Sep 2017 | A1 |
| 20170287313 | Park et al. | Oct 2017 | A1 |
| 20170293727 | Klaassen et al. | Oct 2017 | A1 |
| 20170294174 | Albadawi et al. | Oct 2017 | A1 |
| 20170300186 | Kuhar et al. | Oct 2017 | A1 |
| 20170300643 | Bezark et al. | Oct 2017 | A1 |
| 20170303844 | Baker et al. | Oct 2017 | A1 |
| 20170319184 | Sano | Nov 2017 | A1 |
| 20170329933 | Brust et al. | Nov 2017 | A1 |
| 20170330297 | Cronin et al. | Nov 2017 | A1 |
| 20170332980 | Fifield et al. | Nov 2017 | A1 |
| 20170348562 | Jung et al. | Dec 2017 | A1 |
| 20170354845 | Williams | Dec 2017 | A1 |
| 20170357329 | Park et al. | Dec 2017 | A1 |
| 20170357520 | De Vries et al. | Dec 2017 | A1 |
| 20170364637 | Kshepakaran et al. | Dec 2017 | A1 |
| 20180000426 | Li | Jan 2018 | A1 |
| 20180001184 | Tran et al. | Jan 2018 | A1 |
| 20180011686 | Zhao et al. | Jan 2018 | A1 |
| 20180014121 | Lawrence et al. | Jan 2018 | A1 |
| 20180032234 | Michalske | Feb 2018 | A1 |
| 20180039410 | Kim et al. | Feb 2018 | A1 |
| 20180042540 | Kinnunen | Feb 2018 | A1 |
| 20180042559 | Cabrera et al. | Feb 2018 | A1 |
| 20180047277 | Thyroff | Feb 2018 | A1 |
| 20180049659 | Briante et al. | Feb 2018 | A1 |
| 20180049696 | Eom et al. | Feb 2018 | A1 |
| 20180055490 | Lee et al. | Mar 2018 | A1 |
| 20180056130 | Bitran et al. | Mar 2018 | A1 |
| 20180060522 | Petterson et al. | Mar 2018 | A1 |
| 20180064356 | Mendenhall et al. | Mar 2018 | A1 |
| 20180064388 | Heneghan et al. | Mar 2018 | A1 |
| 20180065025 | Toda et al. | Mar 2018 | A1 |
| 20180070861 | Eastman et al. | Mar 2018 | A1 |
| 20180074462 | Helder et al. | Mar 2018 | A1 |
| 20180074464 | Essery et al. | Mar 2018 | A1 |
| 20180081918 | Gravenites et al. | Mar 2018 | A1 |
| 20180096739 | Sano | Apr 2018 | A1 |
| 20180107962 | Lundin et al. | Apr 2018 | A1 |
| 20180110465 | Naima | Apr 2018 | A1 |
| 20180117414 | Miyasaka et al. | May 2018 | A1 |
| 20180120985 | Wallace et al. | May 2018 | A1 |
| 20180122214 | Seth et al. | May 2018 | A1 |
| 20180129994 | Fowler et al. | May 2018 | A1 |
| 20180132768 | Sasahara et al. | May 2018 | A1 |
| 20180137937 | Gass et al. | May 2018 | A1 |
| 20180140211 | Nakazawa et al. | May 2018 | A1 |
| 20180140927 | Kito et al. | May 2018 | A1 |
| 20180154212 | Park et al. | Jun 2018 | A1 |
| 20180157864 | Tribble et al. | Jun 2018 | A1 |
| 20180189077 | Gupta et al. | Jul 2018 | A1 |
| 20180189343 | Embiricos et al. | Jul 2018 | A1 |
| 20180211020 | Fukuda | Jul 2018 | A1 |
| 20180226150 | Hayter et al. | Aug 2018 | A1 |
| 20180239869 | Laing et al. | Aug 2018 | A1 |
| 20180255159 | Cohen et al. | Sep 2018 | A1 |
| 20180256036 | Kogure et al. | Sep 2018 | A1 |
| 20180256078 | Vaterlaus | Sep 2018 | A1 |
| 20180256095 | Arnold et al. | Sep 2018 | A1 |
| 20180263510 | Cronin et al. | Sep 2018 | A1 |
| 20180263517 | Kubo | Sep 2018 | A1 |
| 20180279885 | Bulut | Oct 2018 | A1 |
| 20180329584 | Williams et al. | Nov 2018 | A1 |
| 20180336530 | Johnson et al. | Nov 2018 | A1 |
| 20180345078 | Blahnik | Dec 2018 | A1 |
| 20180350451 | Ohnemus et al. | Dec 2018 | A1 |
| 20180368814 | R. Kudtarkar | Dec 2018 | A1 |
| 20180376107 | Shibaev et al. | Dec 2018 | A1 |
| 20190012898 | Wittrup | Jan 2019 | A1 |
| 20190014205 | Miloseski et al. | Jan 2019 | A1 |
| 20190018588 | Debates et al. | Jan 2019 | A1 |
| 20190034050 | Williams et al. | Jan 2019 | A1 |
| 20190034494 | Bradley et al. | Jan 2019 | A1 |
| 20190043337 | Liu et al. | Feb 2019 | A1 |
| 20190073618 | Kanukurthy et al. | Mar 2019 | A1 |
| 20190090800 | Bosworth et al. | Mar 2019 | A1 |
| 20190090816 | Horseman | Mar 2019 | A1 |
| 20190104951 | Valys et al. | Apr 2019 | A1 |
| 20190108908 | Faulks et al. | Apr 2019 | A1 |
| 20190122523 | Roberts et al. | Apr 2019 | A1 |
| 20190138696 | Carpenter et al. | May 2019 | A1 |
| 20190150854 | Chung et al. | May 2019 | A1 |
| 20190192086 | Menon et al. | Jun 2019 | A1 |
| 20190206538 | Xing et al. | Jul 2019 | A1 |
| 20190223843 | Vitti | Jul 2019 | A1 |
| 20190228179 | Rakshit et al. | Jul 2019 | A1 |
| 20190228640 | Freedman et al. | Jul 2019 | A1 |
| 20190228847 | Soli | Jul 2019 | A1 |
| 20190240534 | Black | Aug 2019 | A1 |
| 20190252054 | Dirani et al. | Aug 2019 | A1 |
| 20190274562 | Soli et al. | Sep 2019 | A1 |
| 20190274563 | Soli et al. | Sep 2019 | A1 |
| 20190274564 | Soli et al. | Sep 2019 | A1 |
| 20190274565 | Soli et al. | Sep 2019 | A1 |
| 20190278556 | Usher et al. | Sep 2019 | A1 |
| 20190298230 | Nicholson et al. | Oct 2019 | A1 |
| 20190302995 | Robinson et al. | Oct 2019 | A1 |
| 20190313180 | Kadiwala 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 |
| 20190339849 | Williams et al. | Nov 2019 | A1 |
| 20190341027 | Vescovi et al. | Nov 2019 | A1 |
| 20190365332 | Fedichev et al. | Dec 2019 | A1 |
| 20190380624 | Ota et al. | Dec 2019 | A1 |
| 20190385708 | Hong et al. | Dec 2019 | A1 |
| 20200000441 | Lafon et al. | Jan 2020 | A1 |
| 20200054931 | Martin et al. | Feb 2020 | A1 |
| 20200069258 | Grinberg | Mar 2020 | A1 |
| 20200100693 | Velo | Apr 2020 | A1 |
| 20200126673 | Tanabe et al. | Apr 2020 | A1 |
| 20200203012 | Kamath et al. | Jun 2020 | A1 |
| 20200214650 | Lee et al. | Jul 2020 | A1 |
| 20200245928 | Kang et al. | Aug 2020 | A1 |
| 20200261011 | Seppänen et al. | Aug 2020 | A1 |
| 20200273566 | Bhowmik et al. | Aug 2020 | A1 |
| 20200297249 | Williams et al. | Sep 2020 | A1 |
| 20200315544 | Levine | Oct 2020 | A1 |
| 20200323441 | Deno et al. | Oct 2020 | A1 |
| 20200350052 | Saint et al. | Nov 2020 | A1 |
| 20200356687 | Salzman et al. | Nov 2020 | A1 |
| 20200374682 | Newman et al. | Nov 2020 | A1 |
| 20200379611 | Dryer et al. | Dec 2020 | A1 |
| 20200381099 | Crowley et al. | Dec 2020 | A1 |
| 20200381123 | Dryer et al. | Dec 2020 | A1 |
| 20200382866 | Felton | Dec 2020 | A1 |
| 20200382867 | Felton | Dec 2020 | A1 |
| 20200384314 | Lee et al. | Dec 2020 | A1 |
| 20210019713 | Vangala et al. | Jan 2021 | A1 |
| 20210068714 | Crowley et al. | Mar 2021 | A1 |
| 20210113137 | Soli et al. | Apr 2021 | A1 |
| 20210204815 | Koskela et al. | Jul 2021 | A1 |
| 20210225482 | Crowley et al. | Jul 2021 | A1 |
| 20210257091 | Spang et al. | Aug 2021 | A1 |
| 20210287520 | Maeda et al. | Sep 2021 | A1 |
| 20210369130 | Felton et al. | Dec 2021 | A1 |
| 20210373746 | Felton et al. | Dec 2021 | A1 |
| 20210373747 | Felton et al. | Dec 2021 | A1 |
| 20210373748 | Felton et al. | Dec 2021 | A1 |
| 20210375157 | Sundstrom et al. | Dec 2021 | A1 |
| 20210375450 | Felton et al. | Dec 2021 | A1 |
| 20210401378 | Pho et al. | Dec 2021 | A1 |
| 20220047250 | Clements et al. | Feb 2022 | A1 |
| 20220066902 | Narra et al. | Mar 2022 | A1 |
| 20220109932 | Felton et al. | Apr 2022 | A1 |
| 20220142515 | Crowley | May 2022 | A1 |
| 20220157143 | Panneer Selvam et al. | May 2022 | A1 |
| 20220160258 | Williams et al. | May 2022 | A1 |
| 20220273204 | Kamath et al. | Sep 2022 | A1 |
| 20230016144 | Dryer et al. | Jan 2023 | A1 |
| 20230020517 | Narra et al. | Jan 2023 | A1 |
| 20230101625 | Soli et al. | Mar 2023 | A1 |
| 20230114054 | Crowley et al. | Apr 2023 | A1 |
| 20240013889 | Crowley et al. | Jan 2024 | A1 |
| 20240050016 | Soli et al. | Feb 2024 | A1 |
| 20240079130 | Maratta et al. | Mar 2024 | A1 |
| Number | Date | Country |
|---|---|---|
| 2815518 | May 2012 | CA |
| 1752973 | Mar 2006 | CN |
| 101107619 | Jan 2008 | CN |
| 102448555 | May 2012 | CN |
| 102790761 | Nov 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 |
| 104680459 | Jun 2015 | CN |
| 104720765 | Jun 2015 | CN |
| 105260078 | Jan 2016 | CN |
| 105388998 | Mar 2016 | CN |
| 105632508 | Jun 2016 | CN |
| 105721667 | Jun 2016 | CN |
| 105980008 | Sep 2016 | CN |
| 106164808 | Nov 2016 | CN |
| 106371816 | Feb 2017 | CN |
| 106415559 | Feb 2017 | CN |
| 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 |
| 107508995 | Dec 2017 | CN |
| 107545930 | Jan 2018 | 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 |
| 1077046 | Feb 2001 | EP |
| 2391004 | Nov 2011 | EP |
| 2568409 | Mar 2013 | EP |
| 2921899 | Sep 2015 | EP |
| 3042606 | Jul 2016 | EP |
| 3096235 | Nov 2016 | EP |
| 3101882 | Dec 2016 | EP |
| 3557590 | Oct 2019 | EP |
| 2018-504660 | Jan 2001 | JP |
| 6382433 | Jan 2001 | JP |
| 2004-80496 | Jan 2004 | JP |
| 2004-80496 | Mar 2004 | JP |
| 2004-318503 | Nov 2004 | JP |
| 2005-79814 | Mar 2005 | JP |
| 2006-107134 | Apr 2006 | JP |
| 2008-11865 | Jan 2008 | JP |
| 2009-232301 | Jan 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 |
| 2011-197992 | Jan 2011 | JP |
| 2011-197992 | Oct 2011 | JP |
| 2011-200575 | Oct 2011 | JP |
| 2012-45373 | Jan 2012 | JP |
| 2012-502343 | Jan 2012 | JP |
| 2012-45373 | Mar 2012 | JP |
| 2012-59264 | Mar 2012 | JP |
| 2012-174055 | Sep 2012 | JP |
| 2012-524640 | Oct 2012 | JP |
| 2012-239808 | Dec 2012 | JP |
| 2013-17631 | Jan 2013 | JP |
| 2013-192608 | Jan 2013 | JP |
| 2013-192608 | Sep 2013 | JP |
| 2013-207323 | Oct 2013 | JP |
| 2013-544140 | Dec 2013 | JP |
| 2014-168685 | Sep 2014 | JP |
| 2015-28686 | Jan 2015 | JP |
| 2015-28686 | Feb 2015 | JP |
| 2015-73590 | Apr 2015 | JP |
| 2015-213686 | Dec 2015 | JP |
| 2016-502875 | Feb 2016 | JP |
| 2016-528016 | Sep 2016 | JP |
| 2016-177151 | Oct 2016 | JP |
| 2016-202751 | Dec 2016 | JP |
| 2016-538926 | Dec 2016 | JP |
| 2017-40981 | Jan 2017 | JP |
| 2017-117265 | Jan 2017 | JP |
| 2017-515520 | Jan 2017 | 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 |
| 2018-523554 | Aug 2018 | JP |
| 6382433 | Aug 2018 | JP |
| 2018-191122 | Nov 2018 | JP |
| 2019-28806 | Jan 2019 | JP |
| 2019-32461 | Jan 2019 | JP |
| 2019-36226 | Jan 2019 | JP |
| 2019-55076 | Jan 2019 | JP |
| 2019-207536 | Jan 2019 | JP |
| 2019-505035 | Jan 2019 | 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-2013-0093837 | Aug 2013 | KR |
| 10-2013-0111569 | Oct 2013 | KR |
| 10-2013-0111570 | Oct 2013 | KR |
| 10-2015-0115385 | Oct 2015 | KR |
| 10-1594486 | Feb 2016 | KR |
| 10-2016-0028351 | Mar 2016 | KR |
| 10-2016-0076264 | Jun 2016 | KR |
| 10-2016-0077199 | Jul 2016 | KR |
| 10-2017-0003608 | Jan 2017 | KR |
| 10-2017-0019040 | Feb 2017 | KR |
| 10-2017-0019745 | Feb 2017 | KR |
| 10-2017-0029014 | Mar 2017 | KR |
| 10-2018-0129188 | Dec 2018 | KR |
| 10-2019-0094795 | Aug 2019 | KR |
| 2001096986 | Dec 2001 | WO |
| 200241134 | May 2002 | WO |
| 2003067202 | Aug 2003 | WO |
| 2006046648 | May 2006 | WO |
| 2008073359 | Jun 2008 | WO |
| 2009095908 | Aug 2009 | WO |
| 2010028320 | Mar 2010 | WO |
| 2010047035 | Apr 2010 | WO |
| 2010126825 | Nov 2010 | WO |
| 2012048832 | Apr 2012 | WO |
| 2012060588 | May 2012 | WO |
| 2012061438 | May 2012 | WO |
| 2012061440 | May 2012 | WO |
| 2013103570 | Jul 2013 | WO |
| 2013109916 | Jul 2013 | WO |
| 2014006862 | Jan 2014 | WO |
| 2014015378 | Jan 2014 | WO |
| 2014207875 | Dec 2014 | WO |
| 2015027133 | Feb 2015 | WO |
| 2015084353 | Jun 2015 | WO |
| 2015153803 | Oct 2015 | WO |
| 2015164845 | Oct 2015 | WO |
| 2015183828 | Dec 2015 | WO |
| 2015187799 | Dec 2015 | WO |
| 2015198488 | Dec 2015 | WO |
| 2016036472 | Mar 2016 | WO |
| 2016036582 | Mar 2016 | WO |
| 2016151479 | Sep 2016 | WO |
| 2016161152 | Oct 2016 | WO |
| 2016164475 | Oct 2016 | WO |
| 2016179559 | Nov 2016 | WO |
| 2016207745 | Dec 2016 | WO |
| 2017003045 | Jan 2017 | WO |
| 2017037242 | Mar 2017 | WO |
| 2017054277 | Apr 2017 | WO |
| 2017062621 | Apr 2017 | WO |
| 2017087642 | May 2017 | WO |
| 2017090810 | Jun 2017 | WO |
| 2017172046 | Oct 2017 | WO |
| 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 |
| 2021212112 | Oct 2021 | WO |
| 2022010573 | Jan 2022 | WO |
| Entry |
|---|
| Advisory Action received for U.S. Appl. No. 16/144,864, mailed on Jul. 29, 2019, 6 pages. |
| Advisory Action received for U.S. Appl. No. 16/143,909, mailed on Nov. 7, 2019, 5 pages. |
| Advisory Action received for U.S. Appl. No. 16/143,997, mailed on Dec. 26, 2019, 7 pages. |
| Advisory Action received for U.S. Appl. No. 16/144,849, mailed on Aug. 12, 2019, 5 pages. |
| Advisory Action received for U.S. Appl. No. 16/144,864, mailed on Jul. 6, 2020, 6 pages. |
| Advisory Action received for U.S. Appl. No. 17/031,779, mailed on Oct. 20, 2022, 5 pages. |
| Applicant Initiated Interview Summary received for U.S. Appl. No. 16/143,997, mailed on Aug. 13, 2020, 3 pages. |
| Applicant Initiated Interview Summary received for U.S. Appl. No. 16/144,849, mailed on Jan. 21, 2020, 6 pages. |
| Applicant Initiated Interview Summary received for U.S. Appl. No. 16/144,864, mailed on Apr. 29, 2020, 4 pages. |
| Applicant Initiated Interview Summary received for U.S. Appl. No. 16/586,154, mailed on Mar. 11, 2020, 4 pages. |
| Applicant Initiated Interview Summary received for U.S. Appl. No. 16/894,309, mailed on Jan. 26, 2021, 3 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/138,809, mailed on Dec. 16, 2020, 7 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/138,809, mailed on Jun. 9, 2020, 4 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/143,997, mailed on May 3, 2021, 4 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/144,864, mailed on Jun. 22, 2020, 3 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/249,627, mailed on Jun. 2, 2021, 5 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/249,627, mailed on Mar. 1, 2023, 4 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/249,627, mailed on Mar. 23, 2022, 3 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/249,627, mailed on Oct. 6, 2021, 4 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/249,627, mailed on Sep. 28, 2022, 4 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/584,186, mailed on Feb. 3, 2020, 4 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/586,154, mailed on Apr. 14, 2021, 4 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/586,154, mailed on Dec. 11, 2020, 5 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/586,154, mailed on Sep. 3, 2021, 4 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/851,451, mailed on Aug. 5, 2022, 3 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/851,451, mailed on Nov. 29, 2022, 4 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/880,552, mailed on Apr. 21, 2021, 3 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/880,552, mailed on Dec. 16, 2020, 6 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/880,552, mailed on Oct. 20, 2020, 6 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/880,714, mailed on Feb. 26, 2021, 5 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/888,780, mailed on Aug. 2, 2022, 4 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/894,309, mailed on Jun. 25, 2021, 4 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/907,261, mailed on Dec. 16, 2020, 6 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/907,261, mailed on Jul. 16, 2021, 10 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/907,261, mailed on Mar. 25, 2021, 2 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/953,781, mailed on Oct. 31, 2022, 12 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/031,704, mailed on Feb. 9, 2021, 3 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/031,704, mailed on Jun. 25, 2021, 3 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/031,717, mailed on Jan. 29, 2021, 5 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/031,717, mailed on May 17, 2021, 5 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/031,717, mailed on Nov. 4, 2021, 5 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/031,723, mailed on Aug. 30, 2022, 4 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/031,723, mailed on Jan. 23, 2023, 4 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/031,723, mailed on Mar. 21, 2021, 5 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/031,779, mailed on Aug. 29, 2022, 2 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/031,779, mailed on Mar. 10, 2022, 2 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/041,415, mailed on Jun. 29, 2022, 2 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/952,053, mailed on Apr. 5, 2023, 6 pages. |
| Brief Communication Regarding Oral Proceedings received for European Patent Application No. 13812320.3, mailed on Sep. 16, 2021, 2 pages. |
| Brief Communication Regarding Oral Proceedings received for European Patent Application No. 20180581.9, mailed on Jan. 26, 2022, 1 page. |
| Brief Communication Regarding Oral Proceedings received for European Patent Application No. 20180581.9, mailed on Nov. 30, 2021, 1 page. |
| Brief Communication regarding Oral Proceedings received for European Patent Application No. 20180592.6, mailed on Dec. 21, 2021, 1 page. |
| Brief Communication regarding Oral Proceedings received for European Patent Application No. 20180592.6, mailed on Jan. 26, 2022, 2 pages. |
| Brief Communication Regarding Oral Proceedings received for European Patent Application No. 20182116.2, mailed on Apr. 13, 2022, 3 pages. |
| Brief Communication Regarding Oral Proceedings received for European Patent Application No. 20203526.7, mailed on Jan. 18, 2023, 1 page. |
| Brief Communication Regarding Oral Proceedings received for European Patent Application No. 20746438.9, mailed on Nov. 7, 2022, 1 page. |
| Casella Cel Casella, “The Casella dBadge2—World's First Truly Wireless Noise Dosimeter and Airware App!”, Retrieved from URL: <https://www.youtube.com/watch?v=Xvy2fl3cgYo>, May 27, 2015, 3 pages. |
| Certificate of Examination received for Australian Patent Application No. 2019100222, mailed on Aug. 29, 2019, 2 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=lttzlCid_d8, May 18, 2016, 1 page. |
| Cook James, “German Period Tracking App Clue Has Over 2.5 Million Active Users—But It's Still Not Sure How It's Going to Make Money”, Available online at:https://www.businessinsider.in/tech/german-period-tracking-app-clue-has-over-2-5-million-active-users-but-its-still-not-sure-how-its-going-to-make-money/articleshow/50511307.cms, Jan. 9, 2016, 9 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/143,909, mailed on Feb. 20, 2020, 3 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/143,909, mailed on Mar. 18, 2020, 3 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/143,959, mailed on Dec. 13, 2019, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/143,997, mailed on Jul. 2, 2021, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/143,997, mailed on Jun. 4, 2021, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/143,997, mailed on Nov. 16, 2021, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/143,997, mailed on Oct. 21, 2021, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/584,186, mailed on Jul. 31, 2020, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/586,154, mailed on Oct. 27, 2021, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/880,552, mailed on Dec. 22, 2021, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/880,552, mailed on Dec. 23, 2020, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/880,552, mailed on Jul. 7, 2021, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/921,312, mailed on Dec. 7, 2021, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/921,312, mailed on Sep. 24, 2021, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/990,846, mailed on Feb. 9, 2022, 3 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 17/031,704, mailed on Nov. 2, 2021, 7 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 17/031,717, mailed on Apr. 15, 2022, 3 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 17/031,717, mailed on May 19, 2022, 3 pages. |
| DC Rainmaker, “Garmin Fenix3 New Auto Climb Functionality”, Available online at: https://www.youtube.com/watch?v=iuavOSNpVRc, Feb. 19, 2015, 1 page. |
| Decision on Appeal received for Korean Patent Application No. 10-2019-7025538, mailed on Feb. 24, 2021, 20 pages. |
| Decision to Grant received for Danish Patent Application No. PA201870379, mailed on Jul. 5, 2019, 2 pages. |
| Decision to Grant received for Danish Patent Application No. PA201870600, mailed on Oct. 17, 2019, 2 pages. |
| Decision to Grant received for Danish Patent Application No. PA201870601, mailed on Aug. 17, 2020, 2 pages. |
| Decision to Grant received for Danish Patent Application No. PA201870602, mailed on Aug. 18, 2020, 2 pages. |
| Decision to Grant received for Danish Patent Application No. PA202070619, mailed on Aug. 11, 2022, 2 pages. |
| Decision to Grant received for European Patent Application No. 20180592.6, mailed on Sep. 1, 2022, 3 pages. |
| Decision to Refuse received for European Patent Application No. 13812320.3, mailed on Oct. 14, 2021, 4 pages. |
| Decision to Refuse received for European Patent Application No. 20180581.9, mailed on Apr. 13, 2022, 16 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, 2017, pp. 6876-6888. |
| European Search Report received for European Patent Application No. 20182116.2, mailed on Oct. 21, 2020, 4 pages. |
| Evergreen et al., “Bar Chart”, Better Evaluation, Available Online at: https://www.betterevaluation.org/en/evaluation-options/BarChart, Oct. 31, 2014, 8 pages. |
| Extended European Search Report received for European Patent Application No. 20180581.9, mailed on Aug. 12, 2020, 9 pages. |
| Extended European Search Report received for European Patent Application No. 20180592.6, mailed on Aug. 11, 2020, 10 pages. |
| Extended European Search Report received for European Patent Application No. 20203526.7, mailed on Jan. 29, 2021, 13 pages. |
| Extended European Search Report received for European Patent Application No. 22190169.7, mailed on Nov. 23, 2022, 11 pages. |
| Final Office Action received for U.S. Appl. No. 15/167,699, mailed on Jun. 30, 2017., 8 pages. |
| Final Office Action received for U.S. Appl. No. 16/138,809, mailed on Aug. 27, 2020, 24 pages. |
| Final Office Action received for U.S. Appl. No. 16/143,909, mailed on Aug. 28, 2019, 20 pages. |
| Final Office Action received for U.S. Appl. No. 16/143,997, mailed on Feb. 9, 2021, 16 pages. |
| Final Office Action received for U.S. Appl. No. 16/143,997, mailed on Sep. 30, 2019, 16 pages. |
| Final Office Action received for U.S. Appl. No. 16/144,030, mailed on Feb. 13, 2020, 11 pages. |
| Final Office Action received for U.S. Appl. No. 16/144,030, mailed on Oct. 1, 2019, 13 pages. |
| Final Office Action received for U.S. Appl. No. 16/144,849, mailed on Jun. 7, 2019, 29 pages. |
| Final Office Action received for U.S. Appl. No. 16/144,864, mailed on May 17, 2019, 24 pages. |
| Final Office Action received for U.S. Appl. No. 16/144,864, mailed on May 28, 2020, 29 pages. |
| Final Office Action received for U.S. Appl. No. 16/249,627, mailed on Feb. 14, 2022, 19 pages. |
| Final Office Action received for U.S. Appl. No. 16/586,154, mailed on Jul. 6, 2020, 27 pages. |
| Final Office Action received for U.S. Appl. No. 16/586,154, mailed on May 24, 2021, 29 pages. |
| Final Office Action received for U.S. Appl. No. 16/851,451, mailed on Oct. 20, 2022, 31 pages. |
| Final Office Action received for U.S. Appl. No. 16/888,780, mailed on Nov. 25, 2022, 10 pages. |
| Final Office Action received for U.S. Appl. No. 16/894,309, mailed on Feb. 24, 2021, 30 pages. |
| Final Office Action received for U.S. Appl. No. 16/907,261, mailed on Mar. 18, 2021, 20 pages. |
| Final Office Action received for U.S. Appl. No. 17/031,704, mailed on Apr. 1, 2021, 31 pages. |
| Final Office Action received for U.S. Appl. No. 17/031,717, mailed on Feb. 24, 2021, 23 pages. |
| Final Office Action received for U.S. Appl. No. 17/031,723, mailed on Jul. 12, 2022, 25 pages. |
| Final Office Action received for U.S. Appl. No. 17/031,779, mailed on Jul. 14, 2022, 19 pages. |
| Fitbit App, Available online at: <http://web.archive.org/web/20180114083150/https://www.fitbit.com/au/app>, Jan. 14, 2018, 8 pages. |
| Garmin,“Fenix 5x Owner's Manual”, Online Available at :—https://web.archive.org/web/20180127170640/https://static.garmin.com/pumac/fenix5x_OM_EN.pdf, Jan. 27, 2018, 42 pages. |
| Graphs and Charts, online available at: <https://www.teachervision.com/lesson˜planning/graph-chart-teacher-resources, retrieved on Dec. 12, 2018, 4 pages. |
| Gupta Rajat, “Disable High Volume Warning no root) in Samsung S7, S8 / Android 7.0”, Online available at:<https://www.youtube.com/watch?v=9fKwRBtk-x8>, Retrieved on Nov. 26, 2020; esp. 2:04, Aug. 6, 2017, 1 page. |
| Haslam Oliver, “Stop Coronavirus in its Tracks by Using This Apple Watch App to Time Hand Washes”, Available Online at: <https://www.imore.com/stop-coronavirus-its-tracks-using-apple-watch-app-time-hand-washes>, Mar. 12, 2020, 12 pages. |
| Intention to Grant received for Danish Patent Application No. PA201870379, mailed on May 2, 2019, 2 pages. |
| Intention to Grant received for Danish Patent Application No. PA201870600, mailed on Jul. 10, 2019, 2 pages. |
| Intention to Grant received for Danish Patent Application No. PA201870601, mailed on Apr. 24, 2020, 2 pages. |
| Intention to Grant received for Danish Patent Application No. PA201870602, mailed on Apr. 24, 2020, 2 pages. |
| Intention to Grant received for Danish Patent Application No. PA202070619, mailed on Jan. 17, 2022, 2 pages. |
| Intention to Grant received for European Patent Application No. 20180592.6, mailed on Apr. 20, 2022, 21 pages. |
| Intention to Grant received for European Patent Application No. 20182116.2, mailed on Jun. 2, 2022, 8 pages. |
| Intention to Grant received for European Patent Application No. 20182116.2, mailed on Nov. 11, 2022, 9 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2020/035164, mailed on Dec. 16, 2021, 19 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2020/035462, mailed on Dec. 16, 2021, 16 pages. |
| Intemational Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2013/073188, mailed on Jun. 16, 2016, 6 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2019/014215, mailed on Aug. 6, 2020, 14 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2019/019694, mailed on Sep. 24, 2020, 12 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2019/024570, mailed on Nov. 19, 2020, 10 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2020/025768, mailed on Dec. 16, 2021, 8 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2020/035474, mailed on Dec. 16, 2021, 11 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2020/042439, mailed on Jan. 27, 2022, 10 pages. |
| Intemational Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2020/070280, mailed on Mar. 17, 2022, 15 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2021/035227, mailed on Dec. 15, 2022, 10 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2021/035504, mailed on Dec. 15, 2022, 8 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2021/048568, mailed on Mar. 9, 2023, 11 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2013/073188 mailed on Feb. 24, 2014, 8 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2019/014215, mailed on Jun. 4, 2019, 17 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2019/019694, mailed on Sep. 2, 2019, 17 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2019/024570, mailed on Aug. 8, 2019, 18 pages. |
| International Search Report and written Opinion received for PCT Patent Application No. PCT/US2020/025768, mailed on Aug. 10, 2020, 11 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2020/035164, mailed on Feb. 8, 2021, 26 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2020/035462, mailed on Sep. 11, 2020, 17 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2020/035474, mailed on Nov. 26, 2020, 16 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2020/042439, mailed on Oct. 9, 2020, 14 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2020/070280, mailed on Nov. 30, 2020, 20 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2021/035227, mailed on Oct. 6, 2021, 17 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2021/035504, mailed on Sep. 16, 2021, 12 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2021/048568, mailed on Jan. 7, 2022, 14 pages. |
| Invitation to Pay Addition Fees and Partial International Search Report received for PCT Patent Application No. PCT/US2019/014215, mailed on Apr. 12, 2019, 13 pages. |
| Invitation to Pay Addition Fees received for PCT Patent Application No. PCT/US2020/035474, mailed on Oct. 2, 2020, 11 pages. |
| Invitation to Pay Additional Fees and Partial International Search Report received for PCT Patent Application No. PCT/US2020/035164, mailed on Oct. 16, 2020, 14 pages. |
| Invitation to Pay Additional Fees received for PCT Patent Application No. PCT/US2019/019694, mailed on Jul. 10, 2019, 12 pages. |
| Invitation to Pay Additional Fees received for PCT Patent Application No. PCT/US2020/070280, mailed on Oct. 7, 2020, 12 pages. |
| Invitation to Pay Search Fees received for European Patent Application No. 19703582.7, mailed on Sep. 12, 2022, 3 pages. |
| Invitation to Pay Search Fees received for European Patent Application No. 19726205.8, mailed on Feb. 14, 2020, 5 pages. |
| Invitation to Pay Search Fees received for European Patent Application No. 20746438.9, mailed on Dec. 2, 2022, 4 pages. |
| Invitation to Pay Search Fees received for European Patent Application No. 20760607.0, mailed on Nov. 21, 2022, 3 pages. |
| Liaqat et al., “Challenges with Real-World Smartwatch based Audio Monitoring”, WearSys'18, Munich, Germany, Available Online at: <https://doi.org/10.1145/3211960.3211977>, Jun. 10, 2018, 6 pages. |
| Lovejoy Ben, “Apple Watch blood sugar measurement coming in Series 7, claims report”, Available Online at:https://9to5mac.com/2021/01/25/apple-watch-blood-sugar-measurement/, Jan. 25, 2021, 6 pages. |
| Lyles Taylor, “Wear OS Smartwatches are Now Sending Reminders to Wash Your Hands”, Available Online at: <https://www.theverge.com/2020/4/14/21221294/google-wear-os-smartwatches-reminders-wash-your-hands>, Apr. 14, 2020, 2 pages. |
| Megadepot,“Casella dBadge2 Noise Dosimeter”, Retrieved from URL: <https://www.youtube.com/watch?v=pHiHLIYCD08>, Jun. 12, 2018, 3 pages. |
| 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. |
| Minutes of the Oral Proceedings received for European Patent Application No. 20182116.2, mailed on May 24, 2022, 7 pages. |
| Moglia et al., “Evaluation of Smartphone Menstrual Cycle Tracking Applications Using an Adapted Applications Scoring System”, Obstetrics and Gynecology, vol. 127. No. 6, June 2016, pp. 1153-1160. |
| Multi-Set Bar Chart, The Data Visualization Catalogue, Available Online at: https://datavizcatalogue.com/methods/multiset_barchart.html, Feb. 8, 2014, 3 pages. |
| 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. |
| Non Final Office Action Received for U.S. Appl. No. 16/144,864, mailed on Dec. 18, 2018, 19 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/167,699, mailed on Oct. 21, 2016, 13 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/885,448, mailed on Apr. 16, 2020, 9 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/138,809, mailed on Feb. 28, 2020, 22 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/143,909, mailed on Apr. 19, 2019, 16 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/143,959, mailed on Apr. 17, 2019, 15 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/143,997, mailed on Jul. 27, 2020, 15 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/143,997, mailed on May 21, 2019, 15 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/144,030, mailed on Apr. 12, 2019, 8 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/144,030, mailed on Nov. 5, 2020, 5 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/144,849, mailed on Dec. 31, 2018, 28 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/144,849, mailed on Sep. 17, 2019, 9 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/144,864, mailed on Jan. 31, 2020, 29 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/249,627, mailed on Aug. 22, 2022, 21 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/249,627, mailed on Aug. 31, 2021. 18 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/249,627, mailed on Jan. 19, 2023, 19 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/249,627, mailed on Mar. 11, 2021, 21 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/584,186, mailed on Dec. 6, 2019, 13 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/586,154, mailed on Dec. 9, 2019, 23 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/586,154, mailed on Dec. 28, 2020, 26 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/851,451, mailed on Feb. 24, 2023, 28 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/851,451, mailed on May 9, 2022, 26 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/880,552, mailed on Feb. 19, 2021, 11 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/880,552, mailed on Jul. 23, 2020, 19 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/880,714, mailed on Oct. 28, 2020, 11 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/888,780, mailed on Apr. 20, 2022, 22 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/894,309, mailed on Oct. 15, 2020, 24 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/907,261, mailed on Sep. 30, 2020, 22 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/953,781, mailed on Jul. 26, 2022, 9 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/990,846, mailed on May 10, 2021, 16 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/031,704, mailed on Dec. 10, 2020, 30 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/031,717, mailed on Nov. 19, 2020, 22 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/031,717, mailed on Sep. 14, 2021, 35 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/031,723, mailed on Dec. 5, 2022, 27 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/031,723, mailed on Jan. 24, 2022, 17 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/031,779, mailed on Feb. 16, 2022, 17 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/041,415, mailed on Mar. 29, 2022, 11 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/337,147, mailed on Feb. 21, 2023, 15 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/952,053, mailed on Jan. 12, 2023, 12 pages. |
| Notice from the European Patent Office dated Oct. 1, 2007 Concerning Business Methods, Official Journal EPO, available online at <http://archive.epo.org/epo/pubs/oj007/11_07/11_5927.pdf>, Nov. 2007, pp. 592- 593. |
| Notice of Acceptance received for Australian Patent Application No. 2013406817, mailed on Nov. 21, 2017, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2018201260, mailed on Jan. 15, 2020, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2019210192, mailed on Dec. 2, 2021, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2019222943, mailed on May 5, 2020, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2020204153, mailed on Jul. 6, 2020, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2020239692, mailed on Apr. 6, 2022, 3 pages. |
| Notice of Acceptance received for Australian Patent application No. 2020239740, mailed on Feb. 22, 2022., 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2020256383, mailed on Aug. 3, 2021, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2020288147, mailed on Dec. 22, 2021, 3 pages. |
| Notice of Allowance received for Chinese Patent Application No. 201380081315.7, mailed on Jan. 4, 2019, 2 pages. |
| Notice of Allowance received for Chinese Patent Application No. 201910972529.2, mailed on Sep. 14, 2020, 6 pages. |
| Notice of Allowance received for Chinese Patent Application No. 202010606407.4, mailed on Jan. 24, 2022, 2 pages. |
| Notice of Allowance received for Chinese Patent Application No. 202010618569.X, mailed on Jan. 7, 2022, 2 pages. |
| Notice of Allowance received for Chinese Patent Application No. 202111611270.2, mailed on Sep. 21, 2022, 4 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2018-184532, mailed on Jan. 17, 2022, 4 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2019-162293, mailed on Apr. 9, 2021, 4 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2020-104679, mailed on Jan. 4, 2021, 4 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2020-153166, mailed on Sep. 13, 2021, 4 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2020-160023, mailed on Apr. 11, 2022, 4 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2020-547369, mailed on Jul. 16, 2021, 4 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2020-551585, mailed on Jul. 22, 2022, 4 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2020-560883, mailed on Oct. 29, 2021, 4 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2021-167557, mailed on Jan. 27, 2023, 4 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2021-571467, mailed on Apr. 11, 2022, 4 pages. |
| Notice of Allowance received for Korean Patent Application No. 10-2016-7014353, mailed on Aug. 2, 2018, 3 pages. |
| Notice of Allowance received for Korean Patent Application No. 10-2018-7032096, mailed on Dec. 12, 2018, 4 pages. |
| Notice of Allowance received for Korean Patent Application No. 10-2019-7025538, mailed on Mar. 10, 2021, 5 pages. |
| Notice of Allowance received for Korean Patent Application No. 10-2020-7023277, mailed on Jul. 18, 2022, 5 pages. |
| Notice of Allowance received for Korean Patent Application No. 10-2020-7026035, mailed on Aug. 23, 2021, 4 pages. |
| Notice of Allowance received for Korean Patent Application No. 10-2020-7026391, mailed on May 11, 2021, 3 pages. |
| Notice of Allowance received for Korean Patent Application No. 10-2020-7026453, mailed on May 11, 2021, 3 pages. |
| Notice of Allowance received for Korean Patent Application No. 10-2021-7038005, mailed on Dec. 14, 2021, 4 pages. |
| Notice of Allowance received for Korean Patent Application No. 10-2021-7042504, mailed on Jan. 17, 2022, 6 pages. |
| Notice of Allowance received for Korean Patent Application No. 10-2022-7008569, mailed on May 19, 2022, 5 pages. |
| Notice of Allowance received for U.S. Appl. No. 15/167,699, mailed on Oct. 27, 2017, 8 pages. |
| Notice of Allowance received for U.S. Appl. No. 15/885,448, mailed on Jun. 16, 2020, 5 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/138,809, mailed on Apr. 16, 2021, 11 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/138,809, mailed on Jul. 20, 2021, 6 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/143,909, mailed on Jan. 21, 2020, 9 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/143,959, mailed on Oct. 31, 2019, 10 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/143,997, mailed on May 13, 2021, 10 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/143,997, mailed on Sep. 30, 2021, 8 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/144,030, mailed on Apr. 5, 2021, 8 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/144,849, mailed on Apr. 17, 2020, 2 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/144,849, mailed on Mar. 6, 2020, 9 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/144,864, mailed on Feb. 9, 2021, 13 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/144,864, mailed on Jul. 28, 2020, 27 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/144,864, mailed on Mar. 12, 2021, 2 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/144,864, mailed on Mar. 30, 2021, 2 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/144,864, mailed on Sep. 10, 2020, 3 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/144,864, mailed on Sep. 16, 2020, 2 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/144,864, mailed on Sep. 29, 2020, 2 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/584,186, mailed on Mar. 24, 2020, 10 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/586,154, mailed on Oct. 15, 2021, 8 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/880,552, mailed on Dec. 1, 2020, 7 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/880,552, mailed on Jul. 23, 2021, 5 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/880,552, mailed on May 12, 2021, 7 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/880,552, mailed on Nov. 24, 2021, 5 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/880,714, mailed on Jun. 9, 2021, 6 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/880,714, mailed on Mar. 19, 2021, 7 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/894,309, mailed on Feb. 25, 2022, 9 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/894,309, mailed on Nov. 5, 2021, 12 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/907,261, mailed on Aug. 13, 2021, 8 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/907,261, mailed on Sep. 28, 2021, 6 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/921,312, mailed on Nov. 29, 2021, 5 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/921,312, mailed on Sep. 14, 2021, 9 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/953,781, mailed on Feb. 27, 2023, 5 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/953,781, mailed on Nov. 9, 2022, 7 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/990,846, mailed on Jan. 20, 2022, 6 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/990,846, mailed on Sep. 22, 2021, 9 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/031,704, mailed on Jul. 21, 2021, 10 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/031,717, mailed on Jul. 7, 2022, 12 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/031,717, mailed on Mar. 16, 2022, 12 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/031,727, mailed on Dec. 24, 2020, 12 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/031,727, mailed on Jun. 25, 2021, 6 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/031,727, mailed on Mar. 12, 2021, 7 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/031,779, mailed on Feb. 1, 2023, 11 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/041,415, mailed on Aug. 31, 2022, 7 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/317,084, mailed on Aug. 29, 2022, 10 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/317,084, mailed on Jan. 6, 2023, 6 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/952,053, mailed on Apr. 17, 2023, 6 pages. |
| Office Action received for Australian Patent Application No. 2013406817, mailed on Aug. 1, 2017, 3 pages. |
| Office Action received for Australian Patent Application No. 2013406817, mailed on Nov. 14, 2016, 4 pages. |
| Office Action received for Australian Patent Application No. 2018201260, mailed on Feb. 12, 2019, 6 pages. |
| Office Action received for Australian Patent Application No. 2018201260, mailed on Jul. 17, 2019, 3 pages. |
| Office Action received for Australian Patent Application No. 2018201260, mailed on Sep. 5, 2019, 5 pages. |
| Office Action received for Australian Patent Application No. 2019100222, mailed on May 24, 2019, 6 pages. |
| Office Action received for Australian Patent Application No. 2019100495, mailed on Mar. 6, 2020, 3 pages. |
| Office Action received for Australian Patent Application No. 2019100495, mailed on Mar. 16, 2020, 3 pages. |
| Office Action received for Australian Patent Application No. 2019100495, mailed on Sep. 17, 2019, 7 pages. |
| Office Action received for Australian Patent Application No. 2019210192, mailed on May 25, 2021, 4 pages. |
| Office Action received for Australian Patent Application No. 2019210192, mailed on Sep. 9, 2021, 4 pages. |
| Office Action received for Australian Patent Application No. 2019222943, mailed on Oct. 3, 2019, 3 pages. |
| Office Action received for Australian Patent Application No. 2019234289, mailed on Jul. 20, 2021, 4 pages. |
| Office Action received for Australian Patent Application No. 2019234289, mailed on Mar. 16, 2021, 8 pages. |
| Office Action received for Australian Patent Application No. 2019234289, mailed on Nov. 1, 2021, 4 pages. |
| Office Action received for Australian Patent Application No. 2019234289, mailed on Nov. 2, 2020, 6 pages. |
| Office Action received for Australian Patent Application No. 2020230340, mailed on Mar. 2, 2021, 6 pages. |
| Office Action received for Australian Patent Application No. 2020230340, mailed on May 27, 2021, 5 pages. |
| Office Action received for Australian Patent Application No. 2020230340, mailed on Nov. 2, 2020, 5 pages. |
| Office Action received for Australian Patent Application No. 2020230340, mailed on Oct. 11, 2021, 4 pages. |
| Office Action received for Australian Patent Application No. 2020239692, mailed on Jan. 27, 2022, 3 pages. |
| Office Action received for Australian Patent Application No. 2020239692, mailed on Jul. 20, 2021, 5 pages. |
| Office Action received for Australian Patent Application No. 2020239740, mailed on Jul. 9, 2021, 4 pages. |
| Office Action received for Australian Patent Application No. 2020239740, mailed on Sep. 28, 2021, 5 pages. |
| Office Action received for Australian Patent Application No. 2020256383, mailed on Jun. 4, 2021, 3 pages. |
| Office Action received for Australian Patent Application No. 2020313970, mailed on Dec. 22, 2022, 3 pages. |
| Office Action received for Australian Patent Application No. 2021261861, mailed on Jan. 12, 2023, 4 pages. |
| Office Action received for Australian Patent Application No. 2021261861, mailed on Oct. 14, 2022, 5 pages. |
| Office Action received for Australian Patent Application No. 2021266294, mailed on Nov. 11, 2022, 3 pages. |
| Office Action received for Australian Patent Application No. 2022201823, mailed on Mar. 9, 2023, 3 pages. |
| Office Action received for Australian Patent Application No. 2022202459, mailed on Jan. 6, 2023, 3 pages. |
| Office Action received for Australian Patent Application No. 2022204568, mailed on Mar. 11, 2023, 4 pages. |
| Office Action received for Chinese Patent Application No. 201380081315.7, mailed on Aug. 16, 2018, 6 pages. |
| Office Action received for Chinese Patent Application No. 201380081315.7, mailed on Mar. 2, 2018, 12 pages. |
| Office Action received for Chinese Patent Application No. 201910204981.4, mailed on Nov. 29, 2022, 14 pages. |
| Office Action received for Chinese Patent Application No. 201910858933.7, mailed on Aug. 18, 2020, 14 pages. |
| Office Action received for Chinese Patent Application No. 201910858933.7, mailed on Dec. 30, 2021, 9 pages. |
| Office Action received for Chinese Patent Application No. 201910858933.7, mailed on Jun. 29, 2021, 8 pages. |
| Office Action received for Chinese Patent Application No. 201910972529.2, mailed on Jun. 28, 2020, 8 pages. |
| Office Action received for Chinese Patent Application No. 202010606407.4, mailed on Jan. 27, 2021, 16 pages. |
| Office Action received for Chinese Patent Application No. 202010606407.4, mailed on Jun. 2, 2021, 12 pages. |
| Office Action received for Chinese Patent Application No. 202010606407.4, mailed on Nov. 18, 2021, 6 pages. |
| Office Action received for Chinese Patent Application No. 202010618240.3, mailed on Dec. 3, 2021, 23 pages. |
| Office Action received for Chinese Patent Application No. 202010618240.3, mailed on Mar. 29, 2021, 21 pages. |
| Office Action received for Chinese Patent Application No. 202010618240.3, mailed on May 25, 2022, 20 pages. |
| Office Action received for Chinese Patent Application No. 202010618240.3, mailed on Sep. 21, 2022, 16 pages. |
| Office Action received for Chinese Patent Application No. 202010618569.X, mailed on Mar. 12, 2021, 14 pages. |
| Office Action received for Chinese Patent Application No. 202010618569.X, mailed on Sep. 7, 2021, 7 pages. |
| Office Action received for Chinese Patent Application No. 202011220489.5, mailed on Apr. 25, 2022, 15 pages. |
| Office Action received for Chinese Patent Application No. 202011220489.5, mailed on Dec. 1, 2021, 19 pages. |
| Office Action received for Chinese Patent Application No. 202011220489.5, mailed on Jun. 1, 2021, 12 pages. |
| Office Action received for Chinese Patent Application No. 202111611270.2, mailed on May 10, 2022, 16 pages. |
| Office Action received for Chinese Patent Application No. 202180053264.1, mailed on Sep. 23, 2023, 17 pages. |
| Office Action received for Chinese Patent Application No. 202210004176.9, mailed on Sep. 28, 2022, 12 pages. |
| Office Action received for Danish Patent Application No. PA201870378, mailed on Feb. 25, 2019, 3 pages. |
| Office Action received for Danish Patent Application No. PA201870378, mailed on Jan. 6, 2020, 3 pages. |
| Office Action received for Danish Patent Application No. PA201870379, mailed on Feb. 28, 2019, 3 pages. |
| Office Action received for Danish Patent Application No. PA201870380, mailed on Mar. 5, 2020, 2 pages. |
| Office Action received for Danish Patent Application No. PA201870380, mailed on Mar. 27, 2019, 4 pages. |
| Office Action received for Danish Patent Application No. PA201870380, mailed on Sep. 11, 2018, 9 pages. |
| Office Action received for Danish Patent Application No. PA201870599, mailed on Dec. 20, 2019, 5 pages. |
| Office Action received for Danish Patent Application No. PA201870600, mailed on May 8, 2019, 3 pages,. |
| Office Action received for Danish Patent Application No. PA201870601, mailed on Dec. 13, 2018, 8 pages. |
| Office Action received for Danish Patent Application No. PA201870601, mailed on Jan. 14, 2020, 3 pages. |
| Office Action received for Danish Patent Application No. PA201870601, mailed on Jun. 25, 2019, 3 pages. |
| Office Action received for Danish Patent Application No. PA201870602, mailed on Feb. 5, 2020, 3 pages. |
| Office Action received for Danish Patent Application No. PA201870602, mailed on Jun. 26, 2019, 3 pages. |
| Office Action received for Danish Patent Application No. PA201970534, mailed on Feb. 16, 2021, 2 pages. |
| Office Action received for Danish Patent Application No. PA201970534, mailed on Jun. 29, 2020, 2 pages. |
| Office Action received for Danish Patent Application No. PA202070335, mailed on Jun. 11, 2021, 4 pages. |
| Office Action received for Danish Patent Application No. PA202070335, mailed on Nov. 17, 2021, 6 pages. |
| Office Action received for Danish Patent Application No. PA202070395, mailed on Dec. 15, 2021, 5 pages. |
| Office Action received for Danish Patent Application No. PA202070395, mailed on Oct. 7, 2022, 4 pages. |
| Office Action received for Danish Patent Application No. PA202070619, mailed on Aug. 27, 2021, 12 pages. |
| Office Action received for Danish Patent Application No. PA202070619, mailed on Oct. 14, 2021, 3 pages. |
| Office Action received for Danish Patent Application No. PA202070620, mailed on May 10, 2021, 5 pages. |
| Office Action received for Danish Patent Application No. PA202070620, mailed on Nov. 19, 2021, 2 pages. |
| Office Action received for European Patent Application No. 19703582.7, mailed on Jan. 11, 2023, 11 pages. |
| Office Action received for European Patent Application No. 19721883.7, mailed on Jan. 10, 2020, 4 pages. |
| Office Action received for European Patent Application No. 19721883.7, mailed on Jun. 15, 2021, 9 pages. |
| Office Action received for European Patent Application No. 19721883.7, mailed on May 28, 2020, 11 pages. |
| Office Action received for European Patent Application No. 19726205.8, mailed on Jun. 26, 2020, 9 pages. |
| Office Action received for European Patent Application No. 20180581.9, mailed on Apr. 1, 2021, 11 pages. |
| Office Action received for European Patent Application No. 20180592.6, mailed on Apr. 1, 2021, 11 pages. |
| Office Action received for European Patent Application No. 20182116.2, mailed on May 25, 2021, 9 pages. |
| Office Action received for European Patent Application No. 20182116.2, mailed on Nov. 6, 2020, 9 pages. |
| Office Action received for European Patent Application No. 20203526.7, mailed on Nov. 23, 2021, 9 pages. |
| Office Action received for European Patent Application No. 20746438.9, mailed on Feb. 1, 2023, 9 pages. |
| Office Action received for European Patent Application No. 20746438.9, mailed on Oct. 31, 2022, 7 pages. |
| Office Action received for European Patent Application No. 20760607.0, mailed on Feb. 1, 2023, 13 pages. |
| Office Action received for European Patent Application No. 13812320.3, mailed on Mar. 28, 2018, 7 pages. |
| Office Action received for Indian Patent Application No. 201617016494, mailed on Apr. 27, 2020, 7 pages. |
| Office Action received for Indian Patent Application No. 202014041484, mailed on Dec. 8, 2021, 8 pages. |
| Office Action received for Japanese Patent Application No. 2018-184532, mailed on Mar. 1, 2021, 11 pages. |
| Office Action received for Japanese Patent Application No. 2019-162293, mailed on Jan. 31, 2020, 8 pages. |
| Office Action received for Japanese Patent Application No. 2019-162293, mailed on Jul. 27, 2020, 9 pages. |
| Office Action received for Japanese Patent Application No. 2020-104679, mailed on Sep. 18, 2020, 13 pages. |
| Office Action received for Japanese Patent Application No. 2020-153166, mailed on May 31, 2021, 6 pages. |
| Office Action received for Japanese Patent Application No. 2020-160023, mailed on Jan. 17, 2022, 11 pages. |
| Office Action received for Japanese Patent Application No. 2020-547369, mailed on Apr. 9, 2021, 4 pages. |
| Office Action received for Japanese Patent Application No. 2020-551585, mailed on Jan. 6, 2022, 11 pages. |
| Office Action received for Japanese Patent Application No. 2021-167557, mailed on Aug. 15, 2022, 5 pages. |
| Office Action received for Japanese Patent Application No. 2021-192437, mailed on Dec. 16, 2022, 4 pages. |
| Office Action received for Korean Patent Application No. 10-2016-7014353, mailed on Mar. 21, 2018, 11 pages. |
| Office Action received for Korean Patent Application No. 10-2019-7025538, mailed on Aug. 15, 2020, 8 pages. |
| Office Action received for Korean Patent Application No. 10-2019-7025538, mailed on Feb. 17, 2020, 12 pages. |
| Office Action received for Korean Patent Application No. 10-2020-0124134, mailed on Jul. 28, 2022, 22 pages. |
| Office Action received for Korean Patent Application No. 10-2020-7023277, mailed on Jan. 26, 2022, 11 pages. |
| Office Action received for Korean Patent Application No. 10-2020-7026035, mailed on Feb. 19, 2021, 13 pages. |
| Office Action received for Korean Patent Application No. 10-2020-7026391, mailed on Jan. 27, 2021, 5 pages. |
| Office Action received for Korean Patent Application No. 10-2020-7026453, mailed on Jan. 27, 2021, 5 pages. |
| Office Action received for Korean Patent Application No. 10-2020-7033395, mailed on Aug. 29, 2022, 11 pages. |
| Office Action received for Korean Patent Application No. 10-2022-7036381, mailed on Jan. 6, 2023, 10 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. |
| Result of Consultation received for European Patent Application No. 19721883.7, mailed on Oct. 7, 2020. 3 pages. |
| Result of Consultation received for European Patent Application No. 19726205.8, mailed on Mar. 15, 2021, 19 pages. |
| Result of Consultation received for European Patent Application No. 20180581.9, mailed on Jan. 21, 2022, 14 pages. |
| Result of Consultation received for European Patent Application No. 20180592.6, mailed on Jan. 26, 2022, 18 pages. |
| 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. |
| Search Report and Opinion received for Danish Patent Application No. PA201870378, mailed on Sep. 10, 2018, 9 pages. |
| Search Report and Opinion received for Danish Patent Application No. PA201870379, mailed on Sep. 14, 2018, 9 pages. |
| Search Report and Opinion received for Danish Patent Application No. PA201870599, mailed on Dec. 21, 2018, 9 pages. |
| Search Report and Opinion received for Danish Patent Application No. PA201870600, mailed on Jan. 31, 2019, 8 pages. |
| Search Report and Opinion received for Danish Patent Application No. PA201870602, mailed on Dec. 19, 2018, 8 pages. |
| Search Report and Opinion received for Danish Patent Application No. PA201970534, mailed on Sep. 23, 2019, 6 pages. |
| Search Report and Opinion received for Danish Patent Application No. PA202070335, mailed on Nov. 27, 2020, 10 pages. |
| Search Report and Opinion received for Danish Patent Application No. PA202070395, mailed on Nov. 24, 2020, 10 pages. |
| Search Report and Opinion received for Danish Patent Application No. PA202070619, mailed on Dec. 2, 2020, 11 pages. |
| Search Report and Opinion received for Danish Patent Application No. PA202070620, mailed on Dec. 11, 2020, 9 pages. |
| 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. |
| Summons to Attend Oral Proceedings received for European Patent Application No. 13812320.3, mailed on Mar. 12, 2021, 9 pages. |
| Summons to Attend Oral Proceedings received for European Patent Application No. 19726205.8, mailed on Oct. 29, 2020, 13 pages. |
| Summons to Attend Oral Proceedings received for European Patent Application No. 20180581.9, mailed on Aug. 18, 2021, 15 pages. |
| Summons to Attend Oral Proceedings received for European Patent Application No. 20180592.6, mailed on Aug. 11, 2021, 16 pages. |
| Summons to Attend Oral Proceedings received for European Patent Application No. 20182116.2, mailed on Dec. 21, 2021, 7 pages. |
| Summons to Attend Oral Proceedings received for European Patent Application No. 20203526.7, mailed on Jun. 23, 2022, 9 pages. |
| Supplemental Notice of Allowance received for U.S. Appl. No. 16/144,849, mailed on Mar. 31, 2020, 2 pages. |
| Supplemental Notice of Allowance received for U.S. Appl. No. 16/880,714, mailed on Sep. 16, 2021, 2 pages. |
| Supplemental Notice of Allowance received for U.S. Appl. No. 16/894,309, mailed on Apr. 8, 2022, 3 pages. |
| Supplemental Notice of Allowance received for U.S. Appl. No. 16/894,309, mailed on Dec. 24, 2021, 2 pages. |
| Supplemental Notice of Allowance received for U.S. Appl. No. 16/894,309, mailed on Jan. 25, 2022, 2 pages. |
| Supplemental Notice of Allowance received for U.S. Appl. No. 17/031,727, mailed on Jan. 15, 2021, 2 pages. |
| Supplemental Notice of Allowance received for U.S. Appl. No. 17/041,415, mailed on Oct. 13, 2022, 2 pages. |
| Supplemental Notice of Allowance received for U.S. Appl. No. 17/041,415, mailed on Sep. 20, 2022, 2 pages. |
| Supplemental Notice of Allowance received for U.S. Appl. No. 17/317,084, mailed on Jan. 19, 2023, 2 pages. |
| Supplemental Notice of Allowance received for U.S. Appl. No. 17/317,084. mailed on Sep. 20, 2022, 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. |
| Suunto, “Suunto Spartan—Heart Rate Zones”, Online Available at :—https://www.youtube.com/watch?v=aixfoCnS0OU, Mar. 19, 2018, 2 page. |
| Tech, Kalyani,“I See Some problems in Honor Band 5”, Retrieved from: https://www.youtube.com/watch?v=5XPnYJFqajl, May 19, 2020, 1 page. |
| Teunmo, “Data field: Visual Pace Alarm”, Garmin Forum; Available online at: https://forums.garmin.com/forum/developers/connect-iq/connect-iq-showcase/115996-data-field-visual-pace-alarm, Nov. 17, 2015, 10 pages. |
| Ticks, Smartwatch,“Senbono S10 IP67 Waterproof Multi-Function Blood Pressure Sports Smartwatch: One Minute Overview”, Retrieved from: https://www.youtube.com/watch?v=rMxLJvKIVBs, Oct. 30, 2019, 1 page. |
| TomTom, “TomTom Runner & Multi-Sport Reference Guide”, Online available at :—https://web.archive.org/web/20150908075934/http://download.tomtom.com/open/manuals/Runner_Multi-Sport/refman/TomTom-Runner-Multi-Sport-RG-en-gb.pdf, Sep. 8, 2015, 44 pages. |
| Visual Pace Alarm app, Available Online at: https://apps.garmin.com/en-us/apps/3940f3a2-4847-4078-a911-d77422966c82, Oct. 19, 2016, 1 page. |
| Weiyu et al., “A Multi-identities Authentication and Authorization Schema in Cloud Computing”, Aug. 20, 2012, pp. 7-10. |
| 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. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/851,451, mailed on Feb. 20, 2024, 3 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/135,710, mailed on Feb. 14, 2024, 4 pages. |
| Office Action received for Chinese Patent Application No. 201980018078.7, mailed on Nov. 25, 2023, 20 pages (9 pages of English Translation and 11 pages of Official Copy). |
| Office Action received for Indian Patent Application No. 202315061713, mailed on Feb. 14, 2024, 8 pages. |
| Office Action received for Indian Patent Application No. 202315061718, mailed on Feb. 14, 2024, 8 pages. |
| Extended European Search Report received for European Patent Application No. 23200361.6, mailed on Mar. 28, 2024, 10 pages. |
| Final Office Action received for U.S. Appl. No. 16/249,627, mailed on Apr. 3, 2024, 23 pages. |
| Notice of Allowance received for Chinese Patent Application No. 201980018078.7, mailed on Mar. 28, 2024, 2 pages (1 page of English Translation and 1 page of Official Copy). |
| Office Action received for Japanese Patent Application No. 2023-028769, mailed on Apr. 1, 2024, 8 pages (4 pages of English Translation and 4 pages of Official Copy). |
| Final Office Action received for U.S. Appl. No. 17/584,190, mailed on Mar. 13, 2024, 20 pages. |
| Intention to Grant received for European Patent Application No. 20746438.9, mailed on Mar. 21, 2024, 15 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2023/031421, mailed on Feb. 9, 2024, 22 pages. |
| Invitation to Pay Additional Fees and Partial International Search Report received for PCT Patent Application No. PCT/US2023/031421, mailed on Dec. 1, 2023, 10 pages. |
| Office Action received for Australian Patent Application No. 2021283914, mailed on Mar. 14, 2024, 5 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2022-131993, mailed on Dec. 18, 2023, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Office Action received for Japanese Patent Application No. 2022-573764, mailed on Dec. 25, 2023, 8 pages (4 pages of English Translation and 4 pages of Official Copy). |
| Final Office Action received for U.S. Appl. No. 16/888,780, mailed on Feb. 29, 2024, 12 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2022-573764, mailed on Feb. 26, 2024, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 202180053264.1, mailed on Jan. 18, 2024, 14 pages (8 pages of English Translation and 6 pages of Official Copy). |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/249,627, mailed on Aug. 1, 2023, 3 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/249,627, mailed on Nov. 21, 2023, 5 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/851,451, mailed on Apr. 20, 2023, 4 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/888,780, mailed on Dec. 14, 2023, 3 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/031,723, mailed on Jun. 22, 2023, 2 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/031,723, mailed on Oct. 31, 2023, 4 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/584,190, mailed on Dec. 4, 2023, 5 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/953,781, mailed on Mar. 30, 2023, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 17/031,779, mailed on Jun. 14, 2023, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 17/135,710, mailed on Aug. 18, 2023, 4 pages. |
| Decision on Appeal received for Korean Patent Application No. 10-2020-0124134, mailed on Oct. 20, 2023, 24 pages (4 pages of English Translation and 20 pages of Official Copy). |
| Final Office Action received for U.S. Appl. No. 16/249,627, mailed on Jun. 30, 2023, 19 pages. |
| Final Office Action received for U.S. Appl. No. 16/851,451, mailed on Jun. 1, 2023, 35 pages. |
| Final Office Action received for U.S. Appl. No. 17/031,723. mailed on Oct. 4, 2023, 13 pages. |
| Final Office Action received for U.S. Appl. No. 17/337,147, mailed on Oct. 31, 2023, 17 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/249,627, mailed on Oct. 31, 2023, 23 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/888,780, mailed on Aug. 17, 2023, 12 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/031,723, mailed on Jun. 2, 2023, 23 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/584,190, mailed on Oct. 5, 2023, 17 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/952,182, mailed on Mar. 28, 2023, 9 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2020313970, mailed on Jun. 22, 2023, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2022201823, mailed on Sep. 26, 2023, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2022202459, mailed on May 11, 2023, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2022203508, mailed on Jun. 27, 2023, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2022204568, mailed on Jul. 27, 2023, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2023212604, mailed on Oct. 12, 2023, 3 pages. |
| Notice of Allowance received for Chinese Patent Application No. 201910204981.4, mailed on Aug. 2, 2023, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for Japanese Patent Application No. 2021-192437, mailed on May 19, 2023, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for Japanese Patent Application No. 2022-078277, mailed on Oct. 27, 2023, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for Japanese Patent Application No. 2022-078280, mailed on Sep. 4, 2023, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for Japanese Patent Application No. 2022-502594, mailed on Jul. 7, 2023, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for Korean Patent Application No. 10-2020-0124134, mailed on Nov. 21, 2023, 8 pages (2 pages of English Translation and 6 pages of Official Copy). |
| Notice of Allowance received for Korean Patent Application No. 10-2022-7036381, mailed on Jul. 12, 2023, 7 pages (2 pages of English Translation and 5 pages of Official Copy). |
| Notice of Allowance received for U.S. Appl. No. 17/031,779, mailed on May 26, 2023, 9 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/135,710, mailed on Jul. 27, 2023, 9 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/135,710, mailed on Nov. 6, 2023, 7 pages. |
| Notice of Allowance received for U.S. Appl. No. 18/078,444, mailed on Aug. 31, 2023, 6 pages. |
| Notice of Allowance received for U.S. Appl. No. 18/078,444, mailed on May 12, 2023, 9 pages. |
| Notice of Hearing received for Indian Patent Application No. 201617016494, mailed on Apr. 10, 2023, 2 pages. |
| Office Action received for Australian Patent Application No. 2020313970, mailed on Mar. 22, 2023, 4 pages. |
| Office Action received for Australian Patent Application No. 2021261861, mailed on May 3, 2023, 4 pages. |
| Office Action received for Australian Patent Application No. 2021261861, mailed on Sep. 22, 2023, 5 pages. |
| Office Action received for Australian Patent Application No. 2021283914, mailed on Sep. 25, 2023, 5 pages. |
| Office Action received for Australian Patent Application No. 2022201823, mailed on Jun. 26, 2023, 6 pages,. |
| Office Action received for Australian Patent Application No. 2022202459, mailed on Mar. 27, 2023, 5 pages. |
| Office Action received for Australian Patent Application No. 2022203508, mailed on May 19, 2023, 2 pages. |
| Office Action received for Australian Patent Application No. 2022204568, mailed on May 22, 2023, 4 pages. |
| Office Action received for Australian Patent Application No. 2023212604, mailed on Sep. 4, 2023, 3 pages. |
| Office Action received for Chinese Patent Application No. 201910204981.4, mailed on Apr. 29, 2023, 12 pages (4 pages of English Translation and 8 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 202210004176.9, mailed on Apr. 28, 2023, 12 pages (6 pages of English Translation and 6 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 202210004176.9, mailed on Feb. 19, 2023, 23 pages (14 pages of English Translation and 9 pages of Official Copy). |
| Office Action received for Danish Patent Application No. PA202070395, mailed on Jul. 5, 2023, 6 pages. |
| Office Action received for Danish Patent Application No. PA202070395, mailed on Mar. 31, 2023, 3 pages. |
| Office Action received for Danish Patent Application No. PA202070395, mailed on Nov. 3, 2023, 3 pages. |
| Office Action received for European Patent Application No. 20746438.9, mailed on Jul. 4, 2023, 7 pages. |
| Office Action received for European Patent Application No. 20746438.9, mailed on Oct. 31, 2023, 9 pages. |
| Office Action received for European Patent Application No. 20751022.3, mailed on Oct. 19, 2023, 8 pages. |
| Office Action received for European Patent Application No. 20753659.0, mailed on Oct. 26, 2023, 9 pages. |
| Office Action received for European Patent Application No. 20760607.0, mailed on Aug. 17, 2023, 7 pages. |
| Office Action received for German Patent Application No. 112020002566.7, mailed on Mar. 24, 2023, 32 pages (14 pages of English Translation and 18 pages of official copy). |
| Office Action received for Indian Patent Application No. 202215032692, mailed on Jun. 15, 2023, 3 pages. |
| Office Action received for Japanese Patent Application No. 2022-078277, mailed on Jun. 9, 2023, 11 pages (6 pages of English Translation and 5 pages of Official Copy). |
| Office Action received for Japanese Patent Application No. 2022-078280, mailed on 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, mailed on Sep. 15, 2023, 6 pages (3 pages of English Translation and 3 pages of Official Copy). |
| Office Action received for Japanese Patent Application No. 2022-502594, mailed on Mar. 20, 2023, 10 pages (5 pages of English Translation and 5 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2020-0124134, mailed on Jun. 23, 2023, 8 pages (4 pages of English Translation and 4 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2020-0124134, mailed on Mar. 28, 2023, 9 pages (4 pages of English Translation and 5 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2022-7012608, mailed on Dec. 5, 2023, 12 pages (5 pages of English Translation and 7 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2023-7034892, mailed on Nov. 8, 2023, 5 pages (2 pages of English Translation and 3 pages of Official Copy). |
| Supplemental Notice of Allowance received for U.S. Appl. No. 18/078,444, mailed on Jun. 15, 2023, 2 pages. |
| Supplemental Notice of Allowance received for U.S. Appl. No. 18/078,444, mailed on Oct. 16, 2023, 4 pages. |
| Dabek et al., “A timeline-based framework for aggregating and summarizing electronic health records”, IEEE Workshop on Visual Analytics in Healthcare (VAHC), available online at: https://www.researchgate.net/publication/325833364_A_timeline-based framework_for_aggregating_and_summarizing_electronic_health_records, 2017, 7 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. |
| Kardia By Alivecor, “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. |
| 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. |
| 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. |
| Prasad et al., “Understanding Sharing Preferences and Behavior for Mheaith 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. |
| Final Office Action received for U.S. Appl. No. 17/952,182, mailed on Jan. 4, 2024, 9 pages. |
| Office Action received for Australian Patent Application No. 2021283914, mailed on Dec. 13, 2023, 5 pages. |
| Office Action received for European Patent Application No. 20760607.0, mailed on Jan. 3, 2024, 7 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 17/952,053, mailed on Jan. 25, 2024, 6 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/554,678, mailed on Feb. 1, 2024, 10 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/851,451, mailed on Jan. 31, 2024, 13 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/135,710, mailed on Jan. 23, 2024, 7 pages. |
| Office Action received for Korean Patent Application No. 10-2023-7018399, mailed on Jan. 24, 2024, 11 pages (4 pages of English Translation and 7 pages of Official Copy). |
| Number | Date | Country | |
|---|---|---|---|
| 20240053862 A1 | Feb 2024 | US |
| Number | Date | Country | |
|---|---|---|---|
| 63072889 | Aug 2020 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 17952053 | Sep 2022 | US |
| Child | 18222386 | US | |
| Parent | 16953781 | Nov 2020 | US |
| Child | 17952053 | US |
