Vehicle end data processing method and device, equipment and storage medium

By deduplication and time period deduplication of the original CAN message received by the vehicle end, and signal acquisition is carried out under task priority management, the problem of repeated redundant data and resource consumption in vehicle end data processing is solved, and processing efficiency is improved.

CN119520415APending Publication Date: 2025-02-25DONGFENG MOTOR CO LTD DONGFENG NISSAN PASSENGER VEHICLE CO
View PDF 0 Cites 1 Cited by

Patent Information

Application Number
CN202411543041.5
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-10-31
Publication Date
2025-02-25

AI Technical Summary

Technical Problem

In the prior art, during the data transmission process between the vehicle terminal and the cloud terminal, data deduplication operation is complicated, resulting in more duplicate and redundant data, increasing resource consumption, and affecting the data processing efficiency of the vehicle terminal.

Method used

By deduplication of the received original CAN message, avoiding repeated parsing of the same data, and deduplication of the collected data period before uploading the data, uploading only data within different time periods, reducing duplicate redundant data, setting priority between tasks, and signal acquisition is performed according to priority.

Benefits of technology

Reduces duplicate redundant data, reduces vehicle-side resource consumption, improves data processing efficiency, and prevents the vehicle from entering a high load state.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119520415A_ABST
    Figure CN119520415A_ABST
Patent Text Reader

Abstract

The invention discloses a vehicle end data processing method and device, equipment and a storage medium, and relates to the technical field of vehicle end data processing, and the method comprises the steps: carrying out the data deduplication of an original CAN message of a target vehicle, and obtaining a to-be-analyzed CAN message; determining a current starting task based on the priority of the signal acquisition task; based on the rule information of the current starting task, determining a target vehicle signal in the analyzed vehicle signals corresponding to the CAN message to be analyzed, and collecting the target vehicle signal; and uploading the signal data acquired in the de-duplication acquisition time period to a cloud. Through the above mode, the received original CAN message is subjected to de-duplication, and the data acquisition time period is subjected to de-duplication before data uploading, so that repeated data uploading is avoided, repeated redundant data is reduced, vehicle end resource consumption is reduced, the priority is set between tasks, signal acquisition is performed according to the priority, the vehicle end is prevented from entering a high-load state, and the reliability of the vehicle end is improved. The treatment efficiency is improved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the technical field of vehicle-side data processing, and in particular to vehicle-side data processing methods, devices, equipment and storage media. Background Art

[0002] At present, in the process of data transmission between the vehicle and the cloud, data deduplication operations usually use SQL (Structured Query Language) to screen and process relevant data. Due to the complexity of writing SQL statements, deduplication is not considered comprehensively enough, and there will still be duplicate and redundant data. When processing this data, resource consumption will increase. Once multiple collection tasks are run, the vehicle is prone to enter a high-load state, affecting the data processing efficiency of the vehicle.

[0003] The above contents are only used to assist in understanding the technical solution of the present invention and do not constitute an admission that the above contents are prior art. Summary of the invention

[0004] The main purpose of this application is to provide a vehicle-side data processing method, device, equipment and storage medium, aiming to solve the technical problems in the prior art that there is a large amount of duplicate and redundant data, which increases resource consumption and affects the efficiency of vehicle-side data processing.

[0005] To achieve the above objectives, the present application provides a vehicle-side data processing method, the method comprising:

[0006] De-duplicate the original CAN message of the target vehicle to obtain the CAN message to be parsed;

[0007] Based on the priority of the signal acquisition task, determine the current startup task;

[0008] Based on the rule information of the current startup task, determine the target vehicle signal in the parsed vehicle signal corresponding to the CAN message to be parsed, and collect the target vehicle signal;

[0009] The signal data collected during the deduplication collection period is uploaded to the cloud.

[0010] In one embodiment, the step of deduplicating the original CAN message of the target vehicle includes:

[0011] Filter out duplicate data frames in the original CAN message and delete the duplicate data frames;

[0012] Based on the identification information and time sequence information of the original CAN message, the latest CAN message corresponding to the same identification information within a preset time period is determined, and the original CAN messages except the latest CAN message are deleted.

[0013] In one embodiment, before the step of performing data deduplication on the original CAN message of the target vehicle to obtain the CAN message to be parsed, the step further includes:

[0014] When receiving the original CAN message of the target vehicle, adding corresponding time sequence information to the original CAN message of the target vehicle based on the arrival order of the original CAN message;

[0015] After the step of performing data deduplication on the original CAN message of the target vehicle to obtain the CAN message to be parsed, the following steps are further included:

[0016] Obtain the timestamp information of the CAN message to be parsed, and add the timestamp information to the corresponding CAN message to be parsed.

[0017] In one embodiment, when receiving the original CAN message of the target vehicle, the step of adding corresponding time sequence information to the original CAN message of the target vehicle based on the arrival order of the original CAN message includes:

[0018] When receiving the original CAN message of the target vehicle, based on the arrival order of the original CAN message, the original CAN message is counted to obtain a counting sequence of the original CAN message;

[0019] The count sequence of the original CAN message is added to the corresponding original CAN message as time sequence information.

[0020] In one embodiment, the step of determining the currently started task based on the priority of the signal acquisition task includes:

[0021] Acquiring resource consumption data of the target vehicle, and determining whether the target vehicle is in a high-load state based on the resource consumption data;

[0022] When the target vehicle is in a high-load state, determining a low-priority startup task based on the running state and priority of the signal acquisition task;

[0023] Based on the ranking value of the low-priority startup task, determine a target stop task among the low-priority startup tasks, and adjust the running state of the target stop task to a stop state;

[0024] The signal acquisition task whose running state is the startup state is used as the current startup task.

[0025] In one embodiment, after the step of obtaining the resource consumption data of the target vehicle and determining whether the target vehicle is in a high-load state based on the resource consumption data, the step further includes:

[0026] When the target vehicle is not in a high-load state and has abundant resources, determining a high-priority stop task based on the running state and priority of the signal acquisition task;

[0027] Based on the ranking value of the high priority stop task, determine a target start task in the high priority stop task, and adjust the running state of the target start task to a start state;

