US 9,965,059 B2Grant
Methods, systems and devices for physical contact activated display and navigation
Issue Date:2018-05-08
•21 Claims
•16 Drawing Sheets
Abstract
Methods, systems and devices are provided for providing user interface navigation of screen display metrics of a device. In one example, a device is configured for capture of activity data for a user. The device includes a housing and a screen disposed on the housing to display a plurality of metrics which include metrics that characterize the activity captured over time. The device further includes a sensor disposed in the housing to capture physical contact upon the housing. A processor is included to process the physical contact to determine if the physical contact qualifies as an input. The processor enables the screen from an off state when the physical contact qualifies as the input. The screen is configured to display one or more of the plurality of metrics in accordance with a scroll order, and a first metric displayed in response to the physical contact that qualifies as the input.
Metadata
Assignee
- Fitbit, Inc.
Inventors
- Nicholas Myers
- Christine Brumback
- Timothy Roberts
- James Park
- Dave Knight
- Shelten Yuen
- Jayson Messenger
Application Information
Application Number:US 15/096,240
Filing Date:2016-04-11
Priority Date:2010-09-30
Art Unit:2624
Classifications
IPC:
G06F3/038G06F3/041G06F19/00A63B24/00G06F1/16G06F3/0482G06F3/0485H04B7/26A61B5/00A61B5/0205A61B5/021A61B5/024A61B5/11A61B5/22G01C22/00
Field of Search:
G06F 3/0485G06F 1/163G06F 3/03547G06F 3/0414G06F 1/1613G06F 2200/1637G06F 3/014
Patent Drawings (16 sheets)
Description
Claim of Priority
[0001] This application is a continuation of U.S. patent application Ser. No. 14/192,282, entitled “Methods, Systems and Devices for Physical Contact Activated Display and Navigation,” filed on Feb. 27, 2014, which claims priority from U.S. patent application Ser. No. 14/050,270, entitled “Methods, Systems and Devices for Physical Contact Activated Display and Navigation”, filed on Oct. 10, 2013, which claims priority to U.S. Provisional Application No. 61/885,959, entitled “Methods, Systems and Devices for Physical Contact Activated Display and Navigation”, filed on Oct. 2, 2013, all of which are incorporated herein by reference.
[0002] U.S. patent application Ser. No. 14/192,282, entitled “Methods, Systems and Devices for Physical Contact Activated Display and Navigation,” filed on Feb. 27, 2014 is a continuation-in-part of U.S. patent application Ser. No. 13/959,714 (now issued as U.S. Pat. No. 8,762,101, issued Jun. 24, 2014), filed on Aug. 5, 2013, titled “Methods and Systems for Identification of Event Data Having Combined Activity and Location Information of Portable Monitoring Devices”, which is a continuation-in-part of U.S. patent application Ser. No. 13/693,334 (now U.S. Pat. No. 8,548,770, issued Oct. 1, 2013), filed on Dec. 4, 2012, titled “Portable Monitoring Devices and Methods for Operating Same”, which is a divisional of U.S. patent application Ser. No. 13/667,229 (now U.S. Pat. No. 8,437,980, issued on May 7, 2013), filed on Nov. 2, 2012, titled “Portable Monitoring Devices and Methods for Operating Same”, which is a divisional of U.S. patent application Ser. No. 13/469,027 (now U.S. Pat. No. 8,311,769, issued Nov. 13, 2012) filed May 10, 2012, titled “Portable Monitoring Devices and Methods for Operating Same”, which is a divisional of U.S. patent application Ser. No. 13/246,843 (now U.S. Pat. No. 8,180,591, issued on May 15, 2012) filed on Sep. 27, 2011, which is a divisional of U.S. patent application Ser. No. 13/156,304 (now U.S. Pat. No. 9,167,991, issued on Oct. 27, 2015) filed on Jun. 8, 2011, titled “Portable Monitoring Devices and Methods for Operating Same”, which claims the benefit of and priority to, under 35 U.S.C. 119 § (e) to U.S. Provisional Patent Application No. 61/388,595, filed on Sep. 30, 2010, and titled “Portable Monitoring Devices and Methods for Operating Same”, and to U.S. Provisional Patent Application No. 61/390,811, filed on Oct. 7, 2010, and titled “Portable Monitoring Devices and Methods for Operating Same”, all of which are hereby incorporated by reference in their entirety.
[0003] U.S. patent application Ser. No. 13/959,714, (now issued as U.S. Pat. No. 8,762,101) filed Aug. 5, 2013, titled “Methods and Systems for Identification of Event Data Having Combined Activity and Location Information of Portable Monitoring Devices”, is a continuation-in-part of U.S. patent application Ser. No. 13/759,485, (now issued as U.S. Pat. No. 8,543,351, issued on Sep. 24, 2013), filed on Feb. 5, 2013, titled “Portable Monitoring Devices and Methods for Operating Same”, which is a divisional of U.S. patent application Ser. No. 13/667,229 (now U.S. Pat. No. 8,437,980, issued on May 7, 2013) filed on Nov. 2, 2012, titled “Portable Monitoring Devices and Methods for Operating Same”, which is a divisional of U.S. patent application Ser. No. 13/469,027 (now U.S. Pat. No. 8,311,769, issued on Nov. 13, 2012), filed on May 10, 2012, titled “Portable Monitoring Devices and Methods for Operating Same”, which is a divisional of U.S. patent application Ser. No. 13/246,843 (now U.S. Pat. No. 8,180,591, issued on May 15, 2012) filed on Sep. 27, 2011, which is a divisional of U.S. patent application Ser. No. 13/156,304 (now U.S. Pat. No. 9,167,991, issued on Oct. 27, 2015), filed on Jun. 8, 2011, titled “Portable Monitoring Devices and Methods for Operating Same”, which claims the benefit of and priority under 35 U.S.C. 119 § (e), to U.S. Provisional Patent Application No. 61/388,595, filed on Sep. 30, 2010, and titled “Portable Monitoring Devices and Methods for Operating Same” and to U.S. Provisional Patent Application No. 61/390,811, filed on Oct. 7, 2010, and titled “Portable Monitoring Devices and Methods for Operating Same”, all of which are hereby incorporated by reference in their entirety.
[0004] U.S. patent application Ser. No. 14/192,282, entitled “Methods, Systems and Devices for Physical Contact Activated Display and Navigation,” filed on Feb. 27, 2014 is a continuation-in-part of U.S. patent application Ser. No. 13/913,726 (now U.S. Pat. No. 8,670,953, issued on Mar. 11, 2014), filed on Jun. 10, 2013, titled “Portable Monitoring Devices and Methods for Operating Same”, all of which are incorporated by reference in its entirety.
Field
[0005] The present disclosure relates to systems and methods for capturing activity data over a period of time and methods and systems for navigating metric data to a display.
Background
[0006] 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.
[0007] To provide users concerned with health and fitness a way of measuring or accounting for their activity or lack thereof, fitness trackers are often used. Fitness trackers are used to measure activity, such as walking, motion, running, sleeping, being inactive, bicycling, exercising on an elliptical trainer, and the like. Usually, the data collected by such fitness trackers can be transferred and viewed on a computing device. However, such data is often provided as a basic accumulation of activity data with complicated or confusing interfaces.
[0008] It is in this context that embodiments described herein arise.
Summary
[0009] Embodiments described in the present disclosure provide systems, apparatus, computer readable media, and methods for analyzing tracked activity data and providing navigation screens and interfaces on a device used by a user. The activity tracking device includes sensor(s) for detecting when physical contact occurs onto the activity tracking device and logic for providing a display action to the screen of the activity tracking device. The physical contact, in one embodiment, can be qualified as an input when the physical contact has a particular characteristic or pattern that is predefined. The characteristic can be, when the contact is the result of one or more taps, e.g., physical contact to the activity tracking device by a finger or hand of the user, or object held by a user and used to impart the contact.
[0010] In one embodiment, a method is provided. The method includes detecting a physical contact by a sensor of a device that is configured to display a plurality of metrics on a screen of the device and examining the physical contact to determine if the physical contact qualifies as an input for the device. The method acts to maintain the screen of the device in an off state for physical contact that does not qualify as the input and actives the screen of the device to display a first metric when the examining determines that the physical contact qualifies as the input. The method is executed by a processor.
[0011] In another embodiment, a device configured for capture of activity data for a user is provided. The device includes a housing and a screen disposed on the housing to display a plurality of metrics which include metrics that characterize the activity captured over time. The device further includes a sensor disposed in the housing to capture physical contact upon the housing. A processor is included to process the physical contact to determine if the physical contact qualifies as an input. The processor enables the screen from an off state when the physical contact qualifies as the input. The screen is configured to display one or more of the plurality of metrics in accordance with a scroll order, and a first metric of the plurality of metrics is displayed in accordance with user configuration identifying that the first metric is to be displayed in response to the physical contact that qualifies as the input, as determined by the processor.
[0012] In another embodiment, computer readable medium for storing program instructions executable by a processor is provided. The computer readable medium includes (a) program instructions for detecting a physical contact by a sensor of a device that is configured to display a plurality of metrics on a screen of the device; (b) program instructions for examining the physical contact to determine if the physical contact qualifies as an input for the device; (c) program instructions for maintaining the screen of the device in an off state for physical contact that does not qualify as the input; (d) program instructions for activating the screen of the device to display a first metric when the examining determines that the physical contact qualifies as the input, (e) program instructions for detecting user input to transition from the first metric to a next metric in a scroll order or to an off state when no user input is detected. If user input is received within a predetermined time after the off state, a process turns the screen on and displays the last displayed metric, and if the user input is received after the predetermined time after the off state, a process turns the screen on and displays the first metric. The plurality of metrics include a time of day metric and metrics representing activity data captured by the device when associated with a user, the activity data being of the user.
[0013] In some embodiments, the input is associated with qualified physical contact, and the user input is associated with one of qualified physical contact, or non-touch proximity input, or voice input, or button press input.
[0014] In still another embodiment, an activity tracking device is configured for capturing data or activity data for a user. The device includes a housing configured as a wearable wrist attachable structure or a structure that can accompany the user to capture the activity data. The device includes a screen disposed on the housing to display a plurality of metrics which include metrics that characterize the activity captured over time. The device has an accelerometer sensor disposed in the housing to capture physical contact upon the housing. The device further includes a processor to process the physical contact to determine if the physical contact qualifies as an input. The processor enables the screen from an off state when the physical contact qualifies as the input, and the screen is configured to display one or more of the plurality of metrics in accordance with a scroll order. A first metric of the plurality of metrics is displayed in accordance with user configuration identifying that the first metric is to be displayed in response to the physical contact that qualifies as the input, as determined by the processor. The physical contact captured by the accelerometer sensor is from sensing or detecting one or more taps having a predefined tap profile upon the housing by a finger, or hand or object. The user configuration identifying the first metric enables setting of a shortcut to any metric in the scroll order to be the first metric.
[0015] 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.
Brief Description of the Drawings
[0016] Various embodiments described in the present disclosure may best be understood by reference to the following description taken in conjunction with the accompanying drawings.
[0017] FIG. 1A shows a block diagram of an activity tracking device, in accordance with one embodiment of the present invention.
[0018] FIG. 1B illustrates an example of an activity tracking device, in accordance with one embodiment of the present invention.
[0019] FIG. 1C illustrates another example of an activity tracking device, in accordance with one embodiment of the present invention.
[0020] FIG. 2A illustrates an example of activity tracking device including example components utilized for tracking activity and motion of the device, and associated interfaces to a display screen, in accordance with one embodiment of the present invention.
[0021] FIG. 2B illustrates an example of activity tracking device in communication with a remote device, in accordance with one embodiment of the present invention.
[0022] FIG. 3A illustrates a diagram of input interfaces for accessing screens that display metrics associated with the activity tracking device, in accordance with one embodiment of the present invention.
[0023] FIG. 3B illustrates an example where the activity tracking device has been programmed or customize by a user to select a specific metric to display on the display screen upon receiving input, in accordance with one embodiment of the present invention.
[0024] FIG. 3C illustrates another example where the activity tracking device 100 has been programmed or customize by a user to select a different metric to be the first metric, in accordance with one embodiment of the present invention.
[0025] FIG. 3D illustrates a flowchart defining example interactivity and display functionality of the activity tracking device, in accordance with one embodiment of the present invention.
[0026] FIG. 3E illustrates an example of a table showing example scroll orders and inputs, in accordance with one embodiment of the present invention.
[0027] FIG. 3F illustrates an example of the scroll order that extends from metric 1 to metric 4, in accordance with one embodiment of the present invention.
[0028] FIG. 3G illustrates an example where metric 3 is designated as the first metric, which will be the metric data displayed initially upon receiving the double tap input.
[0029] FIG. 4A-1 illustrates an example in accordance with an alternative embodiment, associated with navigating the screens of an activity tracking device showing ready mode.
[0030] FIG. 4A-2 illustrates an example in accordance with an alternative embodiment, associated with navigating the screens of an activity tracking device showing a first metric.
[0031] FIG. 4A-3 illustrates an example in accordance with an alternative embodiment, associated with navigating the screens of an activity tracking device showing a next metric.
[0032] FIG. 4A-4 illustrates an example in accordance with an alternative embodiment, associated with navigating the screens of an activity tracking device showing a next metric.
[0033] FIG. 4A-5 illustrates an example in accordance with an alternative embodiment, associated with navigating the screens of an activity tracking device showing a next metric.
[0034] FIG. 4A-6 illustrates an example in accordance with an alternative embodiment, associated with navigating the screen of an activity tracking device showing a next metric.
[0035] FIG. 4A-7 illustrates an example in accordance with an alternative embodiment, associated with navigating the screens of an activity tracking device showing no physical contact.
[0036] FIG. 4A-8 illustrates an example in accordance with an alternative embodiment, associated with navigating the screens of an activity tracking device showing a ready mode.
[0037] FIG. 4B illustrates an example of a system that includes the device, a remote device, and the server interfacing over the Internet, in accordance with one embodiment of the present invention.
[0038] FIG. 5 illustrates a table providing a scroll order and the various inputs that can be defined to traverse the scroll order, in one embodiment.
[0039] FIG. 6 illustrates an example of a physical contact represented by tap(s), which act to activate the display in a first metric, in accordance with one embodiment of the present invention.
[0040] FIG. 7 illustrates another example where a single tap activates the display in the first metric, in accordance with one embodiment of the present invention.
[0041] FIG. 8 illustrates an example of a double tap physical contact acting to initiate the display with the first metric, in accordance with one embodiment of the present invention.
[0042] FIG. 9 illustrates an example where various types of activities of users 900A-900I can be captured or collected by activity tracking devices, in accordance with various embodiments of the present invention.
Detailed Description
[0043] Embodiments described in the present disclosure provide systems, apparatus, computer readable media, and methods for analyzing tracked activity data and providing navigation screens and interfaces. Some embodiments are directed to providing navigation interfaces for an activity tracking device. The activity tracking device includes sensors for detecting when physical contact occurs onto the activity tracking device and logic for providing a display action to the screen of the activity tracking device. The physical contact, in one embodiment, can be qualified as an input when the physical contact has a particular characteristic that is predefined. The characteristic can be, when the contact is the result of one or more taps, e.g., physical contact to the activity tracking device by a finger or hand of the user, or object held by a user and used to impart the contact.
[0044] In other embodiments, the input can be non-physical, such as proximity sensing input. The proximity sensing input can be processed by an infrared proximity sensor, a thermal sensor, etc. The input can also be by way of a button, voice input, gaze detected input, input processed in response to motion or motion profiles, etc.
[0045] 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.
[0046] 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.
[0047] FIG. 1A shows a block diagram of an activity tracking device 100, in accordance with one embodiment of the present invention. The activity tracking device 100 is contained in a housing, which may be worn or held by a user. The housing may be in the form of a wristband, a clip on device, a wearable device, or may be held by the user either in the user's hand or in a pocket or attached to the user's body. The activity tracking device 100 includes device components 102, which may be in the form of logic, storage, and glue logic, one or more processors, microelectronics, and interfacing circuitry. In one example, the components 102 will include a processor 106, memory 108, a wireless transceiver 110, a user interface 114, biometric sensors 116, and environmental sensors 118.
[0048] 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.).
[0049] In some embodiments, the user interface 114 is configured to receive user interaction 104 that is in the form of noncontact input. The noncontact input can be 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.
[0050] 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. As will be explained in more detail below, the 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.
[0051] FIG. 1B illustrates an example of an activity tracking device 100 having a housing 130 in the form of a wearable wrist attachable device. The sensors of the activity tracking device 100 can, as mentioned above, detect motion such as physical contact that is applied and received on a surface 120 of the housing 130. In the example shown, the physical contact 124 is in the form of a tap or multiple taps on the surface 120. Device components 102 are, in one embodiment, contained within the housing 130. The location at which the device components 102 are integrated into the housing 130 can vary. For example, the device components 102 can be integrated throughout various locations around the housing 130, and not limited to the central portion of the wrist attachable device. In some embodiments, the device components 102 can be integrated into or with a smart watch device.
[0052] In other embodiments, the device components 102 are positioned substantially in a central position of the wrist attachable device, such as under or proximate to a location where a display screen 122 is located. In the illustrated example, the housing 130 also includes a button 126. The button 126 can be pressed to activate the display screen 122, navigate to various metrics displayed on the screen 122, or turn off the screen 122.
[0053] FIG. 1C illustrates another example of an activity tracking device 100, in accordance with one embodiment of the present invention. The form factor of the activity tracking device 100 is shown as a clickable device that includes a screen 122, a button 126, and device components 102 integrated within the housing 130′. The housing 130′ can include a clip that allows for attachment to clothing or articles of the user, or to simply place the device within a pocket or holder of the user. Accordingly, the physical contact 124 shown with respect to FIG. 1B can also be implemented upon the surface 120 of activity tracking device 100 of FIG. 1C . It should be understood, therefore, that the form factor of the activity tracking device 100 can take on various configurations and should not be limited to the example configurations provided herein.
[0054] FIG. 2A illustrates an example of activity tracking device 100 of FIG. 1A , showing some additional example components utilized for tracking activity and motion of the device, and associated interfaces to display screen 122. In this example, the finger of a user can be used to tap and provide physical contact 124 onto any surface 120 of activity tracking device 100. The physical contact, when sensed by sensors 156 of the activity tracking device 100, will cause a response by the activity tracking device 100, and therefore provide some metric on the display screen 122. In one embodiment, examples of a display screen 122 can include, but are not limited to, liquid crystal display (LCD) screens, light emitting diode (LED) screens, organic light emitting diode (OLED) screens, plasma display screens, etc.
[0055] As shown in FIG. 2A , the activity tracking device 100 includes logic 158. Logic 158 may include activity tracking logic 140, physical contact logic 142, display interface logic 144, alarm management logic 146, wireless communication logic 148, processor 106, and sensors 156. Additionally, storage (e.g. memory) 108, and a battery 154 can be integrated within the activity tracking device 100. The activity tracking logic 140 can include logic that is configured to process motion data produced by sensors 156, so as to quantify the motion and produce identifiable metrics associated with the motion.
[0056] 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.
[0057] In other embodiments, the physical contact logic can be programmed to determine when particular physical contacts occurred, the time in between the physical contacts, and whether the one or more physical contacts will qualify within predefined motion profiles that would indicate that an input is desired. If physical contact occurs that is not within some predefined profile or pattern, the physical contact logic will not indicate or qualify that physical contact as an input.
[0058] The display interface logic 144 is configured to interface with the processor and the physical contact logic to determine when specific metric data 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.
[0059] 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.
[0060] 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.
[0061] FIG. 2B illustrates an example of activity tracking device 100 in communication with a remote device 200. Remote device 200 is a computing device that is capable of communicating wirelessly with activity tracking device 100 and with the Internet 160. Remote device 200 can support installation and execution of applications. Such applications can include an activity tracking application 202. Activity tracking application 202 can be downloaded from a server. The server can be a specialized server or a server that provides applications to devices, such as an application store. Once the activity tracking application 202 is installed in the remote device 200, the remote device 200 can communicate or be set to communicate with activity tracking device 100 (Device A). The remote device 200 can be a smartphone, a handheld computer, a tablet computer, a laptop computer, a desktop computer, or any other computing device capable of wirelessly interfacing with Device A and the Internet.
[0062] 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.
[0063] 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.
[0064] 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.
[0065] The information can include, without limitation, data associated with a display scroll order 230, user data, etc. As will be described in greater detail below, the display scroll order 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.
[0066] 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.
[0067] The configurations can include defining which metrics will be displayed on the activity tracking device 100. In addition, the configurations can include identification of which metrics will be a first metric to be displayed on the activity tracking device. The first metric to be displayed by the activity tracking device can be in response to a user input at the activity tracked device 100. As noted above, the user input can be by way of physical contact. The physical contact is qualified by the processor and/or logic of the activity tracking device 100 to determine if the physical contact should be treated as an input. The input can trigger or cause the display screen of the activity tracking device 100 to be turned on to display a specific metric, that is selected by the user as the first metric to display. In another embodiment, the first metric displayed in response to the input can be predefined by the system as a default.
[0068] The configuration provided by the user by way of the server 220 and the activity management application 224 can also be provided by way of the activity tracking application 202 of the computing device 200. For example, the activity tracking application 202 can include a plurality of screens that also display metrics associated with the captured motion data of the activity tracking device 100. The activity tracking application 202 can also allow for user input and configuration at various graphical user interface screens to set and define which input will produce display of the first metric. In other embodiments, in addition to identifying the first metric to be displayed in response to the input, which may be physical contact, the configuration can allow an ordering of which metrics will be displayed in a specific scroll order.
[0069] In another embodiment, the scroll order of the metrics is predefined. In some embodiments, the input provided by the user by way of the physical contact can be pre-assigned to a specific metric in the scroll order. For example, the scroll order can remain the same, while the input can allow the screen to jump to a specific entry in the scroll order. Jumping to a specific entry can be viewed as a shortcut to a specific entry that is desired to be seen first by the user upon providing physical contact or input to the device 100.
[0070] FIG. 3A illustrates a diagram of input interfaces for accessing screens that display metrics associated with the activity tracking device 100, in accordance with one embodiment of the present invention. As shown, the display screen 122 is in the off state before access is requested of the device 100. In one embodiment, the device 100 will shift to and off state when input is not received for a predetermined period of time, which allows the device 102 to save energy (i.e., battery power).
[0071] In mode 1, the display screen 122 is off 300 and upon a button press (e.g., of button 126 in FIG. 1B ), the display screen 122 changes in transition 302a in direction 303a, to illustrate the time of day metric. However, if the battery is determined to be critical (e.g., the battery is too low to activate the device or operate it properly for a period of time), the display screen 122 will illustrate a graphic of a battery 304. The graphical battery 304 will indicate to the user that the device must be charged. If it is determined that the battery is low, a low battery indicator 306 will be shown in the display 122. The user can continue to use the device, but the critical battery notification may be re-displayed. After showing the low battery indicator 306, the display will advance to the clock metrics 310 after a predetermined period of time (e.g., 1 second). If it is determined that the timer function has been running, then the transition from the low battery indicator 306 would be automatic to the timer metric 308. Therefore, if the timer function is not running, the system will transition to the clock metrics 310, in this embodiment.
[0072] In mode 2, if it is determined that a button of the activity tracking device 100 had been pressed and held for a predetermined period of time (e.g., 1 second), then the transition would be directly to a timer metric 308. The timer metric 308 operates a stopwatch function, which first shows a graphic of a stopwatch and then automatically transitions to the time kept by the stopwatch function. If the user desires to transition from the timer metric 308 to one of the other metrics in the scroll order shown in FIG. 3A , the user can press the button 126 of the activity tracking device 100. For example, the downward facing arrow indicates that a button press will transition the display screen 122 to the next metric and so on. It should be understood that the downward facing arrow can also be activated by other than a button press, such as by physical contact (e.g., one or more taps onto the surface of the activity tracking device 100). As noted above, other input functions can also be provided, such as proximity sensing, touchscreens, voice activation, gesture detection, etc.
[0073] In mode 3, if it is determined that a double tap was detected on the surface of the activity tracking device 100 by a sensor, the display screen 122 will go from being on 302, to displaying a predetermined first metric. In this example, the predetermined first metric is a main goal 330 of the user, and is shown to be a step count metric 312. As shown, the display screen 122 will transition 302b in a direction 303a, which exposes an icon or graphic associated with the main goal 330, which are steps. The steps are shown as feet icon. The display screen 122, in one embodiment also transitions from the feet icon to the numerical value of the steps taken by the user utilizing the activity tracking device 100. If the user wishes to transition and view the other metrics in the scroll order, such as distance metric, calories burned metric, floors metric, very active minutes metric, alarm metric, the user can transition by pressing buttons 126 on the device 100. Again, transitioning downward (or through a list in any direction) is shown by the downward facing arrows, which are activated in response to a button press (or other types of inputs). These example transitions allow for display of other screens/data concerning metrics 308, 310, 312, 314, 316, 318, 320, 322, etc. It should be understood that additional metrics can be added to the scroll order, certain metrics can be deleted from the scroll order, the scroll order can be re-arranged, and these customizations can be made in response to user configurations or system configurations or default configurations.
[0074] After a predetermined period of time that no input is received by the activity tracking device 100, the display screen 122 will transition to and off state 300. The transition, in one embodiment allows for the display screen 122 to transition off 302c in direction 303b. Therefore, the display screen 122 will move to the off state 300 where battery consumption is reduced. In one embodiment, the transition to the off state 300 will occur after about 6 seconds. It should be understood that this predefined period of time can be modified for the specific configuration and should not be limited to the specific example. As will be described below with reference to FIG. 3D , one embodiment will allow for custom transitions between an off state to specific metrics based on the amount of time determined to have passed when no user input has been received.
[0075] FIG. 3B illustrates an example where the activity tracking device 100 has been programmed or customize by a user to select a specific metric to display on the display screen 122 upon receiving input. In this example, the configuration has been made to the functionality of mode 3. In mode 3, the user has configured a double tap (physical contact) detected to activate or jump to a specific metric selected by the user. In this example, the user has selected that a double tap input will cause the display screen 122 to transition from off state 302 to the clock metric 310. This will jump 332a, in the scroll order, to the clock metric 310. The clock metric 310 will be considered the first metric, of a plurality of metrics to be displayed on the display screen 122 of the activity tracking device, in response to a double tap. Once the device jumps to display the clock metric 310, the user can then scroll through the remaining metrics by selecting or pressing a button 126 of the activity tracking device 100. As noted above, transition to the other metrics can also be enabled by additional physical contact or non-physical contact inputs.
[0076] FIG. 3C illustrates another example where the activity tracking device 100 has been programmed or customize by a user to select a different metric to be the first metric. The first metric is a metric that will be displayed on the display screen 122 upon receiving the input, in accordance with mode 3. In this example, mode 3 is a transition from the off state 300 to display the first metric in response to a double tap. Although specific mention of a double tap is provided herein, it should be understood that any number of tap(s) can be provided to qualify as the physical contact sensed by a sensor of the device 100. Once the double tap is received, the display screen of the activity tracking device 100 will jump 332b to calories burned metric 316. Calories burned metric 316 is a metric that the user has configured to be the first metric that will be displayed upon receiving a double tap when the display was in an off state. By way of this illustration, it should be understood that any one of the metrics can be configured to be the first metric that is shown on the display screen 122 upon receiving the double tap. A user can then transition to other metrics in the scroll order or list of metrics by providing additional input. The downward facing arrow between the metrics shows the transition through the various metrics. Upon displaying each of the metrics, in one embodiment, the display screen 122 will display a graphic icon indicative of the type of metric that will be displayed. The right facing arrow indicates that the transition between the graphic icons to the numerical metrics will be automatically transitioned without additional user input.
[0077] FIG. 3D illustrates a flowchart defining example interactivity and display functionality of the activity tracking device 100, in accordance with one embodiment of the present invention. In one embodiment, the screen is in an off state in operation 390. In operation 391, physical contact or input is detected by the activity tracking device 100. The physical contact or input, as defined above can include taps, touches, proximity, button pushes, etc. Once the input is detected in operation 391, the display screen of the device will be activated to show the first metric. As described above, the first metric can be user configured so as to allow selection of which metric will be displayed first upon receiving the input. In operation 393, it is determined if additional input is received to scroll or move to the next metric.
[0078] If additional input is received in operation 394, the display screen will move in scroll to the next metric. This will continue as the user is allowed to select the next metric in the list or scroll order. In one embodiment, the scroll order can wrap around and continue to display metrics. If no input is received for a period of time, the display screen will turn off in operation 395. In operation 396, it is determined if input is received within a predetermined amount of time after the screen was turned off. For example, if input, such as a button press is received within 3 seconds of the screen turning off, the screen will turn back on and display the last metric that had been displayed.
[0079] For instance, in FIG. 3A , if the last metric being viewed was calories burned 316, and no input was received, the screen will turn off. If within 3 seconds of the screen being off a button press is detected, the calories burned metric 316 will be displayed once again in operation 397. The method will then proceed back to operation 394 where it is determined if additional input is received to transition to view a next metric 393. If no input is received after a predetermined amount of time since the screen was off in operation 396, the method will transition to operation 398. In operation 398 it is determined that input occurred after the predetermined amount of time that the screen was off, the method will return back to activate the screen and show the first metric. The input received in operation 398 may be a button press or a physical contact, such as input received through mode 1 or mode 3. If after the predetermined amount of time that the screen was off no input was received, the screen will transition back or remain in the off state 390.
[0080] FIG. 3E illustrates an example of a table 350 showing example scroll order 352 and input 354. In this example, the scroll order will include screen off 300, clock metric 310, distance metric 314, calories burned metric 316, floors metric 318, very active minutes metric 320, alarm metric 322. In this example, when no physical contact qualifying as an input is received, the screen will remain off. This of course also includes receiving no button presses so that the screen will remain off. In this example, a double tap (DT) physical contact 124 will activate the display screen 122 with the first metric, which is identified by the user to be the clock metric 310. The user can then transition by various button presses 126a to the various metrics in the scroll order after receiving each of the button presses. As noted above, instead of button presses other input can also be used to transition between the metrics.
[0081] FIG. 3F illustrates an example of the scroll order 380 that extends from metric 1 to metric 4. In this example, the first metric has been identified to be metric 1. Additionally, a double tap input is predefined to access metric 1 as the initially displayed metric on the activity tracking device. FIG. 3G illustrates an example where metric 3 is designated as the first metric, which will be the metric data displayed initially upon receiving the double tap input 124. The custom designation of the first metric to any one of the metrics in the scroll order functions as a jump 332 to the specific metric identified by the user. The specific metric identified as the first metric can also be predefined by the system or set as a default. As used herein, a jump should be interpreted to also include a shortcut to a specific metric in a list.
[0082] FIGS. 4A-1 to 4A-8 illustrate examples in accordance with an alternative embodiment, associated with navigating the screens of activity tracking device 100. In this example, that device 100 has a screen 122 that is in the off state. In FIG. 4A-1 , the screen is in an off state, which may indicate that the device is in a ready mode and ready to receive input. In FIG. 4A-2 , the device receives physical contact 124, which may be a double tap. The physical contact and 24 will activate the display screen 122 and display a first metric. In this example the first metric is the time of day. In FIG. 4A-3 , additional physical contact is received by device 100 which causes the display screen 122 to show a next metric, which in this example is step count. In FIG. 4A-4 , the device 100 has received another double tap 124 which then causes the display screen 122 to show a next metric. This next metric is a step count. In FIG. 4A-5 , the device receives another physical contact 124 which causes the device to illustrate a next metric. The next metric is calories burned. In FIG. 4A-6 , the device receives another physical contact 124 which causes the display screen 122 to show a next metric. The next metric is a distance. In FIG. 4A-7 , it is determined that no physical contact has occurred for a predetermined period of time 402. This will cause the device 100, as shown in FIG. 4A-8 , to transition to turn off the screen, and back to the ready mode.
[0083] FIG. 4B illustrates an example of a system that includes the device 100, a remote device 200, and the server 220 interfacing over the Internet 160. The interfacing allows for the remote device 200 to set the specific configuration of the scroll order settings of device 100, in accordance with a user configuration. In this example, using the remote device 200, the user navigates to a screen provided by the application 202 of the remote device. The application 202 is an activity tracking application that can communicate with activity monsoon application 224 managed by the server 220. As discussed above with reference to FIG. 2B , activity tracking application 202 can include a plurality of user interfaces and screens to allow user input and access to the activity data or configure settings.
[0084] The settings being configured in this example includes settings associated with the scroll order and the definition of the first metric. In this example, the activity tracking application 202 will allow the user to login to his or her user accounts and access and identify device a, which is the activity tracking device 100. Using screens and menus provided by the activity tracking application, the user is able to identify the display scroll order settings in the screen 200a of the device 100. In this example, the user has decided to set the home screen metric (e.g. first metric), as time or clock. Optionally, the user may then select the scroll order of the various screens or GUIs (e.g., screens 200a-200h) to be traversed. In this example, the user has selected step count metric to follow, then stairs metric, then calories burned metric, and then distance metric. The user may also be prompted or can elect to edit, remove or add additional metrics to the scroll order setting. Once the user approves of the settings, the user can save the settings to the user profile. Saving the settings to the user profile can act to update the settings to the user display scroll order configuration 230 in the user account (user A). This configuration setting is synchronized with the server 220 and then transferred to the device 100 by way of a wireless connection over a predefined proximity distance 404. As noted above, in one embodiment, communication between the device 100 and the remote device 200 (computing device) is by way of a wireless link. The wireless link may be, for example Bluetooth radio communication, and in one embodiment, low-energy Bluetooth radio communication.
[0085] FIG. 5 illustrates a table providing a scroll order 352 and the various inputs 354 that can be defined to traverse the scroll order, in one embodiment. In this embodiment, the screen is off 300 and ready for use. When the screen is off, the device is on and operating, but energy to power the screen does not consume battery power. In this state, no physical contact has been received during a period of time. When a double tap is received, the configuration will allow the screen to transition to a first metric, which is the time of day. As noted above, the first metric can be defined to be any one of the metrics in the scroll order. Additionally, the scroll order can remain in the same order yet the first metric can be identified as any one of the metrics in the scroll order, and access to the specific metric can be by way of a jump or shortcut. In another embodiment, the scroll order configuration can be reordered. In this example, transitioning from metric to next metric is by way of double tap (DT) physical contact. However as noted above, the transitioning between the metrics can be by way of any number of inputs, such as physical and nonphysical interfaces, voice communication, proximity communication, button presses, etc.
[0086] FIG. 6 illustrates an example of a physical contact 124 represented by taps, which act to activate the display 602 in a first metric. The next input can be an additional tap or another suitable input 604, to transition to the next metric 606.
[0087] FIG. 7 illustrates another example where a single tap 124 activates the display 602 in the first metric. In this example, the first metric 1.0 is time. If within a period of time a double tap is received 610, a sub-data metric 1.1 can be displayed. Sub-data metric can be an additional metric that further describes or provides additional information related to the first metric. For example, sub-data metric 1.1 can be the date. Another double tap 612 can provide sub metric 1.2 which can be a calendar. Another double tap 614 can provide another sub metric 1.3, which can be sunrise metrics. A single tap 616 can then provide the next metric 2.0, which will define the metric data 617 associated with that next metric. Accordingly, it should be understood that a specific metric can have additional information (e.g., multiple levels of information or formats) that relate to that same metric, and that additional information can be provided by additional screen displays of metric data that relate to one of the metrics.
[0088] FIG. 8 illustrates an example of a double tap physical contact 124 acting to initiate the display 602 with the first metric 1.0. A single tap 620 can then expose or present sub-data 1.1, single tap 622 can present sub-data 1.2, single tap 624 can present sub-data 1.3. Similar to FIG. 7 , the provides additional data/information regarding a specific metric. However, in FIG. 8 , the transitions between the sub-data screens are by way of a single tap, as opposed to a double tap. Thus a double tap 626 can then expose a next metric 627, shown as metric 2.0. Metric 2.0 can also have sub-data (not shown). Another double tap 626 can then expose the next metric 630, shown as metric 3.0. Each of the various metrics organized in a scroll order can have sub-data associated therewith, if desired for the specific configuration. These examples are provided to show that physical contact input can be configured and quantified to define a specific input for traversing a specific display screen, or selecting specific metrics to show in specific screen displays.
[0089] In some embodiments, a device is provided. The device is defined in a form of a wearable wrist attachable structure. In one embodiment, the device has a housing that is at least partially constructed or formed from a plastic material. In one embodiment, the housing of the device includes an altimeter. The defines can further include a transiently visible display, or a dead-front display, a touch screen display, a monochrome display, a digital display, a color display, or combination thereof. In yet another embodiment, the device can include one or more accelerometers. In one specific example, the device can include a 3-axis accelerometer. On still another embodiment, a 3-axis accelerometer can be replaced with or replicated by use of separate accelerometers (e.g., 3 accelerometers) positioned orthogonally to each other.
[0090] FIG. 9 illustrates an example where various types of activities of users 900A-900I can be captured by activity tracking devices 100, in accordance with one embodiment of the present invention. As shown, the various types of activities can generate different types of data that can be captured by the activity tracking device 100. The data, which can be represented as motion data (or processed motion data) can be transferred 920 to a network 176 for processing and saving by a server, as described above. In one embodiment, the activity tracking device 100 can communicate to a device using a wireless connection, and the device is capable of communicating and synchronizing the captured data with an application running on the server. In one embodiment, an application running on a local device, such as a smart phone or tablet or smart watch can capture or receive data from the activity tracking device 100 and represent the tract motion data in a number of metrics.
[0091] 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.
[0092] 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.
[0093] 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.
[0094] 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.
[0095] 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.
[0096] 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 website.
[0097] 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).
[0098] 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.
[0099] 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 bio impedance of the user. Examples of the biological sensors include, without limitation, a biometric sensor, a physiological parameter sensor, a pedometer, or a combination thereof.
[0100] 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.
[0101] 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.
[0102] 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.
[0103] 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.
[0104] 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.
[0105] 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.
[0106] 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.
[0107] 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.
[0108] 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.
[0109] 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.
Claims
What is claimed is:
1. A method, comprising,
receiving motion data corresponding to first physical contact, the motion data generated by a sensor of an activity tracking device, the first physical contact being received on a touch sensitive screen mounted on a housing of the activity tracking device, the touch sensitive screen of the activity tracking device configured to display a plurality of metrics, the plurality of metrics being arranged in a pre-defined scroll order, wherein the physical contact received on the touch sensitive screen comprises one or more taps by a bare finger of a user of the activity tracking device, wherein the activity tracking device is wearable by the user and programmable by the user on a computing device associated with the user to display a pre-defined first metric from among the plurality of metrics on the touch sensitive screen;
determining, based on the motion data, that the first physical contact qualifies as a double tap input for the activity tracking device;
in response to determining that the first physical contact qualifies as the double tap input, causing the touch sensitive screen of the activity tracking device to be activated, the touch sensitive screen being configured to display, upon activation, the first metric of the plurality of metrics;
determining, based on additional motion data generated by the sensor in response to second physical contact received on the touch sensitive screen subsequent to the first physical contact, whether the second physical contact qualifies as a single tap input that is different from the double tap input;
in response to determining that the second physical contact qualifies as the single tap input, causing the first metric displayed on the touch sensitive screen to be replaced with a next one of the plurality of metrics in the scroll order that is different from the first metric to be displayed on the touch sensitive screen such that only one metric of the plurality of metrics in the scroll order is displayed at a time; and
for each subsequent physical contact that qualifies as the single tap input, causing another next one of the plurality of metrics in the scroll order to be displayed on the touch sensitive screen, the method being executed by one or more processors of the activity tracking device.
2. The method of claim 1, wherein the plurality of metrics comprises one or more of step count, floors climbed, stairs climbed, distance traveled, active minutes, or calories burned.
3. The method of claim 1, wherein the scroll order is user configurable and defines which respective ones of the plurality of metrics follow the first metric.
4. The method of claim 3, wherein the activity tracking device is associated to a user account, the user account provides access to configure the scroll order.
5. The method of claim 4, wherein the computing device is usable to access a website for the user account, the computing device is provided with one or more graphical user interfaces to configure the scroll order.
6. The method of claim 5, wherein the computing device is a portable computing device, the activity tracking device being configured to receive the scroll order from the portable computing device via a wireless connection.
7. The method of claim 4, further comprising enabling wireless communication with a portable computing device paired with the activity tracking device, the portable computing device provided with access to a website for access to the user account associated with the activity tracking device, the scroll order being stored in association with the user account, wherein the activity tracking device is configured to receive the scroll order obtained from the website by the portable computing device.
8. The method of claim 4, wherein the computing device is usable to access a website for the user account, the computing device provided with one or more graphical user interface to configure the scroll order of the plurality of metrics and to remove or add metrics to the plurality of metrics.
9. The method of claim 1, wherein the first metric is a home screen metric specified by the user of the activity tracking device, the home screen metric being initially displayed on the touch sensitive screen upon determining that the first physical contact qualifies as the double tap input.
10. The method of claim 1, further comprising,
causing the touch sensitive screen to be deactivated, subsequent to the second physical contact, when a period of time passes without further detected user input; and
causing the touch sensitive screen to be activated, after the period of time passes, and to display the first metric in response to determining that third physical contact is qualified as the double tap input.
11. The method of claim 1, further comprising, transitioning the touch sensitive screen to an off state in an absence of user input to the activity tracking device.
12. The method of claim 1, wherein the first metric comprises a time metric and one or more remaining metrics of the plurality of metrics each comprises an activity metric indicative of activity data of the user captured over time by the activity tracking device.
13. An activity tracking device configured for capture of activity data for a user, comprising,
a housing;
a screen disposed on the housing, the screen configured to display a plurality of metrics which include a time of day metric and activity metrics that characterize the activity data captured over time, the plurality of metrics being arranged in a pre-defined scroll order, wherein the activity tracking device is wearable by the user and programmable by the user on a computing device to display a pre-defined first metric from among the plurality of metrics on the screen;
a sensor disposed in the housing, the sensor configured to generate motion data in response to physical contact upon the housing; and
one or more processors configured to:
receive first motion data corresponding to first physical contact, the first motion data generated by the sensor in response to the first physical contact received upon the housing of the activity tracking device,
determine, based on the first motion data, that the first physical contact qualifies as a double tap input,
in response to determining that the first physical contact qualifies as the double tap input, cause the screen to be activated and to display, upon activation, the first metric of the plurality of metrics, and
determine, based on second motion data generated by the sensor in response to second physical contact received upon the housing subsequent to the first physical contact, whether the second physical contact qualifies as a single tap input that is different from the double tap input, and
in response to determining that the second physical contact qualifies as the single tap input, cause the first metric displayed on the screen to be replaced with a next one of the plurality of metrics in the scroll order that is different from the first metric to be displayed on the screen such that only one metric of the plurality of metrics in the scroll order is displayed at a time; and
for each subsequent physical contact that qualifies as the single tap input, cause another next one of the plurality of metrics in the scroll order to be displayed on the screen.
14. The activity tracking device of claim 13, wherein the housing is part of a wearable wrist attachable structure, or an attachable structure that can be carried or worn by the user of the activity tracking device.
15. The activity tracking device of claim 13, wherein the physical contact produces motion that is captured by the sensor, and the physical contact is received from a finger or hand.
16. The activity tracking device of claim 13, further comprising one or both of an altimeter and an accelerometer.
17. The activity tracking device of claim 13, wherein the housing further includes a memory for storing the activity data, captured data, and also includes wireless communication logic, and the wireless communication logic includes one of WiFi processing logic, or Bluetooth (BT) processing logic, or radio processing logic.
18. The activity tracking device of claim 17, wherein the wireless communication logic is configured to pair with a portable computing device or a computer, and the portable computing device or the computer is configured for communication over the Internet with a server, the server having processing instructions for configuring the scroll order of the plurality of metrics, or removing metrics from, or adding metrics to, the plurality of metrics.
19. The activity tracking device of claim 13, wherein the one or more processors are further configured to examine motion profiles captured by the sensor to determine whether the physical contact qualifies as the double tap input or the single tap input.
20. The activity tracking device of claim 13, wherein the plurality of metrics comprises one or more of step count, floors climbed, stairs climbed, distance traveled, active minutes, or calories burned.
21. The activity tracking device of claim 13, wherein the scroll order is user configurable and defines which respective ones of the plurality of metrics follow the first metric.
Patent Citations (361)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US2717736(A) | 1955-09-01 | Schlesinger | Applicant |
| US2827309(A) | 1958-03-01 | Fred | Applicant |
| US2883255(A) | 1959-04-01 | Anderson | Applicant |
| US3163856(A) | 1964-12-01 | Kirby | Applicant |
| US3250270(A) | 1966-05-01 | Walter | Applicant |
| US3522383(A) | 1970-07-01 | Chang | Applicant |
| US3918658(A) | 1975-11-01 | Beller | Applicant |
| US4192000(A) | 1980-03-01 | Lipsey | Applicant |
| US4244020(A) | 1981-01-01 | Ratcliff | Applicant |
| US4281663(A) | 1981-08-01 | Pringle | Applicant |
| US4284849(A) | 1981-08-01 | Anderson et al. | Applicant |
| US4312358(A) | 1982-01-01 | Barney | Applicant |
| US4367752(A) | 1983-01-01 | Jimenez et al. | Applicant |
| US4390922(A) | 1983-06-01 | Pelliccia | Applicant |
| US4407295(A) | 1983-10-01 | Steuer et al. | Applicant |
| US4425921(A) | 1984-01-01 | Fujisaki et al. | Applicant |
| US4575804(A) | 1986-03-01 | Ratcliff | Applicant |
| US4578769(A) | 1986-03-01 | Frederick | Applicant |
| US4617525(A) | 1986-10-01 | Lloyd | Applicant |
| US4887249(A) | 1989-12-01 | Thinesen | Applicant |
| US4977509(A) | 1990-12-01 | Pitchford et al. | Applicant |
| US5058427(A) | 1991-10-01 | Brandt | Applicant |
| US5224059(A) | 1993-06-01 | Nitta et al. | Applicant |
| US5295085(A) | 1994-03-01 | Hoffacker | Applicant |
| US5323650(A) | 1994-06-01 | Fullen et al. | Applicant |
| US5446705(A) | 1995-08-01 | Haas et al. | Applicant |
| US5456648(A) | 1995-10-01 | Edinburg et al. | Applicant |
| US5553296(A) | 1996-09-01 | Forrest et al. | Applicant |
| US5583776(A) | 1996-12-01 | Levi et al. | Applicant |
| US5645509(A) | 1997-07-01 | Brewer et al. | Applicant |
| US5671162(A) | 1997-09-01 | Werbin | Applicant |
| US5704350(A) | 1998-01-01 | Williams, III | Applicant |
| US5724265(A) | 1998-03-01 | Hutchings | Applicant |
| US5890128(A) | 1999-03-01 | Diaz et al. | Applicant |
| US5891042(A) | 1999-04-01 | Sham et al. | Applicant |
| US5894454(A) | 1999-04-01 | Kondo | Applicant |
| US5899963(A) | 1999-05-01 | Hutchings | Applicant |
| US5947868(A) | 1999-09-01 | Dugan | Applicant |
| US5955667(A) | 1999-09-01 | Fyfe | Applicant |
| US5976083(A) | 1999-11-01 | Richardson et al. | Applicant |
| US6018705(A) | 2000-01-01 | Gaudet et al. | Applicant |
| US6077193(A) | 2000-06-01 | Buhler et al. | Applicant |
| US6085248(A) | 2000-07-01 | Sambamurthy et al. | Applicant |
| US6129686(A) | 2000-10-01 | Friedman | Applicant |
| US6145389(A) | 2000-11-01 | Ebeling et al. | Applicant |
| US6183425(B1) | 2001-02-01 | Whalen et al. | Applicant |
| US6213872(B1) | 2001-04-01 | Harada et al. | Applicant |
| US6241684(B1) | 2001-06-01 | Amano et al. | Applicant |
| US6287262(B1) | 2001-09-01 | Amano et al. | Applicant |
| US6301964(B1) | 2001-10-01 | Fyfe et al. | Applicant |
| US6302789(B2) | 2001-10-01 | Harada et al. | Applicant |
| US6305221(B1) | 2001-10-01 | Hutchings | Applicant |
| US6309360(B1) | 2001-10-01 | Mault | Applicant |
| US6469639(B2) | 2002-10-01 | Tanenhaus et al. | Applicant |
| US6478736(B1) | 2002-11-01 | Mault | Applicant |
| US6513381(B2) | 2003-02-01 | Fyfe et al. | Applicant |
| US6513532(B2) | 2003-02-01 | Mault et al. | Applicant |
| US6527711(B1) | 2003-03-01 | Stivoric et al. | Applicant |
| US6529827(B1) | 2003-03-01 | Beason et al. | Applicant |
| US6558335(B1) | 2003-05-01 | Thede | Applicant |
| US6561951(B2) | 2003-05-01 | Cannon et al. | Applicant |
| US6571200(B1) | 2003-05-01 | Mault | Applicant |
| US6585622(B1) | 2003-07-01 | Shum et al. | Applicant |
| US6607493(B2) | 2003-08-01 | Song | Applicant |
| US6620078(B2) | 2003-09-01 | Pfeffer | Applicant |
| US6678629(B2) | 2004-01-01 | Tsuji | Applicant |
| US6699188(B2) | 2004-03-01 | Wessel | Applicant |
| US6761064(B2) | 2004-07-01 | Tsuji | Applicant |
| US6790178(B1) | 2004-09-01 | Mault et al. | Applicant |
| US6808473(B2) | 2004-10-01 | Hisano et al. | Applicant |
| US6811516(B1) | 2004-11-01 | Dugan | Applicant |
| US6813582(B2) | 2004-11-01 | Levi et al. | Applicant |
| US6813931(B2) | 2004-11-01 | Yadav et al. | Applicant |
| US6856938(B2) | 2005-02-01 | Kurtz | Applicant |
| US6862575(B1) | 2005-03-01 | Anttila et al. | Applicant |
| US7041032(B1) | 2006-05-01 | Calvano | Applicant |
| US7062225(B2) | 2006-06-01 | White | Applicant |
| US7133690(B2) | 2006-11-01 | Ranta-Aho et al. | Applicant |
| US7162368(B2) | 2007-01-01 | Levi et al. | Applicant |
| US7171331(B2) | 2007-01-01 | Vock et al. | Applicant |
| US7200517(B2) | 2007-04-01 | Darley et al. | Applicant |
| US7246033(B1) | 2007-07-01 | Kudo | Applicant |
| US7261690(B2) | 2007-08-01 | Teller et al. | Applicant |
| US7272982(B2) | 2007-09-01 | Neuhauser et al. | Applicant |
| US7285090(B2) | 2007-10-01 | Stivoric | Examiner |
| US7373820(B1) | 2008-05-01 | James | Applicant |
| US7443292(B2) | 2008-10-01 | Jensen et al. | Applicant |
| US7457724(B2) | 2008-11-01 | Vock et al. | Applicant |
| US7467060(B2) | 2008-12-01 | Kulach et al. | Applicant |
| US7502643(B2) | 2009-03-01 | Farringdon et al. | Applicant |
| US7505865(B2) | 2009-03-01 | Ohkubo et al. | Applicant |
| US7539532(B2) | 2009-05-01 | Tran | Applicant |
| US7558622(B2) | 2009-07-01 | Tran | Applicant |
| US7559877(B2) | 2009-07-01 | Parks et al. | Applicant |
| US7653508(B1) | 2010-01-01 | Kahn et al. | Applicant |
| US7690556(B1) | 2010-04-01 | Kahn et al. | Applicant |
| US7713173(B2) | 2010-05-01 | Shin et al. | Applicant |
| US7762952(B2) | 2010-07-01 | Lee et al. | Applicant |
| US7771320(B2) | 2010-08-01 | Riley et al. | Applicant |
| US7774156(B2) | 2010-08-01 | Niva et al. | Applicant |
| US7789802(B2) | 2010-09-01 | Lee et al. | Applicant |
| US7805150(B2) | 2010-09-01 | Graham | Applicant |
| US7881902(B1) | 2011-02-01 | Kahn et al. | Applicant |
| US7927253(B2) | 2011-04-01 | Vincent et al. | Applicant |
| US7983876(B2) | 2011-07-01 | Vock et al. | Applicant |
| US8028443(B2) | 2011-10-01 | Case, Jr. | Applicant |
| US8055469(B2) | 2011-11-01 | Kulach et al. | Applicant |
| US8099318(B2) | 2012-01-01 | Moukas et al. | Applicant |
| US8132037(B2) | 2012-03-01 | Fehr et al. | Applicant |
| US8177260(B2) | 2012-05-01 | Tropper et al. | Applicant |
| US8180591(B2) | 2012-05-01 | Yuen et al. | Applicant |
| US8180592(B2) | 2012-05-01 | Yuen et al. | Applicant |
| US8270297(B2) | 2012-09-01 | Akasaka et al. | Applicant |
| US8311769(B2) | 2012-11-01 | Yuen et al. | Applicant |
| US8311770(B2) | 2012-11-01 | Yuen et al. | Applicant |
| US8386008(B2) | 2013-02-01 | Yuen et al. | Applicant |
| US8437980(B2) | 2013-05-01 | Yuen et al. | Applicant |
| US8462591(B1) | 2013-06-01 | Marhaben | Applicant |
| US8463576(B2) | 2013-06-01 | Yuen et al. | Applicant |
| US8463577(B2) | 2013-06-01 | Yuen et al. | Applicant |
| US8533269(B2) | 2013-09-01 | Brown | Applicant |
| US8533620(B2) | 2013-09-01 | Hoffman et al. | Applicant |
| US8543185(B2) | 2013-09-01 | Yuen et al. | Applicant |
| US8543351(B2) | 2013-09-01 | Yuen et al. | Applicant |
| US8548770(B2) | 2013-10-01 | Yuen et al. | Applicant |
| US8562489(B2) | 2013-10-01 | Burton et al. | Applicant |
| US8583402(B2) | 2013-11-01 | Yuen et al. | Applicant |
| US8597093(B2) | 2013-12-01 | Engelberg et al. | Applicant |
| US8615377(B1) | 2013-12-01 | Yuen | Applicant |
| US8634796(B2) | 2014-01-01 | Johnson | Applicant |
| US8670953(B2) | 2014-03-01 | Yuen et al. | Applicant |
| US8684900(B2) | 2014-04-01 | Tran | Applicant |
| US8690578(B1) | 2014-04-01 | Nusbaum et al. | Applicant |
| US8734296(B1) | 2014-05-01 | Brumback | Applicant |
| US8738321(B2) | 2014-05-01 | Yuen et al. | Applicant |
| US8738323(B2) | 2014-05-01 | Yuen et al. | Applicant |
| US8744803(B2) | 2014-06-01 | Park et al. | Applicant |
| US8762101(B2) | 2014-06-01 | Yuen et al. | Applicant |
| US8764651(B2) | 2014-07-01 | Tran | Applicant |
| US8847988(B2) | 2014-09-01 | Geisner et al. | Applicant |
| US8968195(B2) | 2015-03-01 | Tran | Applicant |
| US9288298(B2) | 2016-03-01 | Choudhary | Applicant |
| US9389057(B2) | 2016-07-01 | Meschter | Applicant |
| US9409052(B2) | 2016-08-01 | Werner | Applicant |
| US9420083(B2) | 2016-08-01 | Roberts | Applicant |
| US9641469(B2) | 2017-05-01 | Chaudhary et al. | Applicant |
| US9672715(B2) | 2017-06-01 | Roberts et al. | Applicant |
| US2001/0049470(A1) | 2001-12-01 | Mault | Examiner |
| US2001/0055242(A1) | 2001-12-01 | Deshmuhk et al. | Applicant |
| US2002/0013717(A1) | 2002-01-01 | Ando et al. | Applicant |
| US2002/0019585(A1) | 2002-02-01 | Dickenson | Applicant |
| US2002/0077219(A1) | 2002-06-01 | Cohen et al. | Applicant |
| US2002/0082144(A1) | 2002-06-01 | Pfeffer | Applicant |
| US2002/0087264(A1) | 2002-07-01 | Hills et al. | Applicant |
| US2002/0109600(A1) | 2002-08-01 | Mault et al. | Applicant |
| US2002/0178060(A1) | 2002-11-01 | Sheehan | Applicant |
| US2002/0198776(A1) | 2002-12-01 | Nara et al. | Applicant |
| US2003/0018523(A1) | 2003-01-01 | Rappaport et al. | Applicant |
| US2003/0050537(A1) | 2003-03-01 | Wessel | Applicant |
| US2003/0065561(A1) | 2003-04-01 | Brown et al. | Applicant |
| US2003/0131059(A1) | 2003-07-01 | Brown et al. | Applicant |
| US2004/0054497(A1) | 2004-03-01 | Kurtz | Applicant |
| US2004/0061324(A1) | 2004-04-01 | Howard | Applicant |
| US2004/0117963(A1) | 2004-06-01 | Schneider | Applicant |
| US2004/0152957(A1) | 2004-08-01 | Stivoric et al. | Applicant |
| US2004/0239497(A1) | 2004-12-01 | Schwartzman et al. | Applicant |
| US2004/0249299(A1) | 2004-12-01 | Cobb | Applicant |
| US2005/0037844(A1) | 2005-02-01 | Shum et al. | Applicant |
| US2005/0038679(A1) | 2005-02-01 | Short | Applicant |
| US2005/0054938(A1) | 2005-03-01 | Wehman et al. | Applicant |
| US2005/0102172(A1) | 2005-05-01 | Sirmans, Jr. | Applicant |
| US2005/0107723(A1) | 2005-05-01 | Wehman et al. | Applicant |
| US2005/0163056(A1) | 2005-07-01 | Ranta-Aho et al. | Applicant |
| US2005/0171410(A1) | 2005-08-01 | Hjelt et al. | Applicant |
| US2005/0228244(A1) | 2005-10-01 | Banet | Applicant |
| US2005/0228692(A1) | 2005-10-01 | Hodgdon | Applicant |
| US2005/0234742(A1) | 2005-10-01 | Hodgdon | Applicant |
| US2005/0248718(A1) | 2005-11-01 | Howell et al. | Applicant |
| US2006/0020174(A1) | 2006-01-01 | Matsumura et al. | Applicant |
| US2006/0020177(A1) | 2006-01-01 | Seo et al. | Applicant |
| US2006/0025282(A1) | 2006-02-01 | Redmann | Applicant |
| US2006/0047208(A1) | 2006-03-01 | Yoon | Applicant |
| US2006/0047447(A1) | 2006-03-01 | Brady et al. | Applicant |
| US2006/0064276(A1) | 2006-03-01 | Ren et al. | Applicant |
| US2006/0069619(A1) | 2006-03-01 | Walker et al. | Applicant |
| US2006/0089542(A1) | 2006-04-01 | Sands | Applicant |
| US2006/0111944(A1) | 2006-05-01 | Sirmans, Jr. | Applicant |
| US2006/0129436(A1) | 2006-06-01 | Short | Applicant |
| US2006/0143645(A1) | 2006-06-01 | Vock et al. | Applicant |
| US2006/0217231(A1) | 2006-09-01 | Parks et al. | Applicant |
| US2006/0247952(A1) | 2006-11-01 | Muraca | Applicant |
| US2006/0277474(A1) | 2006-12-01 | Robarts et al. | Applicant |
| US2006/0282021(A1) | 2006-12-01 | DeVaul et al. | Applicant |
| US2006/0287883(A1) | 2006-12-01 | Turgiss et al. | Applicant |
| US2007/0050715(A1) | 2007-03-01 | Behar | Applicant |
| US2007/0051369(A1) | 2007-03-01 | Choi et al. | Applicant |
| US2007/0071643(A1) | 2007-03-01 | Hall et al. | Applicant |
| US2007/0072156(A1) | 2007-03-01 | Kaufman et al. | Applicant |
| US2007/0083602(A1) | 2007-04-01 | Heggenhougen et al. | Applicant |
| US2007/0123391(A1) | 2007-05-01 | Shin et al. | Applicant |
| US2007/0136093(A1) | 2007-06-01 | Rankin et al. | Applicant |
| US2007/0146116(A1) | 2007-06-01 | Kimbrell | Applicant |
| US2007/0155277(A1) | 2007-07-01 | Amitai et al. | Applicant |
| US2007/0159926(A1) | 2007-07-01 | Prstojevich et al. | Applicant |
| US2007/0179356(A1) | 2007-08-01 | Wessel | Applicant |
| US2007/0194066(A1) | 2007-08-01 | Ishihara et al. | Applicant |
| US2007/0197920(A1) | 2007-08-01 | Adams | Applicant |
| US2007/0208544(A1) | 2007-09-01 | Kulach et al. | Applicant |
| US2007/0276271(A1) | 2007-11-01 | Chan | Applicant |
| US2008/0084823(A1) | 2008-04-01 | Akasaka et al. | Applicant |
| US2008/0093838(A1) | 2008-04-01 | Tropper et al. | Applicant |
| US2008/0096726(A1) | 2008-04-01 | Riley | Examiner |
| US2008/0097550(A1) | 2008-04-01 | Dicks et al. | Applicant |
| US2008/0114829(A1) | 2008-05-01 | Button et al. | Applicant |
| US2008/0125288(A1) | 2008-05-01 | Case | Applicant |
| US2008/0129457(A1) | 2008-06-01 | Ritter et al. | Applicant |
| US2008/0134102(A1) | 2008-06-01 | Movold et al. | Applicant |
| US2008/0140163(A1) | 2008-06-01 | Keacher et al. | Applicant |
| US2008/0140338(A1) | 2008-06-01 | No et al. | Applicant |
| US2008/0146892(A1) | 2008-06-01 | LeBoeuf et al. | Applicant |
| US2008/0155077(A1) | 2008-06-01 | James | Applicant |
| US2008/0176655(A1) | 2008-07-01 | James et al. | Applicant |
| US2008/0287751(A1) | 2008-11-01 | Stivoric et al. | Applicant |
| US2009/0018797(A1) | 2009-01-01 | Kasama et al. | Applicant |
| US2009/0043531(A1) | 2009-02-01 | Kahn et al. | Applicant |
| US2009/0047645(A1) | 2009-02-01 | Dibenedetto et al. | Applicant |
| US2009/0048044(A1) | 2009-02-01 | Oleson et al. | Applicant |
| US2009/0054737(A1) | 2009-02-01 | Magar et al. | Applicant |
| US2009/0063193(A1) | 2009-03-01 | Barton et al. | Applicant |
| US2009/0085865(A1) | 2009-04-01 | Fattah | Examiner |
| US2009/0098821(A1) | 2009-04-01 | Shinya | Applicant |
| US2009/0150178(A1) | 2009-06-01 | Sutton et al. | Applicant |
| US2009/0156172(A1) | 2009-06-01 | Chan | Applicant |
| US2009/0171788(A1) | 2009-07-01 | Trooper et al. | Applicant |
| US2009/0184849(A1) | 2009-07-01 | Nasiri | Examiner |
| US2009/0195350(A1) | 2009-08-01 | Tsern et al. | Applicant |
| US2009/0262088(A1) | 2009-10-01 | Moll-Carrillo et al. | Applicant |
| US2009/0264713(A1) | 2009-10-01 | Van Loenen et al. | Applicant |
| US2009/0271147(A1) | 2009-10-01 | Sugai | Applicant |
| US2009/0287921(A1) | 2009-11-01 | Zhu et al. | Applicant |
| US2009/0307517(A1) | 2009-12-01 | Fehr et al. | Applicant |
| US2009/0309742(A1) | 2009-12-01 | Alexander et al. | Applicant |
| US2010/0059561(A1) | 2010-03-01 | Ellis et al. | Applicant |
| US2010/0069203(A1) | 2010-03-01 | Kawaguchi et al. | Applicant |
| US2010/0159709(A1) | 2010-06-01 | Kotani et al. | Applicant |
| US2010/0167783(A1) | 2010-07-01 | Alameh et al. | Applicant |
| US2010/0185064(A1) | 2010-07-01 | Bandic et al. | Applicant |
| US2010/0205541(A1) | 2010-08-01 | Rapaport et al. | Applicant |
| US2010/0217099(A1) | 2010-08-01 | LeBoeuf et al. | Applicant |
| US2010/0240458(A1) | 2010-09-01 | Gaiba | Examiner |
| US2010/0261987(A1) | 2010-10-01 | Kamath | Applicant |
| US2010/0331145(A1) | 2010-12-01 | Lakovic et al. | Applicant |
| US2011/0003665(A1) | 2011-01-01 | Burton et al. | Applicant |
| US2011/0009051(A1) | 2011-01-01 | Khedouri et al. | Applicant |
| US2011/0022349(A1) | 2011-01-01 | Stirling et al. | Applicant |
| US2011/0080349(A1) | 2011-04-01 | Holbein et al. | Applicant |
| US2011/0087076(A1) | 2011-04-01 | Brynelsen et al. | Applicant |
| US2011/0106449(A1) | 2011-05-01 | Chowdhary et al. | Applicant |
| US2011/0131005(A1) | 2011-06-01 | Ueshima et al. | Applicant |
| US2011/0193704(A1) | 2011-08-01 | Harper et al. | Applicant |
| US2011/0197157(A1) | 2011-08-01 | Hoffman et al. | Applicant |
| US2011/0224508(A1) | 2011-09-01 | Moon | Applicant |
| US2011/0230729(A1) | 2011-09-01 | Shirasaki et al. | Applicant |
| US2011/0242043(A1) | 2011-10-01 | Yarvis | Examiner |
| US2011/0261079(A1) | 2011-10-01 | Ingrassia, Jr. | Examiner |
| US2012/0015778(A1) | 2012-01-01 | Lee | Applicant |
| US2012/0015779(A1) | 2012-01-01 | Powch | Examiner |
| US2012/0072165(A1) | 2012-03-01 | Jallon | Applicant |
| US2012/0083705(A1) | 2012-04-01 | Yuen et al. | Applicant |
| US2012/0083714(A1) | 2012-04-01 | Yuen et al. | Applicant |
| US2012/0083715(A1) | 2012-04-01 | Yuen et al. | Applicant |
| US2012/0083716(A1) | 2012-04-01 | Yuen et al. | Applicant |
| US2012/0084053(A1) | 2012-04-01 | Yuen et al. | Applicant |
| US2012/0084054(A1) | 2012-04-01 | Yuen et al. | Applicant |
| US2012/0092157(A1) | 2012-04-01 | Tran | Applicant |
| US2012/0094649(A1) | 2012-04-01 | Porrati et al. | Applicant |
| US2012/0119911(A1) | 2012-05-01 | Jeon et al. | Applicant |
| US2012/0165684(A1) | 2012-06-01 | Sholder | Applicant |
| US2012/0166257(A1) | 2012-06-01 | Shiragami et al. | Applicant |
| US2012/0183939(A1) | 2012-07-01 | Aragones et al. | Applicant |
| US2012/0197986(A1) | 2012-08-01 | Chen | Applicant |
| US2012/0226471(A1) | 2012-09-01 | Yuen et al. | Applicant |
| US2012/0226472(A1) | 2012-09-01 | Yuen et al. | Applicant |
| US2012/0227737(A1) | 2012-09-01 | Mastrototaro et al. | Applicant |
| US2012/0265480(A1) | 2012-10-01 | Oshima | Applicant |
| US2012/0274508(A1) | 2012-11-01 | Brown et al. | Applicant |
| US2012/0277891(A1) | 2012-11-01 | Aragones | Applicant |
| US2012/0283855(A1) | 2012-11-01 | Hoffman | Applicant |
| US2012/0290109(A1) | 2012-11-01 | Engelberg | Applicant |
| US2012/0295676(A1) | 2012-11-01 | Ackerson | Applicant |
| US2012/0316456(A1) | 2012-12-01 | Rahman et al. | Applicant |
| US2012/0324226(A1) | 2012-12-01 | Bichsel et al. | Applicant |
| US2012/0330109(A1) | 2012-12-01 | Tran | Applicant |
| US2013/0006718(A1) | 2013-01-01 | Nielsen et al. | Applicant |
| US2013/0041590(A1) | 2013-02-01 | Burich et al. | Applicant |
| US2013/0072169(A1) | 2013-03-01 | Ross et al. | Applicant |
| US2013/0073254(A1) | 2013-03-01 | Yuen et al. | Applicant |
| US2013/0073255(A1) | 2013-03-01 | Yuen et al. | Applicant |
| US2013/0080113(A1) | 2013-03-01 | Yuen et al. | Applicant |
| US2013/0095459(A1) | 2013-04-01 | Tran | Applicant |
| US2013/0096843(A1) | 2013-04-01 | Yuen et al. | Applicant |
| US2013/0106684(A1) | 2013-05-01 | Weast et al. | Applicant |
| US2013/0151196(A1) | 2013-06-01 | Yuen et al. | Applicant |
| US2013/0158369(A1) | 2013-06-01 | Yuen et al. | Applicant |
| US2013/0166048(A1) | 2013-06-01 | Werner et al. | Applicant |
| US2013/0190903(A1) | 2013-07-01 | Balakrishnan et al. | Applicant |
| US2013/0191034(A1) | 2013-07-01 | Weast et al. | Applicant |
| US2013/0203475(A1) | 2013-08-01 | Kil | Applicant |
| US2013/0228063(A1) | 2013-09-01 | Turner | Applicant |
| US2013/0231574(A1) | 2013-09-01 | Tran | Applicant |
| US2013/0238287(A1) | 2013-09-01 | Hoffman et al. | Applicant |
| US2013/0261475(A1) | 2013-10-01 | Mochizuki | Applicant |
| US2013/0267249(A1) | 2013-10-01 | Rosenberg | Applicant |
| US2013/0268199(A1) | 2013-10-01 | Nielsen et al. | Applicant |
| US2013/0268236(A1) | 2013-10-01 | Yuen et al. | Applicant |
| US2013/0268687(A1) | 2013-10-01 | Schrecker | Applicant |
| US2013/0274904(A1) | 2013-10-01 | Coza et al. | Applicant |
| US2013/0289366(A1) | 2013-10-01 | Chua et al. | Applicant |
| US2013/0296666(A1) | 2013-11-01 | Kumar et al. | Applicant |
| US2013/0296672(A1) | 2013-11-01 | O'Neil et al. | Applicant |
| US2013/0296673(A1) | 2013-11-01 | Thaveeprungsriporn et al. | Applicant |
| US2013/0310896(A1) | 2013-11-01 | Mass | Applicant |
| US2013/0325396(A1) | 2013-12-01 | Yuen et al. | Applicant |
| US2013/0337974(A1) | 2013-12-01 | Yanev et al. | Applicant |
| US2014/0035761(A1) | 2014-02-01 | Burton et al. | Applicant |
| US2014/0039804(A1) | 2014-02-01 | Park et al. | Applicant |
| US2014/0039840(A1) | 2014-02-01 | Yuen et al. | Applicant |
| US2014/0039841(A1) | 2014-02-01 | Yuen et al. | Applicant |
| US2014/0052280(A1) | 2014-02-01 | Yuen et al. | Applicant |
| US2014/0067278(A1) | 2014-03-01 | Yuen et al. | Applicant |
| US2014/0077673(A1) | 2014-03-01 | Garg et al. | Applicant |
| US2014/0081667(A1) | 2014-03-01 | Joao | Applicant |
| US2014/0094941(A1) | 2014-04-01 | Ellis et al. | Applicant |
| US2014/0125618(A1) | 2014-05-01 | Panther et al. | Applicant |
| US2014/0164611(A1) | 2014-06-01 | Molettiere et al. | Applicant |
| US2014/0213858(A1) | 2014-07-01 | Presura et al. | Applicant |
| US2014/0249393(A1) | 2014-09-01 | Proud | Applicant |
| US2014/0275885(A1) | 2014-09-01 | Isaacson et al. | Applicant |
| US2014/0278229(A1) | 2014-09-01 | Hong et al. | Applicant |
| US2014/0316305(A1) | 2014-10-01 | Venkatraman et al. | Applicant |
| US2015/0026647(A1) | 2015-01-01 | Park et al. | Applicant |
| US2015/0081465(A1) | 2015-03-01 | Dyment | Applicant |
| US2015/0181314(A1) | 2015-06-01 | Swanson | Applicant |
| US2015/0262499(A1) | 2015-09-01 | Wicka | Applicant |
| US2017/0237694(A1) | 2017-08-01 | Choudhary | Applicant |
| US2017/0270765(A1) | 2017-09-01 | Roberts | Applicant |
| CN100998921 | 2007-07-01 | Applicant | |
| CN101380252 | 2009-03-01 | Applicant | |
| CN102598086 | 2012-07-01 | Applicant | |
| JP11-347021 | 1999-12-01 | Applicant | |
| RU2178588 | 2002-01-01 | Applicant | |
| WO2/011019 | 2002-02-01 | Applicant | |
| WO6/055125 | 2006-05-01 | Applicant | |
| WO6/090197 | 2006-08-01 | Applicant | |
| WO8/038141 | 2008-04-01 | Applicant | |
| WO9/042965 | 2009-04-01 | Applicant | |
| WO12/170586 | 2012-12-01 | Applicant | |
| WO12/170924 | 2012-12-01 | Applicant | |
| WO12/171032 | 2012-12-01 | Applicant | |
| WO15/127067 | 2015-08-01 | Applicant | |
| WO16/003269 | 2016-01-01 | Applicant |
Non-Patent Literature (21)
- 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.Applicant
- Fang et al., Dec. 2005, Design of a Wireless Assisted Pedestrian Dead Reckoning System—The NavMote Experience, IEEE Transactions on Instrumentation and Measurement, 54(6):2342-2358.Applicant
- Godfrey et al., 2008, Direct Measurement of Human Movement by Accelerometry, Medical Engineering & Physics, 30:1364-1386.Applicant
- Godha et al., May 2008, Foot Mounted Inertia System for Pedestrian Naviation, Measurement Science and Technology, 19(7):1-9.Applicant
- Intersema App., Using MS5534 for altimeters and barometers, Note AN501, Jan. 2006.Applicant
- Ladetto et al., Sep. 2000, On Foot Navigation: When GPS alone is not Enough, Journal of Navigation, 53(2):279-285.Applicant
- Lammel et al., Sep. 2009, Indoor Navigation with MEMS Sensors, Proceedings of the Eurosensors XIII conference, 1(1):532-535.Applicant
- 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.Applicant
- Lester et al., 2009, Validated caloric expenditure estimation using a single body-worn sensor, Proc. of the Int'l Conf. on Ubiquitous Computing, pp. 225-234.Applicant
- 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.Applicant
- Parkka et al., Jan. 2006, Activity Classification Using Realistic Data From Wearable Sensors, IEEE Transactions on Information Technology in Biomedicine, 10(1):119-128.Applicant
- Perrin et al., 2000, Improvement of Walking Speed Prediction by Accelerometry and Altimetry, Validated by Satellite Positioning, Medical & Biological Engineering & Computing, 38:164-168.Applicant
- Retscher, 2006, An Intelligent Multi-Sensor system for Pedestrian Navigation, Journal of Global Positioning Systems, 5(1):110-118.Applicant
- SCP 1000-D01/D11 Pressure Sensor as Barometer and Altimeter, VTI Technologies Application, Jun. 2006, Note 33.Applicant
- 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.Applicant
- Suunto LUMI User Guide, Jun. and Sep. 1997.Applicant
- 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.Applicant
- International Search Report dated Aug. 15, 2008, in related application PCT/IB07/03617.Applicant
- 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.Applicant
- Sagawa et al., Oct. 2000, Non-restricted measurement of walking distance, IEEE Int'l Conf. on Systems, Man, and Cybernetics, 3:1847-1852.Applicant
- Specification of the Bluetooth® System, Core Package, version 4.1, Dec. 2013, vols. 0 & 1, 282 pages.Applicant