Luxembourg SUMO Traffic (LuST) Scenario: 24 hours of mobility for vehicular networking research

Abstract

Abstract-Different research communities varying from telecommunication to traffic engineering are working on problems related to vehicular traffic congestion, intelligent transportation systems, and mobility patterns using information collected from a variety of sensors. To test the solutions, the first step is to use a vehicular traffic simulator with an appropriate scenario in order to reproduce realistic mobility patterns. Many mobility simulators are available, and the choice is usually done based on the size and type of simulation required, but a common problem is to find a realistic traffic scenario. In order to evaluate and compare new communication protocols for vehicular networks, it is necessary to use a wireless network simulator in combination with a vehicular traffic simulator. This additional step introduces further requirements for the scenario. The aim of this work is to provide a scenario able to meet all the common requirements in terms of size, realism and duration, in order to have a common basis for the evaluations. In the interest of building a realistic scenario, we decided to start from a real city with a standard topology common in mid-size European cities, and real information concerning traffic demands and mobility patterns. In this paper we show the process used to build the Luxembourg SUMO Traffic (LuST) Scenario, and present a summary of its characteristics together with an overview of its possible use cases.

Scalable & Resilient Vehicle-Centric Certificate Revocation List Distribution in Vehicular Communication Systems

“…We use OMNET++ [69] and the Veins framework to simulate a large-scale scenario using SUMO [70] with a realistic mobility trace, the LuST dataset [71]. For the cryptographic protocols and primitives (Elliptic Curve Digital Signature Algorithm (ECDSA)-256 and SHA-256 as per IEEE 1609.2 [4] and ETSI [1]), we use OpenSSL.…”

Getting the Most Out of Your VNFs: Flexible Assignment of Service Priorities in 5G

“…We leverage the real-world mobility trace [21], to assign user density and request rates. Focusing on a downtown intersection, we consider that (i) all vehicles within 50 m from the intersection are users of the ICA service, and send a CAM every 0.1 s; (ii) all vehicles within 100 m from the intersection are users of the CT service, and send a request (i.e., refresh their video) every 200 ms; (iii) a total of 200 sensors are deployed in the area, each generating, according to the traffic model described in the 3GPP standard [22], one request Finally, we assume that the PoP contains 10 VMs, each of which can be scaled up to at most C(m) = 1000 units, and each associated with fixed and proportional costs of κ f = 1000 units and κ p = 1 unit, respectively.…”

Scaling pseudonymous authentication for large mobile systems

“…or 3 minutes (τ P =172.8 sec), respectively. According to actual large-scale urban vehicular mobility dataset, e.g., Tapas-Cologne [86] or LuST [40], the average trip duration is within 10-30 minutes. Moreover, according to the US DoT, the average daily commute time in the US is around 1 hour [1].…”