[0028] The signal acquisition task whose running state is the startup state is used as the current startup task.

[0029] In one embodiment, before the step of uploading the signal data collected during the deduplication collection time period to the cloud, the step further includes:

[0030] Determining a collection time period of the target vehicle signal based on rule information corresponding to the current startup task of the target vehicle signal;

[0031] Determining a repetition time period based on a collection time period of the target vehicle signal;

[0032] The repeated time periods in the collection time periods are deleted to obtain the de-duplicated collection time periods.

[0033] In addition, to achieve the above purpose, the present application also proposes a vehicle-side data processing device, which includes:

[0034] The data access module is used to deduplicate the original CAN message of the target vehicle and obtain the CAN message to be parsed;

[0035] The task management module is used to determine the current startup task based on the priority of the signal acquisition task;

[0036] The signal acquisition module is further used to determine the target vehicle signal in the parsed vehicle signal corresponding to the CAN message to be parsed based on the rule information of the current startup task, and to collect the target vehicle signal;

[0037] The data upload module is used to upload the signal data collected during the deduplication collection period to the cloud.

[0038] In addition, to achieve the above-mentioned purpose, the present application also proposes a vehicle-side data processing device, which includes: a memory, a processor, and a computer program stored in the memory and executable on the processor, and the computer program is configured to implement the steps of the vehicle-side data processing method as described above.

[0039] In addition, to achieve the above-mentioned purpose, the present invention also proposes a storage medium, which is a computer-readable storage medium. A computer program is stored on the storage medium. When the computer program is executed by a processor, the steps of the vehicle-side data processing method as described above are implemented.

[0040] In addition, to achieve the above-mentioned purpose, the present application also provides a computer program product, which includes a computer program, and when the computer program is executed by a processor, it implements the steps of the vehicle-side data processing method as described above.

[0041] The present application provides a vehicle-side data processing method, which deduplicates the original CAN message of the target vehicle to obtain the CAN message to be parsed; determines the current startup task based on the priority of the signal acquisition task; determines the target vehicle signal in the parsed vehicle signal corresponding to the CAN message to be parsed based on the rule information of the current startup task, and collects the target vehicle signal; uploads the signal data collected during the deduplication collection time period to the cloud. The present application deduplicates the received original CAN message to avoid repeated parsing of the same data, and deduplicates the time period of the collected data before uploading the data, only uploading data in different time periods, avoiding repeated uploading of data, reducing duplicate and redundant data, and reducing vehicle-side resource consumption. At the same time, priorities are set between tasks, and signal acquisition is performed according to the priority to avoid the vehicle-side from entering a high-load state, improve processing efficiency, and solve the technical problems of a large amount of duplicate and redundant data, increased resource consumption, and affecting the vehicle-side data processing efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0042] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.

[0043] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.

[0044] Figure 1 This is a flow chart of the first embodiment of the vehicle-side data processing method of the present application;

[0045] Figure 2 A schematic diagram of deduplication of the collection time period of the vehicle-side data processing method provided in the first embodiment of the present application;

[0046] Figure 3 This is a flow chart of the second embodiment of the vehicle-side data processing method of the present application;

[0047] Figure 4A schematic diagram of the message data format of the vehicle-side data processing method provided in Example 1 of the present application;

[0048] Figure 5 This is a flow chart of Embodiment 3 of the vehicle-side data processing method of the present application;

[0049] Figure 6 A priority diagram of the vehicle-side data processing method provided in Embodiment 3 of the present application;

[0050] Figure 7 This is a flow chart of the fourth embodiment of the vehicle-side data processing method of the present application;

[0051] Figure 8 A schematic diagram of the priority management process of the vehicle-side data processing method provided in the fourth embodiment of the present application;

[0052] Fig. 9 A brief flowchart of the vehicle-side data processing method provided in the fourth embodiment of the present application;

[0053] Fig.10 This is a schematic diagram of the module structure of the vehicle-side data processing device according to an embodiment of the present application;

[0054] Fig.11 This is a schematic diagram of the device structure of the hardware operating environment involved in the vehicle-side data processing method in the embodiment of the present application.

[0055] The realization of the purpose, functional features and advantages of this application will be further explained in conjunction with embodiments and with reference to the accompanying drawings. DETAILED DESCRIPTION

[0056] It should be understood that the specific embodiments described herein are only used to explain the technical solutions of the present application and are not used to limit the present application.

[0057] In order to better understand the technical solution of the present application, a detailed description will be given below in conjunction with the accompanying drawings and specific implementation methods.

[0058] The main solution of the embodiment of the present application is: to deduplicate the original CAN message of the target vehicle to obtain the CAN message to be parsed; to determine the current startup task based on the priority of the signal acquisition task; to determine the target vehicle signal in the parsed vehicle signal corresponding to the CAN message to be parsed based on the rule information of the current startup task, and to collect the target vehicle signal; and to upload the signal data collected during the deduplication collection time period to the cloud.

[0059] At present, in the process of data transmission between the vehicle and the cloud, data deduplication operations usually use SQL to screen and process related data. Due to the complexity of writing SQL statements, deduplication is not considered comprehensively enough, and duplicate and redundant data will still exist. When processing this data, resource consumption will increase. Once multiple collection tasks are run, the vehicle is prone to enter a high-load state, affecting the data processing efficiency of the vehicle.

[0060] The present application provides a solution to deduplicate the received original CAN messages to avoid repeated parsing of the same data, and to deduplicate the time period of data collection before uploading the data. Only data within different time periods can be uploaded to avoid repeated uploading of data, reduce duplicate and redundant data, and reduce vehicle-side resource consumption. At the same time, priorities are set between tasks, and signals are collected according to the priorities to avoid the vehicle-side entering a high-load state, improve processing efficiency, and solve the technical problems of a large amount of duplicate and redundant data, increased resource consumption, and affecting the vehicle-side data processing efficiency.

[0061] It should be noted that the execution subject of this embodiment may be a vehicle-side data processing device capable of realizing the above functions, and this embodiment does not specifically limit this. The following takes the vehicle-side data processing device as an example to illustrate this embodiment and the following embodiments.

