WO2018017100A1

WO2018017100A1 - Event tracking systems and methods

Info

Publication number: WO2018017100A1
Application number: PCT/US2016/043347
Authority: WO
Inventors: Chih-Wei Tang; Sudipto Aich; John Michael Galan FERRER
Original assignee: Ford Global Technologies, Llc
Priority date: 2016-07-21
Filing date: 2016-07-21
Publication date: 2018-01-25

Abstract

Example event tracking systems and methods are described. In one implementation, a method determines normal bicycle riding characteristics and identifies current bicycle characteristics. The method determines whether the current bicycle riding characteristics deviate from the normal bicycle riding characteristics. If the current bicycle riding characteristics deviate from the normal bicycle riding characteristics, current data is received from multiple sensors and an event record is generated. The event record is associated with the current bicycle riding characteristics and the current sensor data.

Description

EVENT TRACKING SYSTEMS AND METHODS

TECHNICAL FIELD

[0001] The present disclosure relates to systems and methods that detects and records events that occur while riding a bicycle or other vehicle.

BACKGROUND

[0002] In many areas, such as densely populated cities with heavy traffic, alternative modes of transportation are popular. For example, bikes and e-bikes (electric bicycles) are commonly used for transportation in densely populated areas. Experienced users of bikes, e- bikes, and other modes of transportation may select a route based on prior knowledge of the roads (e.g., road conditions or current road construction), expected car traffic, number of pedestrians, and road safety (e.g., dangerous intersections or locations of potential accidents).

[0003] Users of bikes, e-bikes, and other modes of transportation may experience multiple events when riding or driving on various roads. These events include rough road segments, potholes, sudden braking, swerving, tire slipping, and the like. Although a particular user may remember some of the events that occur on a bicycle ride, the user may forget those events over time or forget some of the details associated with the event.

BRIEF DESCRIPTION OF THE DRAWINGS

[0004] Non-limiting and non-exhaustive embodiments of the present disclosure are described with reference to the following figures, wherein like reference numerals refer to like parts throughout the various figures unless otherwise specified. [0005] FIG. 1 depicts an example embodiment of a system for detecting, tracking, and recording events.

[0006] FIG. 2 is a block diagram illustrating an embodiment of an event tracker.

[0007] FIG. 3 is a flow diagram depicting an embodiment of a method for detecting and recording an event.

[0008] FIG. 4 is a flow diagram depicting an embodiment of a method for automatically detecting an event associated with a bicycle.

[0009] FIG. 5 depicts an embodiment of an event record generated by an event tracker.

[0010] FIG. 6 is a flow diagram depicting an embodiment of a method for identifying event records related to a planned bicycle ride.

[0011] FIG. 7 is a block diagram depicting an embodiment of a computing device.

DETAILED DESCRIPTION

[0012] In the following disclosure, reference is 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.

[0013] 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.

[0014] 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.

[0015] 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.

[0016] 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 is 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 herein. Rather, the described features and acts are disclosed as example forms of implementing the claims.

[0017] 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.

[0018] 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.

[0019] It should be noted that the sensor embodiments discussed herein 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).

[0020] At least some embodiments of the disclosure are 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. [0021] The event tracking systems and methods discussed herein automatically detect events during a bicycle ride. The described systems and methods also allow a user (e.g., a rider of the bicycle) to manually identify an event using a button or other activation device mounted to the bicycle. The terms "bike" and "bicycle" are used interchangeably herein. Although particular examples refer to a bicycle, the systems and methods discussed herein are applicable to any type of vehicle such as motorcycles, scooters, cars, trucks, buses, and the like.

Additionally, specific embodiments may be used by pedestrians, runners, and so forth.

[0022] As used herein, an "event" refers to any activity, condition, occurrence or situation associated with a bicycle (or other vehicle) or the environment in which the bicycle is operating. Example events include, but are not limited to, road conditions (e.g., potholes, obstacles, road construction, poor street lighting, bad bike lane markings (or lack of bike lane markings)), heavy vehicle traffic, heavy pedestrian traffic, dangerous intersections, accidents, potential accidents, sudden braking of the bicycle, swerving of the bicycle, sudden acceleration of the bicycle, bicycle tire slippage, and the like.

