Vehicle data processing method and device, storage medium and equipment

Abstract

The invention provides a vehicle data processing method and device, a storage medium and equipment, and the method comprises the steps: obtaining vehicle data through a target API interface before an appointed application of vehicle-end equipment transmits or stores the vehicle data, carrying out the preprocessing of the vehicle data, scanning the preprocessed vehicle data through a Yara rule engine, and carrying out the scanning of the preprocessed vehicle data through a Yara rule engine; according to the method, sensitive information in vehicle data is comprehensively and accurately detected by means of various sensitive information rules which are built in a Yara rule engine and aim at vehicle data safety, then the detected sensitive information is subjected to desensitization processing, and then the desensitized data are output. Therefore, the sensitive data scanning engine is developed based on the Yara framework, and the sensitive data, related to personal privacy, of the vehicle can be scanned in multiple dimensions by utilizing the flexibility of the Yara rule, so that the sensitive data is effectively prevented from being leaked easily, and the vehicle data security is protected.

Description

Technical Field

[0001] The present application relates to the field of data security technology, and more specifically, to a vehicle data processing method, apparatus, storage medium, and device. Background Art

[0002] With the rapid advancement of automotive technology, vehicles are becoming mobile data centers, collecting and processing vast amounts of data, including location information, driving behavior, passenger preferences, and vehicle performance parameters. This data is not only crucial for vehicle operation but also provides drivers with a convenient and personalized driving experience. This data, however, presents challenges in data security and privacy protection. To address these challenges, the development of vehicle data security technologies is crucial. These technologies include, but are not limited to, data encryption, access control, intrusion detection systems, and security protocols. These technologies ensure the security of data during collection, storage, transmission, and processing, preventing data leakage and misuse.

[0003] However, current vehicle data security technologies mainly provide strong security guarantees for data transmission and cloud storage, but often pay insufficient attention to data protection on vehicle-side devices. This can easily lead to the leakage of sensitive information stored in vehicle-side devices, such as personal privacy data, vehicle safety parameters, diagnostic information, and trade secrets, thereby causing serious impacts on personal privacy and corporate interests. Summary of the Invention

[0004] The purpose of this application is to provide a vehicle data processing method, apparatus, storage medium and equipment, aiming to solve the problem that vehicle data security technology in related technologies is insufficient in data protection on vehicle-side devices, which easily leads to the leakage of sensitive information stored in vehicle-side devices, thereby causing serious impact on personal privacy and corporate interests.

[0005] In the first aspect, the present application provides a vehicle data processing method, including: before the designated application of the vehicle-side device sends or stores the vehicle data, obtaining the vehicle data through the target API interface and preprocessing the vehicle data; scanning the preprocessed vehicle data through the Yara rule engine to identify sensitive information in the vehicle data; the Yara rule engine is provided with a variety of sensitive information rules for vehicle data security; the identified sensitive information is desensitized, and then the desensitized data is output.

[0006] In the above implementation process, before the designated application on the vehicle-side device sends or stores vehicle data, it obtains the vehicle data through the target API interface and pre-processes the vehicle data. The pre-processed vehicle data is then scanned using the Yara rule engine. With the help of the various sensitive information rules built into the Yara rule engine for vehicle data security, the sensitive information in the vehicle data is comprehensively and accurately detected. The detected sensitive information is then desensitized and output. In this way, a sensitive data scanning engine is developed based on the Yara framework, leveraging the flexibility of Yara rules to support multi-dimensional scanning of sensitive vehicle and personal privacy data, effectively ensuring that sensitive data will not be easily leaked and protecting vehicle data security.

[0007] Furthermore, in some embodiments, the method is applied to an SDK; the SDK is integrated into the vehicle-side device; the SDK has the Yara rule engine built in; and the target API interface is provided by the SDK to an external program.

[0008] In the above implementation process, the vehicle data processing method is encapsulated into an SDK for easy integration into vehicle-side equipment.

[0009] Furthermore, in some embodiments, obtaining the vehicle data through the target API interface includes: if the designated application passes the data cache through the target API interface, reading the vehicle data from the data cache; if the designated application passes the specified file path through the target API interface, locating and reading the file under the specified file path from the disk of the vehicle-end device, and obtaining the vehicle data from the read file.

