STRAIN GAUGE

TECHNICAL FIELD

[0001] The present disclosure relates to activity tracking and more particularly relates to tracking routes and activity on a bicycle or other human powered transportation vehicle.

BACKGROUND

[0002] Human powered transportation vehicles, such as bicycles, can be pedaled or otherwise powered by human riders to provide transportation. Bicycles and other human powered transportation vehicles have been gaining popularity and provide for a significant amount of leisure, commute, or commercial transportation. In fact, the number of bicyclists in cities is growing as a year-over-year trend. In some cases, it is useful or even necessary for bicyclists or bicycle owners to track commute or riding activities. This data may be useful for both for personal interests as well as the interests of city planners, automobile makers, etc.

[0003] Connected bicycle applications can provide highly valuable data to consumers and original equipment manufacturers alike. These devices rely on wireless connections and bicycle motion to properly connect over Bluetooth and to stream data to a user's mobile phone or directly to the cloud. However, using motion sensors and proximity sensors alone in at least some cases may not be sufficient to accurately tell if a rider is on his/her bicycle. BRIEF DESCRIPTION OF THE DRAWINGS

[0004] FIG. 1 is a schematic diagram illustrating an example system for collecting data for the use and routes of a human powered transportation vehicle.

[0005] FIG. 2 is a schematic block diagram illustrating an activity tracker, according to one embodiment.

[0006] FIG. 3 is a perspective top view of an activity tracker, according to one embodiment.

[0007] FIG. 4 is a perspective bottom view of an activity tracker, according to one embodiment.

[0008] FIG. 5 is a perspective view of an activity tracker with a removable portion removed, according to one embodiment.

[0009] FIG. 6 is a perspective view of a removable portion removed, according to one embodiment.

[0010] FIGS. 7A-7C illustrate views during coupling of a removable portion with a housing of an activity tracker, according to one embodiment.

[0011] FIG. 8 is a perspective view of an activity tracker mounted on a bicycle frame, according to one embodiment.

[0012] FIG. 9 is a perspective side view of an activity tracker and water bottle cage mounted on a bicycle frame, according to one embodiment.

[0013] FIG. 10 is a perspective side view of an activity tracker with integrated pedal cadence sensor mounted on a bicycle frame, according to one embodiment. [0014] FIG. 11 is a perspective exploded view of an activity tracker with integrated strain gauge, according to one embodiment.

[0015] FIG. 12 is a schematic block diagram illustrating a system for collecting data from a data collection device, according to one embodiment.

[0016] FIG. 13 is a schematic flow chart diagram illustrating a method for obtaining route information, according to one embodiment.

[0017] FIG. 14 is a schematic flow chart diagram illustrating a method for synchronizing data from a data collection device, according to one embodiment.

[0018] FIG. 15 is a block diagram illustrating an example computing device in accordance with the teachings and principles of the disclosure.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

[0019] Applicants have developed and herein present systems, methods, and devices for gathering information about routes or activity for bicycles or other human powered transportation vehicles. According to one embodiment, an activity tracker may be mounted or integrated into a bicycle for collecting data. The activity tracker may also be referred to herein as a data collection device. The activity tracker may enable connected bicycle applications and systems to provide highly valuable data to consumers and original equipment manufacturers (OEMs) alike. In one embodiment, the activity tracker uses a wireless connection and bicycle motion to properly connect over Bluetooth and stream data to a user's phone or directly to the cloud. In another embodiment, the activity tracker stores data locally and periodically synchronizes with another device or system using a cable or wireless interface. Because the activity tracker, or a portion of the activity tracker, may remain with a bicycle when it is locked or left in a public location, the activity tracker may have a discrete profile so as to not draw extra attention to limit providing an added incentive for a thief to steal the bicycle.

[0020] According to one embodiment, the activity tracker may be securely attached to a bicycle or other human transportation vehicle. In one embodiment, the activity tracker does not need to be removed from the bicycle for synchronization, data communication, or recharging. For example, the activity tracker may be rigidly attached to the bicycle using a water bottle cage having holes or secure zip ties anywhere on the frame. Locking bolts or secure zip ties may prevent a thief from taking or stealing the activity tracker. In one embodiment, the activity tracker includes a removable battery pack so that the device can be recharged without having to remove the activity tracker itself or a main portion of the activity tracker. The activity tracker or data collection device may have a wireless transceiver so that the data collected from the bicycle can be transmitted to a user's smart phone (e.g., via Bluetooth) or to a remote server (e.g., via a wireless mobile network such as a cellular network).

[0021] In one embodiment, the activity tracker includes a mounting member or mechanism for attaching or mounting the activity tracker to a bicycle or other human powered transportation vehicle. In one embodiment, the mounting member may be configured for attachment to a bicycle using standardized holes and hole spacing to match a water bottle holder. Many bicycles, as manufactured, use the same spacing and size for screw/bolt holes that can be used for mounting water bottle cages. In one embodiment, the design utilizes this common interface such that a data collection device can be installed on almost any bicycle. The activity tracker device can be installed with normal bolts or tamper-resistant bolts to limit chances that the device will be stolen. Alternatively or additionally, the activity tracker may include zip tie holes integrated into a chassis or housing of the activity tracker so that the activity tracker can be securely installed anywhere else on the bicycle (or other human powered transportation vehicle) in the absence of standardized water bottle cage holes. In one embodiment, a water bottle cage may be mounted on top of the activity tracker, thus allowing a cyclist or other rider to easily bring water bottles with them.

[0022] In one embodiment, the activity tracker comprises a removable battery. The activity tracker may include a removable portion that includes a rechargeable battery so that the rest of the activity tracker can remain on the bicycle (e.g., securely mounted) while the battery is recharged. Also, because the battery is removable, there may be no need to bring the bicycle (or the whole activity tracker or chassis/housing) to a location where an electrical outlet or charging port is available. For example, the bicycle and activity tracker may be able to remain in a bicycle storage location, such as a garage, shed, or the like, where no electrical power is available. The battery pack, or removable portion, may include or form an environmental seal with the housing or chassis of the activity tracker to protect from water, dirt, or other environmental conditions.

[0023] In one embodiment, the removable portion includes electrodes for providing selective electrical communication between the battery and a remaining portion of the activity tracker. Similarly, the electrodes may selectively establish electrical

communication with a battery charger. In one embodiment, the electrodes may include exposed conductive surfaces, electrode posts, or the like. In one embodiment, the removable portion may include a universal serial bus (USB) port for charging the battery.

