Systems and methods for monitoring and quantifying vehicle behavior

Abstract

The disclosure herein pertains to monitoring and quantifying vehicle drive behavior. In one example, a system includes a vehicle having a sensor subsystem configured to capture vehicle behavior data; a multi-command serial bus configured to format multiple vehicle behavior data inputs; a display device; and a computing device configured to calculate a trip score using the vehicle behavior data, apply points to a point total of the user profile based on the trip score, and generate and output for display on the display device a first set of redeemable products.

Description

SYSTEMS AND METHODS FOR MONITORING AND QUANTIFYING VEHICLE BEHAVIORFIELD

[0001] The disclosure relates to methods and apparatuses for a vehicle system and, in particular, monitoring and quantification of vehicle drive behaviors.BACKGROUND

[0002] Traffic is increasing worldwide due to a growing number of vehicles and demand for personal transportation. Today, owning a car is a necessity for many, especially those working in urban cities. Among the problems that arise with increased traffic is the mental stress that one experiences while trying to manage one’s way around the traffic when driving on a road. Frustration and mental stress may be caused during driving due to other incompetency of other drivers, as well as one’s own incompetency which can cause a similar mental stress to those around. Per a study conducted by University of Sharjah, UAE, presented in 9th Asia Pacific Global Summit on Healthcare & Immunolog}', traffic congestion can lead to greater emotional health effects; mostly stress (80.4%), nervousness (74.2%), and aggressiveness (52.2%).

[0003] Vehicle behavior data may be used to identify desirable behaviors that may reduce traffic, and undesirable behaviors that may increase traffic. For example, frequent lane changes, turning without use of an indicator, and quick accelerations may be undesirable behaviors. These undesirable behaviors may be difficult for other road users to predict, which may lead to increases in traffic congestion, as w ell as increases in user frustration. Desirable behaviors such as maintaining travel in a single lane and traveling at an approximate average speed may reduce traffic congestion and user stress / frustration, as vehicle behavior may be predicted and / or anticipated by other road users. In order to decrease traffic, which may reduce road user frustration and lead to further decreases in traffic, it is desirable to incentivize desirable vehicle behaviors and provide disincentives for undesirable vehicle behaviors.SUMMARY

[0004] Described herein are systems and methods for monitoring and quantifying vehicle drive behaviors. In one or more embodiments, a system comprises a vehicle having a sensor subsystem configured to capture vehicle behavior data of the vehicle; a multi-command serial bus configured as a zonal architecture that accumulates multiple vehicle behavior data inputsfrom the sensor subsystem into a daisy-chained, one-to-one architecture; a display device; and a computing device including a processor and a non-transitory memory storing executable instructions. When executed, the instructions cause the processor to: receive the vehicle behavior data that is in the daisy-chained, one-to-one architecture from the multi-command serial bus; extract behavior statistics from the vehicle behavior data; calculate atrip score using the vehicle behavior data by applying a weight to each behavior statistic of the vehicle behavior data, and subtracting weighted behavior statistics from a maximum trip score; determine a number of points, based on the trip score, to apply to a user profde and add the number of points to a point total of the user profile; and generate and output for display on the display device a first set of redeemable products, where a price of each product of the first set of redeemable products is equal to and / or less than the point total.

[0005] It should be understood that the summary above is provided to introduce in simplified form a selection of concepts that are further described in the detailed description. It is not meant to identify key or essential features of the claimed subject matter, the scope of which is defined uniquely by the claims that follow the detailed description. Furthermore, the claimed subject matter is not limited to implementations that solve any disadvantages noted above or in any part of this disclosure.BRIEF DESCRIPTION OF THE DRAWINGS

[0006] The disclosure may be better understood from reading the following description of non-limiting embodiments, with reference to the attached drawings, wherein below:

[0007] FIG. 1 shows a partial view of a cabin of a vehicle;

[0008] FIG. 2 shows a block diagram of an in-vehicle computing system of the vehicle ofFIG. 1;

[0009] FIG. 3 shows a flowchart for a method for calculating a trip score using vehicle behavior data collected during atrip of the vehicle of FIGS. 1-2;

[0010] FIG. 4 shows a flowchart for a method for updating a point total and a set of redeemable products that may be purchased using points that are awarded based on the trip score;

[0011] FIG. 5 shows a flowchart for a method for collecting vehicle behavior data that may be used to calculate the trip score;

[0012] FIG. 6 shows a first example view of a display, illustrating a summary' of vehicle behavior statistics used to calculate the trip score;

[0013] FIG. 7 shows a second example view of the display, illustrating profile information of a user;

[0014] FIG. 8 shows a third example view of the display, illustrating a first reward redemption screen;

[0015] FIG. 9 shows a fourth example view of the display, including a second reward redemption screen; and

[0016] FIG. 10 shows a fifth example view of the display, including a third reward redemption screen.DETAILED DESCRIPTION

[0017] The following description relates to systems and methods for vehicle behavior monitoring and quantification and in particular, for calculating a vehicle behavior score of the vehicle, where the vehicle behavior score quantifies actions of the vehicle. In some examples, the method includes collecting vehicle data, calculating a trip score using the vehicle data, awarding points based on the trip score, and redeeming rewards using points via a mobile application.

[0018] A trip score is calculated based on vehicle behaviors during a trip of the vehicle, where the trip score is increased by performance of desirable behaviors, such as maintaining travel in a single lane for an extended duration, and the trip score is decreased by performance of undesirable behaviors, such as turning without an indicator. The system uses information captured during a trip to determine a trip score based on various parameters. The parameters may include, for example, a number of times a driver changes lanes on a straight road, a number of times the driver turns the vehicle without using a turn indicator, an average speed of the vehicle during the trip, impulsive hard braking and / or quick acceleration, a duration for which the driver maintained the drive lane during the trip, a number of times the driver honked during the trip, and if the driver has high beams on while driving within city boundaries. Further parameters may be added to the system, such as adherence to traffic laws while driving.

[0019] Points are added to a user profile based on the trip score. Points may be redeemed to purchase products, for example, via an application accessed using a mobile application and / or website. In this way, an incentive is provided for performing desirable vehicle behaviors and for avoiding undesirable vehicle behaviors. The trip score is generated using the parameters collected during the trip, and points are awarded to the driver based on the trip score. The points may be aggregated after each trip to a total point sum of the driver linked to a profile of the driver in a mobile application. The points may be redeemed in the mobile application topurchase accessories, coupons, and / or products from a catalogue available in the mobile application. In this way. the systems and methods described herein may motivate drivers to perform desirable behaviors, such as following basic traffic laws and driving rules, as well as encourage them to drive with consideration of fellow drivers around them, using a rewardbased system.

[0020] Compared to other systems and methods for monitoring and quantifying vehicle behaviors, the systems and methods described herein provide a solution that protects data in transit, optimizes bandwidth when collecting vehicle behavior data, and prioritizes bandwidth for operational components of the vehicle. Vehicle behavior data may be securely published to a cloud server, where the vehicle behavior data is processed, stored, and archived. A multilevel approach is used to protect data in transit, including physical layer and network layer encryption. A zonal architecture may be used to manage simultaneously receiving multiple vehicle behavior data inputs, as well as vehicle operational commands. For example, vehicle behavior data may be tagged with a low priority indicator, and vehicle operational data (e.g., brake commands) may be tagged with a high priority indicator.

[0021] The methods described herein may incentivize increases in driver awareness and driver competency, and motivate drivers to follow traffic laws and driving rules, but also drive in a way which can increase satisfaction in the driving on-road experience with a reward-based system. One of the prime reasons for road-rage, and mental stress during driving, is that people are frustrated with driving from those around them that includes undesirable vehicle behaviors. The methods described herein de-motivate undesirable vehicle behaviors and rewards drivers with points for performing desirable vehicle behaviors, and for following traffic laws and driving rules. The system may also reduce the mental stress and frustration of a driver due to haphazard traffic, attempts to inculcate a culture of sensible driving, and reduce instances of road-rage. Additionally, this system may increase product sales by providing discounted prices and directly presenting products to the user which they are eligible to redeem.

