Vehicle data processing method, vehicle, and readable storage medium
By identifying the application scenarios and sensitivity levels of intelligent connected vehicle data, and performing de-identification processing and encrypted transmission, the problem of low security in vehicle data access is solved, and customized protection and secure access to data are achieved.
Patent Information
- Application Number
- PCT/CN2026/108932
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2026-01-14
- Filing Date
- 2026-07-06
- Publication Date
- 2026-11-19
AI Technical Summary
In the field of intelligent connected vehicles, insufficient privacy protection during vehicle data access results in low data security and vulnerability to unauthorized access.
By responding to client data access commands, the system identifies data application scenarios and sensitivity levels, performs data anonymization, determines authorized access data, and encrypts transmission based on scenario security levels and client permission levels, dynamically adjusting anonymization strength and access permissions.
It enables customized protection based on data usage and scenario characteristics, improving the security and privacy protection level of data transmission and ensuring the effective use and secure access of data in different application scenarios.
Smart Images

Figure CN2026108932_19112026_PF_FP_ABST
Abstract
Description
Method for processing vehicle data, vehicle and readable storage medium TECHNICAL FIELD
[0001] Embodiments of the present disclosure relate to the field of vehicles, and in particular, to a method for processing vehicle data, a vehicle and a readable storage medium. BACKGROUND
[0002] In the field of intelligent networked vehicles, the integration of vehicle-mounted sensors and communication technologies enables vehicles to collect and transmit private data including location and driving behavior. Real-time data requirements for scenarios such as autonomous driving, remote diagnosis and personalized services require privacy protection for processed data. However, in the current vehicle data access process, the privacy protection is not enough, which affects the security of the data and makes the data vulnerable to illegal access in high-risk environments.
[0003] There is currently no good solution to the above problems. SUMMARY
[0004] Embodiments of the present disclosure provide a method for processing vehicle data to at least solve the technical problem of low security of data access.
[0005] According to an aspect of an embodiment of the present disclosure, a method for processing vehicle data is provided, comprising: in response to receiving a data access instruction of a client for a vehicle, obtaining vehicle data corresponding to the data access instruction and a data application scenario corresponding to the vehicle data; determining a target sensitive level of the vehicle data from a plurality of sensitive levels, wherein different sensitive levels are used to quantify different severity levels of vehicle data leakage; performing desensitization processing on the vehicle data based on the target sensitive level and the data application scenario to obtain desensitized vehicle data; determining authorized access data in the desensitized vehicle data based on a scene security level of the data application scenario and an access permission level of the client, and sending the authorized access data to the client, wherein the authorized access data is data in the desensitized vehicle data that is allowed to be accessed by the client.
[0006] Further, determining the target sensitive level of the vehicle data from the plurality of sensitive levels comprises: determining a target data category of the vehicle data from a plurality of data categories, and determining a data refinement degree of the vehicle data, wherein the data refinement degree is used to represent the collection accuracy of the vehicle data; determining the target sensitive level from the plurality of sensitive levels based on the data refinement degree and the target data category of the vehicle data.
[0007] Further, the vehicle data is desensitized based on the target sensitivity level and the data application scenario to obtain desensitized vehicle data, including: determining a desensitization strength based on the target sensitivity level; determining a desensitization object in the vehicle data based on the data application scenario, wherein the desensitization object is used to represent an object to be desensitized; and desensitizing the desensitization object in the vehicle data based on the desensitization strength to obtain the desensitized vehicle data.
[0008] Further, the vehicle data is desensitized based on the desensitization strength and the desensitization object to obtain desensitized vehicle data, including: determining a target desensitization operation type corresponding to a target data category from a plurality of desensitization operation types, wherein different data categories correspond to different desensitization operation types; and desensitizing the desensitization object in the vehicle data based on the target desensitization operation type according to the desensitization strength to obtain the desensitized vehicle data.
[0009] Further, the authorized access data in the desensitized vehicle data is determined based on the scene security level of the data application scenario and the access permission level of the client, including: determining an authorized access data type of the client based on the scene security level of the data application scenario and the access permission level of the client; and determining the authorized access data corresponding to the authorized access data type from the desensitized vehicle data.
[0010] Further, the authorized access data is sent to the client, including: encrypting the authorized access data based on the target sensitivity level and the scene security level to obtain encrypted vehicle data; and transmitting the encrypted vehicle data to the client.
[0011] Further, the method further includes: obtaining an abnormal access number of the vehicle data, a desensitization backtracking number of the vehicle data, and an encryption abnormal number of the vehicle data, wherein the desensitization backtracking number represents a number of successful backtracking of the desensitized vehicle data, and the encryption abnormal number represents a number of abnormal encryption of the vehicle data; performing risk assessment on the vehicle data based on the abnormal access number, the desensitization backtracking number, and the encryption abnormal number to obtain a risk value of the vehicle data; and adjusting a desensitization strength corresponding to the target sensitivity level and the access permission level based on the risk value, the abnormal access number, and the desensitization backtracking number.
[0012] Further, the desensitization strength corresponding to the target sensitivity level and the access permission level is adjusted based on the risk value, including: if the risk value is greater than a first preset threshold value and the abnormal access number is greater than a first preset number, the access permission level of the client is reduced; if the risk value is greater than the first preset threshold value and the desensitization backtracking number is greater than a second preset number, the desensitization strength is enhanced; and if the risk value is less than a second preset threshold value, the access permission level is improved and / or the desensitization strength is weakened, wherein the second preset threshold value is less than the first preset threshold value.
[0013] According to another aspect of the embodiments of the present disclosure, a vehicle is also provided, comprising: a memory storing an executable program; and a processor configured to run the program, wherein the program performs the method in various embodiments of the present disclosure when running.
[0014] According to another aspect of the embodiments of the present disclosure, a computer-readable storage medium is also provided, comprising a stored executable program, wherein the computer-readable storage medium controls the device where the computer-readable storage medium is located to perform the method in various embodiments of the present disclosure when the executable program runs.
[0015] According to another aspect of the embodiments of the present disclosure, a computer program product is also provided, comprising a computer program, which, when executed by a processor, implements the method in various embodiments of the present disclosure.
[0016] According to another aspect of the embodiments of the present disclosure, a computer program product is also provided, comprising a non-volatile computer-readable storage medium storing a computer program, which, when executed by a processor, implements the method in various embodiments of present disclosure.
[0017] According to another aspect of the embodiments of the present disclosure, a computer program is also provided, which, when executed by a processor, implements the method in various embodiments of the present disclosure
[0018] In the embodiments of the present disclosure, in response to receiving a data access instruction of a client for a vehicle, vehicle data corresponding to the data access instruction is obtained, and a data application scenario corresponding to the vehicle data is obtained; a target sensitive level corresponding to the vehicle data is determined from a plurality of sensitive levels, wherein different sensitive levels are used to quantify different severity levels of vehicle data leakage; based on the target sensitive level and the data application scenario, the vehicle data is desensitized to obtain desensitized vehicle data; based on a scene security level of the data application scenario and an access permission level of the client, authorized access data in the desensitized vehicle data is determined, wherein the authorized access data is data in the desensitized vehicle data that is allowed to be accessed by the client. Through the fusion analysis of multi-source information such as data use, access subject, scene security level, etc., the specific scene of current data processing is identified in real time, and the collected private data is classified and graded, and the sensitivity of each type of data is clarified for subsequent targeted protection, so as to achieve the purpose of dynamically adjusting the parameters of the desensitization algorithm or selecting different desensitization methods according to the identified scene characteristics and data sensitivity level, thereby realizing the technical effect of being able to provide customized protection measures for different data types and scenes, including not only desensitization processing of the data itself, but also dynamic adjustment of access permissions to ensure the safe access of data, thereby solving the technical problem of low security of data access. BRIEF DESCRIPTION OF DRAWINGS
[0019] The accompanying drawings, which are included to provide a further understanding of the disclosure and constitute a part of the disclosure, illustrate embodiments of the present disclosure and serve to explain the present disclosure together with the descriptions: in the drawings:
[0020] FIG. 1 is a schematic diagram of a vehicle data processing method according to the related art;
[0021] FIG. 2 is a flowchart of an optional vehicle data processing method according to an embodiment of the present disclosure;
[0022] FIG. 3 is a schematic diagram of an optional vehicle data processing method according to an embodiment of the present disclosure;
[0023] FIG. 4 is a schematic diagram of an optional vehicle data processing apparatus according to an embodiment of the present disclosure. DETAILED DESCRIPTION
[0024] In order to enable persons skilled in the art to better understand the present disclosure scheme, the technical solutions in the embodiments of the present disclosure will be clearly and completely described below in conjunction with the drawings in the embodiments of the present disclosure. Obviously, the described embodiments are only a part of the embodiments of the present disclosure, not all the embodiments. Based on the embodiments in the present disclosure, all other embodiments obtained by persons skilled in the art without creative labor should be within the scope of protection of the present disclosure.
[0025] It should be noted that the terms "first", "second", and the like in the specification and claims of the present disclosure and the above-described drawings are used to distinguish similar objects, and do not necessarily indicate a specific order or a chronological sequence. It should be understood that the data thus used can be interchanged under appropriate circumstances, so that the embodiments of the present disclosure described herein can be implemented in an order other than that illustrated or described herein. In addition, the terms "include" and "have" and any variations thereof are intended to cover non-exclusive inclusion, for example, a process, method, system, product or device that includes a series of steps or units does not necessarily have to be limited to those steps or units clearly listed, but can include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.
[0026] According to an embodiment of the present disclosure, an embodiment of a vehicle data processing method is provided. It should be noted that the steps shown in the flowchart of the drawings can be executed in a computer system such as a set of computer executable instructions, and although the logical order is shown in the flowchart, in some cases, the steps shown or described herein can be executed in a different order than that shown herein.
[0027] A method for processing vehicle data is provided in the embodiments of the present disclosure. FIG. 1 is a flowchart of the method for processing vehicle data according to the embodiments of the present disclosure. As shown in FIG. 1, the flow includes the following steps:
[0028] In S102, in response to receiving the data access instruction of the client for the vehicle, the vehicle data corresponding to the data access instruction is obtained, and the data application scenario corresponding to the vehicle data is obtained.
[0029] The client mentioned above refers to an entity initiating a data access request, including but not limited to a smart device, an application program or a service provider. In the field of intelligent and networked vehicles, the client is a vehicle owner's personal device, a vehicle enterprise service platform or a third-party maintenance institution, etc.
[0030] The data access instruction mentioned above refers to a command issued by the client, aiming to obtain a specific type of vehicle data. The data access instruction not only indicates the specific type of the required data (such as location information, driving habits, vehicle status, etc.), but also implies the subsequent use of the data and the identity information of the access subject.
[0031] The vehicle data mentioned above refers to various data generated by intelligent and networked vehicles through on-board sensors and systems during driving, covering multiple dimensions such as location trajectory, driving mode, vehicle health status, etc., and is the basis for realizing advanced functions such as automatic driving and remote diagnosis.
[0032] The data application scenario mentioned above refers to a context description of vehicle data being used to realize a certain specific function or solve a certain problem. The data application scenario determines the sensitivity of the data, such as path planning in automatic driving, fault code reading in remote diagnosis, and driving habit analysis in personalized services.
[0033] In an optional embodiment, after receiving the data access instruction issued by the client, the system first analyzes the data access instruction to identify the specific vehicle data requirements contained in the instruction, which covers the vehicle's location information, driving behavior records or health status parameters, etc. Then, the matching vehicle data is extracted from the data warehouse, and the purpose of the matched data, the identity attribute of the access subject, and the scene security level during data processing are analyzed. In the embodiments of the present disclosure, in response to the process of receiving the data access instruction of the client for the vehicle, real-time identification of the data application scenario and definition of the data sensitivity level are integrated. First, the embodiments of the present disclosure realize the matching of the access instruction and the data purpose through data application scenario analysis, enhancing the pertinence and scene adaptability of data protection.
[0034] By obtaining the vehicle data corresponding to the data access instruction, the corresponding privacy data is extracted from the data storage or real-time collection stream of the vehicle according to the data type specified in the access instruction. For example, when the data access instruction requires obtaining driving habit data, the system will filter the required information from the driving behavior record.
[0035] By identifying the data application scenario corresponding to the vehicle data, the use intention and scenario characteristics behind the data access instruction are analyzed, the purpose of data processing (such as supporting autonomous driving, performing remote diagnosis or providing personalized services) is judged, and the scenario security level of accessing data (such as whether to access under public network) is judged. Identifying the data application scenario helps to dynamically generate the corresponding desensitization strategy and access permission rule in the subsequent.
[0036] The embodiments of the present disclosure achieve the scenario-based management and precise protection of the privacy data of intelligent networked vehicles by responding to the received client data access instruction, obtaining vehicle data and identifying the corresponding data application scenario. This innovative method not only dynamically adjusts the data access permission according to the actual use of the data and the scenario security level, but also ensures the efficient use of the data on the premise of protecting the data privacy and security. This improvement is an important upgrade from static rules to dynamic intelligent strategies for the privacy protection system of intelligent networked vehicles, which improves the flexibility and efficiency of data protection and meets the data security needs in various application scenarios.
[0037] S104, determining a target sensitive level corresponding to the vehicle data from a plurality of sensitive levels.
[0038] Among them, different sensitive levels are used to quantify different severity levels of vehicle data leakage.
[0039] The above plurality of sensitive levels are obtained by dividing the data into a plurality of levels for the purpose of managing privacy data. These levels reflect the risk degree brought by data leakage from low to high.
[0040] The target sensitivity level refers to a specific sensitivity level determined according to the attributes of the vehicle data and potential consequences of a leak for each batch or each type of vehicle data. Different sensitivity levels can quantify different severity levels of vehicle data leaks. In the embodiments of the present disclosure, the process of determining the target sensitivity level of vehicle data from multiple sensitivity levels is different from the uniform fixed level protection measures for all data in the related art. The embodiments of the present disclosure dynamically evaluate and determine the sensitivity level of data according to the specific type and application scenario of the data. Specifically, the data sensitivity is matched with the application scenario, and the most appropriate sensitivity level is matched by analyzing the potential threat of the data. The embodiments of the present disclosure enhance the balance between data security and functional availability. Specifically, the determination of the target sensitivity level can adjust the accessibility and availability of data according to actual needs while ensuring data security, ensuring that data maximizes its role in key functions such as autonomous driving and remote diagnosis, while reducing the risk of privacy leaks.
[0041] In an optional embodiment, the type and content of the vehicle data are first analyzed to identify the inherent sensitivity of the data. The type of vehicle data refers to location data, driving behavior data, vehicle state data, etc. The content of the vehicle data can be the accuracy of the data, time sensitivity, user association, etc. Based on the above evaluation, the severity of the consequences of data leaks is quantified, such as the degree of invasion of user privacy, the degree of impact on vehicle functions, and potential legal liability risks, to determine different severity levels of data leaks. Further considering the characteristics of the data application scenario and the needs of the data application scenario for data sensitivity, the sensitivity level of the vehicle data is dynamically adjusted in combination with the scene security level and the attributes of the access subject, to ensure the most suitable security level for the specific scene. The data application scenario is autonomous driving, vehicle maintenance, data analysis, etc.
[0042] The embodiments of the present disclosure achieve the security protection of intelligent connected vehicle data by determining the target sensitivity level of vehicle data from multiple sensitivity levels. This process not only accurately reflects the potential risks of data leaks, but also dynamically adjusts the sensitivity level of vehicle data according to the real-time changes of the data application scenario, the scene security level, and the attributes of the access subject, thereby protecting data security while ensuring the effectiveness and availability of data in supporting advanced functions such as autonomous driving and remote diagnosis.
[0043] S106, based on the target sensitivity level and the data application scenario, desensitizing the vehicle data to obtain desensitized vehicle data.
[0044] The desensitization processing mentioned above refers to modifying or converting the original vehicle data to protect privacy, so as to reduce or eliminate sensitive information in the data while meeting the needs of the data application scenario. The desensitization processing includes but is not limited to the implementation modes of coordinate offset, field mask, data aggregation, and identity stripping.
[0045] The desensitized vehicle data mentioned above refers to vehicle data after desensitization processing, in which sensitive information is reduced or eliminated. The desensitized vehicle data retains the usability of the data while improving the security and privacy protection level of the data.
[0046] The embodiments of the present disclosure adopt fixed or pre-set desensitization rules according to actual needs. The embodiments of the present disclosure flexibly adjust and implement desensitization strategies according to the actual sensitivity of vehicle data and the characteristics of the application scenario, to ensure the accuracy and adaptability of data protection.
[0047] In the embodiments of the present disclosure, the vehicle data is desensitized based on the target sensitivity level and the data application scenario. First, the target sensitivity level of each item of data is determined by analyzing the inherent attributes of the vehicle data and the potential consequences of leakage. Second, after obtaining the data access instruction, the application scenario is further analyzed, including data usage, access subject, and scene security level. Finally, according to the target sensitivity level and the characteristics of the data application scenario, corresponding desensitization processing is performed to remove or obscure sensitive information, and desensitized vehicle data is generated.
[0048] For example, location information is marked as a very high sensitivity level, while vehicle brand information is considered as a low sensitivity level. Desensitization processing can include coordinate blurring, field partial hiding, statistical period adjustment, or identity information stripping.
[0049] The embodiments of the present disclosure improve the security and privacy protection level in the data transmission process by dynamically desensitizing the vehicle data based on the target sensitivity level and the data application scenario. Desensitization processing can effectively reduce the exposure of sensitive information during transmission and storage.
[0050] In S108, the authorized access data in the desensitized vehicle data is determined based on the scene security level of the data application scenario and the access permission level of the client, and the authorized access data is sent to the client.
[0051] The authorized access data is the data in the desensitized vehicle data that is allowed to be accessed by the client.
[0052] The access permission level refers to the permission level corresponding to the authentication result of the client in the vehicle data access system, reflecting the type and sensitivity level of vehicle data that the client can access. The authorized access data refers to vehicle data that has been desensitized and meets the requirements of the data application scenario security level and the client access permission level, i.e., the specific data set that the client is allowed to access.
[0053] The scenario security level refers to the data security risk level defined and evaluated according to the specific environment and conditions during data access and use in the intelligent networked vehicle data processing process.
[0054] In the embodiments of the present disclosure, the authorized access data is determined from the desensitized vehicle data based on the scenario security level of the data application scenario and the access permission level of the client. The embodiments of the present disclosure generate a set of authorized access data by dynamically analyzing the characteristics of the data application scenario and the access conditions of the client. This dynamic authorization mechanism based on scenarios and permissions enhances the pertinence and flexibility of privacy protection. Secondly, the client access permission level is verified through identity authentication and permission review to determine the range of vehicle data types and sensitivity levels that the client can access. Then, the scenario security level and the client access permission level are compared with the classification and grading information of the desensitized vehicle data to determine the specific data subset that the client can access. In the embodiments of the present disclosure, first, the data application scenario and the scenario security level are analyzed to analyze the data access instructions of the client and identify the specific details of the data application scenario, while evaluating the security level of the current environment.
[0055] For example, if the application scenario involves vehicle remote diagnosis and the client is located in a secure private network, it will be determined that the scenario security level is high.
[0056] The embodiments of the present disclosure determine the authorized access data based on the scenario security level of the data application scenario and the access permission level of the client, achieving management and dynamic improvement of data access control. This method ensures that the client can access information within its permission range when accessing vehicle data, without touching private data beyond its scenario security level and permission level.
[0057] In the embodiments of the present disclosure, upon receiving a data access instruction of a client for a vehicle, vehicle data corresponding to the data access instruction is acquired, and a data application scenario corresponding to the vehicle data is acquired; a target sensitive level corresponding to the vehicle data is determined from a plurality of sensitive levels, wherein different sensitive levels are used to quantify different severity levels of vehicle data leakage; based on the target sensitive level and the data application scenario, desensitization processing is performed on the vehicle data to obtain desensitized vehicle data; based on a scene security level of the data application scenario and an access permission level of the client, authorized access data in the desensitized vehicle data is determined, wherein the authorized access data is data in the desensitized vehicle data that is allowed to be accessed by the client. Through the fusion analysis of multiple source information such as data use, access subject, and scene security level, the specific scene of current data processing is identified in real time, and the collected private data is classified and graded, and the sensitivity of each type of data is determined, so as to facilitate subsequent targeted protection, so as to achieve the purpose of dynamically adjusting the parameters of the desensitization algorithm or selecting different desensitization methods according to the identified scene characteristics and data sensitivity level, thereby realizing the technical effect of being able to provide customized protection measures for different data types and scenes, including desensitization processing of data itself, and also covering dynamic adjustment of access permission, to ensure the safe access of data, thereby solving the technical problem of low data transmission security.
[0058] Optionally, determining the target sensitive level corresponding to the vehicle data from the plurality of sensitive levels comprises: determining a target data category corresponding to the vehicle data from a plurality of data categories, and determining a data refinement degree of the vehicle data, wherein the data refinement degree is used to represent the collection accuracy of the vehicle data; and determining the target sensitive level from the plurality of sensitive levels based on the data refinement degree and the target data category of the vehicle data.
[0059] The plurality of data categories described above are a plurality of categories obtained by dividing vehicle data according to different information types in the field of intelligent networked vehicles, including but not limited to position information, driving behavior information, biometric information, vehicle state information, etc. Each data category corresponds to different data collection and processing requirements, and different privacy protection needs.
[0060] In the embodiments of the present disclosure, it is determined which category or categories of data are selected as the target data category for processing and use according to the purpose of data processing (i.e., data use). The selection of the target data category is based on data requirements, ensuring that the collected and processed data meet the implementation of specific functions while avoiding the collection of irrelevant or overly sensitive data for the functions, reducing privacy risks.
[0061] The data refinement degree refers to the accuracy or detail level of the vehicle data when collected. Taking location information as an example, the data refinement degree is reflected in the accuracy of the latitude and longitude of the location. For example, high refinement degree refers to location data accurate to the meter level, while low refinement degree refers to data accurate to the kilometer level or larger range. The collection accuracy described above is a specific embodiment of the data refinement degree. The collection accuracy describes the accuracy or resolution when collecting data. High collection accuracy usually means that the data is more detailed and specific.
[0062] The plurality of sensitivity levels described above are obtained by dividing the vehicle data according to the leaked private information and potential risks. For example, the data sensitivity levels are divided into four levels: very high, high, medium, and low, to guide the processing and protection strategies of the data.
[0063] The target sensitivity level described above is the minimum protection requirement established for a specific data category and data use. That is, the minimum privacy protection strength that should be taken to ensure data security when processing a certain type of data. The target sensitivity level is set based on the data refinement degree and the target data category, aiming to balance the needs of data protection and function implementation.
[0064] In the embodiments of the present disclosure, first, the target data category corresponding to the vehicle data is determined from a plurality of data categories. Then, according to the target data category and the functional requirements, the refinement degree of the data, i.e., the accuracy requirement when collecting data, is determined. After the data refinement degree and the target data category are determined, the target sensitivity level is determined from a plurality of sensitivity levels according to a preset rule, to guide the subsequent data processing and protection strategies.
[0065] For example, when implementing the automatic driving function, real-time location information and vehicle state information are determined as the target data category that needs to be collected and processed. The data refinement degree of the location information needs to be accurate to the meter level to support accurate navigation.
[0066] For example, considering the automatic driving scenario, high-precision location data is needed, but location data also belongs to the very high sensitivity level. In this scenario, although high-precision location data is collected and used, information directly related to the user's identity is removed through desensitization processing, and high-strength encryption is used in the data transmission and storage process to reduce the risk of privacy leakage.
[0067] The embodiments of the present disclosure realize accurate control of vehicle data in the process of collection, processing and use, dynamically determine the collection accuracy, target data category and sensitive level of the data, ensure that the data meets the functional implementation requirements while taking privacy protection measures. This mechanism effectively reduces the risk of data leakage and improves the security and privacy protection level of data use. Especially in the complex application scenarios of intelligent and connected vehicles, it can flexibly adapt to different data processing needs and security levels, providing a more secure solution for vehicle data management and use.
[0068] Optionally, based on the target sensitive level and the data application scenario, the vehicle data is desensitized to obtain desensitized vehicle data, including: determining the desensitization strength based on the target sensitive level; determining the desensitization object in the vehicle data based on the data application scenario, wherein the desensitization object is used to represent the object to be desensitized; and desensitizing the desensitization object in the vehicle data based on the desensitization strength to obtain the desensitized vehicle data.
[0069] The target sensitive level described above is a pre-set privacy protection strength level in the intelligent and connected vehicle privacy protection framework according to the attributes and processing requirements of the data. The desensitization strength described above refers to the degree of privacy protection processing of the data, that is, the degree of modification, fuzzification or replacement of the data. High desensitization strength means more thorough modification of the data to prevent leakage of sensitive information, while low desensitization strength retains more details to support data analysis or specific function implementation.
[0070] The desensitization object described above refers to the data part that needs to be desensitized in a specific application scenario. In the intelligent and connected vehicle environment, the desensitization object is any vehicle data field that leaks privacy, such as Global Positioning System (GPS) coordinates, vehicle fault codes, driver biometric data, etc.
[0071] The desensitization processing described above is a privacy protection technology that modifies or fuzzifies the data without significantly affecting the value of the data to eliminate or reduce sensitive information in the data. Common desensitization methods include coordinate offset, field masking, data aggregation, etc.
[0072] In the embodiments of the present disclosure, the target sensitive level is determined based on the sensitivity of the data itself and the security requirements of the application scenario, and is the basis for selecting the desensitization strength. Then, according to the specific data application scenario, the object that needs to be desensitized is determined, that is, which data field should be processed in the current scenario. Finally, the desensitization object is processed according to the selected desensitization strength to generate desensitized vehicle data.
[0073] Exemplarily, in the scenario of pushing the advertisement to the third-party service provider, it is determined that the target sensitive level is the extremely high sensitive level, that is, the data involving the accurate position information needs to be protected at a high level. Based on the target sensitive level, the desensitization object is identified as the real-time GPS coordinate. Then, according to the requirement of the high desensitization strength, the coordinate offset and the fuzzification method are adopted to process the real-time GPS coordinate, so as to obtain the desensitized vehicle data. The accurate position information has been effectively hidden, avoiding the third-party service provider from using the data to deduce the specific position in the low security level scenario.
[0074] Exemplarily, when the maintenance personnel accesses the vehicle data in the regular maintenance scenario, the desensitization object is determined as the vehicle fault code and the battery status according to the medium sensitive level and the specific maintenance requirement. At the same time, the corresponding desensitization strength (such as the field partial mask) is adopted for processing, which can prevent the leakage of the fault code and the battery status, and will not affect the accurate judgment of the vehicle status by the maintenance personnel, ensuring the smooth progress of the maintenance work. This fine-grained desensitization processing based on the scene requirement not only improves the security of the data, but also maintains the practicability of the data, significantly enhancing the effectiveness and flexibility of the privacy protection strategy.
[0075] The embodiments of the present disclosure ensure the privacy protection adaptability of the data in different application scenarios through the desensitization strength and the selected desensitization object. This mechanism can effectively prevent the leakage of sensitive information during the processing and use of the data, while retaining the use value of the data, meeting the diversified functional requirements of the intelligent connected vehicle.
[0076] Optionally, the desensitization object in the vehicle data is desensitized based on the desensitization strength to obtain desensitized vehicle data, including: determining a target desensitization operation type corresponding to a target data category from a plurality of desensitization operation types, wherein the data categories corresponding to different desensitization operation types are different; and desensitizing the desensitization object in the vehicle data according to the desensitization strength based on the target desensitization operation type to obtain the desensitized vehicle data.
[0077] The plurality of desensitization operation types described above are a plurality of types in the intelligent connected vehicle privacy protection system. Each type is designed for different data characteristics and requirements to achieve a specific privacy protection effect. For example, coordinate offset is used for position information protection, field mask is suitable for partial occlusion of biometric features, data aggregation can be applied to driving behavior statistics, and identity stripping is used to remove personal identification information in the data. Different desensitization operation types correspond to different data categories to ensure targeted implementation of privacy protection.
[0078] The target desensitization operation type described above refers to the desensitization operation type that is most suitable for a given data application scenario and target data category. According to the data characteristics, application scenario requirements and security level, the target desensitization operation type is selected to achieve a better balance between privacy protection and function implementation.
[0079] The above-mentioned desensitization strength describes the depth of the desensitization operation, that is, the degree of modification of the data to ensure the elimination or reduction of sensitive information. In the embodiments of the present disclosure, the desensitization strength will be dynamically adjusted according to the target sensitive level and the security requirements of the data application scenario, so as to find a proper balance point between privacy protection and data usability.
[0080] Firstly, the embodiments of the present disclosure need to determine the most suitable operation type corresponding to the target data category from multiple desensitization operation types. This process relies on in-depth understanding of the data and analysis of the application scenario. For example, for location data, coordinate offset is selected as the target desensitization operation type; and for biometric information, field masking is used. Next, based on the selected target desensitization operation type, the desensitization strength is determined in combination with the target sensitive level and the security requirements in the current scenario, to guide the desensitization processing of the data. For example, in a high-risk application scenario, the desensitization strength will be set higher to ensure that the data will not leak sensitive information during transmission and storage. Finally, according to the determined desensitization strength, the operation required by the target desensitization operation type is performed on the desensitization object in the vehicle data, to generate desensitized vehicle data.
[0081] Exemplarily, in the scenario of pushing advertisements to third-party service providers, the precise location information of the user is protected from being obtained by the third-party service providers. At this time, firstly, the location information is determined as the target data category, and coordinate offset is selected as the target desensitization operation type. Then, considering that the security level in the scenario of pushing advertisements to third-party service providers is low, the desensitization strength is set higher, and the real-time GPS coordinates are greatly offset and blurred, so as to reduce the risk of location leakage. Finally, the coordinate offset operation with high desensitization strength is applied to process the location information in the vehicle data, to generate desensitized vehicle data, so as to ensure that the precise location of the user will not be leaked when the data is provided to the third-party service providers.
[0082] Exemplarily, in the scenario of maintenance diagnosis by a third-party maintenance agency, vehicle fault codes (belonging to state class data, with a medium-sensitive level) and driving habit data (behavior class data, with a high-sensitive level) become the target data category. Data aggregation (statistical in weeks instead of real-time recording) is selected as the target desensitization operation type for the driving habit data, and an appropriate desensitization strength is set to retain the analysis value of the data. The vehicle fault codes are slightly processed through field masking, to ensure that the third-party maintenance agency can quickly diagnose the problem, but direct exposure of the fault codes is avoided. This flexible desensitization mechanism not only guarantees the usability of the data, but also significantly reduces the risk of privacy leakage, and improves the overall privacy protection level.
[0083] By determining the target desensitization operation type and adjusting the desensitization strength, the embodiments of the present disclosure can provide customized privacy protection strategies for different data categories and application scenarios. This method not only enhances the pertinence and effectiveness of data protection, but also ensures that vehicle data can effectively avoid the improper disclosure of sensitive information while supporting the implementation of vehicle functions.
[0084] Optionally, based on the scene security level of the data application scenario and the access permission level of the client, the authorized access data in the desensitized vehicle data is determined, including: determining the authorized access data type of the client based on the scene security level of the data application scenario and the access permission level of the client; and determining the authorized access data corresponding to the authorized access data type from the desensitized vehicle data.
[0085] The above-mentioned data application scenario refers to a specific environment or functional requirement in which vehicle data will be applied, such as automatic driving control, remote fault diagnosis, advertisement recommendation, etc. Each scenario has different requirements for data and different levels of attention to privacy protection.
[0086] The above-mentioned scene security level is a security standard for evaluating the data transmission and processing environment in the data application scenario. It is usually determined based on the security of network connection, the security of physical environment, and the sensitivity level of data, and is divided into high security (such as private Wi-Fi network), medium security (such as public parking lot), and low security (such as open road Wi-Fi hotspot) levels. The above-mentioned access permission level is the authorization level of the client when accessing vehicle data, reflecting the type and sensitivity of data that the client can access. The higher the permission level, the more sensitive data the client can access.
[0087] The above-mentioned authorized access data type refers to a specific type of data that the client is allowed to access based on the access permission level of the client and the security level of the data application scenario, such as location data, driving behavior data, vehicle status data, etc. The above-mentioned authorized access data is the data that the client can legally access, which is filtered from the desensitized vehicle data according to the authorized access data type.
[0088] In the embodiments of the present disclosure, the type of data that the client can access is determined according to the combination of the scene security level of the data application scenario and the access permission level of the client. Specifically, the role of the client (such as the vehicle manufacturer), the scene characteristics of the request access (such as whether it is a high-security environment), and the sensitivity level of the data are comprehensively analyzed to generate a fine-grained "data type-client" access control list. Subsequently, the data that the client is authorized to access is extracted from the desensitized vehicle data according to the control list, ensuring that the data meets the functional requirements when being used and does not exceed the permission range, effectively protecting the user privacy.
[0089] For example, in the repair diagnosis scenario of a third-party repair institution, based on the access permission level of the third-party repair institution and the scenario feature of the medium security level, it is determined that the third-party repair institution can access the desensitized vehicle state data and part of the driving behavior data (such as fault codes of medium sensitive level and statistics of emergency braking times). Then, the authorized access data related to repair diagnosis is filtered from the desensitized vehicle data, such as recent vehicle fault codes and battery status information, which is provided to the third-party repair institution, without including location data or biometric data (extremely high sensitive level), even if it has been desensitized, to ensure strict control of data access and privacy protection.
[0090] The embodiments of the present disclosure achieve fine-grained management of vehicle data by dynamically adjusting authorized access data types and access control based on permission levels. This mechanism ensures that in different data application scenarios, the data accessible by the client meets its functional needs and does not exceed its permission range, effectively balancing the needs of data availability and user privacy protection, and improving the accuracy and flexibility of privacy protection for intelligent networked vehicles.
[0091] For example, in the data analysis application scenario of the vehicle enterprise, the embodiments of the present disclosure allow the vehicle manufacturer to access the security level of the desensitized driving behavior data, but limit the time span of access (such as weekly statistics instead of real-time). This access control strategy based on scenarios and permissions ensures that the vehicle enterprise can conduct effective data analysis.
[0092] Optionally, sending the authorized access data to the client includes: encrypting the authorized access data based on the target sensitive level and the scenario security level to obtain encrypted vehicle data; and transmitting the encrypted vehicle data to the client.
[0093] The above encryption is a data protection technology that converts original data into ciphertext through an algorithm, and only authorized parties with the correct key can decrypt it to prevent unauthorized access and data leakage during data transmission or storage.
[0094] The above-mentioned encrypted vehicle data refers to data that has been encrypted according to the requirements of the target sensitive level and the scenario security level. Encryption technology ensures that data is not illegally intercepted and interpreted during transmission.
[0095] The above transmission to the client means sending the encrypted authorized access data to the designated access, i.e. the client, to ensure that the data is protected during transmission and only decrypted and used by the legitimate recipient after reaching the destination.
[0096] In the embodiments of the present disclosure, the encryption strategy is dynamically adjusted based on the target sensitivity level and the scene security level to ensure the security of the authorized access data during transmission. Specifically, the sensitivity level of the data and the security level of the current scene are analyzed, and a suitable encryption algorithm and key update frequency are selected according to the preset rules to encrypt the authorized access data and generate encrypted vehicle data. Subsequently, the encrypted vehicle data is transmitted to the client through a secure communication channel to ensure the confidentiality and integrity of the data during transmission.
[0097] For example, in the maintenance diagnosis scene of a third-party maintenance institution, it is determined that the authorized access data includes part of the driving behavior data (high sensitivity level) and vehicle state data (medium sensitivity level). According to the embodiments of the present disclosure, since the data involves high sensitivity level and the scene security level is medium security level, the Advanced Encryption Standard (AES) is selected for encryption, and the key update frequency is set according to the data sensitivity and scene risk. In the data transmission stage, the encrypted authorized access data is securely transmitted to the third-party maintenance institution, ensuring that the data cannot be interpreted without authorization, thereby effectively improving the security of data transmission and the protection level of user privacy.
[0098] The encryption technology of the embodiments of the present disclosure dynamically adjusts the encryption strategy by combining the target sensitivity level and the scene security level to ensure the security of the authorized access data during the transmission process, preventing data leakage and unauthorized access. This mechanism of adaptively adjusting the encryption strength according to the data sensitivity and environmental risk not only strengthens data protection but also improves encryption efficiency, avoiding resource waste caused by over-encryption of low-sensitive data, and avoiding insufficient encryption strength of high-sensitive data in low-security scenes, thereby building a secure and reliable data transmission channel for intelligent connected vehicle data transmission.
[0099] For example, in the application scene of remote upgrading by the vehicle manufacturer, the embodiments of the present disclosure allow the vehicle manufacturer to access vehicle state data, which is of medium sensitivity level. Since the scene security level is at a high security level, a lower strength encryption algorithm such as Advanced Encryption Standard 128-bit (AES-128) is used during data transmission, and the key update frequency is relaxed to improve data transmission efficiency. This approach not only ensures the security of data transmission but also takes into account the data transmission speed requirements in scenes such as remote upgrading, achieving a balance between security and efficiency and improving the overall efficiency of intelligent connected vehicle data management.
[0100] Optionally, the method further comprises: obtaining the number of abnormal accesses of the client to the vehicle data, the number of times of desensitization reverse deduction of the vehicle data, and the number of times of abnormal encryption of the vehicle data, wherein the number of times of desensitization reverse deduction is used to represent the number of times of successful reverse deduction of the desensitized vehicle data, and the number of times of abnormal encryption is used to represent the number of times of abnormal encryption of the vehicle data; performing risk assessment on the vehicle data based on the number of abnormal accesses, the number of times of desensitization reverse deduction, and the number of times of abnormal encryption, to obtain a risk value of the vehicle data; and adjusting the desensitization intensity corresponding to the access permission level and the target sensitive level based on the risk value, the number of abnormal accesses, and the number of times of desensitization reverse deduction.
[0101] The number of abnormal accesses mentioned above refers to the number of times of attempts of the client to access unauthorized data or access data in an irregular manner within a period of time. This indicator is an important parameter for evaluating the effectiveness of the system access control strategy, and reflects the frequency of violation of the access control rules.
[0102] The number of times of desensitization reverse deduction mentioned above refers to the number of times of successful recovery of original sensitive information by attackers or unauthorized parties through reverse analysis of the desensitized vehicle data. The number of times of desensitization reverse deduction measures the robustness of the desensitization algorithm, that is, the ability of the desensitized data to maintain privacy protection when facing malicious attacks or analysis.
[0103] The number of times of abnormal encryption mentioned above refers to the number of times of abnormal situations encountered by the vehicle data during encryption or after encryption, including encryption failure, key management error, encryption algorithm cracking, and the like. The number of times of abnormal encryption reflects the stability and security of the encryption mechanism.
[0104] The risk assessment mentioned above is to comprehensively evaluate the security risk degree of the vehicle data under the privacy protection mechanism by analyzing the number of abnormal accesses, the number of times of desensitization reverse deduction, the number of times of abnormal encryption, and the like, to generate a risk value for guiding subsequent strategy adjustment.
[0105] The risk value mentioned above is a quantitative indicator for representing the privacy leakage risk degree in the intelligent connected vehicle data processing process. The risk value comprehensively considers the risk factors such as the number of abnormal accesses, the number of times of desensitization reverse deduction, and abnormal encryption, and is calculated through a specific algorithm to guide the dynamic adjustment of the system. In the embodiments of the present disclosure, firstly, the number of abnormal accesses of the client to the vehicle data, the number of times of successful reverse deduction of the desensitized vehicle data, and the number abnormal situations encountered during data encryption are monitored and counted. Subsequently, based on these statistical data, a specific algorithm (such as weighted summation) is used for risk assessment to calculate a quantitative indicator, that is, the risk value. Finally, according to the risk value and the detailed information of abnormal access and desensitization reverse deduction, the desensitization intensity corresponding to the access permission level and the target sensitive level is dynamically adjusted to realize real-time improvement of the privacy protection strategy.
[0106] For example, if it is detected that the abnormal access frequency of the third-party service provider in the advertisement pushing scenario frequently increases, and the desensitization reverse pushing frequency also increases, a higher risk value will be calculated. Based on the risk assessment result, the access permission of the third-party service provider is automatically tightened, the access frequency of the third-party service provider to data above a high sensitivity level (such as driving behavior records) is reduced, and the desensitization processing strength is enhanced, such as increasing time fuzzing processing on driving behavior data, to reduce the risk of privacy leakage. At the same time, the effectiveness of the encryption mechanism is checked, such as whether the encryption algorithm is cracked, whether the encryption abnormality frequency increases, and the encryption strategy is further improved to ensure the security of data in the transmission and storage process.
[0107] The embodiments of the present disclosure effectively improve the flexibility and security of the intelligent networked vehicle data protection mechanism by monitoring the abnormal access, desensitization reverse pushing and encryption abnormality of vehicle data in real time, and dynamically adjusting the access control and desensitization strategy based on risk assessment. This dynamic adjustment strategy based on risk assessment can timely respond to changes in the data security environment, enhance the adaptive ability of the system, reduce the risk of privacy leakage, and improve the overall efficiency of data protection.
[0108] For example, in the scenario of a repair mechanism for repair diagnosis, if the system monitors an increase in abnormal access frequency, indicating an increase in data protection vulnerability. At this time, the embodiments of the present disclosure will dynamically adjust and increase the authentication requirements for the repair mechanism to access data of a medium sensitivity level (such as vehicle status information). At the same time, the desensitization algorithm is enhanced, such as using more complex field masking technology for vehicle status information to reduce the risk of successful desensitization reverse pushing. In addition, the encryption mechanism during data transmission is strengthened, such as increasing the encryption strength to a higher encryption strength and accelerating the key update frequency, to further ensure the security of data in the repair diagnosis scenario.
[0109] Optionally, the access permission level and the desensitization strength corresponding to the target sensitivity level are adjusted based on the risk value, including: if the risk value is greater than a first preset threshold and the abnormal access frequency is greater than a first preset number, the access permission level of the client is reduced; if the risk value is greater than the first preset threshold and the desensitization reverse pushing frequency is greater than a second preset number, the desensitization strength is enhanced; if the risk value is less than a second preset threshold, the access permission level is increased, and / or the desensitization strength is weakened, wherein the second preset threshold is less than the first preset threshold.
[0110] The above-mentioned preset threshold is used to determine whether the risk value reaches a level that requires action. The first preset threshold and the second preset threshold are respectively used to distinguish between high-risk and low-risk situations, wherein the second preset threshold is less than the first preset threshold, which enables the system to respond accordingly based on the different degrees of risk.
[0111] The access permission level reflects the permission range of the client to access the vehicle data legally. In the embodiments of the present disclosure, the access permission level of the client is dynamically adjusted according to the risk assessment result to control data access and adapt to the needs of different security levels.
[0112] In the embodiments of the present disclosure, the access behavior of the client to the vehicle data and the state of data protection are continuously monitored, and corresponding policy adjustments are taken according to the risk value and abnormal situations. When the risk value is greater than the first preset threshold and the number of abnormal accesses is greater than the first preset number, it indicates that there is a high-risk unauthorized access threat at present, and therefore the access permission level of the client can be reduced to reduce the potential risk of privacy leakage. If the risk value also exceeds the first preset threshold, but the abnormal situation is that the number of desensitization reverse pushing is higher than the second preset number, it indicates that the existing desensitization processing is not enough to prevent sensitive information from being restored. At this time, the desensitization strength corresponding to the target sensitive level is enhanced, and the desensitization algorithm or the desensitization level is increased to strengthen the privacy protection of the data. On the contrary, when the risk value is lower than the second preset threshold, it indicates that the current environment is relatively safe, and the access permission level of the client and / or the desensitization strength of the target sensitive level can be improved to improve the availability and processing efficiency of the data on the premise of controllable risk.
[0113] Exemplarily, in the maintenance diagnosis scene of the third-party maintenance institution, if it is monitored that the number of abnormal accesses suddenly increases and the risk value breaks through the first preset threshold, it means that the third-party maintenance institution has unauthorized access behavior or there is a loophole in the internal data processing flow. In this case, the access permission level of the third-party maintenance institution is immediately reduced, for example, from allowing access to all historical fault data to only being able to access data in the past week, to reduce the exposure opportunity of sensitive information. On the other hand, if the monitoring data indicates that the number of desensitization reverse pushing exceeds the second preset number, even if the number of abnormal accesses does not reach the first preset number, the desensitization strength of the sensitive level data such as fault codes will be enhanced, for example, by increasing the random disturbance range or using a more complex desensitization algorithm, to prevent sensitive information from being restored by reverse engineering. Finally, assuming that after a period of time, if the risk value is stably lower than the second preset threshold and there is no abnormal access or desensitization reverse pushing event, the access permission of the third-party maintenance institution will be improved to allow it to access fault data with a longer time span. At the same time, the desensitization strength is relaxed, the delay of data processing is reduced, and the work efficiency of maintenance diagnosis is improved, on the premise of ensuring data security is not threatened.
[0114] The embodiments of the present disclosure achieve real-time monitoring and intelligent response to intelligent connected vehicle data access risks by setting two preset threshold values and dynamically adjusting access permission levels and desensitization strength, effectively improving the flexibility and reliability of the data protection mechanism. This mechanism not only quickly responds to high-risk situations to prevent data leakage, but also relaxes control in low-risk environments to promote effective use of data, ensuring a balance between security and usability for vehicle data, and providing strong technical support for the intelligent connected vehicle industry.
[0115] FIG. 2 is a flowchart of an optional vehicle data processing method according to an embodiment of the present disclosure. As shown in FIG. 2, the specific process is as follows:
[0116] S1, classification and grading. The classification and grading operation described above is performed after data collection. The sources of private data collection include vehicle-mounted sensors (cameras, positioning systems, radars), vehicle-mounted systems (driving behavior records, biometric data), and vehicle-to-everything (V2X) communication data (vehicle-to-vehicle and vehicle-to-road interaction data).
[0117] For example, first, the data processing component of the vehicle-mounted system captures the video stream input signal from the front camera. Then, the vehicle-mounted system further analyzes the video stream and identifies the key features of the driver's face image contained therein. Finally, after completing the sensitivity assessment, the vehicle-mounted system labels the data set as a higher sensitive level and stores this level information.
[0118] S2, scene recognition. Real-time information collected by the vehicle-mounted system and external sensors, such as vehicle status, user operation, network environment, and geographic location, is combined with a pre-defined scene feature library to dynamically identify the current data application scenario (including data use, access subject, and scene security level). For example, when a request for remote diagnosis is received, in combination with the fact that the vehicle is currently stationary and connected to an authenticated private network, the vehicle-mounted system identifies the current scenario as "maintenance diagnosis - maintenance personnel - high security environment" (represented as a three-tuple of use - subject - security level).
[0119] S3, dynamic desensitization. According to the scene features and data sensitivity levels identified in S2, dynamically select and apply corresponding desensitization algorithms and techniques to process sensitive information in vehicle data. For example, for high-sensitivity location data, in the "advertising push - third-party service provider - low security environment" scenario of S2, coordinate offset and fuzzification processing is used to reduce data accuracy to the kilometer level, while removing timestamp associations to reduce the risk of data leakage.
[0120] S4, Dynamic Access Control. Based on the data sensitivity levels determined in S1, the scenario features identified in S2, and the data de-sensitization in S3, dynamic access permission rules are generated. Through the access control component, all client access requests are monitored and managed in real-time, ensuring that only requests that meet the rules are allowed to access specific data. For example, in the "Maintenance Diagnosis - Third-Party Maintenance Agency - Medium Security Environment" scenario, permissions are dynamically adjusted to allow maintenance personnel to access vehicle fault data within the past 7 days, but prohibit access to the driver's biometric information.
[0121] S5, Dynamic Encryption Transmission and Storage. Based on the information in S2 and S3, the algorithm and key strength of data encryption are dynamically adjusted to ensure the security of data during transmission and storage. For example, for P1 or P2 level data, in the "Emergency Rescue - Emergency Service Department - Low Security Environment" scenario, the Advanced Encryption Standard (AES-256) encryption algorithm is used. For P3 or P4 level data, in the "Vehicle Health Monthly Report - Vehicle Owner - High Security Level" scenario, the Advanced Encryption Standard (AES-128) encryption algorithm is used. Encryption keys are dynamically generated by security chips to ensure secure data transmission in non-secure network conditions.
[0122] S6, Risk Monitoring. The vehicle-mounted system continuously monitors the access of vehicle data and changes in the security environment, and calculates the privacy risk value in real time by evaluating abnormal access frequency, insufficient de-sensitization, and encryption anomalies. Once the risk value exceeds the set threshold, the risk response mechanism is immediately activated, notifying relevant personnel or automatically adjusting security policies. For example, when a certain Internet Protocol (IP) address is found to frequently attempt to access high-sensitive level vehicle data, the vehicle-mounted system will automatically increase the encryption strength of the data and limit the access permissions of the relevant IP.
[0123] S7, Policy Improvement. Based on the risk detection results in S6, the policy improvement component analyzes the source and nature of the risk, dynamically adjusts the de-sensitization rules in S3, the access permission settings in S4, and the encryption policy in S5 to adapt to the new security situation. For example, if the vehicle-mounted system detects an increase in off-site access requests for vehicle data in recent days, it needs to temporarily increase the degree of data de-sensitization and strengthen authentication and auditing for remote access clients to prevent potential data leaks. After the policy is improved, the data is sent to the client.
[0124] FIG. 3 is a schematic diagram of a system structure of a vehicle data processing system according to an embodiment of the present disclosure, which includes a data classification component, a scene identification component, a dynamic de-sensitization component, a policy improvement component, a risk monitoring component, a dynamic encryption component, and an access control component.
[0125] The data classification component is configured to implement data classification grading, and the classification criteria and grading rules of the data classification component are flexibly set according to actual needs. The classification criteria are classified by data type into location type (such as real-time positioning coordinates, trajectory data), identity type (such as driver facial recognition features, account information), behavior type (such as acceleration / brake frequency, driving time), state type (such as vehicle fault code, battery status), and environment type (such as in-vehicle image, out-of-vehicle road condition image). The grading rules are classified by sensitivity into four levels: very high (P1), high (P2), medium (P3), and low (P4).
[0126] The grading rules are set as P1, P2, P3, and P4. Among them, P1 is data directly associated with user identity and with serious consequences after leakage, such as driver facial recognition original features and real-time location trajectory accurate to within 1 meter. P2 is data indirectly associated with identity but sensitive, such as driving habits (frequent acceleration / brake) and vehicle identification number (VIN) (after preliminary anonymization processing). P3 is data with low identity association but needs to be protected, such as vehicle battery status and regular fault codes. P4 is public or low-sensitive data, such as vehicle brand and model and public road conditions (non-specific area).
[0127] By way of example, through preset feature library matching, positioning coordinates (accuracy ≤ 1 meter) are marked as P1, vehicle frequent acceleration times statistics are marked as P2, and battery power data are marked as P3.
[0128] The scene recognition component identifies the scene through multi-source information fusion, wherein the multi-source information is data usage, access subject, scene security level, and scene output. For data usage, the data use purpose is obtained through the vehicle-mounted system interface, such as automatic driving control (high-precision position is required), over-the-air (OTA) (vehicle status is required), advertisement pushing (area preference is required), and maintenance diagnosis (fault data is required). For access subject, the access party is identified through identity authentication, such as the car owner (himself), car enterprise service provider, third-party maintenance agency, and road management department. For scene security level, it is determined based on network security monitoring (such as whether connected to a trusted network) and physical environment (such as whether in a private garage), and is divided into high security (S1), medium security (S2), and low security (S3). For scene output, it can be represented by a triple of “usage-subject-security level”, such as “automatic driving-car owner-S1” and “maintenance diagnosis-third-party maintenance agency-S2”.
[0129] The dynamic desensitization component generates a desensitization strategy according to the data sensitivity level (P1-P4) and the scene triple. For P1-level data and the scene “automatic driving-car owner-S1”, the original precision (≤1 meter) is retained, and only the identity is desensitized (such as removing the user ID association in GPS data), for example, the scene is “advertisement pushing-third-party service provider-S3”, coordinate offset + fuzzing is adopted, the position precision is reduced to an area of more than 1 kilometer, and the timestamp association is removed. For P2-level data and the scene “maintenance diagnosis-maintenance agency-S2”, the original driving habit data (such as the number of sudden accelerations) is retained, but the specific occurrence time is hidden, for example, the scene is “data analysis-car enterprise-S2”, the driving habit data is aggregated (such as weekly statistics instead of real-time). P3-level data can use field partial masking, such as battery status only showing “normal / low” instead of specific values. P4-level data does not need to be desensitized or only needs to be slightly processed (such as removing redundant fields).
[0130] The above scene recognition component also includes a desensitization algorithm, including coordinate offset (based on Gaussian noise), field masking (part of the characters are replaced with “*”), data aggregation (statistical period is extended), and identity stripping (removing direct association with user ID).
[0131] The access control component implements fine-grained authorization, including attribute definition, rule engine, and dynamic adjustment of permissions. The attribute definition includes subject attributes (identity type, authentication level), scenario attributes (purpose, security level), and data attributes (sensitivity level). The rule engine uses "if-then" rules. For example, Rule 1: If subject = car owner and purpose = autonomous driving and data level ≤ P2, then grant "read-real-time" permission. Rule 2: If subject = third-party maintenance agency and purpose = repair diagnosis and security level = S2 and data level ≤ P3, then grant "read-specific time period" permission (only the last 7 days of fault data). Rule 3: If subject = third-party service provider and data level = P1, then deny access regardless of the scenario. The dynamic adjustment of permissions includes real-time updating of permissions when the scenario changes (e.g., from "S2" to "S3"), such as automatically revoking P3-level data access permissions when the security level of the repair scenario decreases.
[0132] The dynamic encryption component adjusts the encryption strategy based on the data sensitivity level and the scenario security level, including transmission encryption and storage encryption. Transmission encryption is P1 or P2 level data + scenario security level S3, using AES-256 encryption algorithm, with key dynamic update every 10 seconds. P3 or P4 level data + scenario security level S1, using AES-128 encryption, with key update every 5 minutes. Storage encryption is used when desensitized data is stored, using "encryption + hash check". The hash value is dynamically updated with the desensitization strategy to ensure that the data has not been tampered with. For example, P1 level data is transmitted in S3 scenario, triggering AES-256 encryption, and the key is dynamically generated by a secure chip and not stored in regular memory.
[0133] The risk monitoring component assesses risk through multi-dimensional indicators, with the formula: R = α × A + β × D + γ × E
[0134] Where A is the number of abnormal access times (access attempts that do not meet the rules within a unit of time); D is the number of times the desensitization intensity is insufficient (the number of times sensitive information can be inferred from desensitized data); E is the number of encryption anomalies (transmission / storage encryption failures or key leakage warnings); R is the risk value; α, β, and γ represent the influence of abnormal access times, insufficient desensitization intensity times, and encryption anomaly times on the risk value, with larger values representing greater influence on the risk value, and α + β + γ = 1. For example, α = 0.4, β = 0.3, γ = 0.3, and the R risk value threshold can be set to 0.6 (after normalization, it can be limited to 0-1), and exceeding the threshold triggers a risk response.
[0135] The policy improvement component adjusts the policy based on the risk value R. If R>0.6 and A is dominant, the access rights of the abnormal subject are temporarily frozen, and the access control rules are tightened (such as increasing the identity authentication level). If R>0.6 and D is dominant, the desensitization strength is enhanced (such as reducing the precision of P1 level data in the original scene). If R<0.3, the encryption strength is reduced or the desensitization rule is relaxed to improve the data availability (such as reducing the masking field of P3 level data in S1 scene).
[0136] The data classification component first receives raw data continuously collected from various sensors and vehicle-mounted systems, and performs preliminary classification according to the preset data type classification standard. Then, the scene recognition component analyzes the environment and data usage of the current vehicle in real time, identifies the scene features of the "usage-subject-security level" three-tuple, and integrates the scene features output by the scene recognition component to dynamically generate a desensitization strategy suitable for the current scene. Then, the data flow is desensitized according to the strategy to reduce the risk of sensitive information exposure. Then, the access control component assigns access rights to the desensitized data. At the same time, the dynamic encryption component adjusts the encryption algorithm and key update frequency in real time based on the sensitivity level provided by the data classification component and the scene security level given by the scene recognition component.
[0137] In addition, the risk monitoring component continuously operates throughout the entire data processing process, and monitors risk indicators such as abnormal access, insufficient desensitization strength, and encryption anomalies in real time. The policy improvement component dynamically responds and updates. When the risk monitoring component detects a privacy risk, the policy improvement component dynamically adjusts the desensitization strategy and access control rules according to the risk assessment results, such as temporarily increasing the encryption strength, tightening the access rights, or performing more stringent subject authentication.
[0138] It should be noted that the user information (including but not limited to user equipment information, user personal information, etc.) and data (including but not limited to data for analysis, stored data, displayed data, etc.) involved in the present disclosure are all information and data authorized by the user or authorized by all parties, and the collection, use and processing of related data need to comply with relevant laws, regulations and standards of relevant countries and regions, and provide corresponding operation portal for user to choose authorization or refusal.
[0139] According to the embodiment of the present disclosure, a device embodiment of processing of vehicle data is provided. It should be noted that the device can be configured to execute the method of processing of vehicle data. FIG. 4 is a schematic diagram of a vehicle data processing device according to an embodiment of the present disclosure. As shown in FIG. 4, the device 400 includes an acquisition component 402, a first determination component 404, a desensitization component 406, and a second determination component 408.
[0140] Optionally, the obtaining component 402 is configured to, in response to receiving a data access instruction of a client for a vehicle, obtain vehicle data corresponding to the data access instruction and a data application scenario corresponding to the vehicle data; the first determining component 404 is configured to determine a target sensitivity level corresponding to the vehicle data from a plurality of sensitivity levels, wherein different sensitivity levels are used to quantify different severity levels of vehicle data leakage; the desensitization component 406 is configured to perform desensitization processing on the vehicle data based on the target sensitivity level and the data application scenario to obtain desensitized vehicle data; and the second determining component 408 is configured to determine authorized access data in the desensitized vehicle data based on a scene security level of the data application scenario and an access permission level of the client, and send the authorized access data to the client, wherein the authorized access data is data in the desensitized vehicle data that is allowed to be accessed by the client.
[0141] Optionally, the first determining component is further configured to determine a target data category corresponding to the vehicle data from a plurality of data categories, and determine a data refinement degree of the vehicle data, wherein the data refinement degree is used to represent the collection accuracy of the vehicle data; and determine the target sensitivity level from a plurality of sensitivity levels based on the data refinement degree and the target data category of the vehicle data.
[0142] Optionally, the desensitization component is further configured to determine a desensitization strength based on the target sensitivity level, determine a desensitization object in the vehicle data based on the data application scenario, wherein the desensitization object is used to represent an object to be desensitized, and perform desensitization processing on the desensitization object in the vehicle data based on the desensitization strength to obtain the desensitized vehicle data.
[0143] Optionally, the desensitization component is further configured to determine a target desensitization operation type corresponding to the target data category from a plurality of desensitization operation types, wherein different desensitization operation types correspond to different data categories; and perform desensitization processing on the desensitization object in the vehicle data based the target desensitization operation type and the desensitization strength to obtain the desensitized vehicle data.
[0144] Optionally, the second determining component is further configured to determine an authorized access data type of the client based on the scene security level of the data application scenario and the access permission level of the client; and determine authorized access data corresponding to the authorized access data type from the desensitized vehicle data.
[0145] Optionally, the second determining component is further configured to encrypt the authorized access data based on the target sensitivity level and the scene security level to obtain encrypted vehicle data; and transmit the encrypted vehicle data to the client.
[0146] Optionally, the apparatus is further configured to obtain an abnormal access times of the client to the vehicle data, a desensitization reverse times of the vehicle data, and an encryption abnormal times of the vehicle data, wherein the desensitization reverse times represent a number of times of successfully reversing the desensitized vehicle data, and the encryption abnormal times represent a number of times of abnormally encrypting the vehicle data; perform risk assessment on the vehicle data based on the abnormal access times, the desensitization reverse times, and the encryption abnormal times to obtain a risk value of the vehicle data; and adjust the desensitization intensity corresponding to the access authority level and the target sensitive level based on the risk value, the abnormal access times, and the desensitization reverse times.
[0147] Optionally, the apparatus is further configured to reduce the access authority level of the client if the risk value is greater than a first preset threshold value and the abnormal access times are greater than a first preset number of times; enhance the desensitization intensity if the risk value is greater than the first preset threshold value and the desensitization reverse times are greater than a second preset number of times; and increase the access authority level and / or weaken the desensitization intensity if the risk value is less than a second preset threshold value, wherein the second preset threshold value is less than the first preset threshold value.
[0148] Embodiments of the present disclosure further provide a vehicle, comprising a memory storing an executable program; and a processor configured to run the program, wherein the program performs the method in the embodiments of the present disclosure when running.
[0149] Embodiments of the present disclosure further provide a computer readable storage medium comprising a stored executable program, wherein the computer readable storage medium controls a device where the computer readable storage medium is located to perform the method in the embodiments of the present disclosure when the executable program runs.
[0150] Embodiments of the present disclosure further provide a computer program product comprising a computer program, wherein the computer program implements the method in the embodiments of the present disclosure when executed by a processor.
[0151] Embodiments of the present disclosure further provide a computer program product comprising a non-volatile computer readable storage medium configured to store a computer program, wherein the computer program implements the method in the embodiments of the present disclosure when being executed by a processor.
[0152] Embodiments of the present disclosure further provide a computer program, wherein the computer program implements the method in the embodiments of the present disclosure when the computer program is executed by a processor.
[0153] In the above embodiments of the present disclosure, the description of each embodiment has its own focus, and the parts not described in detail in a certain embodiment can be referred to the relevant description of other embodiments.
[0154] In several embodiments provided by the present disclosure, it should be understood that the disclosed technology can be implemented in other manners. For example, the described unit embodiments can be divided into other ways, for example, the units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the displayed or discussed mutual couplings or direct couplings or communication connections can be implemented by using some interfaces, and the indirect couplings or the communication connections can be implemented in electric or other forms.
[0155] The units described as separate components can or can not be physically separate, and the components shown as units can or can not be physical units, that is, can be located in one place, or can be distributed on multiple units. Some or all of the units can be selected according to actual needs to achieve the purpose of the embodiments.
[0156] In addition, each functional unit in the various embodiments of the present disclosure can be integrated in one processing unit, or each unit can exist physically, or two or more units can be integrated in one unit. The integrated unit can be implemented in the form of hardware or in the form of a software functional unit.
[0157] When the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer readable storage medium. Based on this understanding, the technical solutions of the present disclosure essentially or the part that makes a contribution to the related art or the whole or part of the technical solutions can be embodied in the form of a software product. The computer software product is stored in a storage medium, and includes several instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present disclosure. The foregoing storage medium includes: a U disk, a read-only memory (ROM, Read-Only Memory), a random access memory (RAM, Random Access Memory), a mobile hard disk, a magnetic disk or an optical disk, and various media that can store program codes.
[0158] The above descriptions are only preferred embodiments of the present disclosure, and it should be pointed out that, for those skilled in the art, without departing from the principles of the present disclosure, some improvements and refinements can be made, and these improvements and refinements should be regarded as the protection scope of the present disclosure.
Claims
1. A method for processing vehicle data, comprising: In response to receiving a data access instruction from a client for a vehicle, the system obtains the vehicle data corresponding to the data access instruction and the data application scenario corresponding to the vehicle data. The target sensitivity level corresponding to the vehicle data is determined from multiple sensitivity levels, wherein different sensitivity levels are used to quantify different severity levels of vehicle data leakage; Based on the target sensitivity level and the data application scenario, the vehicle data is de-identified to obtain de-identified vehicle data; Based on the scenario security level of the data application scenario and the access permission level of the client, the authorized access data in the de-identified vehicle data is determined, and the authorized access data is sent to the client. The authorized access data is a subset of the data in the de-identified vehicle data that the client is allowed to access.
2. The method of claim 1, wherein, Determining the target sensitivity level corresponding to the vehicle data from multiple sensitivity levels includes: The target data category corresponding to the vehicle data is determined from multiple data categories, and the data refinement level of the vehicle data is determined, wherein the data refinement level is used to represent the collection accuracy of the vehicle data; Based on the level of data refinement and the target data category, the target sensitivity level is determined from the plurality of sensitivity levels.
3. The method of claim 2, wherein, Determining the level of detail in the vehicle data includes: The level of data refinement is determined based on the target data category and functional requirements.
4. The method of claim 2, wherein, The method further includes: Based on the characteristics of the data application scenario, the data sensitivity requirements of the data application scenario, the scenario security level, and the client attributes, the target sensitivity level is adjusted.
5. The method of claim 1, wherein, Determining the target sensitivity level corresponding to the vehicle data from multiple sensitivity levels includes: Determine the target data category corresponding to the vehicle data from multiple data categories; The sensitivity level of the target is determined based on the target data category and the data application scenario.
6. The method of claim 1, wherein, Based on the target sensitivity level and the data application scenario, the vehicle data is de-identified to obtain de-identified vehicle data, including: Based on the target sensitivity level, determine the desensitization intensity; Based on the data application scenario, the de-identified objects in the vehicle data are determined, wherein the de-identified objects are used to represent objects to be de-identified; Based on the desensitization intensity, the desensitized objects in the vehicle data are desensitized to obtain the desensitized vehicle data.
7. The method of claim 6, wherein, Based on the stated desensitization strength, the desensitized objects in the vehicle data are desensitized to obtain the desensitized vehicle data, including: Determine the target de-identification operation type corresponding to the target data category from multiple de-identification operation types, where different de-identification operation types correspond to different data categories; Based on the target desensitization operation type and the desensitization intensity, the desensitized objects in the vehicle data are desensitized to obtain the desensitized vehicle data.
8. The method of claim 6, wherein, Based on the target sensitivity level, the desensitization intensity is determined, including: The desensitization intensity is determined based on the target sensitivity level and the security requirements of the data application scenario.
9. The method of claim 1, wherein, Based on the scenario security level of the data application scenario and the access permission level of the client, the authorized access data in the de-identified vehicle data is determined, including: Based on the scenario security level of the data application scenario and the access permission level of the client, the authorized access data type of the client is determined; From the de-identified vehicle data, determine the data corresponding to the authorized access data type to obtain the authorized access data.
10. The method of claim 9, wherein, Based on the scenario security level of the data application scenario and the access permission level of the client, the authorized access data types of the client are determined, including: Based on the scenario security level, the access permission level, and the target sensitivity level, an access control list is generated; Based on the access control list, the authorized access data type is determined from the anonymized vehicle data.
11. The method of claim 9, wherein, Sending the authorized access data to the client includes: Based on the target sensitivity level and the scenario security level, the authorized access data is encrypted to obtain encrypted vehicle data; The encrypted vehicle data is transmitted to the client.
12. The method of claim 11, wherein, Based on the target sensitivity level and the scenario security level, the authorized access data is encrypted to obtain encrypted vehicle data, including: Based on the target sensitivity level and the scenario security level, determine the target encryption algorithm and key update frequency; Based on the target encryption algorithm and the key update frequency, the authorized access data is encrypted to obtain the encrypted vehicle data.
13. The method of claim 11, wherein, Transmitting the encrypted vehicle data to the client includes: The encrypted vehicle data is transmitted to the client via a secure communication channel.
14. The method of claim 1, wherein, Based on the scenario security level of the data application scenario and the access permission level of the client, the authorized access data in the de-identified vehicle data is determined, including: Analyze the characteristics of the data application scenario and the client's access adjustments to generate an authorized access data set; The access permissions of the client are verified to determine the authorized access data types and sensitivity level ranges of the client; The authorized access data type and the sensitivity level range are compared with the authorized access data set to determine the authorized access data.
15. The method of any one of claims 1-14, wherein, The method further includes: The number of abnormal accesses to the vehicle data by the client, the number of times the vehicle data was de-identified and reversed, and the number of times the vehicle data was encrypted abnormally are obtained. The number of times the de-identification and reversed is used to indicate the number of times the de-identified vehicle data was successfully reversed, and the number of times the encryption was encrypted abnormally is used to indicate the number of times the vehicle data was encrypted abnormally. Based on the number of abnormal accesses, the number of times the data was de-identified and reversed, and the number of times the encryption was abnormal, a risk assessment was performed on the vehicle data to obtain the risk value of the vehicle data. Based on the risk value, the number of abnormal accesses, and the number of desensitization reverse calculations, the desensitization intensity corresponding to the access permission level and the target sensitivity level is adjusted.
16. The method of claim 15, wherein, Adjusting the desensitization intensity corresponding to the access permission level and the target sensitivity level based on the risk value includes: if the risk value is greater than a first preset threshold value and the number of abnormal access times is greater than a first preset number, the access permission level of the client is reduced; if the risk value is greater than the first preset threshold value and the number of desensitization reverse times is greater than a second preset number, the desensitization strength is increased; if the risk value is less than a second preset threshold value, the access permission level is increased and / or the desensitization strength is decreased, wherein the second preset threshold value is less than the first preset threshold value.
17. The method of any one of claims 1-14, wherein, obtaining a data application scenario corresponding to the vehicle data, including: analyzing the data access instruction to determine a use intention and a scene feature; determining the data application scenario based on the use intention and the scene feature.
18. The method of claim 17, wherein, The data application scenario includes: data use, access subject, scene security level.
19. A vehicle, comprising: a memory storing an executable program; a processor configured to run the program, wherein the program performs the method of any one of claims 1 to 18 when running.
20. A computer readable storage medium comprising a stored executable program, wherein, controlling the device where the storage medium is located to perform the method of any one of claims 1 to 18 when the executable program is running.