[0010] In the above implementation process, the target API interface supports the caller to pass in data cache, and also supports the caller to pass in a specified file path as the data source, so that external programs can call and operate data in an efficient and flexible manner.

[0011] Furthermore, in some embodiments, the preprocessing of the vehicle data includes: when the vehicle data is in file format, analyzing the file type of the vehicle data; if the analysis result indicates that the vehicle data is an image file, using optical character recognition technology to convert the text information contained in the image file into editable text data; if the analysis result indicates that the vehicle data is a text or binary file, directly reading the data content in the vehicle data.

[0012] In the above implementation process, a pre-processing method for vehicle data input in the form of files is provided. Through file type analysis and application of OCR technology, standardized processing of input data is achieved, laying a good foundation for subsequent sensitive information scanning and desensitization processing.

[0013] Furthermore, in some embodiments, the file type of the vehicle data is analyzed using the Magic module of the Yara rule engine.

[0014] In the above implementation process, we rely on Yara's own Magic module to analyze the file type of vehicle data, thereby ensuring the correct identification and adaptation of different file types.

[0015] Furthermore, in some embodiments, the desensitizing processing of the identified sensitive information includes: desensitizing the sensitive information by adopting a corresponding desensitizing method according to the type of the identified sensitive information; the desensitizing method includes deletion, formatting and hash replacement.

[0016] In the above implementation process, for different types of sensitive information, corresponding desensitization methods are used to desensitize sensitive information, thereby improving data security while maintaining data availability.

[0017] Furthermore, in some embodiments, the outputting of the desensitized data includes: if the vehicle data is passed into the designated application through cache, returning the desensitized data to the designated application; if the vehicle data is passed into the designated application through a file path, re-outputting the desensitized data into the file to overwrite the original file content.

[0018] In the above implementation, if the caller passes in cached data, the desensitized cached data is output. If the caller passes in a file path, the desensitized data is re-output to the file, overwriting the original content. This ensures that sensitive data is securely processed before being transmitted or stored in the local file system.

[0019] In the second aspect, the present application provides a vehicle data processing device, including: an acquisition module, which is used to obtain the vehicle data through a target API interface and pre-process the vehicle data before the designated application of the vehicle-side device sends or stores the vehicle data; an identification module, which is used to scan the pre-processed vehicle data through the Yara rule engine to identify sensitive information in the vehicle data; the Yara rule engine is equipped with a variety of sensitive information rules for vehicle data security; a processing module, which is used to desensitize the identified sensitive information and then output the desensitized data.

[0020] In a third aspect, the present application provides an electronic device comprising: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the steps of the method described in any one of the first aspects when executing the computer program.

[0021] In a fourth aspect, the present application provides a computer-readable storage medium having instructions stored thereon. When the instructions are executed on a computer, the computer is caused to execute the method as described in any one of the first aspects.

[0022] In a fifth aspect, the present application provides a computer program product, which, when running on a computer, enables the computer to execute the method as described in any one of the first aspects.

[0023] Other features and advantages disclosed in the present application will be described in the following description, or some features and advantages can be inferred or determined without doubt from the description, or can be learned by implementing the above-mentioned technology disclosed in the present application.

[0024] In order to make the above-mentioned objects, features and advantages of the present application more obvious and easy to understand, preferred embodiments are given below and described in detail with reference to the accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0025] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the following is a brief introduction to the drawings required for use in the embodiments of the present application. It should be understood that the following drawings only show certain embodiments of the present application and therefore should not be regarded as limiting the scope. For ordinary technicians in this field, other relevant drawings can be obtained based on these drawings without creative work.

[0026] Figure 1 A flowchart of a vehicle data processing method provided in an embodiment of the present application;

[0027] Figure 2 A schematic diagram of the logical architecture of the SDK provided in a Yara-based vehicle data security protection solution provided in an embodiment of the present application;

[0028] Figure 3 A block diagram of a vehicle data processing device provided in an embodiment of the present application;

