with the growth of the service-oriented architecture paradigm in the automotive industry, several middleware options have emerged, along with the widely known autosar adaptive platform. many powerful companies like zeekr are also looking to develop their own middleware for in-vehicle operating systems (os). zeekr implements multiple function clusters for such an in-vehicle operating system for smart evs. when we talk about how to develop software for soa or do the actual coding, the first thing that comes to mind is handwritten c language, which puts forward high requirements not only on the programmer's ability but also on the accompanying toolchain. in contrast, model-based design is the dominant approach in traditional onboard embedded system development and there are a lot of experienced engineers. starting with r2022a, simulink® provides some new features like a client-server interface, which enables modeling instead of handwriting soa software. companies can use the power of matlab® and simulink to quickly transition from the embedded software era to the emerging soa software era. there are two main challenges in using model-based design to develop soa software running on in-vehicle os: how to model the software behavior and how to maintain complex software clusters. this talk focuses on solving these two problems. zeekr made full use of the powerful capabilities of matlab and simulink for soa software development, formulated many strategies according to local conditions, and facilitated the implementation of soa application software running on in-vehicle os.
