In this study, we propose a variation of the RAdNet for vehicular environments (RAdNet-VE). The proposed scheme extends the message header, mechanism for registering interest, and message forwarding mechanism of RAdNet. To obtain results, we performed simulation experiments involving two use scenarios and communication protocols developed from the Veins framework. Based on results obtained from these experiments, we compare the performance of RAdNet-VE against that of RAdNet, a basic content-centric network (CCN) using reactive data routing, (CCN @math ), and a basic CCN using proactive data routing, CCN @math . These CCNs provide non-cacheable data services. Moreover, the communication radio standards adopted in the scenarios 1 and 2 were respectively IEEE 802.11n and IEEE 802.11p. The results shown that the performance of the RAdNet-VE was superior to than those of RAdNet, CCN @math and CCN @math . In this sense, RAdNet-VE protocol (RVEP) presented low communication latencies among nodes of just 20.4ms (scenario 1) and 2.87 ms (scenario 2). Our protocol also presented high data delivery rates, i.e, 83.05 (scenario 1) and 88.05 (scenario 2). Based on these and other results presented in this study, we argue that RAdNet-VE is a feasible alternative to CCNs as information-centric network (ICN) model for VANET, because the RVEP satisfies all of the necessary communication requirements.
Wang @cite_18 presented a CCN architecture, but did not consider which applications or events would significantly affect its design. Moreover, the proposed architecture cannot be used efficiently in applications based on vehicle-to-vehicle communications. Wang @cite_25 also proposed a packet dissemination mechanism to reduce the latency of content delivery. This mechanism employed timers to coordinate the packet sending among the network nodes. However, the proposal of the mechanism did not establish the limits of interest dissemination within a geographical area. Thus, the flooding problem persisted. Finally, their evaluation did not consider how the mobility of the nodes would impact the proposed mechanism.
@cite_18 @cite_25
1988342793 2014952121
Vehicular networking is becoming reality. Today vehicles use TCP IP to communicate with centralized servers through cellular networks. However many vehicular applications, such as information sharing for safety and real time traffic purposes, desire direct V2V communications which is difficult to achieve using the existing solutions. This paper explores the named-data approach to address this challenge. We use case studies to identify the design requirements and put forth a strawman proposal for the data name design to understand its advantages and limitations. Network use has evolved to be dominated by content distribution and retrieval, while networking technology still speaks only of connections between hosts. Accessing content and services requires mapping from the what that users care about to the network's where. We present Content-Centric Networking (CCN) which treats content as a primitive - decoupling location from identity, security and access, and retrieving content by name. Using new approaches to routing named content, derived heavily from IP, we can simultaneously achieve scalability, security and performance. We implemented our architecture's basic features and demonstrate resilience and performance with secure file downloads and VoIP calls.