[0029] Figure 4 This is a structural block diagram of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0030] The technical solutions in the embodiments of the present application will be described below in conjunction with the drawings in the embodiments of the present application.

[0031] It should be noted that similar reference numerals and letters represent similar items in the following drawings. Therefore, once an item is defined in one drawing, it does not need to be further defined or explained in subsequent drawings. At the same time, in the description of this application, the terms "first", "second", etc. are only used to distinguish the description and should not be understood as indicating or implying relative importance.

[0032] As described in the background, prior art vehicle data security technologies often lack sufficient protection for data stored on vehicle-side devices, which can easily lead to the leakage of sensitive information stored on vehicle-side devices, thus seriously impacting personal privacy and corporate interests. Based on this, the present invention provides a vehicle data processing solution to address this issue.

[0033] Next, the implementation process of the embodiment of this application is introduced:

[0034] like Figure 1 As shown, Figure 1 This is a flowchart of a vehicle data processing method provided in an embodiment of the present application. The method can be implemented as an SDK (Software Development Kit). The SDK is integrated on the vehicle-side device and requires the vehicle-side application involved in the flow of sensitive data, that is, the specified application calls the SDK before sending or storing vehicle-side data. In this embodiment, the SDK has a built-in Yara rule engine. The Yara rule engine here is a sensitive data scanning engine developed based on the Yara framework. Yara is an open source program based on string scanning and matching, mostly used for identifying and analyzing malware and security scanning. Its main principle is to match the content in the file by defining rules, thereby detecting target feature data. In addition, users can independently develop customized modules to meet their specific detection needs. These modules can be seamlessly integrated into the Yara rule engine to provide users with more personalized and efficient threat detection solutions.

[0035] The method comprises:

[0036] Step 101: Before a designated application of a vehicle-side device sends or stores vehicle data, the vehicle data is obtained through a target API interface and pre-processed.

[0037] The target API (Application Programming Interface) mentioned in this step can be provided to external programs by the SDK mentioned above. Before the designated application sends or stores vehicle data, the designated application transmits the vehicle data through the target API interface, allowing the SDK to scan and desensitize the vehicle data. The vehicle data here can be data that the designated application requests to read from the vehicle-side device's disk and prepares to send to other applications, or data that the designated application intends to write to the vehicle-side device's disk.

[0038] In some embodiments, obtaining the vehicle data through the target API interface mentioned in this step may include: if the designated application passes the data cache through the target API interface, reading the vehicle data from the data cache; if the designated application passes the specified file path through the target API interface, locating and reading the file under the specified file path from the disk of the vehicle-end device, and obtaining the vehicle data from the read file.

[0039] In other words, the target API interface supports two ways to pass vehicle data: data cache and file path. Specifically, the caller passes the data cache through the target API interface. The data cache contains the data that needs to be desensitized. At this time, the SDK reads the vehicle data directly from the data cache, thereby reducing disk I / O operations and improving processing speed. The caller passes the specified file path as the data source through the target API interface. In this case, the SDK locates and reads the file under the specified file path from the disk, obtains its data content, and then performs subsequent scanning and desensitization processing. In this way, external programs can call and operate data in an efficient and flexible manner.

[0040] After acquiring the vehicle data, the SDK pre-processes it to ensure smooth and accurate subsequent processing. In some embodiments, the pre-processing of the vehicle data mentioned in this step may include: when the vehicle data is in file format, analyzing the file type of the vehicle data; if the analysis result indicates that the vehicle data is an image file, using optical character recognition technology to convert the text information contained in the image file into editable text data; if the analysis result indicates that the vehicle data is a text or binary file, directly reading the data content in the vehicle data. That is, for vehicle data passed in as files, the SDK analyzes the file type. For image files, the SDK applies optical character recognition (OCR) technology to accurately convert the text contained in the image into editable text data. OCR technology uses optical and computer technology to read text printed or written on paper and convert it into a format that is acceptable to computers and understandable to humans. During implementation, OCR technology can be used to integrate the image recognition and file conversion function into the Yara rule engine as a module. For text or binary files, the SDK directly reads the file content, providing raw material for subsequent data analysis and processing. This achieves standardized processing of input data, laying a good foundation for subsequent sensitive information scanning and desensitization. In addition, for vehicle data passed in as a data cache, the SDK can instantly recognize it and directly pass the data to the Yara rule engine for scanning, saving processing time and resources.

