# Smart Collection of Real-Time Vehicular Mobility Traces
## 2 Related Works  
Researchers were constantly eager to understand realistic mobility behaviors of mobile networks. Diverse trace mobility models were collected over various time periods. In this section, we aim to present some traces that are previously implemented in a brief survey. **Cambridge [7]:** In this experiment, groups of users carried small devices iMotes with them for five days; most of them are students at the Computer Lab of Cambridge University, UK. Moreover, a number of fixed nodes are deployed at the most visited places around Cambridge city. The authors anticipate people to visit various locations like pubs, shopping centers, and marketplaces. Only 12 devices are successfully tracked at the first Cambridge trace due to losing some of the experimented iMotes, as well a lot of hardware problems have occurred. Where, these problems were not detected while deployment than analyzing records of retrieved devices. Only 12 devices are successfully tracked at the first Cambridge trace due to losing some of the experimented iMotes, as well a lot of hardware problems have occurred. Where, these problems were not detected while deployment than analyzing records of retrieved devices. **Intel [7]:** This data set contains users' Bluetooth sightings in Intel Research Cambridge Corporate Laboratory for about 6 days. They were distributed amongst researchers and staff which were represented as 'interns'. However, residual devices are recognized as 'externals'. 9 iMotes are correctly collected where node 1 was steady and iMotes from 2 to 9 were mobile. But, widely of traces set only 3 days. **Toronto [8]:** Researchers gathered Bluetooth traces in various urban environments with the aim of investigating the viability of a large-scale Bluetooth worm outbreak in practice. Devices were carried by students at Toronto University for 16 days. This data set was collected by activating Bluetooth on 23 Palm Tungsten-T PDAs with 16 MB of RAM and a PalmOS to scan Bluetooth devices. **ZebraNET [9]:** In this experiment, the recorded data represent the movement traces regarding two real scenarios of ZebraNet deployments at Sweetwaters Game Reserve of Nanyuki, Kenya. The first experiment was in January 2004 and the second was in summer 2005. The hardware of the sensor nodes was mainly composed of a MSP430 processor, flash memory, a radio interface module, and a GPS module. The collected data set used Unix Time-Stamp format and provided detailed information of animals location. **San Francisco Taxi Trace [10]:** The records obtained in this test included traces of 500 taxis in the San Francisco Bay area taken for 30 days. Each taxi is equipped with a GPS receiver which indicates the identifier, timestamp, and geo-coordinates. Cab mobility traces were provided by the Exploratorium during the cabspotting project development. **UMassDieselNet [11]:** This was also a vehicular DTN trace experiement which was implemented by the UMass Amherst branch of the Pioneer Vallet Transport Authority (PVTA). The collected data represent the daily run of 40 buses on the road. A bus scans other buses 100 times per second which uses an available (discovered) 802.11b radio access point (AP) to access the media and receive incoming \begin{table}
\begin{tabular}{c c c c c c} \hline \hline
**Name of Trace** & **Mobility Type** & **Number of Nodes** & **Duration (days)** & **Device Type** & **Network** \\ \hline Cambridge 1 [7] & Human & 12 & 5 & iMote & Bluetooth \\ Intel [7] & Human & 9 & 3 & iMote & Bluetooth \\ Toronto [8] & Human & 23 & 16 & PDA & Bluetooth \\ ZebraNet [9] & Animal & 100 & 365 & GPS & GPRS \\ SanFrancisco [10] & Vehicle (Taxi) & 500 & 30 & GPS & GPRS \\ UMassDieselNet [11] & Vehicle (Taxi) & 40 & 60 & Ha-Com Open Brick with AP & 802.11b \\
**Morocco Traces** & **Vehicle (heterogeneous)** & **36** & **210** & **GPS** & **GPS** \\ \hline \hline \end{tabular}
\end{table} 
Table 2: Comparative summary of previous trace models and Morocco traces. connections while they are in the AP coverage range.