[0023] FIG. 1 depicts an example embodiment of a system 100 for detecting, tracking, and recording events. System 100 includes a bicycle 102 and an event tracker 104 mounted on bicycle 102. As discussed herein, event tracker 104 automatically detects and records events that occur while riding bicycle 102. In some embodiments, event tracker 104 includes a button (or switch) 106 that is activated by a user (e.g., a rider of bicycle 102) to manually identify an event. In some embodiments, button 106 is a mechanical button (or mechanical switch) mounted on event tracker 104. In other embodiments, button 106 is mounted on a handlebar or other easily accessible area of bicycle 102. Button 106 is any type of device capable of activation by a user to identify a particular event. Alternate embodiments of button 106 include any type of human interface device, such as sensors, touch sensors, and the like. Button 106 is positioned such that the rider of bicycle 102 can easily activate the button without diverting their attention from the road and potential obstacles in their riding path.

[0024] In some embodiments, button 106 is mounted to bicycle 102 separately from event tracker 104. For example, button 106 may be located near event tracker 104 such that button 106 can communicate wirelessly with event tracker 104. In particular embodiments, button 106 communicates wirelessly with event tracker 104 using the Bluetooth^® wireless communication system. In alternate embodiments, any communication system is used to communicate signals between button 106 and event tracker 104.

[0025] Event tracker 104 communicates with an event server 110 via a network 108. Network 108 may be a LAN (local area network), WAN (wide area network), cellular network, the Internet, or any combination of multiple wired and/or wireless networks. In some embodiments, event server 110 is located in a different geographic area than bicycle 102. Event server 110 is coupled to an event database 112 that stores, for example, event-related data. In particular implementations, event tracker 104 communicates with event server 110 (e.g., sending event data to event server 110 and retrieving event data from event server 110).

[0026] Any number of bicycles 114 (with event trackers) and users 116 can access event server 110 for storing and retrieving event-related data. For example multiple event trackers on multiple bicycles 114 can send event-related data to event server 110 for storage in event database 112. This collection of event-related data can be accessed by any number of users 116, computing devices 118, and event trackers on bicycles 114 to assist with bicycle route planning, accident avoidance while riding the bicycle, and notifications of potentially dangerous areas along a route. In some embodiments, user 116 may access event server 110 to identify potentially dangerous areas along a route and may select a different route depending on the severity of the danger. While bicycle 114 is being ridden along a route, the bicycle's event tracker may access event server 110 to identify upcoming areas where previous events occurred with different users. The event tracker can provide notification to the rider of bicycle 114 to be cautious in the upcoming area. Computing device 118 may also access event server 110 to obtain information related to stored events. Computing device 118 may be a mobile device, tablet computer, laptop computer, desktop computer, smart watch, or any other computing device.

[0027] FIG. 2 is a block diagram illustrating an embodiment of an event tracker 104. Event tracker 104 includes a communication module 202, a processor 204, and a memory 206. Communication module 202 allows event tracker 104 to communicate with other systems, such as a button 106, event server 110, other computing devices, and the like. Processor 204 executes various instructions to implement the functionality provided by event tracker 104. Memory 206 stores these instructions as well as other data used by processor 204 and other modules contained in event tracker 104.

[0028] Additionally, event tracker 104 includes a date/time module 208 that maintains (or determines) a current date and time associated with various events. A GPS (global positioning system) receiver 210 receives and decodes GPS data to identify a specific geographic location associated with an identified event. In response to identification of an event, event tracker 104 determines the current geographic location of bicycle 102 based on the GPS data and determines the current date and time. The geographic location, date, and time information is associated with the event and stored as an event record, as discussed herein. [0029] Event tracker 104 also includes an accelerometer 212, a gyroscope 214, a temperature sensor 216, a humidity sensor 218, and a barometric pressure sensor 220.

Accelerometer 212 senses changes in acceleration in bicycle 102, such as a sudden change in direction of bicycle 102 or sudden deceleration of bicycle 102. Sudden changes may indicate an accident, pothole, significant bump, or a swerve by the rider of bicycle 102 to avoid an obstacle. Gyroscope 214 senses the orientation of event tracker 104 and, therefore, the orientation of bicycle 102 to which event tracker 104 is mounted. Temperature sensor 216 senses the ambient temperature near event tracker 104. Humidity sensor 218 senses the current humidity in the area near event tracker 104. Barometric pressure sensor 220 senses the current barometric pressure near event tracker 104.