[0041] Furthermore, in some embodiments, the aforementioned vehicle data file type can be analyzed using the Yara rule engine's Magic module. The Magic module is a Yara-specific module that allows users to include the file type to be detected as a condition in a rule. Therefore, relying on Yara's built-in Magic module to analyze vehicle data file types ensures accurate recognition and adaptation of different file types.

[0042] In step 102, the pre-processed vehicle data is scanned using the Yara rule engine to identify sensitive information in the vehicle data; the Yara rule engine is configured with a variety of sensitive information rules for vehicle data security;

[0043] This step refers to: using the powerful pattern matching capabilities of the Yara rule engine to quickly scan vehicle data to identify sensitive information that may be present. The Yara rule engine has built-in multiple sensitive information rules for vehicle data security. The sensitive information rules here can be Yara rules corresponding to sensitive information, which can cover multiple categories such as vehicle information, personal information, biometric data, and environmental perception data. The vehicle information here can include the vehicle identification number (VIN), part model, vehicle model, etc. Personal information can include the driver's name, age, gender, etc. Biometric data can include the driver's fingerprint, voiceprint, facial recognition information, etc. Environmental perception data can include the vehicle's location information, driving speed, acceleration, etc.

[0044] Yara rules mainly include the strings to be matched and the conditions. When scanning vehicle data, the Yara rule engine can use the corresponding regular expressions based on each Yara rule to match, thereby performing comprehensive and accurate detection of sensitive information.

[0045] In step 103, the identified sensitive information is desensitized, and the desensitized data is output.

[0046] This step means: when sensitive information is detected in the vehicle data, the SDK will locate the location of the sensitive information in the file or data cache, then desensitize the sensitive information, and then output the desensitized data, thereby ensuring that the sensitive information in the vehicle data will not be easily leaked and protecting the security of the vehicle data.

[0047] In some embodiments, desensitizing the identified sensitive information mentioned in this step may include: desensitizing the sensitive information using a corresponding desensitization method based on the type of sensitive information identified; these desensitization methods include deletion, formatting, and hash replacement. Specifically, the SDK supports desensitization methods including deletion, formatting, and hash replacement. Deletion refers to directly deleting the sensitive information from the data cache or file; formatting refers to replacing the sensitive information with content in a specific format; and hash replacement refers to calculating the MD5 value of the sensitive information and replacing the original data. For different sensitive information types, users can configure desensitization methods through configuration rules, and the SDK will then desensitize the sensitive information using the corresponding desensitization method. For example, for sensitive time information, formatting can be used to replace it with "DataTime." For sensitive information such as a vehicle VIN, formatting can be used to replace it with 17 characters "x." For sensitive information whose original data is known, hash replacement can be used to replace it with the MD5 value of the original data. This improves data security while maintaining data availability.

[0048] In addition, in some embodiments, the output of the desensitized data mentioned in this step may include: if the vehicle data is passed in by the designated application in the form of a cache, returning the desensitized data to the designated application; if the vehicle data is passed in by the designated application in the form of a file path, re-outputting the desensitized data to the file to overwrite the original file content. That is to say, if the data passed in by the caller is in the form of a cache, the SDK outputs the desensitized cached data; if the data passed in by the caller is in the form of a file path, the SDK re-outputs the desensitized data to the file to overwrite the original content. In this way, it is ensured that sensitive data has been securely processed before the data is transmitted or stored in the local file system.

[0049] In an embodiment of the present application, before a designated application on a vehicle-side device sends or stores vehicle data, the vehicle data is obtained through a target API interface and pre-processed. The pre-processed vehicle data is then scanned using the Yara rule engine. With the help of the various sensitive information rules built into the Yara rule engine for vehicle data security, the sensitive information in the vehicle data is comprehensively and accurately detected. The detected sensitive information is then desensitized and the desensitized data is output. In this way, a sensitive data scanning engine is developed based on the Yara framework, and the flexibility of Yara rules is utilized to support multi-dimensional scanning of sensitive data related to vehicle and personal privacy, thereby effectively ensuring that sensitive data will not be easily leaked and protecting vehicle data security.

