Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Add protobuf bullet, and links

...

  • Investigation point:  VISSv2 with MQTT as "transport" - is there a possible compatibility?
  • General (MQTT and other):  Binary data representation to optimize compared to VISS-JSON transport.
    • ...use also as variant encoding in VISS?
    • ...use as independent protocol (not part of VISS spec)
  • AUTOSAR Adaptive compatibility
    • SOME/IP is important so we cannot ignore it.
    • DDS also.
    • (However, ARA:COM abstracts the technolgies.  For AUTOSAR systems, generating ARA:COM XML format is enough, the rest follows.  For non-AUTOSAR systems that are going to communicate with AUTOSAR systems, however, something that implements the concrete chosen protocol is needed. 
    • Opinion:  SOME/IP is used in a very static way – an alternative might be desirable.
    • (AUTOSAR) RESTful services (not HTTP, rather stateless principle, get, set etc.) → Only discussions currently, no drive?
      • How is this concrete protocol defined?
      • Bosch might be willing to work on this.
  • Protobuf conversion → Main page
    (because it is used and preferred by SENSORiS, but is also generally popular, and there was a recent vspec2proto converter proposal in vss-tools)


A lot of communication related technologies were investigated in the Generic Protocol Evaluation project during 2019.
A set of reference links are here : List of relevant technologies


...

MQTT-tool



Notes


...

AUTOSAR


Current tool chain   

...