[0062] The present application embodiment provides a vehicle-side data processing method, referring to Figure 1 , Figure 1 This is a flow chart of the first embodiment of the vehicle-side data processing method of the present application.

[0063] In this embodiment, the vehicle-side data processing method includes steps S10 to S40:

[0064] Step S10, deduplication of the original CAN message of the target vehicle is performed to obtain the CAN message to be parsed;

[0065] It should be noted that the target vehicle is the vehicle currently undergoing data processing. The original CAN (Controller Area Network) message, that is, the original CAN message received, is usually transmitted by the various components of the target vehicle to the vehicle-side data processing device of the target vehicle through the CAN bus. The original CAN message usually contains the data / information that the vehicle-side data processing device needs to obtain, such as: vehicle signals, which are not specifically limited. This embodiment is explained using vehicle signals as an example. Vehicle signals are related parameter information fed back by various components of the vehicle, such as: speed, battery status, door status, light status, etc., which are not specifically limited. After receiving the original CAN message, the vehicle-side data processing device parses it to obtain these vehicle signals.

[0066] In addition, it should be noted that after the vehicle signal is parsed, it is necessary to collect the signal according to the task issued by the cloud, and upload the corresponding signal data to the cloud. During the data transmission process between the vehicle side (the vehicle-side data processing device of the target vehicle) and the cloud, the data deduplication operation usually uses SQL to perform relevant data screening and processing, which cannot perform deduplication operations when receiving the original CAN message, which will lead to an increase in duplicate and redundant data, increase resource consumption, and the vehicle is prone to enter a high-load state, affecting the data processing efficiency of the vehicle side. Therefore, this embodiment performs data deduplication when receiving the original CAN message to reduce duplicate and redundant data, reduce resource consumption, and improve vehicle-side data processing efficiency.

[0067] It can be understood that the CAN message to be parsed is the CAN message obtained after deduplication.

[0068] In a feasible implementation manner, the step of deduplicating the original CAN message of the target vehicle may include steps S101 to S102:

[0069] Step S101, filtering out duplicate data frames in the original CAN message and deleting the duplicate data frames;

[0070] It should be noted that a duplicate data frame is a duplicate data frame in the original CAN message, that is, the same data frame in the original CAN message, and the duplicate data frame needs to be deleted to reduce data redundancy. Exemplarily, in the forwarded data message, the RX (Receive) data frame and the TX (Transmit) data frame are the same. If the original CAN message contains both the RX data frame and the TX data frame, it can be considered that the RX data frame is a duplicate data frame relative to the TX data frame, and the TX data frame is a duplicate data frame relative to the RX data frame. At this time, the TX data frame can be deleted as a duplicate data frame and the RX data frame can be retained, or the RX data frame can be deleted as a duplicate data frame and the TX data frame can be retained.

[0071] Step S102, based on the identification information and time sequence information of the original CAN message, determine the latest CAN message corresponding to the same identification information within a preset time period, and delete the original CAN messages except the latest CAN message.

[0072] It should be noted that different CAN messages are usually distinguished by identification information, which may be an ID (Identity Document), namely a CAN ID, which is not specifically limited. This embodiment uses a CAN ID as an example for illustration. The identification information of the original CAN message is the CAN ID of the original CAN message.

[0073] It is understandable that the vehicle-side data processing device may receive messages from the same CAN ID within a period of time. If each received message is parsed, unnecessary resource consumption will increase. Therefore, the latest message can be retained, and other messages can be deleted to deduplicate the data corresponding to the CAN ID.

[0074] In addition, it should be noted that the time sequence information is information that can indicate the time sequence of the original CAN message arrival, such as: timestamp, which is not specifically limited. The preset time period is the period set to retain the latest message, which is usually not too long and can ensure processing efficiency while deduplication, such as: 10ms, which is not specifically limited. The latest CAN message is the latest received / arrived original CAN message, and the latest CAN message corresponding to the same identification information within the preset time period is the latest original CAN message from the same CAN ID within the preset time period.

[0075] It should be understood that the latest original CAN message from the same CAN ID within the preset time period is retained, and the remaining original CAN messages are deleted. After deduplication of the data frames in the original CAN message and deduplication of the data corresponding to the CAN ID, the CAN message to be parsed can be obtained.

[0076] Step S20, determining the current startup task based on the priority of the signal acquisition task;

[0077] It should be noted that the signal acquisition task is a task issued by the cloud to collect the required signals. The signal acquisition task at least includes the basic information of the task and the initial startup state. The basic information of the task is the specific content of the signal acquisition task, including at least the accessed stream information and rule information. The accessed stream information is the stream accessed when collecting signals, and the rule information is the rules to be followed for collecting signals. The basic information of the task is usually in the form of SQL statements. For example, the basic information of the signal acquisition task A is: select a,b from 100ms_stream where c>0, that is, access data from the stream named 100ms_stream, and the collection rule is: when c>0, collect a signal and b signal. The initial startup state is whether the controller is started immediately when it receives the signal acquisition task. If so, the signal acquisition task needs to be started immediately. If not, the signal acquisition task is started later.

[0078] In addition, it should be noted that all received signal acquisition tasks will form a list, namely the task list, and the vehicle-side data processing device will mark the running status of each signal acquisition task in the task list. The running status of the signal acquisition task includes two states, the start state and the stop state (pause state). If the signal acquisition task is in the start state, it means that the signal acquisition task is running, and if the signal acquisition task is in the stop state, it means that the signal acquisition task is not running.

[0079] It is understandable that the vehicle-side data processing device will perform signal acquisition according to the signal acquisition task whose running state is the start state. The more signal acquisition tasks there are, the greater the resource consumption of the vehicle-side. It can be seen that in the case of data redundancy, once multiple acquisition tasks are run, the vehicle is prone to enter a high-load state, affecting the data processing efficiency of the vehicle-side, and also affecting the realization of the vehicle-side functions. Therefore, this embodiment sets corresponding priorities for all signal acquisition tasks, and decides which tasks are started or stopped according to the priorities of the signal acquisition tasks to avoid the vehicle-side from entering a high-load state.

