Vehicle privacy data management system

Abstract

The invention provides a vehicle privacy data management system, and relates to the technical field of intelligent vehicles. The vehicle privacy data management system comprises a vehicle-mounted terminal and a cloud server, wherein the vehicle-mounted terminal is in communication connection with the cloud server; the vehicle-mounted terminal is used for acquiring data of each functional module of a vehicle and uploading the data to the cloud server; the cloud server comprises a private data management module, and the private data management module is used for identifying private data in the data uploaded by the vehicle-mounted terminal and storing the private data to corresponding safe storage areas according to preset storage categories. According to the method, a unified data management specification can be constructed, centralized management of privacy data is realized, omission and repeated development of privacy protection measures are avoided, and the problems of disjunction of vehicle functions and privacy data management, non-uniform data storage, high privacy leakage risk and the like are effectively solved, so that the data management efficiency can be improved.

Description

Technical Field

[0001] The present invention relates to the technical field of intelligent vehicles, and more particularly, to a vehicle privacy data management system. Background Art

[0002] With the development of autonomous driving technology, vehicle networking, big data, and artificial intelligence, intelligent connected vehicles are gradually becoming popular. Intelligent connected vehicles not only have traditional driving functions but also introduce many functions such as remote control, intelligent navigation, autonomous driving, in-vehicle entertainment, driving assistance, and fleet management. Therefore, during the operation of intelligent connected vehicles, a large amount of user privacy data, such as location information, driving behavior data, biometric information, and in-vehicle passenger data, will be collected and processed to support the above functions.

[0003] In the related art, vehicle functions and privacy data are managed independently. For example, the processing methods of privacy data are scattered, and the privacy data protection of different functions is developed independently, resulting in a lack of unified norms for data management and easily leading to omissions or duplicate developments of privacy protection measures. Summary of the Invention

[0004] The problem solved by the present invention is how to provide a systematic function-privacy data association management solution.

[0005] To solve the above problems, the present invention provides a vehicle privacy data management system, including an in-vehicle terminal and a cloud server, and the in-vehicle terminal is communicatively connected to the cloud server;

[0006] The in-vehicle terminal is used to obtain data of each functional module of the vehicle and upload it to the cloud server;

[0007] The cloud server includes a privacy data management module, and the privacy data management module is used to identify privacy data in the data uploaded by the in-vehicle terminal and store the privacy data in corresponding secure storage areas according to preset storage categories.

[0008] Optionally, the privacy data management module is further used to classify the data uploaded by the in-vehicle terminal according to preset classification categories, and respectively identify privacy data in the data uploaded by the in-vehicle terminal according to the classification results, and the preset classification categories include sensitive location information, personal identity information, driving behavior data, user preference settings, and vehicle status information.

[0009] Optionally, the vehicle privacy data management system further includes a mobile application, which is communicatively connected to the cloud server; the in-vehicle terminal and / or the mobile application are used to configure the privacy consent switches of each of the function modules, and the cloud server is used to receive the configuration information of the privacy consent switches sent by the in-vehicle terminal and / or the mobile application, and adjust the function permissions of the function modules to match the privacy attributes according to the configuration information.

[0010] Optionally, the cloud server is used to classify each of the function modules according to privacy attributes; the in-vehicle terminal and / or the mobile application are also used to configure the privacy consent switches of the function modules by category according to the privacy attribute classification results of the function modules.

[0011] Optionally, the cloud server further includes a permission control module, which is used to parse the configuration information to determine the function permissions that need to be adjusted.

[0012] Optionally, the permission control module includes an application access control list, and the permission control module is used to restrict unauthorized operations through the application access control list, where the application access control list includes access rules and permission levels.

[0013] Optionally, the cloud server further includes a log recording module, which is used to record operations and generate log records, where the operations include data collection, permission adjustment, and access control, and the log records include operation time, operation type, operation subject, and operation object.

[0014] Optionally, the cloud server further includes a fleet management module, which is used to configure the function permissions of the vehicle according to preset contract terms, and manage violation operations according to the function usage data of the vehicle.

