Vehicle fault file distributed uploading method, device, equipment and medium

Abstract

The invention discloses a vehicle fault file distributed uploading method and device, equipment and a medium. The method comprises the following steps: receiving a fault signal of a target vehicle through a remote information processing control unit, and extracting a part fault code and fault occurrence time according to the fault signal; collecting working condition data within a specified time range of fault occurrence time and generating a fault file; the method comprises the following steps: dividing a fault file into a plurality of sub-files according to the size of the fault file and the transmission capability of an SIM card, naming each sub-file according to a subpackage sequence, carrying out compression processing on each sub-file by adopting a compression algorithm, and sequentially uploading each compressed file to an Internet of Vehicles platform according to a sequence of file serial numbers in file names from small to large. According to the embodiment of the invention, each sub-file is named, compressed and uploaded by adopting a file subpackage strategy, so that the problem of large file transmission is solved, and the transmission efficiency is optimized; and special characters are added in the last sub-file, so that the integrity and accuracy of the fault file are ensured.

Description

Technical Field

[0001] The present invention relates to the technical field of vehicle networking, and in particular to a method, device, equipment and medium for distributing vehicle fault file uploads. Background Art

[0002] In the Internet of Vehicles system, the telematics control unit (T-Box) undertakes the important task of collecting data from various vehicle components and transmits the working condition data to the Internet of Vehicles platform with the help of SIM cards. When a vehicle fails, the faulty component transmits data to the T-Box through the CAN line, and the T-Box then reports the fault code to the Internet of Vehicles platform.

[0003] In actual applications, the storage capacity of T-Box can generally only save the data of the last 7 days. If R&D personnel need to analyze a fault that occurred 7 days ago, the early data will be overwritten due to the rolling storage method of T-Box, resulting in the inability to extract the data, which seriously affects the in-depth analysis of historical faults. At the same time, if R&D personnel frequently perform data extraction operations on a certain vehicle, the Internet of Vehicles platform will frequently send instructions to T-Box, causing the instructions to be queued and processed in sequence. At this time, if there are other normal business interactions between the Internet of Vehicles platform and T-Box, such as locking the vehicle, unlocking, issuing parameters and other instructions, they will also be affected, reducing the overall operating efficiency of the Internet of Vehicles system. Summary of the invention

[0004] Based on this, the present invention provides a distributed uploading method, device, equipment and medium for vehicle fault files to solve the problems of limited storage capacity of a telematics control unit (T-Box), data acquisition lag and command processing conflict.

[0005] In a first aspect, an embodiment of the present invention provides a distributed uploading method for a vehicle fault file, which is executed by a distributed storage system, wherein the distributed storage system includes a telematics control unit configured with a user identity identification SIM card and a vehicle networking platform, and the method includes: continuously receiving a fault signal of a target vehicle through the telematics control unit, and extracting a component fault code and a fault occurrence time corresponding to the fault signal in the target vehicle according to the fault signal; collecting, through the telematics control unit, various operating condition data corresponding to the component fault code within a specified time range before and after the fault occurrence time, and generating a fault file according to the collected various operating condition data; The remote information processing control unit splits the fault file into multiple sub-files according to a preset sub-packaging order based on the file size of the fault file and the transmission capacity of the SIM card; the remote information processing control unit names each sub-file according to the sub-packaging order, and then compresses each sub-file using a set compression algorithm to obtain multiple compressed files, and uploads each compressed file to the Internet of Vehicles platform in sequence according to the file number in the file name from small to large; wherein each sub-file contains the number of the remote information processing control unit and the file number matching the sub-packaging order, and the sub-file of the last sub-packaging contains special characters.

[0006] In a second aspect, an embodiment of the present invention further provides a distributed upload device for vehicle fault files, which is arranged in a distributed storage system, wherein the distributed storage system includes a telematics control unit configured with a user identity identification SIM card and a vehicle networking platform, and the device includes: a fault signal receiving module, which is used to continuously receive the fault signal of the target vehicle through the telematics control unit, and extract the component fault code and the fault occurrence time corresponding to the fault signal in the target vehicle according to the fault signal; a fault file generating module, which is used to collect various operating condition data corresponding to the component fault code within a specified time range before and after the fault occurrence time through the telematics control unit, and generate a fault file according to the collected various operating condition data a file sub-packaging module, used to split the fault file into multiple sub-files according to a preset sub-packaging order through the telematics control unit according to the file size of the fault file and the transmission capacity of the SIM card; a sub-file uploading module, used to name each sub-file according to the sub-packaging order through the telematics control unit, compress each sub-file using a set compression algorithm to obtain multiple compressed files, and upload each compressed file to the Internet of Vehicles platform in sequence from small to large in the file number in the file name; wherein each sub-file contains the number of the telematics control unit and the file number matching the sub-packaging order, and the sub-file of the last sub-packaging contains special characters.

[0007] In the third aspect, an embodiment of the present invention further provides an electronic device, comprising: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores a computer program executable by the at least one processor, and the computer program is executed by the at least one processor so that the at least one processor can execute a distributed uploading method for vehicle fault files described in any embodiment of the present invention.

[0008] In a fourth aspect, an embodiment of the present invention further provides a computer-readable storage medium, wherein the computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a processor to implement a vehicle fault file distributed uploading method described in any embodiment of the present invention when executed.

[0009] The technical solution of the embodiment of the present invention adopts a file sub-packaging strategy, sub-packaging the faulty file according to the size of the faulty file and the transmission capacity of the SIM card, and uploading each sub-file after naming and compressing it. The sub-packaging and compressed files can be transmitted to the Internet of Vehicles platform more stably and quickly, effectively solving the problem of large file transmission and optimizing the transmission efficiency. In particular, by adding special characters to the last sub-packaging sub-file, it is ensured that the Internet of Vehicles platform merges the scattered sub-files in the correct order after receiving the file, ensuring the integrity and accuracy of the faulty file.