[0080] It should be understood that the currently started task, i.e., the signal acquisition task that needs to be run currently, has been adjusted accordingly according to the priority of the signal acquisition task. The priority of the signal acquisition task can generally be divided into high priority, medium priority, and low priority, and the corresponding signal acquisition tasks are high priority tasks, medium priority tasks, and low priority tasks. Generally speaking, the tasks that need to be stopped will be decided in the low priority task / medium priority task, and the tasks that need to be started will be decided in the medium priority / high priority task.

[0081] Step S30, based on the rule information of the current startup task, determining the target vehicle signal in the parsed vehicle signal corresponding to the CAN message to be parsed, and collecting the target vehicle signal;

[0082] It should be noted that the target vehicle signal, i.e., the signal to be collected contained in the analyzed vehicle signal, can be determined according to the rule information of the current startup task. For example, assuming that the rule information of the current startup task B is: when c>0, collect a signal and b signal, then the signals to be collected by the current startup task B are a signal and b signal.

[0083] It can be understood that after the vehicle signal is analyzed and obtained, the target vehicle signal and the value of the target vehicle signal are collected.

[0084] Step S40, uploading the signal data collected during the deduplication collection time period to the cloud.

[0085] It should be noted that different collection rules may trigger repeated collection time periods (time periods for collecting target vehicle signals), and data in the same collection time period is usually stored in the same file. It can be seen that when uploading data to the cloud, it is very likely that the same data will be uploaded repeatedly. Figure 2 , rule1 and rule2 are collection rule 1 and collection rule 2 respectively. The collection time period triggered by collection rule 1 is [t0, t2], and the collection time period triggered by collection rule 2 is [t1, t3]. If the data collected at [t0, t2] and [t1, t3] are uploaded to the cloud, the data collected at [t1, t2] will be uploaded repeatedly. Therefore, it is necessary to deduplicate the collection time period.

[0086] In a feasible implementation, the step of determining a deduplicated collection time period may include: determining the collection time period of the target vehicle signal based on the rule information corresponding to the current startup task of the target vehicle signal; determining a repeated time period based on the collection time period of the target vehicle signal; and deleting the repeated time period in the collection time period to obtain the deduplicated collection time period.

[0087] It should be noted that the repeated time period is the time period in which repeated data are collected, and the deduplicated collection time period is the collection time period after deduplication. For example, Figure 2 In the figure, [t1, t2] is the repeated time period, and [t0, t2] and [t2, t3] are the deduplication collection time periods.

[0088] It can be understood that according to the rule information of the currently started task, the collection time period of each currently started task can be determined, so as to find the repeated time period, delete the repeated time period in the collection time period, and then determine the deduplication collection time period, and upload the cached files in the deduplication collection time period to the cloud.

[0089] This embodiment provides a vehicle-side data processing method, which deduplicates the original CAN message of the target vehicle to obtain the CAN message to be parsed; determines the current startup task based on the priority of the signal acquisition task; determines the target vehicle signal in the parsed vehicle signal corresponding to the CAN message to be parsed based on the rule information of the current startup task, and collects the target vehicle signal; uploads the signal data collected during the deduplication collection time period to the cloud. Deduplication is performed on the received original CAN message to avoid repeated parsing of the same data, and the time period of the collected data is deduplicated before uploading the data. Only data in different time periods is uploaded to avoid repeated uploading of data, reduce duplicate and redundant data, and reduce vehicle-side resource consumption. At the same time, priorities are set between tasks, and signal collection is performed according to the priority to avoid the vehicle-side entering a high-load state and improve processing efficiency.

[0090] Based on the first embodiment of the present application, in the second embodiment of the present application, the same or similar contents as those in the above-mentioned embodiment 1 can refer to the above introduction, and will not be repeated later. Figure 3 , step S01 may be included before step S10:

[0091] Step S01, when the original CAN message of the target vehicle is received, based on the arrival order of the original CAN message, corresponding time sequence information is added to the original CAN message of the target vehicle.

[0092] It should be noted that the arrival order of the original CAN messages is the order in which the original CAN messages arrive at the vehicle-side data processing device. The time sequence information of the original CAN messages is set according to the arrival order of the original CAN messages.

[0093] In a feasible implementation, step S01 may include: when receiving the original CAN message of the target vehicle, based on the arrival order of the original CAN message, counting the original CAN message to obtain the counting sequence of the original CAN message; adding the counting sequence of the original CAN message as time sequence information to the corresponding original CAN message.

[0094] It should be noted that the network connection may be unstable during the driving process of the vehicle, especially in remote areas or places with weak network signals, which will affect the timing and integrity of data upload. Generally, a timestamp obtained by synchronization between the vehicle end and the background is added to the data. However, due to the existence of clock drift and network delay, this timestamp may have the problem of time inversion, resulting in the inaccuracy of the timestamp on the data. That is, when the vehicle end and the background perform time synchronization, the network delay may cause the transmission of time information to lag, so that the time sequence information received by the vehicle end is not the latest. Even if the vehicle end has synchronized the time, due to the existence of network delay, the time data actually used may still be old. Therefore, this embodiment counts according to the arrival order of the original CAN message, forms a corresponding counting sequence as time sequence information and adds it to the original CAN message to further ensure the accuracy of the time sequence information.

[0095] It is understandable that the counting sequence can adopt a self-increasing sequence. The self-increasing sequence is a sequence marked by a hardware counter. It does not rely on the accuracy of the machine's clock, but generates a sequence based on the relative time of each message arrival. This sequence can ensure the timing of the data, but the self-increasing sequence itself cannot reflect the true timeliness of the data. Every time a new CAN message is received, the self-increasing sequence is increased by "1". When the self-increasing sequence is full, it will go back and count again. When the CCM (Chassis Control Module) is powered on again and awakened from sleep, the self-increasing sequence will also count again. When the self-increasing sequence is full, it will start counting from the beginning. Therefore, when a large self-increasing sequence is followed by a small self-increasing sequence, it can be known that the counting has started again, that is, the subsequent data will arrive later.

