In-car Gateway Architecture for Intra and Inter-vehicular Networks

Hbaieb, Amal; Rhaiem, Olfa Ben; Fourati, Lamia Chaari

doi:10.1109/iwcmc.2018.8450344

Cited by 14 publications

(3 citation statements)

References 8 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The PDU Router exchanges communication messages with the upper layer (Runtime Environment) which interacts with the Application Layer. As an example, authors in [88], propose a software stack for the management of internal and external communications of the vehicle based on the AUTOSAR Classic architecture. There are several examples of automotive specific MCUs in the market which implement the AUTOSAR Classic software stack, e.g.…”

Section: ) Autosar Sw Architecturementioning

confidence: 99%

The Future Roadmap of In-Vehicle Network Processing: A HW-Centric (R-)evolution

2022

View full text Add to dashboard Cite

The automotive industry is undergoing a deep revolution. With the race towards autonomous driving, the amount of technologies, sensors and actuators that need to be integrated in the vehicle increases exponentially. This imposes new great challenges in the vehicle electric/electronic (E/E) architecture and, especially, in the In-Vehicle Network (IVN). In this work, we analyze the evolution of IVNs, and focus on the main network processing platform integrated in them: the Gateway (GW). We derive the requirements of Network Processing Platforms that need to be fulfilled by future GW controllers focusing on two perspectives: functional requirements and structural requirements. Functional requirements refer to the functionalities that need to be delivered by these network processing platforms. Structural requirements refer to design aspects which ensure the feasibility, usability and future evolution of the design. By focusing on the Network Processing architecture, we review the available options in the state of the art, both in industry and academia. We evaluate the strengths and weaknesses of each architecture in terms of the coverage provided for the functional and structural requirements. In our analysis, we detect a gap in this area: there is currently no architecture fulfilling all the requirements of future automotive GW controllers. In light of the available network processing architectures and the current technology landscape, we identify Hardware (HW) accelerators and custom processor design as a key differentiation factor which boosts the devices performance. From our perspective, this points to a need -and a research opportunity -to explore network processing architectures with a strong HW focus, unleashing the potential of next-generation network processors and supporting the demanding requirements of future autonomous and connected vehicles.

show abstract

Section: ) Autosar Sw Architecturementioning

confidence: 99%

The Future Roadmap of In-Vehicle Network Processing: A HW-Centric (R-)evolution

2022

View full text Add to dashboard Cite

show abstract

“…Vehicular ad hoc networks (VANETs) 1 have known a significant development from network and system perspectives. On the one hand, modern vehicles are equipped with multiple interfaces that ensure the intervehicle and vehicle to infrastructure communications 2 . On the other hand, various capacities are available inside vehicles (eg, computing, sensing) that enable services for drivers and passengers.…”

Section: Introductionmentioning

confidence: 99%

“…On the one hand, modern vehicles are equipped with multiple interfaces that ensure the intervehicle and vehicle to infrastructure communications. 2 On the other hand, various capacities are available inside vehicles (eg, computing, sensing) that enable services for drivers and passengers. The expansion of the range of the provided services was followed by the emergence of many challenges related to the resource requirements and the quality of service (QoS) constraints.…”

Section: Introductionmentioning

confidence: 99%

Software‐defined networking in vehicular networks: A survey

Mekki¹,

Jabri

Rachedi

et al. 2021

Trans Emerging Tel Tech

View full text Add to dashboard Cite

Software‐defined networking (SDN) is a new paradigm that consists in decoupling the control plane from the data plane, which offers the flexibility of configuring and managing networks. Recently, an extension of SDN to vehicular ad hoc networks (VANETs), named software‐defined vehicular networks (SDVN), has been emerged to expand the capabilities of VANET in terms of the provided services and to overcome the VANET issues. Also, SDN has gained a lot of interest to be involved in the extensions of VANET, which are vehicular cloud and vehicular fog. In this paper, we overview the use of SDN in VANET. We survey its deployment in the classic vehicular networks, 5G‐VANET, vehicular cloud, and vehicular fog. Thereafter, we discuss some case studies of SDN in the vehicular context. Then, we present a taxonomy of the existing architectures followed by the major challenges in the implementation of SDN in the vehicular context. Next, we review the tools used to simulate SDN‐based VANET scenarios. Finally, we give some future research directions.

show abstract