[0022] FIG. 1 shows a partial view of a cabin of a vehicle, and FIG. 2 shows a block diagram of an in-vehicle computing system of the vehicle. The vehicle of FIGS. 1-2 may include and / or be communicably coupled to a computing device that is configured to receive vehicle behavior data that is captured by a sensor subsystem of the vehicle and compute a trip score using the vehicle behavior data. The computing device may further apply a number of points to a point total of a user profile, where the number of points corresponds to the trip score. Additionally, the computing device may display a set of redeemable products from a library of products, where prices of each product of the set of redeemable products are less than and / orequal to the point total. The point total may be automatically updated in response to awarding of more points (e.g., from additional trips) and / or subtraction of points (e.g., purchasing a product). The set of redeemable products that are made available may also be automatically updated in response to an updated point total. FIG. 3 illustrates a method for calculating a trip score using vehicle behavior data collected during a trip of the vehicle of FIGS. 1-2. FIG. 4 illustrates a method for updating a point total and a set of redeemable products that may be purchased using points that are awarded based on the trip score. FIG. 5 illustrates a method for collecting vehicle behavior data, via a sensor subsystem, that may be used to calculate the trip score. One or more of the methods of FIGS. 3-5 may be performed by the computing device (e.g., integrated in and / or communi cably coupled to the vehicle). FIGS. 6-10 illustrate example views of a display device, including a summary of vehicle behavior statistics used to calculate the trip score, profile information of a user, and various reward redemption screens.

[0023] FIG. 1 shows an example partial view of an interior of a cabin 100 of a vehicle 102, in which one or more passengers may be seated. In some examples, a passenger may be an operator of the vehicle 102, while in other examples, the vehicle 102 may be an autonomous, driver-less vehicle. Vehicle 102 of FIG. 1 may be a motor vehicle including drive wheels (not shown) and an internal combustion engine 104. Internal combustion engine (ICE) 104 may include one or more combustion chambers which may receive intake air via an intake passage and exhaust combustion gases via an exhaust passage. Vehicle 102 may be a road automobile, among other types of vehicles. In some examples, vehicle 102 may include ahybrid propulsion system including an energy conversion device operable to absorb energy from vehicle motion and / or the engine and convert the absorbed energy' to an energy form suitable for storage by an energy storage device. Vehicle 102 may include a fully electric vehicle, incorporating fuel cells, solar energy capturing elements, and / or other energy storage systems for powering the vehicle.

[0024] As shown, an instrument panel 106 may include various displays and controls accessible to passengers of vehicle 102. For example, instrument panel 106 may include atouch screen 108 of an in-vehicle computing system 109 an audio system control panel, and an instrument cluster 110. Touch screen 108 may receive user input to in-vehicle computing system 109 for controlling audio output, visual display output, user preferences, control parameter selection, and so on. In some embodiments, one or more hardware elements of in- vehicle computing system 109, such as touch screen 108, a display screen 111, various control dials, knobs and buttons, memory, processor(s), and any interface elements (e.g., connectors or ports) may form an integrated head unit that is installed in instrument panel 106 of the vehicle. The head unit may be fixedly or removably attached in instrument panel 106. Inadditional or alternative embodiments, one or more hardware elements of in-vehicle computing system 109 may be modular and may be installed in multiple locations of the vehicle.

[0025] Cabin 100 may include one or more sensors for monitoring the vehicle, the user, and / or the environment, including vehicle behaviors and / or operator behaviors. For example, cabin 100 may include one or more seat-mounted pressure sensors configured to measure the pressure applied to the seat to determine the presence of a user, door sensors configured to monitor door activity, humidity sensors to measure the humidity content of the cabin, microphones to receive user input in the form of voice commands, to enable a user to conduct telephone calls, and / or to measure ambient noise in cabin 100, and so on. In further examples, the sensors may be used to identify and differentiate among different operators of the vehicle. It is to be understood that the above-described sensors and / or one or more additional or alternative sensors may be positioned in any suitable location of the vehicle. For example, sensors may be positioned in an engine compartment, on an external surface of the vehicle, and / or in other suitable locations for providing information regarding the operation of the vehicle, ambient conditions of the vehicle, a user of the vehicle, and so on. Information regarding ambient conditions of the vehicle, vehicle status, or vehicle operator may also be received from sensors external to / separate from the vehicle (that is, not part of the vehicle system), such as sensors coupled to external devices 150 and / or a mobile device 128.

[0026] Cabin 100 may also include one or more user objects, such as mobile device 128, that are stored in the vehicle before, during, and / or after travelling. Mobile device 128 may include a smart phone, a tablet, a laptop computer, a portable media player, and / or any suitable mobile computing device. Mobile device 128 may be connected to in-vehicle computing system via a communication link 130. Communication link 130 may be wired (e.g., via Universal Serial Bus (USB). Mobile High-Definition Link (MHL), High-Definition Multimedia Interface (HDMI), Ethernet, and so on) or wireless (e.g., via Bluetooth®, Wi-Fi®, Wi-Fi Direct®, Near-Field Communication (NFC), cellular connectivity, and so on) and configured to provide two-way communication between the mobile device and the in-vehicle computing system. (Bluetooth® is a registered trademark of Bluetooth SIG, Inc., Kirkland, WA. Wi-Fi® and Wi-Fi Direct® are registered trademarks of Wi-Fi Alliance, Austin, Texas.) Mobile device 128 may include one or more wireless communication interfaces for connecting to one or more communication links (e.g., one or more of the example communication links described above). The wireless communication interface may include one or more physical devices, such as antenna(s) or port(s) coupled to data lines for carrying transmitted or received data, as well as one or more modules / drivers for operating the physical devices in accordancewith other devices in the mobile device. For example, communication link 130 may provide sensor and / or control signals from various vehicle systems (such as vehicle audio system, climate control system, and so on) and touch screen 108 to mobile device 128 and may provide control and / or display signals from mobile device 128 to the in-vehicle systems and touch screen 108. Communication link 130 may also provide power to mobile device 128 from an in-vehicle power source in order to charge an internal battery of the mobile device.

[0027] In-vehicle computing system 109 may also be communicatively coupled to additional devices operated and / or accessed by the user but located external to vehicle 102, such as one or more external devices 150. In the depicted embodiment, external devices are located outside of vehicle 102, though it is to be appreciated that in alternate embodiments, external devices may be located inside cabin 100. The external devices 150 may include a server computing system, edge computing device(s), personal computing system, portable electronic device, electronic wrist band, electronic head band, portable music player, electronic activity tracking device, pedometer, smart-watch, GPS system, and so on. External devices 150 may be connected to the in-vehicle computing system via a communication link 136 which may be wired or wireless, as discussed with reference to communication link 130, and configured to provide two-way communication between the external devices and the in-vehicle computing system. For example, external devices 150 may include one or more sensors and communication link 136 may transmit sensor output from external devices 150 to in-vehicle computing system 109 and touch screen 108. External devices 150 may also store and / or receive information regarding contextual data, user behavior / preferences, operating rules, and so on and may transmit such information from external devices 150 to in-vehicle computing system 109 and touch screen 108. External devices 150 may also receive information, such as vehicle behavior data captured by sensors of the vehicle, from the in-vehicle computing system 109.

[0028] In-vehicle computing system 109 may analyze the input data received from external devices 150, mobile device 128, and / or other input sources and select settings for various in-vehicle systems (such as climate control system or audio system), provide output via touch screen 108 and / or speakers 112, communicate with mobile device 128 and / or external devices 150, and / or perform other actions based on the assessment. In some embodiments, all or a portion of the assessment may be performed by mobile device 128 and / or external devices 150.

[0029] In some embodiments, one or more of external devices 150 may be communicatively coupled to in-vehicle computing system 109 indirectly, via mobile device128 and / or another of external devices 150. For example, communication link 136 may communicatively couple external devices 150 to mobile device 128 such that output from external devices 150 is relayed to mobile device 128. Data received from external devices 150 may then be aggregated at mobile device 128 with data collected by mobile device 128. The aggregated data is then transmitted to in-vehicle computing system 109 and touch screen 108 via communication link 130. Similar data aggregation may occur at a server system and then be transmitted to in-vehicle computing system 109 and touch screen 108 via communication link 136 and / or communication link 130.

