JOIN/SIGN UP
Already a Member? |
GET INVOLVED
Understanding and Engaging in COVESA Expert Groups & Projects |
COLLABORATIVE PROJECTS
HISTORICAL
SDV Telemetry Project - On Hold |
We use cookies on this site to enhance your user experience. By using this site, you are giving your consent for us to set cookies. |
LINKS: [Tech stack meeting minutes]
Launch active development projects on key components:
1. "Second" VISS v2 implementation (in addition to GoLang implementation)
2. Demonstration of VSC-based development with Seats Service as example
3. Proposal: Make the "efficient binary encoding" of VSS payloads (as a reusable implementation)
The Technology Stack development is one of three main tracks of the Common Vehicle Interface Initiative
Goal of this activity:
Find/Develop/Define attractive technology solutions that can be used with the industry-common model for data+services.
The term Technology Stack is used to describe all software that is related to the transfer and use of data and services that adhere to the common model(s).
Examples:
Converters and Code Generators
Note: The purpose of the technology stack is to lead us (the automotive industry) towards a limited selected set of solid core technologies.
A table like this might look like a anything-to-anything conversion, but it should be clear that the goal is not to create that – only to make sure there are solutions for technologies that are strongly desired, or unavoidable legacy.
Input | Output | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
VSSo | JSON (VSS definition in alternative format) | Protobuf (VSS/message definition in alternative format) | gRPC | GraphQL (Schema, Apollo format) | ARA:COM (XML) | SOME/IP (code generation, vSomeIP stack) | CommonAPI (enables backends vSOMEIP and others) | DDS (code generation) | Android Vehicle-Properties (mapping via code generation) | Franca IDL (standard) | |
VSS → x | vspec2vsso | vspec2json | vspec2protobuf | Ongoing support in KUKSA.VAL | 1) vspec2graphql | WIP TietoEvery Ongoing discussions. VSS formatted data to/from AUTOSAR systems? | 1) Via Common API capicxx-someip → see next cell | BMW considering releasing vss-2-commonapi generation tools? | Evaluate interest | Ongoing Mapping/plan exists. | Proposal, needs update. vspec2franca |
VSC → x | N/A | N/A | N/A: gRPC is the corresponding protocol. | Evaluate interest | Useful candidate for the "W3C RPC protocol" to carry VSC services. | 1) Std Franca ↔ARA:COM via FARACON (needs maintenance) 2) Possibly new implementation for VSC language? | TODO, obvious mapping. | Via Std Franca IDL → Common API tools. Those tools take standard Franca as input | Evaluate interest | N/A | Definitely planned TODO. because |
Communication protocols / bindings
Completion of technology definition / implementation | |||||
---|---|---|---|---|---|
VISS (data) | MQTT (data) | Kafka | Spark (is an analytics engine, but implementing the data ingestion part and showing analytics on data that came from VSS format) | NiFi | W3C-RPC* (services) |
Full GoLang implementation Other implementations? >> A request for C++ implementation came up (compiler support in some embedded system) | TODO See working page | TODO Evaluate interest | TODO Evaluate interest | TODO Evaluate interest | Pending analysis of VSC/interface language |
Frameworks and Databases and Processing
(Ideally these initiatives are after analysis combined into a single consistent architecture?)
Completion of technology definition / implementation | ||||
---|---|---|---|---|
IoT-event-analytics / VehicleEdge | KUKSA.VAL (part of IoTea) | AOS | CCS Reference Architecture and PoC | Other? |
| Analysis starting | In large parts done, but details remaining and constantly evolving |
Historical / preparation information.
Initial Brainstorm, implementation ideas
Which technologies come immediately to mind?
VSC to code generation
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
Current tool chain
(RED is not existing or not yet clearly defined). (The rest exists already)
Notes
Going via Franca is complicated... → VSS/VSC to AUTOSAR directly makes sense
Direct approach for AUTOSAR