Source: https://insight.rpxcorp.com/pat/US20110275940A1
Timestamp: 2020-08-09 21:13:53
Document Index: 515970517

Matched Legal Cases: ['art 3605', 'art 3605', 'art 5803', 'art 5801', 'art 5805', 'art 5805', 'art 5805', 'art 5811']

Patent US 20110275940A1
US 20110275940A1
Est. Priority Date: 12/09/2009
a data collection module comprising a processor and memory operatively coupled to the processor, the memory further storing computer readable instructions that, when executed, cause the module to;
detect the presence of one or more athletic activity sensors,poll the one or more athletic activity sensors for athletic performance data, andreceive the athletic performance data;
a second sensor configured to measure a second type of athletic activity parameter different from the first type, wherein the second type of athletic activity parameter includes a heart rate of a user performing an athletic activity,wherein the data collection module is configured to collect heart rate information through the second sensor for a plurality of activity types, andwherein the data collection module is configured to collect the first type of athletic activity parameter for only a subset of the plurality of activity types.
Immobility Monitoring System
US 20130214923A1
SENIORS WELLBEING PTY LTD
EXERCISE SUPPORTING DEVICE, EXERCISE SUPPORTING METHOD AND EXERCISE SUPPORTING PROGRAM
US 20140067096A1
US 8,784,115 B1
Thomas Chu-Shan Chuang
D713851S1
D714330S1
D714327S1
D714326S1
D714328S1
D714329S1
D715314S1
D715812S1
D715813S1
D716820S1
D716821S1
D716822S1
D716823S1
D717812S1
Biosensor wristband
D717956S1
D718319S1
System and method for calculation and display of performance driving information
US 8,933,798 B2
Hybrid pulse measuring device
D730526S1
Solmitech Co. Ltd.
D739942S1
US 9,333,411 B2
D757073S1
Athletic Data Aggregation and Display System
US 20160353502A1
D785672S1
D790565S1
GOAL-BASED SOCIAL NETWORKING TO IMPROVE USER MOTIVATION
US 20170289302A1
D805089S1
US 9,867,152 B2
Gathering and Analyzing Kinetic and Kinematic Movement Data
US 20180092572A1
US 20180193697A1
US 10,045,195 B2
Display screen with a transitional graphical user interface for image navigation and selection
D832885S1
Method for displaying content and electronic device therefor
US 10,209,779 B2
US 10,219,708 B2
D845325S1
Transmitting athletic data using non-connected state of discovery signal
US 10,306,687 B2
Athletic activity data device firmware update
US 10,310,836 B2
US 10,313,868 B2
US 10,335,636 B2
Control of system zoom magnification using a rotatable input mechanism
US 10,365,807 B2
US 10,456,077 B1
D865777S1
Negentropics Mesterseges Intelligencia Kutato Es Fejleszto Kft
Monitoring performance of computing devices
US 10,491,650 B1
Athletic training intensity
US 10,499,849 B1
D871425S1
US 10,534,900 B2
Stopwatch and timer user interfaces
US 10,552,009 B2
D875770S1
D876464S1
US 10,582,007 B2
US 10,588,519 B2
D884730S1
Filed 11/07/2019
D886835S1
US 10,700,774 B2
METHOD FOR QUICKSTART WORKOUT GENERATION AND CALIBRATION
US 20100062905A1
Processing of continuous pressure-related signals derivable from a human or animal body or body cavity: methods, devices and systems
US 20060047201A1
DPCOM AS
US 20030181291A1
generating, by a computing device, a graph for an athletic activity comprising at least one of;
heart rate information and pace information;
11. The method of claim 6, further comprising displaying at least one marker in the graph, wherein the marker is indicative of at least one of:
a highest heart rate and a lowest heart rate.
15. The method of claim 13, further comprising receiving user-specified instructions on a manner in which the received data is to be processed, wherein the manner in which the received data is to be processed includes one or more of:
stored in the site and visualization.
memory operatively coupled to the processor and storing computer readable instructions that, when executed, cause the apparatus to;
generate a graph for an athletic activity comprising at least one of;
determine an individual'"'"'s subjective assessment of a difficulty of the athletic activity; and
tag the athletic activity with another indicator specifying the individual'"'"'s subjective assessment of the difficulty of the athletic activity.
wherein generating the graph includes;
According to another aspect, an athlete'"'"'s workout information collected in an athletic performance monitoring device may be transmitted to an athletic performance monitoring site or application situated on a device or server other than the monitoring device. For example, the collected data may be transmitted to a third party athletic performance monitoring site on a remote server where the data may be collected, stored, visualized and compared with other users of the site. The manner in which the athlete'"'"'s workout information is processed may be specified by the user pre-, during and/or post-workout. For example, a user may specify whether data is to be recorded, transmitted and/or visualized.
According to another aspect, a user'"'"'s workout information including heart rate and pace may be compared with other users. For example, a comparison of the user'"'"'s workout with the average workout of friends or all other users of an athletic performance monitoring site may be generated. Such comparisons may provide the user with motivation to increase their workouts or improve in their performance.
According to yet another aspect, an athlete'"'"'s workouts may be summarized according to an amount of time or percentage of the workouts spent in various heart rate ranges. The athlete may further be allowed to define the heart rate ranges and target percentages for each heart rate range. An alert may then be created to alert the athlete whenever his or her workouts are within the specified target percentages. Some tolerance may be provided for determining when an athlete has reached a specified target percentage. For example, if 8% of an athlete'"'"'s workout is within the 170-180 bpm heart rate range and the athlete has defined a target of 10% for that heart rate range, the workout may be determined to have achieved the goal of 10%.
According to yet another aspect, trendlines may be generated for a user'"'"'s workout. For example a heart rate trendline may be generated to indicate a level of progress made by the user during a workout. Trendlines for other metrics (e.g., pace, distance, amount of weight lifted, etc.) may also be generated.
FIG. 29a is an exploded perspective view of the heart rate monitor assembly of FIG. 28;
FIGS. 29b and 29c are partial cross-sectional views of the removable closure assembly of FIG. 28;
FIGS. 33-35 illustrate example user interfaces in which a user'"'"'s workout information including heart rate information is visualized as a distance over time graph according to one or more aspects described herein;
FIGS. 36 and 37 illustrate example user interfaces in which a user'"'"'s pace during a workout is visualized in conjunction with heart rate information according to one or more aspects described herein according to one or more aspects described herein;
FIGS. 38 and 39 illustrate example user interfaces displaying a user'"'"'s heart rate over time for a workout according to one or more aspects described herein;
FIGS. 40 and 41 illustrate example user interfaces displaying a user'"'"'s heart rate over time including an average heart rate and a range of heart rates detected according to one or more aspects described herein;
FIG. 42 illustrates an example user interface in which portions of a user'"'"'s workout pace chart is identified based on a selected heart rate range according to one or more aspects described herein;
The sensor 12 may have various electronic components including a power supply, magnetic sensor element, microprocessor, memory, transmission system and other suitable electronic devices. The sensor 12 in one exemplary embodiment is mounted on the shoe of a user as shown in FIG. 1. Alternatively or additionally, sensor 12 may include a heart rate sensor that is worn in other locations of a user'"'"'s body. The sensor 12 is used in conjunction with the other components of the system to record speed and distance among other parameters of athletic performance such as heart rate. The sensor 12 can be a sensor as disclosed in U.S. Publication Nos. 2007/0006489; 2007/0011919 and 2007/0021269. These U.S. Publications are incorporated by reference herein and made a part hereof In one or more arrangements, multiple sensors may be used in conjunction with assembly 14.
As shown in FIGS. 2-4 and 12-14, the carrier 18 is generally in the form of a wristband 18 having a central portion between a first end portion and a second end portion. The wristband 18 may include a first member 18a and second member 18b generally molded or connected together. The wristband 18 is flexible to fit around a user'"'"'s wrist. In one exemplary embodiment, the wristband 18 may be injected molded of a flexible polymeric material. The wristband 18 has receiving structures for connection to the device 16. The carrier 18 includes a protective sleeve 60 proximate the central portion and having an opening 61 for receiving the connector 23 of the housing 20. The protective sleeve 60 has a generally contoured surface. As shown in FIG. 13, the sleeve 60 may have internal structure for assisting in securing the connector 23, such as ridges 63 that provide an interference type fit between the sleeve 60 and the connector 23. A recess 65 is also defined between the ridges 63 providing a gap between the connector 23 and a bottom portion of the sleeve 60. A vent 67 is provided through a bottom portion of the wristband 18 and is in communication with recess 65 proximate the connector 23 when inserted into the wristband 18. The vent 67 allows any moisture to escape from the wristband 18 and be channeled away from the connector 23. Also at the central portion, the carrier 18 has an aperture 40 dimensioned to receive the protrusion 38 of the wearable device 16. As further shown in FIGS. 3 and 4, the first end portion has a pair of holes 17 (FIG. 13) to accommodate a removable closure as described in greater detail below. The second end portion has a plurality of holes 19 to cooperate with the removable closure as further described below for securing the wristband 18 to a wrist of a user (FIG. 2).
As further shown in FIGS. 4 and 13-16, the wristband 18 has a removable closure 70 used to fasten the wristband 18 to a wrist of a user. To this end, the removable closure 70 cooperates with the plurality of holes in the wristband 18. The removable closure 70 has a plate member 72 and a plurality of posts 74 extending generally in a perpendicular direction from the plate member 72. In the exemplary embodiment depicted in FIG. 15, the plate member 72 has two posts 74. Each post 74 has an insert 76 that is pressed on or snap-fitted onto the post 74. Each insert 76 may be spot welded to the plate member 72. Each insert 76 may be rounded in order to provide a comfortable fit against a user'"'"'s wrist. Other connection methods are possible. A gap is maintained between an inside surface of the plate member 72 and a bottom surface of the post 74. In addition, each post 74 has an annular channel 78 around a periphery of the post 74.
To wear the wristband, first the removable closure 70 is connected to the first end portion of the wristband strap 18 wherein the pair of holes 17 is provided to receive the posts 74. The wristband 18 fills the gap. It is further understood that the recessed area 71 in the wristband 18 is dimensioned according to the size of the plate member 72 wherein the plate member 72 fits snugly within the recessed area 71. The wristband 18 is positioned around the user'"'"'s wrist and the posts 74 are inserted into the holes 19 provided on the second end portion of the wristband 18 as can be appreciated from FIG. 2. The portion of the wristband 18 proximate the holes 19 fits within the annular channels 78 of the posts 74. After the posts 74 are inserted into the pair of holes 17 of the first end portion of the wristband 18 and the plurality of holes 19 of the second end portion of the wristband 18, the first end portion and second end portion of the wristband overlap one another. With the use of a pair of posts 74, the removable closure 70 allows for a secure connection and greater flexibility in connection providing for a greater adjustment to accommodate for a range of wrist sizes.
The software has an extremely simple calibration method and user interface. For example, it is very simple to calibrate distance measurements onto the device. The software can also track motivational information among several classes of fitness activity recording devices. For example, the user can set weekly goals and the software can track the user'"'"'s progress with these goals. The user can also use multiple devices, such as an audio player having a suitable interface device, other types of sport watches etc., along with the device of the present invention, and the software will accumulate the weekly and overall total distance recorded by all of the devices. Thus, the data is kept synchronized over multiple devices.
According to one or more arrangements, a sensor configured to communicate data to a wearable device assembly (e.g., assembly 14 of FIG. 1) may be used to monitor a user'"'"'s heart rate. For example, a sensor may be used to determine a user'"'"'s heart rate (beats per minute) during performance of an athletic activity such as running, using an elliptical, walking and the like. FIGS. 28-31 illustrate a removable closure for a heart rate monitor assembly 780. The heart rate monitor assembly 780 has a chest strap 718 and a transmitter portion 782. The chest strap 718 has a first end 720 and a second end 722, while the transmitter portion 782 also has a first end 724 and a second end 726. The transmitter portion 782 has at least two removable closures 770 which are used to fasten the chest strap 781 to the transmitter portion 782. The removable closure 770 is generally similar in structure to the removable closure 70 described above and shown in FIGS. 4 and 15. One removable closure 770 is attached to the first end 724 of the transmitter portion 782 and one removable closure 770 is attached to the second end 726 of the transmitter portion 782. To this end, the removable closures 770 cooperate with a plurality of holes on the first end 720 and the second end 722 of the chest strap 781.
To wear the heart rate monitor assembly 780, as depicted in FIG. 30, first the first removable closure 770 is connected to the first end 724 of the transmitter portion 782 wherein a pair of holes is provided to receive the posts 74. Next, the first removable closure 770 is connected to the first end 720 of the chest strap 781 by inserting the posts 74 into the holes provided on the first end 720 of the chest strap 781. The chest strap 781 is then positioned around the user'"'"'s chest. Next, in order to fasten the heart rate monitor assembly 780 around the user'"'"'s chest, the second removable closure 770 is connected to the second end 726 of the transmitter portion 782 wherein a pair of holes is provided to receive the posts 74. Next, the second removable closure 770 is connected to the second end 722 of the chest strap 781 by inserting the posts 74 into the holes provided on the second end 722 of the chest strap 781. With the use of the pair of posts 74, the removable closure 770 allows for a secure connection and greater flexibility in connection providing for a greater adjustment to accommodate for a range of chest sizes.
Athletic performance data may be displayed to a user as part of an athletic performance visualization. For example, data regarding the user'"'"'s pace and heart rate during a run may be used to generate a graph to show a user'"'"'s trend during the activity. The visualization might only display information that was selected for uploading or for visualization. For example, as noted above, users may select different performance data types for different purposes. Accordingly, a user may select to record pace, heart rate, time and distance, but select only heart rate and time for visualization. The determination of what information types to upload and/or use in a visualization may be made by the wearable monitoring device, a user'"'"'s computing device and/or a remote performance monitoring system.
FIG. 33 illustrates an example user interface 3300 in which athletic performance data may be visualized and reviewed. Each workout or day of workout may be represented by entries 3303. A workout entry may include a single workout or may include all workouts for a predefined time period (e.g., a day). Thus, user interface 3300 may display multiple workout entries 3303 simultaneously in, for example, a bar graph. That is, each bar 3303 may represent a different workout or day of workouts or other predefined time period of workout sessions. The appearance of entries 3303 may vary depending on the types of data recorded for that workout or day or workout. For example, entry 3303a may be represented by a bar with a heart to indicate that both run data (e.g., pace or distance information) and heart rate information was recorded for that workout. In another example, entry 3303b might include a bar with no heart, indicating that run/pace information is available for the workout while heart rate information is not. In yet another example, entry 3303c may include a heart with no bar to indicate that heart rate information is available but that distance/pace information was not record or not uploaded to the system. Alternatively, if heart rate information is available or was recorded, the heart may be displayed upon a user hovering over the corresponding workout entry (e.g., workout entry 3303b) instead of the heart or other icon being persistent in the display. Once a user is no longer hovering over or otherwise interacting with the workout entry, the heart may disappear or be removed. Other types of indicators may be used including different fill colors for the bars, different fill patterns, different transparencies and the like.
In some arrangements, indicators may also be used to identify the type of activity corresponding to the athletic activity data. Accordingly, a basketball icon may be displayed in a bar or other portion of the graph to indicate the user was playing basketball while a pool icon may be displayed for swimming activities. By tracking the type of activity contributing to the athletic activity data, different types of coaching and/or thresholds may be used in judging the user'"'"'s performance. In one particular example, a color of the athletic activity bar or segment of a line graph may be selected based on how well the user performed. For example, if a user exceeded a first distance or pace threshold for a running activity, the corresponding bar or portion of a line graph may be displayed in a first appearance (e.g., green), while if the user was below another threshold, the corresponding bar or portion of a line graph may be displayed in a second appearance (e.g., yellow or red). The various thresholds may be selected based on the indicated type of activity. Thus, different activities (e.g., weight lifting, basketball, swimming, running, soccer, etc.) may have different thresholds (e.g., heart rate, pace, distance, etc.). For example, heart rates during weight lifting may be generally lower than heart rates during running or basketball. Accordingly, lower heart rate thresholds may be set for weight lifting than for running or basketball. Thus, the indication (e.g., visualization using color or patterns of the data representations) of whether the user is excelling or underachieving may be relative to the particular activity.
FIG. 33 illustrates an example cardiovascular mile bar graph 3301 (with and without heart rate information) and example mile bars 3303 (with and without heart rate information). According to one or more aspects, hovering over different parts of the graph may display different additional details of the workout. For example, if a user hovers over or otherwise interacts with heart displayed in bar 3303b, additional details relating to the user'"'"'s heart rate or cardiovascular performance such as a range of heart rates detected, a max and min heart rate, average heart rate and the like may be displayed in pop-up window (similar to window 3305). In another example, a user hovering over only the bar graph portion (without hovering over the heart indicator of bar 3303b) may cause pop-up window 3305 to display more run related metrics including distance, pace and/or time.
Interface 3400 may further display trend information that allows a user to determine a degree of progression or regression in their performance over a specified amount of time. For example, trend information 3409 indicates that the user'"'"'s number of miles run has decreased by 20% in the past 6 months. The trend information may be calculated or determined based on a predefined time period set by the user. For example, the user may configure the interface 3400 to display the user'"'"'s performance trend for a previous year, the past week, past 2 weeks, past month, past 3 months and the like. Trend information 3409 may also be configured to identify trends for different types of performance information such as pace and heart rate. Furthermore, interface 3400 may display a comparison 3411 of performance data that shows the user'"'"'s activity as compared to others including friends and the general public. This information may be retrieved from a database or requested from devices associated with each of the other users.
Users may choose to set a goal for increasing an aspect of their athletic performance, such as pace, by setting an alert using goal setting tool 3413. Tool 3413 allows a user to set a goal and to alert themselves (e.g., through an athletic monitoring device) when the set goal is reached. For example, the goal may correspond to an average number of miles run per workout or over a predefined period of time. Thus, if a user is currently running about 2 miles per workout, the user may set a goal and alert for running 2.5 miles per workout. Upon reaching the goal, the user may receive a notification such as a text message, an e-mail, a message on an athletic performance monitoring device and the like. Interface 3400 may automatically identify zones of improvement that may be considered to require moderate additional effort (e.g., past average zone 3415) or significant additional effort (e.g., push yourself zone 3417). In one example, workout data may be automatically uploaded to the performance monitoring site and system during or after a user'"'"'s workout. Accordingly, a user might not always check the site to review the workout session in relation to preset goals or past activities. Thus, the performance monitoring site may transmit a text message or email or automated voice call in order to alert the user of the achievement. In some arrangements, the performance monitoring site might also post a message on a user'"'"'s social networking site or issue a broadcast message through services such as TWITTER.
FIGS. 36 and 37 illustrate user interfaces in which a user'"'"'s workout is displayed as a graph of pace over distance. Graph 3601 of FIG. 36 includes multiple indicators 3603 identifying predefined times or distances of the workout. For example, indicators 3603 may correspond to mile markers or hourly markers. Alternatively or additionally, markers 3603 may be used to identify an amount of progress toward a goal. Thus, markers 3603 may be placed at positions on graph 3601 that correspond to 0%, 25%, 50%, 75% and 100% of the goal distance. Furthermore, graph 3601 may include heart rate markers 3605 that identify the points in the workout where an athlete reached his or her highest and lowest heart rates. For example, marker 3605a may correspond to the athlete'"'"'s highest heart rate during the workout and marker 3605b may correspond to the athlete'"'"'s lowest heart rate. Additional heart rate markers may also be included in graph 3601 depending on the preferences of the user. In one or more arrangements, the highest and lowest heart rates might only be selected from a portion of a workout after a warm-up period or other predefined amount of initial workout time. For example, interface 3600 might only identify the highest and lowest heart rates after the first 30 seconds, 1 minute, 3 minutes, 5 minutes of the workout. Alternatively or additionally, interface 3600 might ignore a predefined amount of time at the end of the workout. Ignoring these portions of the workout in determining highest and lowest heart rates may help eliminate artificially low or high heart rates due to cool down, initial warm-up and the like. According to one or more aspects, the highest and lowest heart rates may be determined by identifying the highest and lowest average heart rates, respectively, for a predefined period of time (e.g., 5 seconds, 10 seconds, 15 seconds, 20 seconds, 30 seconds, etc.). In one example, the determined heart rate for time 1 minute and 30 seconds may correspond to an average of the heart rates between 1 minute and 20 seconds and 1 minute and 40 seconds. Hovering over each of markers 3603 and 3605 may provide detailed information similar to the detailed information displayed in window 3305 of FIG. 33. Alternatively or additionally, detailed information may be displayed in a pop-up window for one or more markers 3603 and 3605 without having to hover over or otherwise interact with marker 3603 and/or 3605. Hovering or otherwise interacting with other portions of graph 3601 may also provide additional information about a particular portion of graph 3601. According to one or more aspects, a user may set low and high thresholds for his or her heart rate. Accordingly, indicators 3605a and 3605b may correspond to the points in the workouts where the user crossed above or below those thresholds. For example, a user may set a high heart rate threshold at 150 bpm. Accordingly, graph 3601 may display heart 3605b at the point where the user first crosses the 150 bpm threshold. An indicator such as heart 3605b may be displayed at each point along graph 3601 where the user crossed above or met the threshold. Similarly, an indicator may be displayed along graph 3601 where a user crossed below or met a lower or minimum threshold to help the user recognize where he or she exhibited a weaker performance in terms of heart rate.
As noted herein, workout data may be displayed in either pace form or heart rate format. FIGS. 38-41 illustrate various example heart rate graphs that provide a visualization of a user'"'"'s heart rate over a workout period. Heart rate may be expressed as the number of beat per minute (bpm). In FIG. 38, graph 3800 may include heart rate markers 3803 that identify predefined positions in the workout. For example, markers 3803 may be placed at every hour or other predefined amount of time, every 25% or other percentage of the workout (either based on time or distance), at every mile or other specified distance and/or combinations thereof. Total workout time 3805 may be displayed at the end of the graph along with the average heart rate 3807. FIG. 39 illustrates another example heart rate graph 3900 where heart rate markers 3903 may be placed at the beginning and end of the workout as well at the points in time where the athlete reached his highest and lowest heart rates.
FIG. 40 illustrates a heart rate graph 4000 for multiple workouts. Since each workout may include multiple heart rate readings, heart rate graph 4000 may be configured to chart the average heart rate for each workout against time. However, the range of heart rates for each workout may also be represented and visualized in graph 4000 by the colored or grayed region 4003. In one arrangement, a user'"'"'s average heart rate may be displayed along the graphed line while the range may be represented by a region having an appearance (e.g., color, pattern, transparency) different from the graphed line. Heart rate markers 4005 may be placed along the top edge of the grayed or colored region 4003 to identify the highest heart rate an athlete reached during that particular workout or day of workouts. Hovering over or otherwise interacting with markers 4005 may cause a pop-up window 4007 to be displayed. Pop-up window 4007 may include information such as the number of miles run for that workout, the average pace and the average heart rate. Additionally or alternatively, hovering within region 4003 may display a corresponding heart rate and amount of time the user exhibited that particular heart rate during that particular workout session, day or other time period. In one particular example, if a user hovers over the “T 17” workout day and around the 125 bpm mark, the interface may display an amount of time the user exhibited a 125 bpm (or a predefined range around 125 bpm such as 10% above and below, 5 bpm above and below and the like) during that workout day. In addition or alternatively to an amount of time the user exhibited a particular heart rate, the interface may display a distance or other amount of exercise performed at that heart rate.
FIG. 41 illustrates another example of a heart rate graph for heart rate information over multiple workouts. Interface 4100 may include a heart zone management tool 4103 that provides the user with the option of setting alerts when the user'"'"'s workout meets a predefined heart rate profile. A heart rate profile may include a specification of the amount of a workout that should fall within each of multiple heart rate ranges. In the illustration of FIG. 41, the profile specifies that the user'"'"'s workout is to be 35% in the 78 to 98 bpm range, 30% in the 99 to 117 bpm range, 25% in the 118 to 137 bpm range and 10% in the 138 to 175 bpm range. If the user approaches these ranges, an alert may be sent to the user notifying the user of the same. A certain level of tolerance may be provided so that a user does not have to exactly match the heart rate profile. For example, if the user exhibits a heart rate between 138 to 175 bpm during 8% of his or her workout, the user may be determined to have matched at least the 138 to 175 bpm portion of the heart rate profile.
FIGS. 42-48 illustrate example interfaces wherein portions of a workout graph is highlighted based on a selected heart rate range. For example, FIG. 42 illustrates a pace graph in which various ranges or zones 4203 are highlighted, superimposed or overlaid. The interface 4200 further includes a heart rate range control bar 4201 that allows a user to select a particular range of heart rates using low end slider 4205a and high end slider 4205b. Ranges or zones 4203 may then be generated and overlaid over the portions of the workout where a user exhibited a heart range in the selected range. The generation and modification of zones 4203 may be performed in real-time as the user is modifying or selecting a desired heart rate range. For example, in control bar 4201, the user may select a heart rate range of 122-142 bpm. Accordingly, ranges 4203 represent the portions of the workout in which the user exhibited a heart rate in the range of 122-142 bpm. Interface 4200 may further include an information portion 4207 that displays the amount or percentage of time the user exhibited that range of heart rates (e.g., 14 minutes and 25 seconds and 32%). In one or more arrangements, instead of displaying highlighting bars 4203, the interface may modify the appearance of the relevant segments of the line graph in which the user exhibited the selected range of heart rates. For example, the matching portions of the line graph may be displayed in another color, with a different pattern and/or the like.
According to another aspect, upon selecting a heart rate range, various heart rate indicators may be modified based upon the selected range. For example, high heart rate and low heart rate indicators may be modified to reflect the locations along the line graph where the user exhibited the high heart rate and low heart rate within the selected range. In another example, the location of an indicator identifying the location where the user'"'"'s heart rate exhibited the greatest change may be modified to reflect the greatest change within the selected heart rate range.
FIGS. 47 and 48 illustrate other example interfaces that are configured to identify portions of a user'"'"'s workout that correspond to a particular heart rate range. Interface 4700 may include further information including a highest heart beat rate 4703, a comparison 4705 of the user'"'"'s highest heart rate to that of the user'"'"'s friends and a comparison 4707 of the user'"'"'s heart rate to that of the others. Interface 4700 may further include options 4709 that allow the user to indicate the user'"'"'s feeling about the workout (4709a), the weather associated with the workout (4709b) and a type of workout terrain (4709c). Other words, phrases, images and the like may be used to tag the workout using tagging option 4711. Tagging may allow a user to more easily find workout entries by searching for the words or phases with which the entries have been tagged. Additional tagging options are discussed below with respect to FIG. 59.
FIGS. 49 and 50 illustrate example interfaces in which the heart rate range control bar 4903 is provided as a drop down menu upon selection of heart rate control option 4907. When exposed, the heart rate range control bar 4903 may overlay a portion of graph 4901. Heart rate range control bar 4903 may include multiple predefined range selectors 4909 that allows a user to identify predefined ranges on graph 4901. The predefined ranges, in one or more example, may include up to 120, 121-140, 141-160, 161-180 and 181 and over. Thus, selecting one of selectors 4909 may automatically modify and/or define the range to the predefined range corresponding to the selector. Alternatively or additionally, the user may choose to create a custom heart rate range using sliders 4911a and 4911b. Each selected range may be identified using a different pattern, color, hue and/or combinations thereof. In one or more arrangements, interface 4900 might only allow the user to select and view one range at a time. In one or more examples, the user may choose and display multiple heart rate ranges simultaneously using different appearance characteristics such as color, pattern, transparency, brightness, hue, tone, flash and the like.
In FIG. 52, for example, a legend 5203 is provided at the bottom of graph 5201 to indicate the colors representing each of the ranges and to allow a user to control which ranges are selected and displayed. In interface 5200, ranges 5205a and 5205b are selected for identification in graph 5201. The selection buttons 5207a and 5207b corresponding to ranges 5205a and 5205b, respectively, are provided in different colors corresponding to the colors used to identify the portions of the user'"'"'s workout corresponding to those ranges. The predefined ranges 5205 may be predefined based on a default configuration, based on a coach or third party input, based on a user'"'"'s preferred configuration or setting or the like. For example, a user may define preferences to indicate a set of preferred ranges. Upon accessing a visualization of a workout, the user may be offered those preferred ranges for viewing heart rate information.
FIG. 55 illustrates another example pace graph 5501 in which the athlete'"'"'s actual lap time 5503 is displayed with a split time 5505. This display may allow the user to compare his current pace with a desired pace. Additionally, heart rate information for the current workout and for the split may also be displayed for purposes of comparison. The split may be generated from a previous workout or based on a target workout. The target workout may be defined by the user or a third party such as a coach (e.g., by setting desired 400 meter times and 800 meter times as well as desired heart rates at predefined points of the workout) or selected from a library of predefined workouts.
FIG. 57 illustrates a heart rate graph 5701 in which a user'"'"'s average heart rate for each day is represented as a bar. A trend line 5703 may overlay or be superimposed on graph 5701 to represent the user'"'"'s trend in heart rate for his or her workouts. As illustrates, trend line 5703 indicates that the user'"'"'s heart rate has been declining over the displayed time range. This may help the athlete determine whether they should increase the pace of their workouts, increase the length of workouts, change the type of workouts or the like.
Flowchart 5803 illustrates a series of displays that may be generated when the monitoring and data collection device is configured to receive data from both a shoe based sensor and a heart rate sensor. As described with respect to flowchart 5801, the user may activate a workout mode on the device by pressing a specified button for a specified amount of time. The monitoring device may then request that the user begin walking so that the sensors can be detected and the data transmission tested. Depending on if shoe based sensor data or heart rate data is received first, the device may proceed to flowchart 5805 or 5807. For example, if shoe based sensor data is received first, flowchart 5805 illustrates that the words “SHOE” “OK” is displayed to notify the user that the shoe sensor has been detected and is working appropriately. The device may then proceed to detect the heart rate sensor. During this time, the letters “HRS” may be displayed on and off for a predefined amount of time (e.g., 0.5 seconds every 1 second for 3 seconds). The device may further provide the user with the option to begin the workout without trying to detect a heart rate by displaying “OR,” “PUSH,” “TO,” and “RUN” sequentially. If a user'"'"'s pushes the button to begin the run, flowchart 5805 may proceed to display a timer display. If, on the other hand, a heart rate is detected, the device may proceed to flowchart 5811 which displays “PUSH,” “TO,” and “RUN” in sequence to prompt the user to begin the workout.
FIG. 59 illustrates another example user interface displaying a user'"'"'s heart rate during a workout session. In interface 5900, a user is provided with a plurality of tag options including a feeling or condition (e.g., mood or physical conditions such as sick, tired, happy, energetic, etc.) tag 5901, a weather tag 5903 and a run terrain tag 5905. Additionally, interface 5900 allows a user to specify a heart rate intensity using tag option 5907. Heart rate intensity may include the subjective feeling or assessment of the user regarding their heart rate during the run and/or perceived level of effort or difficulty. For example, the first heart rate intensity tag 5909 may indicate a comfortable heart rate while tag 5911 may indicate a heart rate intensity where the user was required to exert him or herself to a greater extent than a comfortable jog or fast paced walk. Further, tag 5913 may indicate a heart rate intensity where the user had to maximize his or her effort. In one or more arrangements, a system may automatically tag the heart rate intensity based on the user'"'"'s actual recorded heart rate for the athletic activity session. For example, if the user averaged 80% above his or her resting heart rate, a high intensity heart rate indicator (e.g., indicator 5913) may be selected or used to tag the activity session. In another example, if the user'"'"'s average heart rate during the activity session is 65% above his or her resting heart rate, the workout session may be labeled with a medium heart rate intensity tag (e.g., indicator 5911).
FIGS. 60-62 illustrate a series of example interfaces through which a user may earn a number of credits through the recordation of heart rate information. The credits earned may be used for bragging rights or may act as currency for purchase of products or services. In interface 6000, for example, a user may be encouraged to begin earning heart beats (e.g., a type of credit) by performing heart rate activities. The user may then dedicate the heart beats to one or more of the user'"'"'s interests. Interface 6000 illustrates a community heart beats dedication display 6003 in which various interests, causes, organizations and the like are listed. A number of heart beats users have dedicated to each interest, cause or organization may be displayed in association with each of the interests, causes and/or organizations (e.g., a 10K run, the New York Marathon, weight loss, breast cancer, vacation, dessert, dog parks, etc.). The display 6003 may include the interests, causes and/or organizations having the greatest number of heart beats or other credits dedicated. Accordingly, the credits or heart beats may be used to raise awareness of one or more interests, causes and/or organizations. In some arrangements, the credits may be associated with a monetary value. For example, a system, company, user, site or the like may donate an amount of money to an interest, cause or organization upon the interest, cause or organization having a specified number of credits (e.g., heart beats) dedicated thereto.
FIG. 63 illustrates a workout activity graph 6301 identifying the user'"'"'s average heart rate during one or more workout sessions. In the illustrated example, the user'"'"'s average heart rate is displayed over a previous 7 workouts in the past two months. The average heart rate is identified by heart rate marker 6309. Line graph 6311 identifies the trendline corresponding to the average heart rates recorded for the 7 workouts. Trendlines may be useful since average heart rates might not provide a user a good sense of progress or relative performance. In some instances, absolute heart rate measurements might not allow the user to detect or perceive his or her progress. The user may use control 6303 to increase the size of the time frame (e.g., by expanding span bar 6305) and/or move the time frame (e.g., by moving span bar 6305) along timeline 6307. The trendline may then adjust appropriately based on the heart rate data within that time frame (rather than the entire set of available heart rate data). Graph 6301 may automatically adjust and in real-time based on the operation of control 6303. A user may toggle the trendline showing by selecting option 6313. If option 6313 is turned off, the graph 6301 might only display the heart rate markers and average heart rates without the displaying the trend.
Hailey, Michael Benjamin, Capozzi, Matt, Crankson, Kwamina, Nims, Jason
US 9,895,096 B2
A63B 2220/00 : Measuring of physical param...
US 10,646,152 B2