Case Study – Vehicle to Cloud
VEHICLE DATA UPLOAD TO CLOUD SERVICES
SITUATION
- Vehicle time-history data required to be available for retrospective analysis
- Vehicle time-history data required to be available for remote real-time monitoring
OUR RESPONSE
- Vehicle data passing through an on-board Hypermotive controller must be available for recording and monitoring
- Design and implement services onto Hypermotive controllers that allow upload of data to an S3 (simple secure storage) service in the cloud
- Design and implement services onto Hypermotive controllers that allow real-time monitoring of data on a remote virtual dashboard
OUTCOME
- Controllers can publish data to the cloud through a connected router using an internet connection (sim card data, wi-fi connection of physical WLAN)
- Data published is stored in S3 service such as AWS or MS AZURE.
- Data streamed in real-time to remote dashboard services
VEHICLE DATA DOWNLOAD FROM CLOUD SERVICES
SITUATION
- OTA (Over-The-Air) software updates required in Hypermotive controllers located remotely with no physical access from software engineers.
- OTA software updates required to be cyber-secure
OUR RESPONSE
- Implement protocols and services to remotely update software in a Hypermotive controller in a functionally safe, seamless manner
- Implement protocols and services to digitally sign software and reject updates that do not pass security checks
- Allow the software to be rolled back in the event of an update failure
OUTCOME
- OTA updates can be done successfully to a single Hypermotive controller or to any Hypermotive controller on a network of controllers.
- OTA update process is cyber secure, with encrypted and digitally signed software