[0015] Optionally, the in-vehicle terminal and / or the mobile application include a user interaction interface, which is used to display each function module and its privacy attributes.

[0016] Optionally, the vehicle privacy data management system further includes a network communication module, and both the in-vehicle terminal and the mobile application are communicatively connected to the cloud server through the network communication module; and / or, the privacy data includes corresponding identifiers one by one, and the identifiers are used to indicate the source, use, and access permissions of the privacy data.

[0017] The beneficial effects of the vehicle privacy data management system of the present invention are as follows: The data of each functional module of the vehicle is obtained through the in-vehicle terminal and uploaded to the cloud server. The privacy data management module of the cloud server identifies the privacy data in the data uploaded by the in-vehicle terminal and stores the privacy data in the secure storage area according to the preset storage categories, thereby constructing a unified data management specification, realizing the centralized management of privacy data, avoiding the omission and repeated development of privacy protection measures, effectively solving the problems of the disconnection between vehicle functions and privacy data management, inconsistent data storage, and high risk of privacy leakage, and thus being able to improve the data management efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] Figure 1 It is a schematic diagram of the composition of the vehicle privacy data management system according to an embodiment of the present invention;

[0019] Figure 2 It is an overall architecture diagram of the vehicle privacy data management system according to an embodiment of the present invention;

[0020] Figure 3 It is a schematic diagram of the classification of vehicle functions and their corresponding privacy attributes according to an embodiment of the present invention;

[0021] Figure 4 It is a schematic diagram of the principle of the privacy consent switch according to an embodiment of the present invention;

[0022] Figure 5 It is a schematic diagram of the principle of the privacy data management module according to an embodiment of the present invention;

[0023] Figure 6 It is a schematic diagram of the principle of the permission control module according to an embodiment of the present invention;

[0024] Figure 7 It is a schematic diagram of the principle of the log management module according to an embodiment of the present invention;

[0025] Figure 8 It is a schematic diagram of the principle of the fleet management module according to an embodiment of the present invention;

[0026] Figure 9 It is a schematic diagram of the principle of the user interface according to an embodiment of the present invention. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0027] In order to make the above objects, features, and advantages of the present invention more obvious and understandable, the following detailed description of the specific embodiments of the present invention will be given with reference to the accompanying drawings. Although some embodiments of the present invention are shown in the drawings, it should be understood that the present invention can be implemented in various forms and should not be construed as limited to the embodiments described herein. On the contrary, these embodiments are provided to more thoroughly and completely understand the present invention. It should be understood that the drawings and embodiments of the present invention are only for exemplary purposes and are not used to limit the protection scope of the present invention.

[0028] It should be understood that the various steps described in the method embodiments of the present invention can be executed in different orders and / or executed in parallel. In addition, the method embodiments may include additional steps and / or omit the steps shown. The scope of the present invention is not limited in this regard.

[0029] As used herein, the term "including" and its variants are open-ended, i.e., "including but not limited to"; the term "based on" means "at least partially based on"; the term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one additional embodiment"; the term "some embodiments" means "at least some embodiments"; the term "optionally" means "optional embodiments". The relevant definitions of other terms will be given in the following description. It should be noted that the concepts such as "first" and "second" mentioned in the present invention are only used to distinguish different devices, modules or units, and are not used to limit the order or interdependence of the functions performed by these devices, modules or units.

[0030] It should be noted that the modification of "one" and "multiple" mentioned in the present invention is illustrative rather than restrictive. Those skilled in the art should understand that, unless otherwise clearly specified in the context, it should be understood as "one or more".

[0031] The names of the messages or information exchanged between multiple devices in the embodiments of the present invention are only for illustrative purposes and are not used to limit the scope of these messages or information.

[0032] As Figure 1 shown, a vehicle privacy data management system provided by an embodiment of the present invention includes an in-vehicle terminal and a cloud server, and the in-vehicle terminal is communicatively connected to the cloud server;