[0030] FIG. 2 shows a block diagram of the in-vehicle computing system 109 configured and / or integrated inside the vehicle 102. In-vehicle computing system 109 may perform one or more of the methods described herein in some embodiments. In-vehicle computing system 109 may include, or be coupled to, various vehicle systems, sub-systems, hardware components, as well as software applications and systems that are integrated in, or integratable into, vehicle 102 in order to enhance an in-vehicle experience for a driver and / or a passenger.

[0031] In-vehicle computing system 109 may include one or more processors including an operating system processor 214 and an interface processor 220. Operating system processor 214 may execute an operating system on in-vehicle computing system 109, and control input / output, display, playback, and other operations of in-vehicle computing system 109. Interface processor 220 may interface with a vehicle control system 230 via an inter-vehicle system communication module 222.

[0032] Inter-vehicle system communication module 222 may output data to one or more other vehicle systems 231 and / or one or more other vehicle control elements 261, while also receiving data input from other vehicle systems 231 and other vehicle control elements 261, e.g., by way of vehicle control system 230. When outputting data, inter-vehicle system communication module 222 may provide a signal via a bus corresponding to any status of the vehicle, the vehicle surroundings, or the output of any other information source connected to the vehicle. Vehicle data outputs may include, for example, analog signals (such as current velocity), digital signals provided by individual information sources (such as clocks, thermometers, location sensors such as Global Positioning System (GPS) sensors, and so on), digital signals propagated through vehicle data networks (such as an engine controller area network (CAN) bus through which engine related information may be communicated, a climate control CAN bus through which climate control related information may be communicated, and a multimedia data network through which multimedia data is communicated between multimedia components in the vehicle). For example, in-vehicle computing system 109 mayretrieve from the engine CAN bus the current speed of the vehicle estimated by the wheel sensors, a power state of the vehicle via a battery and / or power distribution system of the vehicle, an ignition state of the vehicle, and so on. In addition, other interfacing means such as Ethernet may be used as well without departing from the scope of this disclosure.

[0033] A storage device 208 may be included in the in-vehicle computing system 109 to store data such as instructions executable by operating system processor 214 and / or interface processor 220 in non-volatile form. Storage device 208 may store application data, including prerecorded sounds, to enable in-vehicle computing system 109 to run an application for connecting to and / or collecting information for transmission to a cloud-based server and / or an edge computing device. The application may retrieve information gathered by vehicle systems, sensors, input devices (e.g., a user interface 218). data stored in one or more storage devices, such as a volatile memory 219A or a non-volatile memory 219B, devices in communication with the in-vehicle computing system 109 (e.g., a mobile device connected via a Bluetooth® link), and so on. (Bluetooth® is a registered trademark of Bluetooth SIG, Inc., Kirkland, WA.) Volatile memory 219A may be random access memory (RAM). Non-transitory storage devices, such as non-volatile storage device 208 and / or non-volatile memory 219B, may store instructions and / or code that, when executed by a processor (e.g., operating system processor 214 and / or interface processor 220), controls in-vehicle computing system 109 to perform one or more of the actions described in the disclosure.

[0034] One or more additional sensors may be included in a sensor subsystem 210 of in- vehicle computing system 109, where sensors of the sensor subsystem 210 are configured to capture information about a vehicle behavior and / or an operator behavior. For example, sensor subsystem 210 may include a camera, such as a rear view camera for assisting a user in parking the vehicle and / or a cabin camera for identifying a user (e.g., using facial recognition and / or user gestures). Sensor subsystem 210 of in-vehicle computing system 109 may communicate with and receive inputs from various vehicle sensors and may further receive user inputs. For example, the inputs received by sensor subsystem 210 may include transmission gear position, transmission clutch position, gas pedal input, brake input, transmission selector position, vehicle speed, engine speed, mass airflow through the engine, ambient temperature, intake air temperature, and so on, as well as inputs from climate control system sensors (such as heat transfer fluid temperature, antifreeze temperature, fan speed, passenger compartment temperature, desired passenger compartment temperature, ambient humidify, and so on), an audio sensor detecting voice commands issued by a user, a fob sensor receiving commandsfrom and optionally tracking the geographic location / proximity of a fob of the vehicle, and so on.

[0035] The sensor subsystem 210 may continuously record instances and / or durations of the vehicle behaviors, such as a number of hard braking events, an average speed, a number of honks, and a number of and / or frequency of lane changes. For example, the sensor subsystem 210 may include one or more of a braking electronic control unit (ECU), and / or an engine ECU. The sensor subsystem 210 may further include an advanced driver assistant system (ADAS) unit, which is an integrated ECU with object recognition, condition evaluation, and control judgment functions of vehicle operation functions such as lane keep assist, rear-side warning, autonomous braking, and so on.

[0036] While certain vehicle system sensors may communicate with sensor subsystem 210 alone, other sensors may communicate with both sensor subsystem 210 and vehicle control system 230, or may communicate with sensor subsystem 210 indirectly via vehicle control system 230. A navigation subsystem 211 of in-vehicle computing system 109 may generate and / or receive navigation information such as location information (e.g.. via a GPS sensor and / or other sensors from sensor subsystem 210), route guidance, traffic information, point-of- interest (POI) identification, and / or provide other navigational services for the driver.

[0037] An external device interface 212 of in-vehicle computing system 109 may be selectively coupled to and / or communicate with one or more external devices 150 located external to vehicle 102. While the external devices are illustrated as being located external to vehicle 102, it is to be understood that they may be temporarily housed in vehicle 102, such as when the user is operating the external devices while operating vehicle 102. In other words, external devices 150 are not integral to vehicle 102. External devices 150 may include a mobile device 128 (e g., connected via a Bluetooth®. NFC, WI-FI Direct®, or other wireless connection) or an alternate Bluetooth®-enabled device. (Wi-Fi Direct® is a registered trademark of Wi-Fi Alliance, Austin, Texas.)

[0038] Mobile device 128 may be a mobile phone, smart phone, wearable devices / sensors that may communicate with the in-vehicle computing system via wired and / or wireless communication, or other portable electronic device(s). Other external devices include one or more external services 246. For example, the external devices may include extra-vehicular devices that are separate from and located externally to the vehicle. Still other external devices include one or more external storage devices 254, such as solid-state drives, pen drives, Universal Serial Bus (USB) drives, and so on. External devices 150 may communicate with in- vehicle computing system 109 either wirelessly or via connectors without departing from thescope of this disclosure. For example, external devices 150 may communicate with in-vehicle computing system 109 through external device interface 212 over a network 260, a USB connection, a direct wired connection, a direct wireless connection, and / or other communication link.

[0039] External device interface 212 may provide a communication interface to enable the in-vehicle computing system to communicate with mobile devices associated with contacts of the driver. For example, external device interface 212 may enable phone calls to be established and / or text messages (e.g., Short Message Service (SMS), Multimedia Message Service (MMS), and so on) to be sent (e.g., via a cellular communications network) to a mobile device associated with a contact of the driver. External device interface 212 may additionally or alternatively provide a wireless communication interface to enable the in-vehicle computing system to synchronize data with one or more devices in the vehicle (e.g., the driver’s mobile device) via Wi-Fi Direct®, as described in more detail below.

[0040] One or more applications 244 may be operable on mobile device 128. As an example, a mobile device application 244 may be operated to aggregate user data regarding interactions of the user with the mobile device. For example, mobile device application 244 may be used to manage a user and / or vehicle profile, view a number of points associated with the user and / or vehicle profile, view trip scores and / or average trip scores of the user and / or vehicle profile, and / or redeem products using available points. The collected data may be transferred by application 244 to external device interface 212 over network 260. In addition, specific user data requests may be received at mobile device 128 from in-vehicle computing system 109 via external device interface 212. The specific data requests may include requests for determining where the user is geographically located, an ambient noise level and / or music genre at the user’s location, an ambient weather condition (temperature, humidity, and so on) at the user’s location, and so on. Mobile device application 244 may send control instructions to components (e.g., microphone, amplifier, and so on) or other applications (e.g., navigational applications) of mobile device 128 to enable the requested data to be collected on the mobile device or requested adjustment made to the components. Mobile device application 244 may then relay the collected information back to in-vehicle computing system 109.