[0010] It should be understood that the contents described in this section are not intended to identify the key or important features of the embodiments of the present invention, nor are they intended to limit the scope of the present invention. Other features of the present invention will become easily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the following briefly introduces the drawings required for use in the description of the embodiments. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0012] Figure 1 The present invention is a flowchart of a method for distributing vehicle fault file upload provided in accordance with the first embodiment of the present invention.

[0013] Figure 2 This is a flowchart of another method for distributing vehicle fault files according to the second embodiment of the present invention.

[0014] Figure 3 It is a structural diagram of a distributed uploading device for vehicle fault files provided according to Embodiment 3 of the present invention.

[0015] Figure 4It is a structural schematic diagram of an electronic device for implementing a distributed uploading method for vehicle fault files according to an embodiment of the present invention. DETAILED DESCRIPTION

[0016] In order to enable those skilled in the art to better understand the scheme of the present invention, the technical scheme in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present invention.

[0017] It should be noted that the terms "first", "second", etc. in the specification and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of the present invention described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units that are clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0018] Embodiment 1

[0019] Figure 1 This is a flow chart of a method for distributed uploading of vehicle fault files provided in Example 1 of the present invention. This embodiment can be applicable to the situation where operating condition data collected by a remote information processing control unit is distributedly uploaded to a vehicle networking platform. The method can be executed by a vehicle fault file distributed uploading device, which can be implemented in the form of hardware and / or software. The device can be configured in a distributed storage system that supports distributed uploading.

[0020] like Figure 1 As shown, the method includes: S110, continuously receiving the fault signal of the target vehicle through the remote information processing control unit, and extracting the component fault code and the fault occurrence time corresponding to the fault signal in the target vehicle according to the fault signal.

[0021] The telematics control unit, also known as Telematics Box, or T-Box for short, is a remote communication terminal that integrates vehicle body network and wireless communication functions, and contains a user identification SIM card for mobile communication. The vehicle system must have a T-Box device to achieve networking. In the embodiment of the present invention, T-Box is mainly used to collect and process the working condition information of various components in the vehicle; the fault signal is a signal generated and sent when a vehicle fails, carrying characteristic information related to the fault; and the component fault code is used to uniquely identify the code of a certain component failure of the vehicle. Different fault codes correspond to different fault types and components, which facilitates and quickly locates the fault location; the fault occurrence time refers to the specific time when the fault occurs, which is an important basis for determining the time range for collecting working condition data.

[0022] T-Box monitors the target vehicle at all times and immediately receives the fault signal once the vehicle fails. Then, through the internal preset signal analysis program, key information is extracted from the fault signal, namely the component fault code and the time of the fault. The component fault code can accurately locate the specific component of the vehicle that has failed, and the time of the fault provides a time reference point for the subsequent collection of working condition data.

[0023] S120. Collect, through the remote information processing control unit, various operating condition data corresponding to the component fault code within a specified time range before and after the fault occurrence time, and generate a fault file based on the collected various operating condition data.

[0024] The operating condition data reflects the various operating parameters of the vehicle under different working conditions. By analyzing these data, we can gain an in-depth understanding of the actual operating conditions of the vehicle when a fault occurs, which helps to accurately determine the cause of the fault. The fault file is a file generated by T-Box by collating and combining the collected operating condition data. It is the core data carrier for subsequent transmission and analysis, and contains detailed information about the vehicle when the fault occurs.

[0025] Based on the extracted fault occurrence time, T-Box collects various operating condition data related to component fault codes within a specified time range before and after the fault (e.g., 60 seconds before the fault to 60 seconds after the fault). These operating condition data include operating parameters of multiple vehicle systems, such as engine speed, vehicle speed, oil temperature, etc. After the collection is completed, these operating condition data are integrated to generate a fault file according to a specific data format and logic, which comprehensively records the operating status of the vehicle when the fault occurs.

[0026] S130. Splitting the fault file into a plurality of sub-files according to a preset packetization sequence through the telematics control unit based on the file size of the fault file and the transmission capability of the SIM card.

[0027] File size refers to the size of the storage space occupied by the fault file, and is one of the important factors that determine whether sub-packet transmission is required; due to the data transmission rate and capacity limitations of SIM cards, different types of SIM cards have different transmission capabilities, which determines the amount of data that can be transmitted at one time; to ensure that sub-files can be correctly merged on the Internet of Vehicles platform, the accuracy of sub-file transmission and merging is guaranteed through the pre-set sequence rules for splitting fault files; sub-files are smaller files generated after the fault file is split, and each sub-file contains part of the data of the original fault file, which is the basic data unit in the transmission process.

[0028] T-Box will evaluate the size of the faulty file and determine whether and how to sub-package it based on the transmission capacity of the SIM card. If the faulty file is too large and exceeds the capacity of the SIM card for one transmission, the faulty file will be split into multiple smaller sub-files based on the preset sub-packaging rules to ensure that the file can be smoothly transmitted through the SIM card and avoid transmission failure due to excessive file size.

[0029] S140. After naming each sub-file according to the subpackaging order, the remote information processing control unit uses a set compression algorithm to compress each sub-file to obtain multiple compressed files, and uploads each compressed file to the Internet of Vehicles platform in sequence according to the file number in the file name from small to large.

[0030] Each sub-file contains the number of the telematics control unit and a file sequence number that matches the sub-packaging order, and the sub-file of the last sub-packaging contains special characters.

[0031] A compression algorithm is a computational method used to reduce file size. It removes data redundancy through a specific encoding method and reduces the file size without losing key information. Common algorithms include ZIP and RAR. A compressed file is a sub-file processed by a compression algorithm. Its size becomes smaller and more suitable for transmission over the network. The Internet of Vehicles platform is a platform that integrates data reception, storage, analysis and management functions. It is responsible for receiving various types of data uploaded by vehicles, including fault files, and provides support for vehicle fault diagnosis, maintenance and management.

