# BSM-Data Reuse Model Based on In-Vehicular Computing
## 5 Study Case: In-Vehicle BSM Data Services Platform
### Data Delivery
#### 5.3.3 Simulation and Discussion  
To check out how the API is getting vehicle data behaves, we simulate vehicle trips according to the following steps:  
* Step 1: Creating a trip: the first step in our simulating trip data is to configure a route. The starting and ending location may be anywhere. However, our available dataset is limited to Ann Arbor, Michigan, as illustrated in Figure 12. Our trip runs 12.67 miles from the start point at: \"S State St, Ann Arbor, MI 48108, USA\" to the endpoint at: \"M-14, Ann Arbor, MI 48105, USA\". Immediately after we inputted the starting and ending location, we will notice in Figure 12, that the map will provide a visual representation of the driver's route.
* Step 2: Configure Events: we may select different events to simulate during each test run. The events might occur a couple times within the test but will always occur at least once. At present, we have three available events shown in the Figure 12, bellow.
* Step 3: Run the Simulation: as depicted in Figure 13, once the simulation begins, you will automatically see data coming in every 3 s within the \"Point Dataset\" tab located on the left side. The vehicle will progress within its route and indicate the location of the driver. Once an event takes place, a small circle will appear on the map. Additionally, the Point dataset timestamp will have a red dot next to it to indicate an event took place at this time. As To see a list of all the events that took place during the simulation, press the \"Events\" tab located on the left side.  
\begin{table}
\begin{tabular}{l l l} \hline \hline
**Data Delivery Method** & **Real Time/Historical** & **Push/Pull** \\ \hline Streaming & Real-time & Push \\ Historical Data Reports & Historical & Pull \\ Events & Real-time & Push \\ \hline \hline \end{tabular}
\end{table}
Table 10: Data delivery methods key attributes.  
\begin{table}
\begin{tabular}{l l l l} \hline \hline
**API** & **Request Type** & **Time Frame** & **Description** \\ \hline Raw Data & BSM data & Up to 1 month & Provides data points from all the BSMs associated with a specific service \\ \hline Aggregated & Aggregated & Up to 1 month & Provides aggregated data on the various trips vehicles have driven \\ \hline Trip Points & BSM Data & Length of trip & Provides data points from a specific trip a vehicle has driven \\ \hline \hline \end{tabular}
\end{table}
Table 11: Available historical data APIs.  
Previous photos (Figures 12 and 13) show the Importance of maintaining and making BSM data available through multiple delivery methods. Hot data are real-time delivered over a continuous streaming mechanism, while cold data are diffused at regular intervals to increase their value and utility. Undoubtedly, cold data may not be valuable for traffic safety applications as collision avoidance applications, but it may be useful in other applications, such as those that are related to road planning. The following gains can be achieved to name but a few:  
1 It gives data consumers the possibility of remotely reuse BSMs data.
2 It also allows developers to begin developing their applications without actually having any connected vehicles.
3 Real-time traffic information and navigation services and apps can use APIs to highlight areas of congestion and help drivers to find the fastest routes.  
Figure 12: Simulation configuration.  
Figure 13: Simulation results.