[0041] Likewise, one or more applications 248 may be operable on external services 246. As an example, external services applications 248 may be operated to aggregate and / or analyze data from multiple data sources. For example, external services applications 248 may aggregate data from one or more social media accounts of the user, data from the in-vehicle computing system (e.g., sensor data, log files, user input, and so on), data from an internet query (e.g.,weather data, POI data), data from an edge computing device to which the in-vehicle computing system 109 is communicably coupled, and so on. The collected data may be transmitted to another device and / or analyzed by the application to determine a context of the driver, vehicle, and environment and perform an action based on the context (e.g., requesting / sending data to other devices).

[0042] Vehicle control system 230 may include controls for controlling aspects of various vehicle systems 231 involved in different in-vehicle functions. These may include, for example, controlling aspects of vehicle audio system 232 for providing audio entertainment to the vehicle occupants, aspects of a climate control system 234 for meeting the cabin cooling or heating needs of the vehicle occupants, as well as aspects of a telecommunication system 236 for enabling vehicle occupants to establish telecommunication linkage with others.

[0043] The in-vehicle computing system 109 may include a multi-command serial bus 240 that is configured as a zonal architecture to accumulate multiple vehicle behavior data inputs from the sensor subsystem (e.g., the sensor subsystem 210) of the vehicle 102. As further described with respect to FIGS. 3-5. the multi-command serial bus 240 may be configured to convert multiple vehicle behavior data inputs into a daisy -chained, one-to-one architecture for transmission to one or more devices that are communicably coupled to the multi-command serial bus 240.

[0044] Audio system 232 may include one or more acoustic reproduction devices including electromagnetic transducers such as one or more speakers 235. Vehicle audio system 232 may be passive or active such as by including a power amplifier. In some examples, in- vehicle computing system 109 may be a sole audio source for the acoustic reproduction device or there may be other audio sources that are connected to the audio reproduction system (e.g., external devices such as a mobile phone). The connection of any such external devices to the audio reproduction device may be analog, digital, or any combination of analog and digital technologies.

[0045] Climate control system 234 may be configured to provide a comfortable environment within the cabin or passenger compartment of vehicle 102. Climate control system 234 includes components enabling controlled ventilation such as air vents, a heater, an air conditioner, an integrated heater and air-conditioner system, and so on. Other components linked to the heating and air-conditioning setup may include a windshield defrosting and defogging system capable of clearing the windshield and a ventilation-air filter for cleaning outside air that enters the passenger compartment through a fresh-air inlet.

[0046] Vehicle control system 230 may also include controls for adjusting the settings of various vehicle control elements 261 (or vehicle controls, or vehicle system control elements) related to the engine and / or auxiliary elements within a cabin of the vehicle, such as one or more steering wheel controls 262 (e.g., steering wheel-mounted audio system controls, cruise controls, windshield wiper controls, headlight controls, turn signal controls, and so on), instrument panel controls, microphone(s), accelerator / brake / clutch pedals, a gear shift, door / window controls positioned in a driver or passenger door, seat controls, cabin light controls, audio system controls, cabin temperature controls, and so on. Vehicle control elements 261 may also include internal engine and vehicle operation controls (e.g., engine controller module, actuators, valves, and so on) that are configured to receive instructions via the CAN bus of the vehicle to change operation of one or more of the engine, exhaust system, transmission, and / or other vehicle system. The control signals may also control audio output at one or more speakers 235 of vehicle audio system 232. For example, the control signals may adjust audio output characteristics such as volume, equalization, audio image (e g., the configuration of the audio signals to produce audio output that appears to a user to originate from one or more defined locations), audio distribution among a plurality of speakers, and so on. Likewise, the control signals may control vents, air conditioner, and / or heater of climate control system 234. For example, the control signals may increase delivery7of cooled air to a specific section of the cabin.

[0047] Control elements positioned on an outside of a vehicle (e.g., controls for a security system) may also be connected to in-vehicle computing system 109, such as via inter-vehicle system communication module 222. The control elements of vehicle control system 230 may be physically and permanently positioned on and / or in the vehicle for receiving user input. In addition to receiving control instructions from in-vehicle computing system 109, vehicle control system 230 may also receive input from one or more external devices 150 operated by the user, such as from mobile device 128. This allows aspects of vehicle systems 231 and vehicle control elements 261 to be controlled based on user input received from external devices 150.

[0048] In-vehicle computing system 109 may further include one or more antennas 206. The in-vehicle computing system may obtain broadband wireless internet access via antennas 206, and may further receive broadcast signals such as radio, television, weather, traffic, and the like. In-vehicle computing system 109 may receive positioning signals such as GPS signals via antennas 206. The in-vehicle computing system may also receive wireless commands via radio frequency (RF) such as via antennas 206 or via infrared or other means throughappropriate receiving devices. In some embodiments, antenna 206 may be included as part of audio system 232 or telecommunication system 236. Additionally, antenna 206 may provide AM / FM radio signals to external devices 150 (such as to mobile device 128) via external device interface 212.

[0049] One or more elements of in-vehicle computing system 109 may be controlled by a user via user interface 218. User interface 218 may include a graphical user interface presented on a touch screen and / or user-actuated buttons, switches, knobs, dials, sliders, and so on. For example, user-actuated elements may include steering wheel controls, door and / or window controls, instrument panel controls, audio system settings, climate control system settings, and the like. A user may also interact with one or more applications of in-vehicle computing system 109 and mobile device 128 via user interface 218. In addition to receiving a user’s vehicle setting preferences on user interface 218, vehicle settings selected by in-vehicle control system 230 may be displayed to a user on user interface 218. Notifications and other messages (e.g., received messages), as well as navigational assistance, may be displayed to the user on a display of the user interface. User preferences / information and / or responses to presented messages may be performed via user input to the user interface. For example, the in-vehicle computing system 109 may receive one or more vehicle control commands from an external device 150, such as an edge computing device, and a prompt may be displayed on the user interface 218 that the user may interact with to accept or reject implementation of the vehicle control command.

[0050] The methods described herein for monitoring and quantifying vehicle behaviors may be implemented by a variety of systems. Each of the vehicle, the multi-command serial bus, the display device, and the computing device may be separate devices that are communicably coupled via a wired and / or a wireless connection. In some examples, one or more of the vehicle, the multi-command serial bus, the display device, and the computing device may be integrated in the same device. For example, the display device may be a display device of the vehicle (e.g., the touch screen 108 and / or the display screen 111 of the vehicle 102 of FIGS. 1-2).

[0051] In another example, one or more of the methods described herein for monitoring and quantifying vehicle behavior may be implemented by a computing device that is external to and communicably coupled to the vehicle. For example, the computing device may be the mobile device 128 and / or one or more external devices 150, such as a cloud server. The computing device may include a display device, a user interface, a processor, and a non-transitory memory storing executable instructions that, when executed, cause the processor to execute the methods described herein.

[0052] FIG. 3 shows a flow chart for a method 300 for calculating a trip score using vehicle behavior data collected during a trip of the vehicle. The method 300 may be stored in a memory of a computing device as instructions that are executable by a processor of the computing device. For example, instructions for executing the method 300 may be stored in the memory of and executed by the processor of the in-vehicle computing system 109. In other examples, instructions for executing the method 300 may be stored in the memory of and executed by the processor of an external device (e.g., of the external devices 150) that is communicably coupled to the vehicle 102.

[0053] At 302, the method 300 includes receiving vehicle behavior data that is collected during a trip of a vehicle. Vehicle behavior data may be collected by the sensor subsystem, including one or more ECU of the vehicle. The vehicle behavior data may include one or more of a number of hard braking events, an average speed, a number of honks, and a number of and / or frequency of lane changes. Further detail about vehicle behavior data collection is described with respect to FIG. 5. In examples where the method 300 is executed by a computing device of the vehicle, vehicle behavior data may be transferred directly from the sensors / ECUs that capture the vehicle behavior data to the computing device. In examples where the method 300 is executed by a device other than the vehicle computing device, for example by a mobile device communicably coupled to the computing device of the vehicle, the vehicle behavior data may be sent to the computing device executing the method 300 via a wired and / or a wireless connection. The vehicle behavior data may be received in a daisy-chained, one-to-one architecture, which may reduce bandwidth demand. For example, instead of being stored and transmitted as individual data, each behavior statistic (e.g.. each of the different types of vehicle behavior data collected) of the vehicle behavior data may be linked together in series and stored as a single data structure. If the vehicle behavior data is received in the daisy-chained format, the method 300 may include extracting vehicle behavior statistics from the daisy-chained format.