[0032] Among them, the file sequence number refers to the number assigned to each sub-file according to the sub-packaging order, which is used to identify the order of the sub-files in the entire fault file, so as to facilitate the Internet of Vehicles platform to receive and merge them in sequence; and the special characters are pre-set specific symbols, which are added to the name of the last sub-packaging sub-file to inform the Internet of Vehicles platform that the sub-file is the last sub-packaging file, which is an important identifier for file merging.

[0033] Use the set compression algorithm to compress each named sub-file to reduce the file size, improve transmission efficiency and save SIM card traffic. After compression, upload the compressed files to the Internet of Vehicles platform in order from small to large file numbers in the file name. Each compressed file contains the telematics control unit number and file number to facilitate platform reception and management.

[0034] Optionally, the remote information processing control unit names each subfile according to the subpackaging order, which may include: generating a number of the remote information processing control unit according to the identification information of the remote information processing control unit and the time when the fault occurred through the remote information processing control unit; obtaining a current subfile obtained by splitting in sequence through the remote information processing control unit; determining the subpackaging position of the current subfile in all subfiles according to the subpackaging order through the remote information processing control unit, and determining the current file sequence number of the current subfile according to the subpackaging position; judging by the remote information processing control unit, if the current subfile does not belong to the subfile of the last subpackaging, naming the current subfile according to the number of the remote information processing control unit and the current file sequence number, and returning to execute the operation of obtaining a current subfile obtained by splitting in sequence; judging by the remote information processing control unit, if the current subfile belongs to the subfile of the last subpackaging, naming the current subfile according to the number of the remote information processing control unit, the current file sequence number and preset special characters, and ending the file name process.

[0035] The identification information is used to uniquely identify the specific information of the telematics control unit. The number generated in combination with the time when the fault occurred can ensure that each sub-file can clearly identify its source and generation time. After the fault file is split into multiple sub-files, the sub-files are selected one by one in a certain order for naming operations. Each time a sub-file is selected as the current processing object, so that its subsequent location and naming can be performed to ensure that each sub-file can be processed correctly. The sub-packaging order is a pre-set rule for splitting the fault file, which determines the generation order of the sub-files and the arrangement order during the transmission process, ensuring the orderliness of the sub-files; the sub-packaging position indicates the specific position of the current sub-file in all the split sub-files, which is the key basis for determining the file number.

[0036] According to the preset sub-packaging order, the position of the currently acquired sub-file in all sub-files is judged, and a corresponding file number is determined for the current sub-file based on the current position information. The file number increases in sequence from 1, and is used to identify the order of the sub-files in the entire fault file, ensuring that the sub-files can be received and merged in the correct order on the Internet of Vehicles platform.

[0037] The last sub-file is the last file in all the sub-files. Its naming method is slightly different from other sub-files. Special characters are needed to mark the integrity of the file and inform the Internet of Vehicles platform that all sub-files have been transferred and can be merged. The preset special characters are specific symbols pre-set in the naming rules, such as "#" and "@", which are added to the file name of the last sub-file.

[0038] The current subfile is judged. If the current subfile is not the subfile of the last subpackage, the generated telematics control unit number and the determined current file serial number are used to name the subfile. After the naming is completed, return to the step of "obtaining a current subfile obtained by splitting in sequence" and continue to name the next subfile; if the current subfile is a subfile of the last subpackage, the preset special characters are added to the telematics control unit number and the current file serial number to name it. After the naming is completed, the entire file name generation process ends, which means that all subfiles have been named.

[0039] The technical solution of the embodiment of the present invention adopts a file sub-packaging strategy, sub-packaging the faulty file according to the size of the faulty file and the transmission capacity of the SIM card, and uploading each sub-file after naming and compressing it. The sub-packaging and compressed files can be transmitted to the Internet of Vehicles platform more stably and quickly, effectively solving the problem of large file transmission and optimizing the transmission efficiency. In particular, by adding special characters to the last sub-packaging sub-file, it is ensured that the Internet of Vehicles platform merges the scattered sub-files in the correct order after receiving the file, ensuring the integrity and accuracy of the faulty file.

[0040] Embodiment 2

[0041] Figure 2 This is a flow chart of another method for distributing vehicle fault files for uploading provided in the second embodiment of the present invention. This embodiment is refined based on the above embodiment.

[0042] like Figure 2 As shown, the method includes: S210, continuously receiving the fault signal of the target vehicle through the remote information processing control unit, and extracting the component fault code and the fault occurrence time corresponding to the fault signal in the target vehicle according to the fault signal.

[0043] S220. Collect, through the remote information processing control unit, various operating condition data corresponding to the component fault code within a specified time range before and after the fault occurrence time, and generate a fault file based on the collected various operating condition data.

[0044] S230. Split the fault file into a plurality of sub-files according to a preset packetization sequence through the telematics control unit based on the file size of the fault file and the transmission capability of the SIM card.

[0045] S240. After naming each sub-file according to the subpackaging order, the remote information processing control unit compresses each sub-file using a set compression algorithm to obtain multiple compressed files, and uploads each compressed file to the Internet of Vehicles platform in sequence according to the file number in the file name from small to large.

[0046] Each sub-file contains the number of the telematics control unit and a file sequence number that matches the sub-packaging order, and the sub-file of the last sub-packaging contains special characters.

[0047] S250. After uploading each compressed file to the Internet of Vehicles platform in sequence through the remote information processing control unit, the Internet of Vehicles platform decompresses the target compressed file each time it receives a target compressed file transmitted from the target remote information processing control unit to obtain a target temporary sub-file.

[0048] As the core hub for information exchange between vehicles and the outside world, the Internet of Vehicles platform is responsible for receiving, processing, storing and analyzing data uploaded by vehicles. In this scenario, it is responsible for the management of fault files. The target compressed file is a file transmitted by T-Box after being compressed and packaged according to the fault file. It can transmit data more efficiently under limited transmission conditions. The target temporary sub-file is the file obtained after decompressing the target compressed file. Since the final merging and storage operations have not been completed, it is called a temporary sub-file. It contains part of the data content of the fault file.

