Vehicle end log management method, electronic equipment and storage medium
Through cloud-driven vehicle-side log collection, sharding processing and security authentication, the problems of inflexible and insufficient security of traditional vehicle-side log transmission are solved, and more secure data transmission and storage are achieved.
Patent Information
- Application Number
- CN202510867052.7
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-06-26
- Publication Date
- 2025-08-15
AI Technical Summary
The traditional method of collecting and transmitting vehicle-side logs limits the flexibility of data transmission, which can easily lead to data loss or damage, and it is difficult to ensure security during transmission, which may lead to data leakage.
Log collection instructions are sent through the cloud, and fragments are packaged based on the acquisition log and preset storage trigger conditions. After completing the security authentication, the fragmented collection log is uploaded to the preset cloud object storage bucket and secondary merged storage is performed in the cloud.
It reduces the risk of loss or damage of the collection log during transmission, improves the security during data transmission, and reduces the risk of data leakage.
Smart Images

Figure CN120498978A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of vehicle management technology, and in particular to a vehicle-side log management method, electronic device, and storage medium. Background Art
[0002] Currently, with the development of communication technology and log management needs, more and more vehicles are beginning to use vehicle-side logs to achieve real-time management and monitoring of various vehicle parameters.
[0003] However, the traditional collection of vehicle-side logs requires a protocol based on a specific interface, and the collection instructions for the test section logs are issued from a specific communication device. This transmission method of a specific log and a specific transmission interface will limit the flexibility of data transmission and may cause data loss or damage during the transmission process. In addition, the transmission, storage, and downloading of vehicle-side logs in the existing technology are all implemented through a single transmission path, which makes it difficult to ensure the security of data during transmission, and in serious cases, it may cause data leakage. Summary of the Invention
[0004] The embodiments of the present application provide a vehicle-side log management method, electronic device and storage medium. The embodiments provided by the present application solve the technical problem in the prior art that data is lost or damaged during transmission, making it difficult to ensure the security of data during transmission, which may cause data leakage in severe cases. The embodiments provided by the present application reduce the risk of loss or damage of collected logs during transmission, improve the security of data during transmission, and reduce the risk of data leakage.
[0005] In a first aspect of an embodiment of the present application, an embodiment of the present application provides a method for managing a vehicle-side log. The method for managing a vehicle-side log is applied to a vehicle side, and the method for managing a vehicle-side log includes:
[0006] Based on the log collection instruction sent by the cloud, collect the log of the vehicle and determine the collected log of the vehicle, wherein the log collection instruction is determined based on the log collection task and the target communication protocol sent by the cloud;
[0007] Based on the collected logs and preset log storage trigger conditions, determining whether the collected logs need to be packaged and fragmented;
[0008] If necessary, after the packaged and fragmented collection logs complete security authentication, each fragmented collection log is uploaded to a preset cloud object storage bucket based on the log storage path issued by the cloud, so that the cloud can perform a secondary merger of each fragmented collection log to complete the storage of the collection log.
[0009] In a feasible implementation manner, the determining whether the collected logs need to be packaged and fragmented based on the collected logs and the preset log storage trigger condition includes:
[0010] Determining whether the data volume of the collected log reaches a preset data volume threshold, and determining whether the collection time of collecting the collected log reaches a preset collection time limit threshold;
[0011] If the data volume reaches the preset data volume threshold and the collection time reaches the preset collection time limit threshold, it is determined that the collection log needs to be packaged and fragmented;
[0012] If the data volume does not reach the preset data volume threshold and / or the collection time does not reach the preset collection limit time threshold, it is determined that there is no need to package and fragment the collection log.
[0013] In a feasible implementation, security authentication is performed on the packaged and fragmented collection logs in the following manner:
[0014] Based on a preset encryption algorithm, data encryption and digital signature are performed on the packaged and fragmented collection log, and a random string and a timestamp are embedded in the packaged and fragmented collection log to complete the security authentication of the packaged and fragmented collection log.
[0015] In a feasible implementation manner, after collecting the vehicle logs based on the log collection instruction sent based on the cloud and determining the collected vehicle logs, the vehicle-side log management method further includes:
[0016] The response status of collecting the collection log is sent to the cloud, so that the cloud determines whether to issue an alarm based on the response status of the collection log.
[0017] In a feasible implementation, after the packaged and fragmented collection logs complete security authentication, each fragmented collection log is uploaded to a preset cloud object storage bucket based on the log storage path issued by the cloud, and after each of the fragmented collection logs is uploaded, each of the fragmented collection logs is merged again to complete the storage of the collection logs. The method further includes:
[0018] The uploaded sliced collection logs are sent to the cloud so as to verify the integrity of each sliced collection log.
[0019] In a second aspect of the embodiments of the present application, the embodiments of the present application provide a method for managing vehicle-side logs, which is applied to the cloud. The method for managing vehicle-side logs includes:
[0020] Determining a target communication protocol corresponding to the vehicle based on vehicle identification information in the vehicle log collection task;
[0021] Determining a log collection instruction corresponding to the vehicle based on the target communication protocol;
[0022] The log collection instruction is sent to the vehicle, so that the vehicle determines the collection log corresponding to the vehicle according to the log collection instruction.
[0023] In a feasible implementation manner, determining the target communication protocol corresponding to the vehicle based on the vehicle identification information in the vehicle log collection task includes:
[0024] Based on the vehicle identification information in the vehicle log collection task, a target communication protocol corresponding to the vehicle that is adapted to the vehicle identification information is determined from a preset identification communication protocol mapping database.
[0025] In a feasible embodiment, the method further includes:
[0026] When receiving each sharded collection log uploaded by the vehicle end to the preset cloud object storage bucket, each sharded collection log is merged twice to complete the storage of the collection log.
[0027] According to a third aspect of the embodiments of the present application, an electronic device is provided, comprising: a processor, a memory, and a bus, wherein the memory stores machine-readable instructions executable by the processor. When the electronic device is running, the processor communicates with the memory through the bus, and the machine-readable instructions are executed by the processor according to the steps of the vehicle-side log management method described in the first aspect or the vehicle-side log management method described in the second aspect.
[0028] In a fourth aspect of the embodiments of the present application, the embodiments of the present application provide a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the steps of the vehicle-side log management method described in the first aspect or the vehicle-side log management method described in the second aspect are executed.
[0029] The vehicle-side log management method, electronic device, and storage medium provided in the embodiments of the present application are compared with the prior art. The embodiments provided in the present application collect vehicle logs based on log collection instructions sent from the cloud, determine the vehicle's collection logs, and then determine whether the collection logs need to be packaged and fragmented based on the collection logs and preset log storage trigger conditions. If necessary, after the packaged and fragmented collection logs complete security authentication, each fragmented collection log is uploaded to a preset cloud object storage bucket based on the log storage path issued by the cloud, so that the cloud performs a secondary merger of each fragmented collection log to complete the storage of the collection logs. The embodiments provided in the present application reduce the risk of loss or damage of the collection logs during transmission, improve the security of data during transmission, and reduce the risk of data leakage. BRIEF DESCRIPTION OF THE DRAWINGS
[0030] Figure 1 A flowchart of a vehicle-side log management method provided in an embodiment of the present application is shown;
[0031] Figure 2 A screenshot of the interface for downloading collected logs in a vehicle-side log management method provided in an embodiment of the present application is shown;
[0032] Figure 3 A flowchart of another vehicle-side log management method provided in an embodiment of the present application is shown;
[0033] Figure 4 A flowchart of updating a vehicle-side log in a vehicle-side log management method provided in an embodiment of the present application is shown;
[0034] Figure 5 A structural block diagram of a vehicle terminal provided in an embodiment of the present application is shown;
[0035] Figure 6 A structural block diagram of a cloud provided by an embodiment of the present application is shown;
[0036] Figure 7 A schematic structural diagram of an electronic device provided in an embodiment of the present application is shown.
[0037] Figures 5 to 7 The corresponding relationship between the reference numerals and the names of the drawings is as follows:
[0038] 500 vehicle side; 510 first determination module; 520 second determination module; 530 first storage module; 600 cloud; 610 third determination module; 620 fourth determination module; 630 fifth determination module; 640 second storage module, 700 electronic device; 710 processor; 720 memory; 730 bus. DETAILED DESCRIPTION
[0039] In order to better understand the technical solutions provided by the embodiments of this specification, the technical solutions of the embodiments of this specification are described in detail below through the accompanying drawings and specific embodiments. It should be understood that the embodiments of this specification and the specific features in the embodiments are detailed descriptions of the technical solutions of the embodiments of this specification, rather than limitations on the technical solutions of this specification. In the absence of conflict, the embodiments of this specification and the technical features in the embodiments can be combined with each other.
[0040] In this article, relational terms such as first and second are used only to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "comprise", "include" or any other variants thereof are intended to cover non-exclusive inclusion, so that the process, method, article or equipment comprising a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or equipment. In the absence of further restrictions, the elements defined by the statement "comprising a ..." do not exclude the presence of other identical elements in the process, method, article or equipment comprising the elements. The term "two or more" includes two or more than two cases.
[0041] First, the application scenarios to which this application is applicable are introduced. The embodiments provided in this application are applicable to the field of vehicle management technology, and in particular, relate to a vehicle-side log management method, electronic device and storage medium.
[0042] At present, the traditional collection of vehicle-side logs requires a protocol based on a specific interface, and the collection instructions for the test section logs are issued from a specific communication device. This transmission method of specific logs and specific transmission interfaces will limit the flexibility of data transmission and may cause data loss or damage during the transmission process. In addition, the transmission, storage, and downloading of vehicle-side logs in the existing technology are all implemented through a single transmission path, which makes it difficult to ensure the security of data during transmission, and in serious cases, it may cause data leakage.
[0043] Based on this, the embodiments of the present application provide a vehicle-side log management method, electronic device and storage medium. The embodiments provided by the present application solve the technical problem in the prior art that data is lost or damaged during transmission, making it difficult to ensure the security of data during transmission, which may cause data leakage in severe cases. The embodiments provided by the present application reduce the risk of loss or damage of collected logs during transmission, improve the security of data during transmission, and reduce the risk of data leakage.
[0044] Figure 1This is a flowchart of a method for managing vehicle-side logs provided in an embodiment of the present application. Figure 1 As shown, Figure 1 The vehicle-side log management method shown is applied to the vehicle side and includes the following steps:
[0045] S101. Collect vehicle logs based on a log collection instruction sent by the cloud, and determine collected logs of the vehicle, wherein the log collection instruction is determined based on the log collection task and the target communication protocol sent by the cloud.
[0046] In this step, the embodiment provided by the present application realizes data interaction through interaction between the vehicle side and the cloud side. When it is necessary to collect or update the vehicle side log, it is first necessary to determine whether the cloud side has sent a log collection instruction. After receiving the log collection instruction sent by the cloud side, the vehicle side controls the on-board software update component (Over-The-Air Technology, OTA) to start collecting the vehicle log and obtain the vehicle collection log.
[0047] S102: Based on the collected logs and preset log storage trigger conditions, determine whether the collected logs need to be packaged and fragmented.
[0048] In this step, in the process of collecting vehicle logs, the embodiment provided by the present application needs to compare the real-time collected vehicle logs in different states with the preset log storage trigger conditions. When it is determined that the collected logs meet the preset log storage trigger conditions, the collected logs are compressed and the compressed collected logs are segmented.
[0049] It can be understood that the packaging and sharding of collected logs in the embodiments provided in this application refers to dividing a large amount of log data into smaller parts (shards), and then storing, transmitting or analyzing these sharded data. This method helps to manage a large amount of log collection logs more efficiently, especially in resource-constrained environments, such as embedded systems in vehicles.
[0050] Exemplarily, based on the collected logs and preset log storage trigger conditions, determining whether the collected logs need to be packaged and fragmented includes:
[0051] Determine whether the data volume of the collected log reaches the preset data volume threshold, and determine whether the collection time of the collected log reaches the preset collection limit time threshold; if the data volume reaches the preset data volume threshold, and the collection time reaches the preset collection limit time threshold, determine that the collected log needs to be packaged and fragmented; if the data volume does not reach the preset data volume threshold and / or the collection time does not reach the preset collection limit time threshold, determine that the collected log does not need to be packaged and fragmented.
[0052] In the above, the preset log storage trigger conditions of the embodiment provided by the present application can be: triggering of a preset data volume threshold and triggering of a preset collection time. After determining the preset log storage trigger conditions, the embodiment provided by the present application starts to package and fragment the collected logs when it is determined that the data volume of the collected logs is greater than or equal to the preset data volume threshold and the collection time of the collected logs reaches the preset collection limit time threshold.
[0053] It is understandable that if either the amount of data in the collection log or the collection time of the collection log does not reach the preset log storage trigger condition, the collection log will not be packaged and fragmented, and the collection log of the vehicle needs to continue to be collected.
[0054] S103. If necessary, after the packaged and fragmented collection logs complete security authentication, upload each fragmented collection log to a preset cloud object storage bucket based on the log storage path issued by the cloud, so that the cloud can perform a secondary merger of each fragmented collection log to complete the storage of the collection log.
[0055] In this step, the embodiment provided by the present application will not directly store the sharded collection logs directly to the cloud after packaging and sharding the collection logs. Instead, it is necessary to perform security authentication on the collection logs, and after the above-mentioned sharded collection logs complete the corresponding security authentication, obtain the log storage path for storing the above-mentioned collection logs, and then store the above-mentioned sharded collection logs in the preset cloud object storage bucket through the log storage path, so that the cloud can subsequently perform a secondary merger of the various sharded collection logs, thereby realizing the storage of the collection logs, and after the above-mentioned collection logs are stored, push notifications in real time to allow operation and maintenance personnel to timely grasp the collection progress of the collection logs.
[0056] It can be understood that the acquisition and storage processes of the collection logs in the embodiments provided in this application are independent of each other and do not interfere with each other, thereby ensuring the security and integrity of the collection log upload link, so that the collection log data is stored in the cloud without being restricted by hardware.
[0057] The embodiment provided in this application modularizes the functions of collecting, storing and transmitting vehicle-side logs into independent sub-processes. The transmission of each sub-process follows a unified interface to ensure that when components are added or replaced according to different needs, the overall operation of the entire vehicle side will not be affected.
[0058] Among them, the preset cloud object storage bucket in the embodiment provided by this application can be customized and used according to different application scenarios and usage conditions. The preset cloud object storage bucket in the embodiment provided by this application can be set to an AWS S3 storage bucket. The setting of the preset cloud object storage bucket can enable the upload of collected logs to not be processed by other intermediate systems, thereby shortening the upload link and improving upload efficiency.
[0059] For example, security authentication is performed on the packaged and fragmented collection logs in the following manner:
[0060] Based on the preset encryption algorithm, the data of the packaged and fragmented collection logs is encrypted and digitally signed, and a random string and timestamp are embedded in the packaged and fragmented collection logs to complete the security authentication of the packaged and fragmented collection logs.
[0061] It should be noted that the preset encryption algorithm of the embodiment provided in this application can be the encryption and signature of the National Secret 2 (SM2). This application uses SM2 to encrypt and digitally sign the collection log after packaging and fragmentation, and embeds a random string, timestamp and signature verification code in the collection log after packaging and fragmentation to complete the security authentication of the collection log after packaging and fragmentation to prevent the risk of data leakage or tampering.
[0062] It can be understood that this application provides a universal interface layer, provides different interface adaptation services for different protocols and hardware, inherits the capabilities of the universal interface layer, automatically registers the log collection service, and then when the log collection task is issued in the cloud, automatically identifies and selects the corresponding interface adaptation layer service to connect to the vehicle side according to different vehicle model protocols.
[0063] Exemplarily, the embodiment provided in the present application collects the vehicle's logs based on the log collection instructions sent from the cloud. After determining the vehicle's collection logs, it can also: send the response status of the collection logs to the cloud so that the cloud can determine whether to issue an alarm based on the response status of the collection logs.
[0064] Exemplarily, the present application may also: send each uploaded sharded collection log to the cloud to verify the integrity of each sharded collection log.
[0065] It should be noted that the embodiment provided in the present application transmits the response status of the collected log or the upload status of the collected log to the cloud in real time during the process of collecting the vehicle log in real time, or after determining the collected log of the vehicle, and the cloud determines in real time whether the alarm threshold condition is triggered and issues an alarm.
[0066] It can be understood that the triggering alarm threshold conditions in the embodiments provided by the present application can be abnormalities in the issuance status of the real-time monitored log collection instructions, abnormalities in the response status of the collection log, abnormalities in the upload status of the collection log or update log, abnormalities in the verification of the integrity of the log file, and abnormalities in applying for file access permissions, deadlines, and download paths after downloading the above-mentioned transmitted collection logs. When an abnormality occurs, the cloud control can issue an alarm, timely notification, and log records.
[0067] In the above, if the user does not have the application file access permission for the collection log, he or she will not be able to download the collection log.
[0068] For example, when the operation and maintenance personnel in the embodiment provided by this application want to download the collected collection logs, they first need to request from the cloud to obtain the log storage path of the above-mentioned collection logs, and then obtain the vehicle's collection logs from the preset cloud object storage bucket based on the obtained log storage path, so that the operation and maintenance personnel can efficiently locate and solve problems in the log collection and storage process, such as the collection frequency of the collection logs, storage space usage, and transmission success rate.
[0069] See also Figure 2 , Figure 2 The following is a screenshot of the interface for downloading and collecting logs in a vehicle-side log management method provided in an embodiment of the present application. Figure 2 As shown, the embodiment provided by the present application prevents users from downloading incomplete or non-compliant collection logs by limiting the click conditions of the log storage path button. The present application provides a copy button and a close button to facilitate users to copy the log storage path and close the pop-up window operation.
[0070] Figure 3 This is a flowchart of another method for managing vehicle-side logs provided in an embodiment of the present application. Figure 3 As shown, the vehicle-side log management method includes the following steps:
[0071] S301: Determine a target communication protocol corresponding to the vehicle based on vehicle identification information in a log collection task of the vehicle.
[0072] In this step, the cloud in the embodiment provided by this application must first determine the log collection task for the vehicle and the vehicle identification information in the log collection task before sending the log collection instruction to the vehicle. Then, based on the external preset identification communication protocol mapping database, it determines the target communication protocol corresponding to the vehicle.
[0073] It can be understood that the log collection task in the embodiment provided in this application includes a log collection strategy, a storage threshold, an alarm rule, and vehicle identification information.
[0074] Exemplarily, determining a target communication protocol corresponding to a vehicle based on vehicle identification information in a vehicle log collection task includes:
[0075] Based on the vehicle identification information in the vehicle log collection task, a target communication protocol corresponding to the vehicle that is adapted to the vehicle identification information is determined from a preset identification communication protocol mapping database.
[0076] In the above, the target communication protocol in the embodiment provided by this application can be customized and used according to different application scenarios and usage environments. The target communication protocol in the embodiment provided by this application can be set to the MQTT protocol and the TCP32960 protocol. This application directly sends tasks from the cloud and obtains collection logs, which invisibly enhances data security and reduces the risk of data leakage.
[0077] S302: Determine the log collection instruction corresponding to the vehicle based on the target communication protocol.
[0078] In this step, after determining the target communication protocol, the embodiment provided by the present application communicates with the vehicle side through the above target communication protocol and sends a corresponding log collection instruction to the vehicle.
[0079] S303: Send the log collection instruction to the vehicle, so that the vehicle determines the collection log corresponding to the vehicle according to the log collection instruction.
[0080] In this step, in the embodiment provided by the present application, after the configured log collection instruction is sent to the vehicle on the cloud, the vehicle determines the collection log corresponding to the vehicle according to the log collection instruction. The vehicle side re-uploads the determined sharded collection logs after sharding back to the cloud. When receiving the sharded collection logs uploaded by the vehicle side to the preset cloud object storage bucket, the cloud side will perform a secondary merger of the sharded collection logs to complete the storage of the collection logs.
[0081] For example, the log collection tasks in the embodiments provided in this application can be managed in the form of a list. The list of log collection tasks is arranged in descending order by creation time by default, so that the latest log collection task is at the top, which is convenient for users to view quickly. At the same time, it supports list expansion to view the collection log corresponding to the log collection task, thereby improving the readability and operability of the information.
[0082] The list of log collection tasks displays comprehensive fields, including key information such as vehicle series, model, and task name. This helps users quickly understand the overview of log collection tasks. The list of log collection tasks is identified by serial number, making it easier for users to locate and find the collection logs for a specific log collection task.
[0083] The embodiment provided in this application can also query the collected logs, and the query method is relatively flexible. This application supports multiple query conditions, including vehicle series, vehicle models, and task names of log collection tasks, etc. Users can perform precise or fuzzy queries according to actual needs.
[0084] The embodiment provided in this application limits the query scope of the collected logs through a drop-down box and a time filter, reducing the possibility of misoperation and improving the accuracy of the query results; and this application can provide query and reset buttons to facilitate users to quickly execute query operations or clear query conditions.
[0085] The embodiment provided by this application can also view the task details of the vehicle's log collection task, and supports viewing the detailed description of the log collection task, including detailed information such as vehicle identification information, to help users gain an in-depth understanding of the execution of the log collection task. This application can also provide copying and deletion of log storage paths, etc., to facilitate users to manage the collected collection logs. Through status query, this application can understand the progress and status of the log collection task in real time, so as to facilitate timely taking of corresponding measures.
[0086] The embodiments provided in this application support querying of collection logs under various conditions, which can meet the different query requirements of users.
[0087] The embodiment provided by this application can also add new processing to the log collection task. It can ensure the integrity and accuracy of the log collection task by requiring the user to fill in the title of the log collection task, log time setting and other key information. This application supports the selection of multiple car series, models and applications to meet the different collection needs of users. This application ensures the legality and validity of the log collection task by verifying whether the vehicle identification information exists and whether it matches the selected car series and model.
[0088] The vehicle-side log management method, electronic device, and storage medium provided in the embodiments of the present application are compared with the prior art. The embodiments provided in the present application collect vehicle logs based on log collection instructions sent from the cloud, determine the vehicle's collection logs, and then determine whether the collection logs need to be packaged and fragmented based on the collection logs and preset log storage trigger conditions. If necessary, after the packaged and fragmented collection logs complete security authentication, each fragmented collection log is uploaded to a preset cloud object storage bucket based on the log storage path issued by the cloud, so that the cloud performs a secondary merger of each fragmented collection log to complete the storage of the collection logs. The embodiments provided in the present application reduce the risk of loss or damage of the collection logs during transmission, improve the security of data during transmission, and reduce the risk of data leakage.
[0089] This application uses an embodiment to illustrate the method of updating the vehicle-side log in the vehicle-side log management method. Figure 4 , Figure 4 The flowchart of updating the vehicle-side log in the vehicle-side log management method provided by the embodiment of the present application is shown. Figure 4 As shown, the process method for updating the vehicle-side log is as follows:
[0090] First, the vehicle generates a unique code logid, calls the tsp interface to obtain the pre-signed address, and uploads the log to the S3 storage bucket through the above pre-signed address.
[0091] Operations and maintenance personnel can view the log download address on this page and copy the address to a browser to access the S3 bucket and download logs.
[0092] Next, the vehicle side performs OTA update. After the vehicle side requests the pre-signed address from TSP, TSP returns the pre-signed address.
[0093] Then, the vehicle uploads the OTA update log to the S3 storage through the pre-signed address.
[0094] Finally, s3 returns the file upload status to tsp.
[0095] Figure 5 The following is a structural block diagram of a vehicle side provided by an embodiment of the present application. Figure 5 As shown, the vehicle end 500 includes:
[0096] The first determining module 510 is configured to collect vehicle logs based on a log collection instruction sent from the cloud, and determine collected logs of the vehicle, wherein the log collection instruction is determined based on a log collection task and a target communication protocol sent from the cloud.
[0097] The second determining module 520 is configured to determine whether the collected logs need to be packaged and fragmented based on the collected logs and preset log storage triggering conditions.
[0098] The first storage module 530 is used to upload each sharded collection log to a preset cloud object storage bucket based on the log storage path issued by the cloud after the collection log is packaged and sharded, if necessary, and after the security authentication is completed, so that the cloud can perform a secondary merger of each sharded collection log to complete the storage of the collection log.
[0099] Exemplarily, the second determining module 520 is specifically configured to:
[0100] Determine whether the data volume of the collected logs reaches a preset data volume threshold, and determine whether the collection time of the collected logs reaches a preset collection time limit threshold.
[0101] If the data volume reaches the preset data volume threshold and the collection time reaches the preset collection limit time threshold, it is determined that the collected logs need to be packaged and fragmented.
[0102] If the data volume does not reach the preset data volume threshold and / or the collection time does not reach the preset collection limit time threshold, it is determined that the collection logs do not need to be packaged and fragmented.
[0103] For example, security authentication is performed on the packaged and fragmented collection logs in the following manner:
[0104] Based on the preset encryption algorithm, the data of the packaged and fragmented collection logs is encrypted and digitally signed, and a random string and timestamp are embedded in the packaged and fragmented collection logs to complete the security authentication of the packaged and fragmented collection logs.
[0105] Exemplarily, the response status of collecting the collection log is sent to the cloud, so that the cloud determines whether to issue an alarm based on the response status of the collection log.
[0106] Exemplarily, each uploaded sharded collection log is sent to the cloud so as to verify the integrity of each sharded collection log.
[0107] Figure 6 The following is a block diagram showing a cloud structure provided by an embodiment of the present application. Figure 6 As shown, the cloud 600 includes:
[0108] The third determining module 610 is configured to determine a target communication protocol corresponding to the vehicle based on the vehicle identification information in the log collection task of the vehicle.
[0109] The fourth determining module 620 is configured to determine a log collection instruction corresponding to the vehicle based on the target communication protocol.
[0110] The fifth determining module 630 is configured to send a log collection instruction to the vehicle, so that the vehicle determines the collection log corresponding to the vehicle according to the log collection instruction.
[0111] The second storage module 640 is used to perform a secondary merger on each sharded collection log when receiving each sharded collection log uploaded by the vehicle end to the preset cloud object storage bucket to complete the storage of the collection log.
[0112] Exemplarily, the third determining module 610 is specifically configured to:
[0113] Based on the vehicle identification information in the vehicle log collection task, a target communication protocol corresponding to the vehicle that is adapted to the vehicle identification information is determined from a preset identification communication protocol mapping database.
[0114] See also Figure 7 , Figure 7 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application is shown in FIG. Figure 7 As shown, electronic device 700 includes a processor 710 , a memory 720 , and a bus 730 .
[0115] The memory 720 stores machine-readable instructions executable by the processor 710. When the electronic device 700 is running, the processor 710 communicates with the memory 720 via the bus 730. When the machine-readable instructions are executed by the processor 710, the above-mentioned Figures 1 to 2 The vehicle-side log management method in the embodiment of the method shown or Figure 3 The steps of the vehicle-side log management method in the method embodiment shown are specifically implemented in accordance with the method embodiment and will not be described in detail here.
[0116] The embodiment of the present application also provides a computer-readable storage medium on which a computer program is stored. When the computer program is executed by a processor, the computer program can execute the above-mentioned Figures 1 to 2 The vehicle-side log management method in the embodiment of the method shown or Figure 3 The steps of the vehicle-side log management method in the method embodiment shown are specifically implemented in accordance with the method embodiment and will not be described in detail here.
[0117] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.
[0118] It should be noted that, in the above embodiments, the description of each embodiment has its own focus. For parts that are not described in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.
[0119] Those skilled in the art will appreciate that the embodiments of the present application can be provided as methods, systems, or computer program products. Therefore, the present application can adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application can adopt the form of a computer program product implemented on one or more computer-readable storage media (including but not limited to magnetic disk storage, CD-ROM, optical storage, etc.) that contain computer-readable program code.
[0120] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded computer, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 a process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.
[0121] These computer program instructions may also be stored in a computer readable memory that can direct a computer or other programmable data processing device to work in a specific manner, so that the instructions stored in the computer readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 a process or multiple processes and / or boxes Figure 1 The function specified in one or more boxes.
[0122] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operational steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing the instructions executed on the computer or other programmable device for implementing the process. Figure 1 a process or multiple processes and / or boxes Figure 1 A step that specifies a function in one or more boxes.
[0123] An embodiment of the present application also provides a computer program product, which includes computer software instructions. When the computer software instructions are executed on a processing device, the processing device executes the process of the vehicle-side log management method.
[0124] A computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function according to the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from one website, computer, server or data center to another website, computer, server or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium can be any available medium that a computer can store or a data storage device such as a server or data center that includes one or more available media integrated. The available medium can be a magnetic medium (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid state drive (SSD)).
[0125] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.
[0126] In the several embodiments provided in this application, it should be understood that the disclosed devices, apparatuses and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interface, device or unit, which can be electrical, mechanical or other forms.
[0127] Units described as separate components may or may not be physically separate, and components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.
[0128] In addition, the functional units in the various embodiments of the present application may be integrated into a single processing unit, or each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or software functional units.
[0129] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions for enabling a computer device (which can be a personal computer, server, or network device, etc.) to execute all or part of the steps of the various embodiments 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.
[0130] The above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. However, these modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present application.
[0131] Although the preferred embodiments of this specification have been described, those skilled in the art may make additional changes and modifications to these embodiments once they have learned the basic creative concepts. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments and all changes and modifications that fall within the scope of this specification.
[0132] Obviously, those skilled in the art may make various changes and modifications to this specification without departing from the spirit and scope of this specification. Thus, if such changes and modifications fall within the scope of the claims of this specification and their equivalents, this specification is intended to include such changes and modifications.
Claims
1. A vehicle-side log management method, applied to the vehicle side, characterized in that: The vehicle-side log management method includes: Based on the log collection instruction sent by the cloud, collect the log of the vehicle and determine the collected log of the vehicle, wherein the log collection instruction is determined based on the log collection task and the target communication protocol sent by the cloud; Based on the collected logs and preset log storage trigger conditions, determining whether the collected logs need to be packaged and fragmented; If necessary, after the packaged and fragmented collection logs complete security authentication, each fragmented collection log is uploaded to a preset cloud object storage bucket based on the log storage path issued by the cloud, so that the cloud can perform a secondary merger of each fragmented collection log to complete the storage of the collection log.
2. The vehicle-side log management method according to claim 1, characterized in that: The determining whether the collected logs need to be packaged and fragmented based on the collected logs and the preset log storage trigger condition includes: Determining whether the data volume of the collected log reaches a preset data volume threshold, and determining whether the collection time of collecting the collected log reaches a preset collection time limit threshold; If the data volume reaches the preset data volume threshold and the collection time reaches the preset collection time limit threshold, it is determined that the collection log needs to be packaged and fragmented; If the data volume does not reach the preset data volume threshold and / or the collection time does not reach the preset collection limit time threshold, it is determined that there is no need to package and fragment the collection log.
3. The vehicle-side log management method according to claim 1, characterized in that: The security authentication of the collected logs after packaging and fragmentation is performed in the following ways: Based on a preset encryption algorithm, data encryption and digital signature are performed on the packaged and fragmented collection log, and a random string and a timestamp are embedded in the packaged and fragmented collection log to complete the security authentication of the packaged and fragmented collection log.
4. The vehicle-side log management method according to claim 1, characterized in that: After collecting the vehicle logs based on the log collection instruction sent from the cloud and determining the collected vehicle logs, the vehicle-side log management method further includes: The response status of collecting the collection log is sent to the cloud, so that the cloud determines whether to issue an alarm based on the response status of the collection log.
5. The vehicle-side log management method according to claim 1, characterized in that: After the packaged and fragmented collection logs complete security authentication, each fragmented collection log is uploaded to a preset cloud object storage bucket based on the log storage path issued by the cloud. When each fragmented collection log is uploaded, each fragmented collection log is merged again to complete the storage of the collection log. The method further includes: The uploaded sliced collection logs are sent to the cloud so as to verify the integrity of each sliced collection log.
6. A vehicle-side log management method, applied to the cloud, characterized in that: The vehicle-side log management method includes: Determining a target communication protocol corresponding to the vehicle based on vehicle identification information in the vehicle log collection task; Determining a log collection instruction corresponding to the vehicle based on the target communication protocol; The log collection instruction is sent to the vehicle, so that the vehicle determines the collection log corresponding to the vehicle according to the log collection instruction.
7. The vehicle-side log management method according to claim 6, characterized in that: The step of determining a target communication protocol corresponding to the vehicle based on the vehicle identification information in the vehicle log collection task includes: Based on the vehicle identification information in the vehicle log collection task, a target communication protocol corresponding to the vehicle that is adapted to the vehicle identification information is determined from a preset identification communication protocol mapping database.
8. The vehicle-side log management method according to claim 6, characterized in that: The method further comprises: When receiving each sharded collection log uploaded by the vehicle end to the preset cloud object storage bucket, each sharded collection log is merged twice to complete the storage of the collection log.
9. An electronic device, characterized in that: include: A processor, a memory and a bus, wherein the memory stores machine-readable instructions executable by the processor. When the electronic device is running, the processor and the memory communicate through the bus, and the machine-readable instructions are executed by the processor when running, such as the steps of the vehicle-side log management method described in any one of claims 1-5 or the vehicle-side log management method described in any one of claims 6-8.
10. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a computer program, and when the computer program is executed by the processor, the computer program executes the steps of the vehicle-side log management method according to any one of claims 1 to 5 or the vehicle-side log management method according to any one of claims 6 to 8.
Citation Information
Cited By
Log processing method, electronic equipment, intelligent agent, storage medium and program product
CN121682634A