[0054] At 304, the method 300 includes calculating a trip score for the tnp using the vehicle behavior data. The trip score (tscore) may be calculated by identifying individual behavior statistics of the vehicle behavior data, applying a weight to each behavior statistic, dividing a first subset of behavior statistics by a trip duration, and subtracting and / or adding each weighted behavior statistic from / to a maximum trip score. In some examples, the maximum trip score may be 100. The trip score may be calculated as equal to 100 when thereare no undesirable vehicle behaviors in the vehicle behavior data. In another example, the trip score may be calculated as equal to 100 when a sum of weighted values that are subtracted from the total trip score is equal to a sum of w eighted values that are added to the total trip score. For example, the trip score may be calculated using equation 1:(0.1)} (1) where "num Lane Change" is a number oflane change events, "numTurnWithoutlndicator” is anumber of turns performed without using an indicator (e.g., without activating a turn signal), “ numHonks ” is a number of times a hom of the vehicle has been honked, "numH ardBraking" is a number of hard brake events (e.g., rather than gradual application of the brake), "numQuickAcceleration" is a number of quick acceleration events (e.g., rather than gradual acceleration), “durationOfHighBeamlnMin,' is a duration of time in minutes for which a high beam has been activated, “speedidea(” is an ideal and / or desired traveling speed (e g., a posted maximum speed), “speedaverage” is an average speed of the vehicle, and "durationOfLaneMaintainlnMin" is a duration of time in minutes for which the vehicle maintained travel in a single lane (e.g.. did not merge and / or drift out of boundaries of the single lane).

[0055] At 306, the method 300 includes determining a number of points, based on the trip score, to apply to a user profile. When using equation 1 to calculate the trip score, the trip score may be in a range between tmin and 100, wherein tmin is determined based on a number of behavior statistics used to calculate the trip score, with a minimum tmin value of zero. Based upon a range in which the trip score falls, the number of points to be applied to the user profile is determined. For example, for a trip score less than or equal to 100 and greater than or equal to 90, ten points may be applied. For a trip score less than 90 and greater than or equal to 85, nine points may be applied. For a trip score less than 85 and greater than or equal to 80, eight points may be applied. For a trip score less than 80 and greater than or equal to 70, seven points may be applied. For a trip score less than 70 and greater than or equal to 65, six points may be applied. For atrip score less than 65 and greater than or equal to 60, five points may be applied.For a trip score less than 60 and greater than or equal to 50, four points may be applied. For a trip score less than 50 and greater than or equal to 45, three points may be applied. For a trip score less than 45 and greater than or equal to 40, two points may be applied. For a trip score less than 40 and greater than or equal to 33, one point may be applied. For a trip score below 33, no points may be applied.

[0056] At 308, the method 300 includes adding the number of points to a point total of the user profile. For example, the point total of the user profile, as stored in the memon of the computing device, may have a number of points that have been applied from the trip scores of one or more prior trips. The number of points determined to be applied for the present trip score is applied to the stored point total.

[0057] At 310, the method 300 includes storing the point total. For example, the stored point total may be updated to include the number of points applied from a most recent trip score. The reward points, once awarded, will continue to accumulate in the user profile.

[0058] At 312, the method 300 includes displaying a first set of redeemable products, where a price of each product of the first set of redeemable products is equal to and / or less than the point total. The first set of redeemable products may be displayed on a display device, such as the touch screen and / or the display screen of the user interface of FIG. 2, and / or a display device of the external device 150 of FIGS. 1-2. Example views of the display are shown in FIGS. 6-10. The method 300 ends.

[0059] FIG. 4 shows a flow chart for a method 400 for updating a point total and a set of redeemable products that correspond to the point total in response to selection and / or purchase of one or more redeemable products. The method 400 may be executed by a computing device, such as the in-vehicle computing system 109 of the vehicle 102 of FIGS. 1-2, and / or an external device such as the mobile device 128 and / or another external device of the external devices 150. In further examples, the external device may be indirectly coupled to the vehicle 102. For example, the external device configured to execute the method 400 and the vehicle 102 may each be communicable to a cloud server.

[0060] At 402, the method 400 includes receiving a user input, where the user input includes selection of one or more products of the first set of redeemable products. The user input may be received via a user input device of the computing device, such as a touch screen and / or one or more buttons.

[0061] At 404, the method 400 includes subtracting a number of points from the point total, where the number of points is equal to a sum of the prices of each product selected in the user input. As further described with respect to FIGS. 6-10, the first set of redeemable productsmay include products that each have a price that is equal to or less than the number of points available in the point total. If a sum of prices of two or more selected products is greater than the point total, one or more of the selected products may not be purchased and the corresponding price may not be subtracted from the point total.

[0062] At 406, the method 400 includes updating and storing the point total to exclude the number of points subtracted from the point total. In some examples, the points collected will be stored in the user profile for a set amount of time, and may be removed from the point total after the set amount of time. For example, points may lapse at end of two years.

[0063] At 408, the method 400 includes halting display of the first set of redeemable products. As the point total has changed, a price of one or more redeemable products of the first set of redeemable products may be greater than the available point total, and thus ineligible for purchase.

[0064] At 410, the method 400 includes displaying a second set of redeemable products. The second set of redeemable products may include one or more of the redeemable products of the first set of redeemable products. The second set of redeemable products may be automatically generated by retrieving products from a library of products that have prices equal to and / or less than the updated point total. The method 400 ends.

[0065] FIG. 5 shows a flow chart for a method 500 for collecting vehicle behavior data that may be used to calculate the trip score. As described above, the vehicle behavior data may include one or more of a number of quick accelerations, turns without using an indicator, hard braking events, an average speed, a number of honks, a duration of high beam usage, and a number of and / or frequency of lane changes. The method 500 may be executed by the in- vehicle computing system 109 of the vehicle 102 of FIGS. 1-2. For example, instructions for executing the method 500 may be stored in one or more of the storage device 208, the memory 219A, and the memory 219B of FIG. 2. The instructions may be executable by a processor (e.g., the operating system processor 214 and / or the interface processor 220 of FIG. 2) to perform the method 500.

[0066] At 502, the method 500 includes receiving a ‘vehicle ignition on’ indicator. In the example described herein, the ‘vehicle ignition on’ indicator is used to indicate a beginning of a trip of the vehicle. In other examples, such when the method 500 is implemented in hybrid electric vehicles and / or electric vehicles that may use a power source other than an ICE, another indicator (e.g., electric motor state indicator) may be used to indicate the beginning of the trip of the vehicle.

[0067] At 504, the method 500 includes initiating collection of vehicle behavior data via the sensor subsystem of the vehicle. For example, the sensor subsystem may include a braking ECU, and / or an engine ECU. The sensor subsystem may continuously record instances and / or durations of the vehicle behaviors described above.

[0068] At 506, the method 500 includes applying a low priority' identifier to message frames containing vehicle behavior data. This may include reading signals received from each of the one or more ECUs using an ADAS unit (e.g., the ADAS unit of FIGS. 1-2) and determining whether the signals include vehicle behavior data or vehicle operating commands, such as a brake signal and / or an accelerate signal. Applying the low priority' identifier to the message frames containing vehicle behavior data labels these message frames to indicate that other message frames having higher priority’ identifiers than the low priority identifiers are to be transmitted, processed, and / or implemented before performing an action with the message frame having the low priority identifier.

[0069] At 508, the method 500 includes applying a high priority identifier to message frames containing vehicle operating commands. The high priority’ identifier may indicate that the message frame(s) having the high priority identifier are to be transmitted and / or implemented before implementing other message frames that do not have the high priority identifier.

