Data acquisition task management method and device, electronic equipment and readable storage medium
By generating task templates in vehicle data acquisition scenarios and independently generating data acquisition tasks for each vehicle model, the problem of excessively long testing cycles for data acquisition tasks is solved, and more efficient task deployment is achieved.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- SHANGHAI ONSTAR TELEMATICS
- Filing Date
- 2023-07-17
- Publication Date
- 2026-07-31
AI Technical Summary
The testing cycle for data acquisition tasks is too long because all data acquisition instructions are coupled together, causing each vehicle model to have to wait for other vehicle models to pass testing before it can be released.
Generate task templates for vehicle data collection scenarios and generate independent data collection tasks based on the target vehicle model. Once the test is passed, the task can be published to the target vehicle, avoiding waiting for the test progress of other vehicle models.
By generating data collection tasks independently for each vehicle model, the testing cycle was shortened and the efficiency of data collection task release was improved.
Smart Images
Figure CN116929790B_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of vehicle engineering, and more specifically, to a data acquisition task management method, apparatus, electronic device, and readable storage medium. Background Technology
[0002] With technological advancements, vehicle intelligence is becoming increasingly prevalent, and data acquisition is an indispensable component in this process. Vehicles can use their own data acquisition tasks to inform users about their status, such as fuel consumption and tire pressure. When generating a data acquisition task, all data acquisition instructions are coupled together. The data acquisition task requires testing before it can be deployed. However, because all data acquisition instructions are coupled, all vehicle models corresponding to the task need to test each instruction during testing. Even if one vehicle model has successfully tested all data acquisition instructions within the task, the task will only be released to the corresponding model after other models have also successfully tested all instructions. Therefore, the testing cycle for data acquisition tasks is excessively long. Summary of the Invention
[0003] In view of this, this application provides a data acquisition task management method, apparatus, electronic device, and readable storage medium to solve the problem of excessively long testing cycles for data acquisition tasks.
[0004] To achieve the above objectives, the following solution is proposed:
[0005] A data acquisition task management method, the method comprising:
[0006] Acquire vehicle data collection scenarios, collection objects, and target vehicle models;
[0007] Generate a task template for the vehicle data collection scenario based on the data collection object;
[0008] The task template and the target vehicle model are used to generate a data collection task corresponding to the target vehicle model;
[0009] The data acquisition task was tested on the target vehicle model.
[0010] If the test passes, the data collection task will be published to the target vehicle model.
[0011] Optionally, generating a data collection task corresponding to the target vehicle model using the task template and the target vehicle model includes:
[0012] Generate the task ID, data acquisition trigger event, data acquisition frequency, and data upload frequency in the data acquisition task based on the task template;
[0013] Based on the task template, the data collection target is determined, and the data collection instruction corresponding to the data collection target and the target vehicle model is obtained from the task version management database according to the target vehicle model;
[0014] By combining the data acquisition instruction, the task ID, the data acquisition trigger event, the data acquisition frequency, and the data upload frequency, a data acquisition task corresponding to the target vehicle model can be obtained.
[0015] Optional, also includes:
[0016] Receive a self-check request from the vehicle, the self-check request including the vehicle model ID and task information for all the data acquisition tasks currently being performed on the vehicle, the task information including the task ID and the task version number;
[0017] Read the vehicle's task configuration table based on the vehicle model ID;
[0018] Add at least one data acquisition task's task ID from the task configuration table that is inactive to the first task update list;
[0019] The comparison results are obtained by comparing the self-check request with the task version number corresponding to the same task ID in the task configuration table one by one using the task ID;
[0020] Based on the comparison results, the task IDs that are different from the task version numbers corresponding to the self-check request and the task configuration table are placed into the second task update list, and the task status corresponding to the task ID placed in the second task update list is set to inactive.
[0021] The first task update list and the second task update list are combined to obtain the task update list;
[0022] The data collection tasks for the vehicle are updated based on the task update list.
[0023] Optionally, updating the data collection task for the vehicle based on the task update list includes:
[0024] Send a target task update request to the vehicle based on the target task ID in the task update list;
[0025] Upon receiving the result of the target data acquisition task installation completion from the vehicle based on the target task update request, the current task status corresponding to the target task ID in the task update list is set to active.
[0026] Optional, also includes:
[0027] Acquire the first vehicle data collection scenario, the first collection object, and the first target vehicle model;
[0028] Generate a first task template for the first vehicle data collection scenario based on the first collection object;
[0029] Determine whether the first task template exists in the existing vehicle data scenario;
[0030] If it exists, then determine whether the first target vehicle model is included in the vehicle model corresponding to the first task template in the existing vehicle data scenario;
[0031] The generation result of the first data acquisition task corresponding to the first target vehicle model is determined based on the judgment result of whether or not the first target vehicle model is included.
[0032] Optionally, determining the generation result of the first data acquisition task corresponding to the first target vehicle based on the judgment result of whether it includes the first target vehicle includes:
[0033] If the vehicle model corresponding to the first task template in the existing vehicle data scenario includes the first target vehicle model, then the data collection task corresponding to the first target vehicle model is obtained from the existing vehicle data collection scenario and used as the data collection task of the first target vehicle model in the first vehicle data collection scenario.
[0034] Optional, also includes:
[0035] Based on the new target vehicle model, obtain the existing vehicle data collection scenario, the second task template, and the new target vehicle model;
[0036] A second data acquisition task corresponding to the new target vehicle model is generated using the task template and the new target vehicle model.
[0037] The second data acquisition task was tested on the vehicle of the new target model.
[0038] If the test passes, the second data collection task will be sent to the vehicle of the new target model.
[0039] A data acquisition task management device, the device comprising:
[0040] The acquisition unit is used to acquire vehicle data collection scenarios, collection objects, and target vehicle models.
[0041] The template generation unit is used to generate a task template for the vehicle data collection scenario based on the collection object.
[0042] The task generation unit is used to generate a data acquisition task corresponding to the target vehicle model using the task template and the target vehicle model.
[0043] The testing unit is used to test the data acquisition task on the target vehicle model.
[0044] If the test passes, the release unit is triggered;
[0045] The publishing unit is used to publish the data collection task to the target vehicle model.
[0046] An electronic device, comprising a memory and a processor;
[0047] The memory is used to store programs;
[0048] The processor is used to execute the program to implement each step of any of the above data acquisition task management methods.
[0049] A readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of any of the above-described data acquisition task management methods.
[0050] This application provides a data acquisition task management method, apparatus, electronic device, and readable storage medium. The method first generates a task template for a vehicle data acquisition scenario, and then generates a data acquisition task corresponding to the target vehicle model based on the task template. When testing data acquisition tasks, since the tasks are generated independently for each vehicle model, the data acquisition task can be released to vehicles of the target model as soon as it passes testing, without being affected by the testing progress of other vehicle models, effectively shortening the testing cycle of the data acquisition task. Attached Figure Description
[0051] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only embodiments of this application. For those skilled in the art, other drawings can be obtained based on the provided drawings without creative effort.
[0052] Figure 1 A flowchart illustrating a data acquisition task management method provided in an embodiment of this application;
[0053] Figure 2 A flowchart illustrating a data acquisition task management service provided in an embodiment of this application;
[0054] Figure 3A schematic diagram of the structure of a data acquisition task management device provided in an embodiment of this application;
[0055] Figure 4 This is a hardware structure block diagram of an electronic device provided in an embodiment of this application. Detailed Implementation
[0056] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.
[0057] like Figure 1 As shown in the figure, this application provides a data acquisition task management method, which may include:
[0058] S10. Obtain vehicle data collection scenario, collection object, and target vehicle model.
[0059] The vehicle data collection scenario can be any scenario encountered while the vehicle is in motion, and optionally, it can be an autonomous driving scenario. The vehicle data collection scenario script is designed by vehicle engineers based on customer business needs or vehicle engineering update requirements. The script for the vehicle data collection scenario can include the scenario ID corresponding to the scenario, a list of vehicle models corresponding to the scenario (the list can contain multiple models, each with a corresponding model ID), scenario content (the scenario content can include at least one task ID and task content, where the task content can include the trigger event for data collection, the data collection object (containing specific data collection elements), collection frequency, upload frequency, and release status, where the release status can include added, passed test, and released), status, approval status, start time, and end time. The status can be divided into active and inactive. Active indicates that the lifecycle of the vehicle data collection scenario has not yet ended; inactive indicates that the lifecycle of the vehicle data collection scenario has ended. The approval status can be divided into approved and disapproved. After vehicle engineers submit the script for the vehicle data collection scenario, it is reviewed by designated personnel. If the review is passed, the script can proceed to the next stage; if it fails, the script is returned or terminated. Therefore, the approval status represents the legality of the vehicle data collection scenario. The data collection object can be any object in the vehicle data collection scenario. For example, in an autonomous driving scenario, the data collection object could be the vehicle's state, road state, and driver state. The target vehicle model can be any vehicle model included in the vehicle model list within the script for the vehicle data collection scenario.
[0060] S11. Generate a task template for the vehicle data collection scenario based on the data collection object.
[0061] In this context, the task template can be a collection of specific data collection elements corresponding to the collection object in a vehicle data collection scenario. Since the collection object is the data collection target in the vehicle data collection scenario, this embodiment can generate at least one task template for the vehicle data collection scenario based on the collection object. For example, if the vehicle data collection scenario is an autonomous driving scenario, then the collection objects in this autonomous driving scenario are the vehicle body state, road state, and driver state. The task template can be a collection of specific collection elements for the vehicle body state collection task. Optionally, the specific collection elements may include driving range elements and tire pressure elements. In this case, the task template for the vehicle body state collection task is a collection of driving range elements and tire pressure elements.
[0062] S12. Generate a data collection task corresponding to the target vehicle model using the task template and the target vehicle model.
[0063] To ensure that data acquisition tasks for each vehicle model in the vehicle data acquisition scenario can be tested independently without being affected by the testing progress of other models, this embodiment generates multiple independent data acquisition tasks for each vehicle model based on the task template and the vehicle model. Therefore, the generation of data acquisition tasks in the vehicle data acquisition scenario can be divided into two parts: the first part generates the general part of the data acquisition task; the second part generates the unique part for the target vehicle model, and the general part plus the unique part constitutes the data acquisition task corresponding to that target vehicle model. Of course, the general and unique parts of the data acquisition task can be generated simultaneously or sequentially. Furthermore, after the current target vehicle model completes the generation of its data acquisition task, when generating the data acquisition task for the next target vehicle model, the general part of its data acquisition task can be directly copied from the current target vehicle model's data acquisition task, and the unique part of the next target vehicle model is generated, with the general and unique parts forming the data acquisition task corresponding to the next target vehicle model.
[0064] S13. Test the data acquisition task on the target vehicle model;
[0065] If the test passes, proceed to step S14;
[0066] S14. Distribute the data collection task to the target vehicle model.
[0067] After generating data acquisition tasks, these tasks need to be tested to avoid potential risks. To avoid repeatedly testing multiple data acquisition tasks for different vehicle models within a given vehicle data acquisition scenario, the data acquisition tasks for multiple vehicle models can be aggregated and sent to the corresponding testers when sending them to the testers. For example, a vehicle data acquisition scenario might correspond to two vehicle models, A and B. The data acquisition tasks for model A are A1, B1, and C1; the data acquisition tasks for model B are A2, B2, and C2. The testers for models A and B are the same. If B1 and B2 are identical, and C1 and C2 are identical, then for this vehicle data acquisition scenario, the testers will receive test tasks A1, A2, B1, and C1. If A1 and A2 are different, B1 and B2 are different, and C1 and C2 are different, then for this vehicle data acquisition scenario, the testers will receive test tasks A1, A2, B1, B2, C1, and C2. Furthermore, after the data acquisition task passes the test, this embodiment can publish the data acquisition task to the task version management database for easy acquisition and subsequent sending to the vehicle.
[0068] This application provides a data acquisition task management method. The method first generates a task template for a vehicle data acquisition scenario, and then generates a data acquisition task corresponding to the target vehicle model based on the task template. When testing data acquisition tasks, since the tasks are generated independently for each vehicle model, the data acquisition task can be released to vehicles of the target model as soon as it passes testing, without being affected by the testing progress of other vehicle models, effectively shortening the testing cycle of the data acquisition task.
[0069] In another data acquisition task management method provided according to an embodiment of this application, Figure 1 Step S12 shown may include steps one through three:
[0070] Step 1: Generate the task ID, data acquisition trigger event, data acquisition frequency, and data upload frequency for the data acquisition task based on the task template;
[0071] Step 2: Determine the data collection target based on the task template and retrieve the data collection instructions corresponding to the data collection target and the target vehicle model from the task version management database;
[0072] Step 3: Combine the data acquisition command, task ID, data acquisition trigger event, data acquisition frequency, and data upload frequency to obtain the data acquisition task corresponding to the target vehicle model.
[0073] In this embodiment, for the current target vehicle model in the vehicle data scenario, a general part of the target data acquisition task for the current target vehicle model is generated according to the task template. This general part includes a task ID, a data acquisition trigger event, a data acquisition frequency, and a data upload frequency. The task ID for generating the target data acquisition task is obtained by establishing a correspondence between the task ID of the target data acquisition task in the vehicle data acquisition scenario script and the vehicle model ID of the current target vehicle. Similarly, the trigger event, data acquisition frequency, and data upload frequency for generating the target data acquisition task are obtained from the vehicle data acquisition scenario script and then incorporated into the task template to generate the general part of the target data acquisition task for the current target vehicle model. The data acquisition target refers to the specific data acquisition elements included in the data acquisition object, such as driving range and tire pressure. In this embodiment, specific data acquisition instructions corresponding to the target vehicle model can be obtained from the task version management database based on the data acquisition elements. For example, if the data acquisition target is the driving range element, and the target vehicle model is a gasoline vehicle, the specific data acquisition instruction could be related to the remaining fuel; if the target vehicle model is an electric vehicle, the specific data acquisition instruction could be related to the remaining battery power. Multiple specific data acquisition instructions corresponding to the target vehicle model are placed into the task template to generate a unique part of the target data acquisition task corresponding to the target vehicle model. Furthermore, after generating the target data acquisition task, this embodiment allows the task's release status to be set to "test".
[0074] In another data acquisition task management method provided according to an embodiment of this application, the method may further include steps four to ten:
[0075] Step 4: Receive the vehicle's self-check request. The self-check request includes the vehicle model ID and task information for all current data collection tasks of the vehicle. The task information includes the task ID and task version number.
[0076] Step 5: Read the vehicle's task configuration table based on the vehicle model ID;
[0077] Step 6: Add the task ID of at least one data acquisition task that is inactive in the task configuration table to the first task update list;
[0078] Step 7: Compare the self-check requests with the task version numbers corresponding to the same task ID in the task configuration table one by one using the task ID to obtain the comparison results;
[0079] Step 8: Based on the comparison results, add the task IDs that are different from the task version numbers in the self-check request and the task configuration table to the second task update list, and set the status of the task IDs added to the second task update list to inactive.
[0080] Step 9: Combine the first task update list and the second task update list to obtain the task update list;
[0081] Step 10: Update the vehicle data collection tasks based on the task update list.
[0082] Among them, the vehicle's self-check request can be a task update request sent by the vehicle to the task publishing server in order to obtain the latest version of the data collection task in a timely manner. The change of the data collection task version can be the change of the same data collection task under different vehicle models. That is, when the vehicle model changes, the same data collection task also needs to be changed accordingly in order to adapt to the changed vehicle model.
[0083] Specifically, after every ten vehicle startup cycles, the vehicle's data acquisition task management module sends a self-check request to the task publishing server via the mobile cellular network. The startup cycle can be the time from vehicle ignition to vehicle shutdown. The self-check request can include the vehicle model ID, task information for all current data acquisition tasks, and task information such as task version number, task ID, and timestamp. Upon receiving the self-check request from the vehicle, the task publishing server queries the task configuration table corresponding to the vehicle model ID in the self-check request. Since the task configuration table contains the task ID, its corresponding task status, and task version number, and the self-check request contains the task ID, task status, and task version number, this embodiment can compare the task status and task version number using the task ID. The task status can be active or inactive. Active indicates that the data acquisition task has been published to the vehicle and is effective in the vehicle; inactive indicates that the data acquisition task has not been sent to the vehicle and is not effective in the vehicle. In this embodiment, data acquisition tasks that have not been sent to the vehicle and are not active in the vehicle are identified as inactive tasks in the task configuration table based on their task status. The task ID of these inactive tasks is then added to the first task update list. For active data acquisition tasks in the task configuration table, this embodiment compares the task ID with the task version number to determine if the current version of the vehicle's data acquisition task is the latest version. If not, the latest version of the data acquisition task is retrieved from the task version management database based on the task ID, and the corresponding task ID is added to the second task update list, with the task status set to inactive. This embodiment obtains the vehicle's task update list using both the first and second task update lists and updates tasks to the vehicles one by one according to the task update list.
[0084] In another data acquisition task management method provided according to an embodiment of this application, step ten may include steps eleven and twelve:
[0085] Step 11: Send a target task update request to the vehicle based on the target task ID in the task update list;
[0086] Once the system receives the result indicating that the target data acquisition task installation is complete from the vehicle's update request based on the target task, proceed to step twelve.
[0087] Step 12: Set the status of the current task corresponding to the target task ID in the task update list to active.
[0088] In this embodiment, vehicle data acquisition tasks can be updated one by one according to the task update list. Specifically, the task publishing server sends a target task update request to the vehicle's data acquisition task management module. After receiving the target data acquisition task update request, the data acquisition task management module can complete the data acquisition task update in two steps. First, it deletes the old data acquisition task corresponding to the target task ID in the data acquisition task management module according to the target task ID in the target task update request; second, it installs the new data acquisition task corresponding to the target task ID in the target task update request. After completing the above two steps, the data acquisition task management module reports the installation result of the target data acquisition task to the task publishing server. Based on the reported installation result of the target data acquisition task, the task publishing server sets the task status of the data acquisition task corresponding to the target task ID in the task update list to active and continues to update the next data acquisition task. In addition, the update progress of the task update list can be checked after each data acquisition task update is completed. Specifically, it can check whether the task status of all data acquisition tasks in the task update list is active. If so, the vehicle's data acquisition task update is completed; otherwise, the vehicle's data acquisition tasks are updated one by one.
[0089] like Figure 2 The data acquisition task management workflow is shown below. The task version management server generates data acquisition tasks and publishes them to the task version management database. During the self-check cycle, the vehicle's data acquisition task management module begins a task self-check and sends a task self-check request to the task publishing server. The task publishing server retrieves the latest version of the task from the task version management database based on the self-check request, compiles a task update list, and sends task update requests to vehicles one by one according to the task update list. The vehicle, based on the task update request, deletes the old version task, installs the new version task, and reports the task installation result back to the task publishing server. The task publishing server sets the task status of the tasks in the task update list based on the task installation result and checks the task update list to determine if all tasks in the list have been updated. If not, it continues to send task update requests to vehicles one by one; if so, it ends the current task update process.
[0090] In another data acquisition task management method provided according to an embodiment of this application, the method may further include steps thirteen to seventeen:
[0091] Step 13: Obtain the first vehicle data collection scenario, the first collection object, and the first target vehicle model;
[0092] Step Fourteen: Generate the first task template for the first vehicle data collection scenario based on the first data collection object;
[0093] Step 15: Determine if the first task template exists in the existing vehicle data scenario;
[0094] If it exists, proceed to steps sixteen and seventeen;
[0095] Step 16: Determine whether the first target vehicle model is included in the vehicle models corresponding to the first task template in the existing vehicle data scenario;
[0096] Step 17: Determine the generation result of the first data acquisition task corresponding to the first target vehicle model based on the judgment result of whether the first target vehicle model is included.
[0097] When a first vehicle data collection scenario needs to be added due to business requirements, vehicle engineers can design a script for the scenario according to the business needs. The script can include: scenario ID, vehicle model list, scenario content, status (new, active, and inactive; here it can be new), start time, and end time. The scenario content can include at least one task ID, data collection trigger time, data collection elements, collection frequency, upload frequency, and release status (new, passed test, and released). The script is submitted to reviewers for approval. If the review is successful, it can be submitted to the task version management server, which will then generate the first data collection task for the first vehicle data collection scenario. Specifically, before generating the first data acquisition task in the first vehicle data acquisition scenario, it can first determine whether there is a data acquisition task in the existing vehicle data acquisition scenarios that is the same as the first vehicle data acquisition scenario, based on the first task template (which includes the first task ID, data acquisition trigger time, data acquisition elements, acquisition frequency, upload frequency, and publishing status). If so, it can then be determined whether the vehicle models corresponding to the data acquisition task in the existing vehicle data acquisition scenarios include the first target vehicle model, where the first target vehicle model can be a vehicle model in the first vehicle data acquisition scenario. Specifically, this embodiment can determine whether there is a first data acquisition task in the existing vehicle data acquisition scenarios through the first task ID in the first task template, where the first data acquisition task can be a task in the first vehicle data acquisition scenario. This embodiment can determine whether to generate a first data acquisition task in the first vehicle data acquisition scenario that corresponds to the first target vehicle model based on the first task template and the first target vehicle model. If the first task template in the first vehicle data acquisition scenario exists in the existing vehicle data acquisition scenario and the vehicle model corresponding to the first task template includes the first target vehicle model, then the first target vehicle model can directly reuse the data acquisition task corresponding to the first target vehicle model in the existing vehicle data acquisition scenario, effectively avoiding the repeated generation of the data acquisition task for the first target vehicle model in the first vehicle data acquisition scenario, thus saving time.
[0098] Specifically, if the vehicle model corresponding to the first task template in the existing vehicle data scenario includes the first target vehicle model, then the data acquisition task corresponding to the first target vehicle model is obtained from the existing vehicle data acquisition scenario and used as the data acquisition task for the first target vehicle model in the first vehicle data acquisition scenario; if the first task template already exists in the existing vehicle data acquisition scenario but the vehicle model corresponding to the first task template does not include the first target vehicle model, then the first data acquisition task corresponding to the first target vehicle model is generated in the first vehicle data acquisition scenario based on the first task template; if the first task template does not exist in the existing vehicle data acquisition scenario, then the first data acquisition task corresponding to the first target vehicle model is generated in the first vehicle data acquisition scenario based on the first task template.
[0099] Furthermore, this embodiment can include two matrix tables: a scenario-task matrix and a task-vehicle matrix. The scenario-task matrix table can include scenario IDs and task IDs, with a one-to-many relationship (one scenario ID can correspond to multiple task IDs). The task-vehicle matrix table can include task IDs and vehicle IDs, with a many-to-many relationship (one task ID can correspond to multiple vehicle IDs, and vice versa). The correspondence between task IDs and vehicle IDs is unique within the task-vehicle matrix table. Changes in the vehicle data collection scenario can lead to expansion or contraction of both the scenario-task and task-vehicle matrix tables. Similarly, changes in vehicle models can also lead to expansion or contraction of these tables. After each expansion or contraction of the scenario-task and task-vehicle matrix tables, the new tables are stored in the task version management database. Additionally, updated information such as new vehicle data collection scenario scripts, new task templates, and new vehicle models can also be stored in the task version management database. Once the scenario-task matrix table and the task-vehicle model matrix table have been expanded or reduced, the data collection tasks corresponding to the vehicle models that need to be tested can be sent to the testers for testing.
[0100] Furthermore, this embodiment can periodically check the lifecycle of vehicle data collection scenarios through a task version management server, specifically by polling every five minutes. In this embodiment, it can first determine whether the vehicle data collection scenario is a newly added scenario; if so, it enters the newly added scenario stage; if not, it determines the lifecycle of the vehicle data collection scenario, that is, whether the end time of the vehicle data collection scenario is earlier than the current time; if so, it enters the stage of completing the expired scenario.
[0101] For the new scenario phase, the task version management server generates new data acquisition tasks corresponding to different vehicle models under the new vehicle data acquisition scenario script (the data acquisition task generation process has been described in detail above and will not be repeated here), and expands the scenario-task matrix table and the task-vehicle model matrix table. After the table expansion operation is completed, the new data acquisition task is sent to the corresponding testers for testing. After each new data acquisition task is tested, the release status of the new data acquisition task is changed from test to release. The task version management server sends a task release request to the task release server. The task release request can include: vehicle model ID, task ID, operation type (new task), and release time. The task release server can determine the specific vehicle corresponding to the vehicle model ID in the received task release request and obtain the task configuration list corresponding to the vehicle (the task configuration list of each vehicle is independent). The task release server can add the new data acquisition task corresponding to the task ID in the vehicle's task configuration table according to the task ID and operation type in the received task release request, and set the task status of the new data acquisition task to inactive.
[0102] For scenarios nearing completion and expiration, the task version management server retrieves the scenario ID, task ID, and vehicle model ID for the expiring vehicle data collection scenario and shrinks the scenario-task matrix and task-vehicle model matrix. After shrinking, the task version management server determines the task ID and corresponding vehicle model ID to be deleted and sends a task deletion request to the task publishing server. This request may include: vehicle model ID, task ID, operation type (delete task), and deletion time. The task publishing server can then determine the specific vehicle based on the vehicle model ID in the received deletion request and retrieve the corresponding task configuration list. The task publishing server can then directly delete the corresponding data collection task from the vehicle's task configuration list based on the task ID in the received deletion request.
[0103] Specifically, regarding table expansion, after the task version management server receives new information, it can retrieve the scenario-task matrix table and the task-vehicle matrix table based on the scenario ID, the corresponding task ID, and the vehicle model ID in the new information, and determine the actual operation to be performed on the scenario-task matrix table and the task-vehicle matrix table.
[0104] If both the scenario ID and task ID exist in the scenario-task matrix table, it means that the new vehicle data collection scenario already exists, and this addition is for a new vehicle model; therefore, there is no need to expand the scenario-task matrix table. If the scenario-task matrix table does not contain a scenario ID but contains a task ID, it means that the data collection task in the new vehicle data collection scenario reuses an existing data collection task; therefore, the scenario-task matrix table needs to be expanded by adding a correspondence between the scenario ID and the task ID. If the scenario-task matrix table contains neither a scenario ID nor a task ID, it means that the data collection task is a new task; therefore, a correspondence between the scenario ID and the task ID needs to be added to the scenario-task matrix table.
[0105] If both the scenario ID and vehicle model ID exist in the task-vehicle matrix table, it indicates that the data collection task is a reuse of an existing data collection task, and the current addition is a new scenario. In this case, there is no need to expand the task-vehicle matrix table. If the task-vehicle matrix table contains a scenario ID but not a vehicle model ID, it indicates that the current addition is a new vehicle model. In this case, the task-vehicle matrix table needs to be expanded by adding a mapping between the task ID and the vehicle model ID. If the task-vehicle matrix table contains neither a scenario ID nor a vehicle model ID, then the mapping between the task ID and the vehicle model ID needs to be added directly to the task-vehicle matrix table.
[0106] Specifically, regarding table shrinking, when the task version management server receives the deletion information of a completed or expired scenario, it first retrieves all task IDs under that scenario ID in the scenario-task matrix table based on the scenario ID of the completed or expired scenario. Then, it retrieves the scenario ID corresponding to the task ID in the scenario-task matrix table in reverse order based on the task ID. Based on the retrieval results, it determines the actual operation to be performed on the scenario-task matrix table.
[0107] If a task ID in the scenario-task matrix table does not correspond to any other scenario ID, it indicates a unique correspondence between the task ID and the scenario ID. In this case, the scenario-task matrix table is shrunk, meaning the correspondence between the task ID and the scenario ID is deleted. If a task ID in the scenario-task matrix table corresponds to another scenario ID, it indicates that the data acquisition task has been reused by other vehicle data acquisition scenarios. The vehicle model IDs that have not reused the data acquisition task are identified, and the correspondence between the vehicle model IDs and task IDs that have not reused the data acquisition task is deleted from the task-vehicle model matrix table. Based on the scenario ID, the corresponding record in the scenario-task matrix table is deleted, and the scenario content definition script in the completed and expired scenario script is also deleted. In this embodiment, when determining the vehicle model ID that has not reused the data collection task, the system first retrieves all vehicle model IDs corresponding to the task ID from the task-vehicle matrix table to form a first vehicle model ID list. Then, it retrieves other scenario IDs corresponding to the task ID from the scenario-task matrix table and retrieves the vehicle model list in the scenario script based on the other scenario IDs to form a second vehicle model ID list. Finally, it compares the first vehicle model ID list and the second vehicle model ID list to determine the vehicle model ID that has not reused the data collection task. The vehicle model ID that has not reused the data collection task is the one that exists only in the first vehicle model ID list and not in the second vehicle model ID list.
[0108] In another data acquisition task management method provided according to an embodiment of this application, the method may further include steps seventeen to twenty:
[0109] Step 17: Obtain the existing vehicle data collection scenario, the second task template, and the new target vehicle model based on the new target vehicle model;
[0110] Step 18: Generate a second data collection task corresponding to the new target vehicle model using the task template and the new target vehicle model;
[0111] Step 19: Test the second data acquisition task on the new target vehicle model;
[0112] If the test passes, proceed to step twenty;
[0113] Step 20: Publish the second data collection task to the new target vehicle model.
[0114] This embodiment allows adding new target vehicle models to existing vehicle data collection scenarios. Specifically, the task version management server can select an existing scenario ID based on the new target vehicle's model ID, retrieve the scenario content of the existing vehicle data collection scenario from the task version management database, generate a second task template based on the scenario content, and then generate a data collection task corresponding to the new target vehicle using the second task template and the new target vehicle. Of course, when generating the data collection task corresponding to the new target vehicle, if a second task template exists in another vehicle data collection scenario and the vehicle model corresponding to the second task template includes the new target vehicle, then the data collection task corresponding to the new target vehicle can be obtained from that other vehicle data collection scenario and used as the data collection task for the new target vehicle in the existing vehicle data collection scenario, eliminating the need for repeated generation and saving time.
[0115] Corresponding to the data acquisition task management method provided in the embodiments of this application, the embodiments of this application also provide a data acquisition task management device.
[0116] like Figure 3 As shown in the illustration, this application also provides a data acquisition task management device, which may include:
[0117] Acquisition unit 100 is used to acquire vehicle data collection scenarios, collection objects, and target vehicle models;
[0118] Template generation unit 110 is used to generate a task template for vehicle data collection scenario based on the collection object;
[0119] The task generation unit 120 is used to generate a data acquisition task corresponding to the target vehicle model by using a task template and the target vehicle model.
[0120] Test unit 130 is used to test the data acquisition task on the target vehicle model;
[0121] If the test passes, release unit 140 will be triggered.
[0122] The publishing unit 140 is used to publish the data collection task to the target vehicle model.
[0123] In another data acquisition task management device provided according to an embodiment of this application, Figure 2 The task generation unit 120 shown may include:
[0124] The task has a common generation sub-unit, which is used to generate the task ID, data acquisition trigger event, data acquisition frequency and data upload frequency in the data acquisition task according to the task template;
[0125] The task-specific part generation sub-unit is used to determine the data collection target according to the task template and obtain the data collection instructions corresponding to the data collection target and the target vehicle from the task version management database according to the target vehicle.
[0126] The task acquisition subunit is used to combine the data acquisition instruction, task ID, data acquisition trigger event, data acquisition frequency, and data upload frequency to obtain the data acquisition task corresponding to the target vehicle model.
[0127] In another data acquisition task management device provided according to an embodiment of this application, the device may further include:
[0128] The request receiving unit is used to receive the vehicle's self-test request. The self-test request includes the vehicle model ID and task information for all current data acquisition tasks of the vehicle. The task information includes the task ID and task version number.
[0129] The task reading unit is used to read the vehicle's task configuration table based on the vehicle model ID.
[0130] The first task update list acquisition unit is used to put the task ID of at least one data acquisition task that is inactive in the task configuration table into the first task update list.
[0131] The task comparison unit is used to compare the self-test request with the task version number corresponding to the same task ID in the task configuration table one by one by the task ID to obtain the comparison result.
[0132] The second task update list acquisition unit is used to, based on the comparison results, put the task IDs that are different from the task version numbers corresponding to the self-check request and the task configuration table into the second task update list, and set the status of the task corresponding to the task ID put into the second task update list to inactive.
[0133] The task update list acquisition unit is used to combine the first task update list and the second task update list to obtain a task update list.
[0134] The task update unit is used to update the vehicle's data acquisition tasks based on the task update list.
[0135] In another data acquisition task management device provided according to an embodiment of this application, the task update unit may include:
[0136] The update request sending subunit is used to send a target task update request to the vehicle based on the target task ID in the task update list;
[0137] Upon receiving feedback from the vehicle regarding the completion of the target data acquisition task installation based on the target task update request, the task status setting subunit is triggered.
[0138] The Task Status Setting sub-unit is used to set the status of the current task corresponding to the target task ID in the task update list to active.
[0139] In another data acquisition task management device provided according to an embodiment of this application, the device may further include:
[0140] The first acquisition unit is used to acquire the first vehicle data acquisition scenario, the first acquisition object, and the first target vehicle model;
[0141] The first task template generation unit is used to generate a first task template for the first vehicle data acquisition scenario based on the first acquisition object.
[0142] The first task template judgment unit is used to determine whether the first task template exists in the existing vehicle data scenario;
[0143] If it exists, the first target vehicle model judgment unit and the task generation result determination subunit are triggered;
[0144] The first target vehicle model determination unit is used to determine whether the first target vehicle model is included in the vehicle models corresponding to the first task template in the existing vehicle data scenario.
[0145] The task generation result determination subunit is used to determine the generation result of the first data acquisition task corresponding to the first target vehicle model based on the judgment result of whether the first target vehicle model is included.
[0146] In another data acquisition task management device provided according to an embodiment of this application, the aforementioned task generation result determination subunit may include:
[0147] If the vehicle model corresponding to the first task template in the existing vehicle data scenario includes the first target vehicle model, then the data acquisition task acquisition sub-unit is triggered.
[0148] The data acquisition task acquisition subunit is used to acquire the data acquisition task corresponding to the first target vehicle model from the existing vehicle data acquisition scenario, and use it as the data acquisition task of the first target vehicle model in the first vehicle data acquisition scenario.
[0149] In another data acquisition task management device provided according to an embodiment of this application, the device may further include:
[0150] The second acquisition unit is used to acquire the existing vehicle data collection scenario, the second task template, and the new target vehicle model based on the new target vehicle model.
[0151] The second data acquisition task acquisition unit is used to generate a second data acquisition task corresponding to the new target vehicle model through the task template and the new target vehicle model.
[0152] The second data acquisition task test unit is used to test the second data acquisition task on the new target model vehicle.
[0153] If the test passes, the second task release unit is triggered;
[0154] The second task publishing unit is used to publish the second data acquisition task to the new target vehicle model.
[0155] like Figure 4 As shown, this application provides an electronic device 70, including at least one processor 701, at least one memory 702 connected to the processor 701, and a bus 703; wherein the processor 701 and the memory 702 communicate with each other through the bus 703; the processor 701 is used to call program instructions in the memory 702 to execute the above-described data acquisition task management method. The electronic device 70 in this document may be a server, PC, etc.
[0156] This application also provides a readable storage medium storing a computer program thereon, which, when executed by a processor, implements the various steps of any of the above-described data acquisition task management methods.
[0157] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart... Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.
[0158] In a typical configuration, the device includes one or more processors (CPUs), memory, and a bus. The device may also include input / output interfaces, network interfaces, etc.
[0159] Memory may include non-persistent memory in computer-readable storage media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM, and memory includes at least one memory chip. Memory is an example of a computer-readable medium.
[0160] Computer-readable storage media include both permanent and non-permanent, removable and non-removable media that can store information by any method or technology. Information can be computer-readable instructions, data structures, program modules, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic magnetic disk storage or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.
[0161] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.
[0162] It should be noted that, in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such process, method, article, or apparatus. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes the element.
[0163] The various embodiments in this specification are described in a related manner. Similar or identical parts between embodiments can be referred to mutually. Each embodiment focuses on describing the differences from other embodiments. In particular, the apparatus embodiments are basically similar to the method embodiments, so the description is relatively simple; relevant parts can be referred to the descriptions of the method embodiments.
[0164] The above are merely embodiments of this application and are not intended to limit the scope of this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of the claims of this application.
Claims
1. A method of managing data collection tasks, characterized by, The method includes: Acquire vehicle data collection scenarios, collection objects, and target vehicle models; Generate a task template for the vehicle data collection scenario based on the data collection object; The task template and the target vehicle model are used to generate a data collection task corresponding to the target vehicle model; The data acquisition task was tested on the target vehicle model. If the test passes, the data collection task will be published to the target vehicle model. The step of generating a data collection task corresponding to the target vehicle model using the task template and the target vehicle model includes: Generate the task ID, data acquisition trigger event, data acquisition frequency, and data upload frequency in the data acquisition task based on the task template; Based on the task template, the data collection target is determined, and the data collection instruction corresponding to the data collection target and the target vehicle model is obtained from the task version management database according to the target vehicle model; By combining the data acquisition instruction, the task ID, the data acquisition trigger event, the data acquisition frequency, and the data upload frequency, a data acquisition task corresponding to the target vehicle model can be obtained.
2. The method of claim 1, wherein, Also includes: Receive a self-check request from the vehicle, the self-check request including the vehicle model ID and task information for all the data acquisition tasks currently being performed on the vehicle, the task information including the task ID and the task version number; Read the vehicle's task configuration table based on the vehicle model ID; Add at least one data acquisition task's task ID from the task configuration table that is inactive to the first task update list; The comparison results are obtained by comparing the self-check request with the task version number corresponding to the same task ID in the task configuration table one by one using the task ID; Based on the comparison results, the task IDs that are different from the task version numbers corresponding to the self-check request and the task configuration table are placed into the second task update list, and the task status corresponding to the task ID placed in the second task update list is set to inactive. The first task update list and the second task update list are combined to obtain the task update list; The data collection tasks for the vehicle are updated based on the task update list.
3. The method of claim 2, wherein, The step of updating the vehicle's data collection task based on the task update list includes: Send a target task update request to the vehicle based on the target task ID in the task update list; Upon receiving the result of the target data acquisition task installation completion from the vehicle based on the target task update request, the current task status corresponding to the target task ID in the task update list is set to active.
4. The method of claim 1, wherein, Also includes: Acquire the first vehicle data collection scenario, the first collection object, and the first target vehicle model; Generate a first task template for the first vehicle data collection scenario based on the first collection object; Determine whether the first task template exists in the existing vehicle data scenario; If it exists, then determine whether the first target vehicle model is included in the vehicle model corresponding to the first task template in the existing vehicle data scenario; The generation result of the first data acquisition task corresponding to the first target vehicle model is determined based on the judgment result of whether or not the first target vehicle model is included.
5. The method according to claim 4, characterized in that, The step of determining the generation result of the first data acquisition task corresponding to the first target vehicle based on the judgment result of whether the first target vehicle is included includes: If the vehicle model corresponding to the first task template in the existing vehicle data scenario includes the first target vehicle model, then the data collection task corresponding to the first target vehicle model is obtained from the existing vehicle data collection scenario and used as the data collection task of the first target vehicle model in the first vehicle data collection scenario.
6. The method of claim 1, wherein, Also includes: Based on the new target vehicle model, obtain the existing vehicle data collection scenario, the second task template, and the new target vehicle model; A second data acquisition task corresponding to the new target vehicle model is generated using the second task template and the new target vehicle model. The second data acquisition task was tested on the vehicle of the new target model. If the test passes, the second data collection task will be sent to the vehicle of the new target model.
7. A data acquisition task management device, characterized in that, The device includes: The acquisition unit is used to acquire vehicle data collection scenarios, collection objects, and target vehicle models. The template generation unit is used to generate a task template for the vehicle data collection scenario based on the collection object. The task generation unit is used to generate a data acquisition task corresponding to the target vehicle model using the task template and the target vehicle model. The testing unit is used to test the data acquisition task on the target vehicle model. If the test passes, the release unit is triggered; The publishing unit is used to publish the data collection task to the target vehicle model. The task generation unit includes: Generate the task ID, data acquisition trigger event, data acquisition frequency, and data upload frequency in the data acquisition task based on the task template; Based on the task template, the data collection target is determined, and the data collection instruction corresponding to the data collection target and the target vehicle model is obtained from the task version management database according to the target vehicle model; By combining the data acquisition instruction, the task ID, the data acquisition trigger event, the data acquisition frequency, and the data upload frequency, a data acquisition task corresponding to the target vehicle model can be obtained.
8. An electronic device, comprising: Including memory and processor; The memory is used to store programs; The processor is used to execute the program to implement each step of the data acquisition task management method as claimed in any one of claims 1-6.
9. A readable storage medium, having stored thereon a computer program, characterized in that, When the computer program is executed by the processor, it implements each step of the data acquisition task management method as described in any one of claims 1-6.