|
One possibility would be to use Google proto buffers over SLIP. Lots of ideas in this space but free few implementations. I tried experimenting with MIN (oss IPC stack) but it didn't meet the great with respect to robustness; but most of the sauce was available
to look at. I also tried LWIP but this has serious issues with regard to traffic prioritization and overhead, both could, member and packet, but it sure is tempting to use udp and or TCP to enable security and toe in with sockets on the remote host.
From: Fulup Ar Foll <fulup.arfoll@xxxxxxx>
Sent: Wednesday, April 10, 2019 5:10:59 PM To: Shufro, Eric; Sachin Gwasikoti; automotive-discussions@xxxxxxxxxxxxxxxxxxxxxxxxx Subject: Re: Project Ideas for AGL Eric,
This is almost exactly the subject of the talk I proposed for ALS this summer (see abstract here after).
Fulup
AGL-µBinder : a fast, secure and seamless option to connect AGL to small ECUs? In order to embrace the global automotive ecosystem, AGL micro-services architecture should support not only all Linux in a car, but also seamlessly retrieve data from small ECUs and securely send collected information to the cloud. Because of existing application framework dependencies, as today, AGL bindings run only on Linux. In order to extend to global automotive ecosystem, AGL’s binders/bindings architecture needs to be reviewed. On one hand, remove Linux’s systemD dependencies and extend security model. On a second hand, support ‘alien’ transport protocols including non TCP/IP ones. This talk presents the lesson learned from a POC to run a subset of current AGL binder onto a micro-controller with Zephyr. How to solve binder/binding dependencies, how to map the transport onto a non TCP/IP link, how to extend AGL security model, ... On 10/04/2019 01:02, Shufro, Eric wrote:
|
_______________________________________________ automotive-discussions mailing list automotive-discussions@xxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linuxfoundation.org/mailman/listinfo/automotive-discussions