[0096] Step S10 may include step S11:

[0097] Step S11, obtaining the timestamp information of the CAN message to be parsed, and adding the timestamp information into the corresponding CAN message to be parsed.

[0098] It can be understood that the timestamp information is the timestamp obtained by the synchronization background, and the corresponding timestamp information is added to the CAN message to be parsed. The data format of the final CAN message to be parsed can be referred to Figure 4 , based on the information it contains, it adds a self-increasing sequence and timestamp.

[0099] It should be understood that the timestamp obtained by the synchronization background plus the self-increasing sequence can effectively ensure the timing of receiving messages and will not cause incorrect time sequence information due to problems such as network delays.

[0100] This embodiment provides a vehicle-side data processing method, which adds a timestamp obtained by the synchronization background and a self-increment sequence marked by a hardware counter to the CAN message to ensure the timing of the received message, so that the latest CAN message can be accurately determined and the accuracy of deduplication can be guaranteed.

[0101] Based on the above embodiments of the present application, in the third embodiment of the present application, the same or similar contents as those in the above embodiments can be referred to the above introduction, and will not be described in detail later. Figure 5 , step S20 may include steps S201 to S204:

[0102] Step S201, obtaining resource consumption data of the target vehicle, and judging whether the target vehicle is in a high-load state based on the resource consumption data;

[0103] It should be noted that the resource consumption data is data that can reflect the resource consumption of the target vehicle. If the resource consumption is high, it means that the target vehicle is in a high-load state. If the resource consumption is low, it means that the target vehicle is not in a high-load state.

[0104] Step S202, when the target vehicle is in a high-load state, determining a low-priority startup task based on the running state and priority of the signal acquisition task;

[0105] It should be noted that the priority of signal acquisition tasks can usually be divided into high priority, medium priority and low priority, and the corresponding signal acquisition tasks are high priority tasks, medium priority tasks and low priority tasks. The attributes of signal acquisition tasks at different levels are inconsistent. For example, high-level tasks: once triggered to run on the vehicle side, they are not allowed to be stopped; medium-level tasks: can be stopped and started on the vehicle side according to resource conditions; low-level tasks: once stopped due to priority management when running on the vehicle side, they are not allowed to be started again.

[0106] In addition, it should be noted that, in order to determine the priority between signal acquisition tasks of the same level, this embodiment sets a ranking value of 0-99, and the larger the ranking value, the lower the priority. Figure 6 Task 1, Task 2, and Task 3 are high-level tasks, Task 4, Task 5, and Task 6 are medium-level tasks, and Task 4, Task 5, and Task 6 have different ranking values ​​in the medium-level tasks, which are 3, 2, and 1 respectively. Task 7, Task 8, and Task 9 are low-level tasks, and Task 7, Task 8, and Task 9 have different ranking values ​​in the low-level tasks, which are 4, 3, and 2 respectively.

[0107] It is understandable that a low priority startup task is a signal acquisition task with a lower priority, a startup state, and can be stopped. In this embodiment, a high priority task cannot be stopped, so a medium-level task and a low-level task with a startup state can be used as a low priority startup task.

[0108] It should be understood that when the target vehicle is in a high-load state, it is necessary to reduce the running tasks and select low-priority startup tasks so as to subsequently determine the signal acquisition tasks that need to be stopped.

[0109] Step S203, based on the ranking value of the low-priority startup task, determining a target stop task in the low-priority startup task, and adjusting the running state of the target stop task to a stop state;

[0110] It should be noted that the target stop task is the signal acquisition task that needs to be stopped. According to the ranking value of the low priority start task, the lowest priority low priority start task is found as the target stop task, and the running state of the target stop task will be adjusted to the stop state.

[0111] It is understandable that if the target vehicle is still in a high-load state after stopping a task, a new target stop task can be determined from the remaining low-priority start tasks, and the running state of the new target stop task can be adjusted to the stop state, and so on, until there is no task to stop, or the target vehicle is no longer in a high-load state.

[0112] For example, reference Figure 6 , assuming that tasks 1 to 9 are all running, and the target vehicle is detected to be in a high-load state, the task process is triggered to stop. At this time, the tasks are sorted according to their priorities and sorting values, that is, task 1 = task 2 = task 3 > task 6 > task 5 > task 4 > task 9 > task 8 > task 7. Tasks 4 to 9 can be started as low-priority tasks, among which task 7 has the lowest priority, so task 7 is stopped first. According to the actual load situation, tasks 8, task 9, task 4, task 5, and task 6 can also be stopped in turn.

[0113] Step S204: taking the signal collection task whose running state is the startup state as the current startup task.

[0114] It can be understood that, after priority management, the signal acquisition task whose current running state is the startup state is the current startup task.

[0115] This embodiment provides a vehicle-side data processing method, which obtains the resource consumption data of the target vehicle, and determines whether the target vehicle is in a high-load state based on the resource consumption data; when the target vehicle is in a high-load state, based on the running state and priority of the signal acquisition task, a low-priority start task is determined; based on the ranking value of the low-priority start task, a target stop task is determined in the low-priority start task, and the running state of the target stop task is adjusted to the stop state; the signal acquisition task with the running state of the start state is used as the current start task. Priorities are set between tasks, and signals are collected according to the priorities. When the target vehicle is in a high-load state, some tasks with lower priorities are stopped to prevent the vehicle-side from entering a high-load state and improve processing efficiency.

[0116] Based on the above-mentioned embodiment 3 of the present application, in the fourth embodiment of the present application, the same or similar contents as those in the above-mentioned embodiment can refer to the above introduction, and will not be repeated later. Figure 7 , step S201 may include steps S202' to S204':

[0117] Step S202', when the target vehicle is not in a high-load state and has abundant resources, a high-priority stop task is determined based on the running state and priority of the signal acquisition task;

[0118] It should be noted that a high priority stop task is a signal acquisition task with a higher priority, a running state of a stop state and can be started. In this embodiment, a high priority task cannot be stopped, and a low priority task cannot be started after being stopped. Therefore, a medium-level task with a running state of a stop state can be used as a high priority stop task.

