{"title":"在汽车Linux信息娱乐系统中添加Android功能:可用的虚拟化技术","authors":"Srdjan Usorac, Dejan Bogdanović, Dario Perić, Ž. Lukač","doi":"10.1109/TELFOR52709.2021.9653406","DOIUrl":null,"url":null,"abstract":"People use Android applications to perform everyday activities. That is why the most common In-Vehicle Infotainment (IVI) consumer requirement is the support for user-attractive Android applications. However, many Original Equipment Manufacturers (OEMs) have developed their automotive IVI domain based on Linux OS. A few years ago, Google started to develop Android Automotive as an Android-based solution for the automotive IVI domain. Because of competition, the automotive industry is looking for different ways of adding support for Android applications. But having Android applications in an already present Linux is not an easy task considering the amount of effort put in establishing noticeable UI/UX features. This paper gives an overview of two software-based virtualization solutions for adding support for Android applications on an already running Linux IVI domain. The solutions are hypervisor technology, already used in production, and container technology, a relatively new approach in the automotive. Both solutions are deployed on the same automotive-grade platform to preserve the same test conditions. The memory consumption is evaluated between a specific hypervisor and container runtime solution. The paper concludes that it is better to use container technology to add Android support to systems where memory usage by several Android applications is not known in advance.","PeriodicalId":330449,"journal":{"name":"2021 29th Telecommunications Forum (TELFOR)","volume":"26 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"2021-11-23","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"0","resultStr":"{\"title\":\"Adding Android capabilities in automotive Linux infotainment: available virtualization technologies\",\"authors\":\"Srdjan Usorac, Dejan Bogdanović, Dario Perić, Ž. Lukač\",\"doi\":\"10.1109/TELFOR52709.2021.9653406\",\"DOIUrl\":null,\"url\":null,\"abstract\":\"People use Android applications to perform everyday activities. That is why the most common In-Vehicle Infotainment (IVI) consumer requirement is the support for user-attractive Android applications. However, many Original Equipment Manufacturers (OEMs) have developed their automotive IVI domain based on Linux OS. A few years ago, Google started to develop Android Automotive as an Android-based solution for the automotive IVI domain. Because of competition, the automotive industry is looking for different ways of adding support for Android applications. But having Android applications in an already present Linux is not an easy task considering the amount of effort put in establishing noticeable UI/UX features. This paper gives an overview of two software-based virtualization solutions for adding support for Android applications on an already running Linux IVI domain. The solutions are hypervisor technology, already used in production, and container technology, a relatively new approach in the automotive. Both solutions are deployed on the same automotive-grade platform to preserve the same test conditions. The memory consumption is evaluated between a specific hypervisor and container runtime solution. The paper concludes that it is better to use container technology to add Android support to systems where memory usage by several Android applications is not known in advance.\",\"PeriodicalId\":330449,\"journal\":{\"name\":\"2021 29th Telecommunications Forum (TELFOR)\",\"volume\":\"26 1\",\"pages\":\"0\"},\"PeriodicalIF\":0.0000,\"publicationDate\":\"2021-11-23\",\"publicationTypes\":\"Journal Article\",\"fieldsOfStudy\":null,\"isOpenAccess\":false,\"openAccessPdf\":\"\",\"citationCount\":\"0\",\"resultStr\":null,\"platform\":\"Semanticscholar\",\"paperid\":null,\"PeriodicalName\":\"2021 29th Telecommunications Forum (TELFOR)\",\"FirstCategoryId\":\"1085\",\"ListUrlMain\":\"https://doi.org/10.1109/TELFOR52709.2021.9653406\",\"RegionNum\":0,\"RegionCategory\":null,\"ArticlePicture\":[],\"TitleCN\":null,\"AbstractTextCN\":null,\"PMCID\":null,\"EPubDate\":\"\",\"PubModel\":\"\",\"JCR\":\"\",\"JCRName\":\"\",\"Score\":null,\"Total\":0}","platform":"Semanticscholar","paperid":null,"PeriodicalName":"2021 29th Telecommunications Forum (TELFOR)","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1109/TELFOR52709.2021.9653406","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
Adding Android capabilities in automotive Linux infotainment: available virtualization technologies
People use Android applications to perform everyday activities. That is why the most common In-Vehicle Infotainment (IVI) consumer requirement is the support for user-attractive Android applications. However, many Original Equipment Manufacturers (OEMs) have developed their automotive IVI domain based on Linux OS. A few years ago, Google started to develop Android Automotive as an Android-based solution for the automotive IVI domain. Because of competition, the automotive industry is looking for different ways of adding support for Android applications. But having Android applications in an already present Linux is not an easy task considering the amount of effort put in establishing noticeable UI/UX features. This paper gives an overview of two software-based virtualization solutions for adding support for Android applications on an already running Linux IVI domain. The solutions are hypervisor technology, already used in production, and container technology, a relatively new approach in the automotive. Both solutions are deployed on the same automotive-grade platform to preserve the same test conditions. The memory consumption is evaluated between a specific hypervisor and container runtime solution. The paper concludes that it is better to use container technology to add Android support to systems where memory usage by several Android applications is not known in advance.