[0050] In order to explain the solution of this application in more detail, a specific embodiment is introduced below:

[0051] This embodiment provides a vehicle data security protection solution based on Yara. This solution is developed based on the Yara rule engine and is specifically designed for vehicle data security protection. It is packaged into an SDK for easy integration into vehicle-side devices. This SDK not only includes the core Yara rule engine, but also expands the user-configurable sensitive information rule library and is equipped with an additional data processing module. Through these configuration rules and plug-ins, the Yara rule engine can effectively identify sensitive information in the data. Once such information is found, the system will automatically perform desensitization processing to ensure that sensitive data has been securely processed before it is transmitted or stored in the local file system.

[0052] When implementing this solution, applications on the vehicle side that involve sensitive data flow must call the SDK to perform security scanning and desensitization on the data before sending or storing it, and then continue to perform subsequent operations. The logical architecture of the SDK is as follows: Figure 2 As shown, it includes a data receiving module 21, a data pre-processing module 22, a sensitive information scanning module 23, a data desensitization module 24 and a data output module 25. Among them:

[0053] The data receiving module 21 provides a set of API interfaces that allow external programs to call and operate data in an efficient and flexible manner. The API interface supports the caller to pass in a data cache containing the data that needs to be desensitized. In this case, the data receiving module 21 will read the data directly from the provided cache. The API interface also supports the caller to pass in a specified file path as the data source. In this case, the data receiving module 21 will be responsible for locating and reading the file under the specified file path from the disk and obtaining its data content.

[0054] The data preprocessing module 22 is responsible for standardizing and preparing the input data to ensure the smoothness and accuracy of the subsequent processing flow. For data input in the form of data cache, the data preprocessing module 22 can immediately identify and skip unnecessary processing steps, and directly pass the data to the sensitive information scanning module 23, thereby saving processing time and resources; when the data input is in the form of a file, the data preprocessing module 22 relies on Yara's own Magic module to analyze the file, which can support a variety of file formats including pictures, text and binary data. This wide range of format support capabilities effectively improves the versatility and practicality of the module; for image files, the data preprocessing module 22 uses OCR technology to accurately convert the text information contained in the image into editable text data. The application of this technology effectively expands the module's ability to process non-text data; for text or binary files, the data preprocessing module 22 will directly read the file content to provide raw materials for subsequent data analysis and processing; in addition, the data preprocessing module 22 also supports parsing the CAN message data content based on the DBC file (a commonly used CAN bus data definition file) and extracting key signal information;

[0055] The sensitive information scanning module 23 is responsible for identifying sensitive vehicle information. It relies primarily on the Yara rule engine, which performs comprehensive and accurate detection of sensitive data based on customized detection rules. The Yara rule engine has built-in multiple sensitive information rules for vehicle data security. Yara rules mainly contain strings to be matched and conditions. For example, the Yara rule engine has a Yara rule for sensitive information such as vehicle VIN. The Yara rule uses the regular expression "[A-HJ-NPR-Z0-9]{17}" to write and match the vehicle VIN. In addition, Yara rules also support string format, hexadecimal format, and a variety of wildcards.

[0056] The data desensitization module 24 is primarily responsible for desensitizing sensitive information, and supports desensitization methods including deletion, formatting, and hash replacement. When the sensitive information scanning module 23 detects that the data content contains sensitive information, it will output the type, location, and length of the sensitive information to the data desensitization module 24. The data desensitization module 24 uses this information to locate the location of the sensitive information in the file or data cache. For different sensitive information types, users can set the desensitization method by configuring rules.

[0057] The data output module 25 is mainly responsible for outputting the scanned anonymized data. If the incoming data is in cache form, the data output module 25 outputs a segment of anonymized cache data. If the incoming data is a file path, the data output module 25 re-outputs the anonymized content into the file to overwrite the original content.