In one embodiment, a USB port, charging electrodes, or the like are surrounded by an elastomer or seal material that provides an environmental seal. The housing and removable portion may include attachment or interaction mechanisms to hold the removable portion firmly attached and against the housing to maintain the seal. Similarly, the removable portion, when attached, is held firmly so that the battery does not fall off or become electrically disconnected during riding or transportation.

[0024] According to one embodiment, an activity tracker includes a pedal cadence sensor. Cyclists, including recreational and commuter cyclists, often care about pedal cadence as they ride. Pedal cadence can be useful in measuring rider performance. In one embodiment, pedal cadence may also be useful to embedded software of an activity tracker in order to detect whether or not a rider is actively riding the bicycle (e.g., versus riding on a train or transporting a bicycle). Embodiments disclosed herein may include an activity tracker that includes a pedal sensor. With the activity tracker mounted on a frame of the bicycle (e.g., using zip ties or a water bottle holder mount) the activity tracker may provide a frame-mounted pedal proximity sensor, which resides in a main body (or housing) of a data collection device or activity tracker. A light-based or magnetic based sensor embedded in the main housing of the activity tracker may be used to detect the proximity of a pedal and thereby produce (for example) an average pedal rotation speed. Pedal rotation may also useful from an internal operation perspective. For example, the activity tracker may only track/log data when it is detected that the rider is pedaling. An activity tracker with a built-in pedal proximity sensor may allow a user to omit installation/addition of a separate pedal cadence sensor. In this case, the rider needs only install the activity tracker to meet multiple needs.

[0025] In some cases, it may be difficult for a device or activity tracker to accurately determine if a rider is on his/her bicycle. For example, if a rider is standing next to his/her bicycle on a train, then motion sensors and proximity sensors may determine that the rider is riding and proceed to connect to the device and thus collect unnecessary data (and also drain the battery). Similar problems can occur if the bicycle is on a bicycle rack attached to a car or vehicle.

[0026] Applicants have developed methods and devices for determining whether a rider is physically on a bicycle. In one embodiment, a strain gauge sensor may be located in a water-bottle cage fitted device. The sensor may include a printed circuit board (PCB) mounted strain gauge between two bolts of a water bottle cage mount (e.g., accessory device mount bosses). In one embodiment, the strain gauge measures deflections of frame tubes to accurately capture whether or not a rider is on the bicycle. For example, the weight of the rider will induce a strain on the frame tube, which can be detected in design implementations disclosed herein. No other separate cadence sensor or rider detection mechanism may be needed.

[0027] An additional challenge can include non-real time fleet management in bicycles (or other human powered transportation vehicles). As regular bicycles do not have on-board energy storage, frame mounted data collection devices often need to integrate a large battery in the design to maximize the operation time in the field. In some embodiments, collected data is temporarily stored in the device until someone manually uploads the data and clears the memory. In some cases, a fleet management organization may be required to constantly monitor the state of charge of each device, and potentially charge the battery or sync and upload data when the memory is full. However, this may require removal of the device or bringing a bicycle to a location where the charging and synchronization can occur. In some cases, using wireless communication, such as Wi-Fi or Cellular LTE, to synchronize data may present high battery consumption, and hence may add to operation overhead.