[0030] Event tracker 104 further includes an event detection module 222 that

automatically detects an event based on, for example, data from accelerometer 212 and/or gyroscope 214. If a significant change in the acceleration of bicycle 102 is detected based on the data from accelerometer 212, event detection module 222 determines that an event has occurred. Similarly if a significant (or sudden) change in the orientation of bicycle 102 is detected based on the data from gyroscope 214, event detection module 222 determines that an event has occurred. When an event is detected by event detection module 222, an event record manager 224 receives data from multiple sensors in event tracker 104 and creates an event record for the event that includes an event type, sensor data, current date and time, geographic location of the event, and the like. Event record manager 224 also manages the storage of the event record within event tracker 104 and in one or more remote event servers or other storage systems.

[0031] Event tracker 104 also includes a user interface module 226 that allows a user to interact with event tracker 104 and presents information to a user. For example, user interface module 226 may receive user commands related to a bicycle route or other activity. Additionally, user interface module 226 may present information to a user in the form of audible information, visual information, or haptic information. For example, user interface module 226 may generate an alert when bicycle 102 is approaching an area with many previous events reported by other users. This alert may indicate the types of previous events or may simply alert the rider of bicycle 102 to be more cautious as they ride through the approaching area. A battery 228 provides power to the various components and modules contained in event tracker 104.

[0032] FIG. 3 is a flow diagram depicting an embodiment of a method 300 for detecting and recording an event. Initially, an event tracker is activated at 302, such as when a user is starting a bicycle ride. The event tracker monitors various sensors (e.g., accelerometer 212 and gyroscope 214) and button 106 to detect events 304 during the bicycle ride. Upon detecting an event, the event tracker receives 306 current data from multiple sensors and, optionally, from other components. For example, upon detecting an event, event tracker may receive information related to current date and time, geographic location, accelerometer data, gyroscope data, temperature, humidity, and barometric pressure. The event tracker generates 308 an event record associated with the detected event. The event record contains some or all of the data received from the multiple sensors and other components. Additionally, the event record may include data received from systems or components external to the event tracker, such as information collected via network 108 from other servers, computing systems, or data sources.

[0033] The event record is then stored 310 in the event tracker or in a storage device associated with the event tracker. The event record is also communicated 312 to an event server (e.g., event server 1 10) for storage and sharing with other users. [0034] FIG. 4 is a flow diagram depicting an embodiment of a method 400 for automatically detecting an event associated with a bicycle. Initially, an event tracker is activated at 402. The event tracker determines 404 normal bicycle riding characteristics, such as normal ranges for accelerometer values and normal ranges for gyroscope values. For example, normal bicycle riding characteristics may include steering characteristics, lean characteristics (e.g., leaning the bicycle to the right or left), acceleration characteristics, braking characteristics, tire slipping characteristics, and the like. When accelerometer and gyroscope values are within normal ranges, the event tracker does not detect an event. The method continues by identifying 406 current bicycle characteristics (e.g., current accelerometer and gyroscope values). If any of the current bicycle characteristics deviate 408 from the normal bicycle riding characteristics, then the event tracker detects an event. For example, if the event tracker identifies a current accelerometer value outside the normal range for accelerometer values, an event is detected. Similarly, if the event tracker identifies a current gyroscope value outside the normal range for gyroscope values, an event is detected. In some embodiments, threshold values are used to define the normal ranges for accelerometer values and gyroscope values. If a current bicycle characteristic exceeds any of the threshold values, an event is detected.

[0035] In response to detecting an event (a deviation from normal bicycle riding characteristics), the event tracker receives 410 current data from multiple sensors and, optionally, other components or systems. The event tracker then generates 412 and event record associated with the current bicycle characteristics and current sensor data. The event record is stored 414 in the event tracker and communicated 416 to an event server for storage and sharing with other users. [0036] FIG. 5 depicts an embodiment of an event record 500 generated by an event tracker. A left column 502 of event record 500 identifies the type of information and a right column 504 of event record 500 identifies the data values for the particular event record. In the example of FIG. 5, the detected event was a swerve followed by hard braking. This swerve and hard braking was detected, for example, based on information received from the accelerometer and/or the gyroscope. The accelerometer values were likely outside the normal bicycle riding characteristics during the hard braking. Additionally, the gyroscope values may have been outside the normal bicycle riding characteristics during the swerve if the rider of the bicycle leaned sideways to avoid an obstacle.

