{'fraction_non_alphanumeric': 0.02211126961483595, 'fraction_numerical': 0.0, 'mean_word_length': 5.1535087719298245, 'pattern_counts': {'":': 0, '<': 0, '<?xml version=': 0, '>': 0, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
Practical experiences on a communication middleware for IP-based in-car networks

Current in-car communication networks are based on automotive specific technologies like CAN, FlexRay and MOST and use proprietary communication protocols. While CAN and FlexRay come with a signal-based communication paradigm, MOST provides a more sophisticated interface based on "function blocks" to the application programmer. In the next years, we expect IP-based protocols and standard technologies like Ethernet to be deployed for more and more in-car communication tasks. As a result, we need an IP-based communication middleware that provides both signaland function-based interaction paradigms and works for all distributed applications in vehicles. Main challenges are the large variety of embedded devices and operating systems used in a single car in terms of footprint and compute power. Furthermore, it must be possible to migrate existing interface definitions from legacy technologies to the new IP-based solution. In this paper, we propose an IP-based in-car middleware framework based on an open source solution, Apache Etch. We sketch how different, yet interoperable versions of the middleware can be used to construct a scalable system that fits to both small and large devices. Finally, we identify extensions to Etch that are necessary to qualify the solution for the use in the automotive domain.