[0033] The in-vehicle terminal is configured to obtain data of each functional module of the vehicle and upload it to the cloud server;

[0034] The cloud server includes a privacy data management module, and the privacy data management module is configured to identify privacy data in the data uploaded by the in-vehicle terminal and store the privacy data in corresponding secure storage areas according to preset storage categories.

[0035] Specifically, as Figure 2 shown, the vehicle privacy data management system includes an in-vehicle terminal and a cloud server. The in-vehicle terminal is communicatively connected to the cloud server. The in-vehicle terminal is responsible for collecting data of each functional module of the vehicle, such as vehicle operation data (such as location information, driving behavior data, etc.), and uploading it to the cloud server.

[0036] Among them, as Figure 3As shown in the figure, each function of the whole vehicle can be classified into the following categories according to the privacy attributes of the data to be collected, processed, and sent: (1) Basic functions: functions that do not involve any privacy data, such as vehicle startup, basic driving control, etc.; (2) Advanced functions: functions that involve a small amount of non-sensitive privacy data, such as navigation, music playback, etc.; (3) Privacy functions: functions that involve sensitive privacy data, such as real-time location tracking, driving behavior analysis, etc.; (4) Full functions: functions that require comprehensive collection and processing of user privacy data, such as Advanced Driver Assistance Systems (ADAS), vehicle health monitoring, etc.; (5) Rental functions: special functions rented for a short period (e.g., purchasing a license for 1 week, or 1 month, or 1 year, and renting the function of Highway Autopilot NOA); (6) Trial functions: functions for users to experience temporarily; special functions for short-term experience (e.g., applying for a license for 1 week, or 1 month, or 3 months, and experiencing the Automatic Valet Parking function AVP for free); (7) One-time authorization functions: functions that can be used only once under specific conditions (e.g., lending the vehicle to a friend or other person for short-term use, distributing a one-time mobile key to this person, and authorizing the use of specific related functions; after the vehicle is returned, this one-time mobile key becomes invalid, and the related functions are automatically closed). From basic functions to advanced functions and then to full functions, it reflects the increasing complexity of privacy data processing from low to high; functions such as rental, trial, and one-time authorization are independent of the main classification, indicating their special uses.

[0037] Among them, the cloud server includes a Central Management Module (CMM). The central management module is used to uniformly manage and coordinate the privacy data identification and protection requirements of each function of the whole vehicle, such as privacy data management, permission control, and logging. Through the central management module, the configuration information can be parsed, and the function permissions can be adjusted according to the parsing results. By uniformly managing and coordinating the privacy data identification and protection requirements of each function of the whole vehicle through the central management module, it avoids the phenomenon of data islands where each function module stores and manages data separately, effectively solves problems such as the disconnection between vehicle functions and privacy data management, inconsistent data storage, and high risk of privacy leakage, thereby improving the data management efficiency.

[0038] Among them, combined with Figure 5As shown in the figure, the centralized management module includes a Privacy Data Management (PDM) module, which is used to identify privacy data in the data uploaded by the vehicle terminal. For example, the privacy data management module first analyzes the data collection requirements of each functional module in the vehicle system. By parsing the configuration files or interface documents of the functional modules, it clarifies the data types that need to be collected (such as location information, driving behavior data, user preference settings, etc.). Then, according to the preset classification categories (such as sensitive location information, personal identity information, etc.), it classifies the collected data. Finally, it stores the identified privacy data in the specified secure storage area (such as an encrypted database or an isolated storage area) according to the preset storage categories.

[0039] Among them, the exemplary storage categories are shown in the following table:

[0040]

[0041]

[0042] Exemplary secure storage areas include three databases that respectively store highly sensitive data (data that requires the highest level of protection), moderately sensitive data (data that requires medium-strength protection), and low-sensitive data (data that does not involve personal privacy or has been anonymized).