[0058] This embodiment can be integrated into vehicle systems or onboard T-BOX devices, which typically contain large amounts of sensitive information. Applications involving this sensitive data filter and desensitize the data using the API provided by this embodiment before sending it externally or storing it on disk, thereby preventing the easy leakage of sensitive data and protecting vehicle data security. This embodiment uses Yara as the sensitive information scanning engine, improving the speed and stability of information scanning. Through a rich set of sensitive information rules, it can determine whether data content contains sensitive information from multiple dimensions, thereby providing a more efficient threat detection solution.

[0059] Corresponding to the embodiments of the aforementioned method, the present application also provides embodiments of a vehicle data processing device and a terminal used therein:

[0060] like Figure 3 As shown, Figure 3 is a block diagram of a vehicle data processing device provided in an embodiment of the present application, the device comprising:

[0061] An acquisition module 31 is configured to acquire the vehicle data through a target API interface and pre-process the vehicle data before the designated application of the vehicle-side device sends or stores the vehicle data;

[0062] An identification module 32 is configured to scan the pre-processed vehicle data using a Yara rule engine to identify sensitive information in the vehicle data; the Yara rule engine is configured with a variety of sensitive information rules for vehicle data security;

[0063] The processing module 33 is used to desensitize the identified sensitive information and then output the desensitized data.

[0064] The implementation process of the functions and effects of each module in the above-mentioned device is specifically described in the implementation process of the corresponding steps in the above-mentioned method, and will not be repeated here.

[0065] This application also provides an electronic device, see Figure 4 , Figure 4This is a block diagram of the structure of an electronic device provided in an embodiment of the present application. The electronic device may include a processor 410, a communication interface 420, a memory 430, and at least one communication bus 440. The communication bus 440 is used to enable direct communication between these components. The communication interface 420 of the electronic device in this embodiment of the present application is used to communicate signaling or data with other node devices. The processor 410 may be an integrated circuit chip with signal processing capabilities.

[0066] The processor 410 may be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; it may also be a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component. The various methods, steps, and logic block diagrams disclosed in the embodiments of the present application may be implemented or executed. The processor 410 may be a microprocessor, or the processor 410 may be any conventional processor.

[0067] The memory 430 may be, but is not limited to, a random access memory (RAM), a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), etc. The memory 430 stores computer-readable instructions. When the computer-readable instructions are executed by the processor 410, the electronic device can perform the above-mentioned operations. Figure 1 The various steps involved in the method embodiment.

[0068] Optionally, the electronic device may further include a storage controller and an input / output unit.

[0069] The memory 430, storage controller, processor 410, peripheral interface, and input / output units are electrically connected to each other directly or indirectly to enable data transmission or interaction. For example, these components can be electrically connected to each other via one or more communication buses 440. The processor 410 is used to execute executable modules stored in the memory 430, such as software function modules or computer programs included in the electronic device.

[0070] The input and output unit is used to provide users with the ability to create tasks and to create optional time periods or preset execution times for the tasks to enable interaction between the user and the server. The input and output unit can be, but is not limited to, a mouse and a keyboard.

[0071] I understand. Figure 4 The structure shown is only for illustration, and the electronic device may also include Figure 4 More or fewer components than shown, or with Figure 4 Different configurations shown. Figure 4 Each component shown in the figure can be implemented by hardware, software or a combination thereof.

[0072] An embodiment of the present application further provides a storage medium having instructions stored thereon. When the instructions are run on a computer, the computer program is executed by a processor to implement the method described in the method embodiment. To avoid repetition, details are not given here.

[0073] The present application also provides a computer program product, which, when running on a computer, enables the computer to execute the method described in the method embodiment.

[0074] In the several embodiments provided in this application, it should be understood that the disclosed devices and methods can also be implemented in other ways. The device embodiments described above are merely illustrative. For example, the flowcharts and block diagrams in the accompanying drawings show the possible architectures, functions and operations of the devices, methods and computer program products according to the multiple embodiments of the present application. In this regard, each box in the flowchart or block diagram can represent a module, a program segment or a part of the code, and the module, program segment or a part of the code contains one or more executable instructions for implementing the specified logical functions. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in an order different from that marked in the accompanying drawings. For example, two consecutive boxes can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram and / or flowchart, and the combination of boxes in the block diagram and / or flowchart, can be implemented using a dedicated hardware-based system that performs the specified function or action, or can be implemented using a combination of dedicated hardware and computer instructions.

