Merge pull request COVESA#55 from UlfBj/master

test_vehicles.db added. README updates.

README.md

@@ -1,13 +1,15 @@
-# ccs-w3c-client
+# ccs-components
 This project contains a number of components used in the Cloud & Connected Services (CCS) project at the Connected Vehicle Systems Alliance (COVESA).
-The figure below shows an example of this technology stack, where all the components on this repo are used.
+The figure below shows an example of this technology stack, where the components on this repo are used.
 
 ![Technology stack, CCS project](docs/Tech-stack-ccs-project.jpg?raw=true)<br>
 
 <br><img src="docs/VSS_CCS_Setup.png" alt="CCS GitHub Deployment Model" width="800" height="480"/><br>
 
-Please not that in the Git deployment model figure the same OVDS DB and server are shown representing both a cloud deployment, and a vehicle deployment.
-The Technology stack figure shows them separated, which is how it is used in the CCS project when vehicle data is simulated. In a vehicle deployment the live simulator, the OVDS server and database would be replaced by a "vehicle native" data feeder implementation. 
+Please note that in the Git deployment model figure the same OVDS DB and server are shown representing both a cloud deployment, and a vehicle deployment.
+The Technology stack figure shows them separated, which is how it is used in the CCS project when vehicle data is simulated. In a vehicle deployment the live simulator, the OVDS server and database would be replaced by a "vehicle native" data feeder implementation.<br>
+The VISSv2 internal interfaces between the core server, the HTTP/WS/MQTT transport managers, and the service manager all run over the Websocket protocol, with JSON payloads as specified for the Websocket transport in the VISSv2 specification.<br>
+The statestorage interface is realized by the SQLITE queries that can be formulated to read or write single signals from/to it.
 
 # OVDS server/db
 The Open Vehicle Data Set database is a database schema that is well suited for storing vehicle data from multiple vehicles. 

ovds/server/README.md

@@ -35,5 +35,14 @@ When a set request contains a VIN that has not been entered into the database be
 
 CREATE TABLE TV_1 (`value` TEXT NOT NULL, `timestamp` TEXT NOT NULL, `path` TEXT)
 
-where the index 1 in the example table name above is the value in the vin_id field of the entry for this VIN in the table VIN_TIV.
+where the index 1 in the example table name above is the value in the vin_id field of the entry for this VIN in the table VIN_TIV.<br>
+
+This directory contains two OVDS databases:<br>
+- sawtooth_trip.db: Contains dummy trip data for lat/long/speed signals. The dummy data forms a sawtooth shaped curve.<br>
+- test_vehicles.db: Contains trip data from four vehicles, with multiple signals. The data has been de-identified, 
+but is otherwise authentic recordings from vehicle trips. The data was collected using curve logging. 
+The OVDS interpolator in the livesim/ovds-interpolation directory can be used to recreate a database with with eqvi-distant time periods between samples.<br>
+
+These databases can be used as input to the live simulator as it accesses it via an OVDS server. 
+The sawtooth_trip.db can e. g. be used for verifying the curve logging functionality provided by the VISSv2 server.