[0043] In this embodiment, data from each functional module of the vehicle is obtained through the vehicle terminal and uploaded to the cloud server. The privacy data management module of the cloud server identifies the privacy data in the data uploaded by the vehicle terminal and stores the privacy data in the secure storage area according to the preset storage categories, thereby constructing a unified data management specification, realizing centralized management of privacy data, avoiding omissions and duplicate development of privacy protection measures, effectively solving problems such as the disconnection between vehicle functions and privacy data management, inconsistent data storage, and high privacy leakage risks, and thus being able to improve data management efficiency.

[0044] Optionally, the privacy data management module is further configured to classify the data uploaded by the vehicle terminal according to the preset classification categories, and respectively perform privacy data identification on the data uploaded by the vehicle terminal according to the classification results. The preset classification categories include sensitive location information, personal identity information, driving behavior data, user preference settings, and vehicle status information.

[0045] Specifically, the exemplary classification categories are shown in the following table:

[0046]

[0047]

[0048] Among them, when identifying the privacy data type, it can be determined whether a field belongs to privacy data according to predefined rules or a machine learning model. An exemplary identification method is shown in the following table:

[0049]

[0050] In this optional embodiment, the data is subdivided through preset classification categories, and then finer-grained permissions can be configured to ensure that different functions comply with access specifications when calling data, preventing abuse or illegal acquisition.

[0051] Optionally, the vehicle privacy data management system further includes a mobile application, and the mobile application is communicatively connected to the cloud server; the in-vehicle terminal and / or the mobile application are used to configure the privacy consent switches of each function module, and the cloud server is used to receive the configuration information of the privacy consent switches sent by the in-vehicle terminal and / or the mobile application, and adjust the matching of the function permissions and privacy attributes of the function module according to the configuration information.

[0052] Specifically, the vehicle privacy data management system further includes a mobile application, and the mobile application is communicatively connected to the cloud server; the user can view the function privacy attributes and configure and adjust the privacy consent switch (Privacy Consent Switch, PCS) through the in-vehicle terminal or the mobile application. Each function category is provided with a unique privacy consent switch. The cloud server receives the configuration information of the privacy consent switch sent by the in-vehicle terminal or the mobile application, and adjusts the matching of the function permissions and privacy attributes of the function module according to the configuration information to ensure that the user has clear control over the functions involving privacy data.

[0053] Among them, as shown in Figure 4 The user can enter the privacy settings interface through the in-vehicle terminal or the mobile application, and select the function permissions (such as location information, driving behavior analysis, etc.) that need to be turned on or off in the interface. The user's operation will generate PCS configuration information and send it to the cloud server; the cloud server receives the user's PCS configuration information and dynamically adjusts the permissions of relevant functions according to the status (on or off) of the PCS. For example, if the PCS turns off the "real-time location tracking" function, this function will be restricted from use. If the PCS turns on the "driving behavior analysis" function, this function will be normally enabled; if the PCS turns off a function involving sensitive privacy data (such as sensitive location information), this function will not be able to run properly, and the system will feedback corresponding prompt information to the user (such as "This function has been turned off"). Through the user's active configuration, the dynamic adjustment of the cloud server, and the strict restriction of sensitive functions, the system can effectively manage and protect the user's privacy data.

[0054] In this alternative embodiment, after the user configures the privacy consent switch through the in-vehicle terminal or mobile application, the cloud server adjusts the matching of function permissions and privacy attributes according to the configuration information, and can flexibly configure function permissions in different usage scenarios (such as personal vehicle use, car rental, etc.), thereby realizing the centralized management and dynamic control between the vehicle functions and privacy data, enabling the vehicle functions to be accurately matched with the privacy data, ensuring that the privacy data is only available for authorized users or functions to call, and reducing the risk of data leakage.

[0055] Optionally, the cloud server is used to classify each of the function modules according to privacy attributes; the in-vehicle terminal and / or the mobile application are also used to configure the privacy consent switches of the function modules by category according to the privacy attribute classification results of the function modules.