[0037] In some embodiments, event record 500 may include additional data from other sources, such as external servers, computing systems, and data sources. For example, the additional data may be weather data accessed from a web site or data source containing weather information. The additional weather data may include information such as wind conditions, rain conditions, and whether the day is sunny or cloudy.

[0038] FIG. 6 is a flow diagram depicting an embodiment of a method 600 for identifying event records related to a planned bicycle ride. Initially, a user plans 602 a bicycle riding route and requests relevant event records. The request for relevant event records may be communicated to an event server, such as event server 110 discussed herein.

[0039] In the illustrated implementation, method 600 identifies 604 current weather conditions. The planned bicycle riding route and current weather conditions are communicated 606 to a remote event server, such as event server 110. The remote event server identifies 608 event records for similar riding routes and similar weather conditions. The identified event records are communicated 610 to the event tracker (or other device). For example the identified event records may be communicated to the event tracker, a user's mobile device, a laptop computer, a tablet computer, a smart watch, or any other computing device. In some

implementations, information associated with the identified event is communicated 612 to the user prior to starting the bicycle ride and at appropriate points during the route. For example, the user may receive event information on their mobile device prior to starting the bicycle ride, then receive alerts and, optionally, updates via the event tracker during the bicycle ride. As discussed herein, the alerts and/or updates received via the event tacker may be audible alerts/updates, visual alerts/updates, or haptic alerts/updates.

[0040] In some embodiments, relevant event records have related geographic areas, such as geographic areas along the user's planned bicycle ride. Additionally, relevant event records may also have a similar time of day or similar weather conditions. For example, if a user is planning a bicycle ride at 10:00am on a cool, cloudy day along a particular roadway, relevant event records are those with similar times that also occurred on a cool, cloudy day on the same roadway. Thus, if the cool conditions cause the particular roadway to be slippery in the morning, the relevant event records will likely identify at least portions of the particular roadway as being slippery during the planned bicycle ride.

[0041] FIG. 7 is a block diagram depicting an example computing device 700.

Computing device 700 may be used to perform various procedures, such as those discussed herein. Computing device 700 can function as a server (e.g., an event server), a client or any other computing entity. Computing device 700 can be any of a wide variety of computing devices, such as a desktop computer, a notebook computer, a server computer, a handheld computer, a tablet, and the like. [0042] Computing device 700 includes one or more processor(s) 702, one or more memory device(s) 704, one or more interface(s) 706, one or more mass storage device(s) 708, and one or more Input/Output (I/O) device(s) 710, all of which are coupled to a bus 712.

Processor(s) 702 include one or more processors or controllers that execute instructions stored in memory device(s) 704 and/or mass storage device(s) 708. Processor(s) 702 may also include various types of computer-readable media, such as cache memory.

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

[0044] Mass storage device(s) 708 include various computer readable media, such as magnetic tapes, magnetic disks, optical disks, solid state memory (e.g., Flash memory), and so forth. Various drives may also be included in mass storage device(s) 708 to enable reading from and/or writing to the various computer readable media. Mass storage device(s) 708 include removable media and/or non-removable media.

[0045] I/O device(s) 710 include various devices that allow data and/or other information to be input to or retrieved from computing device 700. Example I/O device(s) 710 include cursor control devices, keyboards, keypads, microphones, monitors or other display devices, speakers, printers, network interface cards, modems, lenses, CCDs or other image capture devices, and the like.

[0046] Interface(s) 706 include various interfaces that allow computing device 700 to interact with other systems, devices, or computing environments. Example interface(s) 706 include any number of different network interfaces, such as interfaces to local area networks (LANs), wide area networks (WANs), wireless networks, and the Internet.

[0047] Bus 712 allows processor(s) 702, memory device(s) 704, interface(s) 706, mass storage device(s) 708, and I/O device(s) 710 to communicate with one another, as well as other devices or components coupled to bus 712. Bus 712 represents one or more of several types of bus structures, such as a system bus, PCI bus, IEEE 1394 bus, USB bus, and so forth.

[0048] 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 700, and are executed by processor(s) 702. 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.

