# BSM-Data Reuse Model Based on In-Vehicular Computing
## 1 Introduction
As presented in Figure 1 from Prepio ([[https://premioinc.com/pages/in-vehicle-fanless-computer](https://premioinc.com/pages/in-vehicle-fanless-computer)]([https://premioinc.com/pages/in-vehicle-fanless-computer](https://premioinc.com/pages/in-vehicle-fanless-computer))), today's vehicle computing solutions propose complete models for all requirements of in-vehicle computing and offer industrial-grade in-vehicle computers. Consequently, intelligent transportation systems are required in order to shift to mobile computing technology for the flexibility that they need to meet the daily challenges of demanding connected and autonomous vehicles applications. Dedicated Short Range Communication (DSRC) protocol has been adopted as a leading communication standard in the U.S., for establishing an advanced connected vehicle network and supporting traffic efficiency and safety, along with SAE J2735 as a primary standard to provide V2X data guidelines for deploying applications for DSRC-enabled connected vehicle. Actually, the DSRC and SAE-J2735 together grant the potential to exchange safety data wirelessly and very effectively using what is presented as basic safety messages (BSM) [1; 2; 3]. This commonly referred to as the \"heartbeat\" message, is nominated as the main data set used to continuously exchange safety data between connected vehicles. Over real-time exchange of this safety message, CV applications are able to discover and determine perilous situations. They can then inform drivers of the expected danger before it occurs or automatically acts toward impending incidents using vehicle control systems. Historically speaking, the primary purpose of the U.S. CV program was to enhance road safety by aiding vehicle-to-vehicle safety applications making the right decisions. Nevertheless, generating data for transport agencies while using connected vehicles is, by design, a very important secondary  
Figure 1: In-vehicle-fanless-computer. principle. A great deal of the ongoing research under the mentioned program is oriented towards such data-providing applications. In this respect, BSMs frequently generated from multiple connected vehicles can play a primordial role in providing transport data see credible and reliable information that they contain. Otherwise, when considering the way BSMs are treated, multiple deficiencies prevent the latter to be capable of constituting a precious connected vehicle data source. First: presently, the basic safety messages are particularly even exclusively used for the safety purpose. In contrast, a big bundle of its data elements are necessary for a considerable collection of applications not related to safety. At least, the BSM Part 1 data elements can conveniently provide basic vehicle information required by several applications. Arguably helpful, safety, mobility, and efficiency are not a separated aspects. Obviously, traffic accidents can breed Traffic congestion and increase CO2 emission. Next: BSMs as safety data are overall regarded as snapshot data that give an idea of the state of the system at a definite time. From the first use, the BSM becomes outdated, useless, and is deleted. Undoubtedly, BSMs collected from multiple connected vehicles can be cached, grouped and stored to construct continuous data streams that can supply almost real-time metrics while they evolve over space and time. Indeed, data are then exploited in a better-connected form to improve safety, decrease fuel consumption, reduce traffic jams, as well as facilitate people's travel overall. Finally: as is well known, safety applications between vehicles require local broadcast of BSM within the limits of the DSRC. Even though, connected vehicles using applications are required to enable an extra-vehicular data exchange to permit collaborative sensing and action at scale. Thus, if transmitted according to different technologies other than DSRC such as Cellular V2X, continuous data obtained through BSMs processing can widely feed applications with requested vehicle information [4].