[0056] Specifically, after the cloud server classifies each function module according to privacy attributes, the in-vehicle terminal or mobile application configures the privacy consent switches of the function modules by category according to the privacy attribute classification results of the function modules, so that the function permissions are matched with the privacy attributes, ensuring that the user has clear control over the functions involving privacy data.

[0057] In this alternative embodiment, after the cloud server classifies each function module according to privacy attributes, the in-vehicle terminal or mobile application configures the privacy consent switches of the function modules by category according to the privacy attribute classification results of the function modules, so that the function permissions are matched with the privacy attributes, ensuring that the user has clear control over the functions involving privacy data.

[0058] Optionally, the cloud server further includes a permission control module, and the permission control module is used to parse the configuration information to determine the function permissions that need to be adjusted.

[0059] Specifically, as shown in Figure 6 The centralized management module of the cloud server includes a permission control module (Permission Control Module, PCM). The permission control module is used to dynamically adjust function permissions according to the user's PCS settings (i.e., configuration information); the user enters the privacy settings interface through the in-vehicle terminal or mobile application, and selects the function permissions that need to be turned on or off in the interface (such as location information, driving behavior analysis, etc.). The user's operation generates PCS configuration information and sends it to the cloud server; the permission control module in the cloud server receives the user's PCS configuration information, parses the function permissions that need to be adjusted according to the status of the PCS (on or off). For example, if the PCS turns off the "real-time location tracking" function, this function will be disabled. If the PCS turns on the "driving behavior analysis" function, this function will be enabled. At the same time, the system feeds back the result of the permission adjustment to the user (such as "real-time location tracking has been turned off").

[0060] In this alternative embodiment, the permission control module is responsible for defining and managing the access permissions of different users and system modules to privacy data. For example, it dynamically adjusts the data access permissions according to factors such as vehicle status, user roles, and operation modes to ensure the legality and security of data access.

[0061] Optionally, the permission control module includes an application access control list, and the permission control module is used to restrict unauthorized operations through the application access control list, where the application access control list includes access rules and permission levels.

[0062] Specifically, the permission control module uses a predefined application access control list (ACL) to restrict unauthorized operations. The application access control list includes detailed access rules and permission levels (such as read-only, write, execute, etc.). The system checks whether each operation request conforms to the provisions of the application access control list and decides whether to allow the operation to be executed.

[0063] Among them, a multi-layer security mechanism (such as encrypted transmission, access control, secure storage, privacy encryption algorithms, etc.) can be adopted to ensure that all operations involving privacy data comply with the legal and regulatory requirements related to vehicle privacy data in the target market.

[0064] In this alternative embodiment, unauthorized operations are restricted through the application access control list to ensure that only operations that conform to the provisions of the application access control list are executed, ensuring the legality and security of data access.

[0065] Optionally, the cloud server further includes a log recording module, and the log recording module is used to record operations and generate log records, where the operations include data collection, permission adjustment, and access control, and the log records include operation time, operation type, operation subject, and operation object.

[0066] Specifically, as shown in Figure 7 The centralized management module of the cloud server includes a log recording module (LogManagement, LM). The log recording module monitors all operations involving privacy data in the system in real time (such as data collection, permission adjustment, access control, etc.). Each time an operation occurs, the system automatically generates a detailed log record, including information such as operation time, operation type, operation subject (such as user or functional module), and operation object (such as specific data fields or functions).

[0067] Among them, the log recording module provides a security audit interface, allowing authorized auditors to query historical logs; auditors can filter and retrieve relevant logs according to different conditions (such as time range, operation type, operation subject, etc.).

[0068] Among them, the system supports exporting eligible log data in a standard format (such as CSV or PDF) for further analysis and reporting.

[0069] In this optional embodiment, the access, processing, and sharing behaviors of privacy data are recorded through a log recording module. For example, through the log recording module, a compliance report on privacy data processing can be provided to the regulatory agency to ensure the traceability and compliance of data processing.

[0070] Optionally, the cloud server further includes a fleet management module, which is used to configure the function permissions of vehicles according to preset contract terms and manage illegal operations based on the function usage data of vehicles.

