The intention of this project is to produce a prescriptive specification for the production, consumption and orchestration of messages between connected vehicle devices and the cloud using MQTT and Protocol Buffers, inclusive of recommendations for vehicle identity, security and system architecture. The message definitions in this project should align to message definitions in the kuksa.val gRPC project.
Documentation of recommended basic practices for MQTT V5 based vehicle to cloud communication patterns. Each of the items below can be worked on independently, with the exception of creating the reference applications and simulation, which is dependent upon at least one set of messages being finalized. HVAC will take priority.
The project currently uses Gradle to build message stubs in Java and C++ and generate documentation.
This potentially pre-exists from another project
Also include vehicle applications/services for connectivity and communication, such as Paho, AWS IoT SDK
Ask | Description | Net Result | Dependency | Estimated Effort (including testing integration) |
Vehicle Identity Service | Programmatic and secure method of producing a vehicle identity that doesn’t expose VIN in plain text | A service or library built into AGL that enables the generation of a secure identity for the vehicle, acting as a proxy for the VIN. Ideally this would be a hash+SALT of the VIN itself and provide both security and privacy compliance. | None | 0 - It seems this is already being produced by other workstreams |
UUID Service for Messages | A simple UUID service for producing non-repeating message IDs for use in publishing mqtt messages | A service or library built into AGL that produces unique id’s for messages that are sent via the V2C project | None | Including testing and integration this should be 40 to 80 person hours |
Embedded Protobuf Library | Include protobuf libraries for C, C++ and java in Linux build | This likely already exists, but would be beneficial if Protobuf Libraries are embedded and distributed with AGL builds | ~80 hours | |
Telecommunications Client Reference | A client that receives message requests from application services and creates and publishes messages to the broker. | The net result of this is a reference client made in C/C++ or Rust that can be leveraged when testing or developing with the V2C project. The client should handle secure connectivity and the building and publishing of final messages on the behalf of embedded applications | Needs at least one full set of messages and documentation completed (June 23) | ~200 hours |
Reference Cloud Services | Implementations in AWS IoT and other cloud services showing the orchestration of messages from the cloud side | The net result of this would be a minimum connected vehicle platform that handles the cloud side of publish and subscribe for messages using the V2C specification | Needs at least one full set of messages and documentation completed (June 23 | ~100 hours. |
What work needs to be completed prior to contractor engagement, what work can be completed in tandem with contractor work/dependent on contract work, and what work needs to be completed after contract work?