[0119] It is understandable that when the target vehicle is not in a high-load state and has abundant resources, the running tasks can be increased and the high-priority stop tasks can be selected so as to subsequently determine the signal collection tasks that need to be started.

[0120] Step S203', based on the ranking value of the high priority stop task, determine the target start task in the high priority stop task, and adjust the running state of the target start task to the start state;

[0121] It should be noted that the target start task is the signal acquisition task that needs to be started. According to the ranking value of the high priority stop task, the high priority stop task with the highest priority is found as the target start task, and the running state of the target start task will be adjusted to the start state.

[0122] It is understandable that if the target vehicle still has surplus resources after starting a task, a new target start task can be determined from the remaining high-priority stop tasks, and the running state of the new target start task can be adjusted to the start state, and so on, until no tasks can be started or the target vehicle is close to a high load state.

[0123] For example, reference Figure 6 , assuming that there are tasks 1 to 9, and tasks 4 to 9 have been stopped due to resource shortage. At this time, it is detected that the target vehicle has abundant resources, which triggers the start of the task process. At this time, the stopped tasks are sorted according to the priority and sorting value of the tasks, that is, task 6>task 5>task 4>task 9>task 8>task 7. Tasks 4 to 6 can be used as high-priority stopped tasks, among which task 6 has the highest priority, so task 6 will be started first. According to the actual load situation, tasks 5 and 4 can also be started in sequence.

[0124] For example, reference Figure 6, assuming that there are tasks 1 to 9, and tasks 7 to 9 have been stopped due to resource shortage. At this time, it is detected that the target vehicle has abundant resources, which triggers the start of the task process. At this time, the stopped tasks are sorted according to the task priority and sorting value, that is, task 9>task 8>task 7. Since tasks 7 to 9 are all low-priority tasks, they cannot be started after being stopped. At this time, no task can be used as a high-priority stopped task, and thus no task can be started.

[0125] Step S204': taking the signal collection task whose running state is the startup state as the current startup task.

[0126] It can be understood that, after priority management, the signal acquisition task whose current running state is the startup state is the current startup task.

[0127] In the specific implementation, refer to Figure 8 When it is detected that the vehicle-side resources are tight, the vehicle-side triggers the task stop process, selects a signal acquisition task with the lowest priority from the running tasks, and executes the task pause operation; when the vehicle-side resources are abundant, selects a signal acquisition task with the highest priority from the tasks that have been stopped due to resource shortages, and executes the task start operation.

[0128] This embodiment provides a vehicle-side data processing method. When the target vehicle is not in a high-load state and resources are abundant, a high-priority stop task is determined based on the running state and priority of the signal acquisition task; based on the ranking value of the high-priority stop task, a target start task is determined in the high-priority stop task, and the running state of the target start task is adjusted to the start state; the signal acquisition task with the running state of the start state is used as the current start task. Priorities are set between tasks, and signals are collected according to the priorities. When the target vehicle is not in a high-load state, some tasks with higher priorities are started to avoid wasting vehicle-side resources and improve processing efficiency.

[0129] For example, in order to help understand the implementation process of the vehicle signal acquisition method obtained by combining this embodiment with the above-mentioned embodiment 4, please refer to Fig. 9 , Fig. 9 A brief flow chart of a vehicle signal acquisition method is provided, specifically:

[0130] Receive the original CAN message from the vehicle, mark it with a self-increasing sequence in the order of message arrival, then deduplicate the data, delete the duplicate data frames (RX data frames / TX data frames), and retain the latest CAN message corresponding to the same CAN ID within 10ms, remove other messages, and add a timestamp to the deduplicated message, parse the CAN message to obtain the vehicle signal, and after priority management of the collection tasks, determine the currently running task, collect the required signal from the parsed vehicle signal, deduplicate the time period of the collected data before uploading the data, and only upload data in different time periods to the cloud.

[0131] It should be noted that the above examples are only used to understand the present application and do not constitute a limitation on the vehicle-side data processing method of the present application. More simple transformations based on this technical concept are all within the scope of protection of the present application.

[0132] This application also provides a vehicle-side data processing device, please refer to Fig.10 , the vehicle-side data processing device includes:

[0133] The data access module 10 is used to perform data deduplication on the original CAN message of the target vehicle to obtain the CAN message to be parsed.

[0134] The task management module 20 is used to determine the current startup task based on the priority of the signal acquisition task.

[0135] The signal acquisition module 30 is further used to determine the target vehicle signal in the parsed vehicle signal corresponding to the CAN message to be parsed based on the rule information of the current startup task, and to collect the target vehicle signal.

[0136] The data uploading module 40 is used to upload the signal data collected during the deduplication collection time period to the cloud.

[0137] In a feasible implementation manner, the data access module 10 is further used to filter out duplicate data frames in the original CAN message and delete the duplicate data frames;

[0138] Based on the identification information and time sequence information of the original CAN message, the latest CAN message corresponding to the same identification information within a preset time period is determined, and the original CAN messages except the latest CAN message are deleted.

[0139] In a feasible implementation manner, the data access module 10 is further used to add corresponding time sequence information to the original CAN message of the target vehicle based on the arrival order of the original CAN message when receiving the original CAN message of the target vehicle.

[0140] In a feasible implementation manner, the data access module 10 is further used to obtain the timestamp information of the CAN message to be parsed, and add the timestamp information into the corresponding CAN message to be parsed.

[0141] In a feasible implementation manner, the data access module 10 is further configured to, when receiving the original CAN message of the target vehicle, count the original CAN messages based on the arrival order of the original CAN messages to obtain a counting sequence of the original CAN messages;

[0142] The count sequence of the original CAN message is added to the corresponding original CAN message as time sequence information.

[0143] In a feasible implementation manner, the task management module 20 is further used to obtain resource consumption data of the target vehicle, and based on the resource consumption data, determine whether the target vehicle is in a high-load state;

[0144] When the target vehicle is in a high-load state, determining a low-priority startup task based on the running state and priority of the signal acquisition task;