[0049] S260: Detect, through the Internet of Vehicles platform, whether the file name of the target temporary sub-file contains a special character for locating the last sub-packet.

[0050] After the Internet of Vehicles platform obtains the target temporary sub-file, it first parses its file name, that is, checks whether the file name contains a pre-set special character used to locate the last sub-package. This special character is a key identifier in the entire file processing flow and is used to determine whether the current sub-file is the last sub-package file of the same fault file.

[0051] S270: If not, temporarily cache the target temporary sub-file according to the file name of the target temporary sub-file and a preset storage rule.

[0052] The preset storage rules are a set of specifications pre-set by the Internet of Vehicles platform for managing temporary sub-file storage, including determining the directory structure of file storage, the association between file names and storage locations, etc. For example, different folders may be created according to the T-Box number, and temporary sub-files from the same control unit are stored in the corresponding folders to facilitate subsequent search and merging. Temporary caching refers to temporarily storing sub-files that have not been merged in a cache area. It is similar to a temporary database, which is used to temporarily store these sub-files and wait for all sub-files of the same fault file to be transferred before performing the merge operation.

[0053] Optionally, based on the file name of the target temporary sub-file, the target temporary sub-file is temporarily cached according to preset storage rules, which may include: generating a target file code for the target temporary sub-file through the Internet of Vehicles platform, and storing the target temporary sub-file and the target file code in a file library in association with each other, and then storing the target telematics control unit number, file sequence number and target file code in the file name of the target temporary sub-file in a cache area in association with each other.

[0054] The target file code is a unique identifier assigned by the Internet of Vehicles platform to each target temporary sub-file. It is generated according to a specific coding algorithm and usually contains some file-related information, such as timestamps, random numbers, etc., to ensure the uniqueness of the code in the entire system. Through this code, the Internet of Vehicles platform can accurately identify and manage each sub-file in a large number of files, facilitating subsequent storage, search and operation. Its uniqueness ensures that each sub-file can be accurately distinguished in a complex file management system to avoid file confusion and erroneous operations.

[0055] The file library is an area in the Internet of Vehicles platform for centralized storage of files. It has efficient storage and retrieval functions. In the embodiment of the present invention, it is used to store target temporary sub-files. Various files are classified and stored by adopting a specific storage architecture, such as a file directory structure, database storage, etc. When storing, the target temporary sub-files will be placed in the file library according to a certain directory structure or storage rules, and the target file code will be associated with the storage location of the file and other information so that the corresponding file can be quickly found through the code later.

[0056] The cache is a high-speed temporary data storage area. Unlike the file library, it focuses more on fast access and reading of data. During the vehicle fault file processing, the cache is used to temporarily store key information of the target temporary sub-file, such as the control unit number, file sequence number, and file encoding. When it is necessary to find all sub-files of the same fault file for merging, the Internet of Vehicles platform can quickly obtain this information directly from the cache without frequently reading files from the file library, thereby improving the system's response speed and processing efficiency.

[0057] Furthermore, the number of the target telematics control unit in the file name of the target temporary sub-file, the file sequence number and the target file code are associated and stored in the cache area, which may include: through the Internet of Vehicles platform, creating a key-value pair storage structure with the number of the target telematics control unit as the key name, and filling the file sequence number and the target file code in the key-value pair storage structure in a list form as key values; when the Internet of Vehicles platform receives a new temporary cache task, the current key name is determined by reading the number of the target telematics control unit in the file name of the current target temporary sub-file; through the Internet of Vehicles platform, all historical key-value pair storage structures are traversed in the cache area, and it is determined whether there is a historical key name identical to the current key name in the historical key-value pairs; if so, the file sequence number and the target file code in the file name of the new target temporary sub-file are appended as new key values ​​to the target historical key-value pair storage structure; if not, the number of the target telematics control unit in the file name of the new target temporary sub-file is used as a new key name, and a new target key-value pair storage structure is created.

[0058] The key-value pair storage structure is a standard data storage method, which consists of a key name (key) and a corresponding key value (value). In the embodiment of the present invention, by using the number of the target telematics control unit as the key name, the file number and the target file code related thereto are stored as the key value, so as to facilitate quick search and management of data.

[0059] In a specific example, if the identification information of the target telematics control unit is recorded as TboxA, and the time of the fault is recorded as Time1, then the serial number of the target telematics control unit can be TboxA_Time1, which can be recorded as Key:TboxA_Time1 in the key-value pair storage structure as a key name. Under the key name (key), Value is a list containing multiple sub-items, each of which is a key-value pair, so it can contain multiple sets of file serial numbers and target file codes, such as {serial number: 1, file code: fileNo1}, {serial number: 2, file code: fileNo2}, ..., {serial number: F, file code: fileNoF}. Then, in the key-value pair storage structure, it can be recorded as Value: [{serial number: 1, file code: fileNo1}, {serial number: 2, file code: fileNo2}, {serial number: F, file code: fileNoF}].

[0060] The historical key-value pair storage structure refers to the collection of all key-value pairs that have been stored in the cache, which contains the relevant information of each target temporary sub-file that has been processed before. By traversing this collection, the platform can find out whether there is existing storage information related to the current new sub-file, so as to perform corresponding append or create operations. If there is the same key name, such as TboxA_Time1, it means that other sub-file information from the same fault file has been stored before; if there is no same key name, it means that this is the first sub-file information from the control unit that needs to be stored.

[0061] In the cache, when there is historical storage information from the same fault file as the current new sub-file, the corresponding existing key-value pair storage structure is the target historical key-value pair storage structure. The new sub-file information will be appended to this structure to ensure the consistency and integrity of all sub-file information of the same control unit. If the number of the target telematics control unit of the current new sub-file does not have a corresponding historical key name in the cache, the new target key-value pair storage structure is a new key-value pair structure created to store the relevant information of the sub-file.

