# Smart Collection of Real-Time Vehicular Mobility Traces
## 5 Morocco Traces  
From previous experiments involving models of mobility traces, they simply distribute a number of devices within a university campus, a conference, or a stadium without any controlling system. Nevertheless, these experiments were used as they provided remarkable feedback about the performance and possible improvements. For example, they noticed the high execution cost and the fact that there was no possibility of restoring devices after suffering a problem. In addition, it was not possible to identify the intended deployment problems, which cannot be detected while the experiment. For the proposed solution in the case of this paper, problems such as hardware resets, power consumption, and device breakdown are supervised and controlled by the administrator in real time. That is, a set of global information is continuously generated to guarantee the efficiency of the tracking server, as obviously shown in Figure 18.  
As mentioned before, our vehicle trace mobility model is entitled Morocco traces and was tested for seven months. We design the developed framework to obtain complete records that exactly reflect the real vehicular motions (real-time), solving any deployment problems (smart collection). Moreover, these traces can be further analyzed to extract a number of mobility features that affect the performance of the mobile network, such as the contact time, activity range, and visiting time. The overall information collected will contribute to obtaining and improving the mobility model. The framework is developed for vehicular mobility usage. However, it is also suitable for any other kinds of targets, such as human and animal motions. A set of reports that stores real traces is collected. Three of them are processed and interpreted at the main processing server to smooth vacant report tabs in our framework. Figure 19 depicts them as follows:  
Figure 18: Real-time reports. A dashboard screenshot showing the available real-time reports where the main reported information can be generated. * **History:** This represents the globally targeted traces. These reports show a general overview that represents the main objective and is the heart of our framework. This trace generates exactly a complete trace mobility model. They define a data set that records all registered events during the whole deployment and test period. It also depicts the vehicle identifier, brand, full timing, longitude, latitude, and current speed. We obtain a coherent report with any losses due to detecting, correcting and preventing in advance the most occurred deployed problems. Moreover, all of the developed functionalities are combined in order to achieve and enhance the most effective collection strategy. * **Traveling:** This is a sub-report of the \"Morocco traces\" system, which just records the traveling trajectories to and from predefined locations and includes the details of any event. * **Parking:** This is a sub-trace of \"Morocco traces\". It produces a log of all the information regarding the vehicle parks. Traveling and parking reports are obtained to verify the consistency and stability of the collected data set. These reports can be downloaded as text files or visualized as statistics. A comparative summary of the parameter details of some mobility traces and our proposed trace is outlined in Table 2.  
In the deployed test, the recorded trace corresponds to 36 vehicles in the first version of \"Morocco traces\". In the future, we aim to further extend our experiments using as many vehicles as possible, including heterogeneous ones. For this reason, as shown in Figure 20, we have developed a website with the aim of attracting more companies that would allow us to manage their transport fleets. (The website is available at: [[http://www.gps-maroc.ma/](http://www.gps-maroc.ma/)]([http://www.gps-maroc.ma/](http://www.gps-maroc.ma/))). An important number of mobile devices allows for deep testing and analyzing the server performances in terms of framework synchronization, speed treatment and data storage.