[0145] Based on the ranking value of the low-priority startup task, determine a target stop task among the low-priority startup tasks, and adjust the running state of the target stop task to a stop state;

[0146] The signal acquisition task whose running state is the startup state is used as the current startup task.

[0147] In a feasible implementation manner, the task management module 20 is further used to determine a high priority stop task based on the running state and priority of the signal acquisition task when the target vehicle is not in a high load state and has abundant resources;

[0148] Based on the ranking value of the high priority stop task, determine a target start task in the high priority stop task, and adjust the running state of the target start task to a start state;

[0149] The signal acquisition task whose running state is the startup state is used as the current startup task.

[0150] In a feasible implementation manner, the data uploading module 40 is further used to determine the collection time period of the target vehicle signal based on the rule information corresponding to the current startup task of the target vehicle signal;

[0151] Determining a repetition time period based on a collection time period of the target vehicle signal;

[0152] The repeated time periods in the collection time periods are deleted to obtain the de-duplicated collection time periods.

[0153] The vehicle-side data processing device provided by the present application adopts the vehicle-side data processing method in the above embodiment, which can solve the technical problem that there are too many duplicate and redundant data, increase resource consumption, and affect the efficiency of vehicle-side data processing. Compared with the prior art, the beneficial effects of the vehicle-side data processing device provided by the present application are the same as the beneficial effects of the vehicle-side data processing method provided by the above embodiment, and other technical features in the vehicle-side data processing device are the same as the features disclosed in the above embodiment method, which will not be repeated here.

[0154] The present application provides a vehicle-side data processing device, which includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute the vehicle-side data processing method in the above-mentioned embodiment one.

[0155] Reference below Fig.11 , which shows a schematic diagram of the structure of a vehicle-side data processing device suitable for implementing an embodiment of the present application. The vehicle-side data processing device in the embodiment of the present application may include but is not limited to mobile terminals such as mobile phones, laptop computers, digital broadcast receivers, PDAs (Personal Digital Assistants), PADs (Portable Application Descriptions), PMPs (Portable Media Players), vehicle-mounted terminals (such as vehicle-mounted navigation terminals), etc., and fixed terminals such as digital TVs, desktop computers, etc. Fig.11 The vehicle-side data processing device shown is merely an example and should not bring any limitation to the functions and scope of use of the embodiments of the present application.

[0156] like Fig.11As shown, the vehicle-side data processing device may include a processing device 1001 (such as a central processing unit, a graphics processor, etc.), which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM: Read Only Memory) 1002 or a program loaded from a storage device 1003 to a random access memory (RAM: Random Access Memory) 1004. In RAM1004, various programs and data required for the operation of the vehicle-side data processing device are also stored. The processing device 1001, ROM1002 and RAM1004 are connected to each other through a bus 1005. An input / output (I / O) interface 1006 is also connected to the bus. Generally, the following systems can be connected to the I / O interface 1006: an input device 1007 including, for example, a touch screen, a touchpad, a keyboard, a mouse, an image sensor, a microphone, an accelerometer, a gyroscope, etc.; an output device 1008 including, for example, a liquid crystal display (LCD: Liquid Crystal Display), a speaker, a vibrator, etc.; a storage device 1003 including, for example, a magnetic tape, a hard disk, etc.; and a communication device 1009. The communication device 1009 can allow the vehicle-side data processing device to communicate with other devices wirelessly or by wire to exchange data. Although the figure shows a vehicle-side data processing device with various systems, it should be understood that it is not required to implement or have all the systems shown. More or fewer systems can be implemented or have alternatively.

[0157] In particular, according to the embodiments disclosed in the present application, the process described above with reference to the flowchart can be implemented as a computer software program. For example, the embodiments disclosed in the present application include a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program includes a program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network through a communication device, or installed from a storage device 1003, or installed from a ROM 1002. When the computer program is executed by the processing device 1001, the above-mentioned functions defined in the method of the embodiment disclosed in the present application are executed.

[0158] The vehicle-side data processing device provided by the present application adopts the vehicle-side data processing method in the above embodiment, which can solve the technical problems of large amounts of repeated and redundant data, increased resource consumption, and affected vehicle-side data processing efficiency. Compared with the prior art, the beneficial effects of the vehicle-side data processing device provided by the present application are the same as the beneficial effects of the vehicle-side data processing method provided by the above embodiment, and the other technical features in the vehicle-side data processing device are the same as the features disclosed in the method of the previous embodiment, which will not be repeated here.

[0159] It should be understood that the various parts disclosed in this application can be implemented by hardware, software, firmware or a combination thereof. In the description of the above embodiments, specific features, structures, materials or characteristics can be combined in any one or more embodiments or examples in a suitable manner.

[0160] The above are only specific implementations of the present application, but the protection scope of the present application is not limited thereto. Any technician familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

[0161] The present application provides a computer-readable storage medium having computer-readable program instructions (ie, computer programs) stored thereon, and the computer-readable program instructions are used to execute the vehicle-side data processing method in the above-mentioned embodiment.

[0162] The computer-readable storage medium provided in the present application may be, for example, a USB flash drive, but is not limited to electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, systems or devices, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, 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 above. In this embodiment, the computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in combination with an instruction execution system, system or device. The program code contained on the computer-readable storage medium may be transmitted using any appropriate medium, including but not limited to: wires, optical cables, RF (Radio Frequency), etc., or any suitable combination of the above.

[0163] The above-mentioned computer-readable storage medium may be included in the vehicle-side data processing device; or it may exist independently without being installed in the vehicle-side data processing device.

[0164] The above-mentioned computer-readable storage medium carries one or more programs. When the above-mentioned one or more programs are executed by the vehicle-side data processing device, the vehicle-side data processing device: deduplicates the original CAN message of the target vehicle to obtain the CAN message to be parsed; determines the current startup task based on the priority of the signal acquisition task; determines the target vehicle signal in the parsed vehicle signal corresponding to the CAN message to be parsed based on the rule information of the current startup task, and collects the target vehicle signal; and uploads the signal data collected during the deduplication collection time period to the cloud.

