Scribd
Upload
29 views

Cloudnative

Uploaded by

Vibin V
Copyright
© © All Rights Reserved
Available Formats
Download as PDF or read online on Scribd
29 views

Cloudnative

Uploaded by

Vibin V
Copyright
© © All Rights Reserved
Available Formats
Download as PDF or read online on Scribd
You are on page 1/ 6
srt023, 439 PM (Cloud Native concept for Automotive Platform development — technalinchpin January 2, 2023January 2,,2023 Cloud Native concept for Automotive Platform development Automotive industry is witnessing and undergoing rapid transformation driven by increasing technology and user demands driven by Connectivity, Autonomous Shared and Electric vehicle solutions. This ubiq- uitous trend is challenging the age old followed Automotive Hardware and Software development model to progressively make a shift and adapt their vehicle architectures to advanced digital computing plat- forms driven by software enabled technologies . This is driving the industry to collaborate ,invent and standardize with efficient and effective practices to manage complex and large scale of software develop- ment, verification , validation ,deployment and maintenance cycles to enable and ensure the vehicles re- main safe, secure ,reliable and up-to-date with features ‘The automotive EEA upgrade is mainly reflected in three aspects: software architecture, hardware archi- tecture, and communication architecture. Software architecture will gradually realize hierarchical decou- pling, hardware will develop from distributed style to Domain controller/centralized style, and automo- tive network backbone will develop from LIN/CAN bus to Ethernet. It is expected that most OEMs will still use mixed-domain EEA, that is, part of functional domains will be centralized to form a transition solution of “distributed ECU + domain controllers” and finally forge an architecture of “super controller (central supercomputer) + zonal control Unit (zone controller)” From the perspective of OEM planning, autonomous driving domain, smart cockpit domain, and central control domain may become three main incremental domains. Software Defined Vehicles Seeing the benefits of domain controllers , the industry and ecosystem partners have taken a leapfrog ap- proach to build true software-defined vehicle (SDV) . The SDV will take the approach to consolidate the distributed vehicle control and management functions into the perimeter of high performance computing platform there by eliminating or reducing the EE architecture complexity to have many distributed and independent ECUs . However as the vehicles becomes more software centric software complexity will also increase from the perspective of software development, deployment and maintenance. Many well es- tablished and expert ecosystem innovators like Eclipse Foundation, Redhat, SuSE, Microsoft, Amazon who are widely experienced in the processes , methodologies and framework to manage complex ecosys- tem for extensive large scale distributed software development are part of this journey. Their involve- ment has accelerated the adoption of many proven technology solutions and practices from the cloud centric development arena to define a strong foundation for the SDV platform titps:Rechnolinchpin.wordpress.com/2023/01/02cloud-native-conceptfr-automotive-patform-development 16 sy1073, 439 PM lous Native concept for Automotve Platform development—teetnainehpin The key characteristic of this approach is to treat the “vehicle is almost an extension of the cloud”. Specifically, the software running on the car can be predominately controlled by a central runtime envi- ronment in the cloud adopting a “cloud-native” development model. This model in very simplistic terms consider to leverage the cloud technologies to realize end to end product development demands like de- ploying the development tools to build the software , integrate and deploy them in Virtual ECU models in cloud, where the Virtual ECU models replicates the target hardware architecture /configurations in cloud with the target specific OS and middleware solutions to deploy and verify these application in cloud hosted Virtual target ECUs before you plan to execute them in to the target hardware computing environ- ment used in bench/vehicle setups. When this becomes a reality you can see all the software development and testing and verification will by heavily driven by proven Cloud development technologies in virtual ECUs running in the cloud and fully validated software will be directly deployed to the real targets as live updates!. A first key technical enabler to implementing automotive cloud-native development is achieving environ- mental parity between cloud environments and the target embedded automotive edge platforms for eventually deploying the workload. This is a new concept to the automotive industry. So far most of the development and verification of automotive applications is dependent on the physical target hardware platform . It is thus quite logical to explore what it means to apply cloud-native concepts in the automo- live space such that the vast technical and commercial ecosystem developed around it can be leveraged to increased effectiveness and speed of innovation The technology enablers for SDV This is clearly the direction in which the industry is moving, but reaching the end goal requires some very specific technology. The constituent parts of the software-defined vehicle can be structured as multiple layers as shown 4 SA As AN —— QOUU DOE *High- >erformance Computer The bottom layer consists of the hardware and the electronic/electrical (E/E) architecture. The SDV approach to drive ECU consolidation into high-performance computers (HPCs). -ntps:technelinchpin.wordpress.com/2023/01/0Ziloud-native-concept-for-automative-platform-development/ 216 10728, 439 PM ‘oud Native concept fr Automotive Platiorm development -technalincpin Above this hardware is truly abstracted with Platforms Runtime & Middleware, and Operating System & Virtualization. Some automakers are branding their versions of these two layers, as seen with Volkswagen's vw.os and VolvoCars.OS. Essentially, this layer refers to the range of device operating sys- tems as well as any virtualisation. “These HPCs could have multiple device operating systems running on them, doing different things such as real-time operating system right next to a virtualized Linux OS that’s providing sensor and camera data processing via Adaptive AUTOSAR.” As for the Platforms & Middleware layer, the main function is to abstract the hardware from the software. Developers will want to make sure all the interfaces of a new feature are not directly tied to a specific hardware implementation or operating context. Above this the feature are built This software should all be implemented on top of the vehicle platform, and this makes it a much more updateable runtime. Often these applications are tied in with supporting cloud services, It includes ADAS services and over-the-air (OTA) services. Just below the cloud services layer shared services, referring to the supporting infrastructure such as 5G, V2X and OTA infrastructure, both in the cloud and in the car. SOAFEE — An Industry-led Initiative to Drive Cloud Native in Automotive One of the critical infrastructure requirements for cloud native automotive system development is the re- quirement for a variety of virtual system execution environments for development, integration, and vali- dation purposes that closely resemble the physical environment and that achieves, as much as possible SOAFEE initiative — Scalable Open Architecture for Embedded Edge. SOAFEE offers a cloud-native ar- chitecture enhanced for mixed-criticality for automotive applications, and will also provide an open- source reference implementation to enable commercial and non-commercial offerings. SOAFEE is being driven by an industry-led special interest group (SIG), which is defining the SOAFEE architecture based ‘on open standards and producing an open-source implementation. More information about this initiative can be found on the SOAFEE website. titps:echnolinchpin.wordpress.com/2023/01/02cloud-native-conceptfr-automotive-patform-development a8 510123, 4:38 PM Cloud Native concept for Automotive Platform development —technalinchpin [eamenin | [sessions | C= Jt S J a a The SOAFEE orientation is towards realizing systems through © Microservice oriented architecture © Containerization and © Orchestration in Edge devices SOAFEE platform baseline —A first Step Demo ‘The below figure shows the functional architecture of the prototype with distributed deployment of ser- vices in the ARM target and remote PC managed through the communication framework. The services use the platform provided logger services to stream the logs to ELK container endpoint which supports multi node real-time log consolidation, processing and analytics. een feast ‘The cloud native POC scope functional demonstration will details various technical aspects © Port and Configure the SOAFEE framework for container deployment and orchestration on ARM 64 bit platform. hips: Rechnotinchpin.wordpress.com/2023/01/02/clous-native-concept-for-automotive-platform-

You might also like