[0049] While various embodiments of the present disclosure are described herein, it should be understood that they are 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 described exemplary embodiments, but should be defined only in accordance with the following claims and their equivalents. The description herein is 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 disclosed teaching. Further, it should be noted that any or all of the alternate implementations discussed herein may be used combination desired to form additional hybrid implementations of the disclosure.

Claims

1. A method comprising:

determining normal bicycle riding characteristics;

identifying current bicycle characteristics;

determining whether the current bicycle riding characteristics deviate from the normal bicycle riding characteristics; and

responsive to determining that the current bicycle riding characteristics deviate from the normal bicycle riding characteristics:

receiving current sensor data from a plurality of sensors; and

generating an event record associated with the current bicycle riding characteristics and the current sensor data.

2. The method of claim 1, wherein the multiple sensors include at least one of an accelerometer, a gyroscope, a GPS receiver, a temperature sensor, a humidity sensor, and a barometric pressure sensor.

3. The method of claim 1, wherein the current bicycle characteristics include at least one of steering characteristics, lean characteristics, acceleration characteristics, and braking

characteristics.

4. The method of claim 1, further comprising communicating the event record to an event server that stores the event record.

5. The method of claim 4, wherein the event record is accessible to other users via the event server.

6. The method of claim 1, further comprising storing the event record in an event tacker.

7. The method of claim 1, wherein determining that the current bicycle characteristics deviate from the normal bicycle riding characteristics includes detecting at least one of sudden braking, swerving, sudden acceleration, and bicycle tire slipping.

8. The method of claim 1, wherein the normal bicycle riding characteristics are associated with a current rider of the bicycle.

9. The method of claim 1, wherein determining whether the current bicycle characteristics deviate from the normal bicycle riding characteristics includes determining whether the deviation exceeds a threshold value.

10. The method of claim 1, further comprising:

detecting activation of a button mounted to the bicycle; and

responsive to detecting activation of the button:

receiving current data from multiple sensors;

generating an event record associated with the current bicycle characteristics and the current sensor data.

11. The method of claim 10, wherein activation of the button indicates a user identification of an event while riding the bicycle.

12. A method comprising:

determining, by an event tracker, normal bicycle riding characteristics;

identifying, by the event tracker, current bicycle characteristics;

determining, by the event tracker, whether the current bicycle riding characteristics deviate from the normal bicycle riding characteristics; and

receiving current sensor data from at least one of an accelerometer, a gyroscope, a GPS receiver, a temperature sensor, a humidity sensor, and a barometric pressure sensor associated with the bicycle;

generating an event record associated with the current bicycle riding characteristics and the current sensor data; and

communicating the event record to an event server.

13. The method of claim 12, wherein the current bicycle characteristics include at least one of steering characteristics, lean characteristics, acceleration characteristics, and braking

characteristics.

14. The method of claim 12, wherein the event record is accessible to other users via the event server.

15. The method of claim 12, wherein determining that the current bicycle characteristics deviate from the normal bicycle riding characteristics includes detecting at least one of sudden braking, swerving, sudden acceleration, and bicycle tire slipping.

16. An event tracker associated with a bicycle, the event tracker comprising:

at least one sensor mounted to the bicycle, the sensor including at least one of an accelerometer, a gyroscope, a GPS receiver, a temperature sensor, a humidity sensor, and a barometric pressure sensor; and

an event detection module configured to:

determine normal bicycle riding characteristics;

receive current sensor data from the sensor;

identify current bicycle riding characteristics based on the current sensor data; determine whether the current bicycle riding characteristics deviate from the normal bicycle riding characteristics; and

responsive to determining that the current bicycle characteristics deviate from the normal bicycle riding characteristics, generating an event record associated with the current bicycle riding characteristics and the current sensor data.

17. The event tracker of claim 16, wherein the current bicycle riding characteristics include at least one of steering characteristics, lean characteristics, acceleration characteristics, and braking characteristics.

18. The event tracker of claim 16, further comprising a communication module that communicates the event record to an event server.

19. The event tracker of claim 18, wherein the event record is accessible to a plurality of users via the event server.

20. The event tracker of claim 16, wherein determining whether the current bicycle riding characteristics deviate from the normal bicycle riding characteristics includes detecting at least one of sudden braking, swerving, sudden acceleration, and bicycle tire slipping.