[0075] In addition, the functional modules in each embodiment of the present application can be integrated together to form an independent part, or each module can exist independently, or two or more modules can be integrated to form an independent part.

[0076] If the functions are implemented in the form of software function modules and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art or the part of the technical solution, 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 enabling 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 method described in each embodiment of the present application. The aforementioned storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0077] The foregoing is merely an embodiment of the present application and is not intended to limit the scope of protection of the present application. Various modifications and variations are possible for those skilled in the art. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present application shall be included within the scope of protection of the present application. It should be noted that similar reference numerals and letters represent similar items in the following figures. Therefore, once an item is defined in one figure, it does not need to be further defined or explained in subsequent figures.

[0078] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in the present application should be included in the scope of protection of the present application. Therefore, the scope of protection of the present application should be based on the scope of protection of the claims.

[0079] It should be noted that, in this document, relational terms such as first and second, etc., are used only to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply the existence of any such actual relationship or order between these entities or operations. Moreover, the terms "comprises," "comprising," or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article, or device comprising a series of elements includes not only those elements, but also other elements not explicitly listed, or elements inherent to such process, method, article, or device. In the absence of further limitations, an element defined by the phrase "comprising a ..." does not exclude the presence of other identical elements in the process, method, article, or device comprising the element.

Claims

1. A vehicle data processing method, characterized in that: include: Before the designated application of the vehicle-side device sends or stores the vehicle data, the vehicle data is obtained through the target API interface and the vehicle data is pre-processed; Scanning the pre-processed vehicle data through the Yara rule engine to identify sensitive information in the vehicle data; The Yara rule engine is equipped with a variety of sensitive information rules for vehicle data security; The identified sensitive information is desensitized and then the desensitized data is output.

2. The method according to claim 1, characterized in that: The method is applied to SDK; the SDK is integrated in the vehicle-side device; the SDK has the Yara rule engine built in; and the target API interface is provided by the SDK to an external program.

3. The method according to claim 1, characterized in that The obtaining of the vehicle data through the target API interface includes: If the designated application delivers the data cache through the target API interface, reading the vehicle data from the data cache; If the designated application passes the designated file path through the target API interface, the file under the designated file path is located and read from the disk of the vehicle-side device, and the vehicle data is obtained from the read file.

4. The method according to claim 1, characterized in that: The preprocessing of the vehicle data comprises: When the vehicle data is in the form of a file, analyzing the file type of the vehicle data; If the analysis result indicates that the vehicle data is an image file, using optical character recognition technology to convert text information contained in the image file into editable text data; If the analysis result indicates that the vehicle data is a text or binary file, the data content in the vehicle data is directly read.

5. The method according to claim 4, characterized in that The file type of the vehicle data is obtained by analyzing the Magic module of the Yara rule engine.

6. The method according to claim 1, characterized in that The desensitizing process of the identified sensitive information includes: According to the type of sensitive information identified, a corresponding desensitizing method is adopted to desensitize the sensitive information; the desensitizing method includes deletion, formatting and hash replacement.

7. The method according to claim 3, characterized in that The output of the desensitized data includes: If the vehicle data is transmitted by the designated application in the form of cache, the desensitized data is returned to the designated application; If the vehicle data is passed in by the designated application in the form of a file path, the desensitized data is re-output into the file to overwrite the original file content.

8. A computer program product, characterized in that When the computer program product is executed on a computer, the computer is enabled to perform the method according to any one of claims 1 to 7.

9. A computer-readable storage medium, characterized in that: A computer program is stored thereon, and when the computer program is executed by a processor, the method according to any one of claims 1 to 7 is implemented.

10. An electronic device, characterized in that: The method comprises a processor, a memory, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the computer program, the method according to any one of claims 1 to 7 is implemented.

Images