[0071] Specifically, as shown in Figure 8 For fleet operation scenarios such as taxis and rental cars, a fleet management module (Fleet Management Module, FMM) based on market signing contracts is established. The fleet management module is responsible for fleet function configuration and privacy data compliance management. The functions of the fleet management module include: (1) Automatically configuring the function permissions of vehicles according to the fleet operation contract. For example, the system reads the terms and requirements in the fleet operation contract and automatically configures the function permissions of vehicles according to the contract content (such as restricting the use of certain advanced functions, setting driving behavior rules, etc.), and sends the configuration information to the target vehicle through the cloud server; (2) Monitoring the function usage of all vehicles in the fleet and submitting a privacy data compliance report. For example, real-time collecting the function usage data of all vehicles (such as function enabling status, driving behavior records, etc.), and the data is uploaded to the cloud server through the in-vehicle terminal for analysis and processing to determine whether there are illegal operations (such as function usage beyond the contract scope, violation of driving behavior rules, etc.). If an illegal operation is found, an alarm mechanism is triggered (such as sending an alarm notification to the fleet administrator), a compliance report is submitted (recording the time, type, and relevant evidence of the illegal behavior), and some functions of the illegal vehicle can be restricted to prevent further violations; (3) Providing personalized privacy protection strategy recommendations for fleet users.

[0072] In this optional embodiment, by automatically configuring permissions through the fleet management module, real-time monitoring of function usage, timely warning and handling of illegal operations, it effectively ensures the compliance of fleet operations and provides data support for subsequent improvement.

[0073] Optionally, the in-vehicle terminal and / or the mobile application includes a user interaction interface, which is used to display each function module and its privacy attributes.

[0074] Specifically, as shown in Figure 9As shown, the in-vehicle terminal and / or the mobile application include a user interaction interface that displays each functional module and its privacy attributes, enabling users to conveniently view the privacy attributes of each function and perform authorization or cancellation operations through the privacy consent switch. Users can enter the PCS configuration interface through the "Privacy Settings" entry on the in-vehicle screen or the relevant page of the mobile application (such as located in the main menu or "Settings" option, with a simple and intuitive entry design). The interface displays each functional module and its privacy attributes in the form of cards, and each card contains the following information: (1) Function name: such as "Real-time Location Tracking", "Driving Behavior Analysis", "Voice Assistant", etc.; (2) Privacy data type: such as "Location Information", "Driving Habits", "Voice Recordings", etc.; (3) Privacy level: such as "High Sensitivity", "Medium Sensitivity", "Low Sensitivity"; (4) Current status: such as "Enabled" or "Disabled". Users can quickly enable or disable a function by sliding the switch or clicking the button, or click on the function card to enter the detailed settings page, such as viewing the specific privacy data usage of the function and configuring more fine-grained permissions (such as collecting data only under specific conditions). The system can also provide real-time feedback (such as a beep or visual effect) to confirm the user's operation.

[0075] Among them, the user interaction interface uses icons and simple text descriptions to enhance understandability, provides options such as "Restore Default Settings" or "One-key Optimization" for users to quickly adjust privacy preferences, and pops up a confirmation prompt box before critical operations (such as disabling core functions).

[0076] Among them, the mobile application is synchronized with the in-vehicle system, and users can adjust the PCS settings on any device; the mobile interface design is consistent with the in-vehicle screen to ensure the consistency of the user experience.

[0077] In this optional embodiment, a simple and intuitive configuration interface is provided for users through the user interaction interface, facilitating users to configure permissions.

[0078] Optionally, the vehicle privacy data management system further includes a network communication module, and both the in-vehicle terminal and the mobile application are communicatively connected to the cloud server through the network communication module; and / or, the privacy data includes corresponding identifiers one by one, and the identifiers are used to indicate the source, usage, and access permissions of the privacy data.

[0079] Specifically, the vehicle privacy data management system further includes a network communication module, and both the in-vehicle terminal and the mobile application are communicatively connected to the cloud server through the network communication module. The network communication module can use an encryption protocol (such as TLS) to ensure data security.