[0062] S280: If yes, locate all temporarily cached matching temporary subfiles that belong to the same fault file as the target temporary subfile according to the file name of the target temporary subfile, and merge all matching temporary subfiles with the target temporary subfile to obtain a fault file for standardized storage.

[0063] The matching temporary subfiles and the current target temporary subfile containing special characters belong to other temporary subfiles of the same fault file. These subfiles are temporarily cached during the previous transmission process and are merged after the last subfile arrives. Standardized storage means that the Internet of Vehicles platform stores the merged fault files in a unified format and specification, which includes determining the file storage format (such as database storage format, file system storage format, etc.), storage location, and related index settings, etc., to ensure that the file can be stored for a long time and stably, and facilitate subsequent rapid query and analysis.

[0064] Optionally, based on the file name of the target temporary sub-file, all matching temporary sub-files in the temporary cache that belong to the same fault file as the target temporary sub-file are located, and all matching temporary sub-files are merged with the target temporary sub-file to obtain a fault file for standardized storage, which may include: obtaining each matching file code that matches the number of the target telematics control unit from the cache area through the Internet of Vehicles platform, and obtaining the matching temporary sub-file corresponding to each matching file code from the file library; through the Internet of Vehicles platform, according to the file number that matches the matching file code in the cache area, merging each matching temporary sub-file to obtain a fault file and uploading it to the file library, and deleting each matching file code and matching temporary sub-file currently stored in the file library, as well as the temporary cache in the cache area containing all the matching temporary sub-files and the target temporary sub-file.

[0065] Matching file codes refer to codes associated with the target telematics control unit number and used to identify other sub-files of the same fault file. These codes are generated and stored in the cache when the sub-file is temporarily cached. They can be used to accurately find the corresponding sub-file. Matching temporary sub-files refer to other sub-files that belong to the same fault file as the target temporary sub-file. They are temporarily stored in the file library during the previous transmission process, waiting to be merged into a complete fault file. These sub-files are associated with the records in the cache through file codes to ensure that they can be accurately obtained when needed.

[0066] After completing the merging and uploading of the faulty files, in order to save the storage space of the file library and keep the data neat, the platform will delete the matching file codes and corresponding matching temporary sub-files currently stored in the file library. This is because the temporary sub-files no longer need to be stored separately after the merging is completed. The deletion operation can avoid wasting storage space and simplify the management of the file library. Since all matching temporary sub-files and the target temporary sub-files combine the faulty file, for the same purpose, all temporary caches related to the faulty file are deleted to save cache space to ensure that there is enough space to perform other cache tasks.

[0067] Furthermore, the method may also include: responding to a fault query request initiated by a user on a front-end page through the Internet of Vehicles platform, and obtaining the telematics control unit number, part fault code or fault occurrence time contained in the query request; calling a target fault file containing the telematics control unit number, part fault code or fault occurrence time information in a file library through the Internet of Vehicles platform, and generating a visual fault occurrence record list by parsing the target fault file.

[0068] The Internet of Vehicles platform will respond to the fault query request initiated by the user on the front-end page. When the user enters relevant information on the front-end page and submits the query request, the Internet of Vehicles platform will parse the request and extract key information such as the telematics control unit number, part fault code, or fault occurrence time. The visual fault occurrence record list is the result of parsing and organizing the information in the target fault file and presenting it to the user in an intuitive list format. The list can include detailed information such as the time of the fault, the parts involved in the fault, the fault code, etc., which is convenient for users to view and analyze the fault situation of the vehicle.

[0069] The technical solution of the embodiment of the present invention, through the refinement of the overall solution, mainly focuses on the process of the Internet of Vehicles platform to process vehicle fault files, from file decompression, storage management to merging and querying, providing strong support for vehicle fault analysis. Specifically, by temporarily caching sub-files and storing the sub-files and target file encodings in the file library, an efficient indexing mechanism is established to achieve efficient decompression and orderly caching; by accurately locating all matching temporary sub-files of the same fault file in the temporary cache and merging them into a fault file for standardized storage, accurate merging and standardized storage are achieved; by providing users with a fault query method, maintenance personnel, R&D personnel, etc. can intuitively obtain fault-related information, which helps to quickly diagnose the cause of the fault and improve the efficiency and accuracy of vehicle fault handling; finally, by releasing the storage space of the cache area and the file library, data redundancy is avoided and optimized management of storage resources is achieved.

[0070] Embodiment 3

[0071] Figure 3 A schematic diagram of the structure of a distributed uploading device for vehicle fault files provided in Embodiment 3 of the present invention.

[0072] like Figure 3As shown, the device includes: a fault signal receiving module 310, which is used to continuously receive the fault signal of the target vehicle through the remote information processing control unit, and extract the component fault code and the fault occurrence time corresponding to the fault signal in the target vehicle according to the fault signal; a fault file generating module 320, which is used to collect various working condition data corresponding to the component fault code within a specified time range before and after the fault occurrence time through the remote information processing control unit, and generate a fault file according to the collected various working condition data; a file packaging module 330, which is used to, through the remote information processing control unit, according to the file size of the fault file, and the transmission capacity of the SIM card, splits the fault file into multiple sub-files according to a preset sub-packaging order; a sub-file uploading module 340 is used to name each sub-file according to the sub-packaging order through the telematics control unit, compress each sub-file using a set compression algorithm to obtain multiple compressed files, and upload each compressed file in sequence to the Internet of Vehicles platform in ascending order of the file number in the file name; wherein each sub-file contains the number of the telematics control unit and the file number matching the sub-packaging order, and the sub-file of the last sub-packaging contains special characters.

