Patent Grant
11439324
The following disclosure relates generally to a computer user interfaces and, more specifically, to techniques and devices for presenting workout monitor interfaces.
Whether an individual is exercises for health or competition, the effectiveness of exercise can be improved with real-time feedback of performance and physiological attributes associated with the exercise. For example, data about an individual's heartrate can help the individual determine whether they are in the target heartrate zone for a desired level of activity or whether the individual is over or under exerting themselves. Additionally, performance during exercise can help motivate and track and individual's progress, which aids in reaching goals or even just maintaining a healthy level of exercise.
Some techniques for presenting workout monitor interfaces using electronic devices, however, are generally cumbersome and inefficient. For example, some existing techniques use a complex and time-consuming user interface, which may include multiple key presses, keystrokes, or other user inputs. 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 workout monitoring. Such methods and interfaces optionally complement or replace other methods for workout monitoring. Such methods and interfaces reduce the cognitive burden on a user and produce a more efficient human-machine interface. For battery-operated computing devices, such methods and interfaces conserve power and increase the time between battery charges.
The present disclosure relates to systems and processes for monitoring a workout and for generating improved interfaces for the same. One example user interface detects when a workout of a particular type is started and begins generating activity data related to workout metrics associated with the type of workout selected. Using determined current values for the workout metrics, the example user interface displays a pro-view (“professional” view) display that includes indicators for the workout metrics associated with the selected workout type. The pro-view display also includes a focus indicator that highlights a selected indicator representative of a focused workout metric. The focus indicator is movable among the indicators representative of the workout metrics based on user input. Upon detection of a gesture, the example user interface transitions to a simple-view display that includes an indicator representative of the focused workout metric. The simple-view display includes indicators for less than all of the workout metrics associated with the selected workout type. The example user interface receives input to change the focused workout metric in the simple-view display. The example user interface also receives a gesture to transition the simple-view display back to the pro-view display.
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 workout monitoring, thereby increasing the effectiveness, efficiency, and user satisfaction with such devices. Such methods and interfaces may complement or replace other methods for monitoring workouts.
For a better understanding of the various described embodiments, reference should be made to the Description of Embodiments below, in conjunction with the following drawings in which like reference numerals refer to corresponding parts throughout the figures.
The following description sets forth exemplary methods, parameters and the like. It should be recognized, however, that such description is not intended as a limitation on the scope of the present disclosure but is instead provided as a description of exemplary embodiments.
There is a need for electronic devices that provide efficient methods and interfaces for workout monitoring. Such techniques can reduce the cognitive burden on a user who accesses workout information, thereby enhancing productivity. Further, such techniques can reduce processor and battery power otherwise wasted on redundant user inputs.
Although the following description uses terms first, second, etc. to describe various elements, these elements should not be limited by the terms. These terms are only used to distinguish one element from another. For example, a first touch could be termed a second touch, and, similarly, a second touch could be termed a first touch, without departing from the scope of the various described embodiments. The first touch and the second touch are both touches, but they are not the same touch.
Below,
Although the following description uses terms “first,” “second,” etc. to describe various elements, these elements should not be limited by the terms. These terms are only used to distinguish one element from another. For example, a first touch could be termed a second touch, and, similarly, a second touch could be termed a first touch, without departing from the scope of the various described embodiments. The first touch and the second touch are both touches, but they are not the same touch.
The terminology used in the description of the various described embodiments herein is for the purpose of describing particular embodiments only and is not intended to be limiting. As used in the description of the various described embodiments and the appended claims, the singular forms “a,” “an,” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will also be understood that the term “and/or” as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items. It will be further understood that the terms “includes,” “including,” “comprises,” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
The term “if” is, optionally, construed to mean “when” or “upon” or “in response to determining” or “in response to detecting,” depending on the context. Similarly, the phrase “if it is determined” or “if [a stated condition or event] is detected” is, optionally, construed to mean “upon determining” or “in response to determining” or “upon detecting [the stated condition or event]” or “in response to detecting [the stated condition or event],” depending on the context.
Embodiments of electronic devices, user interfaces for such devices, and associated processes for using such devices are described. In some embodiments, the device is a portable communications device, such as a mobile telephone, that also contains other functions, such as PDA and/or music player functions. Exemplary embodiments of portable multifunction devices include, without limitation, the iPhone®, iPod Touch®, and iPad® devices from Apple Inc. of Cupertino, 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 embodiments, the device is not a portable communications device, but is a desktop computer with a touch-sensitive surface (e.g., a touch screen display and/or a touchpad).
In the discussion that follows, an electronic device that includes a display and a touch-sensitive surface is described. It should be understood, however, that the electronic device optionally includes one or more other physical user-interface devices, such as a physical keyboard, a mouse, and/or a joystick.
The device typically supports a variety of applications, such as one or more of the following: a drawing application, a presentation application, a word processing application, a website creation application, a disk authoring application, a spreadsheet application, a gaming application, a telephone application, a video conferencing application, an e-mail application, an instant messaging application, a workout support application, a photo management application, a digital camera application, a digital video camera application, a web browsing application, a digital music player application, and/or a digital video player application.
The various applications that are executed on the device optionally use at least one common physical user-interface device, such as the touch-sensitive surface. One or more functions of the touch-sensitive surface as well as corresponding information displayed on the device are, optionally, adjusted and/or varied from one application to the next and/or within a respective application. In this way, a common physical architecture (such as the touch-sensitive surface) of the device optionally supports the variety of applications with user interfaces that are intuitive and transparent to the user.
Attention is now directed toward embodiments of portable devices with touch-sensitive displays.
As used in the specification and claims, the term “intensity” of a contact on a touch-sensitive surface refers to the force or pressure (force per unit area) of a contact (e.g., a finger contact) on the touch-sensitive surface, or to a substitute (proxy) for the force or pressure of a contact on the touch-sensitive surface. The intensity of a contact has a range of values that includes at least four distinct values and more typically includes hundreds of distinct values (e.g., at least 256). Intensity of a contact is, optionally, determined (or measured) using various approaches and various sensors or combinations of sensors. For example, one or more force sensors underneath or adjacent to the touch-sensitive surface are, optionally, used to measure force at various points on the touch-sensitive surface. In some implementations, force measurements from multiple force sensors are combined (e.g., a weighted average) to determine an estimated force of a contact. Similarly, a pressure-sensitive tip of a stylus is, optionally, used to determine a pressure of the stylus on the touch-sensitive surface. Alternatively, the size of the contact area detected on the touch-sensitive surface and/or changes thereto, the capacitance of the touch-sensitive surface proximate to the contact and/or changes thereto, and/or the resistance of the touch-sensitive surface proximate to the contact and/or changes thereto are, optionally, used as a substitute for the force or pressure of the contact on the touch-sensitive surface. In some implementations, the substitute measurements for contact force or pressure are used directly to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is described in units corresponding to the substitute measurements). In some implementations, the substitute measurements for contact force or pressure are converted to an estimated force or pressure, and the estimated force or pressure is used to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is a pressure threshold measured in units of pressure). Using the intensity of a contact as an attribute of a user input allows for user access to additional device functionality that may otherwise not be accessible by the user on a reduced-size device with limited real estate for displaying affordances (e.g., on a touch-sensitive display) and/or receiving user input (e.g., via a touch-sensitive display, a touch-sensitive surface, or a physical/mechanical control such as a knob or a button).
As used in the specification and claims, the term “tactile output” refers to physical displacement of a device relative to a previous position of the device, physical displacement of a component (e.g., a touch-sensitive surface) of a device relative to another component (e.g., housing) of the device, or displacement of the component relative to a center of mass of the device that will be detected by a user with the user's sense of touch. For example, in situations where the device or the component of the device is in contact with a surface of a user that is sensitive to touch (e.g., a finger, palm, or other part of a user's hand), the tactile output generated by the physical displacement will be interpreted by the user as a tactile sensation corresponding to a perceived change in physical characteristics of the device or the component of the device. For example, movement of a touch-sensitive surface (e.g., a touch-sensitive display or trackpad) is, optionally, interpreted by the user as a “down click” or “up click” of a physical actuator button. In some cases, a user will feel a tactile sensation such as an “down click” or “up click” even when there is no movement of a physical actuator button associated with the touch-sensitive surface that is physically pressed (e.g., displaced) by the user's movements. As another example, movement of the touch-sensitive surface is, optionally, interpreted or sensed by the user as “roughness” of the touch-sensitive surface, even when there is no change in smoothness of the touch-sensitive surface. While such interpretations of touch by a user will be subject to the individualized sensory perceptions of the user, there are many sensory perceptions of touch that are common to a large majority of users. Thus, when a tactile output is described as corresponding to a particular sensory perception of a user (e.g., an “up click,” a “down click,” “roughness”), unless otherwise stated, the generated tactile output corresponds to physical displacement of the device or a component thereof that will generate the described sensory perception for a typical (or average) user.
It should be appreciated that device 100 is only one example of a portable multifunction device, and that device 100 optionally has more or fewer components than shown, optionally combines two or more components, or optionally has a different configuration or arrangement of the components. The various components shown in
Memory 102 optionally includes one or more computer-readable storage mediums. The computer-readable storage mediums are optionally non-transitory. The computer-readable storage mediums are optionally transitory. Memory 102 optionally includes high-speed random access memory and optionally also includes non-volatile memory, such as one or more magnetic disk storage devices, flash memory devices, or other non-volatile solid-state memory devices. Memory controller 122 optionally controls access to memory 102 by other components of device 100.
Peripherals interface 118 can be used to couple input and output peripherals of the device to CPU 120 and memory 102. The one or more processors 120 run or execute various software programs and/or sets of instructions stored in memory 102 to perform various functions for device 100 and to process data. In some embodiments, peripherals interface 118, CPU 120, and memory controller 122 are, optionally, implemented on a single chip, such as chip 104. In some other embodiments, they are, optionally, implemented on separate chips.
RF (radio frequency) circuitry 108 receives and sends RF signals, also called electromagnetic signals. RF circuitry 108 converts electrical signals to/from electromagnetic signals and communicates with communications networks and other communications devices via the electromagnetic signals. RF circuitry 108 optionally includes well-known circuitry for performing these functions, including but not limited to an antenna system, an RF transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a CODEC chipset, a subscriber identity module (SIM) card, memory, and so forth. RF circuitry 108 optionally communicates with networks, such as the Internet, also referred to as the World Wide Web (WWW), an intranet and/or a wireless network, such as a cellular telephone network, a wireless local area network (LAN) and/or a metropolitan area network (MAN), and other devices by wireless communication. The RF circuitry 108 optionally includes well-known circuitry for detecting near field communication (NFC) fields, such as by a short-range communication radio. The wireless communication optionally uses any of a plurality of communications standards, protocols, and technologies, including but not limited to Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), high-speed downlink packet access (HSDPA), high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO), HSPA, HSPA+, Dual-Cell HSPA (DC-HSPDA), long term evolution (LTE), near field communication (NFC), wideband code division multiple access (W-CDMA), code division multiple access (CDMA), time division multiple access (TDMA), Bluetooth, Bluetooth Low Energy (BTLE), Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11n, and/or IEEE 802.11ac), voice over Internet Protocol (VoIP), Wi-MAX, a protocol for e-mail (e.g., Internet message access protocol (IMAP) and/or post office protocol (POP)), instant messaging (e.g., extensible messaging and presence protocol (XMPP), Session Initiation Protocol for Instant Messaging and Presence Leveraging Extensions (SIMPLE), Instant Messaging and Presence Service (IMPS)), and/or Short Message Service (SMS), or any other suitable communication protocol, including communication protocols not yet developed as of the filing date of this document.
Audio circuitry 110, speaker 111, and microphone 113 provide an audio interface between a user and device 100. Audio circuitry 110 receives audio data from peripherals interface 118, converts the audio data to an electrical signal, and transmits the electrical signal to speaker 111. Speaker 111 converts the electrical signal to human-audible sound waves. Audio circuitry 110 also receives electrical signals converted by microphone 113 from sound waves. Audio circuitry 110 converts the electrical signal to audio data and transmits the audio data to peripherals interface 118 for processing. Audio data is, optionally, retrieved from and/or transmitted to memory 102 and/or RF circuitry 108 by peripherals interface 118. In some embodiments, audio circuitry 110 also includes a headset jack (e.g., 212,
I/O subsystem 106 couples input/output peripherals on device 100, such as touch screen 112 and other input control devices 116, to peripherals interface 118. I/O subsystem 106 optionally includes display controller 156, optical sensor controller 158, intensity sensor controller 159, haptic feedback controller 161, and one or more input controllers 160 for other input or control devices. The one or more input controllers 160 receive/send electrical signals from/to other input control devices 116. The other input control devices 116 optionally include physical buttons (e.g., push buttons, rocker buttons, etc.), dials, slider switches, joysticks, click wheels, and so forth. In some alternate embodiments, input controller(s) 160 are, optionally, coupled to any (or none) of the following: a keyboard, an infrared port, a USB port, and a pointer device such as a mouse. The one or more buttons (e.g., 208,
A quick press of the push button optionally disengages a lock of touch screen 112 or optionally begins a process that uses gestures on the touch screen to unlock the device, as described in U.S. patent application Ser. No. 11/322,549, “Unlocking a Device by Performing Gestures on an Unlock Image,” filed Dec. 23, 2005, U.S. Pat. No. 7,657,849, which is hereby incorporated by reference in its entirety. A longer press of the push button (e.g., 206) optionally turns power to device 100 on or off. The functionality of one or more of the buttons are, optionally, user-customizable. Touch screen 112 is used to implement virtual or soft buttons and one or more soft keyboards.
Touch-sensitive display 112 provides an input interface and an output interface between the device and a user. Display controller 156 receives and/or sends electrical signals from/to touch screen 112. Touch screen 112 displays visual output to the user. The visual output optionally includes graphics, text, icons, video, and any combination thereof (collectively termed “graphics”). In some embodiments, some or all of the visual output optionally corresponds to user-interface objects.
Touch screen 112 has a touch-sensitive surface, sensor, or set of sensors that accepts input from the user based on haptic and/or tactile contact. Touch screen 112 and display controller 156 (along with any associated modules and/or sets of instructions in memory 102) detect contact (and any movement or breaking of the contact) on touch screen 112 and convert the detected contact into interaction with user-interface objects (e.g., one or more soft keys, icons, web pages, or images) that are displayed on touch screen 112. In an exemplary embodiment, a point of contact between touch screen 112 and the user corresponds to a finger of the user.
Touch screen 112 optionally uses LCD (liquid crystal display) technology, LPD (light emitting polymer display) technology, or LED (light emitting diode) technology, although other display technologies are used in other embodiments. Touch screen 112 and display controller 156 optionally detect contact and any movement or breaking thereof using any of a plurality of touch sensing technologies now known or later developed, including but not limited to capacitive, resistive, infrared, and surface acoustic wave technologies, as well as other proximity sensor arrays or other elements for determining one or more points of contact with touch screen 112. In an exemplary embodiment, projected mutual capacitance sensing technology is used, such as that found in the iPhone® and iPod Touch® from Apple Inc. of Cupertino, Calif.
A touch-sensitive display in some embodiments of touch screen 112 is, optionally, analogous to the multi-touch sensitive touchpads described in the following U.S. Pat. No. 6,323,846 (Westerman et al.), U.S. Pat. No. 6,570,557 (Westerman et al.), and/or U.S. Pat. No. 6,677,932 (Westerman), and/or U.S. Patent Publication 2002/0015024A1, each of which is hereby incorporated by reference in its entirety. However, touch screen 112 displays visual output from device 100, whereas touch-sensitive touchpads do not provide visual output.
A touch-sensitive display in some embodiments of touch screen 112 is described in the following applications: (1) U.S. patent application Ser. No. 11/381,313, “Multipoint Touch Surface Controller,” filed May 2, 2006; (2) U.S. patent application Ser. No. 10/840,862, “Multipoint Touchscreen,” filed May 6, 2004; (3) U.S. patent application Ser. No. 10/903,964, “Gestures For Touch Sensitive Input Devices,” filed Jul. 30, 2004; (4) U.S. patent application Ser. No. 11/048,264, “Gestures For Touch Sensitive Input Devices,” filed Jan. 31, 2005; (5) U.S. patent application Ser. No. 11/038,590, “Mode-Based Graphical User Interfaces For Touch Sensitive Input Devices,” filed Jan. 18, 2005; (6) U.S. patent application Ser. No. 11/228,758, “Virtual Input Device Placement On A Touch Screen User Interface,” filed Sep. 16, 2005; (7) U.S. patent application Ser. No. 11/228,700, “Operation Of A Computer With A Touch Screen Interface,” filed Sep. 16, 2005; (8) U.S. patent application Ser. No. 11/228,737, “Activating Virtual Keys Of A Touch-Screen Virtual Keyboard,” filed Sep. 16, 2005; and (9) U.S. patent application Ser. No. 11/367,749, “Multi-Functional Hand-Held Device,” filed Mar. 3, 2006. All of these applications are incorporated by reference herein in their entirety.
Touch screen 112 optionally has a video resolution in excess of 100 dpi. In some embodiments, the touch screen has a video resolution of approximately 160 dpi. The user optionally makes contact with touch screen 112 using any suitable object or appendage, such as a stylus, a finger, and so forth. In some embodiments, the user interface is designed to work primarily with finger-based contacts and gestures, which can be less precise than stylus-based input due to the larger area of contact of a finger on the touch screen. In some embodiments, the device translates the rough finger-based input into a precise pointer/cursor position or command for performing the actions desired by the user.
In some embodiments, in addition to the touch screen, device 100 optionally includes a touchpad (not shown) for activating or deactivating particular functions. In some embodiments, the touchpad is a touch-sensitive area of the device that, unlike the touch screen, does not display visual output. The touchpad is, optionally, a touch-sensitive surface that is separate from touch screen 112 or an extension of the touch-sensitive surface formed by the touch screen.
Device 100 also includes power system 162 for powering the various components. Power system 162 optionally includes a power management system, one or more power sources (e.g., battery, alternating current (AC)), a recharging system, a power failure detection circuit, a power converter or inverter, a power status indicator (e.g., a light-emitting diode (LED)) and any other components associated with the generation, management and distribution of power in portable devices.
Device 100 optionally also includes one or more optical sensors 164.
Device 100 optionally also includes one or more contact intensity sensors 165.
Device 100 optionally also includes one or more proximity sensors 166.
Device 100 optionally also includes one or more tactile output generators 167.
Device 100 optionally also includes one or more accelerometers 168.
In some embodiments, the software components stored in memory 102 include operating system 126, communication module (or set of instructions) 128, contact/motion module (or set of instructions) 130, graphics module (or set of instructions) 132, text input module (or set of instructions) 134, Global Positioning System (GPS) module (or set of instructions) 135, and applications (or sets of instructions) 136. Furthermore, in some embodiments, memory 102 (
Operating system 126 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, iOS, WINDOWS, or an embedded operating system such as VxWorks) includes various software components and/or drivers for controlling and managing general system tasks (e.g., memory management, storage device control, power management, etc.) and facilitates communication between various hardware and software components.
Communication module 128 facilitates communication with other devices over one or more external ports 124 and also includes various software components for handling data received by RF circuitry 108 and/or external port 124. External port 124 (e.g., Universal Serial Bus (USB), FIREWIRE, etc.) is adapted for coupling directly to other devices or indirectly over a network (e.g., the Internet, wireless LAN, etc.). In some embodiments, the external port is a multi-pin (e.g., 30-pin) connector that is the same as, or similar to and/or compatible with, the 30-pin connector used on iPod® (trademark of Apple Inc.) devices.
Contact/motion module 130 optionally detects contact with touch screen 112 (in conjunction with display controller 156) and other touch-sensitive devices (e.g., a touchpad or physical click wheel). Contact/motion module 130 includes various software components for performing various operations related to detection of contact, such as determining if contact has occurred (e.g., detecting a finger-down event), determining an intensity of the contact (e.g., the force or pressure of the contact or a substitute for the force or pressure of the contact), determining if there is movement of the contact and tracking the movement across the touch-sensitive surface (e.g., detecting one or more finger-dragging events), and determining if the contact has ceased (e.g., detecting a finger-up event or a break in contact). Contact/motion module 130 receives contact data from the touch-sensitive surface. Determining movement of the point of contact, which is represented by a series of contact data, optionally includes determining speed (magnitude), velocity (magnitude and direction), and/or an acceleration (a change in magnitude and/or direction) of the point of contact. These operations are, optionally, applied to single contacts (e.g., one finger contacts) or to multiple simultaneous contacts (e.g., “multitouch”/multiple finger contacts). In some embodiments, contact/motion module 130 and display controller 156 detect contact on a touchpad.
In some embodiments, contact/motion module 130 uses a set of one or more intensity thresholds to determine whether an operation has been performed by a user (e.g., to determine whether a user has “clicked” on an icon). In some embodiments, at least a subset of the intensity thresholds are determined in accordance with software parameters (e.g., the intensity thresholds are not determined by the activation thresholds of particular physical actuators and can be adjusted without changing the physical hardware of device 100). For example, a mouse “click” threshold of a trackpad or touch screen display can be set to any of a large range of predefined threshold values without changing the trackpad or touch screen display hardware. Additionally, in some implementations, a user of the device is provided with software settings for adjusting one or more of the set of intensity thresholds (e.g., by adjusting individual intensity thresholds and/or by adjusting a plurality of intensity thresholds at once with a system-level click “intensity” parameter).
Contact/motion module 130 optionally detects a gesture input by a user. Different gestures on the touch-sensitive surface have different contact patterns (e.g., different motions, timings, and/or intensities of detected contacts). Thus, a gesture is, optionally, detected by detecting a particular contact pattern. For example, detecting a finger tap gesture includes detecting a finger-down event followed by detecting a finger-up (liftoff) event at the same position (or substantially the same position) as the finger-down event (e.g., at the position of an icon). As another example, detecting a finger swipe gesture on the touch-sensitive surface includes detecting a finger-down event followed by detecting one or more finger-dragging events, and subsequently followed by detecting a finger-up (liftoff) event.
Graphics module 132 includes various known software components for rendering and displaying graphics on touch screen 112 or other display, including components for changing the visual impact (e.g., brightness, transparency, saturation, contrast, or other visual property) of graphics that are displayed. As used herein, the term “graphics” includes any object that can be displayed to a user, including, without limitation, text, web pages, icons (such as user-interface objects including soft keys), digital images, videos, animations, and the like.
In some embodiments, graphics module 132 stores data representing graphics to be used. Each graphic is, optionally, assigned a corresponding code. Graphics module 132 receives, from applications etc., one or more codes specifying graphics to be displayed along with, if necessary, coordinate data and other graphic property data, and then generates screen image data to output to display controller 156.
Haptic feedback module 133 includes various software components for generating instructions used by tactile output generator(s) 167 to produce tactile outputs at one or more locations on device 100 in response to user interactions with device 100.
Text input module 134, which is, optionally, a component of graphics module 132, provides soft keyboards for entering text in various applications (e.g., contacts 137, e-mail 140, IM 141, browser 147, and any other application that needs text input).
GPS module 135 determines the location of the device and provides this information for use in various applications (e.g., to telephone 138 for use in location-based dialing; to camera 143 as picture/video metadata; and to applications that provide location-based services such as weather widgets, local yellow page widgets, and map/navigation widgets).
Applications 136 optionally include the following modules (or sets of instructions), or a subset or superset thereof:
Examples of other applications 136 that are, optionally, stored in memory 102 include other word processing applications, other image editing applications, drawing applications, presentation applications, JAVA-enabled applications, encryption, digital rights management, voice recognition, and voice replication.
In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, contacts module 137 are, optionally, used to manage an address book or contact list (e.g., stored in application internal state 192 of contacts module 137 in memory 102 or memory 370), including: adding name(s) to the address book; deleting name(s) from the address book; associating telephone number(s), e-mail address(es), physical address(es) or other information with a name; associating an image with a name; categorizing and sorting names; providing telephone numbers or e-mail addresses to initiate and/or facilitate communications by telephone 138, video conference module 139, e-mail 140, or IM 141; and so forth.
In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, telephone module 138 are optionally, used to enter a sequence of characters corresponding to a telephone number, access one or more telephone numbers in contacts module 137, modify a telephone number that has been entered, dial a respective telephone number, conduct a conversation, and disconnect or hang up when the conversation is completed. As noted above, the wireless communication optionally uses any of a plurality of communications standards, protocols, and technologies.
In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch screen 112, display controller 156, optical sensor 164, optical sensor controller 158, contact/motion module 130, graphics module 132, text input module 134, contacts module 137, and telephone module 138, video conference module 139 includes executable instructions to initiate, conduct, and terminate a video conference between a user and one or more other participants in accordance with user instructions.
In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, e-mail client module 140 includes executable instructions to create, send, receive, and manage e-mail in response to user instructions. In conjunction with image management module 144, e-mail client module 140 makes it very easy to create and send e-mails with still or video images taken with camera module 143.
In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, the instant messaging module 141 includes executable instructions to enter a sequence of characters corresponding to an instant message, to modify previously entered characters, to transmit a respective instant message (for example, using a Short Message Service (SMS) or Multimedia Message Service (MMS) protocol for telephony-based instant messages or using XMPP, SIMPLE, or IMPS for Internet-based instant messages), to receive instant messages, and to view received instant messages. In some embodiments, transmitted and/or received instant messages optionally include graphics, photos, audio files, video files and/or other attachments as are supported in an MMS and/or an Enhanced Messaging Service (EMS). As used herein, “instant messaging” refers to both telephony-based messages (e.g., messages sent using SMS or MMS) and Internet-based messages (e.g., messages sent using XMPP, SIMPLE, or IMPS).
In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, GPS module 135, map module 154, and music player module, workout support module 142 includes executable instructions to create workouts (e.g., with time, distance, and/or calorie burning goals); communicate with workout sensors (sports devices); receive workout sensor data; calibrate sensors used to monitor a workout; select and play music for a workout; and display, store, and transmit workout data.
In conjunction with touch screen 112, display controller 156, optical sensor(s) 164, optical sensor controller 158, contact/motion module 130, graphics module 132, and image management module 144, camera module 143 includes executable instructions to capture still images or video (including a video stream) and store them into memory 102, modify characteristics of a still image or video, or delete a still image or video from memory 102.
In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, and camera module 143, image management module 144 includes executable instructions to arrange, modify (e.g., edit), or otherwise manipulate, label, delete, present (e.g., in a digital slide show or album), and store still and/or video images.
In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, browser module 147 includes executable instructions to browse the Internet in accordance with user instructions, including searching, linking to, receiving, and displaying web pages or portions thereof, as well as attachments and other files linked to web pages.
In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, e-mail client module 140, and browser module 147, calendar module 148 includes executable instructions to create, display, modify, and store calendars and data associated with calendars (e.g., calendar entries, to-do lists, etc.) in accordance with user instructions.
In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, and browser module 147, widget modules 149 are mini-applications that are, optionally, downloaded and used by a user (e.g., weather widget 149-1, stocks widget 149-2, calculator widget 149-3, alarm clock widget 149-4, and dictionary widget 149-5) or created by the user (e.g., user-created widget 149-6). In some embodiments, a widget includes an HTML (Hypertext Markup Language) file, a CSS (Cascading Style Sheets) file, and a JavaScript file. In some embodiments, a widget includes an XML (Extensible Markup Language) file and a JavaScript file (e.g., Yahoo! Widgets).
In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, and browser module 147, the widget creator module 150 are, optionally, used by a user to create widgets (e.g., turning a user-specified portion of a web page into a widget).
In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, search module 151 includes executable instructions to search for text, music, sound, image, video, and/or other files in memory 102 that match one or more search criteria (e.g., one or more user-specified search terms) in accordance with user instructions.
In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, and browser module 147, video and music player module 152 includes executable instructions that allow the user to download and play back recorded music and other sound files stored in one or more file formats, such as MP3 or AAC files, and executable instructions to display, present, or otherwise play back videos (e.g., on touch screen 112 or on an external, connected display via external port 124). In some embodiments, device 100 optionally includes the functionality of an MP3 player, such as an iPod (trademark of Apple Inc.).
In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, notes module 153 includes executable instructions to create and manage notes, to-do lists, and the like in accordance with user instructions.
In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, GPS module 135, and browser module 147, map module 154 are, optionally, used to receive, display, modify, and store maps and data associated with maps (e.g., driving directions, data on stores and other points of interest at or near a particular location, and other location-based data) in accordance with user instructions.
In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, text input module 134, e-mail client module 140, and browser module 147, online video module 155 includes instructions that allow the user to access, browse, receive (e.g., by streaming and/or download), play back (e.g., on the touch screen or on an external, connected display via external port 124), send an e-mail with a link to a particular online video, and otherwise manage online videos in one or more file formats, such as H.264. In some embodiments, instant messaging module 141, rather than e-mail client module 140, is used to send a link to a particular online video. Additional description of the online video application can be found in U.S. Provisional Patent Application No. 60/936,562, “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos,” filed Jun. 20, 2007, and U.S. patent application Ser. No. 11/968,067, “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos,” filed Dec. 31, 2007, the contents of which are hereby incorporated by reference in their entirety.
Each of the above-identified modules and applications corresponds to a set of executable instructions for performing one or more functions described above and the methods described in this application (e.g., the computer-implemented methods and other information processing methods described herein). These modules (e.g., sets of instructions) need not be implemented as separate software programs, procedures, or modules, and thus various subsets of these modules are, optionally, combined or otherwise rearranged in various embodiments. For example, video player module is, optionally, combined with music player module into a single module (e.g., video and music player module 152,
In some embodiments, device 100 is a device where operation of a predefined set of functions on the device is performed exclusively through a touch screen and/or a touchpad. By using a touch screen and/or a touchpad as the primary input control device for operation of device 100, the number of physical input control devices (such as push buttons, dials, and the like) on device 100 is, optionally, reduced.
The predefined set of functions that are performed exclusively through a touch screen and/or a touchpad optionally include navigation between user interfaces. In some embodiments, the touchpad, when touched by the user, navigates device 100 to a main, home, or root menu from any user interface that is displayed on device 100. In such embodiments, a “menu button” is implemented using a touchpad. In some other embodiments, the menu button is a physical push button or other physical input control device instead of a touchpad.
Event sorter 170 receives event information and determines the application 136-1 and application view 191 of application 136-1 to which to deliver the event information. Event sorter 170 includes event monitor 171 and event dispatcher module 174. In some embodiments, application 136-1 includes application internal state 192, which indicates the current application view(s) displayed on touch-sensitive display 112 when the application is active or executing. In some embodiments, device/global internal state 157 is used by event sorter 170 to determine which application(s) is (are) currently active, and application internal state 192 is used by event sorter 170 to determine application views 191 to which to deliver event information.
In some embodiments, application internal state 192 includes additional information, such as one or more of: resume information to be used when application 136-1 resumes execution, user interface state information that indicates information being displayed or that is ready for display by application 136-1, a state queue for enabling the user to go back to a prior state or view of application 136-1, and a redo/undo queue of previous actions taken by the user.
Event monitor 171 receives event information from peripherals interface 118. Event information includes information about a sub-event (e.g., a user touch on touch-sensitive display 112, as part of a multi-touch gesture). Peripherals interface 118 transmits information it receives from I/O subsystem 106 or a sensor, such as proximity sensor 166, accelerometer(s) 168, and/or microphone 113 (through audio circuitry 110). Information that peripherals interface 118 receives from I/O subsystem 106 includes information from touch-sensitive display 112 or a touch-sensitive surface.
In some embodiments, event monitor 171 sends requests to the peripherals interface 118 at predetermined intervals. In response, peripherals interface 118 transmits event information. In other embodiments, peripherals interface 118 transmits event information only when there is a significant event (e.g., receiving an input above a predetermined noise threshold and/or for more than a predetermined duration).
In some embodiments, event sorter 170 also includes a hit view determination module 172 and/or an active event recognizer determination module 173.
Hit view determination module 172 provides software procedures for determining where a sub-event has taken place within one or more views when touch-sensitive display 112 displays more than one view. Views are made up of controls and other elements that a user can see on the display.
Another aspect of the user interface associated with an application is a set of views, sometimes herein called application views or user interface windows, in which information is displayed and touch-based gestures occur. The application views (of a respective application) in which a touch is detected optionally correspond to programmatic levels within a programmatic or view hierarchy of the application. For example, the lowest level view in which a touch is detected is, optionally, called the hit view, and the set of events that are recognized as proper inputs are, optionally, determined based, at least in part, on the hit view of the initial touch that begins a touch-based gesture.
Hit view determination module 172 receives information related to sub-events of a touch-based gesture. When an application has multiple views organized in a hierarchy, hit view determination module 172 identifies a hit view as the lowest view in the hierarchy which should handle the sub-event. In most circumstances, the hit view is the lowest level view in which an initiating sub-event occurs (e.g., the first sub-event in the sequence of sub-events that form an event or potential event). Once the hit view is identified by the hit view determination module 172, the hit view typically receives all sub-events related to the same touch or input source for which it was identified as the hit view.
Active event recognizer determination module 173 determines which view or views within a view hierarchy should receive a particular sequence of sub-events. In some embodiments, active event recognizer determination module 173 determines that only the hit view should receive a particular sequence of sub-events. In other embodiments, active event recognizer determination module 173 determines that all views that include the physical location of a sub-event are actively involved views, and therefore determines that all actively involved views should receive a particular sequence of sub-events. In other embodiments, even if touch sub-events were entirely confined to the area associated with one particular view, views higher in the hierarchy would still remain as actively involved views.
Event dispatcher module 174 dispatches the event information to an event recognizer (e.g., event recognizer 180). In embodiments including active event recognizer determination module 173, event dispatcher module 174 delivers the event information to an event recognizer determined by active event recognizer determination module 173. In some embodiments, event dispatcher module 174 stores in an event queue the event information, which is retrieved by a respective event receiver 182.
In some embodiments, operating system 126 includes event sorter 170. Alternatively, application 136-1 includes event sorter 170. In yet other embodiments, event sorter 170 is a stand-alone module, or a part of another module stored in memory 102, such as contact/motion module 130.
In some embodiments, application 136-1 includes a plurality of event handlers 190 and one or more application views 191, each of which includes instructions for handling touch events that occur within a respective view of the application's user interface. Each application view 191 of the application 136-1 includes one or more event recognizers 180. Typically, a respective application view 191 includes a plurality of event recognizers 180. In other embodiments, one or more of event recognizers 180 are part of a separate module, such as a user interface kit (not shown) or a higher level object from which application 136-1 inherits methods and other properties. In some embodiments, a respective event handler 190 includes one or more of: data updater 176, object updater 177, GUI updater 178, and/or event data 179 received from event sorter 170. Event handler 190 optionally utilizes or calls data updater 176, object updater 177, or GUI updater 178 to update the application internal state 192. Alternatively, one or more of the application views 191 include one or more respective event handlers 190. Also, in some embodiments, one or more of data updater 176, object updater 177, and GUI updater 178 are included in a respective application view 191.
A respective event recognizer 180 receives event information (e.g., event data 179) from event sorter 170 and identifies an event from the event information. Event recognizer 180 includes event receiver 182 and event comparator 184. In some embodiments, event recognizer 180 also includes at least a subset of: metadata 183, and event delivery instructions 188 (which optionally include sub-event delivery instructions).
Event receiver 182 receives event information from event sorter 170. The event information includes information about a sub-event, for example, a touch or a touch movement. Depending on the sub-event, the event information also includes additional information, such as location of the sub-event. When the sub-event concerns motion of a touch, the event information optionally also includes speed and direction of the sub-event. In some embodiments, events include rotation of the device from one orientation to another (e.g., from a portrait orientation to a landscape orientation, or vice versa), and the event information includes corresponding information about the current orientation (also called device attitude) of the device.
Event comparator 184 compares the event information to predefined event or sub-event definitions and, based on the comparison, determines an event or sub-event, or determines or updates the state of an event or sub-event. In some embodiments, event comparator 184 includes event definitions 186. Event definitions 186 contain definitions of events (e.g., predefined sequences of sub-events), for example, event 1 (187-1), event 2 (187-2), and others. In some embodiments, sub-events in an event (187) include, for example, touch begin, touch end, touch movement, touch cancellation, and multiple touching. In one example, the definition for event 1 (187-1) is a double tap on a displayed object. The double tap, for example, comprises a first touch (touch begin) on the displayed object for a predetermined phase, a first liftoff (touch end) for a predetermined phase, a second touch (touch begin) on the displayed object for a predetermined phase, and a second liftoff (touch end) for a predetermined phase. In another example, the definition for event 2 (187-2) is a dragging on a displayed object. The dragging, for example, comprises a touch (or contact) on the displayed object for a predetermined phase, a movement of the touch across touch-sensitive display 112, and liftoff of the touch (touch end). In some embodiments, the event also includes information for one or more associated event handlers 190.
In some embodiments, event definition 187 includes a definition of an event for a respective user-interface object. In some embodiments, event comparator 184 performs a hit test to determine which user-interface object is associated with a sub-event. For example, in an application view in which three user-interface objects are displayed on touch-sensitive display 112, when a touch is detected on touch-sensitive display 112, event comparator 184 performs a hit test to determine which of the three user-interface objects is associated with the touch (sub-event). If each displayed object is associated with a respective event handler 190, the event comparator uses the result of the hit test to determine which event handler 190 should be activated. For example, event comparator 184 selects an event handler associated with the sub-event and the object triggering the hit test.
In some embodiments, the definition for a respective event (187) also includes delayed actions that delay delivery of the event information until after it has been determined whether the sequence of sub-events does or does not correspond to the event recognizer's event type.
When a respective event recognizer 180 determines that the series of sub-events do not match any of the events in event definitions 186, the respective event recognizer 180 enters an event impossible, event failed, or event ended state, after which it disregards subsequent sub-events of the touch-based gesture. In this situation, other event recognizers, if any, that remain active for the hit view continue to track and process sub-events of an ongoing touch-based gesture.
In some embodiments, a respective event recognizer 180 includes metadata 183 with configurable properties, flags, and/or lists that indicate how the event delivery system should perform sub-event delivery to actively involved event recognizers. In some embodiments, metadata 183 includes configurable properties, flags, and/or lists that indicate how event recognizers interact, or are enabled to interact, with one another. In some embodiments, metadata 183 includes configurable properties, flags, and/or lists that indicate whether sub-events are delivered to varying levels in the view or programmatic hierarchy.
In some embodiments, a respective event recognizer 180 activates event handler 190 associated with an event when one or more particular sub-events of an event are recognized. In some embodiments, a respective event recognizer 180 delivers event information associated with the event to event handler 190. Activating an event handler 190 is distinct from sending (and deferred sending) sub-events to a respective hit view. In some embodiments, event recognizer 180 throws a flag associated with the recognized event, and event handler 190 associated with the flag catches the flag and performs a predefined process.
In some embodiments, event delivery instructions 188 include sub-event delivery instructions that deliver event information about a sub-event without activating an event handler. Instead, the sub-event delivery instructions deliver event information to event handlers associated with the series of sub-events or to actively involved views. Event handlers associated with the series of sub-events or with actively involved views receive the event information and perform a predetermined process.
In some embodiments, data updater 176 creates and updates data used in application 136-1. For example, data updater 176 updates the telephone number used in contacts module 137, or stores a video file used in video player module. In some embodiments, object updater 177 creates and updates objects used in application 136-1. For example, object updater 177 creates a new user-interface object or updates the position of a user-interface object. GUI updater 178 updates the GUI. For example, GUI updater 178 prepares display information and sends it to graphics module 132 for display on a touch-sensitive display.
In some embodiments, event handler(s) 190 includes or has access to data updater 176, object updater 177, and GUI updater 178. In some embodiments, data updater 176, object updater 177, and GUI updater 178 are included in a single module of a respective application 136-1 or application view 191. In other embodiments, they are included in two or more software modules.
It shall be understood that the foregoing discussion regarding event handling of user touches on touch-sensitive displays also applies to other forms of user inputs to operate multifunction devices 100 with input devices, not all of which are initiated on touch screens. For example, mouse movement and mouse button presses, optionally coordinated with single or multiple keyboard presses or holds; contact movements such as taps, drags, scrolls, etc. on touchpads; pen stylus inputs; movement of the device; oral instructions; detected eye movements; biometric inputs; and/or any combination thereof are optionally utilized as inputs corresponding to sub-events which define an event to be recognized.
Device 100 optionally also include one or more physical buttons, such as “home” or menu button 204. As described previously, menu button 204 is, optionally, used to navigate to any application 136 in a set of applications that are, optionally, executed on device 100. Alternatively, in some embodiments, the menu button is implemented as a soft key in a GUI displayed on touch screen 112.
In some embodiments, device 100 includes touch screen 112, menu button 204, push button 206 for powering the device on/off and locking the device, volume adjustment button(s) 208, subscriber identity module (SIM) card slot 210, headset jack 212, and docking/charging external port 124. Push button 206 is, optionally, used to turn the power on/off on the device by depressing the button and holding the button in the depressed state for a predefined time interval; to lock the device by depressing the button and releasing the button before the predefined time interval has elapsed; and/or to unlock the device or initiate an unlock process. In an alternative embodiment, device 100 also accepts verbal input for activation or deactivation of some functions through microphone 113. Device 100 also, optionally, includes one or more contact intensity sensors 165 for detecting intensity of contacts on touch screen 112 and/or one or more tactile output generators 167 for generating tactile outputs for a user of device 100.
Each of the above-identified elements in
Attention is now directed towards embodiments of user interfaces that are, optionally, implemented on, for example, portable multifunction device 100.
It should be noted that the icon labels illustrated in
Although some of the examples that follow will be given with reference to inputs on touch screen display 112 (where the touch-sensitive surface and the display are combined), in some embodiments, the device detects inputs on a touch-sensitive surface that is separate from the display, as shown in
Additionally, while the following examples are given primarily with reference to finger inputs (e.g., finger contacts, finger tap gestures, finger swipe gestures), it should be understood that, in some embodiments, one or more of the finger inputs are replaced with input from another input device (e.g., a mouse-based input or stylus input). For example, a swipe gesture is, optionally, replaced with a mouse click (e.g., instead of a contact) followed by movement of the cursor along the path of the swipe (e.g., instead of movement of the contact). As another example, a tap gesture is, optionally, replaced with a mouse click while the cursor is located over the location of the tap gesture (e.g., instead of detection of the contact followed by ceasing to detect the contact). Similarly, when multiple user inputs are simultaneously detected, it should be understood that multiple computer mice are, optionally, used simultaneously, or a mouse and finger contacts are, optionally, used simultaneously.
Exemplary techniques for detecting and processing touch intensity are found, for example, in related applications: International Patent Application Serial No. PCT/US2013/040061, titled “Device, Method, and Graphical User Interface for Displaying User Interface Objects Corresponding to an Application,” filed May 8, 2013, published as WIPO Publication No. WO/2013/169849, and International Patent Application Serial No. PCT/US2013/069483, titled “Device, Method, and Graphical User Interface for Transitioning Between Touch Input to Display Output Relationships,” filed Nov. 11, 2013, published as WIPO Publication No. WO/2014/105276, each of which is hereby incorporated by reference in their entirety.
In some embodiments, device 500 has one or more input mechanisms 506 and 508. Input mechanisms 506 and 508, if included, can be physical. Examples of physical input mechanisms include push buttons and rotatable mechanisms. In some embodiments, device 500 has one or more attachment mechanisms. Such attachment mechanisms, if included, can permit attachment of device 500 with, for example, hats, eyewear, earrings, necklaces, shirts, jackets, bracelets, watch straps, chains, trousers, belts, shoes, purses, backpacks, and so forth. These attachment mechanisms permit device 500 to be worn by a user.
Input mechanism 508 is, optionally, a microphone, in some examples. Personal electronic device 500 optionally includes various sensors, such as GPS sensor 532, accelerometer 534, directional sensor 540 (e.g., compass), gyroscope 536, motion sensor 538, and/or a combination thereof, all of which can be operatively connected to I/O section 514.
Memory 518 of personal electronic device 500 can be a non-transitory computer-readable storage medium, 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 process 900 (
As used here, the term “affordance” refers to a user-interactive graphical user interface object that is, optionally, displayed on the display screen of devices 100, 300, and/or 500 (
As used herein, the term “focus selector” refers to an input element that indicates a current part of a user interface with which a user is interacting. In some implementations that include a cursor or other location marker, the cursor acts as a “focus selector” so that when an input (e.g., a press input) is detected on a touch-sensitive surface (e.g., touchpad 355 in
As used in the specification and claims, the term “characteristic intensity” of a contact refers to a characteristic of the contact based on one or more intensities of the contact. In some embodiments, the characteristic intensity is based on multiple intensity samples. The characteristic intensity is, optionally, based on a predefined number of intensity samples, or a set of intensity samples collected during a predetermined time period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10 seconds) relative to a predefined event (e.g., after detecting the contact, prior to detecting liftoff of the contact, before or after detecting a start of movement of the contact, prior to detecting an end of the contact, before or after detecting an increase in intensity of the contact, and/or before or after detecting a decrease in intensity of the contact). A characteristic intensity of a contact is, optionally, based on one or more of: a maximum value of the intensities of the contact, a mean value of the intensities of the contact, an average value of the intensities of the contact, a top 10 percentile value of the intensities of the contact, a value at the half maximum of the intensities of the contact, a value at the 90 percent maximum of the intensities of the contact, or the like. In some embodiments, the duration of the contact is used in determining the characteristic intensity (e.g., when the characteristic intensity is an average of the intensity of the contact over time). In some embodiments, the characteristic intensity is compared to a set of one or more intensity thresholds to determine whether an operation has been performed by a user. For example, the set of one or more intensity thresholds optionally includes a first intensity threshold and a second intensity threshold. In this example, a contact with a characteristic intensity that does not exceed the first threshold results in a first operation, a contact with a characteristic intensity that exceeds the first intensity threshold and does not exceed the second intensity threshold results in a second operation, and a contact with a characteristic intensity that exceeds the second threshold results in a third operation. In some embodiments, a comparison between the characteristic intensity and one or more thresholds is used to determine whether or not to perform one or more operations (e.g., whether to perform a respective operation or forgo performing the respective operation), rather than being used to determine whether to perform a first operation or a second operation.
In some embodiments, a portion of a gesture is identified for purposes of determining a characteristic intensity. For example, a touch-sensitive surface optionally receives a continuous swipe contact transitioning from a start location and reaching an end location, at which point the intensity of the contact increases. In this example, the characteristic intensity of the contact at the end location is, optionally, based on only a portion of the continuous swipe contact, and not the entire swipe contact (e.g., only the portion of the swipe contact at the end location). In some embodiments, a smoothing algorithm is, optionally, applied to the intensities of the swipe contact prior to determining the characteristic intensity of the contact. For example, the smoothing algorithm optionally includes one or more of: an unweighted sliding-average smoothing algorithm, a triangular smoothing algorithm, a median filter smoothing algorithm, and/or an exponential smoothing algorithm. In some circumstances, these smoothing algorithms eliminate narrow spikes or dips in the intensities of the swipe contact for purposes of determining a characteristic intensity.
The intensity of a contact on the touch-sensitive surface is, optionally, characterized relative to one or more intensity thresholds, such as a contact-detection intensity threshold, a light press intensity threshold, a deep press intensity threshold, and/or one or more other intensity thresholds. In some embodiments, the light press intensity threshold corresponds to an intensity at which the device will perform operations typically associated with clicking a button of a physical mouse or a trackpad. In some embodiments, the deep press intensity threshold corresponds to an intensity at which the device will perform operations that are different from operations typically associated with clicking a button of a physical mouse or a trackpad. In some embodiments, when a contact is detected with a characteristic intensity below the light press intensity threshold (e.g., and above a nominal contact-detection intensity threshold below which the contact is no longer detected), the device will move a focus selector in accordance with movement of the contact on the touch-sensitive surface without performing an operation associated with the light press intensity threshold or the deep press intensity threshold. Generally, unless otherwise stated, these intensity thresholds are consistent between different sets of user interface figures.
An increase of characteristic intensity of the contact from an intensity below the light press intensity threshold to an intensity between the light press intensity threshold and the deep press intensity threshold is sometimes referred to as a “light press” input. An increase of characteristic intensity of the contact from an intensity below the deep press intensity threshold to an intensity above the deep press intensity threshold is sometimes referred to as a “deep press” input. An increase of characteristic intensity of the contact from an intensity below the contact-detection intensity threshold to an intensity between the contact-detection intensity threshold and the light press intensity threshold is sometimes referred to as detecting the contact on the touch-surface. A decrease of characteristic intensity of the contact from an intensity above the contact-detection intensity threshold to an intensity below the contact-detection intensity threshold is sometimes referred to as detecting liftoff of the contact from the touch-surface. In some embodiments, the contact-detection intensity threshold is zero. In some embodiments, the contact-detection intensity threshold is greater than zero.
In some embodiments described herein, one or more operations are performed in response to detecting a gesture that includes a respective press input or in response to detecting the respective press input performed with a respective contact (or a plurality of contacts), where the respective press input is detected based at least in part on detecting an increase in intensity of the contact (or plurality of contacts) above a press-input intensity threshold. In some embodiments, the respective operation is performed in response to detecting the increase in intensity of the respective contact above the press-input intensity threshold (e.g., a “down stroke” of the respective press input). In some embodiments, the press input includes an increase in intensity of the respective contact above the press-input intensity threshold and a subsequent decrease in intensity of the contact below the press-input intensity threshold, and the respective operation is performed in response to detecting the subsequent decrease in intensity of the respective contact below the press-input threshold (e.g., an “up stroke” of the respective press input).
In some embodiments, the device employs intensity hysteresis to avoid accidental inputs sometimes termed “jitter,” where the device defines or selects a hysteresis intensity threshold with a predefined relationship to the press-input intensity threshold (e.g., the hysteresis intensity threshold is X intensity units lower than the press-input intensity threshold or the hysteresis intensity threshold is 75%, 90%, or some reasonable proportion of the press-input intensity threshold). Thus, in some embodiments, the press input includes an increase in intensity of the respective contact above the press-input intensity threshold and a subsequent decrease in intensity of the contact below the hysteresis intensity threshold that corresponds to the press-input intensity threshold, and the respective operation is performed in response to detecting the subsequent decrease in intensity of the respective contact below the hysteresis intensity threshold (e.g., an “up stroke” of the respective press input). Similarly, in some embodiments, the press input is detected only when the device detects an increase in intensity of the contact from an intensity at or below the hysteresis intensity threshold to an intensity at or above the press-input intensity threshold and, optionally, a subsequent decrease in intensity of the contact to an intensity at or below the hysteresis intensity, and the respective operation is performed in response to detecting the press input (e.g., the increase in intensity of the contact or the decrease in intensity of the contact, depending on the circumstances).
For ease of explanation, the descriptions of operations performed in response to a press input associated with a press-input intensity threshold or in response to a gesture including the press input are, optionally, triggered in response to detecting either: an increase in intensity of a contact above the press-input intensity threshold, an increase in intensity of a contact from an intensity below the hysteresis intensity threshold to an intensity above the press-input intensity threshold, a decrease in intensity of the contact below the press-input intensity threshold, and/or a decrease in intensity of the contact below the hysteresis intensity threshold corresponding to the press-input intensity threshold. Additionally, in examples where an operation is described as being performed in response to detecting a decrease in intensity of a contact below the press-input intensity threshold, the operation is, optionally, performed in response to detecting a decrease in intensity of the contact below a hysteresis intensity threshold corresponding to, and lower than, the press-input intensity threshold.
Attention is now directed towards embodiments of user interfaces (“UI”) and associated processes that are implemented on an electronic device, such as portable multifunction device 100, device 300, or device 500.
Attention is now directed towards embodiments of user interfaces (“UI”) and associated processes that are implemented on an electronic device, such as portable multifunction device 100, device 300, or device 500.
System 600 can include one or more user devices 610, which can include any type of electronic device, such as a mobile phone, tablet computer, desktop computer, laptop computer, PDA, or the like. In some examples, user device 610 can include a device similar or identical to devices 100, 300, or 500, described above. User device 610 can include an operating system and a wellness database 611 (e.g., memory 102, 370, or 518) for securely storing wellness or non-wellness data along with associated metadata, such as the time the data was recorded, type of data, device used to record the data, user associated with the data, and the like. User device 610 can further include application programming interfaces (APIs) with access controls for storing data in the wellness database 611 and for accessing data stored in the wellness database 611.
User device 610 can be configured to receive wellness or non-wellness data from various sources and can store the received data in the wellness database 611. For example, user device 610 can be configured to receive wellness or non-wellness data from sensors 602, 604, 606, and 608. These sensors can include any type of sensor capable of obtaining wellness data, such as a biometric sensor, activity tracker, or the like. For example, sensors 602, 604, 606, and 608 can include, but are not limited to, a scale, blood pressure cuff, blood glucose monitor, electrocardiogram, step counter, gyroscope, accelerometer, SpO2 sensor, respiration sensor, posture sensor, stress sensor, photoplethysmogram, galvanic skin response sensor, temperature sensor, or the like. Sensors 602, 604, 606, and 608 can also include other types of sensors, such as audio sensors, ambient light sensors, electromagnetic sensors, touch sensors, capacitive sensors, and the like, for obtaining non-wellness data, such as situational data, temporal data, personal data, contact data, and the like data. In some examples, each sensor can be a separate device, while, in other examples, any combination of two or more of the sensors can be included within a single device. For example, the gyroscope, accelerometer, photoplethysmogram, galvanic skin response sensor, and temperature sensor can be included within a wearable electronic device, such as a smart watch, while the scale, blood pressure cuff, blood glucose monitor, SpO2 sensor, respiration sensor, posture sensor, stress sensor, and asthma inhaler can each be separate devices. While specific examples are provided, it should be appreciated that other sensors can be used and other combinations of sensors can be combined into a single device.
Sensors 602, 604, 606, and 608 can be used to measure wellness or non-wellness data continuously, intermittently, periodically, or at any other desired frequency or interval of time. For example, sensors 602, 604, 606, and 608 can be used to obtain a single measurement or multiple measurements over a length of time. Sensors 602, 604, 606, and 608 can be configured to measure wellness or non-wellness data at the same intervals of time, or can be configured to measure wellness or non-wellness data at different intervals of time. These intervals may be set by a user or may be a default setting for each sensor. Additionally, sensors 602, 604, 606, 608 can be used to measure wellness or non-wellness data at any time or location desired by the user. Moreover, sensors 602, 604, 606, and 608 can be used with or without the supervision of a healthcare provider. For example, a user can use sensors 602, 604, 606, and 608 to obtain sensor measurements at home without the supervision of a medical professional.
In some examples, user device 610 can include software sensor applications 613 (e.g., third party applications) associated with each of sensors 602, 604, 606, and 608 for interfacing with the sensors to allow user device 610 to receive the wellness or non-wellness data. In these examples, the applications 613 can use the device's APIs to store the wellness or non-wellness data in the wellness database 611 of user device 610. In some examples, device 610 can be a smart phone, tablet computer, or the like, and the software sensor applications 613 can include software applications downloadable onto device 610. It should be understood that “third party” can correspond to an entity different than the manufacturer of device 610 and/or the entity that created and/or maintains the operating system of device 610. In these instances, third party applications and their corresponding sensors can communicate and function within the operating system of device 610 according to a predefined device protocol associated with device 610.
The applications 613 can similarly use the device's APIs to access data stored in the wellness database 611. In other examples, user device 610 can be configured to share one or more communication formats with sensors 602, 604, 606, and 608 to allow user device 610 to receive and interpret the wellness or non-wellness data from the sensors. The received data can then be stored in the wellness database 611 of user device 610.
User device 610 can further receive wellness or non-wellness data from its own wellness or non-wellness data sensors 620 (e.g., sensors 168, 359, and 520), from a user interacting with user device 610, from another entity, such as a physician, or from other non-sensor sources. For example, using the device's APIs, wellness or non-wellness data can be received from applications 617 (third party or first party applications) on user device 610, such as a clock application, a calendaring application, a gaming application, an application from a healthcare provider, a messaging application, a physical activity application, a workout application, or the like. The wellness or non-wellness data from the applications 617 can originate from sensors 620, a user interacting with the applications, a remote database (e.g., database for a medical website), a healthcare provider institution (e.g., via the institution's application 617), or the like. In these examples, the usage of the application 617 (e.g., how long you play a video game application, when you play the video game, number of times interacting with a stock application, number of times interacting with a social networking application, length of time interacting with a social networking application, etc.), usage of user device 610 (e.g., length of time on the phone or number of text messages sent as determined from a phone payment application, time spent browsing the Internet as determined from the device's browser, etc.), time spent listening to music as determined from a music or streaming radio application, time spent using a remote application for controlling a television, amount of time or money spent on shopping websites, weather data from a weather application (e.g., to determine how weather affects a user's health), type of events occurring in the user's life as determined from a calendar (e.g., meetings, birthdays, holidays, etc.), interactions with certain people as determined from a contact list and/or calendar application and/or a messaging application and/or phone of user device 610, or the like, can be received by user device 610 and stored in the wellness database 611.
In some examples, default or user-selected settings can be provided to restrict the access that at least one application (e.g., at least one of applications 613 and 617) on user device 610 has to the wellness database 611 of user device 610 (for both storage and retrieval purposes) and to the sensor data generated by sensors 620 within user device 610 and/or sensor data generated by sensors 602, 604, 606, and 608. For example, an application for tracking a user's running sessions can be granted access to the data generated by the GPS sensor of user device 610, but can be prevented from accessing the user's blood pressure data stored in the wellness database 611. In some examples, an entity other than the owner of user device 610 can set the authorization settings for various applications on user device 610. For example, the manufacturer of user device 610 and/or the entity that created and/or maintains the operating system of user device 610 can evaluate the applications to determine if they should be given access to the user's wellness data and/or sensor data generated or received by user device 610. In some examples, these settings can be overridden by the user. User device 610 can further include a display for displaying the stored wellness data or non-wellness data.
In some examples, user server 714 and user database 716 can be configured to securely store a user's wellness or non-wellness data using a public/private key system that only allows the owner of the wellness or non-wellness data to decrypt the data. Additionally, the wellness or non-wellness data stored in user database 716 can be stored anonymously (e.g., without identifying and/or personal information about the user, such as a legal name, username, time and location data, or the like). In this way, other users, hackers, and the owner/operator of user database 716 cannot determine the identity of the user associated with the data stored in database 716. In some examples, a user can access their wellness or non-wellness data stored in user database 716 from a user device that is different than the one used to upload the wellness or non-wellness data to user server 714. In these instances, the user can be required to provide login credentials to access their wellness or non-wellness data. User server 714 can be configured to perform the authorization process to restrict access to the data within user database 716.
System 700 can further include any number of other user devices 722 and 724 coupled to network 712. In some examples, user devices 722 and 724 can be operated by the same user as user device 610. In these instances, the user can access their wellness or non-wellness data stored in user database 716 by providing user server 714 with the appropriate credentials. In some examples, wellness and non-wellness data can be synced between user database 716 and one or more of user device 610, 722, and 724. In other examples, the user of user devices 722 and 724 can be a person that is different than the user of user device 610. In these examples, the users of devices 722 and 724 cannot access the wellness or non-wellness data of the user of user device 610 without the authorization of the user of user device 610. If authorization is given, wellness or non-wellness data can be shared with the users of user devices 722 and 724.
In some examples, any of the above described sources of wellness or non-wellness data can be configured to measure, generate, or receive wellness or non-wellness data continuously, intermittently, periodically, or at any other desired frequency or interval of time. As such, the wellness or non-wellness data can similarly be stored or updated in wellness database 611 or user database 716 continuously, intermittently, periodically, or at any other desired frequency or interval of time. The frequencies and intervals of time used for measuring, generating, receiving, or storing wellness or non-wellness can be the same or they can be different. Additionally, these frequencies and intervals can be default values or they can be set by a user to provide the user with wellness or non-wellness data that has been updated within a desired length of time.
While not shown, it should be appreciated that many other user devices can be coupled to user server 714 through network 712 to collect and store wellness or non-wellness data for other users in a manner similar to that described above.
At block 902, one or more processors of the device can receive a selection of a type of workout. The selected type of workout can include any type of workout, such as running, walking, cycling, swimming, yoga, dancing, climbing, cross-training, rowing, or the like. In some examples, the one or more processors of the device can cause, on the display of the device, a display of a list of available types of workouts that a user can select. In these examples, the selection of the type of workout can be received by the one or more processors of the device in response to a user indicating a selection of one of the displayed available types of workouts (e.g., via mouse click, touch on a touch sensitive display, or the like).
For example,
The type of workout selected in block 902 may have multiple workout metrics associated with it. For example, if the workout type “Running” is selected, the workout metrics of elapsed time, distance, pace, and heart rate may be associated with the workout type. In another example, the “Running” workout type may be associated with the elapsed time, distance, pace, heart rate, and calories burned workout metrics. In another example, the cycling workout type may be associated with the elapsed time and distance workout metrics. While a few examples of workout metrics have been given, other workout metrics may also be possible, such as speed, rotations per minute (RPM), and laps.
Additionally, while there may be a default set of workout metrics associated with a given workout type, the set of workout metrics associated with a workout type may be user configurable via a user configuration interface. For example, using a touch-screen or other user input, a user can select workout metrics that are an associated with a given workout metric.
Optionally, in block 902, a later block of process 900, or in a block after block 902 that is not depicted in
For example,
In other examples, the device can select from other of interfaces similar to interface 1200 that allows for other types of goals to be set. For example, while example interfaces for selecting specific workout metrics for the “Running” type of workout have been provided in
In some examples, in response to a selection of start button 1214 in interface 1200, the device can optionally display a countdown before beginning the workout selected at block 902 using the selected goal.
Referring back to
The pro-view display includes an indicator representative of each of the plurality of workout metrics associated with the workout type selected in block 902. For example,
Interface 1300 also includes a focus indicator 1320 that highlights a workout metric indicator that is currently selected as the focused workout metric. In interface 1300, first indicator 1310 represents the focused workout metric. The focus indicator 1320 may be a box or other shape around one of the workout metric indicators, but other methods of highlighting a workout metric indicator may also be used, such as a different coloring, a larger font size, a different background color, or blinking of the indicator. The focus indicator 1320 may be moved to other workout metrics indicators based on, for example, user input. Examples of user input include receiving a gesture on a touch-sensitive display or mechanical user input device, such as a rotatable crown or button. Focus indicator 1320 may aid in a user concentrating on a particular workout metric that is important to the user or for the particular workout type.
As explained above, the workout metrics associated with a given workout type may be configurable.
The ordering of the workout metric indicators in pro-view displays may be configurable. For example, the position of first indicator 1410 with respect to second indicator 1412 may be changed. In some cases, the position may be changed by, for example, dragging the first indicator to a new position while in a position configuration user interface.
Also at block 904, before or after displaying the pro-view, the workout may also be initiated. Initiating the workout can include activating one or more activity sensors (e.g., sensors 168, 359, and 520) and recording activity data provided by those one or more activity sensors. In some examples, the activity sensors activated at block 904 can be selected based on the type of workout selected at block 902. For example, a biometric sensor for measuring heart rate, GPS sensor for measuring position, and accelerometer for measuring motion to determine distance traveled can be activated if a running type of workout was selected at block 902. However, if a cycling type of workout was selected at block 902, a biometric sensor for measuring heart rate and a GPS sensor for measuring position may be activated at block 902, but an accelerometer may not be activated. This may be done because an accelerometer may not provide reliable information in determining distance traveled on a bike and can be left inactive to save power. Other combinations of activity sensors can selectively be activated for other types of workouts.
Referring back to
At block 910, one or more processors of the device can update the pro-view display (e.g., those shown in
Blocks 906, 908, and 910 can continue to be repeated to provide the user with up to date information associated with the workout metrics of the workout type via the pro-view display. In some examples where the workout application is running in the background of the device or while the display of the device is deactivated, block 910 can be omitted and blocks 906 and 908 can repeatedly be performed to monitor the user's workout and update the monitored workout metrics such that an accurate display of the metrics can later be provided to the user when the physical activity application is reopened or the display of the device is activated. In some examples, upon activating the display of the device, the workout interface previously displayed (e.g., one of the interfaces displayed in
In block 912, one or more processors of the device can cause the pro-view display to continue to be displayed. Alternatively, something may trigger a simple-view display to be displayed. For example, a gesture, such as a horizontal swipe, may be detected that causes a transition from the pro-view display to the simple-view display. Other user input could also cause the transition from the pro-view display to the simple-view display.
In block 914, the simply-view display is displayed on the display of the device. The simple-view display includes an indicator for less than all of the workout metrics associated with the selected workout type of block 902. For example,
Referring back to
At block 920, one or more processors of the device can update the simple-view display (e.g., those shown in
Blocks 916, 918, and 920 can continue to be repeated to provide the user with up to date information associated with the attributes of the workout via the workout interface. In some examples where the workout application is running in the background of the device or while the display of the device is deactivated, block 920 can be omitted and blocks 916 and 918 can repeatedly be performed to monitor the user's workout and update the monitored attributes such that an accurate display of the attributes can later be provided to the user when the physical activity application is reopened or the display of the device is activated. In some examples, upon activating the display of the device, the workout interface previously displayed (e.g., one of the interfaces displayed in
In block 922, one or more processors of the device can cause the simple-view display to continue to be displayed. Alternatively, something may trigger the pro-view to be displayed. For example, a gesture, such as a horizontal swipe, may be detected that causes a transition from the simple-view display to the pro-view display. Other user input could also cause the transition from the pro-view display to the simple-view display.
In the case of the simple-view display in
When simple-view is displayed, focused workout metric 1512 and its representative focused indicator 1510 may be changed. For example, by receiving a user input, such as a gesture on a touch-sensitive screen or other user input on a rotatable crown or button, focused workout metric may be changed to the distance workout metric, which is depicted in simple-view display in interface 1600 of
If the focused workout metric of the simple-view display changes, as is the case with the change from interface 1500 of
The transition from the pro-view back to the simple view operates in a similar manner. For example, if the focus indicator changes from the first indicator (e.g., first indicator 1710 in interface 1700 of
The simple-view display of interface 2000 of
The transitions between pro-views and simple-views may use animations. For example, the focused workout metric of the pro-view display may be animated to move into position in the simple-view display. Similar animations can also be used for the transitions between simple-views and pro-views.
User input, such as gestures, can also be used to transition to other displays, such as a workout control or a music control. For example,
While process 900 (
As shown in
Processing unit 2502 can be configured to detect (e.g., using identifying unit 2508) an identification of a type of workout to be performed. The type of workout is associated with a plurality of workout metrics, including a first workout metric and a second workout metric. Movement detecting unit 2510 can be configured to detect movement associated with an electronic device using activity sensor units 2506. Generation unit 2512 can be configured to generate activity data based on the detected movement from movement detecting unit 2510. Determining unit 2514 can be configured to determine a current value of the first workout metric and a current value of a second workout metric based on the activity data. Gesture detecting unit 2516 can be configured to detect a first user gesture corresponding to a request to display workout metric data. Displaying unit 2518 can be configured to, in response to gesture detecting unit 2516, cause, on the touch-sensitive display unit 2504 a first display. The first display can include a plurality of indicators representative of the plurality of workout metrics, including a first indicator representative of the first workout metric and a second indicator representative of the second workout metric. The first display also can include a focus indicator for one of the plurality of indicators, wherein the focus indicator indicates a focused workout metric. The gesture detecting unit 25 can be further configured to detect, while the first displaying is being displayed, a second user gesture corresponding to a request to transition between the first display and a second display. Displaying unit 2518 can be further configured to, in response to the second user gesture being detected while the first display is being displayed, cause, on the touch-sensitive display unit a first transition to the second display. The second display can include an indicator representative of the focused workout metric. Not all of the plurality of workout metrics is represented in the second display. Gesture detecting unit 2516 can be further configured to, while the second display is being displayed, detect a third user gesture corresponding to a request to transition between the second display and the first display. Displaying unit 2518 can be further configured to, in response to the third user gesture being detected while the second display is being displayed, cause, on the touch-sensitive display unit a second transition to the first display.
In some examples, the plurality workout metrics that are associated with the type of workout are configurable.
In some examples, the plurality of workout metrics includes a third workout metric and a fourth workout metric, and the plurality of indicators representative of the plurality of workout metrics further includes a third indicator representative of a third workout metric associated with the type of workout and a fourth indicator representative of a fourth workout metric associated with the type of workout. The plurality of workout metrics include at least four workout metrics selected from: a workout metric related to calories, a workout metric related to heart rate, a workout metric related to speed, a workout metric related to distance traveled, and a workout metric related to time. In some examples, the plurality of indicators in the first display includes only four indicators representative of workout metrics.
In some examples, the first indicator has a position relative to the second indicator in the first display. Gesture detecting unit 2516 can be further configured to detect a fourth user gesture corresponding to a request to change the position of the first indicator relative to the second indicator in the first display. Processing unit 2502 can be further configured to have optional changing unit 2520, which can be configured to, in response to the fourth user gesture being detected, change the position of the first indicator relative to the second indicator.
In some examples, the first indicator has a first color and the second indicator has a second color different than the first color. In some examples, the transition from the first display to the second display includes an animation. In some examples, gesture detecting unit 2516 can be further configured to detect a fifth user gesture corresponding to a request to transition from the first display or the second display to a third display. Displaying unit 2518 can be further configured to, in response to the fifth user gesture being detected while the first display or the second display is being displayed, cause on the touch-sensitive display unit the third display, including workout controls or music controls.
In some examples, gesture detecting unit 2516 can be configured to, while the first display is being displayed, detect a sixth user gesture corresponding to a request to move the focus indicator to a different indicator of the plurality of indicators on the first display. Displaying unit 2518 can be further configure to, in response to the sixth user gesture being detected, move the focus indicator to the different indicator on the first display.
In some examples, generation unit 2512 can be further configured to generate the activity data after gesture detecting unit 2516 detects the first user gesture corresponding to the request to display workout metrics.
As described above, one aspect of the present technology is the gathering and use of data available from various sources to improve the delivery to users of invitational content or any other content that may be of interest to them. The present disclosure contemplates that in some instances, this gathered data may include personal information data that uniquely identifies or can be used to contact or locate a specific person. Such personal information data can include demographic data, location-based data, telephone numbers, email addresses, home addresses, or any other identifying information.
The present disclosure recognizes that the use of such personal information data, in the present technology, can be used to the benefit of users. For example, the personal information data can be used to deliver targeted content that is of greater interest to the user. Accordingly, use of such personal information data enables calculated control of the delivered content. Further, other uses for personal information data that benefit the user are also contemplated by the present disclosure.
The present disclosure further contemplates that the entities responsible for the collection, analysis, disclosure, transfer, storage, or other use of such personal information data will comply with well-established privacy policies and/or privacy practices. In particular, such entities should implement and consistently use privacy policies and practices that are generally recognized as meeting or exceeding industry or governmental requirements for maintaining personal information data private and secure. For example, personal information from users should be collected for legitimate and reasonable uses of the entity and not shared or sold outside of those legitimate uses. Further, such collection should occur only after receiving the informed consent of the users. Additionally, such entities would take any needed steps for safeguarding and securing access to such personal information data and ensuring that others with access to the personal information data adhere to their privacy policies and procedures. Further, such entities can subject themselves to evaluation by third parties to certify their adherence to widely accepted privacy policies and practices.
Despite the foregoing, the present disclosure also contemplates embodiments in which users selectively block the use of, or access to, personal information data. That is, the present disclosure contemplates that hardware and/or software elements can be provided to prevent or block access to such personal information data. For example, in the case of advertisement delivery services, the present technology can be configured to allow users to select to “opt in” or “opt out” of participation in the collection of personal information data during registration for services. In another example, users can select not to provide location information for targeted content delivery services. In yet another example, users can select to not provide precise location information, but permit the transfer of location zone information.
Therefore, although the present disclosure broadly covers use of personal information data to implement one or more various disclosed embodiments, the present disclosure also contemplates that the various embodiments can also be implemented without the need for accessing such personal information data. That is, the various embodiments of the present technology are not rendered inoperable due to the lack of all or a portion of such personal information data. For example, content can be selected and delivered to users by inferring preferences based on non-personal information data or a bare minimum amount of personal information, such as the content being requested by the device associated with a user, other non-personal information available to the content delivery services, or publically available information.
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 appended claims.
This application is a continuation of U.S. patent application Ser. No. 15/600,243, entitled “WORKOUT MONITOR INTERFACE,” filed on May 19, 2017, which claims priority to U.S. Provisional Patent Application Ser. No. 62/398,440, entitled “WORKOUT MONITOR INTERFACE,” filed on Sep. 22, 2016. The contents of each of which are hereby incorporated by reference in their entirety.
| Number | Name | Date | Kind |
|---|---|---|---|
| 4205628 | Null | Jun 1980 | A |
| 4842266 | Sweeney et al. | Jun 1989 | A |
| 5423863 | Felblinger et al. | Jun 1995 | A |
| 5458548 | Crossing et al. | Oct 1995 | A |
| 5474077 | Suga | Dec 1995 | A |
| 5642731 | Kehr | Jul 1997 | A |
| 5685723 | Ladin et al. | Nov 1997 | A |
| 5788655 | Yoshimura et al. | Aug 1998 | A |
| 6013008 | Fukushima | Jan 2000 | A |
| 6095949 | Arai | Aug 2000 | A |
| 6095984 | Amano et al. | Aug 2000 | A |
| 6097371 | Siddiqui et al. | Aug 2000 | A |
| 6097385 | Robinson | Aug 2000 | A |
| 6244988 | Delman | Jun 2001 | B1 |
| 6302789 | Harada et al. | Oct 2001 | B2 |
| 6416471 | Kumar et al. | Jul 2002 | B1 |
| 6603477 | Tittle | Aug 2003 | B1 |
| 6639584 | Li | Oct 2003 | B1 |
| 6705972 | Takano et al. | Mar 2004 | B1 |
| 6837827 | Lee et al. | Jan 2005 | B1 |
| 6866613 | Brown et al. | Mar 2005 | B1 |
| 7020514 | Wiesel | Mar 2006 | B1 |
| 7128693 | Brown et al. | Oct 2006 | B2 |
| 7251454 | White | Jul 2007 | B2 |
| 7302272 | Ackley | Nov 2007 | B2 |
| 7662065 | Kahn et al. | Feb 2010 | B1 |
| 7695406 | Waters | Apr 2010 | B2 |
| 7739148 | Suzuki et al. | Jun 2010 | B2 |
| 8060229 | Gupta et al. | Nov 2011 | B2 |
| 8105208 | Oleson et al. | Jan 2012 | B2 |
| 8321006 | Snyder et al. | Nov 2012 | B1 |
| 8341557 | Pisula | Dec 2012 | B2 |
| 8475339 | Hwang et al. | Jul 2013 | B2 |
| 8496563 | Komatsu et al. | Jul 2013 | B2 |
| 8676170 | Porrati et al. | Mar 2014 | B2 |
| 8768648 | Panther et al. | Jul 2014 | B2 |
| 8784115 | Chuang | Jul 2014 | B1 |
| 8784271 | Brumback | Jul 2014 | B2 |
| 8825445 | Hoffman et al. | Sep 2014 | B2 |
| 8934963 | Farazi | Jan 2015 | B1 |
| 8990006 | Wallace et al. | Mar 2015 | B1 |
| 9011292 | Weast et al. | Apr 2015 | B2 |
| 9020538 | White et al. | Apr 2015 | B1 |
| 9224291 | Moll-Carrillo et al. | Dec 2015 | B2 |
| 9230076 | King et al. | Jan 2016 | B2 |
| 9449365 | Roberts | Sep 2016 | B2 |
| 9532734 | Hoffman et al. | Jan 2017 | B2 |
| 9557881 | Jain et al. | Jan 2017 | B1 |
| 9589445 | White et al. | Mar 2017 | B2 |
| 9712629 | Molettiere et al. | Jul 2017 | B2 |
| 9734477 | Weast et al. | Aug 2017 | B2 |
| 9813642 | Chen et al. | Nov 2017 | B1 |
| 9817481 | Pantelopoulos | Nov 2017 | B2 |
| 9854653 | Ackmann et al. | Dec 2017 | B1 |
| 9880805 | Guralnick | Jan 2018 | B1 |
| 9910571 | Chen | Mar 2018 | B2 |
| 9940682 | Hoffman et al. | Apr 2018 | B2 |
| 10056006 | Hsu-Hoffman et al. | Aug 2018 | B1 |
| 10220258 | Gu et al. | Mar 2019 | B2 |
| 10226195 | Briante et al. | Mar 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 |
| 10489508 | Zhai et al. | Nov 2019 | B2 |
| 10500441 | Lagree | Dec 2019 | B2 |
| 10736543 | Chen et al. | Aug 2020 | B2 |
| 10777314 | Williams et al. | Sep 2020 | B1 |
| 10978195 | Blahnik et al. | Apr 2021 | B2 |
| 11103161 | Williams et al. | Aug 2021 | B2 |
| 11107569 | Devoto | Aug 2021 | B1 |
| 11152100 | Crowley et al. | Oct 2021 | B2 |
| 11202598 | Soli et al. | Dec 2021 | B2 |
| 11209957 | Dryer et al. | Dec 2021 | B2 |
| 11317833 | Williams et al. | May 2022 | 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 |
| 20030134714 | Oishi et al. | Jul 2003 | A1 |
| 20030179229 | Van et al. | Sep 2003 | A1 |
| 20030181291 | Ogawa | Sep 2003 | A1 |
| 20030182628 | Lira | Sep 2003 | A1 |
| 20030216971 | Sick et al. | Nov 2003 | A1 |
| 20030226695 | Mault | Dec 2003 | A1 |
| 20040014567 | Mendel | Jan 2004 | A1 |
| 20040077462 | Brown et al. | Apr 2004 | A1 |
| 20040128286 | Yasushi et al. | Jul 2004 | A1 |
| 20040236189 | Hawthorne et al. | Nov 2004 | A1 |
| 20050075214 | Brown et al. | Apr 2005 | A1 |
| 20050079905 | Martens | Apr 2005 | A1 |
| 20050113650 | Pacione et al. | May 2005 | A1 |
| 20050124324 | Thomas et al. | Jun 2005 | A1 |
| 20050139852 | Chen et al. | Jun 2005 | A1 |
| 20050165627 | Fotsch et al. | Jul 2005 | A1 |
| 20050172311 | Hjelt et al. | Aug 2005 | A1 |
| 20050197063 | White et al. | Sep 2005 | A1 |
| 20050216867 | Marvit et al. | Sep 2005 | A1 |
| 20050228735 | Duquette | Oct 2005 | A1 |
| 20050272564 | Pyles et al. | 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 |
| 20060184800 | Rosenberg | Aug 2006 | A1 |
| 20060240959 | Huang | Oct 2006 | A1 |
| 20060250524 | Roche | Nov 2006 | A1 |
| 20070021269 | Shum | Jan 2007 | A1 |
| 20070032733 | Burton | Feb 2007 | A1 |
| 20070033069 | Rao et al. | Feb 2007 | A1 |
| 20070056727 | Newman | Mar 2007 | A1 |
| 20070071256 | Ito | Mar 2007 | A1 |
| 20070113726 | Oliver et al. | May 2007 | A1 |
| 20070136093 | Rankin et al. | Jun 2007 | A1 |
| 20070143433 | Daigle | Jun 2007 | A1 |
| 20070169614 | Sasaki et al. | Jul 2007 | A1 |
| 20070249949 | Hadley | Oct 2007 | A1 |
| 20070271065 | Gupta et al. | Nov 2007 | A1 |
| 20080020803 | Rios et al. | Jan 2008 | A1 |
| 20080027673 | Trumm | Jan 2008 | A1 |
| 20080051919 | Sakai et al. | Feb 2008 | A1 |
| 20080052945 | Matas et al. | Mar 2008 | A1 |
| 20080058626 | Miyata et al. | Mar 2008 | A1 |
| 20080076637 | Gilley et al. | Mar 2008 | A1 |
| 20080082145 | Skwarek et al. | Apr 2008 | A1 |
| 20080086318 | Gilley et al. | Apr 2008 | A1 |
| 20080096726 | Riley et al. | Apr 2008 | A1 |
| 20080141135 | Mason et al. | Jun 2008 | A1 |
| 20080150731 | Laukkanen et al. | Jun 2008 | A1 |
| 20080161161 | Pipinich et al. | Jul 2008 | A1 |
| 20080161707 | Farringdon et al. | Jul 2008 | A1 |
| 20080200312 | Tagliabue | Aug 2008 | A1 |
| 20080229226 | Rowbottom et al. | Sep 2008 | A1 |
| 20080254767 | Jin | Oct 2008 | A1 |
| 20080262946 | Wren | Oct 2008 | A1 |
| 20080300110 | Smith et al. | Dec 2008 | A1 |
| 20090007017 | Anzures | Jan 2009 | A1 |
| 20090012988 | Brown | Jan 2009 | A1 |
| 20090047645 | Dibenedetto et al. | Feb 2009 | A1 |
| 20090118100 | Oliver et al. | May 2009 | A1 |
| 20090149299 | Tchao et al. | Jun 2009 | A1 |
| 20090164567 | Hara | Jun 2009 | A1 |
| 20090170532 | Lee et al. | Jul 2009 | A1 |
| 20090192823 | Hawkins et al. | Jul 2009 | A1 |
| 20090210078 | Crowley | Aug 2009 | A1 |
| 20090216556 | Martin et al. | Aug 2009 | A1 |
| 20090222056 | Lindh et al. | Sep 2009 | A1 |
| 20090233771 | Quatrochi et al. | Sep 2009 | A1 |
| 20090259134 | Levine | Oct 2009 | A1 |
| 20090262088 | Moll-Carrillo et al. | Oct 2009 | A1 |
| 20090268949 | Ueshima et al. | Oct 2009 | A1 |
| 20090287103 | Pillai | Nov 2009 | A1 |
| 20090319243 | Suarez-Rivera et al. | Dec 2009 | A1 |
| 20100031202 | Morris et al. | Feb 2010 | A1 |
| 20100042949 | Chen | Feb 2010 | A1 |
| 20100048358 | Tchao et al. | Feb 2010 | A1 |
| 20100060586 | Pisula | 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 et al. | May 2010 | A1 |
| 20100137106 | Oshima et al. | Jun 2010 | A1 |
| 20100145209 | 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 |
| 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 |
| 20100309149 | Blumenberg et al. | Dec 2010 | A1 |
| 20100331145 | Lakovic et al. | Dec 2010 | A1 |
| 20110003665 | Burton et al. | Jan 2011 | A1 |
| 20110016120 | Haughay et al. | Jan 2011 | A1 |
| 20110032105 | Hoffman et al. | Feb 2011 | A1 |
| 20110066051 | Moon et al. | Mar 2011 | A1 |
| 20110071869 | Obrien et al. | Mar 2011 | A1 |
| 20110074699 | Marr et al. | Mar 2011 | A1 |
| 20110098928 | Hoffman et al. | Apr 2011 | A1 |
| 20110106553 | Tanaka et al. | May 2011 | A1 |
| 20110112418 | Feild et al. | May 2011 | A1 |
| 20110125041 | Fischell et al. | May 2011 | A1 |
| 20110137678 | Williams | Jun 2011 | A1 |
| 20110137836 | Kuriyama et al. | Jun 2011 | A1 |
| 20110159469 | Hwang et al. | Jun 2011 | A1 |
| 20110167369 | Van Os | Jul 2011 | A1 |
| 20110201911 | Johnson et al. | Aug 2011 | A1 |
| 20110213276 | Sarussi et al. | Sep 2011 | A1 |
| 20110227872 | Huska et al. | Sep 2011 | A1 |
| 20110230169 | Ohki | Sep 2011 | A1 |
| 20110230986 | Lafortune et al. | Sep 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 |
| 20120015778 | Lee et al. | Jan 2012 | A1 |
| 20120015779 | Powch et al. | Jan 2012 | A1 |
| 20120030623 | Hoellwarth | Feb 2012 | A1 |
| 20120034897 | Kreitzer et al. | Feb 2012 | A1 |
| 20120041767 | Hoffman et al. | Feb 2012 | A1 |
| 20120042039 | Mark | Feb 2012 | A1 |
| 20120059664 | Georgiev et al. | Mar 2012 | A1 |
| 20120071770 | Grey et al. | Mar 2012 | A1 |
| 20120092383 | Hysek et al. | Apr 2012 | A1 |
| 20120105225 | Valtonen | May 2012 | A1 |
| 20120116550 | Hoffman et al. | May 2012 | A1 |
| 20120150759 | Tarjan | Jun 2012 | A1 |
| 20120159380 | Kocienda | Jun 2012 | A1 |
| 20120179319 | Gilman et al. | Jul 2012 | A1 |
| 20120232414 | Mollicone et al. | Sep 2012 | A1 |
| 20120253485 | Weast et al. | Oct 2012 | A1 |
| 20120274508 | Brown | Nov 2012 | A1 |
| 20120283855 | Hoffman et al. | Nov 2012 | A1 |
| 20120290109 | Engelberg et al. | Nov 2012 | A1 |
| 20120302840 | Kubo | Nov 2012 | A1 |
| 20120302843 | Otsubo et al. | Nov 2012 | A1 |
| 20120317167 | Rahman et al. | Dec 2012 | A1 |
| 20120326873 | Utter | Dec 2012 | A1 |
| 20130054150 | Sacks et al. | Feb 2013 | A1 |
| 20130054720 | Kang et al. | Feb 2013 | A1 |
| 20130067050 | Kotteri et al. | Mar 2013 | A1 |
| 20130081083 | Yu et al. | Mar 2013 | A1 |
| 20130093715 | Marsden et al. | Apr 2013 | A1 |
| 20130106603 | Weast et al. | May 2013 | A1 |
| 20130106684 | Weast et al. | May 2013 | A1 |
| 20130110264 | Weast 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 |
| 20130138734 | Crivello et al. | May 2013 | A1 |
| 20130141233 | Jacobs et al. | Jun 2013 | A1 |
| 20130151285 | Mclaren et al. | Jun 2013 | A1 |
| 20130158367 | Pacione et al. | Jun 2013 | A1 |
| 20130184613 | Homsi et al. | Jul 2013 | A1 |
| 20130185097 | Saria et al. | Jul 2013 | A1 |
| 20130187923 | Yoshimoto et al. | Jul 2013 | A1 |
| 20130188322 | Lowe et al. | Jul 2013 | A1 |
| 20130197679 | Balakrishnan et al. | Aug 2013 | A1 |
| 20130198672 | Yoon et al. | Aug 2013 | A1 |
| 20130203475 | Shin et al. | Aug 2013 | A1 |
| 20130215119 | Vanhoecke | Aug 2013 | A1 |
| 20130217979 | Blackadar et al. | Aug 2013 | A1 |
| 20130231575 | Erkkila et al. | Sep 2013 | A1 |
| 20130231711 | Kaib | Sep 2013 | A1 |
| 20130233097 | Hayner et al. | Sep 2013 | A1 |
| 20130262155 | Hinkamp | Oct 2013 | A1 |
| 20130263719 | Watterson et al. | Oct 2013 | A1 |
| 20130324210 | Doig et al. | Dec 2013 | A1 |
| 20130325358 | Oshima et al. | Dec 2013 | A1 |
| 20130325394 | Yuen et al. | Dec 2013 | A1 |
| 20130325396 | Yuen et al. | Dec 2013 | A1 |
| 20130330694 | Watterson | 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 |
| 20140039840 | Yuen et al. | Feb 2014 | A1 |
| 20140067096 | Aibara | Mar 2014 | A1 |
| 20140081666 | Teller et al. | Mar 2014 | A1 |
| 20140089836 | Damani et al. | Mar 2014 | A1 |
| 20140108998 | Chaudhri et al. | Apr 2014 | A1 |
| 20140139637 | Mistry et al. | May 2014 | A1 |
| 20140176346 | Brumback | Jun 2014 | A1 |
| 20140176475 | Myers et al. | Jun 2014 | A1 |
| 20140180786 | Sullivan | Jun 2014 | A1 |
| 20140189584 | Weng | 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 |
| 20140274413 | Chelst | Sep 2014 | A1 |
| 20140275852 | Hong et al. | Sep 2014 | A1 |
| 20140275854 | Venkatraman et al. | Sep 2014 | A1 |
| 20140277628 | Nieminen et al. | Sep 2014 | A1 |
| 20140278229 | Hong et al. | Sep 2014 | A1 |
| 20140282153 | Christiansen et al. | Sep 2014 | A1 |
| 20140288680 | Hoffman et al. | Sep 2014 | A1 |
| 20140310598 | Sprague et al. | Oct 2014 | A1 |
| 20140310643 | Karmanenko et al. | Oct 2014 | A1 |
| 20140331314 | Fujioka | Nov 2014 | A1 |
| 20140336796 | Agnew | Nov 2014 | A1 |
| 20140337041 | Madden et al. | Nov 2014 | A1 |
| 20140337450 | Choudhary et al. | Nov 2014 | A1 |
| 20140337451 | Choudhary et al. | Nov 2014 | A1 |
| 20140344693 | Reese et al. | Nov 2014 | A1 |
| 20140344723 | Malik et al. | Nov 2014 | A1 |
| 20140344951 | Brewer | Nov 2014 | A1 |
| 20140358473 | Goel et al. | Dec 2014 | A1 |
| 20140358584 | Worden et al. | Dec 2014 | A1 |
| 20140371887 | Hoffman et al. | Dec 2014 | A1 |
| 20150004578 | Gilley et al. | Jan 2015 | A1 |
| 20150018632 | Khair | Jan 2015 | A1 |
| 20150046814 | Haughay et al. | Feb 2015 | A1 |
| 20150057942 | Self et al. | Feb 2015 | A1 |
| 20150057943 | Self et al. | Feb 2015 | A1 |
| 20150058263 | Landers | Feb 2015 | A1 |
| 20150065095 | Seo et al. | Mar 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 | Mar 2015 | A1 |
| 20150081059 | Hwang et al. | Mar 2015 | A1 |
| 20150081060 | Hwang et al. | Mar 2015 | A1 |
| 20150081529 | Lee et al. | Mar 2015 | A1 |
| 20150083970 | Koh et al. | Mar 2015 | A1 |
| 20150098309 | Adams et al. | Apr 2015 | A1 |
| 20150100245 | Huang et al. | Apr 2015 | A1 |
| 20150106025 | Keller et al. | Apr 2015 | A1 |
| 20150112700 | Sublett et al. | Apr 2015 | A1 |
| 20150113553 | Pan | Apr 2015 | A1 |
| 20150118657 | Shrake et al. | Apr 2015 | A1 |
| 20150124067 | Bala et al. | May 2015 | A1 |
| 20150130830 | Nagasaki et al. | May 2015 | A1 |
| 20150142689 | Squires | May 2015 | A1 |
| 20150153943 | Wang | Jun 2015 | A1 |
| 20150164349 | Gopalakrishnan et al. | Jun 2015 | A1 |
| 20150180746 | Day et al. | Jun 2015 | A1 |
| 20150181314 | Swanson | Jun 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 |
| 20150217163 | Amis et al. | Aug 2015 | A1 |
| 20150220883 | Bfar et al. | Aug 2015 | A1 |
| 20150251053 | Hoffman et al. | Sep 2015 | A1 |
| 20150262497 | Landau et al. | Sep 2015 | A1 |
| 20150269848 | Yuen et al. | Sep 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 |
| 20150343709 | Gerstle et al. | Dec 2015 | A1 |
| 20150347711 | Soli et al. | Dec 2015 | A1 |
| 20150350861 | Soli et al. | Dec 2015 | A1 |
| 20150351655 | Coleman | Dec 2015 | A1 |
| 20150374310 | Lee | Dec 2015 | A1 |
| 20160000379 | Pougatchev et al. | Jan 2016 | A1 |
| 20160004432 | Bernstein | Jan 2016 | 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 |
| 20160058336 | Blahnik et al. | Mar 2016 | A1 |
| 20160058337 | Blahnik et al. | Mar 2016 | A1 |
| 20160062582 | Wilson et al. | Mar 2016 | A1 |
| 20160065505 | Iskander | Mar 2016 | A1 |
| 20160070275 | Anderson et al. | Mar 2016 | A1 |
| 20160072896 | Petersen et al. | Mar 2016 | A1 |
| 20160085937 | Dettinger et al. | Mar 2016 | A1 |
| 20160089569 | Blahnik | Mar 2016 | A1 |
| 20160107031 | Palatsi et al. | Apr 2016 | A1 |
| 20160135731 | Drennan | May 2016 | A1 |
| 20160140828 | Deforest | May 2016 | A1 |
| 20160156584 | Hum et al. | Jun 2016 | A1 |
| 20160196635 | Cho et al. | Jul 2016 | A1 |
| 20160210099 | Hampapuram et al. | Jul 2016 | A1 |
| 20160220225 | Wang et al. | Aug 2016 | A1 |
| 20160235374 | Miller et al. | Aug 2016 | A1 |
| 20160246880 | Battiah et al. | Aug 2016 | A1 |
| 20160250517 | Tilvis et al. | Sep 2016 | A1 |
| 20160256082 | Ely et al. | Sep 2016 | A1 |
| 20160256741 | Holma et al. | Sep 2016 | A1 |
| 20160263435 | Venkatraman et al. | Sep 2016 | A1 |
| 20160278659 | Kaib et al. | Sep 2016 | A1 |
| 20160278667 | Villard et al. | Sep 2016 | A1 |
| 20160279475 | Aragones et al. | Sep 2016 | A1 |
| 20160301794 | Schlakman et al. | Oct 2016 | A1 |
| 20160302680 | Narusawa et al. | Oct 2016 | A1 |
| 20160302717 | Tawa et al. | Oct 2016 | A1 |
| 20160324457 | Dagum | Nov 2016 | A1 |
| 20160328736 | Wang et al. | Nov 2016 | A1 |
| 20160332025 | Repka | Nov 2016 | A1 |
| 20160346607 | Rapfogel | Dec 2016 | A1 |
| 20160371464 | Bricker | Dec 2016 | A1 |
| 20160375306 | Gu et al. | Dec 2016 | A1 |
| 20160379511 | Dawson et al. | Dec 2016 | A1 |
| 20170001073 | Krueger 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 |
| 20170053542 | Wilson et al. | Feb 2017 | A1 |
| 20170065224 | Rahko et al. | Mar 2017 | A1 |
| 20170095695 | Mangusson et al. | Apr 2017 | A1 |
| 20170143262 | Kurunmäki et al. | May 2017 | A1 |
| 20170153606 | Pitis et al. | Jun 2017 | A1 |
| 20170153804 | Kim et al. | Jun 2017 | A1 |
| 20170161014 | Kikugawa et al. | Jun 2017 | A1 |
| 20170209766 | Riley et al. | Jul 2017 | A1 |
| 20170237694 | Choudhary et al. | Aug 2017 | A1 |
| 20170239524 | Lee et al. | Aug 2017 | A1 |
| 20170243508 | Cheng et al. | Aug 2017 | A1 |
| 20170266494 | Crankson et al. | Sep 2017 | A1 |
| 20170269792 | Xu et al. | Sep 2017 | A1 |
| 20170274149 | Aeschlimann | Sep 2017 | A1 |
| 20170274267 | Blahnik | Sep 2017 | A1 |
| 20170281026 | Nick et al. | Oct 2017 | A1 |
| 20170281057 | Blahnik et al. | Oct 2017 | A1 |
| 20170294174 | Albadawi et al. | Oct 2017 | A1 |
| 20170300186 | Kuhar et al. | Oct 2017 | A1 |
| 20170301039 | Dyer et al. | Oct 2017 | A1 |
| 20170319941 | Smith et al. | Nov 2017 | A1 |
| 20170329933 | Brust et al. | Nov 2017 | A1 |
| 20170330297 | Cronin et al. | Nov 2017 | A1 |
| 20170333752 | Korkala et al. | Nov 2017 | A1 |
| 20170337033 | Duyan et al. | Nov 2017 | A1 |
| 20170348562 | Jung et al. | Dec 2017 | A1 |
| 20170354845 | Williams et al. | Dec 2017 | A1 |
| 20170357520 | De Vries et al. | Dec 2017 | A1 |
| 20180000426 | Li | Jan 2018 | A1 |
| 20180001184 | Tran et al. | Jan 2018 | A1 |
| 20180032234 | Michalske | Feb 2018 | A1 |
| 20180053200 | Cronin et al. | Feb 2018 | A1 |
| 20180056132 | Foley et al. | Mar 2018 | A1 |
| 20180065025 | Toda 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 |
| 20180126248 | Dion et al. | May 2018 | A1 |
| 20180137937 | Gass et al. | May 2018 | A1 |
| 20180140903 | Poure et al. | May 2018 | A1 |
| 20180150709 | Ha | May 2018 | A1 |
| 20180189077 | Gupta et al. | Jul 2018 | A1 |
| 20180206766 | Blahnik et al. | Jul 2018 | A1 |
| 20180272190 | Miura et al. | Sep 2018 | A1 |
| 20180294053 | Runyon et al. | Oct 2018 | A1 |
| 20180318647 | Foley et al. | Nov 2018 | A1 |
| 20180329584 | Williams et al. | Nov 2018 | A1 |
| 20180339195 | Bernotas | Nov 2018 | A1 |
| 20180345078 | Blahnik et al. | Dec 2018 | A1 |
| 20190008467 | Averina et al. | Jan 2019 | A1 |
| 20190025995 | Williams | Jan 2019 | A1 |
| 20190034049 | Williams et al. | Jan 2019 | A1 |
| 20190034050 | Williams et al. | Jan 2019 | A1 |
| 20190089701 | Mercury et al. | Mar 2019 | A1 |
| 20190104951 | Valys et al. | Apr 2019 | A1 |
| 20190143194 | Evancha et al. | May 2019 | A1 |
| 20190184234 | Packles et al. | Jun 2019 | A1 |
| 20190209777 | O'connell et al. | Jul 2019 | A1 |
| 20190232110 | Williams et al. | Aug 2019 | A1 |
| 20190232111 | Williams et al. | Aug 2019 | A1 |
| 20190274565 | Soli et al. | Sep 2019 | A1 |
| 20190279520 | Wilson et al. | Sep 2019 | A1 |
| 20190336044 | Williams et al. | Nov 2019 | A1 |
| 20190336045 | Williams et al. | Nov 2019 | A1 |
| 20190336827 | Intonato et al. | Nov 2019 | A1 |
| 20190339849 | Williams et al. | Nov 2019 | A1 |
| 20190342616 | Domm et al. | Nov 2019 | A1 |
| 20190387982 | Buller | Dec 2019 | A1 |
| 20200014967 | Putnam | Jan 2020 | A1 |
| 20200054931 | Martin et al. | Feb 2020 | A1 |
| 20200098278 | Doti et al. | Mar 2020 | A1 |
| 20200101365 | Wilson et al. | Apr 2020 | A1 |
| 20200110814 | Abuelsaad et al. | Apr 2020 | A1 |
| 20200149921 | Hoffman et al. | May 2020 | A1 |
| 20200160961 | Wadhawan et al. | May 2020 | A1 |
| 20200297249 | Williams et al. | Sep 2020 | A1 |
| 20200357522 | Pahwa et al. | Nov 2020 | A1 |
| 20200381100 | Williams et al. | Dec 2020 | A1 |
| 20200382613 | Sundstrom et al. | Dec 2020 | A1 |
| 20210007632 | Blahnik et al. | Jan 2021 | A1 |
| 20210007633 | Blahnik et al. | Jan 2021 | A1 |
| 20210093919 | Lyke et al. | Apr 2021 | A1 |
| 20210110908 | Blahnik et al. | Apr 2021 | A1 |
| 20210113137 | Soli et al. | Apr 2021 | A1 |
| 20210145321 | Chen et al. | May 2021 | A1 |
| 20210191584 | Williams et al. | Jun 2021 | A1 |
| 20210193293 | Blahnik et al. | Jun 2021 | A1 |
| 20210252337 | Devine et al. | Aug 2021 | A1 |
| 20210252341 | Devine et al. | Aug 2021 | A1 |
| 20210252369 | Devine et al. | Aug 2021 | A1 |
| 20210255747 | Devine et al. | Aug 2021 | A1 |
| 20210255758 | Devine et al. | Aug 2021 | A1 |
| 20210255826 | Devine et al. | Aug 2021 | A1 |
| 20210350900 | Blahnik et al. | Nov 2021 | A1 |
| 20210379447 | Lee | Dec 2021 | A1 |
| 20220047918 | Williams et al. | Feb 2022 | A1 |
| 20220062707 | Bedekar et al. | Mar 2022 | A1 |
| 20220121299 | De Vries et al. | Apr 2022 | A1 |
| 20220157184 | Wilson et al. | May 2022 | A1 |
| 20220160258 | Williams et al. | May 2022 | 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 |
| 101978374 | Feb 2011 | CN |
| 102339201 | Feb 2012 | CN |
| 102448555 | May 2012 | CN |
| 102804238 | Nov 2012 | CN |
| 102989159 | Mar 2013 | CN |
| 103154954 | Jun 2013 | CN |
| 103212197 | Jul 2013 | CN |
| 103370924 | Oct 2013 | CN |
| 103403627 | Nov 2013 | CN |
| 104288983 | Jan 2015 | CN |
| 104501043 | Apr 2015 | CN |
| 104508426 | Apr 2015 | CN |
| 104815428 | Aug 2015 | CN |
| 106537397 | Mar 2017 | CN |
| 106709235 | May 2017 | CN |
| 106878550 | Jun 2017 | CN |
| 1935339 | Jun 2008 | EP |
| 2025368 | Feb 2009 | EP |
| 3122038 | Jan 2017 | EP |
| 6-187118 | Jul 1994 | JP |
| 2001-76078 | Mar 2001 | JP |
| 2002-190007 | Jul 2002 | JP |
| 2003-102868 | Apr 2003 | 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 |
| 2007-330513 | Dec 2007 | JP |
| 2008-104758 | May 2008 | JP |
| 2008-183339 | Aug 2008 | JP |
| 2009-78134 | Apr 2009 | JP |
| 2009-112731 | May 2009 | JP |
| 2010-12335 | Jan 2010 | JP |
| 2010-517725 | May 2010 | JP |
| 2010-122901 | Jun 2010 | JP |
| 2010-162297 | Jul 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-020134 | Feb 2012 | JP |
| 2012-35071 | Feb 2012 | 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 |
| 2014-500740 | Jan 2014 | JP |
| 2016-502875 | Feb 2016 | JP |
| 2016-52512 | Apr 2016 | JP |
| 2016-517329 | Jun 2016 | JP |
| 2016-528016 | Sep 2016 | JP |
| 2016-177151 | Oct 2016 | JP |
| 2016-202751 | Dec 2016 | JP |
| 2017-134689 | Aug 2017 | JP |
| 2017-211994 | Nov 2017 | JP |
| 2017-532069 | Nov 2017 | JP |
| 10-2006-0117570 | Nov 2006 | KR |
| 10-2011-0017076 | Feb 2011 | KR |
| 10-2012-0023657 | Mar 2012 | KR |
| 10-2012-0076559 | Jul 2012 | KR |
| 10-2013-0043698 | May 2013 | KR |
| 10-2013-0111569 | Oct 2013 | KR |
| 10-2013-0111570 | Oct 2013 | KR |
| 10-2013-0135282 | Dec 2013 | KR |
| 10-2015-0026635 | Mar 2015 | KR |
| 10-2016-0027943 | Mar 2016 | KR |
| 10-2016-01424118 | Dec 2016 | KR |
| 10-2017-0003608 | Jan 2017 | KR |
| 10-2017-0029014 | Mar 2017 | KR |
| 10-2017-0032471 | Mar 2017 | KR |
| 10-2019-0141702 | Dec 2019 | KR |
| 199941682 | Aug 1999 | WO |
| 200227530 | Apr 2002 | WO |
| 2005070289 | Aug 2005 | WO |
| 2009129402 | Oct 2009 | WO |
| 2010126825 | Nov 2010 | WO |
| 2012021507 | Feb 2012 | WO |
| 2012061438 | May 2012 | WO |
| 2012061440 | May 2012 | WO |
| 2012078079 | Jun 2012 | WO |
| 2012086910 | Jun 2012 | WO |
| 2013052789 | Apr 2013 | WO |
| 2013109762 | Jul 2013 | WO |
| 2013109777 | Jul 2013 | WO |
| 2013109916 | Jul 2013 | WO |
| 2013169870 | Nov 2013 | WO |
| 2013173838 | Nov 2013 | WO |
| 2014200730 | Dec 2014 | WO |
| 2014207294 | Dec 2014 | WO |
| 2015027133 | Feb 2015 | WO |
| 2015179592 | Nov 2015 | WO |
| 2015198488 | Dec 2015 | WO |
| 2016022203 | Feb 2016 | WO |
| 2016036472 | Mar 2016 | WO |
| 2016036582 | Mar 2016 | WO |
| 2017037242 | Mar 2017 | WO |
| 2018213066 | Nov 2018 | WO |
| 2018222313 | Dec 2018 | WO |
| 2019017508 | Jan 2019 | WO |
| 2019024603 | Feb 2019 | WO |
| 2019183422 | Sep 2019 | WO |
| 2019217249 | Nov 2019 | WO |
| 2019231982 | Dec 2019 | WO |
| Entry |
|---|
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/888,629, dated Aug. 4, 2021, 5 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/994,352, dated Jul. 30, 2021, 11 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2020-000492, dated Jul. 16, 2021,4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Final Office Action received for U.S. Appl. No. 17/031,859, dated Apr. 16, 2021, 14 pages. |
| Final Office Action received for U.S. Appl. No. 17/031,874, dated Apr. 16, 2021, 17 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2019-162293, dated Apr. 9, 2021, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for U.S. Appl. No. 16/138,809, dated Apr. 16, 2021, 11 pages. |
| Office Action received for Danish Patent Application No. PA202170113, dated Apr. 15, 2021, 2 pages. |
| 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. 14/732,773, dated Nov. 9, 2018, 6 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. 16/144,849, dated Aug. 12, 2019, 5 pages. |
| Advisory Action received for U.S. Appl. No. 16/144,864, dated Jul. 29, 2019, 6 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. |
| 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. |
| 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/705,849, dated Feb. 14, 2020, 3 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/144,849, dated Jan. 21, 2020, 6 pages. |
| Certificate of Examination received for Australian Patent Application No. 2018100158, dated Oct. 23, 2018, 2 pages. |
| Certificate of Examination received for Australian Patent Application No. 2018101855, dated Aug. 6, 2019, 2 pages. |
| 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: <https://x-blueuv.blogspot.com/2013/12/fitbit-force.html>, Dec. 3, 2013, 8 pages. |
| CNET, “Google Fit's automatic activity tracking is getting smarter on Android Wear”, Available online at: https://www.youtube.com/watch?v=lttzlCid_d8, May 18, 2016, 1 page. |
| 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. |
| 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. 15/183,663, dated Feb. 25, 2019, 3 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 15/183,663, dated Mar. 27, 2019, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 15/600,243, dated Feb. 5, 2020, 3 pages. |
| 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. 15/600,243, dated Mar. 31, 2020, 5 pages. |
| DC Rainmaker, “Garmin Fenix3 New Auto Climb Functionality”, Available online at: https://www.youtube.com/watch?v=iuavOSNpVRc, Feb. 19, 2015, 1 page. |
| Decision to Grant received for Danish Patent Application No. PA201870379, dated Jul. 5, 2019, 2 pages. |
| 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. |
| “DwProgressBarv2: Stepping and Events”, davidwalsh.name/dwprogressbar-2-stepping-events-mootools-progress-bar, retrieved from the Wayback Machine, Aug. 31, 2008, 4 pages. |
| Evergreen et al., “Bar Chart”, Better Evaluation, Available Online at: https://www.betterevaluation.org/en/evaluation-options/BarChart, Oct. 31, 2014, 8 pages. |
| Extended European Search Report received for European Patent Application No. 16837432.0, dated Mar. 11, 2019, 10 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/732,773, dated Jun. 21, 2019, 32 pages. |
| Final Office Action received for U.S. Appl. No. 14/839,922, dated Dec. 14, 2016, 22 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/627,069, dated Mar. 2, 2020, 22 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/144,849, dated Jun. 7, 2019, 29 pages. |
| Final Office Action received for U.S. Appl. No. 16/144,864, dated May 17, 2019, 24 pages. |
| “Fitbit App”, Available online at Khttp://web.archive.org/web/20180114083150/https://www.fitbit.com/au/app>, Jan. 14, 2018, 8 pages. |
| Garmin, “Fenix 5x Owner's Manual”, Online Available at: https://web.archive.org/web/20180127170640/https://static.garmin.com/pumac/fenix5x_OM_EN.pdf, Jan. 27, 2018, 42 pages. |
| “Graphs and Charts”, Online available at: <https://www.teachervision.com/lesson-planning/graph-chart-teacher-resources, retrieved on Dec. 12, 2018, 4 pages. |
| Intention to Grant received for Danish Patent Application No. PA201570668, dated Mar. 27, 2017, 2 pages. |
| Intention to Grant received for Danish Patent Application No. PA201870379, dated May 2, 2019, 2 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2013/073195, dated Jun. 16, 2016, 10 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2015/047282, dated Mar. 16, 2017, 26 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/US2017/035554, dated Dec. 20, 2018, 39 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2018/031662, dated Nov. 28, 2019, 12 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 and Written Opinion received for PCT Patent Application No. PCT/US2018/031662, dated Sep. 27, 2018, 17 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2019/024570, dated Aug. 8, 2019, 18 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 Addition Fees and Partial International Search Report received for PCT Patent Application No. PCT/US2018/031662, dated Jul. 16, 2018, 13 pages. |
| Invitation to Pay 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, dated Sep. 11, 2018, 3 pages. |
| Minutes of Oral Proceedings received for European Patent Application No. 15771747.1, dated Aug. 10, 2018, 11 pages. |
| “Mugs”, Online Available at: https://web.archive.org/web/20151029034349/http://le-mugs.com/, Oct. 29, 2015, 14 pages. |
| “Multi-Set Bar Chart”, The Data Visualization Catalogue, Available Online at: https://datavizcatalogue.com/methods/multiset_barchart.html, Feb. 8, 2014, 3 pages. |
| “My CalStep”, http://www.surprisesoftware.com/mycalstep/, Retrieved 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 Feb. 8, 2019, 32 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. |
| 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/608,848, dated Feb. 6, 2020, 12 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. 15/705,849, dated Nov. 12, 2019, 15 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/138,809, dated Feb. 28, 2020, 22 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/144,735, dated Feb. 19, 2020, 10 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/144,753, dated Mar. 5, 2020, 9 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/144,849, dated Dec. 31, 2018, 28 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/144,849, dated Sep. 17, 2019, 9 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/144,864, dated Dec. 18, 2018, 19 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/144,864, dated Jan. 31, 2020, 29 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2015312215, dated Oct. 9, 2017, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2019201583, dated Jul. 15, 2019, 3 pages. |
| Notice of Allowance received for Chinese Patent Application No. 201580037927.5, dated Oct. 17, 2019, 3 pages. |
| Notice of Allowance received for Chinese Patent Application No. 201810105846.X, dated Feb. 18, 2020, 2 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. |
| Notice of Allowance received for Japanese Patent Application No. 2016-557650, dated Apr. 9, 2019, 4 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2018-068846, dated Dec. 9, 2019, 4 pages. |
| Notice of Allowance received for Korean Patent Application No. 10-2016-7014577, dated May 30, 2019, 5 pages. |
| Notice of Allowance received for Korean Patent Application No. 10-2016-7033638, dated May 31, 2017, 5 pages. |
| Notice of Allowance received for Taiwanese Patent Application No. 104128685, dated May 3, 2017, 3 pages. |
| 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/732,773, dated Dec. 18, 2019, 21 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. |
| Notice of Allowance received for U.S. Appl. No. 15/183,663, dated Jan. 17, 2019, 6 pages. |
| Notice of Allowance received for U.S. Appl. No. 15/600,243, dated Dec. 12, 2019, 7 pages. |
| Notice of Allowance received for U.S. Appl. No. 15/616,480, dated Jan. 3, 2019, 8 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/144,671, dated Feb. 10, 2020, 17 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/144,849, dated Mar. 6, 2020, 9 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. 2018101855, dated Feb. 22, 2019, 4 pages. |
| Office Action received for Australian Patent Application No. 2018200428, dated Mar. 7, 2018, 4 pages. |
| Office Action received for Australian Patent Application No. 2018200428, dated Nov. 15, 2018, 4 pages. |
| Office Action received for Australian Patent Application No. 2019100495, dated Mar. 6, 2020, 3 pages. |
| Office Action received for Australian Patent Application No. 2019100495, dated Sep. 17, 2019, 7 pages. |
| Office Action received for Australian Patent Application No. 2019222943, dated Oct. 3, 2019, 3 pages. |
| Office Action received for Chinese Patent Application No. 201380081349.6, dated Feb. 26, 2019, 12 pages. |
| Office Action received for Chinese Patent Application No. 201380081349.6, dated Jan. 16, 2020, 11 pages. |
| Office Action received for Chinese Patent Application No. 201380081349.6, dated Jul. 15, 2019, 10 pages. |
| Office Action received for Chinese Patent Application No. 201580037927.5, dated Apr. 22, 2019, 9 pages. |
| Office Action received for Chinese Patent Application No. 201580037927.5, dated Jul. 20, 2018, 21 pages. |
| Office Action received for Chinese Patent Application No. 201680047983.1, dated Mar. 18, 2019, 18 pages. |
| Office Action received for Chinese Patent Application No. 201680047983.1, dated Nov. 28, 2019, 9 pages. |
| Office Action received for Chinese Patent Application No. 201810105846.X, dated Aug. 27, 2019, 12 pages. |
| Office Action received for Chinese Patent Application No. 201810105846.X, dated Feb. 25, 2019, 10 pages. |
| Office Action received for Chinese Patent Application No. 201810105846.X, dated Nov. 28, 2019, 9 pages. |
| 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 2, 2019, 4 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. PA201770191, dated Nov. 21, 2018, 4 pages. |
| Office Action received for Danish Patent Application No. PA201770191, dated Oct. 25, 2019, 4 pages. |
| Office Action received for Danish Patent Application No. PA201770423, dated Jun. 12, 2018, 7 pages. |
| Office Action received for Danish Patent Application No. PA201770423, dated Mar. 29, 2019, 6 pages. |
| Office Action received for Danish Patent Application No. PA201870378, dated Feb. 25, 2019, 3 pages. |
| Office Action received for Danish Patent Application No. PA201870378, dated Jan. 6, 2020, 3 pages. |
| Office Action received for Danish Patent Application No. PA201870379, dated Feb. 28, 2019, 3 pages. |
| Office Action received for Danish Patent Application No. PA201870380, dated Mar. 5, 2020, 2 pages. |
| Office Action received for Danish Patent Application No. PA201870380, dated Mar. 27, 2019, 4 pages. |
| Office Action received for Danish Patent Application No. PA201870380, dated Sep. 11, 2018, 9 pages. |
| Office Action received for 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. 16837432.0, dated Jan. 10, 2020, 7 pages. |
| Office Action received for European Patent Application No. 17810749.6, dated Aug. 20, 2019, 9 pages. |
| Office Action received for European Patent Application No. 18154145.9, dated Apr. 3, 2018, 6 pages. |
| Office Action received for European Patent Application No. 19721883.7, dated Jan. 10, 2020, 4 pages. |
| Office Action received for German Patent Application No. 112015002326.7, dated Feb. 20, 2019, 7 pages. |
| Office Action received for Japanese Patent Application No. 2016-535045, dated May 12, 2017, 10 pages. |
| Office Action received for Japanese Patent Application No. 2016-557650, dated Apr. 13, 2018, 9 pages. |
| Office Action received for Japanese Patent Application No. 2016-557650, dated Aug. 10, 2017, 10 pages. |
| Office Action received for Japanese Patent Application No. 2016-557650, dated Nov. 9, 2018, 6 pages. |
| Office Action received for Japanese Patent Application No. 2018-014096, dated Jan. 6, 2020, 17 pages. |
| Office Action received for Japanese Patent Application No. 2018-014096, dated Jun. 29, 2018, 20 pages. |
| Office Action received for Japanese Patent Application No. 2018-014096, dated May 8, 2019, 14 pages. |
| Office Action received for Japanese Patent Application No. 2018-014096, dated Nov. 6, 2018, 15 pages. |
| Office Action received for Japanese Patent Application No. 2018-068846, dated Jan. 8, 2019, 6 pages. |
| Office Action received for Japanese Patent Application No. 2019-162293, dated Jan. 31, 2020, 8 pages. |
| Office Action received for Korean Patent Application No. 10-2016-7014577, dated Dec. 26, 2017, 14 pages. |
| Office Action received for Korean Patent Application No. 10-2016-7014577, dated Oct. 31, 2018, 11 pages. |
| Office Action received for Korean Patent Application No. 10-2016-7033638, dated Jan. 31, 2017, 6 pages. |
| Office Action received for Korean Patent Application No. 10-2019-7025538, dated Feb. 17, 2020, 12 pages. |
| Office Action received for Korean Patent Application No. 10-2019-7025781, dated Nov. 26, 2019, 10 pages. |
| Office Action received forTaiwanese Patent Application No. 104128685, dated Jan. 4, 2017, 40 pages. |
| Partial Supplementary European Search Report received for European Patent Application No. 17810749.6, dated Apr. 25, 2019, 8 pages. |
| Razykdreviews, “In Depth Review of Apple Watch Activity and Workout App”, available at <URL: https://www.youtube.com/watch?v=GkKl3qlK0ow>, Category: X Claims: 1-5 Category: L Reason: Internet citation/video, May 11, 2015, 1 page. |
| Rizknows, “Garmin Connect Mobile App—Review #2”, https://www.youtube.com/watch?v=7my3wMpeRbE, Category: X Claims: 1-5 Category: L Reason: Internet citation/video, Oct. 22, 2015, 1 page. |
| Rizknows, “Tom Tom Multisport Cardio Review”, Online available at: https://www.youtube.com/watch?v=WoVCzLrSN9A, Sep. 4, 2015, 1 page. |
| 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. |
| 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. |
| Smith, “Garmin Fenix 5 Activity/Smart Watch Review”, Online Available at: https://www.youtube.com/watch?v=6PkQxXQxpoU, Sep. 2, 2017, 1 page. |
| Sportstechguides, “Garmin Fenix 5: How to Add Power Data Fields”, Online Available at: https://www.youtube.com/watch?v=ZkPptnnXEiQ, Apr. 29, 2017, 2 pages. |
| Sportstechguides, “Garmin Fenix 5: How To Set Up Run Alerts”, Online Available at: https://www.youtube.com/watch?v=gSMwv8vlhB4, May 13, 2017, 2 pages. |
| Summons to Attend Oral Proceedings received for European Patent Application No. 13811085.3, dated Jan. 26, 2018, 14 pages. |
| Summons to Attend Oral Proceedings received for European Patent Application No. 15771747.1, dated May 25, 2018, 17 pages. |
| Supplemental Notice of Allowance received for U.S. Appl. No. 15/616,480, dated Mar. 28, 2019, 2 pages. |
| Supplementary European Search Report received for European Patent Application No. 17810749.6, dated Aug. 6, 2019, 6 pages. |
| “Suunto Spartan Trainer Wrist HR 1.12”, Online Available at:- https://web.archive.org/web/20180127155200/https://ns.suunto.com/Manuals/Spartan_Trainer_WristHR/Userguides/Suunto_Spartan_Trainer_WristHR_UserGuide_EN.pdf, Jan. 17, 2018, 47 pages. |
| Suunto, “Suunto Spartan—Heart Rate Zones”, Online Available at https://www.youtube.com/watch?v=aixfoCnSOOU, Mar. 19, 2018, 2 pages. |
| Teunmo, “Data field: Visual Pace Alarm”, Garmin Forum; Available online at: https://forums.garmin.com/forum/developers/connect-iq/connect-iq-showcase/115996-data-field-visual-pace-alarm, Nov. 17, 2015, 10 pages. |
| Tomtom, “TomTom Runner & Multi-Sport Reference Guide”, Online available at: https://web.archive.org/web/20150908075934/http://download.tomtom.com/open/manuals/Runner_Multi-Sport/refman/TomTom-Runner-Multi-Sport-RG-en-GB.pdf, Sep. 8, 2015, 44 pages. |
| “Utilization of Galaxy S4—S Health”, ChatOn and Samsung Hub, Available at http://seeit.kr/1263, Jun. 12, 2013, 25 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. |
| Wesley, “Apple Watch Series 1”, Online available at: http://tool-box.info/blog/archives/1737-unknown.html, May 28, 2015, 5 pages. |
| Youtube, “Apple Watch Series 3”, Online available at: https://www.youtube.com/watch?v=iBPr9gEfkK8, Nov. 21, 2017, 15 pages. |
| Zlelik, “Garmin Fenix 5 Open Water Swimming Activity Demo”, Online Available at: https://www.youtube.com/watch?v=iSVhdvw2dcs, Jun. 9, 2017, 1 page. |
| Non-Final Office Action received for U.S. Appl. No. 17/192,161, dated May 13, 2021, 28 pages. |
| Notice of Allowance received for Chinese Patent Application No. 201680047983.1, dated Apr. 28, 2021, 3 pages (1 page of English Translation and 2 pages of Official Copy). |
| Notice of Allowance received for U.S. Appl. No. 16/377,892, dated May 24, 2021, 9 pages. |
| Summons to Oral Proceedings received for European Patent Application No. 15771747.1, dated Apr. 29, 2021, 8 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. |
| 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/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. |
| 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. 16/144,864, dated Sep. 29, 2020, 2 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/820,383, dated Mar. 11, 2021, 2 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2019250251, dated Feb. 18, 2021, 3 pages. |
| Notice of Allowance received for U.S. Appl. No. 15/925,652, dated Mar. 9, 2021, 9 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/144,864, dated Mar. 12, 2021, 2 pages. |
| Office Action received for Chinese Patent Application No. 202010606407.4, dated Jan. 27, 2021, 16 pages (7 pages of English Translation and 9 pages of Official Copy). |
| Office Action received for Japanese Patent Appiication No. 2019-563407, dated Feb. 5, 2021, 5 pages (2 pages of English Translation and 3 pages of Official Copy). |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/894,309, dated Jun. 25, 2021, 4 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/031,859, dated Jun. 30, 2021, 4 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/031,874, dated Jun. 30, 2021, 4 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/192,161, dated Jun. 29, 2021, 4 pages. |
| Decision to Grant received for Danish Patent Application No. PA201670656, dated Jun. 21, 2021, 2 pages. |
| Decision to Grant received for German Patent Application No. 112015002326.7, dated Jun. 15, 2021, 10 pages (1 page of English Translation and 9 pages of Official Copy). |
| European Search Report received for European Patent Application No. 21165295.3, dated Jun. 18, 2021, 4 pages. |
| Notice of Allowance received for U.S. Appl. No. 15/627,069, dated Jun. 17, 2021, 14 pages. |
| Office Action received for Chinese Patent Application No. 202010606407.4, dated Jun. 2, 2021, 12 pages (5 pages of English Translation and 7 pages of Official Copy). |
| Office Action received for European Patent Application No. 19721883.7, dated Jun. 15, 2021, 9 pages. |
| Office Action received for European Patent Application No. 21165295.3, dated Jul. 1, 2021, 10 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. |
| Non-Final Office Action received for U.S. Appl. No. 15/608,848, dated Feb. 12, 2021, 14 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/144,753, dated Feb. 10, 2021, 8 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/144,864, dated Feb. 9, 2021, 13 pages. |
| Supplemental Notice of Allowance received for U.S. Appl. No. 15/925,652, dated Feb. 17, 2021, 3 pages. |
| CBS This Morning, “This smart mirror puts a personal trainer in your reflection”, Available at: https://www.youtube.com/watch?v=nSmTTZcpVGg, Oct. 13, 2018, 4 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/377,892, dated Sep. 9, 2021, 9 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/378,136, dated Sep. 22, 2021, 7 pages. |
| Office Action received for Australian Patent Application No. 2020239743, dated Sep. 3, 2021, 4 pages. |
| Office Action received for Japanese Patent Application No. 2019-044107, dated Jul. 30, 2021, 9 pages (5 pages of English Translation and 4 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2021-7026284, dated Aug. 31, 2021, 10 pages (4 pages of English Translation and 6 pages of Official Copy). |
| 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. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/144,753, dated Nov. 4, 2020, 3 pages. |
| European Search Report received for European Patent Application No. 20182116.2, dated Oct. 21, 2020, 4 pages. |
| Final Office Action received for U.S. Appl. No. 15/627,069, dated Oct. 20, 2020, 25 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/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). |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/138,809, dated Dec. 16, 2020, 7 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). |
| 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. |
| Advisory Action received for U.S. Appl. No. 16/377,892, dated Apr. 9, 2021, 4 pages. |
| Advisory Action received for U.S. Appl. No. 16/378,136, dated Apr. 12, 2021, 4 pages. |
| Applicant Initiated Interview Summary received for U.S. Appl. No. 15/608,848, dated Apr. 13, 2021, 4 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2021200787, dated Mar. 19, 2021, 3 pages. |
| Office Action received for Japanese Patent Application No. 2018-184532, dated Mar. 1, 2021, 11 pages (6 pages of English Translation and 5 pages of Official Copy). |
| Communication of the Board of Appeal received for European Patent Application No. 15771747.1, dated Aug. 25, 2021, 9 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2019-563407, dated Aug. 20, 2021, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for Korean Patent Application No. 10-2020-7026035, dated Aug. 23, 2021, 4 pages (2 page of English Translation and 2 pages of Official Copy). |
| Office Action received for Australian Patent Application No. 2020239748, dated Sep. 1, 2021, 4 pages. |
| Office Action received for European Patent Application No. 21168916.1, dated Aug. 23, 2021, 8 pages. |
| 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-review-3849>, 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. |
| 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, “Howto Log in to PS4 Automatically with Particular User?”, Online available on: - https://www.youtube.com/watch?v=kqdlzXAvOkY, May 30, 2018, 3 pages. |
| Yoyodavid, “Howto Use Multiple Accounts on the PlayStation 4”, Online available at: -https://www.youtube.com/watch?v=5V21obRMeKE, Jan. 9, 2014, 3 pages. |
| Final Office Action received for U.S. Appl. No. 16/144,753, dated Sep. 22, 2020, 9 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. |
| Notice of Allowance received for U.S. Appl. No. 16/144,864, dated Sep. 10, 2020, 3 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/144,864, dated Sep. 16, 2020, 2 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/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 Danish Patent Application No. PA201970532, dated May 29, 2020, 3 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). |
| Search Report and Opinion received for Danish Patent Application No. PA201970532, dated Nov. 8, 2019, 9 pages. |
| Summons to Attend Oral Proceedings received for European Patent Application No. 18154145.9, dated 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. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/192,161, dated Sep. 29, 2021, 3 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/820,383, dated Oct. 5, 2021, 2 pages. |
| Final Office Action received for U.S. Appl. No. 17/030,318, dated Sep. 30, 2021, 28 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2021/017736, dated Sep. 2, 2021,25 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/418,786, dated Oct. 4, 2021, 10 pages. |
| Office Action received for Danish Patent Application No. PA202070613, dated Sep. 30, 2021, 4 pages. |
| Office Action received for Danish Patent Application No. PA202070614, dated Sep. 28, 2021, 4 pages,. |
| Applicant Initiated Interview Summary received for U.S. Appl. No. 17/030,318, dated Jul. 30, 2021, 4 pages. |
| Applicant Initiated Interview Summary received for U.S. Appl. No. 17/030,321, dated Jul. 30, 2021, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/377,892, dated Aug. 11, 2021, 3 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/378,136, dated Aug. 11, 2021, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/820,383, dated Aug. 13, 2021, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/820,383, dated Aug. 19, 2021, 2 pages. |
| Final Office Action received for U.S. Appl. No. 17/030,321, dated Apr. 2, 2021, 28 pages. |
| Final Office Action received for U.S. Appl. No. 17/192,161, dated Aug. 16, 2021, 22 pages. |
| Gym Book—Strength Training Planner, Logger and Analyzer, GymBookApp, Available Online at: https://web.archive.org/web/20160401104508/https://gymbookapp.com/, Apr. 1, 2016, 10 pages. |
| Invitation to Pay Additional Fees received for PCT Patent Application No. PCT/US2021/017736, dated Jun. 15, 2021, 14 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/030,318, dated Apr. 2, 2021, 28 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/030,318, dated Dec. 3, 2020, 22 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/030,321, dated Dec. 15, 2020, 25 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2020256383, dated Aug. 3, 2021, 3 pages. |
| Notice of Allowance received for U.S. Appl. No. 15/608,848, dated Aug. 25, 2021, 9 pages. |
| Office Action received for Australian Patent Application No. 2020239743, dated Mar. 25, 2021, 8 pages. |
| Office Action received for Australian Patent Application No. 2020239748, dated Apr. 21, 2021, 6 pages. |
| Office Action received for Australian Patent Application No. 2020239752, dated Jun. 4, 2021, 8 pages. |
| Office Action received for Chinese Patent Application No. 201780034203.4, dated Jul. 14, 2021, 12 pages (5 pages of English Translation and 7 pages of Official Copy). |
| Search Report and Opinion received for Danish Patent Application No. PA202070612, dated Jun. 7, 2021, 9 pages. |
| Search Report and Opinion received for Danish Patent Application No. PA202070613, dated Jan. 22, 2021, 9 pages. |
| Search Report and Opinion received for Danish Patent Application No. PA202070615, dated Jan. 22, 2021, 9 pages. |
| Search Report and Opinion received for Danish Patent Application No. PA202070616, dated Feb. 3, 2021, 8 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. |
| Invitation to Pay Additional Fees received for PCT Patent Application No. PCT/US2020/035199, dated Sep. 8, 2020, 12 pages. |
| Notice of Allowance received for U.S. Appl. No. 15/925,652, dated Nov. 20, 2020, 9 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. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/378,136, dated Jun. 11, 2021, 2 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/378,136, dated Jun. 3, 2021, 7 pages. |
| Office Action received for Australian Patent Application No. 2020256383, dated Jun. 4, 2021, 3 pages. |
| Office Action received for European Patent Application No. 20182116.2, dated May 25, 2021, 9 pages. |
| Office Action received for Japanese Patent Application No. 2020-115940, dated May 7, 2021, 3 pages (1 page of English Translation and 2 pages of Official Copy). |
| European Search Report received for European Patent Application No. 21168916.1, dated Jul. 14, 2021, 5 pages. |
| Notice of Allowance received for Korean Patent Application No. 10-2019-7025781, dated Jun. 29, 2021, 5 pages (2 pages of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for Korean Patent Application No. 10-2019-7033834, dated Jul. 3, 2021, 4 pages (2 page of English Translation and 2 pages of Official Copy). |
| Notice of Allowance received for U.S. Appl. No. 16/138,809, dated Jul. 20, 2021, 6 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/820,383, dated Jul. 21, 2021, 11 pages. |
| Office Action received for Chinese Patent Application No. 201380081349.6, dated Jun. 2, 2021, 17 pages (8 pages of English Translation and 9 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 201910858933.7, dated Jun. 29, 2021, 8 pages (3 pages of English Translation and 5 pages of Official Copy). |
| Supplemental Notice of Allowance received for U.S. Appl. No. 15/627,069, dated Jul. 12, 2021, 2 pages. |
| Final Office Action received for U.S. Appl. No. 17/192,161, dated Oct. 18, 2021, 22 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/030,321, dated Oct. 18, 2021, 28 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2020-115940, dated Oct. 22, 2021, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for U.S. Appl. No. 15/608,848, dated Oct. 29, 2021, 7 pages. |
| Office Action received for Australian Patent Application No. 2020239752, dated Oct. 25, 2021, 5 pages. |
| Office Action received for Chinese Patent Application No. 201780034203.4, dated Sep. 24, 2021, 7 pages (3 pages of English Translation and 4 pages of Official Copy). |
| Office Action received for Danish Patent Application No. PA202070815, dated Oct. 18, 2021, 2 pages. |
| Office Action received for Korean Patent Application No. 10-2021-7031939, dated Oct. 19, 2021, 11 pages (5 pages of English Translation and 6 pages of Official Copy). |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/031,859, dated Feb. 26, 2021, 4 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/031,874, dated Feb. 26, 2021, 4 pages. |
| Decision to Refuse received for European Patent Application No. 18154145.9, dated Feb. 17, 2021, 20 pages. |
| Final Office Action received for U.S. Appl. No. 16/894,309, dated Feb. 24, 2021, 30 pages. |
| Minutes of the Oral Proceedings received for European Patent Application No. 18154145.9, dated Feb. 12, 2021, 8 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2017277971, dated Feb. 17, 2021, 3 pages. |
| Office Action received for Chinese Patent Application No. 201380081349.6, dated Jan. 5, 2021, 16 pages (7 pages of English Translation and 9 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 201680047983.1, dated Feb. 1, 2021, 6 pages (3 pages of English Translation and 3 pages of Official Copy). |
| 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). |
| 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. |
| Advisory Action received for U.S. Appl. No. 16/144,864, dated Jul. 6, 2020, 6 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 15/608,848, dated May 12, 2020, 5 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/144,735, dated Jun. 18, 2020, 3 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/144,753, dated Jun. 18, 2020, 3 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/144,864, dated Apr. 29, 2020, 4 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/144,864, dated Jun. 22, 2020, 3 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 14/732,773, dated Mar. 24, 2020, 3 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. |
| 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. 15/705,849, dated May 1, 2020, 17 pages. |
| Final Office Action received for U.S. Appl. No. 16/138,809, dated Aug. 27, 2020, 24 pages. |
| Final Office Action received for U.S. Appl. No. 16/144,735, dated May 4, 2020, 12 pages. |
| Final Office Action received for U.S. Appl. No. 16/144,864, dated May 28, 2020, 29 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/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/418,786, dated Apr. 24, 2020, 16 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2019222943, dated May 5, 2020, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2020204153, dated Jul. 6, 2020, 3 pages. |
| Notice of Allowance received for 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/144,849, dated Apr. 17, 2020, 2 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/144,864, dated Jul. 28, 2020, 27 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. 2019100495, dated Mar. 16, 2020, 3 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. 201710439448.7, dated Mar. 27, 2020, 13 pages (7 pages of English Translation and 6 pages of Official Copy). |
| 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 Danish Patent Application No. PA201670656, dated Jul. 1, 2020, 4 pages. |
| Office Action received for European Patent Application No. 19721883.7, dated May 28, 2020, 11 pages. |
| 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). |
| 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). |
| 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). |
| Result of Consultation received for European Patent Application No. 18154145.9, dated Sep. 4, 2020, 3 pages. |
| Summons to Attend Oral Proceedings received for European Patent Application No. 17810749.6, dated Aug. 12, 2020, 11 pages. |
| Supplemental Notice of Allowance received for U.S. Appl. No. 16/144,849, dated Mar. 31, 2020, 2 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/377,892, dated Mar. 26, 2021, 2 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/378,136, dated Mar. 26, 2021, 2 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/418,786, dated Mar. 30, 2021, 4 pages. |
| Decision on Appeal received for Korean Patent Application No. 10-2019-7025538, dated Feb. 24, 2021, 20 pages (4 pages of English Translation and 16 pages of Official Copy). |
| Non-Final Office Action received for U.S. Appl. No. 16/888,629, dated Mar. 31, 2021, 14 pages. |
| Notice of Allowance received for Korean Patent Application No. 10-2019-7025538, dated Mar. 10, 2021, 5 pages (2 pages of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for U.S. Appl. No. 16/144,864, dated Mar. 30, 2021, 2 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/820,383, dated Mar. 31, 2021, 11 pages. |
| Office Action received for European Patent Application No. 18727543.3, dated Mar. 26, 2021, 7 pages. |
| Search Report and Opinion received for Danish Patent Application No. PA202070815, dated Mar. 16, 2021, 8 pages. |
| Applicant Initiated Interview Summary received for U.S. Appl. No. 16/994,352, dated Nov. 2, 2021, 4 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/888,629, dated Nov. 9, 2021, 11 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/894,309, dated Nov. 5, 2021, 12 pages. |
| Office Action received for European Patent Application No. 20721342.2, dated Nov. 4, 2021, 9 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 17/157,728, dated Apr. 4, 2022, 3 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/031,543, dated Apr. 1, 2022, 9 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/381,570, dated Apr. 1, 2022, 29 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2021201130, dated Mar. 28, 2022, 3 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2020-160054, dated Apr. 4, 2022, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for Korean Patent Application No. 10-2021-7031939, dated Apr. 5, 2022, 5 pages (1 page of English Translation and 4 pages of Official Copy). |
| Notice of Allowance received for U.S. Appl. No. 17/030,321, dated Apr. 1, 2022, 8 pages. |
| Office Action received for Australian Patent Application No. 2021203636, dated Mar. 23, 2022, 3 pages. |
| Supplemental Notice of Allowance received for U.S. Appl. No. 16/894,309, dated Apr. 8, 2022, 3 pages. |
| Supplemental Notice of Allowance received for U.S. Appl. No. 17/030,318, dated Apr. 4, 2022, 2 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2020/025997, dated Nov. 18, 2021, 10 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/157,728, dated Nov. 26, 2021, 18 pages. |
| Office Action received for Danish Patent Application No. PA202070615, dated Nov. 16, 2021, 4 pages. |
| Office Action received for European Patent Application No. 20203526.7, dated Nov. 23, 2021, 9 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 17/192,161, dated Mar. 23, 2022, 2 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/418,786, dated Mar. 28, 2022, 14 pages. |
| Notice of Allowance received for Australian Patent Application No. 2020239748, dated Mar. 7, 2022, 3 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/197,628, dated Mar. 23, 2022, 35 pages. |
| Supplemental Notice of Allowance received for U.S. Appl. No. 17/030,318, dated Mar. 16, 2022, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/888,629, dated Jan. 21, 2022, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 17/030,318, dated Jan. 24, 2022, 2 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/031,874, dated Jan. 24, 2022, 18 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2020239743, dated Jan. 13, 2022, 3 pages. |
| Notice of Allowance received for Chinese Patent Application No. 201780034203.4, dated Jan. 17, 2022, 2 pages (1 page of English Translation and 1 page of Official Copy). |
| Notice of Allowance received for Chinese Patent Application No. 202010606407.4, dated Jan. 24, 2022, 2 pages (1 page of English Translation and 1 page of Official Copy). |
| Notice of Allowance received for Japanese Patent Application No. 2018-184532, dated Jan. 17, 2022, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Office Action received for Japanese Patent Application No. 2020-160054, dated Jan. 21, 2022, 8 pages (4 pages of English Translation and 4 pages of Official Copy). |
| Supplemental Notice of Allowance received for U.S. Appl. No. 16/894,309, dated Jan. 25, 2022, 2 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/031,854, dated Feb. 25, 2022, 5 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/031,859, dated Feb. 25, 2022, 4 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/031,874, dated Feb. 25, 2022, 4 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/894,309, dated Feb. 25, 2022, 9 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/994,352, dated Mar. 2, 2022, 14 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/157,728, dated Feb. 24, 2022, 7 pages. |
| Office Action received for Australian Patent Application No. 2020239748, dated Feb. 11, 2022, 2 pages. |
| Office Action received for Chinese Patent Application No. 201910858933.7, dated Dec. 30, 2021, 9 pages (4 pages of English Translation and 5 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 201911401161.0, dated Jan. 24, 2022, 6 pages (3 pages of English Translation and 3 pages of Official Copy). |
| Supplemental Notice of Allowance received for U.S. Appl. No. 17/030,318, dated Feb. 22, 2022, 2 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/157,728, dated Feb. 3, 2022, 5 pages. |
| Intention to Grant received for Danish Patent Application No. PA202070615, dated Jan. 27, 2022, 2 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2020239752, dated Jan. 31, 2022, 3 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/192,161, dated Feb. 16, 2022, 8 pages. |
| Office Action received for Australian Patent Application No. 2021201130, dated Jan. 27, 2022, 2 pages. |
| Office Action received for Danish Patent Application No. PA202070616, dated Jan. 27, 2022, 2 pages. |
| Office Action received for Japanese Patent Application No. 2020-160053, dated Jan. 31, 2022, 8 pages (4 pages of English Translation and 4 pages of Official Copy). |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/192,161, dated Dec. 24, 2021, 4 pages. |
| Decision of Appeal received for European Patent Application No. 15771747.1, dated Dec. 14, 2021, 21 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2020/035199, dated Dec. 16, 2021, 14 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/031,859, dated Dec. 24, 2021, 16 pages. |
| Notice of Allowance received for Chinese Patent Application No. 201380081349.6, dated Dec. 17, 2021, 2 pages (1 page of English Translation and 1 page of Official Copy). |
| Notice of Allowance received for Korean Patent Application No. 10-2021-7038005, dated Dec. 14, 2021, 4 pages (2 pages of English Translation and 2 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 202010606407.4, dated Nov. 18, 2021, 6 pages (3 pages of English Translation and 3 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 202110363565.6, dated Nov. 16, 2021, 16 pages (9 pages of English Translation and 7 pages of Official Copy). |
| Office Action received for Indian Patent Application No. 202014041571, dated Dec. 17, 2021, 5 pages. |
| Office Action received for Japanese Patent Application No. 2020-160052, dated Dec. 17, 2021, 10 pages (5 pages of English Translation and 5 pages of Official Copy). |
| Search Report and Opinion received for Danish Patent Application No. PA202170113, dated Nov. 30, 2021, 9 pages. |
| Summons to Attend Oral Proceedings received for European Patent Application No. 20182116.2, dated Dec. 21, 2021, 7 pages. |
| Supplemental Notice of Allowance received for U.S. Appl. No. 16/894,309, dated Dec. 24, 2021, 2 pages. |
| Final Office Action received for U.S. Appl. No. 16/994,352, dated Dec. 6, 2021, 14 pages. |
| Minutes of the Oral Proceedings received for European Patent Application No. 15771747.1, dated Dec. 1, 2021, 4 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/418,786, dated Dec. 9, 2021, 9 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/418,786, dated Jan. 5, 2022, 3 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/820,383, dated Jan. 10, 2022, 18 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/031,854, dated Dec. 27, 2021, 13 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/030,318, dated Jan. 5, 2022, 8 pages. |
| Office Action received for Indian Patent Application No. 202014041563, dated Dec. 30, 2021, 6 pages. |
| Office Action received for Danish Patent Application No. PA 2020 70612, dated Mar. 1, 2022, 2 pages. |
| Summons to Attend Oral Proceedings received for European Patent Application No. 13811085.3, dated Mar. 3, 2022, 3 pages. |
| Applicant Initiated Interview Summary received for U.S. Appl. No. 17/381,570, dated Apr. 26, 2022, 5 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/031,543, dated Apr. 21, 2022, 2 pages. |
| Brief Communication Regarding Oral Proceedings received for European Patent Application No. 20182116.2, dated Apr. 13, 2022, 3 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 17/157,728, dated Apr. 14, 2022, 6 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 17/192,161, dated Apr. 22, 2022, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 17/197,628, dated Apr. 27, 2022, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2021203636, dated Apr. 14, 2022, 3 pages. |
| Office Action received for Chinese Patent Application No. 202110783860.7, dated Mar. 10, 2022, 15 pages (5 pages of English Translation and 10 pages of Official Copy). |
| Supplemental Notice of Allowance received for U.S. Appl. No. 17/030,321, dated Apr. 15, 2022, 2 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/418,786, dated May 9, 2022, 2 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/820,383, dated May 10, 2022, 2 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/516,537, dated Jul. 5, 2022, 4 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/418,786, dated Jun. 23, 2022, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 17/031,543, dated Jun. 8, 2022, 3 pages. |
| Final Office Action received for U.S. Appl. No. 16/820,383, dated Jun. 22, 2022, 21 pages. |
| Final Office Action received for U.S. Appl. No. 17/031,854, dated Jun. 10, 2022, 15 pages. |
| Final Office Action received for U.S. Appl. No. 17/031,859, dated Jun. 10, 2022, 13 pages. |
| Final Office Action received for U.S. Appl. No. 17/031,874, dated Jun. 2, 2022, 19 pages. |
| Garmin Edge 520, Owner's Manual, online available at: https://www8.garmin.com/manuals/webhelp/edge520/EN-US/Edge_520_OM_EN-US.pdf, 2015, 24 pages. |
| Intention to Grant received for European Patent Application No. 20182116.2, dated Jun. 2, 2022, 8 pages. |
| Minutes of the Oral Proceedings received for European Patent Application No. 20182116.2, dated May 24, 2022, 7 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/030,318, dated Jun. 14, 2022, 9 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/030,337, dated Jun. 14, 2022, 13 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/030,340, dated Jun. 14, 2022, 15 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/516,537, dated May 5, 2022, 8 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2020-160052, dated Jun. 3, 2022, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for Korean Patent Application No. 10-2022-7008569, dated May 19, 2022, 5 pages (2 pages of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for Korean Patent Application No. 10-2022-7017918, dated Jun. 13, 2022, 6 pages (2 pages of English Translation and 4 pages of Official Copy). |
| Notice of Allowance received for U.S. Appl. No. 16/418,786, dated Jun. 14, 2022, 9 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/994,352, dated Jun. 3, 2022, 9 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/031,543, dated May 11, 2022, 6 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/192,161, dated May 27, 2022, 8 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/197,628, dated Jun. 24, 2022, 8 pages. |
| Office Action received for Australian Patent Application No. 2021204422, dated May 31, 2022, 2 pages. |
| Office Action received for Chinese Patent Application No. 202110363565.6, dated May 7, 2022, 12 pages (7 pages of English Translation and 5 pages of Official Copy). |
| Office Action received for Danish Patent Application No. PA202070612, dated May 10, 2022, 2 pages. |
| Office Action received for Danish Patent Application No. PA202070613, dated May 10, 2022, 2 pages. |
| Office Action received for Danish Patent Application No. PA202070614, dated Apr. 28, 2022, 4 pages. |
| Office Action received for Danish Patent Application No. PA202070616, dated May 5, 2022, 3 pages. |
| Office Action received for Danish Patent Application No. PA202070815, dated Jun. 14, 2022, 3 pages. |
| Office Action received for Danish Patent Application No. PA202170113, dated May 3, 2022, 2 pages. |
| Office Action received for Korean Patent Application No. 10-2020-0123815, dated May 31, 2022, 10 pages (5 pages of English Translation and 5 pages of Official Copy). |
| Summons to Attend Oral Proceedings received for European Patent Application No. 20203526.7, dated Jun. 23, 2022, 9 pages. |
| Summons to Attend Oral Proceedings received for European Patent Application No. 20721342.2, dated May 20, 2022, 11 pages. |
| Supplemental Notice of Allowance received for U.S. Appl. No. 16/994,352, dated Jun. 20, 2022, 2 pages. |
| Supplemental Notice of Allowance received for U.S. Appl. No. 17/030,321, dated Jun. 10, 2022, 2 pages. |
| Supplemental Notice of Allowance received for U.S. Appl. No. 17/030,321, dated May 27, 2022, 2 pages. |
| Supplemental Notice of Allowance received for U.S. Appl. No. 17/192,161, dated Jun. 13, 2022, 2 pages. |
| Supplemental Notice of Allowance received for U.S. Appl. No. 17/192,161, dated May 13, 2022, 2 pages. |
| Number | Date | Country | |
|---|---|---|---|
| 20210113116 A1 | Apr 2021 | US |
| Number | Date | Country | |
|---|---|---|---|
| 62398440 | Sep 2016 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 15600243 | May 2017 | US |
| Child | 16987275 | US |