[0165] Computer program code for performing the operations of the present application may be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, C++, and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0166] The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, function and operation of the system, method and computer program product according to various embodiments of the present application. In this regard, each square box in the flow chart or block diagram can represent a module, a program segment or a part of a code, and the module, the program segment or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the square box can also occur in a sequence different from that marked in the accompanying drawings. For example, two square boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each square box in the block diagram and / or flow chart, and the combination of the square boxes in the block diagram and / or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0167] The modules involved in the embodiments described in this application may be implemented by software or hardware, wherein the name of the module does not constitute a limitation on the unit itself in some cases.

[0168] The readable storage medium provided by the present application is a computer-readable storage medium, which stores computer-readable program instructions (i.e., computer programs) for executing the above-mentioned vehicle-side data processing method, and can solve the technical problems of large amounts of duplicate and redundant data, increased resource consumption, and affected vehicle-side data processing efficiency. Compared with the prior art, the beneficial effects of the computer-readable storage medium provided by the present application are the same as the beneficial effects of the vehicle-side data processing method provided by the above-mentioned embodiment, and will not be repeated here.

[0169] The present application also provides a computer program product, including a computer program, which implements the steps of the above-mentioned vehicle-side data processing method when executed by a processor.

[0170] The computer program product provided by this application can solve the technical problem that there are too many duplicate and redundant data, which increases resource consumption and affects the efficiency of vehicle-side data processing. Compared with the prior art, the beneficial effects of the computer program product provided by this application are the same as the beneficial effects of the vehicle-side data processing method provided by the above embodiment, and will not be repeated here.

[0171] The above are only some embodiments of the present application, and are not intended to limit the patent scope of the present application. All equivalent structural changes made using the contents of the present application specification and drawings under the technical concept of the present application, or direct / indirect application in other related technical fields are included in the patent protection scope of the present application.

Claims

1. A vehicle-side data processing method, characterized in that: The method comprises: De-duplicate the original CAN message of the target vehicle to obtain the CAN message to be parsed; Based on the priority of the signal acquisition task, determine the current startup task; Based on the rule information of the current startup task, determine the target vehicle signal in the parsed vehicle signal corresponding to the CAN message to be parsed, and collect the target vehicle signal; The signal data collected during the deduplication collection period is uploaded to the cloud.

2. The method according to claim 1, characterized in that The step of performing data deduplication on the original CAN message of the target vehicle comprises: Filter out duplicate data frames in the original CAN message and delete the duplicate data frames; Based on the identification information and time sequence information of the original CAN message, the latest CAN message corresponding to the same identification information within a preset time period is determined, and the original CAN messages except the latest CAN message are deleted.

3. The method according to claim 2, characterized in that Before the step of performing data deduplication on the original CAN message of the target vehicle to obtain the CAN message to be parsed, the step further includes: When receiving the original CAN message of the target vehicle, adding corresponding time sequence information to the original CAN message of the target vehicle based on the arrival order of the original CAN message; After the step of performing data deduplication on the original CAN message of the target vehicle to obtain the CAN message to be parsed, the following steps are further included: Obtain the timestamp information of the CAN message to be parsed, and add the timestamp information to the corresponding CAN message to be parsed.

4. The method according to claim 3, characterized in that The step of adding corresponding time sequence information to the original CAN message of the target vehicle based on the arrival order of the original CAN message when the original CAN message of the target vehicle is received comprises: When receiving the original CAN message of the target vehicle, based on the arrival order of the original CAN message, the original CAN message is counted to obtain a counting sequence of the original CAN message; The count sequence of the original CAN message is added to the corresponding original CAN message as time sequence information.

5. The method according to claim 1, characterized in that The step of determining the current startup task based on the priority of the signal acquisition task includes: Acquiring resource consumption data of the target vehicle, and determining whether the target vehicle is in a high-load state based on the resource consumption data; When the target vehicle is in a high-load state, determining a low-priority startup task based on the running state and priority of the signal acquisition task; Based on the ranking value of the low-priority startup task, determine a target stop task among the low-priority startup tasks, and adjust the running state of the target stop task to a stop state; The signal acquisition task whose running state is the startup state is used as the current startup task.

6. The method according to claim 5, characterized in that After the step of obtaining the resource consumption data of the target vehicle and determining whether the target vehicle is in a high-load state based on the resource consumption data, the method further includes: When the target vehicle is not in a high-load state and has abundant resources, determining a high-priority stop task based on the running state and priority of the signal acquisition task; Based on the ranking value of the high priority stop task, determine a target start task in the high priority stop task, and adjust the running state of the target start task to a start state; The signal acquisition task whose running state is the startup state is used as the current startup task.

7. The method according to any one of claims 1 to 6, characterized in that Before the step of uploading the signal data collected during the deduplication collection time period to the cloud, the following steps are also included: Determining a collection time period of the target vehicle signal based on rule information corresponding to the current startup task of the target vehicle signal; Determining a repetition time period based on a collection time period of the target vehicle signal; The repeated time periods in the collection time periods are deleted to obtain the de-duplicated collection time periods.

8. A vehicle-side data processing device, characterized in that: The device comprises: The data access module is used to deduplicate the original CAN message of the target vehicle and obtain the CAN message to be parsed; The task management module is used to determine the current startup task based on the priority of the signal acquisition task; The signal acquisition module is further used to determine the target vehicle signal in the parsed vehicle signal corresponding to the CAN message to be parsed based on the rule information of the current startup task, and to collect the target vehicle signal; The data upload module is used to upload the signal data collected during the deduplication collection period to the cloud.

9. A vehicle-side data processing device, characterized in that: The device comprises: a memory, a processor and a computer program stored in the memory and executable on the processor, wherein the computer program is configured to implement the steps of the vehicle-side data processing method as described in any one of claims 1 to 7.

10. A storage medium, characterized in that: The storage medium is 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 data processing method as described in any one of claims 1 to 7 are implemented.

Citation Information

Cited By

  • Commercial vehicle vehicle-mounted message acquisition method and system, computer equipment and storage medium

    CN121193763A