Patent Grant
10987028
The present disclosure relates generally to user interfaces and more specifically to techniques for displaying user interfaces associated with physical activities.
Many modern electronic devices provide the capability of tracking physical activities by a user. Such electronic devices often display information associated with the physical activities to the user. Some techniques provide the ability to compare the physical activities of the user with physical activities of other users. Other techniques provide the ability to begin and end tracking of a physical activity. Other techniques provide the ability to set pace alerts for a physical activity. However, such techniques can be cumbersome and inefficient.
Some techniques for displaying user interfaces associated with physical activities using electronic devices 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 displaying user interfaces associated with physical activities. Such methods and interfaces optionally complement or replace other methods for displaying user interfaces associated with physical activities. 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.
A system of one or more computers can be configured to perform particular operations or actions by virtue of having software, firmware, hardware, or a combination of them installed on the system that in operation causes or cause the system to perform the actions. One or more computer programs can be configured to perform particular operations or actions by virtue of including instructions that, when executed by data processing apparatus, cause the apparatus to perform the actions.
One general aspect includes a method performed at an electronic device including a display. The method includes receiving first user activity data for a time period, the first user activity data including at least first user activity data for a first time subset and first user activity data for a second time subset. The method further includes receiving second user activity data for the time period, the second user activity data including at least second user activity data for the first time subset and second user activity data for the second time subset. The method further includes displaying, on the display, a user interface including: (1) a representation of the first user activity data for the first time subset; (2) a representation of the first user activity data for the second time subset; (3) a cumulative representation of the first user activity data for the time period, where the cumulative representation of the first user activity data for the time period is based on at least the first user activity data for a first time subset and the first user activity data for a second time subset; (4) a representation of the second user activity data for the first time subset; (5) a representation of the second user activity data for the second time subset; and (6) a cumulative representation of the second user activity data for the time period, where the cumulative representation of the second user activity data for the time period is based on at least the second user activity data for a first time subset and the second user activity data for a second time subset. Other examples of this aspect include corresponding computer systems, apparatus, and computer programs recorded on one or more computer storage devices, each configured to perform the actions of the methods.
One general aspect includes a method performed at an electronic device including a display. The method includes receiving first user activity data for a first user, where the first user activity data corresponds to a first time period and a second time period. The method further includes receiving second user activity data for a second user, where the second user activity data corresponds to the first time period, and where the first time period includes a first elapsed sub-period and a first unelapsed sub-period for an activity competition between the first user and the second user. The method further includes receiving third user activity data for the third user, where the third user activity data corresponds to the second time period, and where the second time period includes a second elapsed sub-period and a second unelapsed sub-period for an activity competition between the first user and the third user. The method further includes displaying, on the display, a user interface including: (1) a representation of the first user activity data and the second user activity data during the first elapsed sub-period for the activity competition between the first user and the second user; (2) an indication of an amount of time in the first unelapsed sub-period for the activity competition between the first user and the second user; (3) a representation of the first activity data and the third activity data during the second elapsed sub-period for the activity competition between the first user and the third user; and (4) an indication of an amount of time in the second unelapsed sub-period for the activity competition between the first user and the third user. Other examples of this aspect include corresponding computer systems, apparatus, and computer programs recorded on one or more computer storage devices, each configured to perform the actions of the methods.
One general aspect includes a method performed at an electronic device including a display and one or more sensors. The method includes detecting, via the one or more sensors, activity data. The method further includes, in response to detecting the activity data and in accordance with a determination that the activity data satisfies activity boundary alert criteria, displaying an activity boundary alert. The method further includes, in further response to detecting the activity data and in accordance with a determination that the activity data does not satisfy the activity boundary alert criteria, forgoing display of the activity boundary alert. Other examples of this aspect include corresponding computer systems, apparatus, and computer programs recorded on one or more computer storage devices, each configured to perform the actions of the methods.
One general aspect includes a method performed at an electronic device. The method includes displaying a physical activity rate user interface including a first setting affordance and a second setting affordance. The method further includes. while displaying the physical activity rate user interface, receiving a first user input. The method further includes, in response to receiving the first user input and in accordance with the first user input corresponding to selection of the first setting affordance, configuring a physical activity rate calculation to use a first portion of a dataset. The method further includes, in response to receiving the first user input and in accordance with the first user input corresponding to selection of the second setting affordance, configuring a physical activity rate calculation to use a second portion of the dataset different from the first portion. Other examples of this aspect include corresponding computer systems, apparatus, and computer programs recorded on one or more computer storage devices, each configured to perform the actions of the methods.
One general aspect includes a non-transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of an electronic device with a display, the one or more programs including instructions for any of the methods described above.
One general aspect includes a transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of an electronic device with a display, the one or more programs including instructions for any of the methods described above.
One general aspect includes an electronic device, including a display. The electronic device also includes one or more processors. The electronic device also includes memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for performing any of the methods described above.
One general aspect includes an electronic device, including a display. The electronic device also includes means for receiving first user activity data for a time period, the first user activity data including at least first user activity data for a first time subset and first user activity data for a second time subset. The electronic device also includes means for receiving second user activity data for the time period, the second user activity data including at least second user activity data for the first time subset and second user activity data for the second time subset. The electronic device also includes means for displaying, on the display, a user interface including: (1) a representation of the first user activity data for the first time subset; (2) a representation of the first user activity data for the second time subset; (3) a cumulative representation of the first user activity data for the time period, where the cumulative representation of the first user activity data for the time period is based on at least the first user activity data for a first time subset and the first user activity data for a second time subset; (4) a representation of the second user activity data for the first time subset; (5) a representation of the second user activity data for the second time subset; (6) and a cumulative representation of the second user activity data for the time period, where the cumulative representation of the second user activity data for the time period is based on at least the second user activity data for a first time subset and the second user activity data for a second time subset.
One general aspect includes an electronic device, including a display. The electronic device also includes means for receiving first user activity data for a first user, where the first user activity data corresponds to a first time period and a second time period. The electronic device also includes means for receiving second user activity data for a second user, where the second user activity data corresponds to the first time period, and where the first time period includes a first elapsed sub-period and a first unelapsed sub-period for an activity competition between the first user and the second user. The electronic device also includes means for receiving third user activity data for the third user, where the third user activity data corresponds to the second time period, and where the second time period includes a second elapsed sub-period and a second unelapsed sub-period for an activity competition between the first user and the third user. The electronic device also includes means for displaying, on the display, a user interface including: (1) a representation of the first user activity data and the second user activity data during the first elapsed sub-period for the activity competition between the first user and the second user; (2) an indication of an amount of time in the first unelapsed sub-period for the activity competition between the first user and the second user; (3) a representation of the first activity data and the third activity data during the second elapsed sub-period for the activity competition between the first user and the third user; and (4) an indication of an amount of time in the second unelapsed sub-period for the activity competition between the first user and the third user.
One general aspect includes an electronic device, including a display. The electronic device also includes means for detecting, via the one or more sensors, activity data. The electronic device also includes a means for, in response to detecting the activity data and in accordance with a determination that the activity data satisfies activity boundary alert criteria, displaying an activity boundary alert. The electronic device also includes a means for, in response to detecting the activity data and in accordance with a determination that the activity data does not satisfy the activity boundary alert criteria, forgoing display of the activity boundary alert.
One general aspect includes an electronic device, including a display. The electronic device also includes means for displaying a physical activity rate user interface including a first setting affordance and a second setting affordance. The electronic device also includes means for, while displaying the physical activity rate user interface, receiving a first user input. The electronic device also includes means for, in response to receiving the first user input and in accordance with the first user input corresponding to selection of the first setting affordance, configuring a physical activity rate calculation to use a first portion of a dataset. The electronic device also includes means for, in response to receiving the first user input and in accordance with the first user input corresponding to selection of the second setting affordance, configuring a physical activity rate calculation to use a second portion of the dataset different from the first portion.
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 displaying user interfaces associated with physical activities, thereby increasing the effectiveness, efficiency, and user satisfaction with such devices. Such methods and interfaces may complement or replace other methods for displaying user interfaces associated with physical activities.
For a better understanding of the various described examples, reference should be made to the Description of Examples 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 examples.
There is a need for electronic devices that provide efficient methods and interfaces for displaying user interfaces associated with physical activities. Such techniques can reduce the cognitive burden on a user who accesses user interfaces associated with physical activities, 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 examples. 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 examples herein is for the purpose of describing particular examples only and is not intended to be limiting. As used in the description of the various described examples 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.
Examples of electronic devices, user interfaces for such devices, and associated processes for using such devices are described. In some examples, 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 examples of portable multifunction devices include, without limitation, the iPhone®, iPod Touch®, and iPad® devices from Apple Inc. of Cupertino, Calif. 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 examples, the device is not a portable communications device, but is a desktop computer with a touch-sensitive surface (e.g., a touch screen display and/or a touchpad).
In the discussion that follows, an electronic device that includes a display and a touch-sensitive surface is described. It should be understood, however, that the electronic device optionally includes one or more other physical user-interface devices, such as a physical keyboard, a mouse, and/or a joystick.
The device typically supports a variety of applications, such as one or more of the following: a drawing application, a presentation application, a word processing application, a website creation application, a disk authoring application, a spreadsheet application, a gaming application, a telephone application, a video conferencing application, an e-mail application, an instant messaging application, a workout support application, a photo management application, a digital camera application, a digital video camera application, a web browsing application, a digital music player application, and/or a digital video player application.
The various applications that are executed on the device optionally use at least one common physical user-interface device, such as the touch-sensitive surface. One or more functions of the touch-sensitive surface as well as corresponding information displayed on the device are, optionally, adjusted and/or varied from one application to the next and/or within a respective application. In this way, a common physical architecture (such as the touch-sensitive surface) of the device optionally supports the variety of applications with user interfaces that are intuitive and transparent to the user.
Attention is now directed toward examples 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 examples, peripherals interface 118, CPU 120, and memory controller 122 are, optionally, implemented on a single chip, such as chip 104. In some other examples, 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 examples, audio circuitry 110 also includes a headset jack (e.g., 212,
I/O subsystem 106 couples input/output peripherals on device 100, such as touch screen 112 and other input control devices 116, to peripherals interface 118. I/O subsystem 106 optionally includes display controller 156, optical sensor controller 158, intensity sensor controller 159, haptic feedback controller 161, and one or more input controllers 160 for other input or control devices. The one or more input controllers 160 receive/send electrical signals from/to other input control devices 116. The other input control devices 116 optionally include physical buttons (e.g., push buttons, rocker buttons, etc.), dials, slider switches, joysticks, click wheels, and so forth. In some alternate examples, 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 examples, 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 example, 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 examples. 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 example, projected mutual capacitance sensing technology is used, such as that found in the iPhone® and iPod Touch® from Apple Inc. of Cupertino, Calif.
A touch-sensitive display in some examples 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 examples 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 examples, 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 examples, 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 examples, 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 examples, in addition to the touch screen, device 100 optionally includes a touchpad (not shown) for activating or deactivating particular functions. In some examples, the touchpad is a touch-sensitive area of the device that, unlike the touch screen, does not display visual output. The touchpad is, optionally, a touch-sensitive surface that is separate from touch screen 112 or an extension of the touch-sensitive surface formed by the touch screen.
Device 100 also includes power system 162 for powering the various components. Power system 162 optionally includes a power management system, one or more power sources (e.g., battery, alternating current (AC)), a recharging system, a power failure detection circuit, a power converter or inverter, a power status indicator (e.g., a light-emitting diode (LED)) and any other components associated with the generation, management and distribution of power in portable devices.
Device 100 optionally also includes one or more optical sensors 164.
Device 100 optionally also includes one or more contact intensity sensors 165.
Device 100 optionally also includes one or more proximity sensors 166.
Device 100 optionally also includes one or more tactile output generators 167.
Device 100 optionally also includes one or more accelerometers 168.
In some examples, 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 examples, memory 102 (FIG. 1A) or 370 (
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 examples, 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 examples, contact/motion module 130 and display controller 156 detect contact on a touchpad.
In some examples, 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 examples, 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 examples, graphics module 132 stores data representing graphics to be used. Each graphic is, optionally, assigned a corresponding code. Graphics module 132 receives, from applications etc., one or more codes specifying graphics to be displayed along with, if necessary, coordinate data and other graphic property data, and then generates screen image data to output to display controller 156.
Haptic feedback module 133 includes various software components for generating instructions used by tactile output generator(s) 167 to produce tactile outputs at one or more locations on device 100 in response to user interactions with device 100.
Text input module 134, which is, optionally, a component of graphics module 132, provides soft keyboards for entering text in various applications (e.g., contacts 137, e-mail 140, IM 141, browser 147, and any other application that needs text input).
GPS module 135 determines the location of the device and provides this information for use in various applications (e.g., to telephone 138 for use in location-based dialing; to camera 143 as picture/video metadata; and to applications that provide location-based services such as weather widgets, local yellow page widgets, and map/navigation widgets).
Applications 136 optionally include the following modules (or sets of instructions), or a subset or superset thereof:
Examples of other applications 136 that are, optionally, stored in memory 102 include other word processing applications, other image editing applications, drawing applications, presentation applications, JAVA-enabled applications, encryption, digital rights management, voice recognition, and voice replication.
In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, contacts module 137 are, optionally, used to manage an address book or contact list (e.g., stored in application internal state 192 of contacts module 137 in memory 102 or memory 370), including: adding name(s) to the address book; deleting name(s) from the address book; associating telephone number(s), e-mail address(es), physical address(es) or other information with a name; associating an image with a name; categorizing and sorting names; providing telephone numbers or e-mail addresses to initiate and/or facilitate communications by telephone 138, video conference module 139, e-mail 140, or IM 141; and so forth.
In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, telephone module 138 are optionally, used to enter a sequence of characters corresponding to a telephone number, access one or more telephone numbers in contacts module 137, modify a telephone number that has been entered, dial a respective telephone number, conduct a conversation, and disconnect or hang up when the conversation is completed. As noted above, the wireless communication optionally uses any of a plurality of communications standards, protocols, and technologies.
In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch screen 112, display controller 156, optical sensor 164, optical sensor controller 158, contact/motion module 130, graphics module 132, text input module 134, contacts module 137, and telephone module 138, video conference module 139 includes executable instructions to initiate, conduct, and terminate a video conference between a user and one or more other participants in accordance with user instructions.
In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, e-mail client module 140 includes executable instructions to create, send, receive, and manage e-mail in response to user instructions. In conjunction with image management module 144, e-mail client module 140 makes it very easy to create and send e-mails with still or video images taken with camera module 143.
In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, the instant messaging module 141 includes executable instructions to enter a sequence of characters corresponding to an instant message, to modify previously entered characters, to transmit a respective instant message (for example, using a Short Message Service (SMS) or Multimedia Message Service (MMS) protocol for telephony-based instant messages or using XMPP, SIMPLE, or IMPS for Internet-based instant messages), to receive instant messages, and to view received instant messages. In some examples, 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 examples, a widget includes an HTML (Hypertext Markup Language) file, a CSS (Cascading Style Sheets) file, and a JavaScript file. In some examples, 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 examples, 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 examples, 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 examples. 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 examples, 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 examples, 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 examples, a “menu button” is implemented using a touchpad. In some other examples, 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 examples, 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 examples, 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 examples, 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 examples, event monitor 171 sends requests to the peripherals interface 118 at predetermined intervals. In response, peripherals interface 118 transmits event information. In other examples, 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 examples, 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 examples, active event recognizer determination module 173 determines that only the hit view should receive a particular sequence of sub-events. In other examples, 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 examples, 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 examples 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 examples, event dispatcher module 174 stores in an event queue the event information, which is retrieved by a respective event receiver 182.
In some examples, operating system 126 includes event sorter 170. Alternatively, application 136-1 includes event sorter 170. In yet other examples, 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 examples, 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 examples, one or more of event recognizers 180 are part of a separate module, such as a user interface kit (not shown) or a higher level object from which application 136-1 inherits methods and other properties. In some examples, 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 examples, 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 examples, 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 examples, 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 examples, 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 examples, 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 examples, the event also includes information for one or more associated event handlers 190.
In some examples, event definition 187 includes a definition of an event for a respective user-interface object. In some examples, 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 examples, 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 examples, 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 examples, 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 examples, 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 examples, 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 examples, 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 examples, 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 examples, 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 examples, 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 examples, 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 examples, event handler(s) 190 includes or has access to data updater 176, object updater 177, and GUI updater 178. In some examples, 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 examples, 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 examples, the menu button is implemented as a soft key in a GUI displayed on touch screen 112.
In some examples, 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 example, 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 examples 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 examples, 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 examples, 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 examples, 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 examples, device 500 has one or more attachment mechanisms. Such attachment mechanisms, if included, can permit attachment of device 500 with, for example, hats, eyewear, earrings, necklaces, shirts, jackets, bracelets, watch straps, chains, trousers, belts, shoes, purses, backpacks, and so forth. These attachment mechanisms permit device 500 to be worn by a user.
Input mechanism 508 is, optionally, a microphone, in some examples. Personal electronic device 500 optionally includes various sensors, such as GPS sensor 532, accelerometer 534, directional sensor 540 (e.g., compass), gyroscope 536, motion sensor 538, and/or a combination thereof, all of which can be operatively connected to I/O section 514.
Memory 518 of personal electronic device 500 can include one or more non-transitory computer-readable storage mediums, for storing computer-executable instructions, which, when executed by one or more computer processors 516, for example, can cause the computer processors to perform the techniques described below, including processes 700 (
As used here, the term “affordance” refers to a user-interactive graphical user interface object that is, optionally, displayed on the display screen of devices 100, 300, and/or 500 (
As used herein, the term “focus selector” refers to an input element that indicates a current part of a user interface with which a user is interacting. In some implementations that include a cursor or other location marker, the cursor acts as a “focus selector” so that when an input (e.g., a press input) is detected on a touch-sensitive surface (e.g., touchpad 355 in
As used in the specification and claims, the term “characteristic intensity” of a contact refers to a characteristic of the contact based on one or more intensities of the contact. In some examples, 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 examples, 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 examples, 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 examples, 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 examples, 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 examples, 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 examples, 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 examples, 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 examples, 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 examples, the contact-detection intensity threshold is zero. In some examples, the contact-detection intensity threshold is greater than zero.
In some examples 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 examples, 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 examples, 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 examples, the display of representations 578A-578C includes an animation. For example, representation 578A is initially displayed in proximity of application icon 572B, as shown in
In some examples, 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 examples, 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 examples, the press input is detected only when the device detects an increase in intensity of the contact from an intensity at or below the hysteresis intensity threshold to an intensity at or above the press-input intensity threshold and, optionally, a subsequent decrease in intensity of the contact to an intensity at or below the hysteresis intensity, and the respective operation is performed in response to detecting the press input (e.g., the increase in intensity of the contact or the decrease in intensity of the contact, depending on the circumstances).
For ease of explanation, the descriptions of operations performed in response to a press input associated with a press-input intensity threshold or in response to a gesture including the press input are, optionally, triggered in response to detecting either: an increase in intensity of a contact above the press-input intensity threshold, an increase in intensity of a contact from an intensity below the hysteresis intensity threshold to an intensity above the press-input intensity threshold, a decrease in intensity of the contact below the press-input intensity threshold, and/or a decrease in intensity of the contact below the hysteresis intensity threshold corresponding to the press-input intensity threshold. Additionally, in examples where an operation is described as being performed in response to detecting a decrease in intensity of a contact below the press-input intensity threshold, the operation is, optionally, performed in response to detecting a decrease in intensity of the contact below a hysteresis intensity threshold corresponding to, and lower than, the press-input intensity threshold.
As used herein, an “installed application” refers to a software application that has been downloaded onto an electronic device (e.g., devices 100, 300, and/or 500) and is ready to be launched (e.g., become opened) on the device. In some examples, a downloaded application becomes an installed application by way of an installation program that extracts program portions from a downloaded package and integrates the extracted portions with the operating system of the computer system.
As used herein, the terms “open application” or “executing application” refer to a software application with retained state information (e.g., as part of device/global internal state 157 and/or application internal state 192). An open or executing application is, optionally, any one of the following types of applications:
As used herein, the term “closed application” refers to software applications without retained state information (e.g., state information for closed applications is not stored in a memory of the device). Accordingly, closing an application includes stopping and/or removing application processes for the application and removing state information for the application from the memory of the device. Generally, opening a second application while in a first application does not close the first application. When the second application is displayed and the first application ceases to be displayed, the first application becomes a background application.
Attention is now directed towards examples 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.
Referring to device 600A in
Referring to device 600B in
User interface 612 can include a scrollable list of affordances 614, where each affordance is associated with a different operation. For example, the scrollable list of affordances 614 includes first affordance 614A, second affordance 614B, and third affordance 614C. Selection of first affordance 614A can initiate a sequence to begin an activity competition between Aled and Molly. Selection of second affordance 614B can cause a messaging interface to be displayed (as depicted in
Referring to
User interface 616 includes icon 618. Icon 618 can represent activity competitions between Molly and Aled, such that all activity competitions (e.g., past activity competitions) between Molly and Aled are associated with icon 618. In some examples, activity competitions between different participants (such as Molly and Steve) can be represented by different icons with different visual themes than icon 618. It should be recognized that, in some examples, icons can be assigned to activity competitions prior to display of user interface 616. User interface 616 further includes affordance 620 for indicating an acceptance of the terms in user interface 616 and causing an invitation to begin an activity competition to be sent to Molly (e.g., to device 600A).
Referring to
User interface 622 of device 600A describes rules for an activity competition, similar to user interface 616. User interface 622 includes icon 624 (which can have the same theme as icon 618, as depicted in
Selection of first affordance 626A can accept the invitation for the activity competition sent by Aled. Acceptance of the invitation can cause the activity competition to begin at a predefined time after the selection (e.g., midnight of the current day), as further described below. Selection of second affordance 626B can cause device 600B to reject the invitation (e.g., cause the activity competition to not begin) and cease to display user interface 612.
Referring to
User interface 640 indicates that the invitation that Aled sent was accepted and that the activity competition with Molly will start tomorrow. User interface 640 includes icon 642 (which can have the same theme as icon 618, as depicted in
Referring to
Referring to
Also in response to selection of second affordance 648B in user interface 646 (as depicted in
While an activity competition is active, participants in the activity competition can receive notifications including a status of the activity competition. For example, in response to the activity competition beginning, a notification can be displayed to each of the participants in the activity competition, as depicted in
Referring to
User interface 660 indicates that the activity competition with Molly has begun. User interface 600 includes a scrollable list of affordances 662, where each affordance is associated with a different operation. For example, the scrollable list of affordances 626 includes (1) first affordance 662A for displaying information related to the activity competition, (2) second affordance 662B for displaying a messaging user interface (as depicted in
As depicted in
Selection of first affordance 662A can cause a user interface with additional information regarding the activity competition to be displayed. For example, the additional information can include graph 670, as depicted in
In addition to a notification being displayed when the activity competition begins, notifications can be displayed at predefined times during the activity competition. For example, a predefined time can be an absolute time during the activity competition (e.g., each day at 10 AM) or as a result of an event occurring on a device where the notification is displayed (e.g., a participant completing a goal, performing a workout, or accessing a particular application on the device). Such notifications can include information related to one or more active activity competitions.
Referring to
User interface 644 includes a scrollable list of affordances 666, where each affordance is associated with a different operation. For example, the scrollable list of affordances 666 includes first affordance 666A for a first activity competition, second affordance 666B for a second activity competition, and third affordance 666C for ceasing to display user interface 660. In some examples, the order of affordances for activity competitions can be based upon when the activity competitions are finishing. For example, activity competitions finishing sooner can be included in the scrollable list before activity competitions finishing later.
First affordance 666A includes information related to the first activity competition. As depicted in
As depicted in
The y-axis of graph 670 includes representations of physical activity detected for each participant in the first activity competition for each subset. For example, representation 670B indicates an amount of physical activity detected for Molly (e.g., detected by device 600A and transmitted to device 600B) on Monday and representation 670C indicates an amount of physical activity detected for Aled on Monday. By having representation 670B adjacent to representation 670C, physical activity for each participant for Monday can easily be compared. It should be noted that representations for Molly are provided to the left of representations for Aled in graph 670. The configuration is such because 600B corresponds to Aled's device. When a subset has not occurred yet (e.g., Saturday as depicted in
In some examples, representations for subsets can be normalized across the time period such that the highest representation for a subset of the time period can be displayed a certain size, with other representations normalized based upon the highest representation. For example, if Molly scored the most points for the time period on Friday, a representation for Molly on Friday will be the biggest representation. In such an example, a representation for either Molly or Aled with half the score will be represented as half the size of the representation for Molly on Friday.
It should be noted that representations associated with Molly are illustrated as being visually distinct from representations associated with Aled in
In some examples, representations associated with a participant that is winning an activity competition can be highlighted as compared to a participant that is losing the activity competition. For example, because Molly's cumulative score is higher than Aled's cumulative score, representations associated with Molly visually appear to be highlighted as compared to representations associated with Aled. Visually highlighting representations associated with a participant that is winning can allow a participant to quickly assess how they are doing in the activity competition.
Graph 670 also includes a number of subsets remaining in the first activity competition (e.g., reference 670F). For example, as depicted in
Representation 670 also includes icon 670G. Icon 670G can either indicate that selection of affordance 666A or icon 670G (depending upon configuration of icon 670G) will cause a messaging interface to be displayed (as depicted in
As depicted in
In addition to a notification being displayed when the activity competition begins and at a predefined time, notifications can be displayed in response to activity by another participant. For example, a notification can be displayed for Aled in response to physical activity by Molly, such as Molly reaching a goal for a day (such as closing three activity rings) or performing a workout. Such notifications can include information related to an activity competition with the other participant.
Referring to
Notifications can be sent (e.g., displayed on respective devices of participants) to participants of an activity competition when the activity competition ends. Such notifications can provide results of the activity competition, including an award of a medal for the winner, and include an option to begin a new activity competition, as depicted in
Referring to
User interface 676 includes a scrollable list of affordances 678, where each affordance is associated with a different operation. For example, the scrollable list of affordances 678 includes first affordance 678A for the activity competition between Molly and Aled, second affordance 678B for displaying a messaging user interface (as depicted
Also in response to the activity competition between Molly and Aled ending, user interface 680 is displayed on touch-sensitive display 602B. User interface 680 can include text catered to Aled and the outcome of the activity competition. For example, user interface 676 states that “YOU WON.” and includes information that Aled's best day during the activity competition was Saturday with 794 points.
User interface 680 includes icon 682, representing that Aled won icon 682 in response to winning the activity competition. In response to winning icon 682, icon 682 can be placed in a trophy case for Aled, as further discussed below for
User interface 680 also includes a scrollable list of affordances 684, where each affordance is associated with a different operation. For example, the scrollable list of affordances 684 includes first affordance 684A for the activity competition between Molly and Aled, second affordance 684B for displaying a messaging user interface (as depicted
Having user interface 676 and user interface 680 side-by-side, it should be recognized that representations in a graph (e.g., the graph included in first affordance 678A and the graph included in first affordance 684A) can be swapped depending upon where the graph is being displayed. For example, when the graph is being displayed on Aled's device, representations associated with Aled are generally on the right of representations associated with Molly. Likewise, when the graph is being displayed on Molly's device, representations associated with Molly are generally on the right of representations associated with Alex. It should also be noted that
Referring to
Also referring to
Similar to as described above for
Referring to
User interface 691 indicates that the invitation that Molly sent was accepted and that the activity competition with Aled will start tomorrow. User interface 691 includes icon 692 (which can have the same theme as icon 618, as depicted in
While the figures described above depict an electronic device in the form of a smart watch, it should be recognized that any of the user interfaces discussed above can be displayed on different electronic devices, such as a smart phone. In some examples, display of the user interfaces discussed above on an electronic device with a larger display area can include further detail (as depicted in
Referring to
Also similar to as described above for
The y-axis of the graph includes representations of physical activity detected for each participant in the activity competition for each subset. For example, representation 698H indicates an amount of physical activity received for Molly (e.g., detected by device 600A and transmitted to device 800) on Monday and representation 698I indicates an amount of physical activity detected for Aled on Monday. By having representation 698H adjacent to representation 698I, physical activity for each participant for Monday can easily be compared. When a subset has not occurred yet (e.g., Saturday as depicted in
In some examples, representations for subsets can be normalized across the time period such that the highest representation for a subset of the time period can be displayed a certain size, with other representations normalized based upon the highest representation. For example, if Aled scored the most points for the time period on Monday, a representation for Aled on Monday will be the biggest representation. In such an example, a representation for either Molly or Aled with half the score will be represented as half the size of the representation for Aled on Monday. As depicted in
It should be noted that representations associated with Molly are illustrated as being visually distinct from representations associated with Aled in
In some examples, representations associated with a participant that is winning an activity competition can be highlighted as compared to a participant that is losing the activity competition. For example, because Molly's cumulative score is higher than Aled's cumulative score, representations associated with Molly visually appear to be highlighted as compared to representations associated with Aled. Visually highlighting representations associated with a participant that is winning can allow a participant to quickly assess how they are doing in the activity competition.
Unlike graph 670 depicted in
In some examples, points provided to a participant in an activity competition are based upon a percentage of a goal reached by the participant. For example, a goal can correspond to an amount of walking for each day. Such a goal can be set by the participant either before the activity begins (in some examples) or at any time during the activity competition (in other examples). In some examples, different participants in an activity competition can have different goals. In some examples, points provided to a participant in an activity completion are based upon a two-tier scoring system, where scoring changes when a participant reaches a threshold (e.g., bonus points after the threshold).
As described below, method 700 provides an intuitive way for displaying a user interface on a device corresponding to a first user, where the user interface includes an activity competition graph (associated with the first user and a second user) having (1) a score comparison for each day of an activity competition between the first user and the second user and (2) a total sum over the activity competition. The user interface permits a user viewing the user interface to readily access physical activity data corresponding to the second user. The method reduces the cognitive burden on a user for accessing physical activity data corresponding to another user, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a user to access physical activity data corresponding to another user faster and more efficiently conserves power and increases the time between battery charges.
At block 702, the device (e.g.,
In some examples, the first user activity data is received (e.g., via one or more antennas of the device) by the device (e.g.,
At block 704, the device (e.g.,
In some examples, the second user activity data is received (e.g., via one or more antennas of the device) by the device from a second device (e.g.,
In some examples, in response to receiving the second user activity data from an external device (e.g.,
At 712, the device (e.g.,
In some examples, prior to displaying the user interface (e.g.,
At 714, the user interface (e.g.,
At 716, the user interface (e.g.,
At 718, the user interface (e.g.,
At 720, the user interface (e.g.,
In some examples, the representation of the second user activity data for the first time subset is displayed adjacent to (e.g., next to or in a first region of the user interface) the representation (e.g.,
At 722, the user interface (e.g.,
In some examples, the representation of the second user activity data for the second time subset is displayed adjacent to (e.g., next to or in a second region of the user interface) the representation (e.g.,
At 724, the user interface (e.g.,
In some examples, the first time subset of the first user activity data corresponds to the first time subset of the second user activity data.
In some examples, the user interface (e.g.,
In some examples, the user interface (e.g.,
In some examples, a length of the first time subset is equal to a length of the second time subset (e.g.,
In some examples, displaying the user interface (e.g.,
In some examples, the representations can be normalized.
In some examples, the representations can be based upon percentage completion of one or more goals. Optionally, the one or more goals are user defined.
In some examples, the first user activity data corresponds to a first user and the second user activity data corresponds to a second user. In such examples, prior to displaying the user interface (e.g.,
In some examples, while displaying the user interface, the device receives a second user input corresponding to a request to display additional information corresponding to the first user activity data and/or the second user activity data. In such examples, in response to receiving the second user input, the device displays a second user interface including additional information corresponding to the first user activity data and/or the second user activity data. In such examples, the additional information was not included in the user interface. In some examples, the additional information includes contact information, daily average, actual number of points corresponding to activity data for particular days, or the like. In some examples, the additional information functionality occurs when the affordance is included in an alert rather than a notification, where an alert must be dismissed before looking at other content using the device and a notification is available for a user to view in the background.
In some examples, while displaying the user interface, the device receives a third user input corresponding to a request to display a messaging user interface (e.g.,
In some examples, in response to user input at a location corresponding to a representation, the device displays a messaging user interface (e.g.,
In some examples, the first user activity data includes standing data, moving data, and exercise data.
In some examples, the first user activity data corresponds to a first user and the second user activity data corresponds to a second user. In such examples, the user interface further can include a representation (e.g.,
Note that details of the processes described above with respect to method 700 (e.g.,
Referring to
Referring to
As depicted in
First portion 812 includes a scrollable list of affordances 816, where each affordance is associated with a different activity competition. For example, the scrollable list of affordances 816 includes first affordance 816A for a first activity competition (between Molly and Aled) and second affordance 816B for a second activity competition (between John and Aled). In some examples, the order of affordances for activity competitions can be based upon when the activity competitions are finishing. For example, activity competitions finishing sooner can be included in the scrollable list of affordances 816 before activity competitions finishing later.
First affordance 816A includes information related to the first activity competition, such as a cumulative score for Molly (i.e., 2303) and Aled (i.e., 2136, labeled “ME”), a number of times Molly has won a past activity competition between Molly and Aled (i.e., 23 times), a number of times Aled has won a past activity competition between Molly and Aled (i.e., 7 times), and an amount of time left in the first activity competition (i.e., 2 days left). Second affordance 616B includes information related to the second activity competition, which can be similar to the information related to the first activity competition described above. It should be noted that, in some examples, affordances in the scrollable list of affordances 816 can include more or less information than depicted in
Second portion 814B includes a scrollable list of affordances 818, where each affordance is associated with a different friend of a user (e.g., Aled) logged into device 800. For example, the scrollable list of affordances 818 includes first affordance 818A for a first friend (i.e., Jane), second affordance 818B for a second friend (i.e., Molly), and third affordance 818C for a third friend (i.e., John). It should be noted that, in some examples, friends included in second portion 814B can also be included in an activity competition in first portion 814A. For example, Molly is a participant of the first activity competition (e.g., first affordance 816A) and included in the scrollable list of affordances 818 (e.g., second affordance 818B). In other examples, friends included in first portion 814A are not included in second portion 814B.
Each affordance in the scrollable list of affordances 818 includes information related to the corresponding friend. For example, first affordance 818A corresponds to Jane and includes an identification of Jane (e.g., “Jane”), a percent of goals for Jane that Jane has completed (e.g., “95%), an absolute amount of a goal that Joan has completed with the absolute amount of the goal (e.g., “400/450”), and icon 818AA visually depicting an amount of multiple goals that Joan has completed.
User interface 812 further includes sharing affordance 820. Selection of sharing affordance 820 causes device 800 to display a user interface (e.g., user interface 834 as depicted in
Referring to
User interface 822 also includes back affordance 826 to cause a previous user interface (e.g., user interface 812 as depicted in
Referring to
User interface 828 also includes invite affordance 831 to initiate a process for beginning an activity competition between Jane and Aled. For explanatory purposes, selection of invite affordance 831 can cause user interface 616 (as depicted in
Referring to
Referring to
First portion 836 includes information related to invitations for activity competitions received by device 800. For example, first portion 836 includes invitation 836A. Invitation 836A indicates that Tom has sent an invitation to begin an activity competition to Aled (e.g., to one or more devices (e.g., device 800) associated with Aled). Invitation 836A includes an accept affordance and an ignore affordance in order to respond to the invitation from Tom. Selection of the accept affordance initiates a process to begin an activity competition between Tom and Aled. Selection of the ignore affordance removes invitation 836A from first portion 836.
Second portion 838 includes information related to invitations for activity competitions sent by device 800. For example, second portion 838 includes invitation 838A. Invitation 838A indicates that Aled has sent an invitation to begin an activity competition to Jane. Invitation 838A includes a representation of the amount of time that remains for Jane to accept the invitation.
Similar to user interface 812, user interface 830 includes first portion 842A and second portion 842B. As depicted in
Referring to
First affordance 844A includes information related to the first activity competition, such as a cumulative score for Molly (i.e., 2303) and Aled (i.e., 2136), a number of times Molly has won a past activity competition between Molly and Aled (i.e., 23 times), a number of times Aled has won a past activity competition between Molly and Aled (i.e., 7 times), and an amount of time left in the first activity competition (i.e., 2 days left). Second affordance 616B includes information related to the second activity competition, which can be similar to the information related to the first activity competition described above. It should be noted that, in some examples, affordances in the scrollable list of affordances 816 can include more or less information than depicted in
It should also be noted that while user interface 840 is depicted as having the same information in first portion 842A as user interface 812 in first portion 814A, an organization of the information in user interface 840 is different than an organization of the information in user interface 812. The difference in organization can be because of touch-sensitive display 602B having a smaller display area than touch-sensitive display 802.
Second portion 842B includes a scrollable list of affordances 846, where each affordance is associated with a different friend of a user (e.g., Aled) logged into device 800. For example, the scrollable list of affordances 846 includes first affordance 846A for a first friend (i.e., Jane), second affordance 846B for a second friend (i.e., Molly), third affordance 846C for a third friend (i.e., John), and fourth affordance 846D for a fourth friend (i.e., Tom). It should be noted that, in some examples, friends included in second portion 842B can also be included in an activity competition in first portion 842A. For example, Molly is a participant of the first activity competition (e.g., first affordance 842A) and included in the scrollable list of affordances 846 (e.g., second affordance 846B). In other examples, friends included in first portion 842A are not included in second portion 842B.
Each affordance in the scrollable list of affordances 846 includes information related to the corresponding friend. For example, first affordance 846A corresponds to Jane and includes an identification of Jane (e.g., “Jane”), a percent of goals for Jane that Jane has completed (e.g., “95%), an absolute amount of a goal that Joan has completed with the absolute amount of the goal (e.g., “400/450”), and an icon visually depicting an amount of multiple goals that Joan has completed.
Referring to
Selection of first affordance 850A can accept the invitation for the activity competition sent by Tom. Acceptance of the invitation can cause the activity competition to begin at a predefined time after the selection (e.g., midnight of the current day), as further described below. Selection of second affordance 850B can cause device 600B to reject the invitation (e.g., cause the activity competition to not begin) and cease to display user interface 848. Selection of second affordance 850B can further cause invitation icon 842 to be removed from fourth affordance 846D.
Referring to
Referring to
Each portion can include one or more awards associated with a corresponding type of award. For example, recents 860 can include awards that have been awarded within a particular amount of time from a current time. In some examples, awards in recents 860 can be larger than awards in other portions. Competitions 860B can include awards that have been awarded for activity competitions. Monthly challenges 860C can include awards that have been predefined as a monthly challenge. Achievements 860D can include awards that have been predefined as an achievement. Workouts 860E can include awards that have been awarded using a workout application (as described herein).
In some examples, some awards in a portion might not be visible. In such examples, the awards can be navigated by side scrolling through them.
Display of awards in user interface 858 can differ based upon the particular award. For example, a representation for an award that is received only once on a particular day can include an icon (e.g., icon 862A), an identification of the award (e.g., identification 862B), and a date that the award was received (e.g., date 862C). In some examples, a representation for an award that is received only once on a particular day can include an icon (e.g., icon 862A), an identification of the award (e.g., identification 862B), and further information related to achieving the award, such as a number of calories burned which satisfied at least a minimum amount for the award (e.g., calories 872C). In such examples, the representation might not include a date that the award was received because the identification indicates the date.
For another example, a representation for an award that is received multiple times can include an icon (e.g., icon 864A or 866A), an identification of the award (e.g., identification 864B or 866B), and a number of times that the award has been received (e.g., number 864D or 866C). In some examples, the representation for an award that is received multiple times can also include a date that the award has last been received (e.g., date 864C). In such examples, the representation can also include the date when the award is predefined as hard to receive or the award has been received below a particular number of times.
It should be noted that each icon for each award in competitions 860B (e.g., icons 866A, 868A, and 870A) is different. This can be due to each activity competition being assigned a different representation, as discussed herein.
As described below, method 900 provides an intuitive way for displaying a user interface on a device corresponding to a first user, where the user interface includes affordances for multiple activity competitions, where each activity competition (1) is between the first user and another user and (2) is represented by current scores for the activity competition and a number of days remaining in the activity competition. The user interface permits a user viewing the user interface to readily access physical activity data corresponding to multiple users. The method reduces the cognitive burden on a user for accessing physical activity data corresponding to multiple user, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a user to access physical activity data corresponding to multiple users faster and more efficiently conserves power and increases the time between battery charges.
At 902, the device (e.g.,
In some examples, a length (e.g.,
At 904, the device (e.g.,
At 906, the device (e.g.,
In some examples, the activity competition between the first user and the second user began at a first time (e.g.,
At 908, the device (e.g.,
At 910, the user interface (e.g.,
At 912, the user interface (e.g.,
At 914, the user interface (e.g.,
At 916, the user interface (e.g.,
In some examples, the user interface (e.g.,
In some examples, the third affordance includes a notification (e.g.,
In some examples, the notification is removed from the third affordance after an amount of time (e.g., 48 hours) has passed since the fourth user sent a corresponding request to initiate the activity competition between the first user and the fourth user.
In some examples, while displaying the user interface (e.g.,
In some examples, the representation of the first user activity data and the second user activity data includes: an identification of the first user (e.g.,
In some examples, the third affordance (e.g.,
In some examples, selection of the fourth affordance (e.g.,
In some examples, the second affordance includes a second icon indicating previous activity competitions between the first user and the third user, where the first icon has a first visual theme (e.g., a shape, a background color or pattern, and where the second icon with a second visual theme different from the first visual theme. In some examples, two graphical indications may share a common visual theme, while differing in non-thematic visual elements (e.g., such as a number or initials that are not part of the visual theme. In some examples, unique visual themes are assigned to each other user (e.g., a second user, a third user) that has been, or is currently, in a competition with the user of the electronic device (e.g., the first user.
In some examples, icons for different activity competitions between the same two participants are the same.
In some examples, while displaying the user interface, receiving a third user input (e.g.,
In some examples, the third user interface, for an icon (e.g.,
In some examples, the device receives a fourth user input (e.g.,
In some examples, the representation of the first user activity data and the second user activity data during the first elapsed sub-period for the activity competition between the first user and the second user is based upon a two-tier scoring system, where scoring changes when a user reaches a threshold (e.g., bonus points).
In some examples, while displaying the user interface, the device receives, using a rotatable input mechanism (e.g., an input mechanism that can rotate relative to a housing of the device) (e.g.,
Note that details of the processes described above with respect to method 900 (e.g.,
Referring to
User interface 1004 includes a scrollable list of affordances 1006, where each affordance is associated with a different operation. For example, the scrollable list of affordances 1006 includes start affordance 1006A, change affordance 1006B, and dismiss affordance 1006C. Start affordance 1006A causes a physical activity tracking function configured for outdoor runs to be launched. Change affordance 1006B allows a user to pick a different type of workout such that a physical tracking function configured for the different type of workout is launched. Dismiss affordance 1006C causes user interface 1004 to cease to display.
User interface 1004 further includes physical activity icon 1008 corresponding to the outdoor run. Physical activity icon 1008 is an icon of a runner. In various examples, physical activity icon 1008 is displayed in an animated state, as further illustrated in
In some examples, content included in user interface 1004 might not fit within touch-sensitive display 602A; in which case content not displayed can be displayed in response to a scrolling input (e.g., rotation of rotatable input mechanism 604A).
In some examples, an alert (e.g., user interface 1004) is reissued (e.g., re-displayed or a new alert corresponding to the alert is displayed) after an amount of time (e.g., a predetermined amount of time) has passed without causing the alert to be dismissed (e.g., selecting an affordance in the scrollable list of affordances 1006). For example, if a user does not select an affordance in the scrollable list of affordances 1006 within 3 minutes, a new user interface that is the same or similar to user interface 1004 is displayed on touch-sensitive display 602A of device 600A. In some examples, if the user does select an affordance (e.g., dismiss affordance 1006A) within three minutes of user interface 1004 being displayed, user interface 1004 is not reissued after 3 minutes. While 3 minutes is used as an example, it should be recognized that a different amount of time may be used.
In some examples, the alert is only reissued when the alert has been interrupted (e.g., user interface 1004 is no longer being displayed due to another alert). In some examples, if the alert has not been interrupted, the alert remains (e.g., continues to be displayed and/or is displayed whenever touch-sensitive display 602A transitions from an inactive state to an active state) for a particular amount of time. In some examples, the particular amount of time is based on a type of workout corresponding to the alert. For example, if the alert corresponds to swimming, the alert can remain for 60 minutes; and if the alert corresponds to running or some other type of workout other than swimming, the alert can remain for 30 minutes. In some examples, a notification corresponding to user interface 1004 can be sent to a notification center such that a user is able to view the notification after user interface 1004 ceases to display.
In some examples, prior to displaying user interface 1004, user interface 1064 is displayed on touch-sensitive display 602A of device 600A, as depicted in
As depicted in
In some examples, user interface 1064 is displayed in response to detecting a user input within a first time interval following a perceptual output (e.g., thereby satisfying short-look criteria). Information in user interface 1064 may be referred to as first portion of information. In such examples, after raising a user's wrist to view user interface 1064, the user may then wish to view more information associated with user interface 1064. If device 600A determines that the user continues to maintain device 600A in a viewing position for a predetermined time interval (e.g., thereby satisfying a long-look criteria) after displaying user interface 1064, device 600A displays user interface 1004, which may be referred to as a second portion of the information. That is, in some examples, device 600A can automatically transition from displaying user interface 1064 to displaying user interface 1004 when the user holds device 600A in a viewing position and waits.
In response to selection of start affordance 1006A, user interface 1026 (which is depicted in
To display the data detected by device 600A, user interface 1026 includes representations 1028. In
User interface 1026 also includes a current time, a physical activity icon (as discussed above), or other information determinable by device 600A. The physical activity icon depicted in user interface 1026 can be animated. While
At some point after a workout has started (e.g., after selection of start affordance 1006A), it can be determined that the user is likely (e.g., above a threshold criteria) no longer running outside. The determination can be based upon similar data as described above for beginning the outdoor run, such as data detected by one or more sensors associated with device 600A. In response to the determination that the user is likely no longer running outside, user interface 1038 (as depicted in
User interface 1038 includes a scrollable list of affordances 1040, which are associated with different operations. For example, the scrollable list of affordances 1040 includes end affordance 1040A, pause affordance 1040B, change affordance 1040C, and dismiss affordance 1006D. End affordance 1040A causes the physical activity tracking function corresponding to the outdoor run to stop and data generated by the physical tracking function to be stored as a previous workout. Pause affordance 1040B causes the physical activity tracking function corresponding to the outdoor run to pause. Change affordance 1040C allows a user to choose a different type of workout so that a different physical activity tracking function corresponding to the different type of workout can be launched. Dismiss affordance 1006D causes user interface 1038 to cease to display and the physical activity tracking function for the outdoor run to continue to execute.
User interface 1038 further includes physical activity icon 1042 corresponding to the outdoor run. Physical activity icon 1042 is an icon of a runner. In various examples, physical activity icon 1042 is displayed in a static state.
In some examples, content included in user interface 1038 might not fit within touch-sensitive display 602A; in which case content not displayed can be displayed in response to a scrolling input (e.g., rotation of rotatable input mechanism 604A).
Referring to
Referring to
User interface 1044 also includes an identification of the outdoor run (e.g., representation 1048), a physical activity icon (e.g., physical activity icon 1050), or other information known by device 600A. While
User interface 1030 allows a user to select a different type of workout for a current workout. For example, when it is determined that the user is running outside, the user can change the outdoor run to a second type of workout, indicating that the determination of the outdoor run was incorrect. When a different type of workout is selected, a physical activity tracking function corresponding to the different type of workout launches automatically.
User interface 1030 includes a scrollable list of affordances 1032, which are associated with respective physical activity tracking functions for a physical activity. For example, the scrollable list of affordances 1032 includes affordance 1032A (which corresponds to a physical activity tracking function for climbing stairs (referred to as stair stepping)), affordance 1032B (which corresponds to a physical activity tracking function for an outdoor run), and affordance 1032C (which corresponds to a physical activity tracking function for a walk). It is noted that the scrollable list of affordances 1032 can include additional affordances corresponding to other physical activity tracking functions that are not currently displayed but can be displayed in response to a scrolling input (e.g., rotation of rotatable input mechanism 604A).
In some examples, each of one or more affordances in the scrollable list of affordances 1032 includes representations 1034 corresponding to a physical activity associated with the affordance. Representations 1034 includes a physical activity icon corresponding to the physical activity associated with the affordance. For example, affordance 1032A includes physical activity icon 1034A (e.g., icon of a person climbing stairs). Similarly, affordance 1032C includes physical activity icon 1034D (e.g., icon of a person walking). In various examples, physical activity icons are displayed in a first state (e.g., static state).
Representations 1034 further includes a workout identifier. For example, affordance 1032A includes workout identifier 1034B that indicates that affordance 1032A is associated with a stair stepper workout. Similarly, affordance 1032B includes a workout identifier that indicates that affordance 1032B is associated with an outdoor run workout.
In some examples, one or more affordances in the scrollable list of affordances 1032 includes workout goal information. For example, affordance 1032A includes workout goal information 1034C that indicates that the stair stepper workout associated with affordance 1032A has a predetermined goal of twenty minutes. That is, when affordance 1032A is selected, the associated physical activity tracking function will automatically track information for the stair stepper workout with a preset goal of twenty minutes. Affordance 1032B includes a goal workout affordance that indicates that the outdoor run associated with affordance 1032B is an “open goal.” An open goal indication indicates to the user that the associated workout does not currently have any preset goals. Accordingly, when affordance 1032B is selected, various metrics will be tracked by the associated physical activity tracking function, wherein the metrics do not include any preset goal values.
By depicting user interface 1004 over time, it is illustrated how physical activity icon 1008 can be animated. For example, physical activity icon 1008A depicts physical activity icon 1008 in a first state, physical activity icon 1008B depicts physical activity icon 1008 in a second state subsequent to the first state, and physical activity icon 1008C depicts physical activity icon 1008 in a third state subsequent to the second state.
The animation can give the impression that a person is running. Animating physical activity icon 1008 can provide feedback to a user that device 600A has determined (e.g., detected) that a workout has begun.
Referring to
User interface 1054 further includes physical activity icon 1056 corresponding to a physical activity associated with start affordance 1054A. Physical activity icon 1056 is an icon of a person walking. In various examples, physical activity icon 1056 is displayed in an animated state.
Referring to
User interface 1058 further includes physical activity icon 1062 corresponding to a physical activity associated with start affordance 1060A. Physical activity icon 1062 is an icon of a person rowing. In various examples, physical activity icon 1062 is displayed in an animated state.
In some examples, instead of displaying user interface 1004, user interface 1068 is displayed, as depicted in
In some examples, start indoor run affordance 1070B is related to a type of workout that is an alternative to a type of workout corresponding to start outdoor run affordance 1070A (in some examples, types of workouts are related when tracking data used for one can be used for the other). In such examples, start outdoor run affordance 1070A is visually highlighted (e.g., a different color and/or a different size) as compared to start indoor run affordance 1070B (and in comparison to the other affordances 1070C and 1070D). In some examples, start outdoor run affordance 1070A is visually highlighted because a determination, based on sensor data, has been made that it is more likely that a user is running outdoor than indoors. In some examples, start indoor run affordance 1070B is not visually highlighted as compared to change affordance 1070C and dismiss affordance 1070D. In other words, start indoor run affordance 1070B, change affordance 1070C, and dismiss affordance 1070D can appear similar while start outdoor run affordance 1070A is visually distinct from all three. Examples of types of workouts that might commonly be paired together as a main workout and an alternative workout include outdoor/indoor run, outdoor/indoor walk, and pool swim/open water swim. While only a single alternative is illustrated in
In some examples, after an alert is issued (e.g., user interface 1004), a user interface (e.g., user interface 1076) for selecting to start a workout from a list of workouts includes one or more representations corresponding to the alert, as depicted in
Referring to
As depicted in
It should be noted that user interface 1076 includes a clock indicating that the time is “10:09” and affordance 1078A indicates a workout starting at 10 AM. This illustrates that selection of affordance 1078A causes data tracked since 10 AM to be recorded for a current outdoor running workout even though a user did not indicate to begin an outdoor running workout at 10 AM.
In some examples, the scrollable list of affordances 1078 can include additional affordances corresponding to other physical activity tracking functions that are not currently displayed but can be displayed in response to a scrolling input (e.g., rotation of rotatable input mechanism 604A).
As depicted in
As described below, method 1100 provides an intuitive way for displaying an alert in response to automatically determining a boundary of physical activity (e.g., a workout). The method reduces the cognitive burden on a user for starting and stopping a physical activity tracking function, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a user to track activity data faster and more efficiently conserves power and increases the time between battery charges.
At 1102, the device (e.g., 600A) detects, via the one or more sensors, activity data (e.g., heart rate data, GPS data, movement data, or the like) (e.g.,
In some examples, the activity data is detected before a physical activity tracking function is active (e.g., a tracking function corresponding to 1026). In such examples the activity data is used to determine whether to initiate a physical activity tracking function (e.g., the boundary condition is a start of a workout).
At 1102, in response to detecting the activity data, in accordance with a determination that the activity data satisfies activity boundary alert criteria (e.g., criteria for categorizing activity data as corresponding to a boundary (e.g., a start, an end, a transition from one type of activity to another) of user activity (e.g., a user workout)), the device (e.g., 600A) displays an activity boundary alert (e.g., a user interface including a confirmation affordance and an indication of the type of activity boundary detected) (e.g., 1004 or 1038). Displaying an activity boundary alert provides feedback as to when a device detects an activity boundary. Providing improved feedback and performing an operation when a set of conditions has been met without requiring further user input enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
In some examples, the activity boundary alert (e.g., 1004) includes a first affordance (e.g., 1006A). In such examples, the device (e.g., 600A) receives a first user input (e.g., 1001) corresponding to selection of the first affordance. In response to receiving the first user input, the device initiates a physical activity tracking function (e.g., user interface 1026 can be displayed with information from physical activity tracking function) corresponding to a type of physical activity (e.g., running, HIIT, yoga, or the like) corresponding to the activity boundary alert (e.g., the physical tracking functions corresponds to the first affordance). In some examples, the activity boundary alert includes a third affordance (e.g., 1006C). In such examples, selection of the third affordance causes the device to forgo initiating the physical activity tracking function corresponding to a type of physical activity corresponding to the activity boundary alert. In such examples, the device continues to determine when a workout begins.
In some examples, the physical activity tracking function corresponding to the activity boundary alert (e.g., 1004) tracks activity data detected prior to displaying the activity boundary alert.
In some examples, the activity boundary alert (e.g., 1004) corresponds to a first physical activity tracking function (e.g., an activity tracking function corresponding to a predicted type of activity (e.g., running, swimming, rowing)). In such examples, the activity boundary alert includes a second affordance (e.g., 1006). In such examples, the device receives a second user input (e.g., 1003) corresponding to selection of the second affordance in the activity boundary alert. In response to receiving the second user input, the device displays a first user interface (e.g., 1030) including: a third affordance (e.g., 1032A) corresponding to a second physical activity tracking function different than the first physical activity tracking function; and a fourth affordance (e.g., 1032C) corresponding to a third physical activity tracking function different than the first physical activity tracking function. While displaying the first user interface the device receives a third user input. In accordance with the third user input corresponding to selection of the third affordance in the first user interface, the device configures the electronic device to track activity data detected after selection of the third affordance using the second physical activity tracking function. In accordance with the third user input corresponding to selection of the fourth affordance in the second user interface, the device configures the electronic device to track activity data detected after selection of the fourth affordance using the third physical activity tracking function. In some examples, the activity boundary alert includes an animated affordance (e.g.,
In some examples, the activity data was detected via a first sensor of the one or more sensors. In such examples, initiating the physical activity tracking function corresponding to the type of physical activity corresponding to the activity boundary alert (e.g., the physical tracking functions corresponds to the first affordance) includes detecting second activity data via a second sensor, different than the first sensor (e.g., the first sensor is an accelerometer and the second sensor is a GPS sensor), of the one or more sensors. In some examples, the second sensor is activated, from an inactive state.
In some examples, the activity data is detected while an existing physical activity tracking function is active (e.g., a tracking function corresponding to 1026).
In some examples, the activity data is detected while an existing physical activity tracking function is active. For example, the device is already tracking a workout. In such examples, the activity boundary alert (e.g., 1038) includes a fifth affordance (e.g., 1040A). In such examples, the device receives a first fourth input (e.g., 1005) corresponding to selection of the fifth affordance. In response to receiving the fourth user input, the device ends the current physical activity tracking function. In further response to receiving the fourth user input, the device stores activity data (e.g., including the activity data) detected prior to receiving the fourth user input as a previous workout.
In some examples, the activity boundary alert (e.g., 1038) includes a sixth affordance (e.g., 1040B). In such examples, the device receives a fifth user input corresponding to selection of the sixth affordance. In response to receiving the fifth user input, the device pauses execution of a physical activity tracking function. In some examples, the activity boundary alert includes a dismiss affordance (e.g., 1040D) to not stop recording a workout.
In some examples, the activity boundary alert (e.g., 1038) corresponds to a first physical activity tracking function. In such examples, the activity boundary alert includes a seventh affordance (e.g., 1040C). In such examples, the device receives a sixth user input (e.g., similar to 1003) corresponding to selection of the seventh affordance. In response to receiving the sixth third input, the device initiates a process for ceasing execution of a first physical activity tracking function. In further response to receiving the sixth third input, the device displays a second user interface (e.g., 1030) including: an eighth affordance (e.g., 1032A) corresponding to a second physical activity tracking function different than the first physical activity tracking function, and a ninth affordance (e.g., 1032C) corresponding to a third physical activity tracking function different than the first physical activity tracking function. In such examples, the device receives a seventh user input. In accordance with the seventh user input corresponding to selection of the eighth affordance in the second user interface, the device initiates the second physical activity tracking function. In accordance with the seventh user input corresponding to selection of the ninth affordance in the second user interface, the device initiates the third physical activity tracking function.
In some examples, the activity boundary alert includes a static affordance (e.g.,
In some examples, the determination that the activity data satisfies activity boundary alert criteria can update over time based upon user interactions.
In some examples, the activity boundary alert (e.g., 1068) includes a tenth affordance (e.g., 1070B) (in some examples, the tenth affordance is an affordance for an alternative type of workout as compared to the first affordance (e.g., 1070A)), and wherein the physical activity tracking function corresponding to the activity boundary alert is a first physical activity tracking function. In such examples, the electronic device receives an eighth user input corresponding to selection of the tenth affordance and, in response to receiving the eighth user input, initiates a second physical activity tracking function corresponding to the activity boundary alert, wherein the second physical activity tracking function is different from the first physical activity tracking function (in some examples, each of the first physical activity tracking function and the second physical activity tracking function uses the activity data in a first manner (e.g., tracking number of miles) while a third physical activity tracking function that does not correspond to the activity boundary alert criteria uses the activity data in a second manner different from the first manner (e.g., tracking number of laps)).
In some examples, the first affordance (e.g., 1070A) and the tenth affordance (e.g., 1070B) are ordered based upon which respective workout is determined to be more likely the type of workout being performed. For example, if a determination is made that it is more likely that a user is performing an outdoor run than an indoor run, an affordance associated with an outdoor run precedes an affordance associated with an indoor run, as illustrated in
In some examples, the first affordance is highlighted as compared to the tenth affordance, to highlight that a workout corresponding to the first affordance has been determined to be more likely being performed than a workout corresponding to the tenth affordance.
In some examples, wherein the activity boundary alert is a first activity boundary alert (e.g., 1064) including (in some examples, the activity boundary alert is displayed in response to a short look) first content, after displaying the first activity boundary alert, the electronic device displays a second activity boundary alert (e.g., 1004) (in some examples, the second activity boundary alert is displayed in response to a long look) including second content, wherein the second content is different from the first content (e.g., the second content includes the first content and additional content) (in some examples, the second activity boundary alert is displayed in accordance with a determination that look criteria have been satisfied).
At 1106, in further response to detecting the activity data and in accordance with a determination that the activity data does not satisfy the activity boundary alert criteria, the device forgoes display of the activity boundary alert (e.g., forgoes displaying 1004).
In some examples, further in response to detecting the activity data and in accordance with a determination that the activity data satisfies second activity boundary alert criteria, the device displays a second activity boundary alert (e.g., alert 1058), where the activity boundary alert criteria and the activity boundary alert (e.g., alert 1004) relate to a first type of physical activity (e.g., running), and where the second activity boundary alert criteria and the second activity boundary alert relate to a second type of physical activity (e.g., rowing) different than the first type. In accordance with a determination that the activity data does not satisfy the second activity boundary alert criteria, the device forgoes display of the second activity boundary alert (e.g., forgoes displaying 1004).
In some examples, where the activity boundary alert is a first activity boundary alert, after a predetermined time (e.g., 3 minutes) has lapsed without initiating a physical activity tracking function corresponding to the first activity boundary alert, the electronic device displays a second activity boundary alert (e.g., 1004), wherein a physical activity tracking function corresponding to the second activity boundary alert tracks activity data detected prior to displaying the first activity boundary alert.
In some examples, after displaying the activity boundary alert and before a physical activity tracking function is active, the electronic device displays a third user interface (e.g., 1076) (in some examples, the third user interface is the first user interface) including a scrollable list of affordances (e.g., 1078) associated with physical activities. In some examples, the electronic device receives a ninth user input. In some examples, in accordance with a determination that the ninth user input is detected at an eleventh affordance (e.g., 1078A) in the scrollable list of affordances, the electronic device launches a physical activity tracking function corresponding to the activity boundary alert (in some examples, the physical activity tracking function associated corresponding to the activity boundary alert tracks activity data detected prior to displaying the third user interface) (in some examples, the physical activity tracking function corresponding to the activity boundary alert tracks activity data detected prior to displaying the activity boundary alert). In some examples, in accordance with a determination that the ninth user input is detected at a twelfth affordance (e.g., 1078C) in the scrollable list of affordances, the electronic device launches a physical activity tracking function (1) not corresponding to the activity boundary alert and (2) different from the physical activity tracking function corresponding to the activity boundary alert. In some examples, wherein the physical activity tracking function corresponding to the activity boundary alert is a first the physical activity tracking function, in accordance with a determination that the ninth user input is detected at a thirteenth affordance (e.g., 1078B) in the scrollable list of affordances, the electronic device launches a second physical activity tracking function corresponding to the activity boundary alert, wherein the second physical activity tracking function is different from the first physical activity tracking function, and wherein the second physical activity tracking function corresponding to the activity boundary alert tracks activity data detected after receiving the ninth user input (in some examples, the second physical activity tracking function tracks activity data detected after launching the second physical activity tracking function) (in some examples, one of the physical activity tracking functions corresponding to with the eleventh or twelfth affordance is the same physical activity tracking function corresponding to the thirteenth affordance).
In some examples, the eleventh affordance and the thirteenth affordance are visually highlighted (e.g., different color and/or bigger) as compared to the twelfth affordance, to indicate that the eleventh affordance and the thirteenth affordance are a different type of affordance from the twelfth affordance.
Note that details of the processes described above with respect to method 1100 (e.g.,
Referring to
In some examples, one or more affordances in the scrollable list of affordances 1206 includes an options affordance, as further discussed below. For example, affordance 1206A includes options affordance 1208.
Referring to
Referring to
In some examples, in accordance with a determination that user input 1203 is detected at pace-alert affordance 1214, a user interface (e.g., user interface 1216 as depicted in
Referring to
User interface 1216 further includes a scrollable list of affordances 1218, which are associated with different operations. For example, the scrollable list of affordances 1218 includes set-pace affordance 1218A (which corresponds to causing a display for setting a pace to be displayed), average affordance 1218B (which corresponds to causing a pace to be calculated using data from an entire workout), rolling affordance 1218C (which corresponds to causing a pace to be calculated using a subset of data from a workout, where the subset is less than the entire workout), off affordance 1218D (which corresponds to turning off a pace alert), or any combination thereof. It is noted that, in some examples, the scrollable list of affordances 1218 might not fit within touch-sensitive display 602A; in which case one or more affordances not displayed can be displayed in response to a scrolling input (e.g., rotation of rotatable input mechanism 604A).
As used herein, pace can refer to speed (e.g., an amount of distance that a device travels in an amount of time or an amount of time that it takes for a device to travel an amount of distance). In regards to pace, the different calculations described herein (e.g., average and rolling) can refer to changing an amount of a dataset for a current workout that is used when performing a pace calculation. For example, for average, the pace calculation can be based upon data detected during the entire current workout. For rolling, the pace calculation can be based upon data detected during an amount prior to a current location (e.g., data detected for the last mile or data detected for the last 5 minutes).
Referring to
User interface 1222 further includes multiple affordances for setting a time (e.g., minutes-setting affordance 1224A and seconds-setting affordance 1224B). Minutes-setting affordance 1224A is used to set a number of minutes for a pace. Seconds-setting affordance 1224B is used to set a number of seconds for the pace.
As depicted in
User interface 1222 further includes a scrollable list of affordances 1226, which are each associated with different operations. For example, the scrollable list of affordances 1226 includes set-pace affordance 1226A (which corresponds to setting a pace identified using the multiple affordances for setting a time) and cancel affordance 1226B (which corresponds to displaying a user interface for providing options to configure a pace alert, such as user interface 1216 in
Referring to
As discussed above, the scrollable list of affordances 1218 includes average affordance 1218B. Referring to
Referring to
Referring to
Referring to
In response to selection of affordance 1206A, user interface 1250 (which is depicted in
While a user is performing the outdoor run, a pace of the user might goes above a pace set for the outdoor run. When the pace of the user is above the pace set for the outdoor run, an alert that the pace of the user is above the pace set for the outdoor run can be displayed, as depicted in
Referring to
In response to the user running quicker and bringing their pace to “8′29″”, user interface 1244 can be updated to reflect that the user is on target pace. Referring to
In response to the user running even quicker and bringing their pace to “7′57″”, user interface 1244 can be updated to reflect that the user is below target pace. For example, status 1246A can be updated to indicate that the user in “on target pace” and current pace 1246B can be updated to indicate that the user's current pace is “7′57″” when calculated over the entire current workout. It should be recognized that what values constitute below, on target, and above a target pace can include one or more values around a target pace. For example, a number of seconds above and below target pace can still be considered on target.
In some examples, interface 1244 (as depicted in each of
Referring back to after set-pace affordance 1226A is selected (as depicted in
Referring to
In one illustrative example, the user can run 2 miles in 10 minutes. The average for the run would be 5 minutes per mile. If the rolling average is calculated for the last 5 minutes, the rolling average for the run would be 5 divided by however much distance was covered in the last 5 minutes. For example, if the user ran 1.2 miles in the last 5 minutes, the rolling average for the user is 5 divided by 1.2 (i.e., 4 minutes and 10 seconds per mile).
Referring to
Referring to
Referring to
As depicted in
User interface 1236 further includes a scrollable list of affordances 1240, which are associated with different operations. For example, the scrollable list of affordances 1240 includes set-pace affordance 1240A (which corresponds to setting a pace identified using the multiple affordances for setting the rolling pace) and cancel affordance 1240B (which corresponds to displaying a user interface for providing options to configure a pace alert, such as user interface 1230 in
Referring to
Referring to
Referring to
Referring to
It should also be recognized that icon 1262A can be different depending upon a number of representations 1262. When there are less representations 1262 (e.g., user interface 1260C includes less representations 1262 than user interface 1260B), icon 1262A can be bigger, more detailed, and/or include additional information. For example, icon 1262AD in user interface 1260D includes a running man and portion 1264. In some examples, portion 1264 can indicate a percent of a daily goal completed using device 600A. In other examples, portion 1264 can indicate a percent of a current workout completed using device 600A.
As described below, method 1300 provides an intuitive way for displaying a user interface to configure a dataset that is used to calculate a pace. The method reduces the cognitive burden on a user for configuring the dataset to calculate the pace, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a user to configure a pace faster and more efficiently conserves power and increases the time between battery charges.
At 1302, the device (e.g., 600A) displays a physical activity rate (e.g., a pace (e.g., a mile pace while running)) user interface (e.g., 1216) including a first setting affordance (e.g., 1218B) and a second setting affordance (e.g., 1218C). In some examples, the user interface father includes a third affordance (e.g., 1218A) for setting a pace.
At 1304, while displaying the physical activity rate user interface, the device (e.g., 600A) receives a first user input (e.g., 1213). In some examples, the user input is a finger gesture, such as a tap, on either the first or second affordance.
At 1306, in response to receiving the first user input, in accordance with the first user input corresponding to selection of the first setting affordance (e.g., 1213), the device configures a physical activity rate calculation to use a first portion of a dataset (e.g., average).
In some examples, the first portion of the dataset includes all of the dataset (e.g., for an average pace).
At 1308, in further response to receiving the first user input, in accordance with the first user input corresponding to selection of the second setting affordance (e.g., 1221), the device configures a physical activity rate calculation to use a second portion of the dataset (e.g., rolling) different than the first portion. In some examples, the first portion of the dataset and the second portion of the dataset overlap. Displaying an option to choose between different types of physical activity rate calculations provides additionally configurability regarding how the device operates. Providing additional control options without cluttering the UI 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 examples, configuring the physical activity calculation to use the second portion of the dataset includes displaying a second user interface (e.g., 1230) with a first affordance (e.g., 1232A) and a second affordance (e.g., 1232B). In such examples while displaying the second user interface, the device receives a second user input (e.g., 1223). In response to receiving the second user input, in accordance with a determination that the second user input is detected at the first affordance, the device causes the second portion to be determined based upon an amount of time. In further response to receiving the second user input, in accordance with a determination that the second user input is detected at the second affordance (e.g., 1223), the device causes the second portion to be determined based upon an amount of distance.
In some examples, after a physical activity rate is set for a type of physical activity and while a physical activity tracking function corresponding to the type of physical activity is executing, the device detects a current physical activity rate (e.g., 1262D). In response to detecting the current physical activity rate, in accordance with a determination that the current physical activity rate does not satisfy a first set of one or more alert criteria, the device forgoes output of a first alert. In some examples, the first set of one or more alert criteria includes whether the current physical activity rate is off pace. In some examples, the first alert is a haptic, audio, or visual alert. In further response to detecting the current physical activity rate, in accordance with a determination that the current physical activity rate satisfies the first set of one or more alert criteria, the device outputs the first alert.
In some examples, after outputting the first alert (e.g., a haptic our audio alert), the device receives a third user input. In some examples, the third user input is finger tap or a movement of the device (e.g., detected using one or more accelerometers), such as a wrist raise. In response to determining that the third user input satisfies a first set of one or more visual alert criteria, the device displays a visual alert (e.g., 1244). In some examples, a criterion of the set of one or more visual alert criteria is that movement of the device corresponds to a wrist raise gesture. The visual alert, in accordance with a determination that the current physical activity rate is less than the physical activity rate assigned to the type of physical activity, includes a representation (e.g.,
In some examples, after displaying the visual alert (e.g., 1244), the device receives a fourth user input. In some examples, the fourth user input is a gesture (e.g., wrist raise gesture, a tap gesture, or the like) that is detected within a predetermined time since receiving a first input gesture (e.g., a third user input, described above). In response to determining that the fourth user input satisfies a second set of one or more visual alert criteria, the device displays a second visual alert (e.g., 1250) with additional information not in the first visual alert. In some examples, the additional information includes metrics for a current workout, such as mileage, time, or the like.
In some examples, a current pace is highlighted in the second visual alert.
In some examples, physical activities that are capable of being tracked by the device have animated affordances (e.g., running man animation with no ring,
In some examples, prior to displaying the physical activity rate user interface, the device displays a third user interface (e.g., 1210) with a third affordance (e.g., 1214). In such examples, the device receives a fifth user input (e.g., 1214) corresponding to the third affordance, where the physical activity rate user interface (e.g., 1216) is displayed in response to receiving the fifth user input. After receiving the first user input, the device redisplays the third user interface (e.g., 1210), wherein the third affordance (e.g., 1214) in the redisplayed third user interface includes an identification (e.g., 1214A) of whether the physical activity calculation is configured to use the first portion or the second portion of the dataset, and where the third affordance did not include the identification before receiving the first user input.
In some examples, prior to displaying the third user interface (e.g., 1210), the device displays a fourth user interface (e.g., 1204) with a scrollable list of affordances associated with different physical activities, where a fourth affordance (e.g., 1206A) in the scrollable list includes a fifth affordance (e.g., 1208). In some examples, the fourth affordance is to start an outdoor run workout. In some examples, the fifth affordance is an options button for the fourth affordance. The device receives a sixth user input (e.g., 1201) corresponding to selection of the fifth affordance, where the third user interface (e.g., 1210) is displayed in response to receiving the sixth user input. After receiving the first user input, the device redisplays the fourth user interface (e.g., 1204), where the fourth affordance (e.g., 1206A) in the redisplayed fourth user interface includes an identification (e.g., 1208B) of whether the physical activity calculation is configured to use the first portion or the second portion of the dataset, and where the fourth affordance did not include the identification before receiving the first user input.
In some examples, the fourth affordance (e.g., 1206A) includes an identification (e.g., 1208B) of a first pace assigned to a physical activity corresponding to the fourth affordance, where a sixth affordance (e.g., 1206B) in the scrollable list includes an identification of a second pace assigned to a physical activity corresponding to the sixth affordance, and where the second pace is different from the first pace.
In some examples, the physical activity rate user interface is displayed further in response to a physical activity rate being set (as depicted in
Note that details of the processes described above with respect to method 1300 (e.g.,
The foregoing description, for purpose of explanation, has been described with reference to specific examples. 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 examples 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 examples 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 increase interactions between users. 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 display representations of the personal information. Accordingly, use of such personal information data enables users to view feedback regarding data received from other users. 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 examples 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 activity and workout services, the present technology can be configured to allow users to select to “opt in” or “opt out” of participation in the collection of personal information data during registration for services or anytime thereafter. In another example, users can select not to provide activity associated data for activity and/or workout services. In yet another example, users can select to limit the length that activity associated data is maintained or entirely prohibit the development of user interfaces described herein. 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 examples, the present disclosure also contemplates that the various examples can also be implemented without the need for accessing such personal information data. That is, the various examples 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 activity 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 services described herein, or publicly available information.
This application claims priority to U.S. Provisional Application No. 62/679,906, entitled “DISPLAYING USER INTERFACES ASSOCIATED WITH PHYSICAL ACTIVITIES”, filed Jun. 3, 2018, and U.S. Provisional Application No. 62/668,159, entitled “DISPLAYING USER INTERFACES ASSOCIATED WITH PHYSICAL ACTIVITIES”, filed May 7, 2018, the entire contents of which are hereby incorporated by reference.
| Number | Name | Date | Kind |
|---|---|---|---|
| 4205628 | Null | Jun 1980 | A |
| 4842266 | Sweeney et al. | Jun 1989 | A |
| 5423863 | Felblinger et al. | Jun 1995 | A |
| 5515344 | Ng | May 1996 | A |
| 5642731 | Kehr | Jul 1997 | A |
| 5788655 | Yoshimura et al. | Aug 1998 | A |
| 6013008 | Fukushima | Jan 2000 | A |
| 6095949 | Arai | Aug 2000 | A |
| 6095984 | Amano et al. | Aug 2000 | A |
| 6097371 | Siddiqui et al. | Aug 2000 | A |
| 6244988 | Delman | Jun 2001 | B1 |
| 6416471 | Kumar | Jul 2002 | B1 |
| 6600696 | Lynn | Jul 2003 | B1 |
| 6603477 | Tittle | Aug 2003 | B1 |
| 6639584 | Li | Oct 2003 | B1 |
| 6705972 | Takano | Mar 2004 | B1 |
| 6837827 | Lee et al. | Jan 2005 | B1 |
| 6866613 | Brown et al. | Mar 2005 | B1 |
| 6950839 | Green et al. | Sep 2005 | B1 |
| 7020514 | Wiesel | Mar 2006 | B1 |
| 7128693 | Brown | Oct 2006 | B2 |
| 7166078 | Saini et al. | Jan 2007 | B2 |
| 7251454 | White | Jul 2007 | B2 |
| 7662065 | Kahn et al. | Feb 2010 | B1 |
| 7739148 | Suzuki | Jun 2010 | B2 |
| 8105208 | Oleson et al. | Jan 2012 | B2 |
| 8321006 | Snyder et al. | Nov 2012 | B1 |
| 8341557 | Pisula et al. | Dec 2012 | B2 |
| 8475339 | Hwang | Jul 2013 | B2 |
| 8676170 | Porrati | Mar 2014 | B2 |
| 8725527 | Kahn et al. | May 2014 | B1 |
| 8758262 | Rhee et al. | Jun 2014 | B2 |
| 8784115 | Chuang | Jul 2014 | B1 |
| 8825445 | Hoffman et al. | Sep 2014 | B2 |
| 8934963 | Farazi | Jan 2015 | B1 |
| 8990006 | Wallace et al. | Mar 2015 | B1 |
| 9020538 | White et al. | Apr 2015 | B1 |
| 9026927 | Brumback et al. | May 2015 | B2 |
| 9224291 | Moll-Carrillo et al. | Dec 2015 | B2 |
| 9557881 | Jain et al. | Jan 2017 | B1 |
| 9579060 | Lisy et al. | Feb 2017 | B1 |
| 9589445 | White | Mar 2017 | B2 |
| 9672715 | Roberts et al. | Jun 2017 | B2 |
| 9712629 | Molettiere | Jul 2017 | B2 |
| 9721066 | Funaro et al. | Aug 2017 | B1 |
| 9730621 | Cohen et al. | Aug 2017 | B2 |
| 9734477 | Weast et al. | Aug 2017 | B2 |
| 9801562 | Host-Madsen | Oct 2017 | B1 |
| 9813642 | Chen | Nov 2017 | B1 |
| 9817481 | Pantelopoulos et al. | Nov 2017 | B2 |
| 9854653 | Ackmann et al. | Dec 2017 | B1 |
| 9880805 | Guralnick | Jan 2018 | B1 |
| 9940682 | Hoffman | Apr 2018 | B2 |
| 10175781 | Karagozler et al. | Jan 2019 | B2 |
| 10254911 | Yang | Apr 2019 | B2 |
| 10300334 | Chuang | May 2019 | B1 |
| 10304347 | Wilson et al. | May 2019 | B2 |
| 10339830 | Han et al. | Jul 2019 | B2 |
| 10398381 | Heneghan et al. | Sep 2019 | B1 |
| 10576327 | Kim et al. | Mar 2020 | B2 |
| 10635267 | Williams | Apr 2020 | B2 |
| 10674942 | Williams et al. | Jun 2020 | B2 |
| 10762990 | Schilling et al. | Sep 2020 | B1 |
| 10764700 | Felton | Sep 2020 | B1 |
| 10777314 | Williams et al. | Sep 2020 | B1 |
| 10796549 | Roberts et al. | Oct 2020 | B2 |
| 20010049470 | Mault et al. | Dec 2001 | A1 |
| 20020045960 | Phillips et al. | Apr 2002 | A1 |
| 20020086774 | Warner | Jul 2002 | A1 |
| 20020118121 | Lehrman et al. | Aug 2002 | A1 |
| 20030023178 | Bischoff et al. | Jan 2003 | A1 |
| 20030064860 | Yamashita et al. | Apr 2003 | A1 |
| 20030181291 | Ogawa | Sep 2003 | A1 |
| 20030182628 | Lira | Sep 2003 | A1 |
| 20030191609 | Bernardi et al. | Oct 2003 | A1 |
| 20030216971 | Sick | Nov 2003 | A1 |
| 20030226695 | Mault | Dec 2003 | A1 |
| 20040014567 | Mendel | Jan 2004 | A1 |
| 20040017300 | Kotzin et al. | Jan 2004 | A1 |
| 20040077462 | Brown et al. | Apr 2004 | A1 |
| 20040128286 | Yasushi et al. | Jul 2004 | A1 |
| 20040190729 | Yonovitz et al. | Sep 2004 | A1 |
| 20040193069 | Takehara | Sep 2004 | A1 |
| 20050010117 | Agutter et al. | Jan 2005 | A1 |
| 20050027208 | Shiraishi et al. | Feb 2005 | A1 |
| 20050075214 | Brown | Apr 2005 | A1 |
| 20050079905 | Martens | Apr 2005 | A1 |
| 20050124324 | Thomas et al. | Jun 2005 | A1 |
| 20050139852 | Chen et al. | Jun 2005 | A1 |
| 20050149362 | Peterson et al. | Jul 2005 | A1 |
| 20050172311 | Hjelt et al. | Aug 2005 | A1 |
| 20050197063 | White | Sep 2005 | A1 |
| 20050216867 | Marvit et al. | Sep 2005 | A1 |
| 20050228735 | Duquette | Oct 2005 | A1 |
| 20050244013 | Battenberg et al. | Nov 2005 | A1 |
| 20050272564 | Pyles | Dec 2005 | A1 |
| 20060020174 | Matsumura et al. | Jan 2006 | A1 |
| 20060052727 | Palestrant | Mar 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 |
| 20060235319 | Belohlavek et al. | Oct 2006 | A1 |
| 20060250524 | Roche | Nov 2006 | A1 |
| 20070016440 | Stroup | Jan 2007 | A1 |
| 20070021269 | Shum | Jan 2007 | A1 |
| 20070032733 | Burton | Feb 2007 | A1 |
| 20070056727 | Newman | Mar 2007 | A1 |
| 20070113726 | Oliver et al. | May 2007 | A1 |
| 20070136093 | Rankin et al. | Jun 2007 | A1 |
| 20070143433 | Daigle | Jun 2007 | A1 |
| 20070249949 | Hadley | Oct 2007 | A1 |
| 20070271065 | Gupta et al. | Nov 2007 | A1 |
| 20080052945 | Matas et al. | Mar 2008 | A1 |
| 20080058626 | Miyata et al. | Mar 2008 | A1 |
| 20080076637 | Gilley et al. | Mar 2008 | A1 |
| 20080086318 | Gilley et al. | Apr 2008 | A1 |
| 20080096726 | Riley et al. | Apr 2008 | A1 |
| 20080141135 | Mason et al. | Jun 2008 | A1 |
| 20080146892 | Leboeuf et al. | Jun 2008 | A1 |
| 20080150731 | Laukkanen et al. | Jun 2008 | A1 |
| 20080159547 | Schuler et al. | Jul 2008 | A1 |
| 20080161707 | Farringdon et al. | Jul 2008 | A1 |
| 20080200312 | Tagliabue | Aug 2008 | A1 |
| 20080205660 | Goldstein | Aug 2008 | A1 |
| 20080228045 | Gao et al. | Sep 2008 | A1 |
| 20080240519 | Nagamitsu | Oct 2008 | A1 |
| 20080300110 | Smith et al. | Dec 2008 | A1 |
| 20090007596 | Goldstein et al. | Jan 2009 | A1 |
| 20090012988 | Brown | Jan 2009 | A1 |
| 20090052677 | Smith | Feb 2009 | A1 |
| 20090118100 | Oliver | May 2009 | A1 |
| 20090164567 | Hara | Jun 2009 | A1 |
| 20090180631 | Michael et al. | Jul 2009 | A1 |
| 20090192823 | Hawkins et al. | Jul 2009 | A1 |
| 20090210078 | Crowley | Aug 2009 | A1 |
| 20090216556 | Martin | Aug 2009 | A1 |
| 20090222056 | Lindh et al. | Sep 2009 | A1 |
| 20090233771 | Quatrochi et al. | Sep 2009 | A1 |
| 20090245537 | Morin | Oct 2009 | A1 |
| 20090262088 | Moll-carrillo et al. | Oct 2009 | A1 |
| 20090287103 | Pillai | Nov 2009 | A1 |
| 20090287327 | Hsu et al. | Nov 2009 | A1 |
| 20090290721 | Goldstein et al. | Nov 2009 | A1 |
| 20090319243 | Suarez-Rivera 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 |
| 20100031202 | Morris et al. | Feb 2010 | A1 |
| 20100042949 | Chen | Feb 2010 | A1 |
| 20100046767 | Bayley et al. | Feb 2010 | A1 |
| 20100048358 | Tchao et al. | Feb 2010 | A1 |
| 20100060586 | Pisula et al. | Mar 2010 | A1 |
| 20100062818 | Haughay et al. | Mar 2010 | A1 |
| 20100062905 | Rottler et al. | Mar 2010 | A1 |
| 20100064255 | Rottler et al. | Mar 2010 | A1 |
| 20100076331 | Chan et al. | Mar 2010 | A1 |
| 20100079291 | Kroll et al. | Apr 2010 | A1 |
| 20100121700 | Wigder | May 2010 | A1 |
| 20100145209 | Lee et al. | Jun 2010 | A1 |
| 20100150378 | Lee et al. | Jun 2010 | A1 |
| 20100179832 | Van et al. | Jul 2010 | A1 |
| 20100194692 | Orr et al. | Aug 2010 | A1 |
| 20100198453 | Dorogusker et al. | Aug 2010 | A1 |
| 20100222645 | Nadler et al. | Sep 2010 | A1 |
| 20100281374 | Schulz et al. | Nov 2010 | A1 |
| 20100292600 | Dibenedetto et al. | Nov 2010 | A1 |
| 20100298899 | Donnelly et al. | Nov 2010 | A1 |
| 20100305965 | Benjamin et al. | Dec 2010 | A1 |
| 20100312138 | Regas | Dec 2010 | A1 |
| 20100331145 | Lakovic et al. | Dec 2010 | A1 |
| 20110003665 | Burton et al. | Jan 2011 | A1 |
| 20110016120 | Haughay et al. | Jan 2011 | A1 |
| 20110066051 | Moon et al. | Mar 2011 | A1 |
| 20110071869 | Obrien et al. | Mar 2011 | A1 |
| 20110074699 | Marr et al. | Mar 2011 | A1 |
| 20110093481 | Hussam | Apr 2011 | A1 |
| 20110098928 | Hoffman et al. | Apr 2011 | A1 |
| 20110112418 | Feild et al. | May 2011 | A1 |
| 20110125041 | Fischell et al. | May 2011 | A1 |
| 20110137678 | Williams | Jun 2011 | A1 |
| 20110137836 | Kuriyama et al. | Jun 2011 | A1 |
| 20110152656 | Weinert et al. | Jun 2011 | A1 |
| 20110166631 | Breining | Jul 2011 | A1 |
| 20110167369 | Van Os | Jul 2011 | A1 |
| 20110201911 | Johnson et al. | Aug 2011 | A1 |
| 20110213276 | Sarussi et al. | Sep 2011 | A1 |
| 20110214162 | Brakensiek et al. | Sep 2011 | A1 |
| 20110227872 | Huska et al. | Sep 2011 | A1 |
| 20110230169 | Ohki | Sep 2011 | A1 |
| 20110230986 | Lafortune et al. | Sep 2011 | A1 |
| 20110245623 | Chutani et al. | Oct 2011 | A1 |
| 20110246509 | Migita et al. | Oct 2011 | A1 |
| 20110261079 | Ingrassia et al. | Oct 2011 | A1 |
| 20110275940 | Nims et al. | Nov 2011 | A1 |
| 20110306389 | Nagayama | Dec 2011 | A1 |
| 20110307821 | Martens | Dec 2011 | A1 |
| 20120002510 | Berman, Jr. | Jan 2012 | A1 |
| 20120015778 | Lee et al. | Jan 2012 | A1 |
| 20120015779 | Powch et al. | Jan 2012 | A1 |
| 20120029303 | Shaya | Feb 2012 | A1 |
| 20120030623 | Hoellwarth | Feb 2012 | A1 |
| 20120034897 | Kreitzer et al. | Feb 2012 | A1 |
| 20120038651 | Case et al. | Feb 2012 | A1 |
| 20120041767 | Hoffman | Feb 2012 | A1 |
| 20120042039 | Mark | Feb 2012 | A1 |
| 20120059664 | Georgiev et al. | Mar 2012 | A1 |
| 20120065480 | Badilini et al. | Mar 2012 | A1 |
| 20120071770 | Grey | Mar 2012 | A1 |
| 20120092383 | Hysek et al. | Apr 2012 | A1 |
| 20120105225 | Valtonen | May 2012 | A1 |
| 20120112908 | Prykaeri et al. | May 2012 | A1 |
| 20120116550 | Hoffman et al. | May 2012 | A1 |
| 20120203124 | Lim | Aug 2012 | A1 |
| 20120232414 | Mollicone et al. | Sep 2012 | A1 |
| 20120245447 | Karan et al. | Sep 2012 | A1 |
| 20120253485 | Weast et al. | Oct 2012 | A1 |
| 20120274508 | Brown et al. | Nov 2012 | A1 |
| 20120283587 | Gosh et al. | Nov 2012 | A1 |
| 20120283855 | Hoffman et al. | Nov 2012 | A1 |
| 20120302840 | Kubo | Nov 2012 | A1 |
| 20120317167 | Rahman | Dec 2012 | A1 |
| 20120321094 | Schiller et al. | Dec 2012 | A1 |
| 20120326873 | Utter | Dec 2012 | A1 |
| 20130002425 | Hatch et al. | Jan 2013 | A1 |
| 20130011819 | Horseman | Jan 2013 | A1 |
| 20130012788 | Horseman | Jan 2013 | A1 |
| 20130013331 | Horseman | Jan 2013 | A1 |
| 20130033376 | Seyed et al. | Feb 2013 | A1 |
| 20130054150 | Sacks et al. | Feb 2013 | A1 |
| 20130054720 | Kang et al. | Feb 2013 | A1 |
| 20130065569 | Leipzig et al. | Mar 2013 | A1 |
| 20130067050 | Kotteri et al. | Mar 2013 | A1 |
| 20130073960 | Eppolito et al. | Mar 2013 | A1 |
| 20130081083 | Yu et al. | Mar 2013 | A1 |
| 20130093715 | Marsden et al. | Apr 2013 | A1 |
| 20130095459 | Tran | Apr 2013 | A1 |
| 20130106603 | Weast et al. | May 2013 | A1 |
| 20130106684 | Weast et al. | May 2013 | A1 |
| 20130110264 | Weast et al. | May 2013 | A1 |
| 20130114100 | Torii et al. | May 2013 | A1 |
| 20130115583 | Gordon et al. | May 2013 | A1 |
| 20130132028 | Crankson et al. | May 2013 | A1 |
| 20130137073 | Nacey et al. | May 2013 | A1 |
| 20130141233 | Jacobs et al. | Jun 2013 | A1 |
| 20130151285 | McLaren | Jun 2013 | A1 |
| 20130158416 | Hatlestad et al. | Jun 2013 | A1 |
| 20130184613 | Homsi et al. | Jul 2013 | A1 |
| 20130187923 | Yoshimoto et al. | Jul 2013 | A1 |
| 20130188322 | Lowe | Jul 2013 | A1 |
| 20130197679 | Balakrishnan | Aug 2013 | A1 |
| 20130198672 | Yoon et al. | Aug 2013 | A1 |
| 20130202121 | Georgiou et al. | Aug 2013 | A1 |
| 20130203475 | Kil et al. | Aug 2013 | A1 |
| 20130215042 | Messerschmidt et al. | Aug 2013 | A1 |
| 20130217979 | Blackadar et al. | Aug 2013 | A1 |
| 20130231575 | Erkkila | Sep 2013 | A1 |
| 20130231711 | Kaib | Sep 2013 | A1 |
| 20130231947 | Shusterman | Sep 2013 | A1 |
| 20130233097 | Hayner et al. | Sep 2013 | A1 |
| 20130262155 | Hinkamp | Oct 2013 | A1 |
| 20130268398 | Agami et al. | Oct 2013 | A1 |
| 20130304616 | Raleigh et al. | Nov 2013 | A1 |
| 20130317380 | Liley et al. | Nov 2013 | A1 |
| 20130325394 | Yuen et al. | Dec 2013 | A1 |
| 20130325396 | Yuen et al. | Dec 2013 | A1 |
| 20130332286 | Medelius et al. | Dec 2013 | A1 |
| 20130345978 | Lush et al. | Dec 2013 | A1 |
| 20140037107 | Marino et al. | Feb 2014 | A1 |
| 20140038781 | Foley et al. | Feb 2014 | A1 |
| 20140067096 | Aibara | Mar 2014 | A1 |
| 20140073486 | Ahmed et al. | Mar 2014 | A1 |
| 20140081118 | Reinhold, Jr. et al. | Mar 2014 | A1 |
| 20140081666 | Teller et al. | Mar 2014 | A1 |
| 20140088995 | Damani | Mar 2014 | A1 |
| 20140108998 | Chaudhri et al. | Apr 2014 | A1 |
| 20140127996 | Park et al. | May 2014 | A1 |
| 20140129243 | Utter | May 2014 | A1 |
| 20140135592 | Ohnemus et al. | May 2014 | A1 |
| 20140139637 | Mistry 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 |
| 20140176335 | Brumback et al. | Jun 2014 | A1 |
| 20140176346 | 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 |
| 20140189584 | Weng et al. | Jul 2014 | A1 |
| 20140197946 | Park et al. | Jul 2014 | A1 |
| 20140200426 | Taub et al. | Jul 2014 | A1 |
| 20140200691 | Lee et al. | Jul 2014 | A1 |
| 20140218369 | Yuen et al. | Aug 2014 | A1 |
| 20140228647 | Sakamoto et al. | Aug 2014 | A1 |
| 20140239065 | Zhou et al. | Aug 2014 | A1 |
| 20140240122 | Roberts et al. | Aug 2014 | A1 |
| 20140240349 | Tuukkanen | Aug 2014 | A1 |
| 20140244009 | Mestas | Aug 2014 | A1 |
| 20140245161 | Yuen et al. | Aug 2014 | A1 |
| 20140257537 | Stroupe et al. | Sep 2014 | A1 |
| 20140266776 | Miller et al. | Sep 2014 | A1 |
| 20140275852 | Hong et al. | Sep 2014 | A1 |
| 20140275854 | Venkatraman et al. | Sep 2014 | A1 |
| 20140275856 | Kohlrausch et al. | Sep 2014 | A1 |
| 20140277628 | Nieminen et al. | Sep 2014 | A1 |
| 20140278220 | Yuen | Sep 2014 | A1 |
| 20140278229 | Hong et al. | Sep 2014 | A1 |
| 20140282153 | Christiansen et al. | Sep 2014 | A1 |
| 20140288680 | Hoffman et al. | Sep 2014 | A1 |
| 20140327527 | Goldstein et al. | Nov 2014 | A1 |
| 20140336796 | Agnew | Nov 2014 | A1 |
| 20140337450 | Choudhary et al. | Nov 2014 | A1 |
| 20140337451 | Choudhary et al. | Nov 2014 | A1 |
| 20140344687 | Durham et al. | Nov 2014 | A1 |
| 20140344723 | Malik et al. | Nov 2014 | A1 |
| 20140344951 | Brewer | Nov 2014 | A1 |
| 20140354494 | Katz | Dec 2014 | A1 |
| 20140358012 | Richards et al. | Dec 2014 | A1 |
| 20140371887 | Hoffman et al. | Dec 2014 | A1 |
| 20150018632 | Khair | Jan 2015 | A1 |
| 20150057943 | Self et al. | Feb 2015 | A1 |
| 20150065302 | Ou et al. | Mar 2015 | A1 |
| 20150067513 | Zambetti et al. | Mar 2015 | A1 |
| 20150067811 | Agnew et al. | Mar 2015 | A1 |
| 20150074571 | Marti et al. | Mar 2015 | A1 |
| 20150081059 | Hwang et al. | Mar 2015 | A1 |
| 20150081210 | Yeh et al. | Mar 2015 | A1 |
| 20150083970 | Koh et al. | Mar 2015 | A1 |
| 20150098309 | Adams et al. | Apr 2015 | A1 |
| 20150099991 | Yamaguchi et al. | Apr 2015 | A1 |
| 20150100245 | Huang et al. | Apr 2015 | A1 |
| 20150106025 | Keller et al. | Apr 2015 | A1 |
| 20150110277 | Pidgeon et al. | Apr 2015 | A1 |
| 20150110279 | Tejerina | Apr 2015 | A1 |
| 20150112700 | Sublett et al. | Apr 2015 | A1 |
| 20150118657 | Shrake et al. | Apr 2015 | A1 |
| 20150120633 | Norlander et al. | Apr 2015 | A1 |
| 20150125832 | Tran | May 2015 | A1 |
| 20150130830 | Nagasaki et al. | May 2015 | A1 |
| 20150142689 | Squires | May 2015 | A1 |
| 20150153943 | Wang | Jun 2015 | A1 |
| 20150181314 | Swanson | Jun 2015 | A1 |
| 20150182843 | Esposito et al. | Jul 2015 | A1 |
| 20150185967 | Ly et al. | Jul 2015 | A1 |
| 20150193805 | Filipiak | Jul 2015 | A1 |
| 20150196804 | Koduri et al. | Jul 2015 | A1 |
| 20150199494 | Koduri et al. | Jul 2015 | A1 |
| 20150205492 | Nobil | Jul 2015 | A1 |
| 20150205930 | Shaanan et al. | Jul 2015 | A1 |
| 20150205947 | Berman et al. | Jul 2015 | A1 |
| 20150216448 | Lotan et al. | Aug 2015 | A1 |
| 20150217163 | Amis | Aug 2015 | A1 |
| 20150220883 | B'Far | Aug 2015 | A1 |
| 20150230717 | Wan | Aug 2015 | A1 |
| 20150262499 | Wicka et al. | Sep 2015 | A1 |
| 20150269848 | Yuen et al. | Sep 2015 | A1 |
| 20150286800 | Kanagala et al. | Oct 2015 | A1 |
| 20150288944 | Nistico et al. | Oct 2015 | A1 |
| 20150289823 | Rack-Gomer et al. | Oct 2015 | A1 |
| 20150293592 | Cheong et al. | Oct 2015 | A1 |
| 20150297134 | Albert et al. | Oct 2015 | A1 |
| 20150301691 | Qin | Oct 2015 | A1 |
| 20150324751 | Orenstein et al. | Nov 2015 | A1 |
| 20150331589 | Kawakita | Nov 2015 | A1 |
| 20150347711 | Soli | Dec 2015 | A1 |
| 20150374310 | Lee | Dec 2015 | A1 |
| 20160015275 | Samadani et al. | Jan 2016 | A1 |
| 20160019360 | Pahwa et al. | Jan 2016 | A1 |
| 20160027282 | Lee | Jan 2016 | A1 |
| 20160048298 | Choi et al. | Feb 2016 | A1 |
| 20160055420 | Karanam et al. | Feb 2016 | A1 |
| 20160058313 | Sato | Mar 2016 | A1 |
| 20160058336 | Blahnik | Mar 2016 | A1 |
| 20160058337 | Blahnik et al. | Mar 2016 | A1 |
| 20160062582 | Wilson et al. | Mar 2016 | A1 |
| 20160063215 | Zamer | Mar 2016 | A1 |
| 20160065505 | Iskander | Mar 2016 | A1 |
| 20160085937 | Dettinger et al. | Mar 2016 | A1 |
| 20160086500 | Kaleal | Mar 2016 | A1 |
| 20160098522 | Weinstein | Apr 2016 | A1 |
| 20160106398 | Kuppuswami | Apr 2016 | A1 |
| 20160109961 | Parshionikar | Apr 2016 | A1 |
| 20160132046 | Beoughter et al. | May 2016 | A1 |
| 20160135731 | Drennan | May 2016 | A1 |
| 20160140828 | Deforest | May 2016 | A1 |
| 20160150978 | Yuen et al. | Jun 2016 | A1 |
| 20160156584 | Hum et al. | Jun 2016 | A1 |
| 20160174857 | Eggers et al. | Jun 2016 | A1 |
| 20160196635 | Cho et al. | Jul 2016 | A1 |
| 20160210099 | Hampapuram | Jul 2016 | A1 |
| 20160220225 | Wang et al. | Aug 2016 | A1 |
| 20160235325 | Chou | Aug 2016 | A1 |
| 20160235374 | Miller | Aug 2016 | A1 |
| 20160249857 | Choi et al. | Sep 2016 | A1 |
| 20160250517 | Tilvis | Sep 2016 | A1 |
| 20160256741 | Holma et al. | Sep 2016 | A1 |
| 20160263435 | Venkatraman | Sep 2016 | A1 |
| 20160275990 | Vassort | Sep 2016 | A1 |
| 20160278659 | Kaib et al. | Sep 2016 | A1 |
| 20160278667 | Villard et al. | Sep 2016 | A1 |
| 20160279475 | Aragones et al. | Sep 2016 | A1 |
| 20160287177 | Huppert et al. | Oct 2016 | A1 |
| 20160292373 | Spors et al. | Oct 2016 | A1 |
| 20160299769 | Hunter et al. | Oct 2016 | A1 |
| 20160301761 | Sanchez-Sandoval et al. | Oct 2016 | A1 |
| 20160301794 | Schlakman et al. | Oct 2016 | A1 |
| 20160302666 | Shaya | Oct 2016 | A1 |
| 20160314670 | Roberts et al. | Oct 2016 | A1 |
| 20160314683 | Felch et al. | Oct 2016 | A1 |
| 20160317341 | Galvan | Nov 2016 | A1 |
| 20160324457 | Dagum | Nov 2016 | A1 |
| 20160328736 | Wang et al. | Nov 2016 | A1 |
| 20160328991 | Simpson et al. | Nov 2016 | A1 |
| 20160332025 | Repka | Nov 2016 | A1 |
| 20160346607 | Rapfogel | Dec 2016 | A1 |
| 20160360100 | Kim et al. | Dec 2016 | A1 |
| 20160375306 | Gu et al. | Dec 2016 | A1 |
| 20160379511 | Dawson et al. | Dec 2016 | A1 |
| 20170000348 | Karsten et al. | Jan 2017 | A1 |
| 20170000359 | Kohli et al. | Jan 2017 | A1 |
| 20170001073 | Krueger et al. | Jan 2017 | A1 |
| 20170007159 | Dieffenderfer et al. | Jan 2017 | A1 |
| 20170007167 | Kostic et al. | Jan 2017 | A1 |
| 20170011210 | Cheong et al. | Jan 2017 | A1 |
| 20170014037 | Coppola et al. | Jan 2017 | A1 |
| 20170021184 | Pavel et al. | Jan 2017 | A1 |
| 20170024399 | Boyle et al. | Jan 2017 | A1 |
| 20170024539 | Webb et al. | Jan 2017 | A1 |
| 20170032168 | Kim | Feb 2017 | A1 |
| 20170039327 | Bitran et al. | Feb 2017 | A1 |
| 20170046024 | Dascola et al. | Feb 2017 | A1 |
| 20170053542 | Wilson et al. | Feb 2017 | A1 |
| 20170071551 | Jain et al. | Mar 2017 | A1 |
| 20170075551 | Robinson et al. | Mar 2017 | A1 |
| 20170086693 | Peterson et al. | Mar 2017 | A1 |
| 20170095695 | Mangusson et al. | Apr 2017 | A1 |
| 20170127997 | Hyde et al. | May 2017 | A1 |
| 20170132395 | Futch | May 2017 | A1 |
| 20170136297 | Penie | May 2017 | A1 |
| 20170150917 | Brief et al. | Jun 2017 | A1 |
| 20170153606 | Pitis et al. | Jun 2017 | A1 |
| 20170153804 | Kim et al. | Jun 2017 | A1 |
| 20170156593 | Ferber et al. | Jun 2017 | A1 |
| 20170161014 | Kikugawa | Jun 2017 | A1 |
| 20170172522 | Insler et al. | Jun 2017 | A1 |
| 20170181645 | Mahalingam et al. | Jun 2017 | A1 |
| 20170188841 | Ma et al. | Jul 2017 | A1 |
| 20170202496 | Ramanathan | Jul 2017 | A1 |
| 20170209766 | Riley et al. | Jul 2017 | A1 |
| 20170235443 | Suzuki | Aug 2017 | A1 |
| 20170237694 | Choudhary et al. | Aug 2017 | A1 |
| 20170239524 | Lee et al. | Aug 2017 | A1 |
| 20170243508 | Cheng | Aug 2017 | A1 |
| 20170258455 | Qi | Sep 2017 | A1 |
| 20170274149 | Aeschlimann | Sep 2017 | A1 |
| 20170274267 | Blahnik | Sep 2017 | A1 |
| 20170281026 | Nick et al. | Oct 2017 | A1 |
| 20170281057 | Blahnik et al. | Oct 2017 | A1 |
| 20170293727 | Klaassen et al. | Oct 2017 | A1 |
| 20170294174 | Albadawi et al. | Oct 2017 | A1 |
| 20170300186 | Kuhar | Oct 2017 | A1 |
| 20170303844 | Baker et al. | Oct 2017 | A1 |
| 20170319184 | Sano | Nov 2017 | A1 |
| 20170319941 | Smith et al. | Nov 2017 | A1 |
| 20170330297 | Cronin et al. | Nov 2017 | A1 |
| 20170333752 | Korkala et al. | Nov 2017 | A1 |
| 20170348562 | Jung | Dec 2017 | A1 |
| 20170354845 | Williams et al. | Dec 2017 | A1 |
| 20170357329 | Park et al. | Dec 2017 | A1 |
| 20170357520 | De vries et al. | Dec 2017 | A1 |
| 20180000426 | Li | Jan 2018 | A1 |
| 20180001184 | Tran et al. | Jan 2018 | A1 |
| 20180011686 | Zhao et al. | Jan 2018 | A1 |
| 20180042559 | Cabrera et al. | Feb 2018 | A1 |
| 20180047277 | Thyroff | Feb 2018 | A1 |
| 20180049659 | Briante et al. | Feb 2018 | A1 |
| 20180049696 | Eom et al. | Feb 2018 | A1 |
| 20180053200 | Cronin et al. | Feb 2018 | A1 |
| 20180055490 | Lee et al. | Mar 2018 | A1 |
| 20180056132 | Foley 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 |
| 20180070861 | Eastman et al. | Mar 2018 | A1 |
| 20180074462 | Helder et al. | Mar 2018 | A1 |
| 20180074464 | Essery et al. | Mar 2018 | A1 |
| 20180078182 | Chen et al. | Mar 2018 | A1 |
| 20180096739 | Sano | Apr 2018 | A1 |
| 20180107962 | Lundin et al. | Apr 2018 | A1 |
| 20180117414 | Miyasaka et al. | May 2018 | A1 |
| 20180126248 | Dion et al. | May 2018 | A1 |
| 20180137937 | Gass | May 2018 | A1 |
| 20180150709 | Ha | May 2018 | A1 |
| 20180154212 | Park et al. | Jun 2018 | A1 |
| 20180189077 | Gupta et al. | Jul 2018 | A1 |
| 20180206766 | Blahnik et al. | Jul 2018 | A1 |
| 20180211020 | Fukuda | Jul 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 |
| 20180263517 | Kubo | Sep 2018 | A1 |
| 20180272190 | Miura et al. | Sep 2018 | A1 |
| 20180279885 | Bulut | Oct 2018 | A1 |
| 20180329584 | Williams et al. | Nov 2018 | A1 |
| 20180336530 | Johnson et al. | Nov 2018 | A1 |
| 20180345078 | Blahnik et al. | Dec 2018 | A1 |
| 20180350451 | Ohnemus et al. | Dec 2018 | A1 |
| 20180368814 | Kudtarkar | Dec 2018 | A1 |
| 20180376107 | Shibaev et al. | Dec 2018 | A1 |
| 20190008467 | Averina et al. | Jan 2019 | A1 |
| 20190012898 | Wittrup | Jan 2019 | A1 |
| 20190014205 | Miloseski et al. | Jan 2019 | A1 |
| 20190025995 | Williams | Jan 2019 | A1 |
| 20190034049 | Williams et al. | Jan 2019 | A1 |
| 20190034050 | Williams et al. | Jan 2019 | A1 |
| 20190034494 | Bradley et al. | Jan 2019 | A1 |
| 20190043337 | Liu et al. | Feb 2019 | A1 |
| 20190090800 | Bosworth et al. | Mar 2019 | A1 |
| 20190090816 | Horseman | Mar 2019 | A1 |
| 20190104951 | Valys | Apr 2019 | A1 |
| 20190122523 | Roberts et al. | Apr 2019 | A1 |
| 20190138696 | Carpenter et al. | May 2019 | A1 |
| 20190192086 | Menon et al. | Jun 2019 | A1 |
| 20190206538 | Xing et al. | Jul 2019 | A1 |
| 20190209777 | O'connell et al. | Jul 2019 | A1 |
| 20190223843 | Vitti | Jul 2019 | A1 |
| 20190228179 | Rakshit et al. | Jul 2019 | A1 |
| 20190232110 | Williams et al. | Aug 2019 | A1 |
| 20190232111 | Williams et al. | Aug 2019 | A1 |
| 20190240534 | Black | Aug 2019 | A1 |
| 20190252054 | Dirani et al. | Aug 2019 | A1 |
| 20190274562 | Soli et al. | Sep 2019 | A1 |
| 20190274563 | Soli et al. | Sep 2019 | A1 |
| 20190274564 | Soli et al. | Sep 2019 | A1 |
| 20190274565 | Soli et al. | Sep 2019 | A1 |
| 20190278556 | Usher et al. | Sep 2019 | A1 |
| 20190279520 | Wilson et al. | Sep 2019 | A1 |
| 20190298230 | Nicholson et al. | Oct 2019 | A1 |
| 20190336044 | Williams et al. | Nov 2019 | A1 |
| 20190336045 | Williams | Nov 2019 | A1 |
| 20190339849 | Williams et al. | Nov 2019 | A1 |
| 20190365332 | Fedichev et al. | Dec 2019 | A1 |
| 20190387982 | Buller | Dec 2019 | A1 |
| 20200000441 | Lafon et al. | Jan 2020 | A1 |
| 20200014967 | Putnam | Jan 2020 | A1 |
| 20200101365 | Wilson et al. | Apr 2020 | A1 |
| 20200126673 | Tanabe et al. | Apr 2020 | A1 |
| 20200261011 | Seppänen et al. | Aug 2020 | A1 |
| 20200273566 | Bhowmik et al. | Aug 2020 | A1 |
| 20200297249 | Williams et al. | Sep 2020 | A1 |
| 20200356687 | Salzman et al. | Nov 2020 | A1 |
| 20200357522 | Pahwa 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 |
| 20200381100 | Williams et al. | Dec 2020 | A1 |
| 20200381123 | Dryer et al. | Dec 2020 | A1 |
| 20200382613 | Sundstrom et al. | Dec 2020 | A1 |
| 20200382866 | Felton | Dec 2020 | A1 |
| 20200382867 | Felton | Dec 2020 | A1 |
| 20200384314 | Lee et al. | Dec 2020 | A1 |
| 20210007632 | Blahnik et al. | Jan 2021 | A1 |
| 20210007633 | Blahnik et al. | Jan 2021 | A1 |
| Number | Date | Country |
|---|---|---|
| 2815518 | May 2012 | CA |
| 1337638 | Feb 2002 | CN |
| 1397904 | Feb 2003 | CN |
| 1585943 | Feb 2005 | CN |
| 101150810 | Mar 2008 | CN |
| 101541387 | Sep 2009 | CN |
| 101651870 | Feb 2010 | CN |
| 101836894 | Sep 2010 | CN |
| 102339201 | Feb 2012 | CN |
| 102448555 | May 2012 | CN |
| 102804238 | Nov 2012 | CN |
| 102989159 | Mar 2013 | CN |
| 103212197 | Jul 2013 | CN |
| 103370924 | Oct 2013 | CN |
| 103403627 | Nov 2013 | CN |
| 104288983 | Jan 2015 | CN |
| 104501043 | Apr 2015 | CN |
| 104720765 | Jun 2015 | CN |
| 106537397 | Mar 2017 | CN |
| 106709235 | May 2017 | CN |
| 106725384 | May 2017 | CN |
| 106878550 | Jun 2017 | CN |
| 107278138 | Oct 2017 | CN |
| 107591211 | Jan 2018 | CN |
| 107713981 | Feb 2018 | CN |
| 1935339 | Jun 2008 | EP |
| 2025368 | Feb 2009 | EP |
| 2391004 | Nov 2011 | EP |
| 2921899 | Sep 2015 | EP |
| 3042606 | Jul 2016 | EP |
| 3096235 | Nov 2016 | EP |
| 3101882 | Dec 2016 | EP |
| 3557590 | Oct 2019 | EP |
| 6-187118 | Jul 1994 | JP |
| 2001-76078 | Mar 2001 | JP |
| 2002-190007 | Jul 2002 | JP |
| 2003-337863 | Nov 2003 | JP |
| 2004-102609 | Apr 2004 | JP |
| 2004-113466 | Apr 2004 | JP |
| 2005-79814 | Mar 2005 | JP |
| 2006-230679 | Sep 2006 | JP |
| 2007-260288 | Oct 2007 | JP |
| 2008-104758 | May 2008 | JP |
| 2008-183339 | Aug 2008 | JP |
| 2010-12335 | Jan 2010 | JP |
| 2010-122901 | Jun 2010 | JP |
| 2010-181280 | Aug 2010 | JP |
| 2011-125633 | Jun 2011 | JP |
| 2011-183101 | Sep 2011 | JP |
| 2011-192126 | Sep 2011 | JP |
| 2011-198184 | Oct 2011 | JP |
| 2011-206323 | Oct 2011 | JP |
| 2011-259253 | Dec 2011 | JP |
| 2012-59264 | Mar 2012 | JP |
| 2012-524640 | Oct 2012 | JP |
| 2012-230503 | Nov 2012 | JP |
| 2013-103020 | May 2013 | JP |
| 2013-117690 | Jun 2013 | JP |
| 2013-544140 | Dec 2013 | JP |
| 2016-502875 | Feb 2016 | JP |
| 2016-177151 | Oct 2016 | JP |
| 2017-134689 | Aug 2017 | JP |
| 2017-532069 | Nov 2017 | JP |
| 10-2011-0017076 | Feb 2011 | KR |
| 10-2012-0023657 | Mar 2012 | KR |
| 10-2013-0111569 | Oct 2013 | KR |
| 10-2013-0111570 | Oct 2013 | KR |
| 10-2013-0135282 | Dec 2013 | KR |
| 10-1594486 | Feb 2016 | KR |
| 10-2016-0028351 | Mar 2016 | KR |
| 10-2017-0003608 | Jan 2017 | KR |
| 10-2019-0094795 | Aug 2019 | KR |
| 199941682 | Aug 1999 | WO |
| 200227530 | Apr 2002 | WO |
| 03067202 | Aug 2003 | WO |
| 2005070289 | Aug 2005 | WO |
| 2006046648 | May 2006 | WO |
| 2008073359 | Jun 2008 | WO |
| 2009129402 | Oct 2009 | WO |
| 2010126825 | Nov 2010 | WO |
| 2012021507 | Feb 2012 | WO |
| 2012060588 | May 2012 | WO |
| 2012061438 | May 2012 | WO |
| 2012061440 | May 2012 | WO |
| 2012078079 | Jun 2012 | WO |
| 2013052789 | Apr 2013 | WO |
| 2013109762 | Jul 2013 | WO |
| 2013109777 | Jul 2013 | WO |
| 2013109916 | Jul 2013 | WO |
| 2013173838 | Nov 2013 | WO |
| 2014015378 | Jan 2014 | WO |
| 2014207294 | Dec 2014 | WO |
| 2015187799 | Dec 2015 | WO |
| 2015198488 | Dec 2015 | WO |
| 2016036582 | Mar 2016 | WO |
| 2016151479 | Sep 2016 | WO |
| 2016161152 | Oct 2016 | WO |
| 2016164475 | Oct 2016 | WO |
| 2017003045 | Jan 2017 | WO |
| 2017037242 | Mar 2017 | WO |
| 2017062621 | Apr 2017 | WO |
| 2017087642 | May 2017 | WO |
| 2017090810 | Jun 2017 | WO |
| 2017215203 | Dec 2017 | WO |
| 2018148356 | Aug 2018 | WO |
| 2019020977 | Jan 2019 | WO |
| 2019024603 | Feb 2019 | WO |
| 2019168956 | Sep 2019 | WO |
| Entry |
|---|
| Graphs and Charts (teacher resources) retrieved from https://www.teachervision.com/lesson-planning/graph-chart-teacher-resources on [Dec. 12, 2018]. 4 pages (Year: 2018). |
| The Data Visualization Catalogue. Multi-set Bar Chart. Internet article published Feb. 8, 2014. Retrieved from [https://datavizcatalogue.com/methods/multiset_barchart.html] via the Internet Archive on [May 9, 2019]. 3 pages. (Year: 2014). |
| Better Evaluation. Bar Chart. Internet article updated 31 Oct. 2014. Retrieved from [https://www.betterevaluation.org/en/evaluation-options/BarChart] on [May 13, 2019]. 8 pages. (Year: 2014). |
| Notice of Allowance received for U.S. Appl. No. 15/183,663, dated Jan. 17, 2019, 6 pages. |
| Office Action received for Japanese Patent Application No. 2018-068846, dated Jan. 8, 2019, 6 pages (3 pages of English Translation and 3 pages of Official copy). |
| Non-Final Office Action received for U.S. Appl. No. 14/732,773, dated Feb. 8, 2019, 32 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2017/035554, dated Dec. 20, 2018, 39 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/144,849, dated Dec. 31, 2018, 28 pages. |
| Notice of Allowance received for U.S. Appl. No. 15/616,480, dated Jan. 3, 2019, 8 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 15/183,663, dated Mar. 27, 2019, 2 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/925,652, dated Apr. 5, 2019, 28 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/144,030, dated Apr. 12, 2019, 8 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2016-557650, dated Apr. 9, 2019, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 201380081349.6, dated Feb. 26, 2019, 12 pages (6 pages of English Translation and 6 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 201680047983.1, dated Mar. 18, 2019, 18 pages (6 pages of English Translation and 12 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 201810105846.X, dated Feb. 25, 2019, 10 pages (5 pages of English Translation and 5 pages of Official copy). |
| Office Action received for Danish Patent Application No. PA201770423, dated Mar. 29, 2019, 6 pages. |
| Office Action received for Danish Patent Application No. PA201870380, dated Mar. 27, 2019, 4 pages. |
| Office Action received for Danish Patent Application No. PA201870601, dated Dec. 13, 2018, 8 pages. |
| Office Action received for Germany Patent Application No. 112015002326.7, dated Feb. 20, 2019, 7 pages (2 pages of English Translation and 5 pages of Official Copy). |
| Search Report and Opinion received for Danish Patent Application No. PA201870599, dated Dec. 21, 2018, 9 pages. |
| Search Report and Opinion received for Danish Patent Application No. PA201870600, dated Jan. 31, 2019, 8 pages. |
| Search Report and Opinion received for Danish Patent Application No. PA201870602, dated Dec. 19, 2018, 8 pages. |
| Supplemental Notice of Allowance received for U.S. Appl. No. 15/616,480, dated Mar. 28, 2019, 2 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. |
| 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. |
| Non-Final Office Action received for U.S. Appl. No. 16/143,909, dated Apr. 19, 2019, 16 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/143,959, dated Apr. 17, 2019, 15 pages. |
| Partial Supplementary European Search Report received for European Patent Application No. 17810749.6, dated Apr. 25, 2019, 8 pages. |
| Office Action received for Danish Patent Application No. PA201770191, dated Nov. 21, 2018, 4 pages. |
| Office Action received for Japanese Patent Application No. 2018-014096, dated Nov. 6, 2018, 15 pages (7 pages of English Translation and 8 pages of Official Copy). |
| Corrected Notice of Allowance received for U.S. Appl. No. 15/183,663, dated Feb. 25, 2019, 3 pages. |
| Extended European Search Report received for European Patent Application No. 16837432.0, dated Mar. 11, 2019, 10 pages. |
| Office Action received for Australian Patent Application No. 2018101855, dated Feb. 22, 2019, 4 pages. |
| Office Action received for Danish Patent Application No. PA201870378, dated Feb. 25, 2019, 3 pages. |
| Office Action received for Danish Patent Application No. PA201870379, dated Feb. 28, 2019, 3 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/143,959, dated Dec. 13, 2019, 2 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2018/031662, dated Nov. 28, 2019, 12 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-odlBJB4>, 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=UvAA4OggL3E>, Jan. 23, 2017, 3 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2018-068846, dated Dec. 9, 2019, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for U.S. Appl. No. 14/732,773, dated Dec. 18, 2019, 21 pages. |
| Notice of Allowance received for U.S. Appl. No. 15/600,243, dated Dec. 12, 2019, 7 pages. |
| Office Action received for Chinese Patent Application No. 201680047983.1, dated Nov. 28, 2019, 9 pages (4 pages of English Translation and 5 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2019-7025781, dated Nov. 26, 2019, 10 pages (4 pages of English Translation and 6 pages of Official Copy). |
| Advisory Action received for U.S. Appl. No. 14/732,773, dated Aug. 23, 2019, 6 pages. |
| Advisory Action received for U.S. Appl. No. 16/144,849, dated Aug. 12, 2019, 5 pages. |
| Certificate of Examination received for Australian Patent Application No. 2018101855, dated Aug. 6, 2019, 2 pages. |
| Final Office Action received for U.S. Appl. No. 14/732,773, dated Jun. 21, 2019, 32 pages. |
| Final Office Action received for U.S. Appl. No. 15/608,848, dated Jun. 26, 2019, 27 pages. |
| Final Office Action received for U.S. Appl. No. 15/925,652, dated Aug. 1, 2019, 30 Pages. |
| Final Office Action received for U.S. Appl. No. 16/143,909, dated Aug. 28, 2019, 20 pages. |
| Final Office Action received for U.S. Appl. No. 16/144,849, dated Jun. 7, 2019, 29 pages. |
| Intention to Grant received for Danish Patent Application No. PA201870600, dated Jul. 10, 2019, 2 pages. |
| Invitation to Pay Additional Fees received for PCT Patent Application No. PCT/US2019/019694, dated Jul. 10, 2019, 12 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/600,243, dated Jun. 27, 2019, 17 Pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/627,069, dated Jun. 21, 2019, 22 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/143,997, dated May 21, 2019, 15 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2019201583, dated Jul. 15, 2019, 3 pages. |
| Notice of Allowance received for Korean Patent Application No. 10-2016-7014577, dated May 30, 2019, 5 pages (2 pages of English Translation and 3 pages of Official Copy). |
| Office Action received for Australian Patent Application No. 2019100222, dated May 24, 2019, 6 pages. |
| Office Action received for Chinese Patent Application No. 201380081349.6, dated Jul. 15, 2019, 10 pages (5 pages of English Translation and 5 pages of Official copy). |
| Office Action received for Chinese Patent Application No. 201580037927.5, dated Apr. 22, 2019, 9 pages (4 pages of English Translation and 5 pages of Official Copy). |
| Office Action Received for Danish Patent Application No. PA201670656, dated May 2, 2019, 4 pages. |
| Office Action received for Danish Patent Application No. PA201870600, dated May 8, 2019, 3 pages. |
| Office Action received for Danish Patent Application No. PA201870601, dated Jun. 25, 2019, 3 pages. |
| Office Action received for Danish Patent Application No. PA201870602, dated Jun. 26, 2019, 3 Pages. |
| Office Action received for European Patent Application No. 17810749.6, dated Aug. 20, 2019, 9 pages. |
| Office Action received for Japanese Patent Application No. 2018-014096, dated May 8, 2019, 14 pages (7 pages of English Translation and 7 pages of Official Copy). |
| Supplementary European Search Report received for European Patent Application No. 17810749.6, dated Aug. 6, 2019, 6 pages. |
| Advisory Action received for U.S. Appl. No. 16/143,909, dated Nov. 7, 2019, 5 pages. |
| Applicant Initiated Interview Summary received for U.S. Appl. No. 15/627,069, dated Nov. 4, 2019, 6 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 15/600,243, dated Nov. 1, 2019, 6 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 15/608,848, dated Nov. 1, 2019, 3 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/705,849, dated Nov. 12, 2019, 15 pages. |
| Intention to Grant received for Danish Patent Application No. PA201870379, dated May 2, 2019, 2 pages. |
| Decision to Grant received for Danish Patent Application No. PA201870600, dated Oct. 17, 2019, 2 pages. |
| Notice of Allowance received for Chinese Patent Application No. 201580037927.5, dated Oct. 17, 2019, 3 pages (1 page of English Translation and 2 pages of Official Copy). |
| Notice of Allowance received for U.S. Appl. No. 16/143,959, dated Oct. 31, 2019, 10 pages. |
| Office Action received for Australian Patent Application No. 2019222943, dated Oct. 3, 2019, 3 pages. |
| Office Action received for Danish Patent Application No. PA201770191, dated Oct. 25, 2019, 4 pages. |
| Casella Cel Casella, “The Casella dBadge2—World's First Truly Wireless Noise Dosimeter and Airwave App!”, Retrieved from URL: <https://www.youtube.com/watch?v=Xvy2fl3cgYo>, May 27, 2015, 3 pages. |
| Final Office Action received for U.S. Appl. No. 16/143,997, dated Sep. 30, 2019, 16 pages. |
| Final Office Action received for U.S. Appl. No. 16/144,030, dated Oct. 1, 2019, 13 pages. |
| “Fitbit App”, Available online at: <http://web.archive.org/web/20180114083150/https://www.fitbit.com/au/app>, Jan. 14, 2018, 8 pages. |
| Megadepot, “Casella dBadge2 Noise Dosimeter”, Retrieved from URL: <https://www.youtube.com/watch?v=pHiHLiYCD08>, Jun. 12, 2018, 3 pages. |
| Office Action received for Australian Patent Application No. 2019100495, dated Sep. 17, 2019, 7 pages. |
| Office Action received for Chinese Patent Application No. 201810105846.X, dated Aug. 27, 2019, 12 pages (5 pages of English Translation and 7 pages of Official Copy). |
| Studiosixdigital, “Dosimeter”, Retrieved from URL: <https://www.youtube.com/watch?v=CZ4jkgutp3l>, Mar. 3, 2017, 3 pages. |
| Certificate of Examination received for Australian Patent Application No. 2019100222, dated Aug. 29, 2019, 2 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2019/019694, dated Sep. 2, 2019, 17 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2019/024570, dated Aug. 8, 2019, 18 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/144,849, dated Sep. 17, 2019, 9 pages. |
| Decision to Grant received for Danish Patent Application No. PA201870379, dated Jul. 5, 2019, 2 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/418,786, dated Apr. 24, 2020, 16 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/144,849, dated Apr. 17, 2020, 2 pages. |
| Office Action received for Chinese Patent Application No. 201710439448.7, dated Mar. 27, 2020, 13 pages (7 pages of English Translation and 6 pages of Official Copy). |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 15/705,849, dated Feb. 14, 2020, 3 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 14/732,773, dated Feb. 10, 2020, 3 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/143,909, dated Feb. 20, 2020, 3 pages. |
| Final Office Action received for U.S. Appl. No. 16/144,030, dated Feb. 13, 2020, 11 pages. |
| Invitation to Pay Search Fees received for European Patent Application No. 19726205.8, dated Feb. 14, 2020, 5 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/144,735, dated Feb. 19, 2020, 10 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/144,671, dated Feb. 10, 2020, 17 pages. |
| Office Action received for Chinese Patent Application No. 201380081349.6, dated Jan. 16, 2020, 11 pages (6 pages of English Translation and 5 pages of Official Copy). |
| Office Action received for Danish Patent Application No. PA201870602, dated Feb. 5, 2020, 3 pages. |
| Office Action received for Japanese Patent Application No. 2018-014096, dated Jan. 6, 2020, 17 pages (8 pages of English Translation and 9 pages of Official Copy). |
| Corrected Notice of Allowance received for U.S. Appl. No. 15/600,243, dated Mar. 13, 2020, 3 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/143,909, dated Mar. 18, 2020, 3 pages. |
| Final Office Action received for U.S. Appl. No. 15/627,069, dated Mar. 2, 2020, 22 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/138,809, dated Feb. 28, 2020, 22 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/144,753, dated Mar. 5, 2020, 9 pages. |
| Notice of Allowance received for Chinese Patent Application No. 201810105846.X, dated Feb. 18, 2020, 2 pages (1 page of English Translation and 1 page of Official Copy). |
| Notice of Allowance received for U.S. Appl. No. 16/144,849, dated Mar. 6, 2020, 9 pages. |
| Office Action received for Australian Patent Application No. 2019100495, dated Mar. 6, 2020, 3 pages. |
| Office Action received for Danish Patent Application No. PA201870380, dated Mar. 5, 2020, 2 pages. |
| Office Action received for Japanese Patent Application No. 2019-162293, dated Jan. 31, 2020, 8 pages (4 pages of English Translation and 4 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2019-7025538, dated Feb. 17, 2020, 12 pages (6 pages of English Translation and 6 pages of Official Copy). |
| Wesley, “Apple Watch Series 1”, Online available at: http://tool-box.info/blog/archives/1737-unknown.html, May 28, 2015, 5 pages (Official copy only) (See Communication under 37 CFR § 1.98(a) (3)). |
| Youtube, “Apple Watch Series 3”, Online available at: https://www.youtube.com/watch?v=iBPr9gEfkK8, Nov. 21, 2017, 15 pages (Official copy only) (See Communication under 37 CFR § 1.98(a) (3)). |
| Applicant Initiated Interview Summary received for U.S. Appl. No. 16/144,849, dated Jan. 21, 2020, 6 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 15/600,243, dated Feb. 5, 2020, 3 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/608,848, dated Feb. 6, 2020, 12 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/143,909, dated Jan. 21, 2020, 9 pages. |
| Office Action received for Danish Patent Application No. PA201870601, dated Jan. 14, 2020, 3 pages. |
| Applicant Initiated Interview Summary received for U.S. Appl. No. 15/608,848, dated May 12, 2020, 5 pages. |
| Final Office Action received for U.S. Appl. No. 15/705,849, dated May 1, 2020, 17 pages. |
| Final Office Action received for U.S. Appl. No. 16/144,735, dated May 4, 2020, 12 pages. |
| Intention to Grant received for Danish Patent Application No. PA201870601, dated Apr. 24, 2020, 2 pages. |
| Intention to Grant received for Danish Patent Application No. PA201870602, dated Apr. 24, 2020, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 14/732,773, dated Mar. 24, 2020, 3 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 15/600,243, dated Mar. 31, 2020, 5 pages. |
| Office Action received for Australian Patent Application No. 2019100495, date Mar. 16, 2020, 3 pages. |
| Supplemental Notice of Allowance received for U.S. Appl. No. 16/144,849, dated Mar. 31, 2020, 2 pages. |
| Office Action received for European Patent Application No. 19721883.7, dated May 28, 2020, 11 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2018/031662, dated Sep. 27, 2018, 19 pages. |
| Invitation to Pay Addition Fees and Partial International Search Report received for PCT Patent Application No. PCT/US2018/031662, dated Jul. 16, 2018, 13 pages. |
| Office Action received for Australian Patent Application No. 2018200428, dated Nov. 15, 2018, 4 pages. |
| Office Action received for Japanese Patent Application No. 2016-557650, dated Nov. 9, 2018, 6 pages (3 pages of English Translation and 3 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2016-7014577, dated Oct. 31, 2018, 11 pages (5 pages of English Translation and 6 pages of Official Copy). |
| Cho, H. S., Satisfactory Innovative Smart-watch (fitbit force) . . . review after seven days of use, such as the amount of sleep and movement (improving sleep is the. |
| Object of X-Blue, Online Available at: http://x-blueuv.blogspot.com/2013/12/fitbit-force.html, Dec. 3, 2013, 6 pages (Official Copy Only). |
| Notice of Acceptance received for Australian Patent Application No. 2019222943, dated May 5, 2020, 3 pages. |
| Advisory Action received for U.S. Appl. No. 16/143,997, dated Dec. 26, 2019, 7 pages. |
| Office Action received for Chinese Patent Application No. 201810105846.X, dated Nov. 28, 2019, 9 pages (5 pages of English Translation and 4 pages of Official Copy). |
| Office Action received for Danish Patent Application No. PA201870378, dated Jan. 6, 2020, 3 pages. |
| Office Action received for Danish Patent Application No. PA201870599, dated Dec. 20, 2019, 5 pages. |
| Office Action received for European Patent Application No. 16837432.0, dated Jan. 10, 2020, 7 pages. |
| Office Action received for European Patent Application No. 19721883.7, dated Jan. 10, 2020, 4 pages. |
| Advisory Action received for U.S. Appl. No. 14/839,922, dated Mar. 24, 2017, 4 pages. |
| Advisory Action received for U.S. Appl. No. 14/732,773, dated Nov. 9, 2018, 3 pages. |
| Apple, “iPhone User's Guide”, Available at: http://mesnotices.20minutes.fr/manuel-notice-mode-emploi/APPLE/IPHONE%2D%5FE#, Retrieved on Mar. 27, 2008, Jun. 2007, 137 pages. |
| Certification of Examination received for Australian Patent Application No. 2018100158, dated Oct. 23, 2018, 2 pages. |
| Codrington, Simon, “Intuitive Scrolling Interfaces with CSS Scroll Snap Points”, Online Available at: https://www.sitepoint.com/intuitive-scrolling-interfaces-with-css-scroll-snap-points/, Dec. 8, 2015, 14 pages. |
| CNET, “Google Fits 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. |
| Decision to Refuse received for European Patent Application No. 13811085.3, dated Sep. 11, 2018, 21 pages. |
| Decision to Refuse received for European Patent Application No. 15771747.1, dated Aug. 10, 2018, 22 pages. |
| “DwProgressBar v2: Stepping and Events”, davidwalsh.name/dwprogressbar-2-stepping-events-mootools-progress-bar, retrieved from the Wayback Machine, Aug. 31, 2008, 4 pages. |
| Extended European Search Report received for European Patent Application No. 18154145.9, dated Mar. 2, 2018, 8 pages. |
| Final Office Action received for U.S. Appl. No. 12/205,847, dated Apr. 25, 2012, 42 pages. |
| Final Office Action received for U.S. Appl. No. 14/732,773, dated Jul. 13, 2018, 48 pages. |
| Final Office Action received for U.S. Appl. No. 14/839,922, dated Dec. 14, 2016, 22 pages. |
| “Garmin Fenix 5 Activity/Smart Watch Review”, Ian Smith, Online Available at: https://www.youtube.com/watch?v=6PkQxXQxpoU, Sep. 2, 2017, 1 page. |
| “Garmin Fenix 5 Open Water Swimming Activity Demo”, zlelik, Online Available at: https://www.youtube.com/watch?v=iSVhdvw2dcs, Jun. 9, 2017, 1 page. |
| “Garmin Fenix 5: How to Add Power Data Fields”, ALF, Online Available at: https://www.youtube.com/watch?v=ZkPptnnXEiQ, Apr. 29, 2017, 1 page. |
| “Garmin Fenix 5: How to Set Up Run Alerts”, ALF, Online Available at: https://www.youtube.com/watch?v=gSMwv8vlhB4, May 13, 2017, 1 page. |
| “Garmin Fenix 5x Owners Manual”, Online Available at: https://web.archive.org/web/20180127170640/https://static.garmin.com/pumac/fenix5x_OM_EN.pdf, Jan. 27, 2018, 42 pages. |
| Intention to Grant received for Danish Patent Application No. PA201570668, dated Mar. 27, 2017, 2 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2016/037686, dated Mar. 1, 2018, 12 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2013/073195, dated Jun. 7, 2016, 9 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2015/047282, dated Mar. 16, 2017, 26 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2015/047282, dated May 9, 2016, 33 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2016/037686, dated Sep. 9, 2016, 19 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2017/035554, dated Sep. 22, 2017, 42 pages. |
| International Search Report received for PCT Patent Application No. PCT/US2013/073195, dated Jun. 23, 2014, 3 pages. |
| International Written Opinion received for PCT Patent Application No. PCT/US2013/073195, dated Jun. 23, 2014, 8 pages. |
| Invitation to Pay Additional Fees received for PCT Patent Application No. PCT/US2015/047282, dated Dec. 22, 2015, 7 pages. |
| Invitation to Pay Additional Fees received for PCT Patent Application No. PCT/US2017/035554, dated Jul. 20, 2017, 2 pages. |
| JENBSJOURNEY, “Wondering About a Fitbit?”, Available at: https://jenbsjourney.blogspot.kr/2013/08/wondering-about-fitbit.html, Aug. 6, 2013, 12 pages. |
| Minutes of Oral Proceedings received for European Patent Application No. 13811085.3, mailed on Sep. 11, 2018, 3 pages. |
| Minutes of Oral Proceedings received for European Patent Application No. 15771747.1, mailed on Aug. 10, 2018, 11 pages. |
| “Mugs”, Online Available at: https://web.archive.org/web/20151029034349/http://le-mugs.com/, Oct. 29, 2015. |
| “My CalStep”, http://www.surprisesoftware.com/mycalstep/, retireved from the Wayback Machine, May 9, 2007, 2 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/608,848, dated Nov. 2, 2018, 21 pages. |
| Non-Final Office Action received for U.S. Appl. No. 12/205,847, dated Oct. 3, 2011, 59 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/732,773, dated Jan. 19, 2018, 45 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/839,916, dated Feb. 4, 2016, 19 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/839,916, dated May 1, 2017, 18 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/839,922, dated Aug. 17, 2016, 25 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/839,922, dated Feb. 25, 2016, 20 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/183,663, dated Jul. 9, 2018, 13 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2015312215, dated Oct. 9, 2017, 3 pages. |
| Notice of Allowance received for Danish Patent Application No. PA201570666, dated Sep. 15, 2016, 1 page. |
| Notice of Allowance received for Danish Patent Application No. PA201570668, dated Oct. 30, 2017, 2 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2016-535045, dated Mar. 2, 2018, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for Korean Patent Application No. 10-2016-7033638, dated May 31, 2017, 5 pages (2 pages of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for Taiwanese Patent Application No. 104128685, dated May 3, 2017, 3 pages (Official Copy only) (see attached 37 CFR § 1.98(a) (3)). |
| Notice of Allowance received for U.S. Appl. No. 12/205,847, dated Aug. 20, 2012, 13 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/839,916, dated Aug. 31, 2016, 11 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/839,916, dated Jan. 10, 2018, 19 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/839,922, dated Jan. 26, 2018, 2 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/839,922, dated Jul. 6, 2017, 8 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/839,922, dated Nov. 2, 2017, 8 pages. |
| Office Action received for Australian Patent Application No. 2015312215, dated Oct. 13, 2016, 3 pages. |
| Office Action received for Australian Patent Application No. 2017100667, dated Aug. 3, 2017, 9 pages. |
| Office Action received for Australian Patent Application No. 2018100158, dated Apr. 23, 2018, 5 pages. |
| Office Action received for Australian Patent Application No. 2018200428, dated Mar. 7, 2018, 4 pages. |
| Office Action received for Chinese Patent Application No. 201580037927.5, dated Jul. 20, 2018, 21 pages (6 pages of English Translation and 15 pages of Official Copy). |
| Office Action received for Danish Patent Application No. PA201570666, dated Feb. 2, 2016, 9 pages. |
| Office Action received for Danish Patent Application No. PA201570666, dated Jun. 27, 2016, 4 pages. |
| Office Action received for Danish Patent Application No. PA201570668, dated Apr. 8, 2016, 8 pages. |
| Office Action received for Danish Patent Application No. PA201570668, dated Sep. 9, 2016, 3 pages. |
| Office Action received for Danish Patent Application No. PA201670656, dated Jun. 14, 2017, 3 pages. |
| Office Action received for Danish Patent Application No. PA201670656, dated May 30, 2018, 5 pages. |
| Office Action received for Danish Patent Application No. PA201670656, dated Nov. 3, 2016, 8 pages. |
| Office Action received for Danish Patent Application No. PA201770191, dated Jan. 25, 2018, 3 pages. |
| Office Action received for Danish Patent Application No. PA201770423, dated Jun. 12, 2018, 7 pages. |
| Office Action received for Danish Patent Application No. PA201870380, dated Sep. 11, 2018, 9 pages. |
| Office Action received for European Patent Application No. 13811085.3, dated Apr. 20, 2018, 15 pages. |
| Office Action received for European Patent Application No. 15771747.1, dated Oct. 31, 2017, 7 pages. |
| Office Action received for European Patent Application No. 18154145.9, dated Apr. 3, 2018, 6 pages. |
| Office Action received for Japanese Patent Application No. 2016-535045, dated May 12, 2017, 10 pages (5 pages of English Translation and 5 pages of Official Copy). |
| Office Action received for Japanese Patent Application No. 2016-557650, dated Apr. 13, 2018, 9 pages (5 pages of English Translation and 4 pages of Official Copy). |
| Office Action received for Japanese Patent Application No. 2016-557650, dated Aug. 10, 2017, 10 pages (5 pages of English Translation and 5 pages of Official Copy). |
| Office Action received for Japanese Patent Application No. 2018-014096, dated Jun. 29, 2018, 20 pages (11 pages of English Translation and 9 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2016-7014577, dated Dec. 26, 2017, 14 pages (6 pages of English Translation and 8 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2016-7033638, dated Jan. 31, 2017, 6 pages (2 pages of English Translation and 4 pages of Official Copy). |
| Office Action received for Taiwanese Patent Application No. 104128685, dated Jan. 4, 2017, 40 pages (15 pages of English Translation and 25 pages of Official Copy). |
| Rainmaker, “Garmin Fenix3 New Auto Climb Functionality”, Available online at: https://www.youtube.com/watch?v=iuavOSNpVRc, Feb. 19, 2015, 1 page. |
| Razykdreviews, “In Depth Review of Apple Watch Activity and Workout App”, available at: URL: https://www.youtube.com/watch?v=GkKl3qlK0ow, May 11, 2015, 1 page. |
| Rizknows, “Garmin Connect Mobile App—Review #2”, https://www.youtube.com/watch?v=7my3wMpeRbE, Oct. 22, 2015, 1 page. |
| Search Report and Opinion received for Danish Patent Application No. PA201870378, dated Sep. 10, 2018, 9 pages. |
| Search Report and Opinion received for Danish Patent Application No. PA201870379, dated Sep. 14, 2018, 9 pages. |
| Search Report and Opinion received for Danish Patent Application No. PA201770191, dated Jun. 30, 2017, 9 pages. |
| Search Report and Opinion received for Danish Patent Application No. PA201770423, dated Oct. 4, 2017, 10 pages. |
| Summons to Attend oral proceedings received for European Patent Application No. 13811085.3, mailed on Jan. 26, 2018, 14 pages. |
| Summons to Attend Oral Proceedings received for European Patent Application No. 15771747.1, mailed on May 25, 2018, 17 pages. |
| “Suunto Spartan—Heart Rate Zones”, 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. 27, 2018, 47 pages. |
| “Suunto Spartan—Heart Rate Zones”, Suunto, Online Available at: https://www.youtube.com/watch?v=aixfoCnS0OU, Mar. 19, 2018, 1 page. |
| “Tom Tom Multisport Cardio Review”, Rizknows, Online available at: https://www.youtube.com/watch?v=WoVCzLrSN9A, Sep. 4, 2015, 1 page. |
| “TomTom Runner & Multi-Sport Reference Guide”, TomTom, Online available at:—https://web.archive.ong/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. |
| “Utilization of Galaxy S4-S Health, ChatOn and Samsung Hub”, Available at: http://seeit.kr/1263, Jun. 12, 2013, 25 pages (Official Copy only) (see attached 37 CFR § 1.98(a) (3)). |
| Office Action received for Korean Patent Application No. 10-2019-7025538, dated Aug. 15, 2020, 8 pages (4 pages of English Translation and 4 pages of Official Copy). |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/138,809, dated Dec. 16, 2020, 7 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/880,552, dated Dec. 16, 2020, 6 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/907,261, dated Dec. 16, 2020, 6 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/880,552, dated Dec. 23, 2020, 2 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/586,154, dated Dec. 28, 2020, 26 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/031,874, dated Dec. 28, 2020, 14 pages. |
| Result of Consultation received for European Patent Application No. 17810749.6, dated Dec. 15, 2020, 3 pages. |
| Search Report and Opinion received for Danish Patent Application No. PA202070620, dated Dec. 11, 2020, 9 pages. |
| Office Action received for Chinese Patent Application No. 201910858933.7, dated Aug. 18, 2020, 14 pages (7 pages of English Translation and 7 pages of Official Copy). |
| Office Action received for Japanese Patent Application No. 2019-162293, dated Jul. 27, 2020, 9 pages (5 pages of English Translation and 4 pages of Official Copy). |
| Final Office Action received for U.S. Appl. No. 16/418,786, dated Jan. 13, 2021, 14 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2018268972, dated Dec. 18, 2020, 3 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2018-014096, dated Jan. 5, 2021, 3 pages (1 page of English Translation and 2 pages of Official Copy). |
| Notice of Allowance received for Japanese Patent Application No. 2020-104679, dated Jan. 4, 2021, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for U.S. Appl. No. 16/556,023, dated Jan. 13, 2021, 8 pages. |
| Search Report and Opinion received for Danish Patent Application No. PA202070614, dated Jan. 14, 2021, 9 pages. |
| Supplemental Notice of Allowance received for U.S. Appl. No. 15/925,652, dated Jan. 6, 2021, 2 pages. |
| Applicant Initiated Interview Summary received for U.S. Appl. No. 15/608,848, dated Oct. 26, 2020, 3 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 15/925,652, dated Nov. 3, 2020, 4 pages. |
| European Search Report received for European Patent Application No. 20182116.2, dated Oct. 21, 2020, 4 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/144,735, dated Oct. 28, 2020, 13 pages. |
| Office Action received for Japanese Patent Application No. 2020-104679, dated Sep. 18, 2020, 13 pages (7 pages of English Translation and 6 pages of Official copy). |
| Summons to Attend Oral Proceedings received for European Patent Application No. 19726205.8, mailed on Oct. 29, 2020, 13 pages. |
| Chatrzarrin Hanieh, “Feature Extraction for the Differentiation of Dry and Wet Cough Sounds”, Carleton University, Sep. 2011, 144 pages. |
| Haslam Oliver, “Stop Coronavirus in its Tracts by Using This Apple Watch App to Time Hand Washes”, Available Online at: <http://www.imore.com/stop-coronavirus-its-tracks-using-apple-watch-app-time-washes>, Mar. 12, 2020, 12 pages. |
| Liaqat et al., “Challenges with Real World Smartwatch based Audio Monitoring”WearSys'18, Munich, Germany, Available Online at: <http://doi.org/10.1145/3211960.3211977>, Jun. 10, 2018, 6 pages. |
| Lyles Taylor, “Wear OS Smartwatches are Now Sending Reminders to Wash Your Hands”, Available Online at: <http://www.theverge.com/2020/4/14/1221294/google-wear-os-smartwatches-reminders-wash-your-hands>Apr. 14, 2020, 2 pages. |
| Peters Jay “Samsung's Smartwatches Get a Hand-Washing Reminder and Timer App”, Available Online at: <http://www.theverge.com/2020/4/17/21225205/samsung-smartwatch-galaxy-active-hand-washing-timer-reminder-app>, Apr. 17, 2020, 2 pages. |
| Schoon Ben, “Wear OS Now Sends a Reminder to Wash Your Hands Every Few Hours”, Available Online at: <http://9to5google.com/2020/04/14/wear-os-wash-hands-reminder-coronavirus/>, Apr. 14, 2020, 7 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/377,892, dated Oct. 13, 2020, 5 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/378,136, dated Oct. 13, 2020, 4 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/880,552, dated Oct. 20, 2020, 6 pages. |
| Final Office Action received for U.S. Appl. No. 15/627,069, dated Oct. 20, 2020, 25 pages. |
| Invitation to Pay Additional Fees received for PCT Patent Application No. PCT/US2020/035474, dated Oct. 2, 2020, 11 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/894,309, dated Oct. 15, 2020, 24 pages. |
| Notice of Allowance received for U.S. Appl. No. 15/705,849, dated Oct. 16, 2020, 14 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/556,023, dated Oct. 15, 2020, 8 pages. |
| Result of Consultation received for European Patent Application No. 19721883.7, dated Oct. 7, 2020, 3 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/586,154, dated Dec. 11, 2020, 5 pages. |
| Board Decision received for Chinese Patent Application No. 201380081349.6, dated Nov. 23, 2020, 2 pages (1 page of English Translation and 1 page of Official Copy). |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2020/035474, dated Nov. 26, 2020, 16 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/820,383, dated Dec. 14, 2020, 11 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/031,859, dated Dec. 15, 2020, 13 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/144,753, dated Dec. 4, 2020, 22 pages. |
| Search Report and Opinion received for Danish Patent Application No. PA2020070335, dated Nov. 27, 20200, 10 pages. |
| Search Report and Opinion received for Danish Patent Application No. PA202070395, dated Nov. 24, 2020, 10 pages. |
| Gupta Rajat, “Disable High Volume Warning (no root) in Samsung S7, S8/Android 7.0”, Online available at: <http://www.youtube.com/watch<v=9fKwRBtk0x8>, Retrieved on Nov. 26, 2020; esp. 2:04, Aug. 6, 2017, 1 page. |
| Kalyani Tech., “I see Some problems in Honor Band 5”, Retrieved from: http://www.youtube.com/watch?v=5XPnYJFqajl, May 19, 2020, 1 page. |
| Smartwatch Ticks, “Senbono S10 IP67 Waterproof Multi-Function Blood Pressure Sports Smartwatch: One Minute Overview”, Retrieved from: https://www.youtube.com/watch?v=rMxLJvKIVBs, Oct. 30, 2019, 1 page. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/144,753, dated Nov. 4, 2020, 3 pages. |
| Bagala et al., “Evaluation of Accelerometer-Based Fall Detection Algorithms on Real-World Falls”, PloS One, vol. 7, No. 5, May 16, 2012, 9 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/144,030, dated Nov. 5, 2020, 5 pages. |
| Office Action received for Australian Patent Application No. 2019234289, dated Nov. 2, 2020, 6 pages. |
| Office Action received for Australian Patent Application No. 2020230340, dated Nov. 2, 2020, 5 pages. |
| Office Action received for European Patent Application No. 20182116.2, dated Nov. 6, 2020, 9 pages. |
| Office Action received for Korean Patent Application No. 10-2019-7025781, dated Oct. 30, 2020, 10 pages (4 pages of English Translation and 6 pages of Official Copy). |
| Applicant Initiated Interview Summary received for U.S. Appl. No. 16/586,154, dated Mar. 11, 2020, 4 pages. |
| Final Office Action received for U.S. Appl. No. 16/586,154, dated Jul. 6, 2020, 27 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2019/024570, dated Nov. 19, 2020, 10 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2020/035199, dated Oct. 30, 2020, 20 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2020/035462, dated Sep. 11, 2020, 17 pages. |
| Invitation to Pay Additional Fees and Partial International Search Report received for PCT Patent Application No. PCT/US2020/035164, dated Oct. 16, 2020, 14 pages. |
| Invitation to Pay Additional Fees received for PCT Patent Application No. PCT/US2020/035199, dated Sep. 8, 2020, 12 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/586,154, dated Dec. 9, 2019, 23 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/880,714, dated Oct. 28, 2020, 11 pages. |
| Notice of Allowance received for U.S. Appl. No. 15/925,652, dated Nov. 20, 2020, 9 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/880,552, dated Dec. 1, 2020, 7 pages. |
| Office Action received for Chinese Patent Application No. 201710439448.7, dated Oct. 10, 2020, 19 pages (8 pages of English Translation and 11 pages of Official Copy). |
| Result of Consultation received for European Patent Application No. 18154145.9, dated Nov. 30, 2020, 17 pages. |
| Applicant Initiated Interview Summary received for U.S. Appl. No. 16/143,997, dated Aug. 13, 2020, 3 pages. |
| Applicant Initiated Interview Summary received for U.S. Appl. No. 16/144,735, dated Jun. 18, 2020, 3 pages. |
| Applicant Initiated Interview Summary received for U.S. Appl. No. 16/144,753, dated Jun. 18, 2020, 3 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 15/627,069, dated Jul. 20, 2020, 5 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 15/705,849, dated Jun. 29, 2020, 3 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/138,809, dated Jun. 9, 2020, 4 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/584,186, dated Feb. 3, 2020, 4 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/584,186, dated Jul. 31, 2020, 2 pages. |
| Decision to Grant received for Danish Patent Application No. PA201870601, dated Aug. 17, 2020, 2 pages. |
| Decision to Grant received for Danish Patent Application No. PA201870602, dated Aug. 18, 2020, 2 pages. |
| Extended European Search Report received for European Patent Application No. 20180581.9, dated Aug. 12, 2020, 9 pages. |
| Extended European Search Report received for European Patent Application No. 20180592.6, dated Aug. 11, 2020, 10 pages. |
| Final Office Action received for U.S. Appl. No. 15/608,848, dated Aug. 21, 2020, 15 pages. |
| Final Office Action received for U.S. Appl. No. 16/138,809, dated Aug. 27, 2020, 24 pages. |
| Final Office Action received for U.S. Appl. No. 16/144,753, dated Sep. 22, 2020, 9 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2019/019694, dated Sep. 24, 2020, 12 pages. |
| International Search Report and written Opinion received for PCT Patent Application No. PCT/US2020/025768, dated Aug. 10, 2020, 11 pages. |
| International Search Report and written Opinion received for PCT Patent Application No. PCT/US2020/025997, dated Jul. 1, 2020, 16 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2020/025997, dated Jul. 14, 2020, 15 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/627,069, dated May 26, 2020, 25 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/925,652, dated Aug. 7, 2020, 39 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/143,997, dated Jul. 27, 2020, 15 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/377,892, dated May 21, 2020, 9 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/378,136, dated Jun. 2, 2020, 8 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/584,186, dated Dec. 6, 2019, 13 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/880,552, dated Jul. 23, 2020, 19 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/907,261, dated Sep. 30, 2020, 22 pages. |
| Notice of Allowance received for Chinese Patent Application No. 201910972529.2, dated Sep. 14, 2020, 6 pages (3 pages of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for U.S. Appl. No. 15/705,849, dated Jul. 28, 2020, 10 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/144,735, dated Jul. 21, 2020, 13 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/584,186, dated Mar. 24, 2020, 10 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/588,950, dated Feb. 10, 2020, 9 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/588,950, dated May 5, 2020, 9 pages. |
| Office Action received for Australian Patent Application No. 2017277971, dated Aug. 12, 2020, 3 pages. |
| Office Action received for Australian Patent Application No. 2017277971, dated Jun. 3, 2020, 3 pages. |
| Office Action received for Australian Patent Application No. 2018268972, dated Jul. 9, 2020, 4 pages. |
| Office Action received for Australian Patent Application No. 2019250251, dated Aug. 6, 2020, 3 pages. |
| Office Action received for Chinese Patent Application No. 201380081349.6, dated Jul. 15, 2020, 9 pages (4 pages of English Translation and 5 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 201680047983.1, dated Jul. 1, 2020, 6 pages (3 pages of English Translation and 3 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 201910972529.2, dated Jun. 28, 2020, 8 pages (1 page of English Translation and 7 pages of Official Copy). |
| Office Action Received for Danish Patent Application No. PA201670656, dated Jul. 1, 2020, 4 pages. |
| Office Action received for Danish Patent Application No. PA201970532, dated May 29, 2020, 3 pages. |
| Office Action received for Danish Patent Application No. PA201970534, dated Jun. 29, 2020, 2 pages. |
| Office Action received for European Patent Application No. 19726205.8, dated Jun. 26, 2020, 9 pages. |
| Office Action received for Japanese Patent Application No. 2018-014096, dated Aug. 28, 2020, 4 pages (2 pages of English Translation and 2 pages of Official Copy). |
| Office Action received for Japanese Patent Application No. 2019-044107, dated May 29, 2020, 6 pages (3 pages of English Translation and 3 pages of Official Copy). |
| Result of Consultation received for European Patent Application No. 18154145.9, dated Sep. 4, 2020, 3 pages. |
| Search Report and Opinion received for Danish Patent Application No. PA201970532, dated Nov. 8, 2019, 9 pages. |
| Search Report and Opinion received for Danish Patent Application No. PA201970534, dated Sep. 23, 2019, 6 pages. |
| Summons to Attend Oral Proceedings received for European Patent Application No. 17810749.6, mailed on Aug. 12, 2020, 11 pages. |
| Summons to Attend Oral Proceedings received for European Patent Application No. 18154145.9, mailed on Sep. 17, 2020, 11 pages. |
| Supplemental Notice of Allowance received for U.S. Appl. No. 16/588,950, dated Apr. 1, 2020, 2 pages. |
| Supplemental Notice of Allowance received for U.S. Appl. No. 16/588,950, dated Jul. 29, 2020, 2 pages. |
| Supplemental Notice of Allowance received for U.S. Appl. No. 16/588,950, dated Jun. 18, 2020, 2 pages. |
| Cyclespeed Tours, “The Most Useful Data Fields to Display on Your Garmin”, Online. Available at: https://www.youtube.com/watch?v=AN0Eo50yxdg, Nov. 16, 2016, 3 pages. |
| Epstein et al., “Examining Menstrual Tracking to Inform the Design of Personal Informatics Tools”, Proceedings of the 2017 CHI Conference on Human Factors in Computing Systems, CHI'17, ACM Press, Denver, CO, USA, May 6-11, 2017, pp. 6876-6888. |
| Moglia et al., “Evaluation of Smartphone Menstrual Cycle Tracking Applications Using an Adapted Applications Scoring System”, Obstetrics and Gynecology, vol. 127. No. 6, Jun. 2016, pp. 1153-1160. |
| Office Action received for Korean Patent Application No. 10-2020-7026035, dated Feb. 19, 2021, 13 pages (6 pages of English Translation and 7 pages of Official Copy). |
| Applicant Initiated Interview Summary received for U.S. Appl. No. 16/894,309, dated Jan. 26, 2021, 3 pages. |
| Adeniyi Samuel, “How to connect a second PS4 controller to a PlayStation 4 console”, Online available on:—https://www.youtube.com/watch?v=mOZX_SrNISE, May 28, 2017, 2 pages. |
| Allison Conor, “Working out with Fiit's wearable-powered boutique fitness classes”, Online available at: <https://www.wareable.com/wearable-tech/fiit-fitness-classes-review3849>, May 14, 2018, 8 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 15/627,069, dated Jan. 22, 2021, 4 pages. |
| Decision to Refuse received for European Patent Application No. 17810749.6, dated Jan. 29, 2021, 24 pages. |
| Extended European Search Report received for European Patent Application No. 20203526.7, dated Jan. 29, 2021, 13 pages. |
| Final Office Action received for U.S. Appl. No. 16/377,892, dated Jan. 28, 2021, 11 pages. |
| Final Office Action received for U.S. Appl. No. 16/378,136, dated Jan. 28, 2021, 9 pages. |
| Hamilton Jim, “Peloton Tips”, Online available on:—<https://www.youtube.com/watch?app=desktop&v=OneXtB0kaD4>, Oct. 22, 2015, 3 pages. |
| Intention to Grant received for Danish Patent Application No. PA201670656, dated Jan. 18, 2021, 2 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. |
| Minutes of the Oral Proceedings received for European Patent Application No. 17810749.6, dated Jan. 26, 2021, 8 pages. |
| Notice of Allowance received for Chinese Patent Application No. 201710439448.7, dated Jan. 26, 2021, 2 pages (1 page of English Translation and 1 page of Official Copy). |
| Office Action received for European Patent Application No. 16837432.0, dated Jan. 27, 2021, 7 pages. |
| Office Action received for Japanese Patent Application No. 2020-000492, dated Dec. 11, 2020, 6 pages (3 pages English Translation and 3 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2019-7033834, dated Jan. 22, 2021, 13 pages (6 pages of English Translation and 7 pages of Official Copy). |
| Result of Consultation received for European Patent Application No. 17810749.6, dated Jan. 18, 2021, 3 pages. |
| Result of Consultation received for European Patent Application No. 17810749.6, dated Jan. 21, 2021, 18 pages. |
| Supplemental Notice of Allowance received for U.S. Appl. No. 15/925,652, dated Jan. 26, 2021, 3 pages. |
| Supplemental Notice of Allowance received for U.S. Appl. No. 16/556,023, dated Feb. 3, 2021, 2 pages. |
| Vicky'S Blog, “How to Log in to PS4 Automatically with Particular User?”, Online available on:—https://www.youtube.com/watch?v=kqdlzXAvOkY, May 30, 2018, 3 pages. |
| Yoyodavid, “How to Use Multiple Accounts on the PlayStation 4”, Online available at:—https://www.youtube.com/watch?v=5V2lobRMeKE, Jan. 9, 2014, 3 pages. |
| Number | Date | Country | |
|---|---|---|---|
| 20190336045 A1 | Nov 2019 | US |
| Number | Date | Country | |
|---|---|---|---|
| 62679906 | Jun 2018 | US | |
| 62668159 | May 2018 | US |
