Secure vehicular data management with enhanced privacy

Abstract

The present disclosure is directed to secure vehicular data management with enhanced privacy. A vehicle may comprise at least a vehicular control architecture (VCA) for controlling operation of the vehicle and a device. The VCA may record operational data identifying at least one vehicle operator and vehicular operational data recorded during operation of the vehicle by the at least one vehicle operator. The device may include at least a communication module and a trusted execution environment (TEE) including a privacy enforcement module (PEM). The PEM may receive the operational data from the VCA via the communication module, may generate filtered data by filtering the operational data based on privacy settings and may cause the filtered data to be transmitted via the communication module. The filtered data may be transmitted to at least one data consumer. The privacy settings may be configured in the PEM by the at least one operator.

What is claimed: 
     
         1 . A device for secure vehicular data management, comprising:
 communication circuitry to communicate with at least a vehicular control architecture for controlling operation of a vehicle and a user interface to configure privacy settings; and   trusted execution environment including a secure workspace in which only known-good programs execute, the known-good programs having privacy enforcement circuitry to:
 receive operational data from the vehicular control architecture via the communication circuitry; 
 generate filtered data by filtering the operational data based on privacy settings; and 
 cause the filtered data to be transmitted by the communication circuitry to at least one data consumer remotely situated from the device. 
   
     
     
         2 . The device of  claim 1 , wherein the device is integrated within the vehicular control architecture. 
     
     
         3 . The device of  claim 1 , wherein, upon the user interface identifying a driver of the vehicle, the trusted execution environment is to store at least driver biometric identification data received via the vehicular control architecture. 
     
     
         4 . The device of  claim 3 , wherein the operational data comprises at least the driver biometric identification data, vehicle location tracking data and vehicle event tracking data. 
     
     
         5 . The device of  claim 4 , wherein in generating filtered data the privacy enforcement circuitry is to remove at least a portion of the operational data from the filtered data based on the privacy settings. 
     
     
         6 . The device of  claim 4 , wherein in generating filtered data the privacy enforcement circuitry is to at least one of replace the at least a portion of the operational data with coded data or to alter at least a portion of the operational data. 
     
     
         7 . The device of  claim 1 , wherein the vehicular control architecture comprises a plurality of controllers for controlling different areas of vehicular operation, at least one controller providing the user interface. 
     
     
         8 . The device of  claim 1 , wherein a requirement for operation received from at the least one data consumer causes the communication circuitry to transmit the operational data to the at least one data consumer. 
     
     
         9 . A method for secure vehicular data management, comprising:
 configuring privacy settings in a user interface at least coupled to a vehicular control architecture for controlling operation of the vehicle;   receiving operational data from the vehicular control architecture;   generating filtered data by filtering the operational data based on the privacy settings, wherein the filtered data is generated by privacy enforcement circuitry included in a trusted execution environment in the device, the trusted execution environment including a secure workspace in which only known-good programs execute; and   causing the filtered data to be transmitted by communication circuitry in the device to at least one data consumer remotely situated from the device.   
     
     
         10 . The method of  claim 9 , wherein the device is integrated within the vehicular control architecture. 
     
     
         11 . The method of  claim 9 , further comprising, upon the user interface identifying a driver of the vehicle, storing, with the trusted execution environment, at least driver biometric identification data received via the vehicular control architecture. 
     
     
         12 . The method of  claim 11 , wherein the operational data comprises at least the driver biometric identification data, vehicle location tracking data and vehicle event tracking data. 
     
     
         13 . The method of  claim 12 , wherein generating filtered data comprises removing, with the privacy enforcement circuitry, at least a portion of the operational data from the filtered data based on the privacy settings. 
     
     
         14 . The method of  claim 12 , wherein generating filtered data comprises at least one of replacing, with the privacy enforcement circuitry, a portion of the operational data with coded data or altering the at least a portion of the operational data. 
     
     
         15 . The method of  claim 9  wherein the vehicular control architecture comprises a plurality of controllers for controlling different areas of vehicular operation, at least one controller providing the user interface. 
     
     
         16 . The method of  claim 9 , further comprising causing the communication circuitry to transmit the operational data to the at least one data consumer based on a requirement for operation received from at the least one data consumer. 
     
     
         17 . At least one machine-readable storage medium having stored thereon, individually or in combination, instructions for secure vehicular data management that, when executed, cause one or more processors to:
 configure privacy settings in a user interface at least coupled to a vehicular control architecture for controlling operation of the vehicle;   receive operational data from the vehicular control architecture;   generate filtered data by filtering the operational data based on the privacy settings, wherein the filtered data is generated by privacy enforcement circuitry included in a trusted execution environment in the device, the trusted execution environment including a secure workspace in which only known-good programs execute; and   cause the filtered data to be transmitted by communication circuitry in the device to at least one data consumer remotely situated from the device.   
     
     
         18 . The medium of  claim 17 , wherein the device is integrated within the vehicular control architecture. 
     
     
         19 . The medium of  claim 17 , further comprising instructions to, upon the user interface identifying a driver of the vehicle, store, with the trusted execution environment, at least driver biometric identification data received via the vehicular control architecture. 
     
     
         20 . The medium of  claim 19 , wherein the operational data comprises at least the driver biometric identification data, vehicle location tracking data and vehicle event tracking data. 
     
     
         21 . The medium of  claim 20 , wherein the instructions to generate filtered data comprise instructions to remove, with the privacy enforcement circuitry, at least a portion of the operational data from the filtered data based on the privacy settings. 
     
     
         22 . The medium of  claim 20 , wherein the instructions to generate filtered data comprises instructions to at least one of replace, with the privacy enforcement circuitry, a portion of the operational data with coded data or alter the at least a portion of the operational data. 
     
     
         23 . The medium of  claim 17  wherein the vehicular control architecture comprises a plurality of controllers for controlling different areas of vehicular operation, at least one controller providing the user interface. 
     
     
         24 . The medium of  claim 17 , further comprising instructions to cause the communication circuitry to transmit the operational data to the at least one data consumer based on a requirement for operation received from at the least one data consumer.