A few other software components that can be useful when setting up a VISSv2 communication tech stack exists:
The VISS2 specification describes an access control model involving two authorization servers:
To trigger the access control and consent functionality it is necessary to tag the corresponding VSS nodes as described in the spec. This can either be done by editing of the actual vspec files from the VSS/spec directory, or by creating overlay files and include them as described in VSS-tools, and then generate the VSS tree in binary format as described in VSS tree configuration.
The AGTS, which typically will be deployed off-vehicle, in the cloud, is separately built and deployed. The file agt_public_key.rsa is generated at startup, which must be copied to the AT server directory.
The ATS is deployed on a separate thread within the VISSv2 server, to include it make sure it is uncommented in the serverComponents string array in viss2server.go. The ATS uses the policy documents described in the spec when validating an access token, examples of these are available in the purposelist.json and scopelist.json files.
The code to realize an OVDS database is found here. The database is realized using SQLite, so it is possible to use the SQLite API to read and write from it.
However, an OVDS server is available that exposes a small set of methods for this, over HTTP. For more details, please check the README on the link.
There is as well an OVDS client available that connects to a VISSv2 server to fetch data that it then writes into the OVDS using the OVDS server interface.
The live simulator reads data from an OVDS containing recorded trip data, and then writes it into a state storage timed by the data time stamps so that it appears timing wise as when it was recorded. For more details, please check the README on the link.
The the test_vehicles.db file in the OVDS server directory contains trip data generously provided by Geotab Inc. It can be used as input to the live simulator, as well as the sawtooth_trip.db for simple testing.
The live simulator needs a copy of the list of leaf node paths (vsspathlist.json), which needs to contain at least all the paths that are to be replayed from the OVDS, and are also to be found in the VSS tree that the VISSv2 server uses.