Vehicle Sensitive Data Management and Removal

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current systems lack an efficient method to determine and manage sensitive data stored on vehicles, particularly in terms of timing for data access and storage, which is crucial for maintaining privacy and operational functionality.

Innovation Solution

A method and system that analyze data stored on vehicles to identify sensitive information, remove it based on the time it is needed, and securely access it prior to the end of that time period, utilizing a processor and memory to determine sensitivity and manage data storage and retrieval.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If sensitive data is stored on the vehicle for extended periods, then data availability for vehicle operations is improved, but data security and privacy protection deteriorate

Engineering Contradiction:
Improvedata availabilityVSAvoidprivacy risk
Core Design Contradiction:
ReliabilityVSObject-affected harmful factors

Solution Approach 1:

The system performs preliminary actions by determining the sensitivity of data before storage and calculating the optimal retention period in advance. Sensitive data is identified and flagged, and the system pre-calculates when the data should be removed based on its sensitivity level and operational requirements, thus preventing privacy risks before they occur while ensuring data is available when needed.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements dynamic data management where the retention period for sensitive data is not fixed but adjusts based on multiple factors including data sensitivity level, vehicle operational needs, and security policies. The system continuously monitors and adjusts data retention strategies, removing data when the calculated optimal period expires, thus balancing availability and security dynamically.

Inventive Principle:
Principle #15Dynamics

2Object-affected harmful factors

If sensitive data is removed from the vehicle, then data security is improved, but data access functionality deteriorates

Engineering Contradiction:
Improvesecurity riskVSAvoiddata access
Core Design Contradiction:
Object-affected harmful factorsVSEase of operation

Solution Approach 1:

The system performs preliminary calculations to determine the optimal retention period for sensitive data before removal. By pre-calculating when data should be removed based on sensitivity and operational requirements, the system ensures that data remains accessible for the necessary duration while being removed promptly afterward, thus maintaining security without compromising operational functionality.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements a feedback mechanism where data access patterns and operational requirements are continuously monitored. This feedback informs the calculation of optimal retention periods and sensitivity determinations, ensuring that data removal decisions are based on actual usage patterns rather than static rules, thus preventing unnecessary removals that would impact functionality.

Inventive Principle:
Principle #23Feedback

3Object-affected harmful factors

If data sensitivity determination and management processes are implemented, then privacy protection is improved, but system complexity deteriorates

Engineering Contradiction:
Improveprivacy vulnerabilityVSAvoiddata management complexity
Core Design Contradiction:
Object-affected harmful factorsVSDevice complexity

Solution Approach 1:

The system segments data management into distinct functional modules: data sensitivity determination, retention period calculation, data removal execution, and access pattern monitoring. Each module handles a specific aspect of data management independently, making the overall complex system manageable through modular design where each segment can be developed, tested, and maintained separately.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system implements self-service capabilities where the data management process automatically determines sensitivity, calculates retention periods, and executes removals without requiring manual intervention. The system autonomously monitors its own data access patterns and adjusts retention strategies accordingly, reducing operational complexity while maintaining robust privacy protection.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS20240427927A1Vehicle-related sensitive data determination and removal
Publication Date: 2024.12.26 TOYOTA MOTOR NORTH AMERICA INC
  • US20240427927A1 patent drawing
  • US20240427927A1 patent drawing
  • US20240427927A1 patent drawing

AI summary

An example operation includes one or more of determining that data stored on a vehicle is sensitive, removing the sensitive data from the vehicle, based on an amount of time until the data is needed to be accessed by the vehicle, and accessing the removed sensitive data, by the vehicle, at a time prior to an end of the amount of time.