Open Source Summit + AI_dev Japan 2024

VirtIO, a widely adopted device virtualization technology, is becoming increasingly important in the trend of Software-Defined Vehicles. It decouples operating systems from physical devices, paving the way for hardware agnostic software to function seamlessly across diverse environments, be it cloud-based or on various automotive edges. In this presentation, we'll be taking a deep-dive into the technical essences of VirtIO-based device virtualization. We will also explore how to leverage this technology to build and deploy the same Automotive Grade Linux (AGL) virtual machine binary on both cloud and automotive hardware platforms. This session is recommended for developers and architects looking to gain a comprehensive understanding of VirtIO and its practical applications in an automotive cloud-native environment. By attending, you will gain valuable insights into how to achieve environment parity using VirtIO, and understand its vital role in the future of Software-Defined Vehicles.

we would like to share with audience about volvo cars' open source journey, and how we drive open source maturity within Volvo Cars.

As SDV gains popularity, the importance of edge orchestration is being addressed. However, the automotive oriented limitation makes this pursuit difficult, as cloud-native technologies sometimes might not be so suitable in such context.

In this session, I'd like to highlight our case with the years of building AosEdge (https://aosedge.tech/), where we started from noticing the need of vehicle-limitation-oriented orchestration tool, enabling mixed-criticality orchestration with unikernel realized by Zephyr RTOS and Xen hypervisor, and then on to adhering the operational scalabity needed from industry perspectives.

Especially, the dynamic rebalance in multi-node vehicle environment opens more possibilities foreseeing the upcoming SDV era, where user experience demand would increase while the vehicle resource would still be limited to some extent.

This session would be inspired by EPAM's Artem Mygaiev's previous presentations, adjusted to the local/global audience, with latest activity updates.

The AGL vehicle to cloud (V2C) expert group has been working for the past year towards the creation of a Vehicle Signal Specification (VSS) to MQTT proxy. This presentation will walk through the architecture and features of the new agl-vss-proxy daemon, as well its integration into the gateway demo that was shown at Embedded World 2024.

Some of the most common license compliance policies violations in automotive are related to specific black listed OSS licenses. Ideally, code under such licenses should be detected during the inbound process. Commercial SCA solutions are the default option in automotive to address this challenge. We need solutions that can be shared in both, commercial environments and in the open. This tutorial will demonstrate how any organization can build their own knowledge base linked to a specific license compliance policy, such as preventing GPLv3 code from landing onto an in-vehicle platform. Julián will also show how to create license scanning and detection mechanisms against such ad-hoc knowledge base during the inbound process, using OSS only. It will also provide solutions on how companies in the automotive supply chain, including open-source organizations, can share and audit the results using this common toolkit and knowledge base. Additionally, the talk will illustrate how this approach can be generalized for broader use cases, with limited usage intensity, using the OSS KB, from the Software Transparency Foundation. OSS KB: https://www.softwaretransparency.org/osskb

[ How to extend AD Sensors to IVI Domain ] 1. Why we extend AD sensors to IVI Domain Can you image that AD sensors can be safely and securely used for IVI Domain, as well as Autonomous Driving ? 2. 3rd party eco system on AD Vehicle AD vehicle has more sensors then the one of smartphone, using them, we can create the more rich application in AD vehicle. 3. E/E Architecture and HPC for the future The communication between SoCs in HPC needs to have very high performance bus, and, now PCI Express is the best candidate. 4. Sensor Sharing and Functional Safety Ghost Device cannot control the physical sensor directly. So, basically there is no way for the cracker to make the high-level Security System harmful. 5. The concept of Ghost Device When numbers of SoC are weaved, a SoC needs to deal with another SoC as a kind of peripheral, because SoC is generally designed as a host of whole system. So, we need to define another SoC as a kind of peripheral, or abstract and emulate data from another SoC as one from peripherals. 6. How to implement it Using ntb_transport, NTRDMA, and ,Infiniband core, Ghost Device is implemented. 7. The example, Camera Sensor (demonstration is ready)