[0073] The technical solution of the embodiment of the present invention adopts a file sub-packaging strategy, sub-packaging the faulty file according to the size of the faulty file and the transmission capacity of the SIM card, and uploading each sub-file after naming and compressing it. The sub-packaging and compressed files can be transmitted to the Internet of Vehicles platform more stably and quickly, effectively solving the problem of large file transmission and optimizing the transmission efficiency. In particular, by adding special characters to the last sub-packaging sub-file, it is ensured that the Internet of Vehicles platform merges the scattered sub-files in the correct order after receiving the file, ensuring the integrity and accuracy of the faulty file.

[0074] Optionally, based on the above embodiments, the sub-file upload module 340 may include: a unique number generation unit, which is used to generate the number of the telematics control unit according to the identification information of the telematics control unit and the time when the fault occurred; a sub-file acquisition unit, which is used to sequentially acquire a current sub-file obtained by splitting; a file sequence number determination unit, which is used to determine the sub-packaging position of the current sub-file in all sub-files according to the sub-packaging order, and determine the current file sequence number of the current sub-file according to the sub-packaging position; a sub-file naming unit, which is used to name the current sub-file according to the number of the telematics control unit and the current file sequence number if the current sub-file does not belong to the sub-file of the last sub-packaging, and return to execute the operation of sequentially acquiring a current sub-file obtained by splitting; a last sub-packaging processing unit, which is used to name the current sub-file according to the number of the telematics control unit, the current file sequence number and preset special characters if the current sub-file belongs to the sub-file of the last sub-packaging, and end the file name process.

[0075] Optionally, on the basis of the above embodiments, it may also include: a file storage unit, which is used to, after uploading each compressed file to the Internet of Vehicles platform in sequence through the remote information processing control unit, decompress the target compressed file through the Internet of Vehicles platform whenever receiving the target compressed file transmitted from the target remote information processing control unit, to obtain a target temporary sub-file; through the Internet of Vehicles platform, detect whether the file name of the target temporary sub-file contains special characters for locating the last sub-packet; if not, temporarily cache the target temporary sub-file according to the file name of the target temporary sub-file and preset storage rules; if so, locate all matching temporary sub-files that belong to the same fault file as the target temporary sub-file in the temporary cache according to the file name of the target temporary sub-file, and merge all matching temporary sub-files with the target temporary sub-file to obtain a fault file for standardized storage.

[0076] Optionally, based on the above embodiments, the file storage unit may include: a target file code generation subunit, which is used to generate a target file code of a target temporary sub-file through the Internet of Vehicles platform, and after the target temporary sub-file and the target file code are associated and stored in the file library, the number of the target telematics control unit, the file sequence number and the target file code in the file name of the target temporary sub-file are associated and stored in the cache area.

[0077] Optionally, based on the above embodiments, the file storage unit may further include: a matching temporary sub-file acquisition sub-unit, which is used to obtain each matching file code that matches the number of the target remote information processing control unit from the cache area through the Internet of Vehicles platform, and obtain the matching temporary sub-file corresponding to each matching file code from the file library; a matching temporary sub-file merging sub-unit, which is used to merge each matching temporary sub-file into a fault file and upload it to the file library through the Internet of Vehicles platform according to the file number that matches the matching file code in the cache area, and delete each matching file code and matching temporary sub-file currently stored in the file library, as well as the temporary cache in the cache area containing all the matching temporary sub-files and the target temporary sub-file.

[0078] Optionally, based on the above embodiments, the target file code generation subunit can be used to create a key-value pair storage structure through the Internet of Vehicles platform with the number of the target remote information processing control unit as the key name, and fill the file number and the target file code in the key-value pair storage structure in a list form as the key value; when the Internet of Vehicles platform receives a new temporary cache task, the current key name is determined by reading the number of the target remote information processing control unit in the file name of the current target temporary sub-file; through the Internet of Vehicles platform, all historical key-value pair storage structures are traversed in the cache area, and it is determined whether there is a historical key name identical to the current key name in the historical key-value pairs; if so, the file number and the target file code in the file name of the new target temporary sub-file are appended as new key values ​​to the target historical key-value pair storage structure; if not, the number of the target remote information processing control unit in the file name of the new target temporary sub-file is used as the new key name, and a new target key-value pair storage structure is created.

[0079] Optionally, based on the above embodiments, it may also include: a query response unit, used to respond to a fault query request initiated by a user on the front-end page, and obtain the telematics control unit number, part fault code or fault occurrence time contained in the query request; call the target fault file containing the telematics control unit number, part fault code or fault occurrence time information in the file library, and generate a visual fault occurrence record list by parsing the target fault file.

[0080] A vehicle fault file distributed uploading device provided by an embodiment of the present invention can execute a vehicle fault file distributed uploading method provided by any embodiment of the present invention, and has functional modules and beneficial effects corresponding to the execution method.

[0081] Embodiment 4

[0082] Figure 4A schematic diagram of the structure of an electronic device 10 that can be used to implement an embodiment of the present invention is shown. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device can also represent various forms of mobile devices, such as personal digital processing, cellular phones, smart phones, wearable devices (such as helmets, glasses, watches, etc.) and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely examples and are not intended to limit the implementation of the present invention described and / or required herein.

[0083] like Figure 4 As shown, the electronic device 10 includes at least one processor 11, and a memory connected to the at least one processor 11, such as a read-only memory (ROM) 12, a random access memory (RAM) 13, etc., wherein the memory stores a computer program that can be executed by at least one processor, and the processor 11 can perform various appropriate actions and processes according to the computer program stored in the read-only memory (ROM) 12 or the computer program loaded from the storage unit 18 to the random access memory (RAM) 13. In the RAM 13, various programs and data required for the operation of the electronic device 10 can also be stored. The processor 11, the ROM 12, and the RAM 13 are connected to each other through a bus 14. The input / output (I / O) interface 15 is also connected to the bus 14.

[0084] A number of components in the electronic device 10 are connected to the I / O interface 15, including: an input unit 16, such as a keyboard, a mouse, etc.; an output unit 17, such as various types of displays, speakers, etc.; a storage unit 18, such as a disk, an optical disk, etc.; and a communication unit 19, such as a network card, a modem, a wireless communication transceiver, etc. The communication unit 19 allows the electronic device 10 to exchange information / data with other devices through a computer network such as the Internet and / or various telecommunication networks.

