Field
The embodiments described below relate to the generation and presentation of activity-related graphics. Some embodiments relate to the generation and presentation of graphical indicators conforming to a personalized display scale.
Description
The benefits of monitoring fitness-related information are well-known. A conventional stationary exercise device may include a display which graphically presents information such as time elapsed, heart rate, calories burned, etc. Wearable/portable fitness monitors also display fitness-related information to users. This information provides motivation, immediate feedback, and a better understanding of progress toward fitness goals.
Fitness-related information is typically presented using alphanumeric characters (e.g., “110 BPM”) or graphical visualizations. For example, a bar chart may present a heart rate over time. Such a bar chart may include several bars, each associated with a different time interval, where the length of a bar represents a heart rate during its associated time interval.
Graphical visualizations may provide an intuitive understanding of underlying fitness-related information. However, improvements to such graphical visualizations are desired, which may result in improved understanding of the underlying information, utilization of display screen area, and/or other benefits.
Some embodiments relate to a device, method, and/or computer-readable medium storing processor-executable process steps to receive from a user, via a sensor, first data indicative of activity of the user, determine one or more values of a metric based on the first data, determine a display scale based on the one or more values, receive from the user, via the sensor, second data indicative of activity of the user over a time interval, determine a second value of the metric based on the second data, generate a graphical indicator representing the second value based on the display scale and the second value, and display the graphical indicator on a display.
Some aspects further include reception from the user, via the sensor, third data indicative of activity of the user over a second time interval, determination of a third value of the metric based on the third data, generation of a second graphical indicator representing the third value based on the display scale and the third value, and display of the second graphical indicator on the display.
In some aspects, the value of the metric associated with a respective time interval is indicative of physical activity during the respective time interval. For example, the metric may be step count, heart rate, distance traveled, activity level, altitude ascended, altitude descended, floors climbed, or calories burned.
According to some aspects, the display scale indicates a length per N units of the metric. The display scale may also or alternatively indicate a number of icons per N units of the metric.
In some aspects, a position of the displayed graphical indicator on the display indicates the time interval. The position may be along an arc of a circle, wherein arcs of the circle represent a plurality of time intervals.
According to some aspects, first data indicative of activity of a user is received, one or more values of a metric are determined based on the first data, a display scale is determined based on the one or more values, second data indicative of activity of the user over a time interval is received, a second value of the metric is determined based on the second data, a graphical indicator representing the second value is generated based on the display scale and the second value, and data representing the graphical indicator is transmitted to a display device.
Further aspects include reception of third data indicative of activity of the user over a second time interval, determination of a third value of the metric based on the third data, generation of a second graphical indicator representing the third value based on the display scale and the third value, and transmission of the second graphical indicator to the display device.
According to some aspects, the display scale indicates a length per N units of the metric. The display scale may also or alternatively indicate a number of icons per N units of the metric.
A more complete understanding of some embodiments can be obtained by referring to the following detailed description and to the drawings appended hereto.
The construction and usage of embodiments will become readily apparent from consideration of the following specification as illustrated in the accompanying drawings, in which like reference numerals designate like parts, and wherein:
The following description is provided to enable any person in the art to make and use the described embodiments. Various modifications, however, will remain readily apparent to those in the art.
A brief example will now be described with reference to
Monitoring device 100 receives data 110 from user 120. Data 110 is received via sensor 105, and is indicative of activity of user 120. Data 110 may be received over any suitable time interval. According to some embodiments, sensor 105 is a heart rate sensor and data 110 comprises signals detected from user 120 by sensor 105.
One or more values of a metric are determined based on data 110. Continuing the example, sensor 105, alone or in conjunction with other elements of monitoring device 100 determines a heart rate of user 120 based on data 110. According to some embodiments, the determined heart rate may comprise an average heart rate during the time interval over which data 110 was received, a maximum heart rate over the time interval, an average heart rate over each of several sub-intervals of the time interval, and/or any other measure of heart rate.
Next, a display scale is determined based on the determined value or values. The display scale associates units (e.g., BPM) of the metric (e.g., heart rate) with a characteristic of a graphical indicators which will be used to represent future values of the metric. In a specific example, a determined maximum heart rate is 150 BPM and a display area is 3.2 cm in height. Accordingly, the determined display scale may be 50 BPM/1 cm. A corresponding graphical indicator representing 150 BPM is 3 cm in length, and is therefore able to fit in the display area. Moreover, additional display height (i.e., 0.2 cm) is available if the heart rate exceeds 150 BPM. If the determined maximum heart rate is 180 BPM, the determined display scale may be 60 BPM/1 cm.
After the display scale is determined, second data indicative of user activity is received over a time interval. Again, the second data may be received from user 120 by sensor 105. A second value of the metric is determined based on the second data, and a graphical indicator representing the second value is generated based on the display scale and the second value.
For example, it will be assumed that a value of 125 BPM is determined based on the second data. Based on the previously-determined display scale of 50 BPM/1 cm, a graphical indicator having a length of 2.5 cm is generated.
The graphical indicator is then displayed.
As described, the display scale used to generate indicators 130 is determined based on metric values which were determined from signals received from user 120. Accordingly, the display scale may optimize a usage of a display area of display 140 based on the user's prior activity.
Embodiments are not limited to the graphical indicators of
In the present disclosure, the term “activity” includes sedentary and nonsedentary activities. As such, the metric may be associated with activities related to sleeping, lying, sitting, and standing stationary (for example, time asleep, the onset, duration, and number of awakenings while attempting to sleep, the time spent in various stages of sleep, sleep latency, sleep efficiency and other sleep quality parameters, the presence of sleep apnea and other diagnostic measures, time spent in a prone non-standing state, and resting heart rate).
Display interface 230 provides communication with display 240, which may comprise any system for visual presentation of information that is or becomes known. Display 240 may comprise a touch screen for receiving user input into system 200 according to some embodiments.
One or more processing units 210 may therefore execute processor-executable program code stored in memory 220 to cause system 200 to receive first data indicative of activity of a user, to determine one or more values of a metric based on the first data, to determine a display scale based on the one or more values, to receive second data indicative of activity of the user over a time interval, to determine a second value of the metric based on the second data, to generate a graphical indicator representing the second value based on the display scale and the second value, and to display the graphical indicator on display 240.
According to some embodiments, system 200 comprises an integrated device such as, but not limited to, a wearable unit (e.g., around wrist, around neck) or an otherwise portable unit (e.g., a smartphone, a dedicated music player, a fob). In some embodiments, elements of system 200 may be embodied in separate devices, such as a server device (e.g., a desktop computer) including elements 210, 220 and 330, and a terminal device (e.g., a watch) including display 240. System 200 may perform functions other than those attributed thereto herein, and may include any elements which are necessary for the operation thereof
Some embodiments of system 200 include a portable monitoring device having a physical size and shape adapted to couple to the body of a user, which allows the user to perform normal or typical user activities (including, for example, exercise of all kinds and type) without hindering the user from performing such activities. The portable monitoring device may include a mechanism (for example, a clip, strap and/or tie) that facilitates coupling or affixing the device to the user during such normal or typical user activities.
For example, during operation, an altitude sensor generates data which is representative of the altitude and/or changes in altitude of the user. A motion sensor generates data which is representative of motion of the user. The data which is representative of the altitude and/or changes in altitude and the data which is representative of the motion of the user, is used to determine energy and/or calorie “burn” of the user.
The data may also be used to determine other activity-related metrics including, for example, (i) in the context of running/walking on level, substantially level, or relatively level ground, (a) number of steps, which may be categorized according to the number of steps associated with a user state, for example, walking, jogging and/or running, (b) distance traveled and/or (c) pace, (ii) in the context of running/jogging/walking/jumping on stairs, hills or ground having a grade of greater than, for example, about 3%, (a) number of stair and/or hill steps, which may be categorized, correlated or organized/arranged according to the number of stair and/or hill steps pertaining to, for example, the speed, pace and/or user state of the user (for example, walking, jogging and/or running), (b) number of flights of stairs, (c) ascent/descent distance on stairs and/or hills, (d) pace, (e) ascent/descent on elevators and/or escalators, (f) number of calories burned or expended by walking/running on stairs and/or hills and/or (g) quantify/compare the additional calories expended or burnt from stairs/hills relative to, versus or over level ground, (iii) in the context of swimming, number of strokes, time between strokes, leg kicks and similar metrics (variance of stroke time, mean stroke time, etc.), depth underwater, strokes per lap, lap time, pace and/or distance, (iv) in the context of using a bicycle, wheelchair, skateboard, skis, snowboard, ladder, etc., (a) ascent/descent distance traversed, (b) number of additional calories expended, (c) time of a downward “run” or upward “climb”, (d) number of calories expended, (e) number of pedal rotations, (f) arm or wheel rotation, (g) the grade of the surface, (h) pushes, kicks and/or steps. This list of activities (if applicable to the particular embodiment) is merely exemplary and is not intended to be exhaustive or limiting.
Elements 310 through 340 of device 300 may operate as described above with respect to similarly-numbered elements of system 200. Device 300 further includes sensor interface 350 for exchanging data with one or more sensors 360.
Sensors 360 may comprise any sensors for acquiring data based on which metric values may be determined. Examples of sensors 360 include, but are not limited to, an accelerometer, a light sensor, a blood oxygen sensor, a gyroscope, a magnetometer, a Global Positioning System device, a proximity sensor, an altimeter, and a heart rate sensor. One or more of sensors 360 may share common hardware and/or software components.
A value of a metric may be determined based on data acquired by one or more of sensors 360. For example, a value of a “distance traveled” metric may be determined based on the outputs of a Global Positioning System device and an altimeter. An “activity level” metric may be determined based on the outputs of a blood oxygen sensor and a heart rate sensor.
User 370 is pictured to indicate that, according to some embodiments, data received by sensors 360 is indicative of activity of user 370. For example, the one or more sensors 360 may receive data based on physical activity of user 370. Moreover, one or more of sensors 360 may receive data via direct contact with the user, for example during heart rate, skin temperature, and/or blood oxygen monitoring.
In some embodiments, calorie expenditure and activity level may be determined based on or using, partially or entirely, the ambulatory speed of user 370. The speed of the user may be calculated, determined and/or estimated as the user's step count over a time epoch multiplied by one or more step lengths of the user (which may be programmed, predetermined and/or estimated (for example, based on attributes of the user (for example, height, weight, age, leg length, and/or gender))). Representative energy expenditure rates expressed as metabolic equivalents per minute (MET/min) may then be estimated, obtained (for example, from a look-up table or database) and/or interpolated from a MET table which provides metabolic equivalents per minute for different user speeds. In some embodiments, step length may be one of two values that are indicative of a walking step length and a running step length dependent on the step frequency and/or acceleration characteristics of the user. In some embodiments, step length may be described as a linear function of step frequency: step length=A+B*step frequency, where A and B are parameters that may be associated with or calibrated to the user. Such parameters may be stored in memory in device 300.
In some embodiments, the speed value may be converted to calorie expenditure by multiplying the corresponding MET value by the user's Body Mass Ratio (BMR). BMR may be obtained through any of a number of well-known equations based on height, weight, gender, age, and/or athletic ability or through designated BMR measurement devices. For example, a user may have a running step length of 57 inches and take 180 running steps during 1 min. Using the method described above, the user's speed estimate is 9.8 miles per hour, which may be linearly interpolated to provide a BMR value of 15.8 MET from the MET table above. Assuming the user's BMR to be 1.10 kcal/MET, the calorie burn of the user in the preceding minute is 17.4 kcal.
An intermediate MET calculation step is not required in this and similar methods. Calorie expenditure may be calculated directly based on speed and one or more physiological parameters of the user such as age, gender, height, weight, and/or athletic ability. Speed may also be filtered over time rather than accepted as a “raw” measurement for a given time epoch. All forms of speed estimation, and mechanisms to implement such techniques, whether now known and/or later developed, may be implemented in some embodiments
Calorie consumption, burn and/or expenditure may be determined using data which is representative of the intensity of user motion for example, as provided or determined by one or more single axis or multi-axis accelerometers, based on a heart rate, based on altitude-related information (for example, from an altimeter disposed on the portable monitoring device), and/or based on any combination of factors described herein.
Initially, at S610, first data is received from a user. The first data is received via a sensor and is indicative of physical activity of the user. The first data may comprise signals acquired from any number of sensors. According to some embodiments, sensor 510 of device 400 acquires heart rate-related signals via contact with a user over a time interval. In some embodiments, an accelerometer of device 400 generates movement data due to user movement over several time intervals.
One or more values of a metric are determined at S620 based on the received data. The metric may comprise any metric described herein or that is (or becomes) known. As described with respect to
The received data is stored in respective ones of memory buffers 722, 724 and 726. The stored data may be raw data or data processed to any output format supported by its respective sensor. For example, according to some embodiments, sensor 714 is a heart rate sensor and outputs a current heart rate to buffer 724 at ten second intervals. Each output heart rate is stored in a memory location of buffer 724.
In some embodiments, application processors 732, 734 and 736 comprise execution threads, processor cores or other processing units for determining metric values based on the data of memory buffers 722, 724 and 726. Application processors 732, 734 and 736 may subscribe to updates of one or more of memory buffers 722, 724 and 726, and determine metric values based on data received according to the subscription. Each of application processors 732, 734 and 736 is associated with a respective metric. That is, each of application processors 732, 734 and 736 determines one or more values of a single metric and also determines a display scale associated with that metric.
In this regard, a display scale is determined at S630 based on the determined value or values. As described above, the display scale associates units of the metric with a characteristic of a graphical indicator which will be used to represent future values of the metric. Any one or more previously-determined metric values may be used to determine the display scale according to some embodiments. For example, application processor 732 may operate to determine the display scale based on metric values associated with a previous week. Values may be additionally or otherwise filtered, using any known filter, for inclusion in the determination of the display scale. Values which are several standard deviations from a mean value may be excluded, for example.
As described above, determination of the display scale may take into account a maximum display area, for example of display 750. An application processor 732, 734, and/or 736 may therefore communicate with display interface 740 at 5630 to determine a size of an available display area.
According to some embodiments, a display scale may specify an area per number of units of the metric (e.g., 2 cm2/5 steps). A display scale may specify a number of icons per number of units of the metric (e.g., 2 icons/50 ft. in elevation). Embodiments of a display scale may specify any graphical characteristic per number of units of the metric
Next, at S640, second data indicative of user activity is received from the user over a time interval. According to some embodiments, any amount of time may pass between S630 and S640. For example, S610 through S630 may be executed during a calibration period, and flow may pause thereafter until a user operates input controls (e.g., buttons 480 and/or touch screen display 440) to enter a monitoring mode at S640.
With respect to the example of
A graphical indicator representing the second value is generated at S660 based on the display scale and the second value. One of application processors 722, 724 and 726 may generate the graphical indicators at S660. Reiterating an example described above, a display scale of 50 BPM/1 cm is determined at S630 and a value of 125 BPM is determined at S650 based on the second data. Accordingly, a graphical indicator having a length of 2.5 cm is generated at S660.
The graphical indicator is displayed at S670. Display of the graphical indicator may comprise transmitting a visualization including the graphical indicator to another device for display, or displaying the graphical indicators on an on-board display. According to some embodiments, one of application processors 722, 724 and 726 transmits the graphical indicator to display interface 740 at S670, and display interface 740 controls display 750 to display the graphical interface thereon.
A position of graphical indicator 810 indicates the time interval associated with the graphical indicator. In the present example, graphical indicator 810 is positioned at the ‘0’ minute position of a traditional analog clock layout, therefore graphical indicator 810 is associated with the 60th minute of the prior hour. More specifically, graphical indicator 810 indicates a heart rate of 90 BPM over the 60th minute of the prior hour. Accordingly, some embodiments efficiently convey values associated with respective time intervals in an intuitive manner which can be quickly grasped by a user.
Returning to process 600, flow continues from S670 to S640 to receive additional data from the user. Accordingly, flow cycles between S640 and S670 to receive new data indicative of physical activity, to determine new matric values based on the data, and to generate and display new graphical indicators based on the values and on the previously-determined display scale.
The new graphical indicators may be displayed along with previously-generated and displayed indicators so as to convey changes in metric values over time.
More specifically, distal ends 1215 of graphical indicators 1210A through 1210D are located on arc 1220 at the :00, :01, :02 and :03 positions of an analog clock, respectively. These positions correspond to time intervals which are one minute in length. The time intervals associated with each graphical indicator may exhibit any duration. For example, each position of an end 1215 may correspond to a five minute interval, a ten minute interval, or an interval of any duration. In a case that a complete circle includes sixty graphical indicators and corresponds to twelve hours, each graphical indicator is associated with a twelve minute interval. Similarly, in a case that a complete circle includes sixty graphical indicators and corresponds to twenty-four hours, each graphical indicator is associated with a twenty-four minute interval.
Visualization 1500 of
Embodiments are not limited to the graphical indicators described herein. A visualization according to some embodiments may include two or more types of graphical indicators. A visualization according to some embodiments may also include displayed elements in addition to the graphical indicators and other elements shown herein.
According to some embodiments, flow may occasionally return to S630 to determine a new display scale. For example, the display scale may be determined based on data which was received after the original determination of the display scale. This re-determination may occur daily, weekly, monthly, or in response to any condition, such as a determination that the determined metric values consistently meet (or fail to meet) a threshold. Such a feature may account for changes in the user's fitness and/or physiology.
Process 600 may pause or terminate at any time according to some embodiments. For example, a user may input an instruction to switch a monitoring mode, causing termination of process 600. Data may continue to be received from the user as described herein despite termination of process 600, and that data may be used to determine a display scale upon resumption of process 600.
Prior to process 1600, it will be assumed that a device embodying process 1600 is activated (i.e., powered on, woken from sleep, etc.) or otherwise instructed to enter a mode for displaying a visualization according to some embodiments.
S1605 through S1615 may be executed as described above with respect to S610 through S630 of process 600, but implementations are not limited thereto. After execution of S630, a display scale has been determined which associates units of a metric with a characteristic of a graphical indicator which will be used to represent future values of the metric. In the present example, the metric is step count and the display scale associates a length of a graphical indicator with a number of steps.
Next, at S1620, a value of the metric is determined for each of a plurality of time intervals of the current hour. The value for each time interval is determined based on second data indicative of physical activity of the user over that time interval. The current time may be determined from a network to which the device is connected (i.e., wired or wirelessly), from an on-board clock, or by other means. For example, if a current time of 12:43 pm is determined, so a value of the metric is determined for each completed minute of the current hour (i.e., for each of forty-two completed minutes). Time intervals are not limited to single minutes in some implementations, as described above. It will be assumed that the metric in the current example is step count, therefore forty step count values are determined at S1620.
For each of the plurality of time intervals, a graphical indicator associated with the time interval is generated at S1625. The length of a graphical indicator is determined based on the display scale and on the value of the metric for the time interval associated with the graphical indicator.
The plurality of graphical indicators are displayed at S1630. According to some embodiments, a position of each of the displayed plurality of graphical indicators indicates a time interval associated with each graphical indicator.
Next, at S1640, a signal indicative of physical activity over a next time interval is detected. In the present example, the next time interval is the forty-third minute of the hour, since values have been determined for the initial forty-two minutes of the hour. The signal may be detected by a sensor such as those already described. More than one signal from more than one sensor may be detected at S1640, depending on the information needed to determine a value of the particular metric being evaluated. In this regard, a next value of the metric is determined at S1645 and, as described with respect to S650 and S660, a graphical indicator representing the next value and associated with the next time interval is determined at S1650. The length of the graphical indicator is determined based on the display scale and on the next value of the metric.
As illustrated by graphical indicator 1810 of
At S1660, it is then determined whether the metric of interest has changed. According to some embodiments, the metric of interest may change to another metric based on a schedule, in which case S1660 consists of confirming the schedule. In some embodiments, a user may issue a command to change the schedule. The command may be issued via buttons such as buttons 480, or by performing a touch screen gesture, such as a swipe, upon display 440. Any suitable input modality may be used to issue such a command.
If it is not determined to change the metric at S1660, it is determined whether the current time has entered a new hour. If not, flow continues to S1640 and to determine a new value, to generate a new graphical indicator based on the value and the display scale, and to display the new graphical indicator at an appropriate position on the arc of the circle.
Upon determining at S1660 that the metric is to be changed, flow returns to the beginning of process 1600 to determine a display scale, and to generate and display a plurality of graphical indicators based on the display scale and on values of the new metric for each time interval of the current hour.
On the other hand, if it is determined at S1665 that a new hour has arrived, flow returns to S1620 to determine a plurality of values of the new metric for a plurality of time intervals of the new hour (S1620), to generate a graphical indicator for each of the values based on the display scale (S1625), and to display the graphical indicators (S1630), where a position of a displayed graphical indicator indicates a time interval associated with the graphical representation.
Upon returning to S1620 from S1665 during the first minute of the hour, no time intervals of the new hour will have elapsed, so the first value and graphical indicator of the current hour are determined at S1645 and S1650. The graphical indicator is displayed at S1655 as part of a new visualization, as illustrated by visualization 2100 of
The foregoing diagrams represent logical architectures for describing processes according to some embodiments, and actual implementations may include more or different components arranged in other manners. Other topologies may be used in conjunction with other embodiments. Moreover, each system described herein may be implemented by any number of devices in communication via any number of other public and/or private networks. Two or more of such computing devices may be located remote from one another and may communicate with one another via any known manner of network(s) and/or a dedicated connection. Each device may include any number of hardware and/or software elements suitable to provide the functions described herein as well as any other functions. For example, any computing device used in an implementation of some embodiments may include a processor to execute program code such that the computing device operates as described herein.
All systems and processes discussed herein may be embodied in program code stored on one or more non-transitory computer-readable media. Such media may include, for example, a floppy disk, a CD-ROM, a DVD-ROM, a Flash drive, magnetic tape, and solid state Random Access Memory (RAM) or Read Only Memory (ROM) storage units. Embodiments are therefore not limited to any specific combination of hardware and software.
Those in the art will appreciate that various adaptations and modifications of the above-described embodiments can be configured without departing from the scope and spirit of the claims. Therefore, it is to be understood that the claims may be practiced other than as specifically described herein.
This is a continuation of co-pending prior U.S. patent application Ser. No. 14/250,635, filed on Apr. 11, 2014, entitled “PERSONALIZED SCALING OF GRAPHICAL INDICATORS”, which is incorporated herein by reference in its entirety for all purposes.
Number | Name | Date | Kind |
---|---|---|---|
2717736 | Schlesinger | Sep 1955 | A |
2883255 | Anderson | Apr 1959 | A |
3163856 | Kirby | Dec 1964 | A |
3250270 | Bloom | May 1966 | A |
3918658 | Beller | Nov 1975 | A |
4192000 | Lipsey | Mar 1980 | A |
4244020 | Ratcliff | Jan 1981 | A |
4281663 | Pringle | Aug 1981 | A |
4284849 | Anderson et al. | Aug 1981 | A |
4312358 | Barney | Jan 1982 | A |
4367752 | Jimenez et al. | Jan 1983 | A |
4390922 | Pelliccia | Jun 1983 | A |
4407295 | Steuer et al. | Oct 1983 | A |
4575804 | Ratcliff | Mar 1986 | A |
4578769 | Frederick | Mar 1986 | A |
4617525 | Lloyd | Oct 1986 | A |
4887249 | Thinesen | Dec 1989 | A |
4962469 | Ono et al. | Oct 1990 | A |
4977509 | Pitchford et al. | Dec 1990 | A |
5058427 | Brandl | Oct 1991 | A |
5224059 | Nitta et al. | Jun 1993 | A |
5295085 | Hoffacker | Mar 1994 | A |
5323650 | Fullen et al. | Jun 1994 | A |
5446705 | Haas et al. | Aug 1995 | A |
5456648 | Edinburg et al. | Oct 1995 | A |
5583776 | Levi et al. | Dec 1996 | A |
5583830 | Okuyama | Dec 1996 | A |
5671162 | Werbin | Sep 1997 | A |
5704350 | Williams, III | Jan 1998 | A |
5724265 | Hutchings | Mar 1998 | A |
5737246 | Furukawa et al. | Apr 1998 | A |
5788655 | Yoshimura et al. | Aug 1998 | A |
5890128 | Diaz et al. | Mar 1999 | A |
5891042 | Sham et al. | Apr 1999 | A |
5894311 | Jackson | Apr 1999 | A |
5899963 | Hutchings | May 1999 | A |
5908396 | Hayakawa et al. | Jun 1999 | A |
5947868 | Dugan | Sep 1999 | A |
5955667 | Fyfe | Sep 1999 | A |
5976083 | Richardson et al. | Nov 1999 | A |
6018705 | Gaudet et al. | Jan 2000 | A |
6077193 | Buhler et al. | Jun 2000 | A |
6085248 | Sambamurthy et al. | Jul 2000 | A |
6129686 | Friedman | Oct 2000 | A |
6145389 | Ebeling et al. | Nov 2000 | A |
6183425 | Whalen et al. | Feb 2001 | B1 |
6213872 | Harada et al. | Apr 2001 | B1 |
6241684 | Amana et al. | Jun 2001 | B1 |
6269054 | Truini | Jul 2001 | B1 |
6287262 | Amana et al. | Sep 2001 | B1 |
6301964 | Fyfe et al. | Oct 2001 | B1 |
6302789 | Harada et al. | Oct 2001 | B2 |
6305221 | Hutchings | Oct 2001 | B1 |
6309360 | Mault | Oct 2001 | B1 |
6469639 | Tanenhaus et al. | Oct 2002 | B2 |
6478736 | Mault | Nov 2002 | B1 |
6513381 | Fyfe et al. | Feb 2003 | B2 |
6513532 | Mault et al. | Feb 2003 | B2 |
6525997 | Narayanaswami et al. | Feb 2003 | B1 |
6527711 | Stivoric et al. | Mar 2003 | B1 |
6529827 | Beason et al. | Mar 2003 | B1 |
6556222 | Narayanaswami | Apr 2003 | B1 |
6561951 | Cannon et al. | May 2003 | B2 |
6571200 | Mault | May 2003 | B1 |
6583369 | Montagnino et al. | Jun 2003 | B2 |
6585622 | Shum et al. | Jul 2003 | B1 |
6601988 | Molander | Aug 2003 | B2 |
6607493 | Song | Aug 2003 | B2 |
6620078 | Pfeffer | Sep 2003 | B2 |
6678629 | Tsuji | Jan 2004 | B2 |
6699188 | Wessel | Mar 2004 | B2 |
6704016 | Oliver et al. | Mar 2004 | B1 |
6720860 | Narayanaswami | Apr 2004 | B1 |
6761064 | Tsuji | Jul 2004 | B2 |
6790178 | Mault et al. | Sep 2004 | B1 |
6808473 | Hisano et al. | Oct 2004 | B2 |
6811516 | Dugan | Nov 2004 | B1 |
6813582 | Levi et al. | Nov 2004 | B2 |
6813931 | Yadav et al. | Nov 2004 | B2 |
6856938 | Kurtz | Feb 2005 | B2 |
7006856 | Baker et al. | Feb 2006 | B2 |
7035170 | Narayanaswami | Apr 2006 | B2 |
7062225 | White | Jun 2006 | B2 |
7113450 | Plancon et al. | Sep 2006 | B2 |
7162368 | Levi et al. | Jan 2007 | B2 |
7167743 | Heruth et al. | Jan 2007 | B2 |
7171331 | Vock et al. | Jan 2007 | B2 |
7200517 | Darley et al. | Apr 2007 | B2 |
7246033 | Kudo | Jul 2007 | B1 |
7261690 | Teller et al. | Aug 2007 | B2 |
7272982 | Neuhauser et al. | Sep 2007 | B2 |
7278966 | Hjelt et al. | Oct 2007 | B2 |
7373820 | James | May 2008 | B1 |
7443292 | Jensen et al. | Oct 2008 | B2 |
7457724 | Vock et al. | Nov 2008 | B2 |
7467060 | Kulach et al. | Dec 2008 | B2 |
7505865 | Ohkubo et al. | Mar 2009 | B2 |
7533326 | Chambers | May 2009 | B2 |
7559877 | Parks et al. | Jul 2009 | B2 |
7587237 | Korzinov et al. | Sep 2009 | B2 |
7623415 | Raeber et al. | Nov 2009 | B2 |
7653508 | Kahn et al. | Jan 2010 | B1 |
7676332 | Damen | Mar 2010 | B2 |
7690556 | Kahn et al. | Apr 2010 | B1 |
7713172 | Shin et al. | May 2010 | B2 |
7717866 | Damen | May 2010 | B2 |
7738320 | Taha | Jun 2010 | B2 |
7774156 | Niva et al. | Aug 2010 | B2 |
7789802 | Lee et al. | Sep 2010 | B2 |
7881802 | Quiles et al. | Feb 2011 | B2 |
7927253 | Vincent et al. | Apr 2011 | B2 |
7940604 | Inoue et al. | May 2011 | B2 |
7959539 | Takeishi et al. | Jun 2011 | B2 |
7983876 | Vock et al. | Jul 2011 | B2 |
8028443 | Case, Jr. | Oct 2011 | B2 |
8055469 | Kulach et al. | Nov 2011 | B2 |
8099318 | Moukas et al. | Jan 2012 | B2 |
8177260 | Trapper et al. | May 2012 | B2 |
8180591 | Yuen et al. | May 2012 | B2 |
8180592 | Yuen et al. | May 2012 | B2 |
8257228 | Quatrochi et al. | Sep 2012 | B2 |
8311769 | Yuen et al. | Nov 2012 | B2 |
8311770 | Yuen et al. | Nov 2012 | B2 |
8350856 | Nazir et al. | Jan 2013 | B1 |
8386008 | Yuen et al. | Feb 2013 | B2 |
8437980 | Yuen et al. | May 2013 | B2 |
8463576 | Yuen et al. | Jun 2013 | B2 |
8463577 | Yuen et al. | Jun 2013 | B2 |
8475367 | Yuen et al. | Jul 2013 | B1 |
8543185 | Yuen et al. | Sep 2013 | B2 |
8543351 | Yuen et al. | Sep 2013 | B2 |
8548770 | Yuen et al. | Oct 2013 | B2 |
8583402 | Yuen et al. | Nov 2013 | B2 |
8597093 | Engelberg et al. | Dec 2013 | B2 |
8615377 | Yuen et al. | Dec 2013 | B1 |
8620617 | Yuen et al. | Dec 2013 | B2 |
8670953 | Yuen et al. | Mar 2014 | B2 |
8805348 | Matsuoka | Aug 2014 | B2 |
9449365 | Roberts | Sep 2016 | B2 |
9449409 | Roberts | Sep 2016 | B2 |
20010055242 | Deshmukh et al. | Dec 2001 | A1 |
20020013717 | Ando et al. | Jan 2002 | A1 |
20020077219 | Cohen et al. | Jun 2002 | A1 |
20020082144 | Pfeffer | Jun 2002 | A1 |
20020109600 | Mault et al. | Aug 2002 | A1 |
20020178060 | Sheehan | Nov 2002 | A1 |
20020198776 | Nara et al. | Dec 2002 | A1 |
20030018523 | Rappaport et al. | Jan 2003 | A1 |
20030050537 | Wessel | Mar 2003 | A1 |
20030065561 | Brown et al. | Apr 2003 | A1 |
20030131059 | Brown et al. | Jul 2003 | A1 |
20040054497 | Kurtz | Mar 2004 | A1 |
20040061324 | Howard | Apr 2004 | A1 |
20040117963 | Schneider | Jun 2004 | A1 |
20040152957 | Stivoric et al. | Aug 2004 | A1 |
20050037844 | Shum et al. | Feb 2005 | A1 |
20050038679 | Short | Feb 2005 | A1 |
20050054938 | Wehman et al. | Mar 2005 | A1 |
20050102072 | Deakin | May 2005 | A1 |
20050102172 | Sirmans, Jr. | May 2005 | A1 |
20050107723 | Wehman et al. | May 2005 | A1 |
20050202934 | Olrik et al. | Sep 2005 | A1 |
20050228692 | Hodgdon | Oct 2005 | A1 |
20050234742 | Hodgdon | Oct 2005 | A1 |
20050248718 | Howell et al. | Nov 2005 | A1 |
20050272564 | Pyles et al. | Dec 2005 | A1 |
20060020177 | Sea et al. | Jan 2006 | A1 |
20060025282 | Redmann | Feb 2006 | A1 |
20060047208 | Yoon | Mar 2006 | A1 |
20060047447 | Brady et al. | Mar 2006 | A1 |
20060089542 | Sands | Apr 2006 | A1 |
20060129436 | Short | Jun 2006 | A1 |
20060143645 | Vock et al. | Jun 2006 | A1 |
20060264730 | Stivoric et al. | Nov 2006 | A1 |
20060277474 | Robarts et al. | Dec 2006 | A1 |
20060282021 | DeVaul et al. | Dec 2006 | A1 |
20060287883 | Turgiss et al. | Dec 2006 | A1 |
20070050715 | Behar | Mar 2007 | A1 |
20070051369 | Choi et al. | Mar 2007 | A1 |
20070123391 | Shin et al. | May 2007 | A1 |
20070136093 | Rankin et al. | Jun 2007 | A1 |
20070155277 | Amitai et al. | Jul 2007 | A1 |
20070159926 | Prstojevich et al. | Jul 2007 | A1 |
20070179356 | Wessel | Aug 2007 | A1 |
20070194066 | Ishihara et al. | Aug 2007 | A1 |
20070208544 | Kulach et al. | Sep 2007 | A1 |
20070276271 | Chan | Nov 2007 | A1 |
20080062719 | Shiau et al. | Mar 2008 | A1 |
20080093838 | Trapper et al. | Apr 2008 | A1 |
20080125288 | Case | May 2008 | A1 |
20080140163 | Keacher et al. | Jun 2008 | A1 |
20080140338 | No et al. | Jun 2008 | A1 |
20080249836 | Angell et al. | Oct 2008 | A1 |
20090018797 | Kasama et al. | Jan 2009 | A1 |
20090043531 | Kahn et al. | Feb 2009 | A1 |
20090048044 | Oleson et al. | Feb 2009 | A1 |
20090054737 | Magar et al. | Feb 2009 | A1 |
20090063293 | Mirrashidi et al. | Mar 2009 | A1 |
20090171788 | Trapper et al. | Jul 2009 | A1 |
20090271147 | Sugai | Oct 2009 | A1 |
20100331145 | Lakovic et al. | Dec 2010 | A1 |
20100331657 | Mensinger et al. | Dec 2010 | A1 |
20110003665 | Burton et al. | Jan 2011 | A1 |
20110009051 | Khedouri et al. | Jan 2011 | A1 |
20110009727 | Mensinger et al. | Jan 2011 | A1 |
20110022349 | Stirling et al. | Jan 2011 | A1 |
20110032105 | Hoffman et al. | Feb 2011 | A1 |
20110080349 | Holbein et al. | Apr 2011 | A1 |
20110106449 | Chowdhary et al. | May 2011 | A1 |
20110126143 | Williams et al. | May 2011 | A1 |
20110131005 | Ueshima et al. | Jun 2011 | A1 |
20110193704 | Harper et al. | Aug 2011 | A1 |
20120020649 | Vanderkaden | Jan 2012 | A1 |
20120072165 | Jallon | Mar 2012 | A1 |
20120083705 | Yuen et al. | Apr 2012 | A1 |
20120083714 | Yuen et al. | Apr 2012 | A1 |
20120083715 | Yuen et al. | Apr 2012 | A1 |
20120083716 | Yuen et al. | Apr 2012 | A1 |
20120084053 | Yuen et al. | Apr 2012 | A1 |
20120084054 | Yuen et al. | Apr 2012 | A1 |
20120092157 | Tran | Apr 2012 | A1 |
20120183939 | Aragones et al. | Jul 2012 | A1 |
20120226471 | Yuen et al. | Sep 2012 | A1 |
20120226472 | Yuen et al. | Sep 2012 | A1 |
20120227737 | Mastrototaro et al. | Sep 2012 | A1 |
20120265326 | Prstojevich et al. | Oct 2012 | A1 |
20120265480 | Oshima | Oct 2012 | A1 |
20120274508 | Brown | Nov 2012 | A1 |
20120316471 | Rahman et al. | Dec 2012 | A1 |
20120330109 | Tran | Dec 2012 | A1 |
20130006718 | Nielsen et al. | Jan 2013 | A1 |
20130072169 | Ross et al. | Mar 2013 | A1 |
20130073254 | Yuen et al. | Mar 2013 | A1 |
20130073255 | Yuen et al. | Mar 2013 | A1 |
20130080113 | Yuen et al. | Mar 2013 | A1 |
20130095459 | Tran | Apr 2013 | A1 |
20130096843 | Yuen et al. | Apr 2013 | A1 |
20130106684 | Weast et al. | May 2013 | A1 |
20130151196 | Yuen et al. | Jun 2013 | A1 |
20130158369 | Yuen et al. | Jun 2013 | A1 |
20130163390 | Gossweiler, III et al. | Jun 2013 | A1 |
20130231574 | Tran | Sep 2013 | A1 |
20130267249 | Rosenberg | Oct 2013 | A1 |
20130268236 | Yuen et al. | Oct 2013 | A1 |
20130280682 | Levine et al. | Oct 2013 | A1 |
20130310896 | Mass | Nov 2013 | A1 |
20130325396 | Yuen et al. | Dec 2013 | A1 |
20130325399 | Yuen et al. | Dec 2013 | A1 |
20140035761 | Burton et al. | Feb 2014 | A1 |
20140039804 | Park et al. | Feb 2014 | A1 |
20140039839 | Yuen et al. | Feb 2014 | A1 |
20140039840 | Yuen et al. | Feb 2014 | A1 |
20140039841 | Yuen et al. | Feb 2014 | A1 |
20140039842 | Yuen et al. | Feb 2014 | A1 |
20140052790 | Yuen et al. | Feb 2014 | A1 |
20140067278 | Yuen et al. | Mar 2014 | A1 |
20140107493 | Yuen et al. | Apr 2014 | A1 |
20140125491 | Park et al. | May 2014 | A1 |
20140127996 | Park et al. | May 2014 | A1 |
20140129243 | Utter, II | May 2014 | A1 |
20140135631 | Brumback et al. | May 2014 | A1 |
20140142403 | Brumback et al. | May 2014 | A1 |
20140143064 | Tran | May 2014 | A1 |
20140143737 | Mistry et al. | May 2014 | A1 |
20170004639 | Roberts | Jan 2017 | A1 |
Number | Date | Country |
---|---|---|
2008038141 | Apr 2008 | WO |
2009042965 | Apr 2009 | WO |
Entry |
---|
“Forerunner 301 Personal Trainer Owner's Manual”, Feb. 2006, Garmin Ltd. or its subsidiaries, Part No. 190-00370-00 Rev. F. 65 pgs. |
“Quick Installation Guide”, Withings Pulse, Jul. 24, 2013, 16pgs. withings.com/pulse. |
Cooper, Daniel, “Withings Pulse review”, Aug. 16, 2013, http://www.engadgel.com/2013/08/16/withings-pulse- review/, (pp. 1-8, total 8 pages). |
Desmarais, Christina, “Which New Activity Tracker is Best for You?”, Sep. 3, 2013, retrieved Sep. 23, 2013, retrieved from http:l/www.techlicious.com/guide/which-new-activity-tracker-is-right-for-you/, (pp. 1-4, total 4 pages). |
Lester, Jonathan et al., “Validated Caloric Expenditure Estimation using a Single Body-Worn Sensor”, UbiComp 2009, Sep. 30-Oct. 3, 2009, Orlando, Florida, USA, ACM 978-1-60558-431-7/09/09 (pp. 225-234, total 10 pages). |
Intersema, “Using MS5534 for altimeters and barometers”, AN501.doc, Application Note, www.intersema.ch, (pp. 1-12, total 12 pages). |
Suunto Lumi “User Guide” Jun. 2007, Sep. 2007, 49 pages. |
VTI Technologies Oy, “SCP100-D01/D11 Pressure Sensor as Barometer and Altimeter”, Application Note 33, www.vti. fi, 3 pgs. |
“Forerunner 405 Owner's Manual: GPS-Enabled Sports Watch With Wireless Sync”, Mar. 2011, Garmin Ltd. or its subsidiaries, Part No. 190-00700-00 Rev. D, 54 pgs. |
“Forerunner 410 Owner's Manual: GPS-Enabled Sports Watch With Wireless Sync”, Jul. 2012, Garmin Ltd. or its subsidiaries, Part No. 190-01274-00 Rev. B, 50 pgs. |
“Forerunner 405CX Owner's Manual: GPS-Enabled Sports Watch With Wireless Sync”, Mar. 2009, Garmin Ltd. or its subsidiaries, Part No. 190-01066-00 Rev. B, 55 pgs. |
“Forerunner 310XT Owner's Manual: Multisport GPS Training Device”, 2009, Garmin Ltd. or its subsidiaries, Part No. 190-01066-00 Rev. B, 56pgs. |
Ohtaki, Yasuaki et al., “Automatic classification of ambulatory movements and evaluation of energy consumptions utilizing accelerometers and a barometer”, Microsyst Technol (2005) 11, DOl: 10.1007/s00542-005-0502-z, (pp. 1034-1040, total 7 pages). |
Retscher, G. “An Intelligent Multi-sensor System for Pedestrian Navigation”, Journal of Global Positioning Systems, (2006), vol. 5, No. 1-2, (pp. 110-118, 9 total pages). |
Clifford, Michelle et al., “Altimeter and Barometer System”, Freescale Semiconductor Application Note, AN1979, Rev. 3, Nov. 2006, 10 pgs. |
Parkka, Juha et al., “Activity Classification Using Realistic Data From Wearable Sensors”, IEEE Transactions on Information Technology in Biomedicine, vol. 10, No. 1, Jan. 2006, (pp. 119-128, total 10 pages). |
DC Rainmaker, “Basis Bi Watch In-Depth Review”, Feb. 4, 2014, http://www.dcrainmaker.com/2013/07/basis-bi-review.html, 56 pgs. |
Lester, Jonathan et al., “A Hybrid Discriminative/Generative Approach for Modeling Human Activities”, IJCAI'05 Proceedings of the 19th International Joint Conference on Artificial Intelligence, 2005, 7pgs. |
“Activator is One of the Best Cydia iPhone Hacks”, retrieved on Jul. 9, 2013, download from http://www.iphone-lips-and-advice.com/activator.html, 10 pgs. |
“Forerunner 50 Owner's Manual: With ANT+Sport wireless technology”, Nov. 2007, Garmin Ltd. or its subsidiaries, Part No. 190-00839-00 Rev. E, 44 pgs. |
“Forerunner 10 Owner's Manual”, Aug. 2012, Garmin Ltd. or its subsidiaries, Part No. 190-01472-00_0A, 8 pgs. |
“Forerunner 110 Owner's Manual: GPS-Enabled Sports Watch”, Dec. 2010, Garmin Ltd. or its subsidiaries, Part No. 190-01154-00 Rev. D, 16 pgs. |
“Forerunner 201 Personal Trainer Owner's Manual”, Feb. 2006, Garmin Ltd. or its subsidiaries, Part No. 190-00318-00 Rev. F, 48 pgs. |
“Forerunner 210 Owner's Manual: GPS-Enabled Sports Watch”, Dec. 2010, Garmin Ltd. or its subsidiaries, Part No. 190-01273-00 Rev. B, 28 pgs. |
U.S. Office Action dated Sep. 18, 2014, in U.S. Appl. No. 14/250,635. |
U.S. Final Office Action dated Dec. 24, 2014, in U.S. Appl. No. 14/250,635. |
U.S. Notice of Allowance dated Mar. 23, 2016, in U.S. Appl. No. 14/250,635. |
U.S. Office Action dated Sep. 16, 2014, in U.S. Appl. No. 14/250,590. |
U.S. Final Office Action dated Feb. 11, 2015, in U.S. Appl. No. 14/250,590. |
U.S. Office Action dated Oct. 27, 2015, in U.S. Appl. No. 14/250,590. |
U.S. Notice of Allowance dated May 26, 2016, in U.S. Appl. No. 14/250,590. |
U.S. Office Action dated Dec. 6, 2017, in U.S. Appl. No. 15/266,223. |
Number | Date | Country | |
---|---|---|---|
20160307295 A1 | Oct 2016 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 14250635 | Apr 2014 | US |
Child | 15189245 | US |