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

Abstract

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.

Automotive Ethernet architecture and security: challenges and technologies

“…In addition, stringent timing requirements must be met: low latency, synchronization, and no noticeable jitter. Table 1 summarizes the numbers and types of sensors expected to be integrated into autonomous vehicle, and their bandwidth requirements [11]. In this paper, many studies on the security of TSNs were reviewed that aimed to enhance protocols, algorithms, and encryption mechanisms to ensure the security of IVNs, as well as architecture and integration issues.…”

“…2. The IVN fields and their subjects in the reviewed works Field Paper(s) Subjects Requirements of automotive TSN [6], [11], [12] List of requirements for future IVN processing platforms [13], [14] Integrate TSN with SDN with security [15] NDN [16] Graceful degradation for real-time autonomous vehicle applications [17] Improve the accuracy of the canvas [10] Reducing latency by porting it to Xronos [18] TSN-5G heterogeneous networks [19] HPVUs security [20] OTT Ethernet algorithm [21] Ethernet backbone with Zone based architecture [22] iDriving [45], [46] TSN PSFP, Protection of the TSN automotive Ethernet Security protocols for IVN [23], [24], [30], [35], [39] Review of blockchain and security attributes of IVN [34] IPSEC [36] Extensions to the SOME/IP protocol for securing SOME/IP service discovery [37] CANFD [25]- [29], [33], [38] Confidentiality, authentication, integrity [30]- [33] Blockchain in IVN [40] Structure-aware CAN Fuzzing procedure [41] Mitigations against an underactuated USV Intrusions detection systems for IVN [29], [42], [44], [47], [48], [53] Intrusion Detection Systems [49], …”

“…As noted in [11], the authors derived a list of requirements for future IVN processing platforms that must be met in order to satisfy the needs of the industry in the future. Two perspectives are used to analyze requirements: i) functional requirements, which define the functionalities or features the gateway (GW) controllers must support and ii) structural requirements, which describe the architectural and design aspects of the GW that are essential to its viability.…”

Resilient Raw Format Live Video Streaming Framework for an Automated Driving System on an Ethernet-Based In-Vehicle Network

“…Because an IVN is built on embedded devices, packet transmission and reception (i.e., Tx/Rx) operations are optimized with a fine-grained procedure due to limited system resources. In order to achieve optimization, a number of fast packet processing frameworks have been applied and tested in the IVN, such as the Data Plane Development Kit (DPDK) and eXpress Data Path (XDP) [19], [20]. The DPDK is a user space micro-kernel solution that can accelerate packet-processing speed by skipping the conventional Operating System (OS) kernel space [19].…”

“…In order to achieve optimization, a number of fast packet processing frameworks have been applied and tested in the IVN, such as the Data Plane Development Kit (DPDK) and eXpress Data Path (XDP) [19], [20]. The DPDK is a user space micro-kernel solution that can accelerate packet-processing speed by skipping the conventional Operating System (OS) kernel space [19]. Therefore, the DPDK has been extended with an HW extension and Smart Network Interface Controllers (NIC)s to achieve low-latency packet processing.…”