[0070] At 510, the method 500 includes determining if a high priority message frame has been received. For example, the sensor subsystem may be continuously collecting vehicle behavior data, and the processor may be labeling message frames containing vehicle behavior data with the low priority identifier. Message frames containing vehicle operating commands, and thus which are labeled with high priority identifiers, may occur less frequently than message frames containing vehicle behavior data. For example, a message frame containing vehicle operating commands may occur in response to a user input such as depressing a brake pedal.

[0071] At 510, in response to receiving a high priority’ message frame, the method 500 proceeds to 516. At 516, the method 500 includes directing control of a data bus to a message frame with a high priority identifier. Use of low priority and high priority message frames may assist in prioritizing bandwidth of the computing device of the vehicle for operating components. For example, collecting vehicle behavior data from the ECUs may consume bandwidth on Ethernet. To reduce an impact of data flow on operations such as braking and engine operation, the multi-command serial bus is implemented to distribute node control. For example, no single commander node may control when individual nodes (e.g., the ECUs,vehicle operation commands) can read and write to the data bus. If multiple nodes attempt to transmit to the data bus at the same time, the node having the high priority identifier takes control of the bus. Thus, in cases of high bandwidth demand on the network, a highest node priority is assigned to message frames with high priority identifiers (e.g., message frames having vehicle operating commands). In some examples, the method 500 further includes halting collection of vehicle behavior data at 518. This may further reduce bandwidth demand and provide computing resources to vehicle operation commands.

[0072] The method 500 returns to operation 510 to continuously monitor whether a high priority message frame is received. In response to not receiving a high priority message frame, the method 500 proceeds to 512 to collect vehicle behavior data via at least one ECU.

[0073] At 514, the method 500 includes determining if the computing device has received a ‘vehicle ignition off indicator. In the example described herein, the ‘vehicle ignition off indicator is used to indicate an end of a trip of the vehicle. In other examples, such as hybrid electric vehicles and / or electric vehicles that may use a power source other than an ICE, another indicator may be used to indicate the end of the trip of the vehicle. In response to receiving the 'vehicle ignition off indicator, the method 500 may end and proceeds to the method 300 of FIG. 3. For example, when the method 300 is executed by the computing device of the vehicle (e.g., the in-vehicle computing system 109), the method 500 may proceed from operation 514 to the method 300 of FIG. 3, as the vehicle behavior data may not be sent to an external device that is communicably coupled to the vehicle 102. In response to not receiving the ‘vehicle ignition off indicator, the method 500 returns to operation 510 to continue monitoring whether a high priority message frame has been received.

[0074] In some examples, a computing device that is external to and communicably coupled to the vehicle 102 may perform the method 300 using the vehicle behavior data captured in the method 500. In these examples, the vehicle behavior data is transmitted to the computing device. The vehicle behavior data may be securely published to the computing device, such as a cloud server, using a multi-level approach. For example, network traffic between cloud data centers may be transparently encrypted at the physical layer. Network traffic within a virtual private cloud (VPC) and among peered VPCs may be transparently encrypted at a network level.

[0075] At 520, the method 500 optionally includes accumulating vehicle behavior data into a daisy-chained, one-to-one architecture. This operation may be performed by the multicommand serial bus. which pulls together multiple vehicle behavior data message frames into a single data unit. In this way, data collected by different sensors of the sensor subsystem areaggregated, which may reduce bandwidth demands for networks, switches, and connections carrying the data. The zonal approach for data transmission and storage may further provide scalability, reliability, and functionality, as a zonal approach may link the central computing complex (e.g., the computing device) to sensors and devices through networked zonal gateways.

[0076] At 522, the method 500 optionally includes outputting the daisy -chained, one-to- one architecture formatted vehicle behavior data to an external computing device. The external computing device may be configured to perform the method 300 to generate the trip score using the vehicle behavior data.

[0077] FIGS. 6-10 illustrate views of a mobile application that may be used to manage a user and / or vehicle profile, view a number of points associated with the user and / or vehicle profile, view trip scores and / or average trip scores of the user and / or vehicle profile, and / or redeem products using available points. The products may include coupons for discounts to purchase items from a physical and / or online store. In another example, the points may be used to purchase car accessories provided by the manufacturer such as floor mats, scents, lubricants, seat covers, car cover, and so on.