[0080] In addition, when storing privacy data, a unique identifier can be generated for each type of privacy data, and its source, usage, and access permissions can be recorded; during the classified storage phase, an appropriate storage strategy (such as encryption strength, access permissions, etc.) can be selected according to the privacy level.

[0081] In this optional embodiment, the network communication module ensures that the data of the intelligent connected vehicle is not lost, leaked, or tampered with during the transmission process through an efficient, secure, and intelligent communication mechanism, improving the overall privacy protection ability and user experience; according to the identifier, the source, usage, and access permissions of the privacy data are indicated, facilitating operations such as tracing the origin of the privacy data, realizing centralized management of privacy data, and avoiding omission and duplicate development.

[0082] Although the present invention is disclosed as above, the protection scope of the present invention is not limited thereto. Those skilled in the art can make various changes and modifications without departing from the spirit and scope of the present invention, and these changes and modifications will all fall within the protection scope of the present invention.

Claims

1. A vehicle privacy data management system, characterized in that, It includes an in-vehicle terminal and a cloud server, and the in-vehicle terminal is communicatively connected to the cloud server; The in-vehicle terminal is used to obtain data of each functional module of the vehicle and upload it to the cloud server; The cloud server includes a privacy data management module, and the privacy data management module is used to identify privacy data in the data uploaded by the in-vehicle terminal and store the privacy data in corresponding secure storage areas respectively according to preset storage categories.

2. The vehicle privacy data management system according to claim 1, wherein The privacy data management module is also used to classify the data uploaded by the in-vehicle terminal according to preset classification categories, and respectively perform privacy data identification on the data uploaded by the in-vehicle terminal according to the classification results. The preset classification categories include sensitive location information, personal identity information, driving behavior data, user preference settings, and vehicle status information.

3. The vehicle privacy data management system according to claim 1, characterized in that, It also includes a mobile application, and the mobile application is communicatively connected to the cloud server; the in-vehicle terminal and / or the mobile application is used to configure privacy consent switches of each functional module, and the cloud server is used to receive configuration information of the privacy consent switches sent by the in-vehicle terminal and / or the mobile application, and adjust the matching of the functional permissions and privacy attributes of the functional modules according to the configuration information.

4. The vehicle privacy data management system according to claim 3, wherein The cloud server is used to classify each functional module according to privacy attributes; the in-vehicle terminal and / or the mobile application is also used to configure the privacy consent switches of the functional modules according to the privacy attribute classification results of the functional modules by category.

5. The vehicle privacy data management system according to claim 3, characterized in that, The cloud server also includes a permission control module, and the permission control module is used to parse the configuration information to determine the functional permissions that need to be adjusted.

6. The vehicle privacy data management system according to claim 5, wherein The permission control module includes an application access control list, and the permission control module is used to restrict unauthorized operations through the application access control list. Among them, the application access control list includes access rules and permission levels.

7. The vehicle privacy data management system according to claim 1, characterized in that, The cloud server also includes a log recording module, and the log recording module is used to record operations and generate log records. Among them, the operations include data collection, permission adjustment, and access control, and the log records include operation time, operation type, operation subject, and operation object.

8. The vehicle privacy data management system according to claim 1, characterized in that, The cloud server also includes a fleet management module, and the fleet management module is used to configure the functional permissions of vehicles according to preset contract terms and manage illegal operations according to the functional usage data of vehicles.

9. The vehicle privacy data management system according to claim 3, wherein The in-vehicle terminal and / or the mobile application includes a user interaction interface, and the user interaction interface is used to display each functional module and its privacy attributes.

10. The vehicle privacy data management system according to any one of claims 3 to 9, characterized in that, It also includes a network communication module, and both the in-vehicle terminal and the mobile application are communicatively connected to the cloud server through the network communication module; and / or, the privacy data includes corresponding identifiers one by one, and the identifiers are used to indicate the source, use, and access permissions of the privacy data.

Images