[0085] The processor 11 may be a variety of general and / or special processing components with processing and computing capabilities. Some examples of the processor 11 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various special artificial intelligence (AI) computing chips, various processors running machine learning model algorithms, a digital signal processor (DSP), and any appropriate processor, controller, microcontroller, etc. The processor 11 executes the various methods and processes described above, such as a distributed uploading method for vehicle fault files.

[0086] That is: the remote information processing control unit continuously receives the fault signal of the target vehicle, and extracts the component fault code and the fault occurrence time corresponding to the fault signal in the target vehicle according to the fault signal; the remote information processing control unit collects the various operating condition data corresponding to the component fault code within a specified time range before and after the fault occurrence time, and generates a fault file according to the collected various operating condition data; the remote information processing control unit splits the fault file into multiple sub-files according to the preset sub-packaging order according to the file size of the fault file and the transmission capacity of the SIM card; the remote information processing control unit names each sub-file according to the sub-packaging order, and then compresses each sub-file using a set compression algorithm to obtain multiple compressed files, and uploads each compressed file to the vehicle networking platform in sequence according to the file number in the file name from small to large; wherein each sub-file contains the number of the remote information processing control unit and the file number matching the sub-packaging order, and the sub-file of the last sub-packaging contains special characters.

[0087] In some embodiments, a method for distributing uploading a vehicle fault file may be implemented as a computer program, which is tangibly contained in a computer-readable storage medium, such as a storage unit 18. In some embodiments, part or all of the computer program may be loaded and / or installed on the electronic device 10 via the ROM 12 and / or the communication unit 19. When the computer program is loaded into the RAM 13 and executed by the processor 11, one or more steps of the method for distributing uploading a vehicle fault file described above may be performed. Alternatively, in other embodiments, the processor 11 may be configured to execute a method for distributing uploading a vehicle fault file by any other appropriate means (e.g., by means of firmware).

[0088] Various implementations of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chips (SOCs), load programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various implementations can include: being implemented in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which can be a special purpose or general purpose programmable processor that can receive data and instructions from a storage system, at least one input device, and at least one output device, and transmit data and instructions to the storage system, the at least one input device, and the at least one output device.

[0089] Computer programs for implementing the methods of the present invention may be written in any combination of one or more programming languages. These computer programs may be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, so that when the computer program is executed by the processor, the functions / operations specified in the flow chart and / or block diagram are implemented. The computer program may be executed entirely on the machine, partially on the machine, partially on the machine and partially on a remote machine as a stand-alone software package, or entirely on a remote machine or server.

[0090] In the context of the present invention, a computer-readable storage medium may be a tangible medium that may contain or store a computer program for use by or in conjunction with an instruction execution system, device, or equipment. A computer-readable storage medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices, or equipment, or any suitable combination of the foregoing. Alternatively, a computer-readable storage medium may be a machine-readable signal medium. A more specific example of a machine-readable storage medium may include an electrical connection based on one or more lines, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0091] To provide interaction with a user, the systems and techniques described herein may be implemented on an electronic device having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and a pointing device (e.g., a mouse or trackball) through which the user can provide input to the electronic device. Other types of devices may also be used to provide interaction with the user; for example, the feedback provided to the user may be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form (including acoustic input, voice input, or tactile input).

[0092] The systems and techniques described herein may be implemented in a computing system that includes backend components (e.g., as a data server), or a computing system that includes middleware components (e.g., an application server), or a computing system that includes frontend components (e.g., a user computer with a graphical user interface or a web browser through which a user can interact with implementations of the systems and techniques described herein), or a computing system that includes any combination of such backend components, middleware components, or frontend components. The components of the system may be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: a local area network (LAN), a wide area network (WAN), a blockchain network, and the Internet.

[0093] A computing system may include a client and a server. The client and the server are generally remote from each other and usually interact through a communication network. The client and server relationship is generated by computer programs running on the corresponding computers and having a client-server relationship with each other. The server may be a cloud server, also known as a cloud computing server or cloud host, which is a host product in the cloud computing service system to solve the defects of difficult management and weak business scalability in traditional physical hosts and VPS services.

[0094] It should be understood that the various forms of processes shown above can be used to reorder, add or delete steps. For example, the steps described in the present invention can be executed in parallel, sequentially or in different orders, as long as the desired results of the technical solution of the present invention can be achieved, and this document does not limit this.

[0095] The above specific implementations do not constitute a limitation on the protection scope of the present invention. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions can be made according to design requirements and other factors. Any modification, equivalent substitution and improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.

Claims

1. A distributed uploading method for vehicle fault files, characterized in that: The method is executed by a distributed storage system, wherein the distributed storage system includes a telematics control unit configured with a user identity identification SIM card and a vehicle networking platform, and the method includes: Continuously receiving the fault signal of the target vehicle through the remote information processing control unit, and extracting the fault code of the component corresponding to the fault signal and the fault occurrence time in the target vehicle according to the fault signal; By means of the telematics control unit, various operating condition data corresponding to the fault code of the component within a specified time range before and after the fault occurs are collected, and a fault file is generated according to the collected various operating condition data; By means of the telematics control unit, the fault file is split into a plurality of sub-files in a preset sub-packaging sequence according to the file size of the fault file and the transmission capability of the SIM card; The remote information processing control unit compresses each sub-file using a set compression algorithm after naming each sub-file in the sub-packaging order to obtain a plurality of compressed files, and uploads each compressed file to the Internet of Vehicles platform in sequence according to the file number in the file name from small to large. Each sub-file contains the number of the telematics control unit and a file sequence number that matches the sub-packaging order, and the sub-file of the last sub-packaging contains special characters.