[0078] FIG. 6 shows a first example view 600 of a display 602 of a display device 604. The display device 604 may be an example of the touch screen 108 and / or the display screen 111 of FIG. 1, the user interface 218 of FIG. 2, and / or a display of the external device 150 (e.g., the mobile device 128). The first example view 600 includes a summary of vehicle behavior statistics 606 that are used to calculate a trip score 608. The trip score 608 is also displayed in the first example view 600. The score may be a score of the last trip. In other examples the trip score may be an average score over a time frame, such as a month period. The view 600 further includes an identifier 610 that illustrates for which vehicle the trip score has been calculated. In other examples, the trip score may be calculated for each user that drives the vehicle (e.g., the same vehicle), and the identifier 610 may illustrate a user for which the trip score has been calculated. The view 600 may include a message indicating a change in the vehicle trip score compared to an average score over a previous time period and / or a prior trip (e.g., “Good job, your score has increased!'’). The view 600 further includes a graph 612 that illustrates trip scores of the identified user and / or vehicle over the selected time period. The graph 612 and / or the time period may be selected to view further details about vehicle behaviors during a selected time period.

[0079] The view 600 further includes navigation tools 614, including buttons which a user may select to navigate out of the view 600 to view notifications, select a different user and / or vehicle for which to view trip score data, adjust settings, and / or to exit an application thatdisplays the trip score 608 and corresponding information. For example, the navigation tools 614 may include a notification icon 620 that may be selected to view notifications such as indication of updated behavior statistics and / or trip score, a reward icon 616 that may be selected to navigate to a reward redemption screen, and a settings icon 618 that may be selected to navigate to a profile information screen.

[0080] FIG. 7 shows a second example view 700 of the display 602 of the display device 604. The second example view 700 shows profile information of a user, including a name of the user 706, a username associated with the user 708, an email of the user 710, a number of available reward points 712, and a number of total earned reward points 714. The view 700 further includes buttons that may be selected to change a password associated with the username 716, and / or to sign out of the present user profile 718. The second example view 700 may be navigated to from the first example view 600 of FIG. 6, for example by selecting the settings icon 618. The first example view 600 may be navigated to from the second example view 700 by selecting a navigation tool 704 of the view 700.

[0081] FIG. 8 shows a third example view 800 of the display 602 of the display device 604. The third example view 800 shows a reward redemption screen. The first example view 600 may be navigated to from the third example view 800 by selecting a navigation tool 804 of the view 800. The reward redemption screen includes a number of available reward points 806 of a present user profile. The view 800 includes a first set of redeemable products 808. The first set of redeemable products 808 may include a selection of (e.g., some, but not all of) a library of products that are offered for purchase. The first set of redeemable products 808 may include products that each have a price 810 (e.g., points) which is equal to and / or less than the number of available reward points 806. The first set of redeemable products 808 may not include products that have a price that is greater than the number of available reward points 806. The first set of redeemable products 808 may be arranged in ascending order of price. An icon 812 and / or a “view” button 814 of each product may be selected to view more information about the product. Alternatively, an “add to cart” button 816 may be selected to select the product for purchase.

[0082] Additional products that are included in the first set of redeemable products 808 may be included on additional pages of the reward redemption screen that may be navigated to by selecting a navigation (e.g., “next page”) button 818. In other examples, the icon 812 and / or buttons of one or more products may be resized to simultaneously show additional products of the first set of redeemable products 808 on the display 602.

[0083] When the reward redemption screen is navigated to, for example by selecting the reward icon 616 of the first example view 600, the library of products that are offered for purchase may be automatically filtered to identify products having a price that is less than and / or equal to the number of available reward points 806, and add identified products to the first set of redeemable products 808 to be displayed on the display device 604.

[0084] In response to selection and purchase of one or more products from the first set of redeemable products 808 via interaction with the user interface (e.g.. the user interface 218 of FIG. 2), a number of points that is equal to a sum of the prices of the one or more selected and redeemed products is subtracted from the number of available reward points 806 (e.g., subtracted from the point total). The number of available reward points 806 is updated and stored in a memory of the computing device (e.g., the storage device 208 and / or memory of the external devices 150).

[0085] FIG. 9 shows a fourth example view 900 of the display 602 of the display device 604. The fourth example view 900 shows an updated reward redemption screen, that includes a second set of redeemable products 908. The second set of redeemable products 908 includes products that have the price 810 that is equal to and / or less than the number of available rewards points 806. In some examples, products that are not available for selection and purchase may be shown in the view 900, but may not be selectable. For example, the products having a price that is greater than the number of available reward points 806 may be crossed out using a graphical indicator (e.g.. using an ‘x’ 910), greyed out, and / or not displayed on the view 900. The third example view 800 may be automatically updated to the fourth example view 900 following selection and purchase of one or more products from the first set of redeemable products 808 displayed in the view- 800.

[0086] In other examples, in response to additional points being applied to the point total following a trip and the point total increasing, the third example view 800 may be automatically updated to a fifth example view 1000 of FIG. 10, w here the fifth example view' 1000 includes a third set of redeemable products 1008. The third set of redeemable products 1008 includes additional products that are not included in the first set of redeemable products 808 nor the second set of redeemable products 908.

[0087] In this way, systems and methods are provided for monitoring and quantifying vehicle behavior data in a way that does not significantly increase bandwidth demands on a processor, does not significantly increase network traffic among computing devices of a network, and provides security for transmitted data. The systems and methods also providing incentives to perform desirable vehicle behaviors.

[0088] The disclosure also provides support for a system, comprising: a vehicle having a sensor subsystem configured to capture vehicle behavior data of the vehicle, a multi-command serial bus configured as a zonal architecture that accumulates multiple vehicle behavior data inputs from the sensor subsystem into a daisy-chained, one-to-one architecture, a display device, and a computing device including a processor and a non-transitory memory storing executable instructions that, when executed, cause the processor to: receive the vehicle behavior data that is in the daisy-chained, one-to-one architecture from the multi-command serial bus, extract behavior statistics from the vehicle behavior data, calculate atrip score using the vehicle behavior data by applying a weight to each behavior statistic of the vehicle behavior data, and subtracting weighted behavior statistics from a maximum trip score, determine a number of points, based on the trip score, to apply to a user profile and add the number of points to a point total of the user profile, and generate and output for display on the display device a first set of redeemable products, where a price of each product of the first set of redeemable products is equal to and / or less than the point total. In a first example of the system, the sensor subsystem comprises one or more of a braking electronic control unit (ECU), an engine ECU. and an advanced driver assistant system unit (ADAS) configured with object recognition, condition evaluation, and control judgement functions including lane keep assist, rear-side warning, and autonomous parking brake engagement. In a second example of the system, optionally including the first example, the computing device is communicably coupled to the multi-command serial bus through networked zonal gateways. In a third example of the system, optionally including one or both of the first and second examples, the multi-command serial bus is communicably coupled to the sensor subsystem via a wired and / or a wireless connection. In a fourth example of the system, optionally including one or more or each of the first through third examples, behavior statistics of the vehicle behavior data captured by the sensor subsystem includes one or more of hard-braking, average speed, number of honks, frequency of lane changes, number of turns without using an indicator, and use of high beam. In a fifth example of the system, optionally including one or more or each of the first through fourth examples, applying the weight to each behavior statistic includes applying a weight to each behavior statistic that corresponds with a type of behavior statistic. In a sixth example of the system, optionally including one or more or each of the first through fifth examples, the system further comprises: a third- party device that is communicably coupled to the computing device and is configured with a memory that stores a library of redeemable products, including one or more of a vehicle accessory, a coupon, and / or a physical product, from which the first set of redeemable products may be generated.

[0089] The disclosure also provides support for a computing device, comprising: a display device, a user interface, a processor, and a non-transitory memory storing executable instructions that, when executed, cause the processor to: receive vehicle behavior data that is in a daisy-chained, one-to-one architecture format from a multi-command serial bus, extract behavior statistics from the vehicle behavior data, calculate a trip score using the vehicle behavior data by applying a weight to each behavior statistic of the vehicle behavior data, and subtracting weighted behavior statistics from a maximum trip score, determine a number of points, based on the trip score, to apply to a user profile and add the number of points to a point total of the user profile, generate and output for display on the display device a first set of redeemable products, where a price of each product of the first set of redeemable products is equal to and / or less than the point total, receive an input via the user interface, where the input includes selection and / or purchase of one or more product of the first set of redeemable products, subtract a sum of the price of each selected product from the point total, update and store the point total in the non-transitory7memory7, halt display of the first set of redeemable products, and generate and output for display on the display device a second set of redeemable products, where the price of each product of the second set of redeemable products is equal to and / or less than the point total. In a first example of the system, calculating the trip score further comprises grouping two or more behavior statistics of the vehicle behavior data into a first set of behavior statistics, and dividing each of the behavior statistics of the first set of behavior statistics by a trip duration time. In a second example of the system, optionally including the first example, the instructions, when executed, cause the processor to sum the first set of weighted behavior statistics and subtract a sum of the first set of weighted behavior statistics from the maximum trip score. In a third example of the system, optionally including one or both of the first and second examples, the instructions, when executed, cause the processor to add one or more behavior statistics, with a corresponding weight applied thereto, to the maximum trip score. In a fourth example of the system, optionally including one or more or each of the first through third examples, the instructions, when executed, cause the processor to identify a score range that the trip score is in, and apply a number of points that corresponds with the score range. In a fifth example of the system, optionally including one or more or each of the first through fourth examples, a number of points that are applied to the user profile decreases as the trip score decreases.

[0090] The disclosure also provides support for a vehicle operating system, comprising: a vehicle ignition system, including a vehicle ignition indicator, a sensor subsystem including at least one electronic control unit (ECU) configured to capture vehicle behavior data, a multi-command serial bus configured to direct control of a data bus to different message frames in response to a priority identifier of a message frame, a display device, a processor, and a non- transitory memory storing executable instructions that, when executed, cause the processor to: receive an ‘on’ indication from the vehicle ignition indicator, initiate collection of vehicle behavior data via the at least one ECU and send message frames containing vehicle behavior data from the sensor subsystem to the processor, apply a low priority identifier to message frames containing vehicle behavior data, receive message frames containing vehicle operating commands, apply a high priority identifier to message frames containing vehicle operating commands, in response to simultaneously receiving a message frame having the high priority identifier and a message frame having the low priority' identifier, halting collection of vehicle behavior data and directing control of the data bus to message frames having the high priority identifier, and in response to receiving an ‘off indication from the vehicle ignition indicator, ending collection of vehicle behavior data. In a first example of the system, the multi-command serial bus is configured as a zonal architecture that accumulates multiple vehicle behavior data inputs from the sensor subsystem into a daisy-chained, one-to-one architecture. In a second example of the system, optionally including the first example, the system further comprises: a virtual private cloud network configured to provide communication between the multicommand serial bus, the sensor subsystem, and the processor. In a third example of the system, optionally including one or both of the first and second examples, the system further comprises: executable instructions stored by the non-transitory memory' and executable by a processor to: calculate a trip score using the vehicle behavior data by applying a weight to each behavior statistic of the vehicle behavior data, and subtracting weighted behavior statistics from a maximum trip score, determine a number of points, based on the trip score, to apply to a user profile, add the number of points to a point total of the user profile, store the point total, and display a first set of redeemable products on the display device, where a price of each product of the first set of redeemable products is equal to and / or less than the point total. In a fourth example of the system, optionally including one or more or each of the first through third examples, the system further comprises: a user interface configured to receive user input including selection of one or more products of the first set of redeemable products, and a display device configured to display' a second set of redeemable products that includes one or more of the products of the first set of redeemable products and one or more products not included in the first set of redeemable products. In a fifth example of the system, optionally including one or more or each of the first through fourth examples, the system further comprises: a cloud server that is communicably coupled to the multi-command serial bus, where the cloudserver is configured to process, store, and archive vehicle behavior data to calculate the trip score and determine the number of points, based on the trip score, to apply to the user profile. In a sixth example of the system, optionally including one or more or each of the first through fifth examples, the system further comprises: executable instructions stored by the non- transitory memory7and executable by the processor to: transparently encry pt vehicle behavior data at a physical layer to be sent to the cloud server, and transparently encrypt vehicle behavior data at a network layer to be sent within a virtual private cloud (VPC).

[0091] The description of embodiments has been presented for purposes of illustration and description. Suitable modifications and variations to the embodiments may be performed in light of the above description or may be acquired from practicing the methods. For example, unless otherwise noted, one or more of the described methods may be performed by a suitable device and / or combination of devices. The methods may be performed by executing stored instructions with one or more logic devices (e.g., processors) in combination with one or more additional hardware elements, such as storage devices, memory7, hardware network interfaces / antennas, switches, actuators, clock circuits, et cetera. The described methods and associated actions may also be performed in various orders in addition to the order described in this application, in parallel, and / or simultaneously. The described systems are exemplary in nature, and may include additional elements and / or omit elements. The subject matter of the present disclosure includes all novel and non-obvious combinations and sub-combinations of the various systems and configurations, and other features, functions, and / or properties disclosed.

[0092] As used in this application, an element or step recited in the singular and preceded with the word “a” or “an’' should be understood as not excluding plural of said elements or steps, unless such exclusion is stated. Furthermore, references to “one embodiment” or “one example” of the present disclosure are not intended to be interpreted as excluding the existence of additional embodiments that also incorporate the recited features. The terms “first,” “second,” and “third,” et cetera are used merely as labels, and are not intended to impose numerical requirements or a particular positional order on their objects. The following claims particularly point out subject matter from the above disclosure that is regarded as novel and non-obvious.

Claims

CLAIMS:1 . A system, comprising: a vehicle having a sensor subsystem configured to capture vehicle behavior data of the vehicle; a multi-command serial bus configured as a zonal architecture that accumulates multiple vehicle behavior data inputs from the sensor subsystem into a daisy-chained, one-to-one architecture; a display device; and a computing device including a processor and a non-transitory memory storing executable instructions that, when executed, cause the processor to: receive the vehicle behavior data that is in the daisy-chained, one-to-one architecture from the multi -command serial bus; extract behavior statistics from the vehicle behavior data; calculate a trip score using the vehicle behavior data by applying a weight to each behavior statistic of the vehicle behavior data, and subtracting weighted behavior statistics from a maximum trip score; determine a number of points, based on the trip score, to apply to a user profile and add the number of points to a point total of the user profile; and generate and output for display on the display device a first set of redeemable products, where a price of each product of the first set of redeemable products is equal to and / or less than the point total.

2. The system of claim 1, wherein the sensor subsystem comprises one or more of a braking electronic control unit (ECU), an engine ECU, and an advanced driver assistant system unit (ADAS) configured with object recognition, condition evaluation, and control judgement functions including lane keep assist, rear-side warning, and autonomous parking brake engagement.

3. The system of claim 1, wherein the computing device is communicably coupled to the multi-command serial bus through networked zonal gateways.

4. The system of claim 1, wherein the multi-command serial bus is communicably coupled to the sensor subsystem via a wired and / or a wireless connection.

5. The system of claim 1, wherein behavior statistics of the vehicle behavior data captured by the sensor subsystem includes one or more of hard-braking, average speed, number of honks, frequency of lane changes, number of turns without using an indicator, and use of high beam.

6. The system of claim 1, wherein applying the weight to each behavior statistic includes applying a weight to each behavior statistic that corresponds with a t pe of behavior statistic.

7. The system of claim 1, further comprising a third-part}' device that is communicably coupled to the computing device and is configured with a memory' that stores a library of redeemable products, including one or more of a vehicle accessory’, a coupon, and / or a physical product, from which the first set of redeemable products may be generated.