[0028] The present disclosure further presents systems and methods for fleet management using a removable battery pack. In one embodiment, a data collection device includes a microcontroller and sensors that fit a target fleet management application as well as the battery pack. In one embodiment, the removable battery pack not only features the actual battery cell, but also a large memory storage. During regular data collection for fleet management use, when the microcontroller is gathering sensor output values, the microcontroller may store the gathered values in the large memory storage in the removable battery pack. Once the energy in the removable battery pack is depleted, the removable battery pack would be removed from the bicycle and plugged in to a special intelligent battery charger. In one embodiment, this intelligent battery charger charges the battery cell and also synchronizes/uploads the data collected in the memory storage in the removable portion (in the battery pack). The removable battery pack may include a wired port connector, such as a USB connection, or a radio for wirelessly communicating the data (e.g., such as Bluetooth, Wi-Fi, or the like. The charging interface may be a physical or wireless charging interface.

[0029] As an example, a battery charger may be located in an operation office where an operator would have access to abundant electricity and an Internet connection. Hence the concern for high power consumption from wireless communication during gathering of data may not be needed, even if wireless communication is used to periodically synchronize the data. An example use case would be that at the end of each week, a fleet management operator world simply remove the removable battery pack from each bicycle and plug them in the intelligent battery charger in the operation office.

[0030] In one embodiment, the activity tracker may include electronics such as a microcontroller, a GPS receiver, an accelerometer, and/or other sensors applicable for fleet management. The electronics may include pogo pins to connect to the removable battery pack for power and data synchronization. The activity tracker may include a removable portion that includes a rechargeable battery or battery pack as well as a large data and memory storage. To recharge or upload data, an intelligent battery charger may also be used that features a battery charging circuit and data synchronization capability.

For example, the intelligent battery charge may include a USB controller to connect to a regular desktop computer or Wi-Fi adapter that can upload data collected to a particular web portal.

[0031] A removable battery pack with integrated memory may provide significant reduction in time and labor to charge the battery and collect the data from each data collection device. For example, an operator only needs to remove the battery pack (or removable portion) and put it in an intelligent battery charger, and then all the data extraction, upload, and charging could be taken care of automatically. This method provides a way for bicycle fleet management application for data collection without the need for costly cellular connection and associated data plan. Without the cellular modules on the electronics, significant power consumption may be accomplished, and battery of smaller capacity could be used or a longer operation time may be achieved. These benefits may result in significantly reduced costs and complexity for non-real time data collection for fleet management of bicycles or other human powered transportation vehicles.

[0032] The term "human powered transportation vehicle," as used herein, is given to mean any type of transportation vehicle whose movement is powered by human input. Example human powered transportation vehicles may include vehicles such as a bicycle, recumbent bicycle, tricycle, pedal powered boat, or other pedal powered vehicle.

Examples of other types of human powered transportation vehicles include scooters, skateboards, or the like. Some examples provided herein are given with respect to certain types of human powered transportation devices, such as with respect to a bicycle.

However, such examples are given by way of example only and it is contemplated within the scope of the present disclosure that examples given with respect to one type of human transportation device may be applied to other types of human transportation devices.

[0033] Further embodiments and examples will be discussed in relation to the figures below.

[0034] Turning to the figures, FIG. 1 is a schematic diagram illustrating a system 100 for obtaining, tracking, and/or storing route data, activity, data or any other data gathered for a bicycle or human powered transportation vehicle. The system 100 includes an activity tracker 102 device mounted on a human powered transportation vehicle. The activity tracker 102 may gather route data or any other information about the use, location, or riding of the human powered transportation vehicle. In one embodiment, the activity tracker 102 transmits the route data or other data for remote storage on an activity data system 104. The activity data system 104 may store and/or provide access to stored activity data. The activity data system 104 may store data in a database 106 or other data store. In one embodiment, the activity tracker 102 may transmit data to the activity data system 104 via communication node 108, such as a wireless access point, base station of a cellular communications network, or the like. The activity data system 104 may forward the data for storage via a network 110, such as the Internet.

[0035] In one embodiment, the activity tracker 102 may include a radio that is configured to communicate with a smart phone 112 or other portable communication device of a user. For example, the activity tracker 102 may transmit route data or other data to the smart phone 112, which may store the data or forward the data on to the activity data system 104. The smart phone 112 may include an application that is configured to receive, store, and/or access data. In one embodiment, the application may provide an interface for data visualization, route information, activity data, or other information about the riding activity of a user on one or more human powered transportation vehicles. For example, the application on the smart phone 112 may allow a user to access or view data stored locally on the smart phone 112 and/or data stored by the activity data system 104. In one embodiment, all data for a user, a plurality of users, a bicycle, or fleet of bicycles may be stored by the activity data system 104 for later access or analysis.

[0036] In one embodiment, the system 100 includes a synchronization station 114 and a host machine 116, such as a computing device. In one embodiment, the activity tracker may include a removable portion that includes a battery and memory. The removable portion may be removed from the activity tracker 102 while the activity tracker remains 102 attached to a bicycle or human transportation vehicle. The activity tracker 102 may store all or a portion of gathered data to the memory on the removable portion. The removable portion may be physically brought to the synchronization station

114 for charging and/or uploading of data while the human transportation vehicle stays at a different location. For example, the synchronization station 114 may include a plurality of USB ports or cables that provide power to a removable portion to charge a battery and to receive data stored on the removable portion. In one embodiment, the synchronization station 114 may include one or more wireless charging coils or pads to charge the removable portion. Similarly, synchronization via the synchronization system may take place using a wireless transceiver such as a Bluetooth or Wi-Fi radio. The data received from the removable portion may be uploaded from the synchronization station 114 to the host machine 116 and to the activity data system 104. In one embodiment, synchronization via the synchronization station 114 may be used if the activity tracker 102 does not include a radio or has not traveled with a smart phone 112 or other mobile computing device that is capable of forwarding data.

[0037] Turning to FIG. 2, a schematic block diagram is shown illustrating example components of an activity tracker 102. In the depicted embodiment, the activity tracker 102 includes a sensor component 202, a housing 204, one or more mounting members 206, a transceiver 208, a microcontroller 210, a removable portion 212, and a coupling interface 214.

[0038] The sensor component 202 obtains sensor data regarding the usage of a human powered transportation vehicle, such as a bicycle. The sensor data may include information about a route traveled by the human powered transportation vehicle, such as information about a location, path, temperature, altitude, pedal cadence, time, vibration or acceleration information, or other information gathered by one or more sensors. The sensor component 202 may store the route information or sensor data in a memory of the activity tracker 102 or sensor component 202. In one embodiment, the route information may include any type of information about the usage of a bicycle or human powered transportation vehicle on which the activity tracker 102 is mounted or with which the activity tracker 102 is traveling. For example, bicycle riders may wish to see information about distance traveled for a trip, time duration for a trip, altitude gained or lost, a map of a route, pedal cadence during riding of one or more routes, acceleration during a route, or any other information about the conditions, location, or route traveled by a rider. In one embodiment, the sensor component 202 may also detect the occurrence of events. For example, the sensor component 202 may detect events such as the presence of a rider on the human powered transportation vehicle, the beginning of a trip, the ending of a trip, or other events that occur during riding of a human powered transportation vehicle.

[0039] The sensor component 202 may include one or more sensors 216 that are used to obtain data or information about the usage or routes of a human powered transportation vehicle. In one embodiment, the sensors 216 include a positioning system receiver, such as a receiver for a global positioning system (GPS), global navigation satellite system

(GLONASS), cellular network positioning system, or any other positioning system. The positioning system receiver may be used to obtain information about a geographic location of the activity tracker 102 (and thus a corresponding human transportation device) such as latitude, longitude, altitude, or the like. In one embodiment, the sensors

216 include an accelerometer for detecting acceleration events, orientation of the human powered transportation vehicle (e.g., leaning, upright, or the like), bumps, impacts, or other changes in velocity or position of the activity tracker. In one embodiment, the sensors 216 include a thermometer for detecting a current temperature at or near the activity tracker 102. In one embodiment, the sensors 216 include a compass, such as an electronic or magnetic compass, for determining a geographic orientation or heading of the activity tracker 102. In one embodiment, the sensors 216 include a barometer for detecting a current altitude, weather condition, or the like about a current location of the activity tracker 102. In one embodiment, the sensors 216 include a humidity sensor for detecting a current humidity or weather condition at a location of the activity tracker 102.

The sensors 216 may be integrated as part of and/or within the sensor component 202 or activity tracker 102 for simplicity and robust operation. In one embodiment, one or more of the sensors 216 may be located separate from or external to the sensor component 202 and/or the activity tracker 102. For example, external sensors may communicate with and provide sensor data to the sensor component 202.

[0040] In one embodiment, the sensor component 202 includes a pedal cadence sensor 218. See FIG. 10 and associated discussion. According to one embodiment, the pedal cadence sensor 218 is integrated with the activity tracker 102 so that a separate device and/or mounting location are not needed to obtain information about pedal cadence. In one embodiment, the pedal cadence sensor 218 may include a light-based or magnetic based sensor that detects a pedal, or corresponding sensor or trigger portion on a pedal. Based on detected proximity, change in proximity, and/or cycle of detected peaks in proximity, the pedal cadence sensor 218 may calculate a pedal rotation speed. The sensor component 202 may use the pedal cadence data to determine an average pedal rate of a rider. Based on the pedal rate or the pedal cadence sensor 218, the sensor component

202 may be able to determine whether a rider is currently riding on the human powered transportation vehicle. In one embodiment, the sensor component 202 only obtains and/or stores sensor data when it detects that a rider is riding a bicycle or human powered transportation vehicle that the activity tracker 102 is riding with or mounted on.

[0041] The sensor component 202 may also include a strain gauge 224. The strain gauge 224 may be used to detect strain in a frame of a bicycle or human powered transportation vehicle. For example, strain above a certain threshold may indicate that a human is sitting on or in the human powered transportation vehicle. In one embodiment, the strain gauge 224 is in mechanical communication with a first mounting location and second mounting location of a mounting member connected to a frame. The strain gauge may detect movement of the first mounting location and the second mounting location of the mounting member relative to each other and generate a signal indicating an amount of detected strain. In one embodiment, the activity tracker includes a printed circuit board (PCB) extending between the first mounting location and the second mounting location. The strain gauge 224 may be position and/or mounted on the PCB and detects strain of the bicycle frame via based on strain of the PCB.

[0042] In one embodiment, the sensor component 202 includes a rider status component 226 configured to determine whether a bicycle is being ridden. The rider status component 226 may determine whether the bicycle (or other human powered transportation vehicle) is being ridden based on strain detected by the strain gauge 224 and/or pedal rotation detected by a pedal cadence sensor 218. For example, the rider status component 226 may determine that a rider is present based on a measured strain exceeding a threshold value. As another example, the rider status component 226 may determine that a rider is present based on a threshold pedal cadence. In one embodiment, the sensor component 202 may only log sensor data when the rider status component 226 determines that a rider is currently riding or on the vehicle. This may help reduce battery usage and/or the gathering of unneeded or irrelevant data.

[0043] The housing 204 provides a structural and/or protective cover for housing one or more components of the activity tracker 102. The housing 204 may include an exterior cover in which other components, such as the sensor component 202 and transceiver 208 are mounted or secured. The housing 204 may also provide a structural chassis on which other portions of the activity tracker 102 can be mounted, secured, or coupled to provide a rigid structural body for other components. The housing 204 may include or form one or more mounting members for securing the housing 204 and/or the activity tracker 102 to a bicycle or human powered transportation vehicle. An example housing 204 is illustrated in FIGS. 3-8.

[0044] The mounting members 206 may include mechanical shapes or features formed by a chassis, housing 204, or other portion of the activity tracker 102 for mounting or securing the activity tracker 102 to a bicycle or human powered

transportation vehicle. See, for example, FIGS. 3-4 and 8. In one embodiment, a mounting member 206 may include one or more holes or slots passing through a housing 204 or chassis of the activity tracker 102. The holes or slots may be spaced to match a bottle cage mounting location on a bicycle. For example, bicycles may include a standardized spacing, hole size, and locations for bolt holes for mounting hardware or accessories, such as a bottle cage, a holder for a pump, or the like. In embodiments where the mounting members 206 include holes or slots with a spacing to match standardized mounts, the activity tracker 102 may be easily and securely mounted to bicycles or human powered transportation vehicles with matching mounting locations. In one embodiment, a mounting member 206 may include one or more holes, slots, or grooves for receiving a zip tie for attachment to a frame of the bicycle or human powered transportation vehicle. The mounting members 206 may be integrated within the housing 204 or chassis of the activity tracker 102. Using locking or anti -tamper bolts or zip ties, the activity tracker 102 may be mounted to a bicycle or human powered transportation vehicle in a way that limits or prevents theft or unauthorized removal of the activity tracker 102.

[0045] The transceiver 208 is configured to provide wired or wireless communication between the activity tracker 102 and another computing or communication device. In one embodiment, the transceiver 208 includes a radio which may be used to communicate route data or sensor data to another device. For example, the transceiver 208 may include a radio for communicating over a cellular, wide area, or other mobile network (such as a 3GPP, WiMax, or other wireless network). In one embodiment, the transceiver 208 may be used for synchronizing or uploaded route data, sensor data, or other data gathered by the sensor component 202 for storage and/or access at a cloud location or remote storage. As another example, the transceiver 208 may include a radio for communicating with a nearby device, such as a Bluetooth, Zigbee, or other short distance communication standard. In one embodiment, the transceiver 208 is configured to communicate route data, sensor data, or other data gathered by the sensor component 202 to a smart phone or other computing device traveling with the activity tracker 102 (or a human powered transportation device with which the activity tracker 102 is traveling). The smart phone or other device may then store the data locally and/or forward the data to a remote or cloud location for storage and later access.

[0046] The microcontroller 210 may include a processor for controlling operation of the activity tracker 102. For example, the microcontroller 210 may perform processing, data storage, data access, or other functions for any of the other components of the activity tracker 102. In one embodiment, the microcontroller 210 may include a low power processor for coordinating, triggering, or performing operations on behalf of or based on the components of the activity tracker 102.

[0047] The removable portion 212 includes a portion of the activity tracker 102 that is removable from a housing 204 or chassis of the activity tracker 102. See, for example,

FIGS. 3-7. For example, the removable portion 212 may be selectively coupled or decoupled from the activity tracker 102 at a coupling interface 214. The removable portion 212 may include a battery 220 and a power/charging interface 222. The battery 220 may include a rechargeable battery or battery pack. The power/charging interface 222 may include contacts or electrode posts for providing electrical communication with the battery 220. For example, the power/charging interface 222 may interact or contact electrical surfaces or contacts on the coupling interface 214, when coupled, to power the sensor component 202, transceiver 208, microcontroller 210, and/or other components of the activity tracker 102. The power/charging interface 222 may include a physical port or contact for charging the battery 220. In one embodiment, the power/charging interface 222 includes a USB interface. In one embodiment, the power/charging interface 222 includes a wireless charging interface such as a wireless charging coil. In one

embodiment, the power/charging interface 222 may include a single interface (e.g., set of contacts) for both providing power to the sensor component 202 and receiving power for charging the battery 220. In one embodiment, the power/charging interface 222 may include two interfaces (e.g., two sets of contacts): one for providing power to the sensor component 202; and another for receiving power for charging the battery 220.

[0048] The removable portion 212 may also include memory 228. The memory 228 may include computer readable memory or storing data gathered by the sensor component 202 or other components of the activity tracker 102. In one embodiment, during gathering of data by the sensor component 202, the microcontroller 210 may store the gathered data on the memory 228.

[0049] In one embodiment, the removable portion 212 includes a communication interface 230. For example, the communication interface 230 may be used to access, upload, delete, or synchronize data in the memory 228. The communication interface 230 may provide communication between the memory 228 and a computing device when the removable portion 212 is not coupled to the housing 204. In one embodiment, the power/charging interface 222 and the communication interface 230 may be part of a single combined interface. For example, only a single cable may need to be plugged into the coupling interface to simultaneously charge the battery 220 and access the memory 228.

[0050] The removable portion 212 may also include a coupling status component 232. The coupling status component 232 may determine whether the removable portion 212 is coupled to the coupling interface 214 or is coupled to a different device, such as a synchronization station 114. In one embodiment, in response to the coupling status component 232 determining that the removable portion is coupled to the housing 204, the removable portion 212: provides electrical power from the battery 202 to the sensor component 202, or other components of the activity tracker 102; receives the route information from the sensor component 202 (or any other information gathered by the activity tracker 102); and stores the route information in the memory 228. In one embodiment, in response to determining that the removable portion is in electrical communication with the synchronization device (such as the synchronization station 114 or host system 116), the removable portion may: receive electrical power from a charging source to charge the battery 220; and provide route information or other data stored in the memory 228 to the synchronization device.

[0051] The coupling interface 214 comprises physical mechanisms and/or features for securing the removable portion 212 to the rest of the activity tracker 102. See FIGS. 5-7, which illustrate an example coupling interface 214 between a removable portion 212 and a housing 204 of an activity tracker 102. In one embodiment, the coupling interface 214 allows the removable portion 212 to be removable from the activity tracker 102 and/or the housing 204 when the housing 204 is mounted to the bicycle. For example, the mounting member 206 may not be located on the removable portion 212 so that any bolt, zip ties, or other fasteners or mechanisms used to attach the activity tracker to a bicycle or human powered transportation vehicle do not interfere with removal of the removable portion 212.

[0052] The coupling interface 214 may provide a watertight or waterproof seal for protecting electronic or electrical components of the activity tracker 102 from water, humidity, dirt, or other environmental conditions. For example, the coupling interface may provide a watertight seal that protects the power/charging interface 222 and/or the communication interface 230 from water or rain. The coupling interface 214 or the removable portion 212 may include an elastomer material that, when coupled, are pressed together to form a water tight seal around a region where the power/charging interface

222 and/or other electrical components of the removable portion 212 or coupling interface 214 are located. In one embodiment, the coupling interface 214 provides a water tight seal around electrical connectors for providing electrical communication between the removable portion 212 and components in the housing 204. In one embodiment, the coupling interface 214 provides a water tight seal around a charging port and/or data communication port on the removable portion 212 for charging the battery 220.

[0053] The components 202-232 are given by way of illustration only and may not all be included in all embodiments. In fact, some embodiments may include only one or any combination of two or more of the components 202-232. Furthermore, some of the components 202-232 may be located outside the activity tracker 102, such as within separate devices or sensors that are in communication with the activity tracker.

[0054] Turning now to FIGS 3-11, example embodiments of an appearance and configuration of an activity tracker 102 are provided. FIG. 3 is a perspective top view of an activity tracker 102. The activity tracker 102 comprises an elongated housing 204 with mounting members that form holes 302 for fastening/mounting the activity tracker 102 to an accessory mount of a bicycle or other human powered transportation vehicle. In one embodiment, the holes 302 may form a slotted or un-slotted counter sunk M5 screw boss for tolerance. For example, a slotted hole or boss may allow for accommodations in slight differences in distances between mounting locations for screws. A removable portion 212 is shown in an attached configuration to the housing 204. The activity tracker 102 also includes a power/control button 304 and a LED indicator area 306. The power/control button 304 may be used to power the activity tracker 102 on or off, trigger pairing with another device, trigger sensor data tracking, or the like. The LED indicator area 306 may provide a region where LED indicators may light up to indicate a current status of the activity tracker 102. Example statuses may include, powered on, powered off, paired, battery low, or the like.

[0055] FIG. 4 is a perspective bottom view of an activity tracker 102. The bottom end of the holes 302 is shown. Additionally, the activity tracker 102 also includes zip tie holes 402, which pass through a portion of the bottom of the housing 204. The zip tie holes 402 may allow a zip tie to pass through the zip tie holes 402 and around a frame or bar member of a bicycle or human powered transportation vehicle to secure the activity tracker 102. For example, if no water bottle mounts are available, the zip tie holes 402 may be used. The activity tracker 102 also includes elastomer ridges 404. The elastomer ridges 404 act as a rubber protector for the paint or a surface of a bicycle frame or frame of a human powered transportation vehicle. In one embodiment, the elastomer ridges 402 are part of an internal seal of the activity tracker 102 to mitigate water and dust intrusion.

[0056] FIG. 5 is a perspective view of the activity tracker 102 with the removable portion 212 removed so that it is not coupled to the housing 204. A coupling member 502 is shown that extends from the housing 204 and includes locking members 504 for engaging and locking the removable portion 212 to the housing 204. A coupling interface on the housing portion is also shown. The coupling interface includes electrical contacts 506 for connecting with a battery or other electronic component in the removable portion 212. In one embodiment, the electrical contacts 506 include pads configured to contact terminals or posts on the removable portion 212. For example, the electrical contacts 506 may include spring loaded pins or pads (such as Pogo terminals). Alternatively or additionally, a USB port or interface may be included for connecting to a corresponding USB port on the removable portion 212. The electrical contacts 506, and/or other electrical or communication ports on the housing 204, may be surrounded by a sealing material 508. The sealing material 508 may include an elastomer or other material that forms a water tight seal with the removable portion to protect the electrical contacts 506 from water or environmental conditions.

[0057] FIG. 6 is a perspective view of a removable portion 212. The removable portion 212 is shown in an uncoupled configuration where the removable portion is removed from a housing 204 or remaining portion of an activity tracker 102. The removable portion 212 includes terminals 602 in electrical communication with a battery within the removable portion 212. The terminals 602 may be sized and position to contact electrical contacts on a housing 204 (such as the electrical contacts 506 shown in FIG. 5). The terminals 602 may include spring loaded terminals (such as PoGo terminals). The terminals 602 may be used to provide power to components housed within a housing 204. The terminals 602 may be used to receive power from a power source, such as a battery charger, to replenish electrical energy within a battery. In one embodiment, the removable portion 212 includes a USB port 604. The USB port 604 may also provide electrical communication with the battery so that charging of the battery may be performed using a USB cable or port on a computing device or charging device. The USB port 604 may also provide communication to and from memory in the removable portion 212. In one embodiment, the removable portion 212 comprises a ridge or other physical portion corresponding to a seal on the housing 204 to provide a water tight seal to protect the terminals 602 and/or the USB port 604.

[0058] FIGS. 7A-7C illustrate coupling of a removable portion 212 with the housing

204, according to one embodiment. FIG. 7 A illustrates the removable portion 212 in an uncoupled state, but is resting on the coupling member 502. FIG. 7B illustrates a user, using a finger 702 to press the removable portion 212 down and toward the housing. In

FIG. 7C, the removable portion 212 is in a coupled state and locked in place by the coupling member 502. To remove a user may place their finger 702 under an edge of the removable portion (for example, at the location indicated at 704) and pry upward to unlock the removable portion from the coupling member 502. These FIGS, show the attachment mechanism for the battery pack (or removable portion). As the removable portion is installed into the main housing, it is forced forward thus pressing against the seal (see FIG. 5). The applied force around the seal may help ensure protection against water intrusion.

[0059] FIG. 8 is a perspective diagram illustrating an activity tracker 102 mounted on a frame 802 of a human powered transportation vehicle. Bolts 804 are shown securing the housing 204 to the frame 802. The removable portion 212 is removable because the bolts do not pass through the removable portion 212. In one embodiment, the bolts 804 may include tamper resistant bolts so that the housing 204 remains attached and limits an unauthorized user from removing the housing 204. The removable portion 212 may be removed from the housing 204 and frame 802 to allow a battery to be recharged and/or uploading of data or synchronization of memory.

[0060] FIG. 9 is a perspective diagram illustrating a stacked configuration for an activity tracker 102 and water bottle cage 902 on a frame 802. For example, elongated bolts that pass through both the water bottle cage 902 (or other accessory) and the activity tracker 102 may be used to secure both the water bottle cage 902 and the activity tracker 102 to the frame 802 at the same mounting location. The water bottle cage 902 holds a water bottle 904 for use by a rider. Thus, the activity tracker 102 may be used without any loss of mounting locations for use by other accessories. A removable portion 212 may still be removable even with the activity tracker 102 and/or the water bottle cage 902 mounted on the frame 802.

[0061] FIG. 10 is a perspective side view of an activity tracker 102 mounted on a frame 1002 of a human powered transportation vehicle, such as a bicycle. The activity tracker 102 includes an integrated pedal cadence sensor 1004 (which may or may not be visible externally to the activity tracker 102). The pedal cadence sensor 1004 may detect the proximity of a pedal 1006 or pedal crank arm 1008 using a light-based or magnetic- based sensor. For example, a sensor trigger may be positioned on the pedal 1006 or pedal crank arm 1008 to activate the pedal cadence sensor 1004. For example, the sensor trigger may include a magnet, a colored sticker or paint, or other material or item that can be detected by the pedal cadence sensor 1004. In one embodiment, the position of the pedal cadence sensor 1004 on or in the activity tracker 102 is configured to position the pedal cadence sensor 1004 laterally from a pedal 1006 or pedal crank arm 1008 of a bicycle. For example, accessory mounts (such as water bottle mounts) are often positioned on a vertical or angled down tube extending between a sprocket shaft and a seat post or the handle bars of a bicycle. The position of the pedal cadence sensor 1004 with respect to holes with mounting members may be configured to place the pedal cadence sensor 1004 at a location close enough (e.g., horizontally near) to the pedal 1006 or pedal crank arm 1008 to sense a magnet or other sensor trigger.

[0062] FIG. 11 is a perspective expanded view of internal parts within a housing 204 of an activity tracker 102, according to one embodiment. The expanded view shows the housing 204 separated from a chassis 1102, which may be used to mount or secure components of the activity tracker 102. The activity tracker includes a PCB 1104 for mounting, using bolts or other fasteners, to a frame of a human powered transportation vehicle, such as a bicycle. An indicator PCB 1112 may be used for mounting of LEDs, buttons, or other human interface devices to present an interface to communicate with or receive input from a user. [0063] The PCB 1104 includes holes for mounting of the activity tracker 102 and/or PCB 1104 to a frame at a first mounting location 1106 and a second mounting location 1108. For example, bolts may pass through the holes 302 of the housing 204 to secure the mounting locations 1106 and 1108 with respect to boss holes in the frame of a bicycle or other human powered transportation vehicle. A cap 1114 may be provided to protect or otherwise cover bolts or other fasteners that may be used to secure the mounting locations 1106 and 1108 with respect to boss holes in the frame of a bicycle or other human powered transportation vehicle. Thus, the PCB 1104 may be fixed relative to a frame and/or flex with a frame when a load is applied to a frame. The PCB 1104 includes a strain gauge 1110 mounted on the PCB 1104, which detects flexion or displacement of the frame based on flexion or displacement of the PCB 1104. Based on the strain, the strain gauge 1110 may provide an output signal indicating a detected amount of strain, which may be used for detecting a rider or a load on a frame of a bicycle or human powered transportation device. In one embodiment, the PCB 1104 may have other components or sensors mounted thereon. In one embodiment a separate PCB with a bus, microcontroller, or other electronic elements may be included. The detected strain may also be used to detect a roughness or smoothness of a road or pathway. For example, variations in strain may indicate the presence of bumps, rocks, pot-holes, or other damage or roughness.

[0064] FIG. 12 is a schematic block diagram illustrating a system 1200 for fleet management of one or more activity trackers 102. The system 1200 includes one or more activity trackers 102 having removable portions 212. The removable portions 212 include flash memory and a lithium ion battery, according to one embodiment. The system 1200 also includes a synchronization station 114 in communication with a host system 116. Removable portions 212 from activity trackers 102 may be removed and placed in the synchronization station 114. The synchronization station 114 may comprise a

communication interface and/or a charging interface for charging a battery and/or synchronizing data (e.g., uploading data). Power may be provided to the batteries for charging via a power bus 1202. The data may be accessed and read from the memory via a sync interface and provided to the host system 116 for storage and/or for transmission for a remote storage or access system. The synchronization station 114 may provide wired or wireless data communication and/or wired or wireless charging to the removable portions. In one embodiment, the synchronization station 114 may charge and/or sync with a plurality of removable portions 212 concurrently.

[0065] FIG. 13 is a schematic flow chart diagram for a method 1300 for activity tracking for a human powered transportation vehicle. The method 1300 includes receiving at 1302 a strain measurement from a strain gauge. The strain gauge is in mechanical communication with a mounting member comprising a first mounting location and a second mounting location sized and spaced to match bottle cage mounts on a bicycle frame of a bicycle. The method 1300 includes determining at 1304 whether the bicycle is being ridden based on the strain measurement. The method 1300 includes, in response to determining that the bicycle is being ridden, determining at 1306 bicycle route information based on information from one or more sensors.

[0066] FIG. 14 is a schematic flow chart diagram for a method 1400 for

synchronization of data from a data collection device, such as an activity tracker 102. The method 1400 includes determining at 1402, using a processor, whether a removable portion is coupled to a housing of an activity tracker for a human powered transportation vehicle. The method 1400 includes, in response to determining that the removable portion is coupled to the housing, providing at 1404 electrical power from a battery in the removable portion to a sensor component of the activity tracker. The method 1400 includes receiving at 1406 route information for the human power transportation vehicle from the sensor component. The method 1400 also includes storing at 1408 the route information in memory of the removable portion. The method 1400 includes determining at 1410 whether the removable portion is in electrical communication with a

synchronization device. The method includes, in response to determining that the removable portion is in electrical communication with the synchronization device, receiving at 1412 electrical power from a charging source to charge the battery in the removable portion. The method 1400 also includes providing at 1414 the route information from the memory to the synchronization device.

[0067] Referring now to FIG. 15, a block diagram of an example computing device 1500 is illustrated. Computing device 1500 may be used to perform various procedures, such as those discussed herein. Computing device 1500 can function as an activity tracker, server, a client, or any other computing entity. Computing device 1500 can perform various monitoring functions as discussed herein, and can execute one or more application programs, such as the application programs or functionality described herein. Computing device 1500 can be any of a wide variety of computing devices, such as a desktop computer, a notebook computer, a server computer, a handheld computer, tablet computer and the like. [0068] Computing device 1500 includes one or more processor(s) 1502, one or more memory device(s) 1504, one or more interface(s) 1506, one or more mass storage device(s) 1508, one or more Input/Output (I/O) device(s) 1510, and a display device 1530 all of which are coupled to a bus 1512. Processor(s) 1502 include one or more processors or controllers that execute instructions stored in memory device(s) 1504 and/or mass storage device(s) 1508. Processor(s) 1502 may also include various types of computer- readable media, such as cache memory.

[0069] Memory device(s) 1504 include various computer-readable media, such as volatile memory (e.g., random access memory (RAM) 1514) and/or nonvolatile memory (e.g., read-only memory (ROM) 1516). Memory device(s) 1504 may also include rewritable ROM, such as Flash memory.

[0070] Mass storage device(s) 1508 include various computer readable media, such as magnetic tapes, magnetic disks, optical disks, solid-state memory (e.g., Flash memory), and so forth. As shown in FIG. 15, a particular mass storage device is a hard disk drive 1524. Various drives may also be included in mass storage device(s) 1508 to enable reading from and/or writing to the various computer readable media. Mass storage device(s) 1508 include removable media 1526 and/or non-removable media.

[0071] I/O device(s) 1510 include various devices that allow data and/or other information to be input to or retrieved from computing device 1500. Example I/O device(s) 1510 include cursor control devices, keyboards, keypads, microphones, monitors or other display devices, speakers, printers, network interface cards, modems, and the like. [0072] Display device 1530 includes any type of device capable of displaying information to one or more users of computing device 1500. Examples of display device 1530 include a monitor, display terminal, video projection device, and the like.

[0073] Interface(s) 1506 include various interfaces that allow computing device 1500 to interact with other systems, devices, or computing environments. Example interface(s) 1506 may include any number of different network interfaces 1520, such as interfaces to local area networks (LANs), wide area networks (WANs), wireless networks, and the Internet. Other interface(s) include user interface 1518 and peripheral device interface 1522. The interface(s) 1506 may also include one or more user interface elements 1518. The interface(s) 1506 may also include one or more peripheral interfaces such as interfaces for printers, pointing devices (mice, track pad, or any suitable user interface now known to those of ordinary skill in the field, or later discovered), keyboards, and the like.

[0074] Bus 1512 allows processor(s) 1502, memory device(s) 1504, interface(s) 1506, mass storage device(s) 1508, and I/O device(s) 1510 to communicate with one another, as well as other devices or components coupled to bus 1512. Bus 1512 represents one or more of several types of bus structures, such as a system bus, PCI bus, IEEE bus, USB bus, and so forth.

[0075] For purposes of illustration, programs and other executable program components are shown herein as discrete blocks, although it is understood that such programs and components may reside at various times in different storage components of computing device 1500, and are executed by processor(s) 1502. Alternatively, the systems and procedures described herein can be implemented in hardware, or a combination of hardware, software, and/or firmware. For example, one or more application specific integrated circuits (ASICs) can be programmed to carry out one or more of the systems and procedures described herein.

Examples

[0076] The following examples pertain to further embodiments.

[0077] Example 1 is a device for detecting strain of a bicycle frame. The device includes a mounting member that includes a first mounting location and a second mounting location sized and spaced to match bottle cage mounting locations on a bicycle frame. The device includes a strain gauge configured to detect movement of the first mounting location and the second mounting location of the mounting member relative to each other.

[0078] In Example 2, the device of Example 1 further includes a PCB extending between the first mounting location and the second mounting location. The strain gauge is mounted on the PCB and detects strain of the bicycle frame via based on strain of the PCB.

[0079] In Example 3, the device as in any of Examples 1-2 further includes a rider status component configured to determine whether a bicycle is being ridden based on a strain measurement.

[0080] In Example 4, device as in any of Examples 1-3 further includes a radio configured to wirelessly communicate one or more of bicycle route information, an indication that a bicycle is being ridden, or an indication of measured strain to a remote computing device. [0081] In Example 5, the device as in any of Examples 1-4 further includes a sensor component configured to obtain bicycle route information based on information from one or more sensors, the one or more sensors including the strain gauge.

[0082] In Example 6, the sensor component in Example 5 is configured to obtain information route information from the one or more sensors based on a strain

measurement of the strain gauge.

[0083] In Example 7, the device as in any of Examples 1-6 further includes a housing comprising the mounting member, the housing enclosing at least a portion of the strain gauge, the sensor component, and a radio.

[0084] In Example 8, the mounting member as in any of Examples 1-7 includes one or more holes or slots passing through the housing and wherein the one or more holes or slots are spaced to match a bottle cage mounting location on a bicycle.

[0085] In Example 9, the device as in any of Examples 1-8 further includes one or more of a microcontroller, a positioning system receiver, an accelerometer, a

thermometer, a compass, a barometer, and a battery.

[0086] Example 10 is a method that includes receiving a strain measurement from a strain gauge. The strain gauge is in mechanical communication with a mounting member that includes a first mounting location and a second mounting location sized and spaced to match bottle cage mounts on a bicycle frame of a bicycle. The method includes determining whether the bicycle is being ridden based on the strain measurement. The method also includes, in response to determining that the bicycle is being ridden, determining bicycle route information based on information from one or more sensors. [0087] In Example 11, the method as in Example 10 further includes one or more of: transmitting, using a radio, the bicycle route information; or storing the bicycle route information in memory.

[0088] In Example 12, the bicycle route information in any of Examples 10-11 includes one or more of geographical location, accelerometer data, altitude data, speed data, direction data, temperature data, and timing data.

[0089] In Example 13, determining whether the bicycle is being ridden in any of Examples 10-12 includes determining whether the strain measurement exceeds a threshold.

[0090] Example 14 is an activity tracking device that includes a housing, a sensor component, a strain gauge, and rider status component, and a radio. The housing includes a mounting member for mounting the housing member to a frame of a human powered transportation vehicle. The sensor component is configured to obtain route information for a route travelled by the human powered transportation vehicle based on information from one or more sensors. The strain gauge is in mechanical communication with the mounting member configured to detect strain in the frame. The rider status component is configured to determine whether a human powered transportation vehicle is being ridden based on the strain. The sensor component is configured to obtain the route information in response to the rider status component determining that the human powered transportation vehicle is being ridden. The radio is configured to wirelessly communicate the route information to a remote computing device.

[0091] In Example 15, the mounting member in Example 14 includes a first mounting location and a second mounting location sized and spaced to match bottle cage mounting locations and the strain gauge is configured to detect strain by detecting movement of the first mounting location and the second mounting location of the mounting member relative to each other.

[0092] In Example 16, the first mounting location and the second mounting location in Example 15 include one or more holes or slots passing through the housing.

[0093] In Example 17, the device as in any of Examples 14-16 further includes a PCB extending between the first mounting location and the second mounting location. The strain gauge is mounted on the PCB and detects strain of the bicycle frame via based on strain of the PCB.

[0094] In Example 18, the housing as in any of Examples 14-17 houses at least a portion of one or more of the sensor component, the strain gauge, the rider status component, and the radio.

[0095] In Example 19, the device as in any of Examples 14-18 further includes one or more of a microcontroller, a positioning system receiver, an accelerometer, a

thermometer, a compass, a barometer, and a battery.

[0096] In Example 20, the sensor component as in Example 19 is configured to determine the route information based on data from one or more of the microcontroller, the positioning system receiver, the accelerometer, the thermometer, the compass, or the barometer.

[0097] Example 21 is a system or device that includes means for implementing a method, system, or device as in any of Examples 1-20.

[0098] In the above disclosure, reference has been made to the accompanying drawings, which form a part hereof, and in which is shown by way of illustration specific implementations in which the disclosure may be practiced. It is understood that other implementations may be utilized and structural changes may be made without departing from the scope of the present disclosure. References in the specification to "one embodiment," "an embodiment," "an example embodiment," etc., indicate that the embodiment described may include a particular feature, structure, or characteristic, but every embodiment may not necessarily include the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to affect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.

[0099] Implementations of the systems, devices, and methods disclosed herein may comprise or utilize a special purpose or general-purpose computer including computer hardware, such as, for example, one or more processors and system memory, as discussed herein. Implementations within the scope of the present disclosure may also include physical and other computer-readable media for carrying or storing computer-executable instructions and/or data structures. Such computer-readable media can be any available media that can be accessed by a general purpose or special purpose computer system.

Computer-readable media that store computer-executable instructions are computer storage media (devices). Computer-readable media that carry computer-executable instructions are transmission media. Thus, by way of example, and not limitation, implementations of the disclosure can comprise at least two distinctly different kinds of computer-readable media: computer storage media (devices) and transmission media. [00100] Computer storage media (devices) includes RAM, ROM, EEPROM, CD- ROM, solid state drives ("SSDs") (e.g., based on RAM), Flash memory, phase-change memory ("PCM"), other types of memory, other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store desired program code means in the form of computer-executable instructions or data structures and which can be accessed by a general purpose or special purpose computer.

[00101] An implementation of the devices, systems, and methods disclosed herein may communicate over a computer network. A "network" is defined as one or more data links that enable the transport of electronic data between computer systems and/or modules and/or other electronic devices. When information is transferred or provided over a network or another communications connection (either hardwired, wireless, or a combination of hardwired or wireless) to a computer, the computer properly views the connection as a transmission medium. Transmissions media can include a network and/or data links, which can be used to carry desired program code means in the form of computer-executable instructions or data structures and which can be accessed by a general purpose or special purpose computer. Combinations of the above should also be included within the scope of computer-readable media.

[00102] Computer-executable instructions comprise, for example, instructions and data which, when executed at a processor, cause a general purpose computer, special purpose computer, or special purpose processing device to perform a certain function or group of functions. The computer executable instructions may be, for example, binaries, intermediate format instructions such as assembly language, or even source code.

Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the described features or acts described above. Rather, the described features and acts are disclosed as example forms of implementing the claims.

[00103] Those skilled in the art will appreciate that the disclosure may be practiced in network computing environments with many types of computer system configurations, including, an in-dash vehicle computer, personal computers, desktop computers, laptop computers, message processors, hand-held devices, multi-processor systems,

microprocessor-based or programmable consumer electronics, network PCs,

minicomputers, mainframe computers, mobile telephones, PDAs, tablets, pagers, routers, switches, various storage devices, and the like. The disclosure may also be practiced in distributed system environments where local and remote computer systems, which are linked (either by hardwired data links, wireless data links, or by a combination of hardwired and wireless data links) through a network, both perform tasks. In a distributed system environment, program modules may be located in both local and remote memory storage devices.

[00104] Further, where appropriate, functions described herein can be performed in one or more of: hardware, software, firmware, digital components, or analog components. For example, one or more application specific integrated circuits (ASICs) can be programmed to carry out one or more of the systems and procedures described herein. Certain terms are used throughout the description and claims to refer to particular system components. As one skilled in the art will appreciate, components may be referred to by different names. This document does not intend to distinguish between components that differ in name, but not function.

[00105] It should be noted that the sensor embodiments discussed above may comprise computer hardware, software, firmware, or any combination thereof to perform at least a portion of their functions. For example, a sensor may include computer code configured to be executed in one or more processors, and may include hardware logic/electrical circuitry controlled by the computer code. These example devices are provided herein purposes of illustration, and are not intended to be limiting. Embodiments of the present disclosure may be implemented in further types of devices, as would be known to persons skilled in the relevant art(s).

[00106] At least some embodiments of the disclosure have been directed to computer program products comprising such logic (e.g., in the form of software) stored on any computer useable medium. Such software, when executed in one or more data processing devices, causes a device to operate as described herein.

[00107] While various embodiments of the present disclosure have been described above, it should be understood that they have been presented by way of example only, and not limitation. It will be apparent to persons skilled in the relevant art that various changes in form and detail can be made therein without departing from the spirit and scope of the disclosure. Thus, the breadth and scope of the present disclosure should not be limited by any of the above-described exemplary embodiments, but should be defined only in accordance with the following claims and their equivalents. The foregoing description has been presented for the purposes of illustration and description. It is not intended to be exhaustive or to limit the disclosure to the precise form disclosed. Many modifications and variations are possible in light of the above teaching. Further, it should be noted that any or all of the aforementioned alternate implementations may be used in any combination desired to form additional hybrid implementations of the disclosure.

[00108] Further, although specific implementations of the disclosure have been described and illustrated, the disclosure is not to be limited to the specific forms or arrangements of parts so described and illustrated. The scope of the disclosure is to be defined by the claims appended hereto, any future claims submitted here and in different applications, and their equivalents.