2. The method according to claim 1, characterized in that By means of the telematics control unit, each sub-file is named according to the sub-packaging sequence, including: generating, by the telematics control unit, a number of the telematics control unit according to identification information of the telematics control unit and a time when a fault occurs; By means of the telematics processing control unit, sequentially obtaining a current sub-file obtained by splitting; Determining, by the telematics control unit, the sub-packaging position of the current sub-file in all the sub-files according to the sub-packaging sequence, and determining the current file sequence number of the current sub-file according to the sub-packaging position; The remote information processing control unit determines that if the current subfile does not belong to the subfile of the last subpackage, the current subfile is named according to the number of the remote information processing control unit and the current file sequence number, and returns to execute the operation of sequentially obtaining the current subfiles obtained by the splitting; The remote information processing control unit determines that if the current sub-file belongs to the last sub-packaged sub-file, the current sub-file is named according to the number of the remote information processing control unit, the current file sequence number and preset special characters, and the file name process is ended.

3. The method according to claim 1, characterized in that After uploading each compressed file to the Internet of Vehicles platform in sequence through the telematics control unit, the method further includes: Whenever the vehicle networking platform receives a target compressed file transmitted from a target telematics control unit, it decompresses the target compressed file to obtain a target temporary sub-file; Through the Internet of Vehicles platform, detect whether the file name of the target temporary sub-file contains special characters used to locate the last sub-packet; If not, the target temporary sub-file is temporarily cached according to the file name of the target temporary sub-file and the preset storage rule; If so, all matching temporary subfiles in the temporary cache that belong to the same fault file as the target temporary subfile are located according to the file name of the target temporary subfile, and all matching temporary subfiles are merged with the target temporary subfile to obtain a fault file for standardized storage.

4. The method according to claim 3, characterized in that According to the file name of the target temporary sub-file, the target temporary sub-file is temporarily cached according to the preset storage rule, including: The target file code of the target temporary sub-file is generated through the Internet of Vehicles platform, and after the target temporary sub-file and the target file code are associated and stored in the file library, the number of the target telematics control unit, the file sequence number and the target file code in the file name of the target temporary sub-file are associated and stored in the cache area.

5. The method according to claim 3, characterized in that: According to the file name of the target temporary sub-file, all matching temporary sub-files in the temporary cache belonging to the same fault file as the target temporary sub-file are located, and all matching temporary sub-files are merged with the target temporary sub-file to obtain a fault file for standardized storage, including: Obtaining, through the Internet of Vehicles platform, from the cache area, each matching file code that matches the serial number of the target telematics control unit, and obtaining, from the file library, a matching temporary sub-file corresponding to each matching file code; Through the Internet of Vehicles platform, according to the file number that matches the matching file code in the cache area, each matching temporary sub-file is merged to obtain a fault file that is uploaded to the file library, and the matching file codes and matching temporary sub-files currently stored in the file library, as well as the temporary cache in the cache area containing all the matching temporary sub-files and the target temporary sub-file are deleted.

6. The method according to claim 4, characterized in that The target telematics control unit number, the file sequence number and the target file code in the file name of the target temporary sub-file are stored in the cache area in association, including: Through the Internet of Vehicles platform, a key-value pair storage structure is created with the serial number of the target telematics control unit as a key name, and the file serial number and the target file code are filled into the key-value pair storage structure in a list form as key values; When the Internet of Vehicles platform receives a new temporary cache task, the current key name is determined by reading the number of the target telematics control unit in the file name of the current target temporary sub-file; Through the Internet of Vehicles platform, traverse all historical key-value pair storage structures in the cache area, and determine whether there is a historical key name that is the same as the current key name in the historical key-value pairs; If it exists, the file name, file number and target file code of the new target temporary sub-file are added as new key values ​​to the target history key-value pair storage structure; If it does not exist, the number of the target telematics control unit in the file name of the new target temporary sub-file is used as a new key name, and a new target key-value pair storage structure is created.

7. The method according to claim 3 or 4, characterized in that: include: Responding to a fault query request initiated by a user on a front-end page through the Internet of Vehicles platform, and obtaining a telematics control unit number, a part fault code, or a fault occurrence time contained in the query request; The target fault file containing the telematics control unit number, part fault code or fault occurrence time information is called in the file library through the Internet of Vehicles platform, and a visual fault occurrence record list is generated by parsing the target fault file.

8. A distributed upload device for vehicle fault files, arranged in a distributed storage system, wherein the distributed storage system includes a telematics control unit configured with a user identity identification SIM card and a vehicle networking platform, characterized in that: include: A fault signal receiving module, used to continuously receive the fault signal of the target vehicle through the telematics control unit, and extract the fault code of the component corresponding to the fault signal in the target vehicle and the time of the fault occurrence according to the fault signal; A fault file generation module, used to collect various operating condition data corresponding to the fault code of the component within a specified time range before and after the fault occurs through the telematics control unit, and generate a fault file according to the collected various operating condition data; A file sub-packaging module, used to split the fault file into multiple sub-files according to a preset sub-packaging order through the telematics control unit according to the file size of the fault file and the transmission capacity of the SIM card; A sub-file uploading module, configured to compress each sub-file using a set compression algorithm after naming each sub-file according to the sub-packaging order through the telematics control unit to obtain a plurality of compressed files, and upload each compressed file to the Internet of Vehicles platform in sequence according to the file number in the file name from small to large; Each sub-file contains the number of the telematics control unit and a file sequence number that matches the sub-packaging order, and the sub-file of the last sub-packaging contains special characters.

9. An electronic device, characterized in that: The electronic device comprises: at least one processor; and, a memory communicatively connected to the at least one processor; wherein, The memory stores a computer program executable by the at least one processor, and the computer program is executed by the at least one processor so that the at least one processor can execute a vehicle fault file distributed uploading method according to any one of claims 1-7.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a processor to implement a vehicle fault file distributed uploading method according to any one of claims 1 to 7 when executed.

Images