8. A computing device, comprising: a display device; a user interface; a processor: and a non-transitory memory’ storing executable instructions that, when executed, cause the processor to: receive vehicle behavior data that is in a daisy -chained, one-to-one architecture format from a multi-command serial bus; extract behavior statistics from the vehicle behavior data; calculate a trip score using the vehicle behavior data by applying a weight to each behavior statistic of the vehicle behavior data, and subtracting weighted behavior statistics from a maximum trip score; determine a number of points, based on the trip score, to apply to a user profile and add the number of points to a point total of the user profile; generate and output for display on the display device a first set of redeemable products, where a price of each product of the first set of redeemable products is equal to and / or less than the point total: receive an input via the user interface, where the input includes selection and / or purchase of one or more product of the first set of redeemable products; subtract a sum of the price of each selected product from the point total; update and store the point total in the non-transitory memory;halt display of the first set of redeemable products; and generate and output for display on the display device a second set of redeemable products, where the price of each product of the second set of redeemable products is equal to and / or less than the point total.

9. The computing device of claim 8, wherein calculating the trip score further comprises grouping two or more behavior statistics of the vehicle behavior data into a first set of behavior statistics, and dividing each of the behavior statistics of the first set of behavior statistics by a trip duration time.

10. The computing device of claim 9, where the instructions, when executed, cause the processor to sum the first set of weighted behavior statistics and subtract a sum of the first set of weighted behavior statistics from the maximum trip score.

11. The computing device of claim 8, where the instructions, when executed, cause the processor to add one or more behavior statistics, with a corresponding weight applied thereto, to the maximum trip score.

12. The computing device of claim 8, where the instructions, when executed, cause the processor to identify a score range that the trip score is in, and apply a number of points that corresponds with the score range.

13. The computing device of claim 12, wherein a number of points that are applied to the user profile decreases as the trip score decreases.

14. A vehicle operating system, comprising: a vehicle ignition system, including a vehicle ignition indicator; a sensor subsystem including at least one electronic control unit (ECU) configured to capture vehicle behavior data; a multi-command serial bus configured to direct control of a data bus to different message frames in response to a priority identifier of a message frame; a display device; a processor; anda non-transitory memory storing executable instructions that, when executed, cause the processor to: receive an ‘on’ indication from the vehicle ignition indicator; initiate collection of vehicle behavior data via the at least one ECU and send message frames containing vehicle behavior data from the sensor subsystem to the processor; apply a low priority identifier to message frames containing vehicle behavior data; receive message frames containing vehicle operating commands; apply a high priority identifier to message frames containing vehicle operating commands; in response to simultaneously receiving a message frame having the high priority identifier and a message frame having the low priority identifier, halting collection of vehicle behavior data and directing control of the data bus to message frames having the high priority identifier; and in response to receiving an ‘off indication from the vehicle ignition indicator, ending collection of vehicle behavior data.

15. The vehicle operating system of claim 14, wherein the multi-command serial bus is configured as a zonal architecture that accumulates multiple vehicle behavior data inputs from the sensor subsystem into a daisy-chained, one-to-one architecture.

16. The vehicle operating system of claim 14, further comprising a virtual private cloud network configured to provide communication between the multi-command serial bus, the sensor subsystem, and the processor.

17. The vehicle operating system of claim 14, further comprising executable instructions stored by the non-transitory memory and executable by the processor to: calculate a trip score using the vehicle behavior data by applying a weight to each behavior statistic of the vehicle behavior data, and subtracting weighted behavior statistics from a maximum trip score; determine a number of points, based on the trip score, to apply to a user profile; add the number of points to a point total of the user profile; store the point total; anddisplay a first set of redeemable products on the display device, where a price of each product of the first set of redeemable products is equal to and / or less than the point total.

18. The vehicle operating system of claim 17, further comprising: a user interface configured to receive user input including selection of one or more products of the first set of redeemable products; and where the display device configured to display a second set of redeemable products that includes one or more of the products of the first set of redeemable products and one or more products not included in the first set of redeemable products.

19. The vehicle operating system of claim 17, further comprising a cloud server that is communicably coupled to the multi-command serial bus, where the cloud server is configured to process, store, and archive vehicle behavior data to calculate the trip score and determine the number of points, based on the trip score, to apply to the user profile.

20. The vehicle operating system of claim 19, further comprising executable instructions stored by the non-transitory menion and executable by the processor to: transparently encry pt vehicle behavior data at a physical layer to be sent to the cloud server; and transparently encrypt vehicle behavior data at a network layer to be sent within a virtual private cloud (VPC).

Images