Patent Grant
11574725
An Application Data Sheet is filed concurrently with this specification as part of the present application. Each application that the present application claims benefit of or priority to as identified in the concurrently filed Application Data Sheet is incorporated by reference herein in its entirety and for all purposes.
The present disclosure relates to systems and methods for fitness activity related messaging.
In recent years, the need for health and fitness has grown tremendously. The growth has occurred due to a better understanding of the benefits of good fitness to overall health and wellness. Unfortunately, although today's modern culture has brought about many new technologies, such as the Internet, connected devices and computers, people have become less active. Additionally, many office jobs require people to sit in front of computer screens for long periods of time, which further reduces a person's activity levels. Furthermore, much of today's entertainment options involve viewing multimedia content, computer social networking, and other types of computer involved interfacing. Although such computer activity can be very productive as well as entertaining, such activity tends to reduce a person's overall physical activity.
To provide users concerned with health and fitness a way of measuring or accounting for their activity or lack thereof, fitness activity trackers have recently grown in popularity. Fitness activity trackers are used to measure activity, such as walking, motion, running, sleeping, being inactive, bicycling, exercising on an elliptical trainer, and the like. Typically, the data collected by such devices can be transferred and viewed on a computing device.
It is in this context that embodiments of the invention arise.
Embodiments described in the present disclosure provide systems, apparatus, computer readable media, and methods for fitness activity related messaging.
In one embodiment, a method for generating a message to a friend of a user is provided, comprising: processing activity data of a first user measured by an activity monitoring device to update a value of an activity metric for the first user; identifying a change in an inequality relationship between the value of the activity metric for the first user and a value of the activity metric for a second user; in response to identifying the change in the inequality relationship, prompting the first user to generate a message to the second user.
In one embodiment, the change in the inequality relationship is defined by the value of the activity metric for the first user changing, from being less than the value of the activity metric for the second user, to being greater than the value of the activity metric for the second user.
In one embodiment, the change in the inequality relationship is defined by the value of the activity metric for the first user changing, from being greater than the value of the activity metric for the second user, to being less than the value of the activity metric for the second user.
In one embodiment, the inequality relationship between the value of the activity metric for the first user and the value of the activity metric for the second user defines a relative ranking of the first user and the second user on a competitive leaderboard for the activity metric.
In one embodiment, the change in the inequality relationship defines a change in the relative ranking of the first user and the second user on the competitive leaderboard for the activity metric.
In one embodiment, prompting the user to generate a message includes identifying the change in the relative ranking of the first user and the second user.
In one embodiment, prompting the first user to generate a message to the second user includes triggering a notification to the first user, the notification providing access to an interface configured to receive input from the first user to define content of the message to the second user.
In one embodiment, the notification is a push notification to a mobile device.
In one embodiment, the interface provides at least one option to send a predefined message to the second user.
In one embodiment, the activity metric is defined by one or more of the following: step count, elevation climbed, distance traveled, active amount of time.
In another embodiment, a method for providing a competitive leaderboard is provided, comprising: receiving a request to display a messaging thread, the messaging thread defined by one or more messages between members of the messaging thread; in response to the request, presenting the messaging thread; for each of the members, retrieving a value of an activity metric; determining a ranked order for the members based on each member's respective value of the activity metric; presenting a leaderboard in conjunction with the messaging thread, the leaderboard defined to display each member's value of the activity metric according to the ranked order; wherein the method is executed by at least one processor.
In one embodiment, the value for the activity metric for a given member is processed from activity data captured by an activity monitoring device associated with the given member.
In one embodiment, receiving the request to display the messaging thread is defined by access activity associated with an inbox defined for a member of the messaging thread.
In one embodiment, the method further comprises: determining whether each of the members of the messaging thread are linked to each other on a social network, and if so, then performing the operation of presenting the leaderboard, and if not, then not performing the operation of presenting the leaderboard.
In one embodiment, the activity metric is selected from a quantity of steps taken, a quantity of floors climbed, or a quantity of calories burned.
In another embodiment, a method for generating a competitive group is provided, comprising: determining a number of messages in a message thread; when the number of messages in the message thread reaches a predefined threshold, providing an option to a first member of the message thread to generate a competitive group for members of the message thread; in response to activation of the option by the first member, sending invitations to remaining members of the message thread to join the competitive group; receiving responses to the sent invitations; generating the competitive group, the competitive group defined to include the first member and, each of the remaining members of the message thread that provides a positive response to the invitation; wherein membership in the competitive group provides access to a value of an activity metric for each of the members of the competitive group.
In one embodiment, the value for the activity metric for a member of the competitive group is processed from activity data captured by an activity monitoring device associated with the member.
In one embodiment, activation of the option includes identifying the activity metric for which membership in the competitive group provides access.
In one embodiment, the activity metric is selected from a quantity of steps taken, a quantity of floors climbed, or a quantity of calories burned.
In another embodiment, a method for forming a competitive group is provided, comprising: determining a quantity of messaging from a first user to one or more second users; when the quantity of messaging exceeds a predefined threshold, then providing an option to the first user to create a competitive group inclusive of the first user and the one or more second users; wherein membership in the competitive group provides access to values of an activity metric for each of the members of the competitive group.
In one embodiment, the quantity of messaging is defined by a number of messages sent from the first user to the one or more second users.
In one embodiment, the quantity of messaging is defined by a frequency of messages sent from the first user to the one or more second users.
In one embodiment, the method further comprises: in response to activation of the option to create the competitive group, sending invitations to each of the one or more second users to join the competitive group; receiving responses to the invitations; generating the competitive group based on the responses to the invitations.
In one embodiment, membership in the competitive group provides access to a group leaderboard, the group leaderboard configured to present a ranked order of the members of the group according to the values of the activity metric for each of the members of the competitive group. In another embodiment, a method is provided, comprising: receiving activity data associated with a first user account, the activity data associated with the first user account being determined from motion data detected by an activity tracking device associated with the first user account; receiving activity data associated with a second user account, the activity data associated with the second user account being determined from motion data detected by an activity tracking device associated with the second user account; processing the activity data associated with the first user account to determine a cumulative activity level for the first user account; processing the activity data associated with the second user account to determine a cumulative activity level for the second user account; comparing the cumulative activity levels for the first and second user accounts; in response to detecting a passing event, defined by the cumulative activity level of the first or second user account surpassing that of the other, then generating and sending a message to the first user account and/or the second user account, the message identifying the passing event.
In one embodiment, generating the message includes selecting a message template for the passing event, and populating the message template with customized data based on the activity metrics of the first and/or second user account.
In one embodiment, selecting the message template is based on a magnitude of a difference between the cumulative activity levels of the first and second user accounts.
In one embodiment, selecting the message template is based on whether the message is to be sent to the first user account or the second user account.
In one embodiment, the activity metrics include one or more of steps taken, stairs climbed, floors climbed, distance traveled, active minutes, heart rate, and/or sleep data.
In one embodiment, sending the message to the first or second user account effects display of the message on one or more of the activity tracking device or a mobile device that is associated to the first or second user account, respectively.
In one embodiment, sending the message is defined by one or more of a push notification, a private message, or an e-mail.
In one embodiment, the method further includes: generating and sending a message identifying the passing event to a third user account, the third user account being identified as a member of a social graph of the first or second user account.
Other aspects will become apparent from the following detailed description, taken in conjunction with the accompanying drawings, illustrating by way of example the principles of embodiments described in the present disclosure.
Various embodiments described in the present disclosure may best be understood by reference to the following description taken in conjunction with the accompanying drawings.
Embodiments described in the present disclosure provide systems, apparatus, computer readable media, and methods for fitness activity related messaging.
It should be noted that there are many inventions described and illustrated herein. The present inventions are neither limited to any single aspect nor embodiment thereof, nor to any combinations and/or permutations of such aspects and/or embodiments. Moreover, each of the aspects of the present inventions, and/or embodiments thereof, may be employed alone or in combination with one or more of the other aspects of the present inventions and/or embodiments thereof. For the sake of brevity, many of those permutations and combinations will not be discussed separately herein.
Further, in the course of describing and illustrating the present inventions, various circuitry, architectures, structures, components, functions and/or elements, as well as combinations and/or permutations thereof, are set forth. It should be understood that circuitry, architectures, structures, components, functions and/or elements other than those specifically described and illustrated, are contemplated and are within the scope of the present inventions, as well as combinations and/or permutations thereof.
The environmental sensors 118 may be in the form of motion detecting sensors. In some embodiments, a motion sensor can be one or more of an accelerometer, or a gyroscope, or a rotary encoder, or a calorie measurement sensor, or a heat measurement sensor, or a moisture measurement sensor, or a displacement sensor, or an ultrasonic sensor, or a pedometer, or an altimeter, or a linear motion sensor, or an angular motion sensor, or a multi-axis motion sensor, or a combination thereof. The biometric sensors 116 can be defined to measure physiological characteristics of the user that is using the activity tracking device 100. The user interface 114 provides a way for communicating with the activity tracking device 100, in response to user interaction 104. The user interaction 104 can be in the form of physical contact (e.g., without limitation, tapping, sliding, rubbing, multiple taps, gestures, etc.).
In some embodiments, the user interface 114 is configured to receive user interaction 104 by way of proximity sensors, button presses, touch sensitive screen inputs, graphical user interface inputs, voice inputs, sound inputs, etc. The activity tracking device 100 can communicate with a client and/or server 112 using the wireless transceiver 110. The wireless transceiver 110 will allow the activity tracking device 100 to communicate using a wireless connection, which is enabled by wireless communication logic. The wireless communication logic can be in the form of a circuit having radio communication capabilities. The radio communication capabilities can be in the form of a Wi-Fi connection, a Bluetooth connection, a low-energy Bluetooth connection, or any other form of wireless tethering or near field communication. In still other embodiments, the activity tracking device 100 can communicate with other computing devices using a wired connection (not shown). As mentioned, the environmental sensors 118 can detect motion of the activity tracking device 100.
The motion can be activity of the user, such as walking, running, stair climbing, etc. The motion can also be in the form of physical contact received on any surface of the activity tracking device 110, so long as the environmental sensors 118 can detect such motion from the physical contact. Such physical contact may be in the form of a tap or multiple taps by a finger upon the housing of the activity tracking device 100.
As shown in
Some motions will produce and quantify various types of metrics, such as step count, stairs climbed, distance traveled, very active minutes, calories burned, etc. The physical contact logic 142 can include logic that calculates or determines when particular physical contact can qualify as an input. To qualify as an input, the physical contact detected by sensors 156 should have a particular pattern that is identifiable as input. For example, the input may be predefined to be a double tap input, and the physical contact logic 142 can analyze the motion to determine if a double tap indeed occurred in response to analyzing the sensor data produced by sensors 156.
The display interface logic 144 is configured to interface with the processor and the motion-activated messaging logic to determine when specific messages will be displayed on the display screen 122 of the activity tracking device 100. The display interface logic 144 can act to turn on the screen, display metric information, display characters or alphanumeric information, display graphical user interface graphics, or combinations thereof. Alarm management logic 146 can function to provide a user interface and settings for managing and receiving input from a user to set an alarm. The alarm management logic can interface with a timekeeping module (e.g., clock, calendar, time zone, etc.), and can trigger the activation of an alarm. The alarm can be in the form of an audible alarm or a non-audible alarm.
A non-audible alarm can provide such alarm by way of a vibration. The vibration can be produced by a motor integrated in the activity tracking device 100. The vibration can be defined to include various vibration patterns, intensities, and custom set patterns. The vibration produced by the motor or motors of the activity tracking device 100 can be managed by the alarm management logic 146 in conjunction with processing by the processor 106. The wireless communication logic 148 is configured for communication of the activity tracking device with another computing device by way of a wireless signal. The wireless signal can be in the form of a radio signal. As noted above, the radio signal can be in the form of a Wi-Fi signal, a Bluetooth signal, a low energy Bluetooth signal, or combinations thereof. The wireless communication logic can interface with the processor 106, storage 108 and battery 154 of device 100, for transferring activity data, which may be in the form of motion data or processed motion data, stored in the storage 108 to the computing device.
In one embodiment, processor 106 functions in conjunction with the various logic components 140, 142, 144, 146, and 148. The processor 106 can, in one embodiment, provide the functionality of any one or all of the logic components. In other embodiments, multiple chips can be used to separate the processing performed by any one of the logic components and the processor 106. Sensors 156 can communicate via a bus with the processor 106 and/or the logic components. The storage 108 is also in communication with the bus for providing storage of the motion data processed or tracked by the activity tracking device 100. Battery 154 is provided for providing power to the activity tracking device 100.
In one embodiment, remote device 200 communicates with activity tracking device 100 over a Bluetooth connection. In one embodiment, the Bluetooth connection is a low energy Bluetooth connection (e.g., Bluetooth LE, BLE, or Bluetooth Smart). Low energy Bluetooth is configured for providing low power consumption relative to standard Bluetooth circuitry. Low energy Bluetooth uses, in one embodiment, a 2.4 GHz radio frequency, which allows for dual mode devices to share a single radio antenna. In one embodiment, low energy Bluetooth connections can function at distances up to 50 meters, with over the air data rates ranging between 1-3 megabits (Mb) per second. In one embodiment, a proximity distance for communication can be defined by the particular wireless link, and is not tied to any specific standard. It should be understood that the proximity distance limitation will change in accordance with changes to existing standards and in view of future standards and/or circuitry and capabilities.
Remote device 200 can also communicate with the Internet 160 using an Internet connection. The Internet connection of the remote device 200 can include cellular connections, wireless connections such as Wi-Fi, and combinations thereof (such as connections to switches between different types of connection links). The remote device, as mentioned above, can be a smartphone or tablet computer, or any other type of computing device having access to the Internet and with capabilities for communicating with the activity tracking device 100.
A server 220 is also provided, which is interfaced with the Internet 160. The server 220 can include a number of applications that service the activity tracking device 100, and the associated users of the activity tracking device 100 by way of user accounts. For example, the server 220 can include an activity management application 224. The activity management application 224 can include logic for providing access to various devices 100, which are associated with user accounts managed by server 220. Server 220 can include storage 226 that includes various user profiles associated with the various user accounts. The user account 228a for user A and the user account 228n for user N are shown to include various information.
The information can include, without limitation, data associated with motion-activated messaging 230, user data, etc. The motion-activated messaging data 230 includes information regarding a user's preferences, settings, and configurations which are settable by the user or set by default at the server 220 when accessing a respective user account. The storage 226 will include any number of user profiles, depending on the number of registered users having user accounts for their respective activity tracking devices. It should also be noted that a single user account can have various or multiple devices associated therewith, and the multiple devices can be individually customized, managed and accessed by a user. In one embodiment, the server 220 provides access to a user to view the user data 232 associated with activity tracking device. The data viewable by the user includes the tracked motion data, which is processed to identify a plurality of metrics associated with the motion data. The metrics are shown in various graphical user interfaces of a website enabled by the server 220. The website can include various pages with graphical user interfaces for rendering and displaying the various metrics for view by the user associated with the user account. In one embodiment, the website can also include interfaces that allow for data entry and configuration by the user.
The monitoring device of the present inventions may use one, some or all of the following sensors to acquire physiological data, including the physiological data outlined in the table below. All combinations and permutations of physiological sensors and/or physiological data are intended to fall within the scope of the present inventions. The monitoring device of the present inventions may include but is not limited to the types one, some or all of sensors specified below to acquire the corresponding physiological data; indeed, other type(s) of sensors may be employed to acquire the corresponding physiological data, which are intended to fall within the scope of the present inventions. Additionally, the device may derive the physiological data from the corresponding sensor output data, but is not limited to the number or types of physiological data that it could derive from said sensor.
Additional examples of types of data which may be acquired by, or processed from data acquired by, a monitoring device in accordance with embodiments of the invention, are further described in U.S. application Ser. No. 14/221,234, filed Mar. 20, 2014, entitled “Portable Monitoring Devices for Processing Applications and Processing Analysis of Physiological Conditions of a User Associated With the Portable Monitoring Device,” the disclosure of which is herein incorporated by reference for all purposes.
A recent activity module 300 is configured to graphically display various metrics from recently detected activity of the user, such as the number of calories burned over time, a number of steps taken over time, or a number of floors climbed over time. In the illustrated embodiment, the module 300 is configured to display a number of calories burned during the course of the present day. A steps module 302 is configured to display a total number of steps taken over a given time period (e.g. last hour, current day, current week, etc.) or towards a particular goal or milestone. In one embodiment, the display of the step count is graphically portrayed, e.g. by a circular meter.
A friends module 304 is configured to display a listing of friends of the user on a social network. The friends are members of a social graph of the user that is defined by the social network. In the illustrated embodiment, the listing of friends includes names (or user names) of the friends of the user along with their profile pictures, and also includes a value of an activity metric for each of the friends. In the illustrated embodiment, each friend listed also includes a step count for that friend. In one embodiment, the friends are listed according to the activity metric, e.g. in descending order from highest to lowest total step count. In this manner, the friends module 304 provides a ranked ordering of the friends of the user, and may also show where the user ranks amongst his/her friends with respect to the particular activity metric. As discussed in further detail below, the user may initiate messaging to a friend, e.g. by clicking on or otherwise selecting the friend's entry in the friends module 304.
A calories module 306 is configured to display a number of calories burned by the user over a given period of time, e.g. during the current day. In one embodiment, a graphical representation of the number of calories burned may be provided, such as a meter or graph.
A distance module 308 is configured to display a distance traveled by the user over a given time period, e.g. during the current day. The distance traveled can also be graphically represented by a meter or graph.
An active minutes module 310 is configured to display a number of minutes for which the user has been engaged in increased levels of activity, during a given time period, e.g. during the current day. The number of active minutes can be graphically represented by a meter or graph.
A sleep module 314 is configured to display an amount of time that the user has spent sleeping, e.g. during a recent time period such as the previous 24-hour period, or the most recent period of sleep. In one embodiment, the amount of sleep can be graphically represented by an identified portion of a clock.
A food plan module 316 is configured to display information related to the user's diet or food plan. In one embodiment, the food plan module 316 is configured to display a number of calories remaining for consumption by the user during that day before exceeding a target number of calories. In one embodiment, the number of calories remaining can be represented graphically by a meter.
A weight module 318 is configured to information related to the weight of the user, such as the current weight of the user or an amount of weight remaining to lose in order to reach a target weight. In one embodiment, the weight information can be graphically represented by a meter or graph.
Thus, in the illustrated embodiment, the listing of each member of the social graph of the user additionally includes a value for an activity metric that is associated with that particular member. In the illustrated embodiment, a seven-day total step count is provided. Furthermore each of the listed members of the social graph is ranked according to their seven-day total step count, and the members of the social graph are listed in order according to their determined ranking. In this manner, the listing of members from the social graph of the user also functions as a leaderboard, displaying a ranked ordering of users based on values for an activity metric for each of the users.
Though in the illustrated embodiment, a seven-day step total is utilized, it will be appreciated that in other embodiments, any activity metric can be displayed and/or utilized for purposes of determining a ranking of members of the social graph of the user, wherein the ranking is applied to determine the order of a listing of members of the social graph of the user. In some embodiments, the ranking may be determined by a combination of activity metrics, or with reference to individualized goals.
With continued reference to
In the illustrated embodiment, an icon 404 may be selected to initiate generation of a normal message to the user Johnny. An icon 406 may be selected to initiate generation of a taunting message to the user Johnny. And an icon 408 can be selected to initiate generation of a cheering message to the user Johnny Selection of any of the foregoing icons may trigger display of a text entry field for the user to enter text to define the message. In one embodiment, sending of a normal message requires entry of text, whereas sending of a taunting message or a cheering message does not require entry of text.
In one embodiment, the interface may have been reached by navigating from a listing of friends of the current user on the social network, e.g. by selecting a particular friend from the listing in order to view additional details about the selected friend. In the illustrated embodiment, details about a friend of the current user named “Emily” are displayed, including the number of steps taken by Emily per day as well as the date Emily joined the social network. A button 500 is provided for navigating back to the listing of friends. A button 502 is provided for initiating a procedure for generating a message to Emily, which as shown, has resulted in the display of a message type selection interface 503 for determining a type of message to generate to the user Emily.
A button 504 is provided for generating a cheering message. When selected the button 504 is selected, the cheering message can be sent without any further input from the current user, or a text entry interface can be presented to allow the current user to define text to be included in the cheering message.
A button 506 is provided for generating a taunting message. When the button 506 is selected, the taunting message can be sent without any further input from the current user, or a text entry interface can be presented to allow the current user to define text to be included in the taunting message.
A button 508 is provided for generating a generic message. In response to triggering the button 508, a text entry interface is provided for allowing the current user to enter text to define the generic message.
A button 510 is provided for canceling the message type selection operation, such that no message will be generated or sent, and the message type selection interface 503 is removed from display.
As shown, various messages/notifications are displayed in a scrollable list. A message 602 is from a user “Nicki” (ref 608). The message 602 includes a profile picture 604 of the user Nicki. A taunting icon 606 indicates that the message 602 is a taunting message. The message 602 is further defined by text content 610, which was previously entered by the user Nicki. At ref. 612, a time is associated with the message 602, indicating when the message was sent/received. In the illustrated embodiment, the message 602 was sent/received 29 seconds ago.
A message 614 is defined from a user “Dave” (ref. 622). A profile picture 616 of the user Dave is shown, and a generic message icon 618 indicates that the message 614 is a regular or generic message (as opposed to a cheering or taunting message). The message 614 is defined by text content 622 provided by the user Dave. And a time indication 624 shows that the message 614 was sent/received approximately one minute ago.
A connection request 626 indicates that the user Dave wishes to be friends with the user Ryan on the social network (ref. 630). The request 626 includes a social icon 628, and a time indication 632 showing the request was sent/received approximately two hours ago. Upon selection or opening of the request 626, options can be provided to the user Ryan to accept or ignore the request. Acceptance of the request will cause the users Dave and Ryan to be connected on the social network, such as each user becomes a member of the other's social graph.
A message 634 is defined from a user “Cameron” (ref. 640). A profile picture 636 of the user Cameron is displayed. A cheering icon 638 indicates that the message 634 is a cheering message. The message 634 is defined by text content 642 which was entered by the user Cameron. Furthermore, a time indication 644 is shown, indicating that the message was sent/received on a prior Sunday.
In addition to messages which are defined and sent by specific users, system-generated notifications can be displayed in the listing of messages. For example, a passing notification 646 can be shown, indicating that the user Ryan has been passed by another user with respect to an activity metric. In other words, another user has attained a value for the activity metric that is superior to that of the user Ryan (value may be greater or less than that of the user Ryan depending upon the particular activity metric being compared). In the illustrated embodiment, the passing notification 646 includes an icon 648 indicating the type of activity metric is a step count. The text portion 650 of the notification 646 indicates that the user Cameron and two other users have passed the user Ryan in terms of their step counts (i.e. have achieved a higher step count than the user Ryan). A time indication 652 indicates that this occurred on a prior Saturday.
In one embodiment, passing or being passed with respect to a given activity metric may trigger an opportunity for the user to send a message to another user who has been passed, or who passed, the instant user. For example, with continued reference to
Another system-generated notification 654 indicates that the user Ryan has lost five pounds, and congratulates the user on the progress towards a weight goal (ref. 650). A profile icon 658 is configured to indicate the loss of five pounds, and an icon 658 is configured to display a trophy.
In the illustrated embodiment, the messages and notifications are listed in reverse chronological order from top to bottom, so that the most recent messages or notifications are featured near the top of the listing. It should be appreciated that in other embodiments, the messages/notifications can be listed in any order so as to prioritize any given feature which may be associated with the messages/notifications. For example, in one embodiment, the messages may be organized according to the sending user's name, so that messages from a given user are grouped together. In another embodiment, the messages can be organized to feature those messages which are unread. In another embodiment, the messages can be organized based on predefined groups. For example, if the user is a member of a competitive group for a given fitness activity, then messages from other members of the competitive group may be collated for display. It should be appreciated that these and other methods of organizing and prioritizing a listing of messages can be combined in various configurations.
The user device 706 includes an application 710 which in various embodiments can be a dedicated application or a browser application. The application 710 is configured to provide access to the user's activity data, the social network, and provide for messaging functionality. The application 710 may retrieve (e.g. from the social data 728, via the social management logic 718) or store locally a friends list 712, which identifies friends of the user on the social network. Additionally, a messaging user interface 714 is provided for allowing the user to view messages as well as define and send messages to other users.
As alluded to above, the server 718 provides access to a social network that is defined by various social data stored to a social data storage 728. The social data includes information defining connections or other relationships between social network users, and thereby defines the social graphs of social network users. Social management logic 722 handles requests relating to the social data. For example, the application 710 may retrieve and display a news feed of current activity/posts from members of the social graph of the user. The application 710 may retrieve the news feed information by requesting it from the social management logic 722 of the remote server 718. In response to a given request, the social management logic 722 may query the social data storage 728 to both identify members of the user's social graph and retrieve posts/notifications/etc. which are related to or posted by the members of the user's social graph. In one embodiment, the social management logic 722 may also query the activity data storage 726 to retrieve activity data/metrics of members of the user's social graph. The retrieved data is returned to the application 710 for display in the social news feed at the user device 706.
It will be appreciated that the messaging user interface 714 of the application 710 may be triggered or activated from various contexts within the application 710. In one embodiment, the application 710 may be configured to allow the user to browse and view information about users in the friends list 712 (e.g. user name, date of joining the social network, activity metrics/data, etc.). When viewing information about a given friend, options may be provided to allow the user to send a message to the friend. Selection of such options may activate the messaging user interface 714 to permit the user to define and send a message to the friend. In another embodiment, the application 710 may enable viewing of a leaderboard for a given activity metric, wherein from the leaderboard, the user may access the messaging user interface 714 to send messages to the users/friends listed on the leaderboard (e.g. by selecting a given user on the leaderboard). In another embodiment, the messaging user interface 714 may be accessed from a view of a group to which the user belongs, enabling the user to send a message to another member of the group. It will be appreciated that in various embodiments, the messaging user interface 714 can be triggered or activated to permit the user to send a message to another user from any number of contexts wherein other users are identified via the application 710.
The remote server includes messaging logic 724 which is configured to handle messaging related requests and activities. For example, when a request is received to retrieve messages from the user's inbox, the messaging logic 724 retrieves the relevant messages from the message data storage 730, and returns them to the application 710 for display via the messaging UI 714. Furthermore, the messaging logic 730 receives data from the application 710 to define a new message to be sent to another user. The messaging logic 730 stores the new message based on the received data to the message data storage 730. The messaging logic 730 may also be configured to notify users when a new message has been received (e.g. send an alert/notification to the user's device).
With continued reference to
From the user device 904, the user 900 accesses a friends list 916 which includes names of users who are members of the user's 900 social graph, including the user 906 (“John”), as well as an activity metric (e.g. a step count) associated with each user. In the illustrated embodiment, selection of the entry for the user “John” provides access to various options (ref 918) for selecting a type of message to generate to the user “John.” The options may include an option to generate a regular message, a cheering message, or a taunting message. Selection of one of the options may then provide access to a text entry field 920 to allow the user 900 to enter text to define the message. In some embodiments, separate fields are provided to enter text for a subject and a body of the message. The indicated selection of the type of message and the text input provided by the user 900 define message data 922. It should be appreciated that the message data 922 may include additional information such as the identity of the sending user (user 900), the identity of the receiving user (user 906), a time stamp, etc. The message is sent to the user 906 by storing it in association with the user's 906 inbox/account. The user 906 may view the message by accessing his/her inbox via the user device 910.
Additionally, a leaderboard option (ref. 1012) is provided whereby the sending user may opt to generate a leaderboard for an activity metric that will be associated with the message (and any thread of messages generated based on the new message). Selection of the leaderboard option provides access to a leaderboard definition interface 1014 that is configured to allow the sending user to define specifics for the leaderboard. For example, in the illustrated embodiment, the sending user may select what activity metric the leaderboard will track (ref 1016), such as steps, floors climbed, distance traveled, active minutes, etc. In the illustrated embodiment, the sending user has selected the leaderboard to track a number of steps. It will be appreciated that more than one activity metric can be designated for tracking on the leaderboard. The sending user may also determine a duration for which the leaderboard will be active, such as until a specific date, for a predefined duration, or indefinitely. In the illustrated embodiment, the sending user has defined the leaderboard to be active for a duration of five days.
The message creation interface 1004 further includes a button 1020 to send the new message, and a button 1022 to cancel the new message. After the message is sent, the message will appear in the inbox view 1024 of the user Bob who is a recipient of the message. By selecting the message preview 1026, an entire view of the message (ref 1028) is accessed. The message 1028 includes an option (ref. 1030) to join the leaderboard. In the illustrated embodiment, buttons for indicating yes or no are provided (ref. 1030) whereby the user Bob may indicate whether he wishes to join the leaderboard.
It will be appreciated that those users who respond positively to the request to join the leaderboard will be members of a competitive group that has been formed based on the message sent by the user Pete. The leaderboard can be displayed in conjunction with viewing of a message that is a part of the message thread (that is defined by the first message sent by the user Pete and any subsequent replies, or replies to replies). Those users that respond positively to the request to join the leaderboard will have their activity metric for which the leaderboard is defined (e.g. step count) tracked on the leaderboard and made available to other members of the competitive group, and they will likewise be able to see other members' activity metrics on the leaderboard.
In response to detecting that the sending user has entered the names of users in the recipient field 1006 whom the sending user messages frequently (or whom the sending user has messaged many times), then an option to form a group including the recipients is displayed (ref. 1062). Upon activation of the option, invitations are sent to the other users to join the group (ref 1064). Based on received responses to the invitations (ref. 1066), the group is generated (ref. 1068).
It should be appreciated that a user's messaging history may be analyzed in various ways to determine when to provide the option to form a group. For example, in one embodiment, when a user has messaged the same plurality of users a given number of times that exceeds a predefined threshold, then the option may be provided upon the next instance where the user creates a message designating the plurality of users as recipients. In one embodiment, the option to form a group is presented when a user has messaged the same users with a frequency or rate that exceeds a predefined threshold frequency or rate.
Additionally, the group that is formed may be a competitive group for which membership provides access to values of an activity metric for each of the members of the group. A leaderboard may be accessed by the members of the competitive group, and may display a ranked ordering of the members of the group based on their respective activity metric values.
The messaging server 1112 defines an API 1114 for accessing data such as message data defined in a message data storage 1122, and user activity data defined in the user activity data 1124. Message creation logic 1116 is provided for managing the generation of new messages. Message retrieval logic 1118 is provided for responding to requests to retrieve messages for a given user. Leaderboard logic 1120 is configured to generate a leaderboard that is to be associated with a given message thread. For example, the leaderboard logic 1120 can be configured to generate a leaderboard based on responses to requests to join a given leaderboard which have been sent to one or more users, as previously described.
The server 1112 may further define a messaging analyzer 1126 which is configured to analyze a user's messaging history to determine the quantity of messaging occurring between a given user and other users. The quantity of messaging can be defined by a number of messages sent, a frequency of messaging, or other metrics which quantify the messaging between the given user and other users.
Group logic 1128 is provided for handling group generation and management, including providing an option to generate a group when a given user's messaging to specific users exceeds a predefined threshold. The group logic 1128 may send invitations to join a group, and generate the group based on the received responses to the invitations.
In some embodiments, methods and systems are provided for identifying interesting, unusual, or otherwise significant activity by a user of an activity tracking device, and delivering messages that are related to the identified activity. Broadly speaking, a user's activity metrics/data can be analyzed to identify characteristic activity levels or patterns, and deviations from the characteristic activity levels or patterns can be identified. In response to the identification of such deviations, messages can be generated and sent to the user.
The time periods P.sub.1, P.sub.2, and P.sub.3 are analogous, similar, or recurrent time periods that have a same or similar time frame. That is, the time periods have a common temporal characteristic. By way of example, without limitation, each of the time periods may be the same or similar in any of the following respects: time of day (e.g. mornings, afternoons, evenings, etc.), timespan as defined by start time of day and end time of day (e.g. 6 am to 9 am), duration (e.g. hours, days, weeks, months, years), day(s) of the week (e.g. Mondays, weekdays, weekends, etc.), day(s) of the month (e.g. 1.sup.st day of the month), week(s) of the month, month(s) of the year, etc.
It will be appreciated that in addition to time periods P.sub.1, P.sub.2, and P.sub.3, there may be additional time periods having the same or similar time frame. The activity metric values for each of these time periods can be processed to determine a characteristic activity level for the recurrent time period, which is indicated by the curve 1214 shown at graph 1212. The characteristic activity level defines characteristic, expected, predicted, normal or otherwise typical activity metric values or levels for the time period. In the illustrated embodiment, the characteristic activity level for the generic period of time P.sub.0 is represented by the curve 1214, and more specifically, has been determined to have a value 26. It should be appreciated that the units supplied with reference to the activity metric are arbitrary and provided for purposes of illustration.
In one embodiment, the characteristic activity level is defined by an average or mean of the activity metric values of the periods of time. In some embodiments, this can be conceptualized as the sum of the areas under the curves 1202, 1206, 1210, etc. during the respective periods of time P1, P2, P3, etc. and divided by the number of the time periods considered and the duration of a given generic time period. In other embodiments, the characteristic activity level is defined by a median or mode of the activity metric values of the periods of time. In other embodiments, any known method for determining characteristic activity levels may be applied that defines characteristic, expected or typical activity metric value(s) for the time period.
In some implementations, the characteristic activity metric level is defined by a singular overall value for the time period (as in the illustrated embodiment). However, in other implementations, characteristic activity metric levels can be defined with greater granularity ranging from the entirety of the time period (resulting in the aforementioned singular overall value) to any temporal subdivision of the period of time, to being continuously defined. In some implementations, a minimum temporal subdivision for the period of time may be defined based on a minimum time duration for which an activity metric value can be determined. In some embodiments, the characteristic activity levels can be determined by averaging or characterizing the activity metric curves together to define an average or characteristic curve.
With continued reference to
It will be appreciated that the first day and the second day can be any two days for which activity data of the user are recorded (e.g. two days in succession, two of the same day of the week (e.g. two Saturdays), etc.). The activity metrics of the two days can be compared to identify interesting differences or changes from the first day to the second day. For example, in the illustrated embodiment, on the second day, as shown at reference 1230, the user's activity level in the morning is greatly increased as compared to that of the first day. Furthermore, the total activity amount for the second day is greater than that of the first day (conceptualized as the area 1228 under the curve 1226 for the second day versus the area 1224 under the curve 1222 for the first day.
Deviations from the characteristic activity levels on a given day can be detected. For example, as indicated at reference 1236, the user may exhibit a level of activity on a Monday that is substantially greater than the characteristic activity level for that time. Upon detection of such activity, a message identifying and/or describing the deviation from normal activity levels can be sent to the user. As another example shown in the illustrated graph, the user's activity level on a Thursday may typically include elevated activity levels on Thursday nights (e.g. user plays basketball on Thursday nights). However, on a given Thursday, the elevated activity level may be even greater than normal, as indicated at reference 1238. In response to detection of this occurrence, a message can be generated and sent to the user, identifying and describing the activity.
The threshold for detection of unusual activity can be context dependent. For example, the threshold for detection of unusual activity for the time period at reference 1236, when activity levels are normally not especially elevated, can be greater than the threshold for detection for the time period at reference 1238, when it is expected that activity levels will already be elevated, and hence even higher elevated activity levels may be considered significant at a lower threshold relative to the already elevated activity levels.
Messages which are generated in response to detection of interesting or unusual activity can be customized to include relevant activity metrics/data that is descriptive of the activity (e.g. “You improved on yesterday's stepcount by 1000 steps,” “You're only 500 steps from beating last week's total”, etc.). Generated messages which are descriptive of the unusual activity are sent to a user account associated with the user. Throughout the present disclosure, messages are described as being sent to users for ease of description, though it will be understood that this includes sending the messages to user accounts that are associated with the users. Messages can be sent via any of a variety of messaging technologies including, but not limited to, private messages, e-mail, push notifications, etc. Additionally, messages may be sent to additional users who are members of the primary user's social graph.
It will be appreciated that detection of interesting or unusual activity may be determined according to any of various methods and techniques. Broadly speaking, activity data for first and second periods of time, which have a similar time frame, can be analyzed to determine characteristic activity levels for the periods of time. These may be compared to determine deviations between the two periods of time, and so identify interesting or unusual activity by a user. For example, in one embodiment, a historic mean level of activity is determined, and deviations from the historic mean can be detected. In other embodiments, other statistical measures of characteristic activity levels can be determined (e.g. median, mode, etc.) and deviations therefrom can be detected to identify interesting or unusual activity. It will be appreciated that in some embodiments, such deviations are detected for current and/or recent time periods which are subsequent to the time period from which the historic mean is calculated, so as to provide feedback to the user regarding their current/recent activity. A deviation can be defined in various ways, such as a difference exceeding a predefined amount, a predefined threshold, a predefined fractional amount (e.g. difference exceeding a specified percentage difference), a predefined number of standard deviations, etc. In still other embodiments, any known method for identifying a statistically significant difference can be applied to activity data of a user to identify unusual activity.
In accordance with additional embodiments, group events can be defined in which two or more users participate based on their activity data. Examples of group events include challenges or races, in which users compete against one another to achieve a highest or otherwise best activity amount or other activity related outcome, missions in which users each have individual goals that are pursued together in the context of the group, and group goals where users collectively pursue a goal.
When a passing event is detected in which the activity value/level of one user surpasses that of another, messages can also be generated and sent. With continued reference to
At reference 1326, the activity levels for users C and D are close to each other (differ by less than a predefined amount) for a length of time, and this may be identified as an interesting event. This will be interesting for user C and D, but may be of less interest to the remaining participants, as users C and D are not in the top rankings. Therefore, messages are generated and sent to users C and D that identify and describe this occurrence, but messages are not sent to the other participants. By way of example, the message to user C may be, “You and User D are running neck and neck!” whereas the message to user D may be, “You and User C are running neck and neck!”
At reference 1328, the activity level of user C surpasses that of user D by a large amount (greater than a threshold amount). Therefore, upon detection of this passing event, messages can be generated and sent to users C and D. For example, the message to user C may be, “You rocketed past User D into third place!” whereas the message to user D may be, “User D rocketed past you into third place!”
It will be appreciated that there may be any number of unusual or interesting events or changes in relationship between activity levels of users, and that such may be detected, and in response, messages can be generated and sent to some or all participating users. Messages can be customized to include activity metric data that is related to or descriptive of the significant event. Several examples are described herein for purposes of illustration, without limitation.
For example, when someone takes first place with a significant lead (e.g. a user “Joe” takes lead from a user “Sally”), messages to third parties may be “Joe rocketed past Sally into first place,” “Joe zoomed into first,” etc. When the recipient is the actor (e.g. “Joe”) the message may be “You rocketed past Sally into first place,” “You zoomed into 1.sup.st,” etc. When the recipient is the subject (e.g. “Sally”), the message may be “Joe rocketed past you into first place,” etc. In the table below, several examples of message templates are provided for the situation when someone takes first place with a significant lead (e.g. activity metric/level exceeds the second place person by at least a threshold amount). The message templates are tailored to the recipient depending upon whether the recipient is a third party (i.e. not involved in gaining or losing first place), an actor (i.e. person who takes first place), or the subject (i.e. person who previously held first place but now lost it). The message templates can include fillable fields for insertion of the appropriate names and relevant activity metric data (indicated in braces in the table below). By way of example, the relevant activity metric data may be a total cumulative amount of the activity metric for the first place person (according to which the ranking is determined), an amount of the activity metric acquired by the person to take first place, an amount by which the first place person is in the lead, etc.
For example, when someone (e.g. user “Joe”) takes first place with a modest lead, messages to third parties may be “Joe squeaked into 1.sup.st,” etc. When the recipient is the actor, the message may be “You squeaked into 1.sup.st,” etc. When the recipient is the subject, the message may be “Joe claimed your lead,” etc. In the table below, several examples of message templates are provided for the situation when someone takes first place with a modest lead (e.g. activity metric/level exceeds the second place person by less than a threshold amount). The message templates are tailored to the recipient depending upon whether the recipient is a third party (i.e. not involved in gaining or losing first place), an actor (i.e. person who takes first place), or the subject (i.e. person who previously held first place but now lost it). The message templates can include fillable fields for insertion of the appropriate names and relevant activity metric data (indicated in braces in the table below). By way of example, the relevant activity metric data may be a total cumulative amount of the activity metric for the first place person (according to which the ranking is determined), an amount of the activity metric acquired by the person to take first place, an amount by which the first place person is in the lead, etc.
For example, when someone takes Nth place with a significant lead (e.g. user “Brad” overtakes user “Abby” by 3000 steps), messages to third parties could be “Brad's in front of Abby by 3000 steps,” etc. When the recipient is the actor (e.g. Brad), the message could be, “You're in front of Abby by 3000 steps,” etc. When the recipient is the subject, the message could be “Brad's in front of you by 3000 steps,” etc. In the table below, several examples of message templates are provided for the situation when someone takes Nth place with a significant lead (e.g. activity metric/level exceeds the next (N+1) place person by at least a threshold amount). The message templates are tailored to the recipient depending upon whether the recipient is a third party (i.e. not involved in gaining or losing Nth place), an actor (i.e. person who takes Nth place), or the subject (i.e. person who previously held Nth place but now lost it). The message templates can include fillable fields for insertion of the appropriate names and relevant activity metric data (indicated in braces in the table below). By way of example, the relevant activity metric data may be a total cumulative amount of the activity metric for the Nth place person (according to which the ranking is determined), an amount of the activity metric acquired by the person to take Nth place, an amount by which the Nth place person is ahead of the next (N+1) place person, etc.
In the table below, several examples of message templates are provided for the situation when someone takes Nth place with a modest lead (e.g. activity metric/level exceeds the next (N+1) place person by less than a threshold amount). The message templates are tailored to the recipient depending upon whether the recipient is a third party (i.e. not involved in gaining or losing Nth place), an actor (i.e. person who takes Nth place), or the subject (i.e. person who previously held Nth place but now lost it). The message templates can include fillable fields for insertion of the appropriate names and relevant activity metric data (indicated in braces in the table below). By way of example, the relevant activity metric data may be a total cumulative amount of the activity metric for the Nth place person (according to which the ranking is determined), an amount of the activity metric acquired by the person to take Nth place, an amount by which the Nth place person is ahead of the next (N+1) place person, etc.
In the table below, several examples of message templates are provided for the situation when two users have very close activity metrics (e.g. activity metric/level of Nth place person and next (N+1) place person is less than a threshold amount). The message templates are tailored to the recipient depending upon whether the recipient is a third party (i.e. not involved in gaining or losing Nth place) or an actor (i.e. person who holds Nth place or the next (N+1) place. The message templates can include fillable fields for insertion of the appropriate names and activity metric data (indicated in braces in the table below).
For example, when the activity level of an individual user is approaching that of another user, then a private notification may be provided to the individual user (e.g. “You're only 500 steps behind Abby”), but not to other users. Examples of message templates for such a scenario are listed in the table below.
In a related example, a user that is about to be passed may receive a private notification (e.g. “Brad is only 500 steps behind you”). Examples of message templates for such a scenario are listed in the table below.
In another example, a private notification may be sent in response to detection of a user being close to taking first place (or any other place) (e.g. “You're 500 steps from taking the lead today”). Examples of message templates for such a scenario are listed in the table below.
Further, personal achievements may be detected in the context of the group event, and related messages can be generated and sent. Examples of personal achievements include: someone making a significant change in activity level (but no change in position), someone reaching 100% of their goal today/yesterday, someone improving day over day, someone having a multi-day goal streak, etc.
In the table below, examples of message templates are provided for the scenario where someone made a significant change in their activity metric (e.g. acquiring an amount greater than a threshold amount), but no change in position.
In the table below, examples of message templates are provided for the scenario where someone reached 100% of their goal today.
In the table below, examples of message templates are provided for the scenario where someone reached 100% of their goal yesterday.
In the table below, examples of message templates are provided for the scenario where somebody improved day over day.
In the table below, examples of message templates are provided for the scenario where somebody has a multi-day goal streak.
Though various examples of message templates have been provided herein, it should be appreciated that such are provided by way of example, and not by way of limitation.
It will be appreciated that for a given detected event, notifications may be sent to (a) an individual user, (b) to selected ones (some) of the users, or (c) to all of the participating users, depending upon various factors such as the characteristics of or type of event that is detected, the identities of the users that are involved in or affected by the event, the current activity state of a given user, a calendar of a user, a location of a user, time of day, etc.
For example, in some implementations, all participating users receive notifications about changes in the first place ranking; whereas notifications about other rank changes (not affecting first place) are sent to only those users who are involved in the rank change (e.g. the users whose rankings have changed). In this manner, notifications are limited so that users do not receive too many notifications. It should be appreciated that though rank changes have generally been described with reference to two users (one user passing another), there may be situations where rank changes affect more than two users (e.g. a user passes two or more users).
In some implementations, when a passing event is detected which affects a ranking that is equal to or above a threshold ranking (e.g. change in first three places), then notification messages are sent to all the participating users in the group event. Whereas if a passing event is detected which affects a ranking below the threshold ranking (e.g. fourth place and below), then notification messages are not sent to all the participating users, but are sent to the users whose rankings have been affected.
Messages may also be posted by users to the messaging feed. Indeed, the messaging stemming from the automated detection of interesting activity occurring during the group event may encourage the participant users to interact more and post additional messages to the group messaging feed.
As has been noted, messages may be sent to one, some or all of the participant users. A message may appear in the messaging feed 1334, though a given user may or may not have received a notification containing the message. For example, in the implementation described above wherein notifications regarding changes in rank other than first place are sent only to those users involved, appropriate messages for the change in rank may appear in the message feed provided to other users, notwithstanding that they did not receive a notification. In this manner, the other users have access to the complete messaging activity history when accessing the message feed, but receive notifications selectively so as not to be overwhelmed with excessive notifications.
Additionally, users may cheer, taunt, and otherwise respond to specific messages.
The generated message can be sent via a notification server 1360, to a user device 1344 that is associated to the user 1340. Upon receipt, the message is surfaced as a notification on the user device 1344.
In another implementation, the message may be sent to and surfaced on the activity tracking device 1342.
For a group event, there may be additional users, with additionally associated activity tracking devices and user devices. Group management logic 1350 is configured to manage the formation and maintenance of a group event. Group management logic 1350 may invoke analysis logic 1352 to identify interesting activity occurring during the group event, and messaging logic 1356 to generate messages which are descriptive of the interesting activity.
In other implementations, notifications and/or messages may be processed and sent to users based other measurable or quantifiable data. For instance, instead of just using activity metrics to determine differences, changes, or relationships among one or more users, other types of data can include a user's weight (e.g., weight loss, weight gain, weight goals, weight loss competitions, weight loss challenges, etc.), a user's food intake (e.g., number of calories consumed, calorie intake per day or period of time, types of foods eaten, meals logged, meals cooked, meals shared, recipes shared, food data shared, etc.), sleep data (e.g., hours slept, number of times moved during a period of time, number of wakeups, activity during sleep periods, restful sleep periods, challenges regarding sleep metrics, etc.). It should be appreciated that these are just some examples of data that can be shared, used or consumed to enable smart notifications or messages to users or to groups of users.
Such data may be detected by, obtained or derived from sources other than the aforementioned activity tracking device, such as by user entry and/or from other types of devices. For example, in implementations wherein users' weights are tracked, weight information may be obtained through user entry (e.g. via an app on a user's mobile device, via a web interface, any other computing device), or from a scale that communicates weight information (e.g. the ARIA.TM. WIFI SMART SCALE sold by Fitbit Inc.). Notifications may also be surfaced on the scale. In some embodiments, notifications are displayed on the scale at the time that a user activates or otherwise uses the scale.
In one embodiment, the device collects one or more types of physiological and/or environmental data from embedded sensors and/or external devices and communicates or relays such metric information to other devices, including devices capable of serving as Internet-accessible data sources, thus permitting the collected data to be viewed, for example, using a web browser or network-based application. For example, while the user is wearing an activity tracking device, the device may calculate and store the user's step count using one or more sensors. The device then transmits data representative of the user's step count to an account on a web service, computer, mobile phone, or health station where the data may be stored, processed, and visualized by the user. Indeed, the device may measure or calculate a plurality of other physiological metrics in addition to, or in place of, the user's step count.
Some physiological metrics include, but are not limited to, energy expenditure (for example, calorie burn), floors climbed and/or descended, heart rate, heart rate variability, heart rate recovery, location and/or heading (for example, through GPS), elevation, ambulatory speed and/or distance traveled, swimming lap count, bicycle distance and/or speed, blood pressure, blood glucose, skin conduction, skin and/or body temperature, electromyography, electroencephalography, weight, body fat, caloric intake, nutritional intake from food, medication intake, sleep periods (i.e., clock time), sleep phases, sleep quality and/or duration, pH levels, hydration levels, and respiration rate. The device may also measure or calculate metrics related to the environment around the user such as barometric pressure, weather conditions (for example, temperature, humidity, pollen count, air quality, rain/snow conditions, wind speed), light exposure (for example, ambient light, UV light exposure, time and/or duration spent in darkness), noise exposure, radiation exposure, and magnetic field.
Still further, other metrics can include, without limitation, calories burned by a user, weight gained by a user, weight lost by a user, stairs ascended, e.g., climbed, etc., by a user, stairs descended by a user, steps taken by a user during walking or running, a number of rotations of a bicycle pedal rotated by a user, sedentary activity data, driving a vehicle, a number of golf swings taken by a user, a number of forehands of a sport played by a user, a number of backhands of a sport played by a user, or a combination thereof. In some embodiments, sedentary activity data is referred to herein as inactive activity data or as passive activity data. In some embodiments, when a user is not sedentary and is not sleeping, the user is active. In some embodiments, a user may stand on a monitoring device that determines a physiological parameter of the user. For example, a user stands on a scale that measures a weight, a body fat percentage, a biomass index, or a combination thereof, of the user.
Furthermore, the device or the system collating the data streams may calculate metrics derived from this data. For example, the device or system may calculate the user's stress and/or relaxation levels through a combination of heart rate variability, skin conduction, noise pollution, and sleep quality. In another example, the device or system may determine the efficacy of a medical intervention (for example, medication) through the combination of medication intake, sleep and/or activity data. In yet another example, the device or system may determine the efficacy of an allergy medication through the combination of pollen data, medication intake, sleep and/or activity data. These examples are provided for illustration only and are not intended to be limiting or exhaustive.
This information can be associated to the users account, which can be managed by an activity management application on the server. The activity management application can provide access to the users account and data saved thereon. The activity manager application running on the server can be in the form of a web application. The web application can provide access to a number of websites screens and pages that illustrate information regarding the metrics in various formats. This information can be viewed by the user, and synchronized with a computing device of the user, such as a smart phone.
In one embodiment, the data captured by the activity tracking device 100 is received by the computing device, and the data is synchronized with the activity measured application on the server. In this example, data viewable on the computing device (e.g. smart phone) using an activity tracking application (app) can be synchronized with the data present on the server, and associated with the user's account. In this way, information entered into the activity tracking application on the computing device can be synchronized with application illustrated in the various screens of the activity management application provided by the server on the web site.
The user can therefore access the data associated with the user account using any device having access to the Internet. Data received by the network 176 can then be synchronized with the user's various devices, and analytics on the server can provide data analysis to provide recommendations for additional activity, and or improvements in physical health. The process therefore continues where data is captured, analyzed, synchronized, and recommendations are produced. In some embodiments, the captured data can be itemized and partitioned based on the type of activity being performed, and such information can be provided to the user on the website via graphical user interfaces, or by way of the application executed on the users smart phone (by way of graphical user interfaces).
In an embodiment, the sensor or sensors of a device 100 can determine or capture data to determine an amount of movement of the monitoring device over a period of time. The sensors can include, for example, an accelerometer, a magnetometer, a gyroscope, or combinations thereof. Broadly speaking, these sensors are inertial sensors, which capture some movement data, in response to the device 100 being moved. The amount of movement (e.g., motion sensed) may occur when the user is performing an activity of climbing stairs over the time period, walking, running, etc. The monitoring device may be worn on a wrist, carried by a user, worn on clothing (using a clip, or placed in a pocket), attached to a leg or foot, attached to the user's chest, waist, or integrated in an article of clothing such as a shirt, hat, pants, blouse, glasses, and the like. These examples are not limiting to all the possible ways the sensors of the device can be associated with a user or thing being monitored.
In other embodiments, a biological sensor can determine any number of physiological characteristics of a user. As another example, the biological sensor may determine heart rate, a hydration level, body fat, bone density, fingerprint data, sweat rate, and/or a bioimpedance of the user. Examples of the biological sensors include, without limitation, a biometric sensor, a physiological parameter sensor, a pedometer, or a combination thereof.
In some embodiments, data associated with the user's activity can be monitored by the applications on the server and the users device, and activity associated with the user's friends, acquaintances, or social network peers can also be shared, based on the user's authorization. This provides for the ability for friends to compete regarding their fitness, achieve goals, receive badges for achieving goals, get reminders for achieving such goals, rewards or discounts for achieving certain goals, etc.
As noted, an activity tracking device 100 can communicate with a computing device (e.g., a smartphone, a tablet computer, a desktop computer, or computer device having wireless communication access and/or access to the Internet). The computing device, in turn, can communicate over a network, such as the Internet or an Intranet to provide data synchronization. The network may be a wide area network, a local area network, or a combination thereof. The network may be coupled to one or more servers, one or more virtual machines, or a combination thereof. A server, a virtual machine, a controller of a monitoring device, or a controller of a computing device is sometimes referred to herein as a computing resource. Examples of a controller include a processor and a memory device.
In one embodiment, the processor may be a general purpose processor. In another embodiment, the processor can be a customized processor configured to run specific algorithms or operations. Such processors can include digital signal processors (DSPs), which are designed to execute or interact with specific chips, signals, wires, and perform certain algorithms, processes, state diagrams, feedback, detection, execution, or the like. In some embodiments, a processor can include or be interfaced with an application specific integrated circuit (ASIC), a programmable logic device (PLD), a central processing unit (CPU), or a combination thereof, etc.
In some embodiments, one or more chips, modules, devices, or logic can be defined to execute instructions or logic, which collectively can be viewed or characterized to be a processor. Therefore, it should be understood that a processor does not necessarily have to be one single chip or module, but can be defined from a collection of electronic or connecting components, logic, firmware, code, and combinations thereof.
Examples of a memory device include a random access memory (RAM) and a read-only memory (ROM). A memory device may be a Flash memory, a redundant array of disks (RAID), a hard disk, or a combination thereof.
Embodiments described in the present disclosure may be practiced with various computer system configurations including hand-held devices, microprocessor systems, microprocessor-based or programmable consumer electronics, minicomputers, mainframe computers and the like. Several embodiments described in the present disclosure can also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a wire-based or wireless network.
With the above embodiments in mind, it should be understood that a number of embodiments described in the present disclosure can employ various computer-implemented operations involving data stored in computer systems. These operations are those requiring physical manipulation of physical quantities. Any of the operations described herein that form part of various embodiments described in the present disclosure are useful machine operations. Several embodiments described in the present disclosure also relate to a device or an apparatus for performing these operations. The apparatus can be specially constructed for a purpose, or the apparatus can be a computer selectively activated or configured by a computer program stored in the computer. In particular, various machines can be used with computer programs written in accordance with the teachings herein, or it may be more convenient to construct a more specialized apparatus to perform the required operations.
Various embodiments described in the present disclosure can also be embodied as computer-readable code on a non-transitory computer-readable medium. The computer-readable medium is any data storage device that can store data, which can thereafter be read by a computer system. Examples of the computer-readable medium include hard drives, network attached storage (NAS), ROM, RAM, compact disc-ROMs (CD-ROMs), CD-recordables (CD-Rs), CD-rewritables (RWs), magnetic tapes and other optical and non-optical data storage devices. The computer-readable medium can include computer-readable tangible medium distributed over a network-coupled computer system so that the computer-readable code is stored and executed in a distributed fashion.
Although the method operations were described in a specific order, it should be understood that other housekeeping operations may be performed in between operations, or operations may be performed in an order other than that shown, or operations may be adjusted so that they occur at slightly different times, or may be distributed in a system which allows the occurrence of the processing operations at various intervals associated with the processing.
Although the foregoing embodiments have been described in some detail for purposes of clarity of understanding, it will be apparent that certain changes and modifications can be practiced within the scope of the appended claims. Accordingly, the present embodiments are to be considered as illustrative and not restrictive, and the various embodiments described in the present disclosure are not to be limited to the details given herein, but may be modified within the scope and equivalents of the appended claims.
| Number | Name | Date | Kind |
|---|---|---|---|
| 2284849 | Anderson et al. | Aug 1941 | A |
| 2717736 | Schlesinger | Sep 1955 | A |
| 2827309 | Fred | Mar 1958 | A |
| 2883255 | Anderson | Apr 1959 | A |
| 3163856 | Kirby | Dec 1964 | A |
| 3250270 | Walter | May 1966 | A |
| 3522383 | Chang | Jul 1970 | 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 |
| 4425921 | Fujisaki et al. | Jan 1984 | A |
| 4575804 | Ratcliff | Mar 1986 | A |
| 4578769 | Frederick | Mar 1986 | A |
| 4617525 | Lloyd | Oct 1986 | A |
| 4887249 | Thinesen | Dec 1989 | A |
| 4977509 | Pitchford et al. | Dec 1990 | A |
| 5058427 | Brandt | 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 |
| 5553296 | Forrest et al. | Sep 1996 | A |
| 5583776 | Levi et al. | Dec 1996 | A |
| 5645509 | Brewer et al. | Jul 1997 | A |
| 5671162 | Werbin | Sep 1997 | A |
| 5704350 | Williams, III | Jan 1998 | A |
| 5724265 | Hutchings | Mar 1998 | A |
| 5890128 | Diaz et al. | Mar 1999 | A |
| 5891042 | Sham et al. | Apr 1999 | A |
| 5894454 | Kondo | Apr 1999 | A |
| 5899963 | Hutchings | May 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 |
| 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 |
| 6527711 | Stivoric et al. | Mar 2003 | B1 |
| 6529827 | Beason et al. | Mar 2003 | B1 |
| 6558335 | Thede | May 2003 | B1 |
| 6561951 | Cannon et al. | May 2003 | B2 |
| 6571200 | Mault | May 2003 | B1 |
| 6585622 | Shum et al. | Jul 2003 | B1 |
| 6607493 | Song | Aug 2003 | B2 |
| 6620078 | Pfeffer | Sep 2003 | B2 |
| 6678629 | Tsuji | Jan 2004 | B2 |
| 6699188 | Wessel | Mar 2004 | B2 |
| 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 |
| 6862575 | Anttila et al. | Mar 2005 | B1 |
| 7041032 | Calvano | May 2006 | B1 |
| 7062225 | White | Jun 2006 | B2 |
| 7133690 | Ranta-Aho et al. | Nov 2006 | B2 |
| 7162368 | Levi 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 |
| 7285090 | Stivoric 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 |
| 7502643 | Farringdon et al. | Mar 2009 | B2 |
| 7505865 | Ohkubo et al. | Mar 2009 | B2 |
| 7539532 | Tran | May 2009 | B2 |
| 7558622 | Tran | Jul 2009 | B2 |
| 7559877 | Parks et al. | Jul 2009 | B2 |
| 7653508 | Kahn et al. | Jan 2010 | B1 |
| 7690556 | Kahn et al. | Apr 2010 | B1 |
| 7713173 | Shin et al. | May 2010 | B2 |
| 7762952 | Lee et al. | Jul 2010 | B2 |
| 7771320 | Riley et al. | Aug 2010 | B2 |
| 7774156 | Niva et al. | Aug 2010 | B2 |
| 7789802 | Lee et al. | Sep 2010 | B2 |
| 7805150 | Graham | Sep 2010 | B2 |
| 7881902 | Kahn et al. | Feb 2011 | B1 |
| 7927253 | Vincent et al. | Apr 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 |
| 8132037 | Fehr et al. | Mar 2012 | B2 |
| 8177260 | Trapper et al. | May 2012 | B2 |
| 8180591 | Yuen et al. | May 2012 | B2 |
| 8180592 | Yuen et al. | May 2012 | B2 |
| 8270297 | Akasaka et al. | Sep 2012 | B2 |
| 8311769 | Yuen et al. | Nov 2012 | B2 |
| 8311770 | Yuen et al. | Nov 2012 | B2 |
| 8386008 | Yuen et al. | Feb 2013 | B2 |
| 8437980 | Yuen et al. | May 2013 | B2 |
| 8462591 | Marhaben | Jun 2013 | B1 |
| 8463576 | Yuen et al. | Jun 2013 | B2 |
| 8463577 | Yuen et al. | Jun 2013 | B2 |
| 8533269 | Brown | Sep 2013 | B2 |
| 8533620 | Hoffman et al. | Sep 2013 | B2 |
| 8543185 | Yuen et al. | Sep 2013 | B2 |
| 8543351 | Yuen et al. | Sep 2013 | B2 |
| 8548770 | Yuen et al. | Oct 2013 | B2 |
| 8562489 | Burton et al. | Oct 2013 | B2 |
| 8583402 | Yuen et al. | Nov 2013 | B2 |
| 8597093 | Engelberg et al. | Dec 2013 | B2 |
| 8615377 | Yuen | Dec 2013 | B1 |
| 8634796 | Johnson | Jan 2014 | B2 |
| 8670953 | Yuen et al. | Mar 2014 | B2 |
| 8684900 | Tran | Apr 2014 | B2 |
| 8690578 | Nusbaum et al. | Apr 2014 | B1 |
| 8734296 | Brumback | May 2014 | B1 |
| 8738321 | Yuen et al. | May 2014 | B2 |
| 8738323 | Yuen et al. | May 2014 | B2 |
| 8744803 | Park et al. | Jun 2014 | B2 |
| 8762101 | Yuen et al. | Jun 2014 | B2 |
| 8764651 | Tran | Jul 2014 | B2 |
| 8847988 | Geisner et al. | Sep 2014 | B2 |
| 8935119 | Yuen | Jan 2015 | B2 |
| 8968195 | Tran | Mar 2015 | B2 |
| 9031812 | Roberts et al. | May 2015 | B2 |
| 9288298 | Choudhary et al. | Mar 2016 | B2 |
| 9389057 | Meschter | Jul 2016 | B2 |
| 9409052 | Werner | Aug 2016 | B2 |
| 9420083 | Roberts | Aug 2016 | B2 |
| 9641469 | Choudhary et al. | May 2017 | B2 |
| 9672715 | Roberts et al. | Jun 2017 | B2 |
| 10104026 | Choudhary et al. | Oct 2018 | B2 |
| 20010049470 | Mault | Dec 2001 | A1 |
| 20010055242 | Deshmuhk et al. | Dec 2001 | A1 |
| 20020013717 | Ando et al. | Jan 2002 | A1 |
| 20020019585 | Dickenson | Feb 2002 | A1 |
| 20020077219 | Cohen et al. | Jun 2002 | A1 |
| 20020082144 | Pfeffer | Jun 2002 | A1 |
| 20020087264 | Hills et al. | Jul 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 |
| 20040239497 | Schwartzman et al. | Dec 2004 | A1 |
| 20040249299 | Cobb | Dec 2004 | A1 |
| 20050037844 | Shum et al. | Feb 2005 | A1 |
| 20050038679 | Short | Feb 2005 | A1 |
| 20050054938 | Wehman et al. | Mar 2005 | A1 |
| 20050102172 | Sirmans, Jr. | May 2005 | A1 |
| 20050107723 | Wehman et al. | May 2005 | A1 |
| 20050163056 | Ranta-Aho et al. | Jul 2005 | A1 |
| 20050171410 | Hjelt et al. | Aug 2005 | A1 |
| 20050228244 | Banet | Oct 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 |
| 20060020174 | Matsumura et al. | Jan 2006 | A1 |
| 20060020177 | Seo et al. | Jan 2006 | A1 |
| 20060025282 | Redmann | Feb 2006 | A1 |
| 20060047208 | Yoon | Mar 2006 | A1 |
| 20060047447 | Brady et al. | Mar 2006 | A1 |
| 20060064276 | Ren et al. | Mar 2006 | A1 |
| 20060069619 | Walker et al. | Mar 2006 | A1 |
| 20060089542 | Sands | Apr 2006 | A1 |
| 20060111944 | Sirmans, Jr. | May 2006 | A1 |
| 20060129436 | Short | Jun 2006 | A1 |
| 20060143645 | Vock et al. | Jun 2006 | A1 |
| 20060217231 | Parks et al. | Sep 2006 | A1 |
| 20060247952 | Muraca | 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 |
| 20070071643 | Hall et al. | Mar 2007 | A1 |
| 20070072156 | Kaufman et al. | Mar 2007 | A1 |
| 20070083602 | Heggenhougen et al. | Apr 2007 | A1 |
| 20070123391 | Shin et al. | May 2007 | A1 |
| 20070136093 | Rankin et al. | Jun 2007 | A1 |
| 20070146116 | Kimbrell | 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 |
| 20070197920 | Adams | Aug 2007 | A1 |
| 20070208544 | Kulach et al. | Sep 2007 | A1 |
| 20070276271 | Chan | Nov 2007 | A1 |
| 20080084823 | Akasaka et al. | Apr 2008 | A1 |
| 20080093838 | Trapper et al. | Apr 2008 | A1 |
| 20080096726 | Riley | Apr 2008 | A1 |
| 20080097550 | Dicks et al. | Apr 2008 | A1 |
| 20080114829 | Button et al. | May 2008 | A1 |
| 20080125288 | Case | May 2008 | A1 |
| 20080129457 | Ritter et al. | Jun 2008 | A1 |
| 20080134102 | Movold et al. | Jun 2008 | A1 |
| 20080140163 | Keacher et al. | Jun 2008 | A1 |
| 20080140338 | No et al. | Jun 2008 | A1 |
| 20080146334 | Kil | Jun 2008 | A1 |
| 20080146892 | LeBoeuf et al. | Jun 2008 | A1 |
| 20080155077 | James | Jun 2008 | A1 |
| 20080176655 | James et al. | Jul 2008 | A1 |
| 20080287751 | Stivoric et al. | Nov 2008 | A1 |
| 20090018797 | Kasama et al. | Jan 2009 | A1 |
| 20090043531 | Kahn et al. | Feb 2009 | A1 |
| 20090047645 | Dibenedetto et al. | Feb 2009 | A1 |
| 20090048044 | Oleson et al. | Feb 2009 | A1 |
| 20090054737 | Magar et al. | Feb 2009 | A1 |
| 20090063193 | Barton et al. | Mar 2009 | A1 |
| 20090063293 | Mirrashidi et al. | Mar 2009 | A1 |
| 20090085865 | Fattah | Apr 2009 | A1 |
| 20090098821 | Shinya | Apr 2009 | A1 |
| 20090150178 | Sutton et al. | Jun 2009 | A1 |
| 20090156172 | Chan | Jun 2009 | A1 |
| 20090171788 | Trapper et al. | Jul 2009 | A1 |
| 20090184849 | Nasiri | Jul 2009 | A1 |
| 20090195350 | Tsern et al. | Aug 2009 | A1 |
| 20090262088 | Moii-Carrillo et al. | Oct 2009 | A1 |
| 20090264713 | Van Loenen et al. | Oct 2009 | A1 |
| 20090271147 | Sugai | Oct 2009 | A1 |
| 20090287921 | Zhu et al. | Nov 2009 | A1 |
| 20090307517 | Fehr et al. | Dec 2009 | A1 |
| 20090309742 | Alexander et al. | Dec 2009 | A1 |
| 20100059561 | Ellis et al. | Mar 2010 | A1 |
| 20100069203 | Kawaguchi et al. | Mar 2010 | A1 |
| 20100159709 | Kotani et al. | Jun 2010 | A1 |
| 20100167783 | Alameh et al. | Jul 2010 | A1 |
| 20100185064 | Bandic et al. | Jul 2010 | A1 |
| 20100205541 | Rapaport et al. | Aug 2010 | A1 |
| 20100217099 | LeBoeuf et al. | Aug 2010 | A1 |
| 20100240458 | Gaiba | Sep 2010 | A1 |
| 20100261987 | Kamath | Oct 2010 | A1 |
| 20100331145 | Lakovic et al. | Dec 2010 | A1 |
| 20110003665 | Burton et al. | Jan 2011 | A1 |
| 20110009051 | Khedouri et al. | Jan 2011 | A1 |
| 20110022349 | Stirling et al. | Jan 2011 | A1 |
| 20110080349 | Holbein et al. | Apr 2011 | A1 |
| 20110087076 | Brynelsen et al. | Apr 2011 | A1 |
| 20110106449 | Chowdhary et al. | May 2011 | A1 |
| 20110131005 | Ueshima et al. | Jun 2011 | A1 |
| 20110193704 | Harper et al. | Aug 2011 | A1 |
| 20110197157 | Hoffman et al. | Aug 2011 | A1 |
| 20110224508 | Moon | Sep 2011 | A1 |
| 20110230729 | Shirasaki et al. | Sep 2011 | A1 |
| 20110242043 | Yarvis et al. | Oct 2011 | A1 |
| 20110261079 | Ingrassia | Oct 2011 | A1 |
| 20120015778 | Lee et al. | Jan 2012 | A1 |
| 20120015779 | Powch | 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 |
| 20120094649 | Porrati et al. | Apr 2012 | A1 |
| 20120119911 | Jean et al. | May 2012 | A1 |
| 20120165684 | Sholder | Jun 2012 | A1 |
| 20120166257 | Shiragami et al. | Jun 2012 | A1 |
| 20120183939 | Aragones et al. | Jul 2012 | A1 |
| 20120197986 | Chen et al. | Aug 2012 | A1 |
| 20120226471 | Yuen et al. | Sep 2012 | A1 |
| 20120226472 | Yuen et al. | Sep 2012 | A1 |
| 20120227737 | Mastrototaro et al. | Sep 2012 | A1 |
| 20120244995 | Dibenedetto | Sep 2012 | A1 |
| 20120265480 | Oshima | Oct 2012 | A1 |
| 20120274508 | Brown et al. | Nov 2012 | A1 |
| 20120277891 | Aragones et al. | Nov 2012 | A1 |
| 20120283855 | Hoffman | Nov 2012 | A1 |
| 20120290109 | Engelberg et al. | Nov 2012 | A1 |
| 20120295676 | Ackerson et al. | Nov 2012 | A1 |
| 20120313776 | Utter, II | Dec 2012 | A1 |
| 20120316456 | Rahman et al. | Dec 2012 | A1 |
| 20120324226 | Bichsel et al. | Dec 2012 | A1 |
| 20120330109 | Tran | Dec 2012 | A1 |
| 20130006718 | Nielsen et al. | Jan 2013 | A1 |
| 20130041590 | Burich et al. | Feb 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 |
| 20130166048 | Wcrncr et al. | Jun 2013 | A1 |
| 20130184841 | Ellis et al. | Jul 2013 | A1 |
| 20130190903 | Balakrishnan et al. | Jul 2013 | A1 |
| 20130191034 | Weast et al. | Jul 2013 | A1 |
| 20130203475 | Kil et al. | Aug 2013 | A1 |
| 20130228063 | Turner | Sep 2013 | A1 |
| 20130231574 | Tran | Sep 2013 | A1 |
| 20130231947 | Shusterman | Sep 2013 | A1 |
| 20130238287 | Hoffman et al. | Sep 2013 | A1 |
| 20130261475 | Mochizuki | Oct 2013 | A1 |
| 20130267249 | Rosenberg | Oct 2013 | A1 |
| 20130268199 | Nielsen et al. | Oct 2013 | A1 |
| 20130268236 | Yuen et al. | Oct 2013 | A1 |
| 20130268687 | Schrecker | Oct 2013 | A1 |
| 20130274904 | Coza et al. | Oct 2013 | A1 |
| 20130289366 | Chua et al. | Oct 2013 | A1 |
| 20130296666 | Kumar et al. | Nov 2013 | A1 |
| 20130296672 | O'Neil et al. | Nov 2013 | A1 |
| 20130296673 | Thaveeprungsriporn et al. | Nov 2013 | A1 |
| 20130310896 | Mass | Nov 2013 | A1 |
| 20130325396 | Yucn ct al. | Dec 2013 | A1 |
| 20130337974 | Yanev et al. | Dec 2013 | A1 |
| 20130338802 | Winsper | Dec 2013 | A1 |
| 20140035761 | Burton et al. | Feb 2014 | A1 |
| 20140039804 | Park et al. | Feb 2014 | A1 |
| 20140039840 | Yuen et al. | Feb 2014 | A1 |
| 20140039841 | Yuen et al. | Feb 2014 | A1 |
| 20140052280 | Yuen et al. | Feb 2014 | A1 |
| 20140067278 | Yuen et al. | Mar 2014 | A1 |
| 20140077673 | Garg et al. | Mar 2014 | A1 |
| 20140081667 | Joao | Mar 2014 | A1 |
| 20140094941 | Ellis et al. | Apr 2014 | A1 |
| 20140125618 | Panther et al. | May 2014 | A1 |
| 20140163402 | Lamego | Jun 2014 | A1 |
| 20140164611 | Molettiere et al. | Jun 2014 | A1 |
| 20140180022 | Stivoric ct al. | Jun 2014 | A1 |
| 20140213858 | Presura et al. | Jul 2014 | A1 |
| 20140249393 | Proud | Sep 2014 | A1 |
| 20140270375 | Canavan | Sep 2014 | A1 |
| 20140275885 | Isaacson et al. | Sep 2014 | A1 |
| 20140278229 | Hong et al. | Sep 2014 | A1 |
| 20140316305 | Venkatraman et al. | Oct 2014 | A1 |
| 20150026647 | Park et al. | Jan 2015 | A1 |
| 20150081465 | Dyment | Mar 2015 | A1 |
| 20150181314 | Swanson | Jun 2015 | A1 |
| 20150262499 | Wicka et al. | Sep 2015 | A1 |
| 20170270765 | Roberts | Sep 2017 | A1 |
| 20190190862 | Choudhary et al. | Jun 2019 | A1 |
| Number | Date | Country |
|---|---|---|
| 100998921 | Jul 2007 | CN |
| 101380252 | Mar 2009 | CN |
| 102598086 | Jul 2012 | CN |
| 11347021 | Dec 1999 | JP |
| 2178588 | Jan 2002 | RU |
| WO2011019 | Feb 2002 | WO |
| WO6055125 | May 2006 | WO |
| WO06090197 | Aug 2006 | WO |
| WO08038141 | Apr 2008 | WO |
| WO09042965 | Apr 2009 | WO |
| WO12170856 | Dec 2012 | WO |
| WO12170924 | Dec 2012 | WO |
| WO12171032 | Dec 2012 | WO |
| WO15127067 | Aug 2015 | WO |
| WO16003269 | Jan 2016 | WO |
| Entry |
|---|
| Ladetto et al. Sep. 2000, On Foot Navigation: When GPS alone is not Enough, Journal of Navigation 53(2):279-285. |
| Lammel et al., Sep. 2009, Indoor Navigation with MEMS Sensors, Proceedings of the Eurosensors XIII conference, 1(1):532-535. |
| Lester et al., 2005, A Hybrid Discriminative/Generative Approach for Modeling Human Activities, Proc. of the Int'l Joint Conf. Artificial Intelligence, pp. 766-772. |
| Lester et al., 2009, Validated caloric expenditure estimation using a single body-worn sensor, Proc. of the lnt'1 Conf. on Ubiquitous Computing, pp. 225-234. |
| Ohtaki et al., Aug. 2005, Automatic classification of ambulatory movements and evaluation of energy consumptions utilizing accelerometers and barometer, Microsystem Technologies, 11(8-10:)1034-1040. |
| Parkka et al., Jan. 2006, Activity Classification Using Realistic Data From Wearable Sensors, IEEE Transactions on Information Technology in Biomedicine, 10(1): 119-128. |
| Perrin et al., 2000, Improvement of Walking Speed Prediction by Accelerometry and Altimetry, Validated by Satellite Positioning, Medical & Biological Engineering & Computing, 38:164-168. |
| Retscher, 2006, An Intelligent Multi-Sensor system for Pedestrian Navigation, Journal of Global Positioning Systems, 5(1): 110-118. |
| Sagawa et al., Aug.-Sep. 1998, Classification of Human Moving Patterns Using Air Pressure and Acceleration, Proceedings of the 24.sup.th Annual Conference of the IEEE Industrial Electronics Society, 2:1214-1219. |
| Sagawa et al., Oct. 2000, Non-restricted measurement of walking distance, IEEE lnt'l Conf. on Systems, Man, and Cybernetics, 3:1847-1852. |
| SCP 1OOO-D01/D11 Pressure Sensor as Barometer and Altimeter, VTI Technologies Application, Jun. 2006, Note 33. |
| Specification of the Bluetooth. RTM. System, Core Package, version 4.1, Dec. 2013, vols. 0 & 1, 282 pages. |
| Stirling et al., 2005, Evaluation of a New Method of Heading Estimation of Pedestrian Dead Reckoning Using Shoe Mounted Sensors, Journal of Navigation, 58:31-45. |
| Suunto LUMI User Guide, Jun. and Sep. 1997. |
| Tanigawa et al., Mar. 2008, Drift-free dynamic height sensor using MEMS IMU aided by MEMS pressure sensor, Workshop on Positioning, Navigation and Communication, pp. 191-196. |
| International Search Report dated Aug. 15, 2008, in related application PCT/IB07/03617. |
| Office Action dated Nov. 18, 2019 issued in U.S. Appl. No. 16/160,805. |
| Office Action dated Jun. 10, 2020 issued in U.S. Appl. No. 16/160,805. |
| Chandrasekar et al., Aug. 28-Sep. 1, 2012, Plug-and-Play, Single-Chip Photoplethysmography, 34th Annual International Conference of the IEEE EMBS, San Diego, California USA, 4 pages. |
| Clifford et al., “Altimeter and Barometer System”, Nov. 2006, Freescale Semiconductor Application Note AN1979, Rev. 3. |
| Fang et al., Dec. 2005, Design of a Wireless Assisted Pedestrian Dead Reckoning System—Thc NavMotc Expcriencc, IEEE Transactions on Instrumcntation and Mcasuremcnt, 54(6):2342-2358. |
| Godfrey et al., 2008, Direct Measurement of Human Movement by Accelerometry, Medical Engineering & Physics, 30:1364-1386. |
| Godha et al., May 2008, Foot Mounted Inertia System for Pedestrian Navigation, Measurement Science and Technology, 19(7):1-9. |
| Intersema App., Using MS5534 for altimeters and barometers, Note AN501, Jan. 2006. |
| Number | Date | Country | |
|---|---|---|---|
| 20220157428 A1 | May 2022 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 16946191 | Jun 2020 | US |
| Child | 17532057 | US | |
| Parent | 16160805 | Oct 2018 | US |
| Child | 16946191 | US | |
| Parent | 15583980 | May 2017 | US |
| Child | 16160805 | US | |
| Parent | 15099325 | Apr 2016 | US |
| Child | 15583980 | US | |
| Parent | 14445033 | Jul 2014 | US |
| Child | 15099325 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 14271412 | May 2014 | US |
| Child | 14445033 | US |
