Acquired data uploading method and device, electronic equipment, vehicle and program product

Abstract

The invention provides a collected data uploading method and device, electronic equipment, a vehicle and a program product, and is applied to the technical field of vehicles, and the collected data uploading method comprises the steps of obtaining a triggering strategy issued by a cloud, the trigger strategy comprises a function scene, a trigger formula corresponding to the function scene and an acquisition label corresponding to the function scene, the acquisition label corresponds to at least one acquisition channel, and each acquisition channel corresponds to one data source; acquiring acquisition data and a trigger signal corresponding to the function scene from each data source according to the acquisition label; and when the trigger signal satisfies a trigger formula, the collected data is stored as a file according to the collection label, and the file is uploaded to the cloud. When the trigger signal meets the trigger formula, the collected data can be placed into the file, and the data can be placed into the file based on the collection label in the process of placing into the file, so that repeated placing and returning of the data are avoided, and the vehicle end load and the bandwidth pressure are reduced.

Description

Technical Field

[0001] The present application relates to the field of vehicle technology, and in particular to a method, device, electronic device, vehicle and program product for uploading collected data. Background Art

[0002] In the autonomous driving system, by continuously iterating the algorithm model, a large number of uncommon or extreme driving scenarios (such as traffic accident scenes, abnormal obstacles, bad weather conditions or complex road conditions, etc.) can be gradually covered to ensure driving safety. In order to achieve rapid and effective iteration of the algorithm model, the autonomous driving data closed loop came into being; the data closed loop is a link that can be circulated, including data collection and storage on the cloud, model optimization, simulation testing, updated model deployment on the vehicle and other processes.

[0003] Data collection is a key point in the link, and the quality of collected data is one of the decisive factors for the effectiveness of model optimization. In order to cover complex scene data requirements, the amount of collected data is very large, including data from multiple cameras, radars, perception, location, chassis, vehicle status, intelligent driving status, etc. At the same time, the types of collected data are complex, and the formats of various data vary greatly, resulting in high vehicle-side load and bandwidth pressure. Summary of the invention

[0004] The purpose of the embodiments of the present application is to provide a method for solving the technical problem in the prior art that the amount of data to be collected is very large, resulting in high vehicle-side load and bandwidth pressure.

[0005] In a first aspect, an embodiment of the present application provides a method for uploading collected data, comprising: obtaining a trigger strategy issued by a cloud, wherein the trigger strategy includes a functional scenario, a trigger formula corresponding to the functional scenario, and a collection tag corresponding to the functional scenario, the collection tag corresponds to at least one collection channel, and each collection channel corresponds to a data source; obtaining collected data and a trigger signal corresponding to the functional scenario from each data source according to the collection tag; when the trigger signal satisfies the trigger formula, writing the collected data to a disk as a file according to the collection tag, and uploading the file to the cloud.

[0006] In the above scheme, the cloud can send a trigger strategy to the vehicle side, and the vehicle side can upload different collected data to the cloud under different functional scenarios based on the above trigger strategy, so as to quickly and efficiently upload the data required by the cloud. Specifically, when the trigger signal meets the trigger formula, the collected data can be written to the disk as a file. In the process of writing to the disk, the data can be written to the disk based on the collection tag, so as to avoid repeated writing and returning of data, and reduce the load and bandwidth pressure on the vehicle side.

[0007] In an optional implementation, the step of writing the collected data to disk as a file according to the collection tag includes: determining whether the collected data corresponding to the collection tag has been written to disk; if the collected data corresponding to the collection tag has not been written to disk, writing the collected data to disk as the file. In the above scheme, before writing the collected data to disk, it is possible to first determine whether the collected data corresponding to the collection tag has been written to disk, and write the collected data to disk if it has not been written to disk, thereby avoiding repeated writing and transmission of data to disk, and reducing vehicle-side load and bandwidth pressure.

[0008] In an optional implementation, the collection tag also corresponds to a priority, and uploading the file to the cloud includes: traversing the priorities corresponding to the multiple collection data respectively; uploading the files corresponding to the multiple collection data to the cloud in order from high to low priority. In the above scheme, in the process of uploading the files after being dropped to the disk to the cloud, priorities can be introduced, so that the files corresponding to the collection data can be uploaded to the cloud in order from high to low priority, so that when multiple trigger strategies are triggered at the same time, the key collection data can be uploaded first.

[0009] In an optional implementation, after obtaining the trigger strategy sent from the cloud, the method further includes: inserting the trigger strategy into at least one of a strategy data table, a collection data table, and a trigger signal data table; wherein the strategy data table is used to record data related to the trigger strategy, the collection data table is used to record data related to the collection tag, and the trigger signal data table is used to record trigger data related to the trigger signal. In the above scheme, a strategy data table, a collection data table, and a trigger signal data table can be introduced, wherein the strategy data table stores data related to the trigger strategy, the collection data table stores data related to the collection tag, and the trigger signal data table stores trigger data related to the trigger signal. When a new trigger strategy is sent from the cloud, the strategy data table, the collection data table, and the trigger signal data table can be updated.

[0010] In an optional implementation, the strategy data table includes the scenario name corresponding to the functional scenario, the trigger strategy ID corresponding to the trigger strategy, the trigger formula, the collection tag, and the collection channel.

[0011] In an optional implementation, the collection data table includes the scene name corresponding to the functional scene, the trigger strategy ID corresponding to the trigger strategy, the collection tag and the collection channel.

[0012] In an optional implementation, the trigger signal data table includes the scenario name corresponding to the functional scenario, the trigger strategy ID corresponding to the trigger strategy, the trigger formula and the trigger signal.

[0013] In an optional implementation, the method for uploading collected data further includes: when the state of the trigger signal has changed, updating the trigger signal state in a trigger signal state data table, wherein the trigger signal state data table is used to record data related to the trigger signal state. In the above scheme, a trigger signal state data table may be introduced, wherein the trigger signal state data table stores data related to the trigger signal state, and the trigger signal state data table may be updated when a new trigger strategy is issued by the cloud or when the trigger signal state changes.

[0014] In an optional implementation, the trigger signal status data table includes the scenario name corresponding to the functional scenario, the trigger strategy ID corresponding to the trigger strategy, the trigger signal, and the trigger signal status.

[0015] In an optional implementation, the method for uploading collected data further includes: when the trigger signal satisfies the trigger formula, or after the collected data is written to the disk as a file according to the collection tag, updating the trigger status in the policy status data table, wherein the policy status data table is used to record data related to the trigger status. In the above scheme, a policy status data table can be introduced, in which data related to the trigger status is stored, and the policy status data table can be updated when a new trigger policy is issued by the cloud or when the trigger status changes.

[0016] In an optional implementation, the policy status data table includes the scenario name corresponding to the functional scenario, the trigger policy ID corresponding to the trigger policy, and the trigger status.

[0017] In an optional embodiment, the method for uploading collected data further includes: after the collected data is written to the disk as a file according to the collected tag, the file address information corresponding to the file is inserted into the collected data file of the file upload data table, and the file upload data table is used to record data related to the collected data file; uploading the file to the cloud includes: uploading the corresponding file to the cloud according to the collected data file in the file upload data table, and deleting the file address information corresponding to the file from the collected data file in the file upload data table. In the above scheme, a file upload data table can be introduced, and the file upload data table stores data related to the collected data file. The file upload data table can be updated after the collected data is written to the disk as a file or after the file is uploaded to the cloud.

[0018] In an optional implementation, the file upload data table includes the scenario name corresponding to the functional scenario, the trigger strategy ID corresponding to the trigger strategy, the collection tag, and the collection data file.

[0019] In a second aspect, an embodiment of the present application provides an upload device for collected data, comprising: a policy management module, used to obtain a trigger policy issued by a cloud, wherein the trigger policy includes a functional scenario, a trigger formula corresponding to the functional scenario, and a collection tag corresponding to the functional scenario, the collection tag corresponds to at least one collection channel, and each collection channel corresponds to a data source; a data collection module, used to obtain the collected data corresponding to the functional scenario from each data source according to the collection tag; a trigger signal collection module, used to obtain the trigger signal corresponding to the functional scenario from each data source according to the collection tag; a state machine module, used to define different trigger states; a trigger condition analysis module, used to determine whether the trigger signal satisfies the trigger formula; a storage module, used to store the collected data as a file according to the collection tag when the trigger signal satisfies the trigger formula; and an upload module, used to upload the file to the cloud.

[0020] In the above scheme, the cloud can send a trigger strategy to the vehicle side, and the vehicle side can upload different collected data to the cloud under different functional scenarios based on the above trigger strategy, so as to quickly and efficiently upload the data required by the cloud. Specifically, when the trigger signal meets the trigger formula, the collected data can be written to the disk as a file. In the process of writing to the disk, the data can be written to the disk based on the collection tag, so as to avoid repeated writing and returning of data, and reduce the load and bandwidth pressure on the vehicle side.

[0021] In an optional implementation, the policy management module is also used to maintain the policy data table, the data acquisition module is also used to maintain the acquisition data table, the trigger signal acquisition module is also used to maintain the trigger signal data table, the state machine module is also used to maintain the policy state data table, the trigger condition analysis module is also used to maintain the trigger signal state data table, and the upload module is also used to maintain the upload data table. In the above scheme, each module is independent in function and each maintains its own data table, so as to facilitate future function iterations.

[0022] In a third aspect, an embodiment of the present application provides an electronic device, comprising: a processor and a memory; the memory stores computer program instructions that can be executed by the processor, and the processor calls the computer program instructions to execute the method for uploading collected data as described in the first aspect.

[0023] In a fourth aspect, an embodiment of the present application provides a vehicle, comprising the electronic device described in the second aspect.

[0024] In a fifth aspect, an embodiment of the present application provides a computer program product, which includes instructions. When the instructions are executed by a computer, the computer implements the method for uploading collected data as described in the first aspect.

[0025] In a sixth aspect, an embodiment of the present application provides a computer-readable storage medium, wherein the computer-readable storage medium stores computer program instructions. When the computer program instructions are executed by a computer, the computer executes the method for uploading collected data as described in the first aspect.

[0026] In order to make the above-mentioned objects, features and advantages of the present application more obvious and easy to understand, the following specifically cites the embodiments of the present application and describes them in detail with reference to the attached drawings. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0028] Figure 1 A flowchart of a method for uploading collected data provided in an embodiment of the present application; Figure 2 A schematic diagram of the structures of various data tables provided in the embodiments of the present application; Figure 3 A structural block diagram of a data collection and uploading system provided in an embodiment of the present application; Figure 4 A structural block diagram of a device for uploading collected data provided in an embodiment of the present application; Figure 5 A structural block diagram of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

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

[0030] Please refer to Figure 1 , Figure 1 The flowchart of a method for uploading collected data provided in an embodiment of the present application is provided. The method for uploading collected data can be applied to a vehicle end, and the vehicle end can communicate with the cloud. The method for uploading collected data provided in an embodiment of the present application may include the following steps: Step S101: Obtain the trigger strategy sent from the cloud, wherein the trigger strategy includes a functional scenario, a trigger formula corresponding to the functional scenario, and a collection tag corresponding to the functional scenario, the collection tag corresponds to at least one collection channel, and each collection channel corresponds to a data source.

[0031] Step S102: Acquire the collected data and trigger signals corresponding to the functional scenarios from various data sources according to the collected tags.

[0032] Step S103: When the trigger signal satisfies the trigger formula, the collected data is saved to the disk as a file according to the collection tag, and the file is uploaded to the cloud.

[0033] Specifically, in the above step S101, the trigger strategy may include a functional scenario, a trigger formula corresponding to the functional scenario, and a collection tag corresponding to the functional scenario, wherein each functional scenario corresponds to a different scenario name and a different scenario ID, and each scenario name and scene ID corresponds to a trigger formula.

[0034] Functional scenarios are used to define different driving scenarios, such as: Navigation on Autopilot (NOA), Automated Valet Parking (AVP), Autonomous Emergency Braking (AEB), Sentry mode (Sentry), Forward Collision Warning (FCW), etc.

[0035] The trigger formula generally includes a trigger signal and a signal condition. The trigger signal can be obtained by communicating with the data source, and the signal condition is used to compare with the trigger signal to determine whether the trigger signal satisfies the trigger formula. For example, a trigger formula corresponding to an AEB_FCW function scenario can be expressed as: AEB_FCW_CONDITION = ( (aebFunctionSts>0)&&( (aebWarningSts==2) || (aebWarningSts==3) ) ), where aebFunctionSts and aebWarningSts are the names of two trigger signals respectively; the above trigger formula indicates that if the AEB function is already in an activated or ready state (ie, aebFunctionSts is greater than 0), and a certain level of collision risk is detected (ie, aebWarningSts is equal to 2 or 3), then the AEB_FCW function scenario is triggered.

[0036] The trigger strategy can also include the data type of acquisition, each of which corresponds to a type of acquisition device, such as camera, radar, perception, location, chassis, vehicle status, intelligent driving status and other data types. Each acquisition data type can include at least one acquisition tag, each acquisition tag corresponds to at least one acquisition channel, and each acquisition channel corresponds to a data source. For example, for the camera acquisition data type, it can correspond to the acquisition tag Camera_A and the acquisition tag Camera_B. The acquisition tag Camera_A corresponds to camera A, and the acquisition tag Camera_B corresponds to camera B.

[0037] In the above step S102, the vehicle side can establish a communication connection with the corresponding data source based on the collection tag, so as to obtain the collection data and trigger signal corresponding to the functional scenario from each data source. The collection data is used to store the data in a file and upload it to the cloud, and the trigger signal is used to compare with the trigger formula to determine whether the collection data needs to be uploaded.

[0038] In the above step S103, the vehicle side can compare the trigger signal with the trigger formula to determine whether the trigger signal satisfies the trigger formula. When the trigger signal satisfies the trigger formula, the vehicle side can save the collected data to the disk as a file according to the collection tag and upload the file to the cloud.

[0039] In the above scheme, the cloud can send a trigger strategy to the vehicle side, and the vehicle side can upload different collected data to the cloud under different functional scenarios based on the above trigger strategy, so as to quickly and efficiently upload the data required by the cloud. Specifically, when the trigger signal meets the trigger formula, the collected data can be written to the disk as a file. In the process of writing to the disk, the data can be written to the disk based on the collection tag, so as to avoid repeated writing and returning of data, and reduce the load and bandwidth pressure on the vehicle side.

[0040] Further, based on the above embodiment, the step of writing the collected data to a disk as a file according to the collection tag in the above step S103 may specifically include the following steps: Step 1) Determine whether the collected data corresponding to the collection tag has been saved to the disk.

[0041] Step 2), if the collected data corresponding to the collection tag has not been saved to the disk, the collected data will be saved to the disk as a file.

[0042] As an implementation method, a list of tags that have been written to disk can be defined; all currently triggered trigger policies are traversed, and then all collection tags of each trigger policy are traversed; it is determined whether the collection data corresponding to each collection tag has been written to disk; if the collection data corresponding to the collection tag has not been written to disk, the collection data is written to disk as a file; the collection tags that have been written to disk are added to the list of tags that have been written to disk.

[0043] In the above scheme, before the collected data is written to the disk, it is possible to first determine whether the collected data corresponding to the collection tag has been written to the disk, and then write the collected data to the disk if it has not been written to the disk, thereby avoiding repeated writing and returning of data and reducing the vehicle-side load and bandwidth pressure.

[0044] Further, based on the above embodiment, the collection tag may also correspond to a priority. In this case, the step of uploading the file to the cloud in the above step S103 may specifically include the following steps: Step 1), traverse the priorities corresponding to multiple collected data.

[0045] Step 2) Upload the files corresponding to the multiple collected data to the cloud in order of priority from high to low.

[0046] As an implementation method, a priority-disk label file map is defined; all currently stored collection labels are traversed; priority-disk label file pairs are added to the map; the disk label files are uploaded in sequence according to the priority; after uploading all the disk files, the map is cleared.

[0047] In the above scheme, in the process of uploading the files after being dropped to the disk to the cloud, priorities can be introduced, so that the files corresponding to the collected data can be uploaded to the cloud in order from high to low priority, so that when multiple trigger strategies are triggered at the same time, key collected data can be uploaded first.

[0048] Further, based on the above embodiments, the present application also provides a variety of data tables, including: strategy data table table_strategy, acquisition data table table_capture_data, trigger signal data table table_capture_signal, trigger signal status data table table_signal_status, strategy status data table table_strategy_state and file upload data table table_upload_file. Please refer to Figure 2 , Figure 2 The following is a schematic diagram of the structures of various data tables provided in the embodiments of the present application. The above-mentioned various data tables are introduced in turn below.

[0049] The strategy data table table_strategy can be used to record data related to the trigger strategy. As an implementation method, the above may include the scenario name corresponding to the functional scenario, the trigger strategy ID corresponding to the trigger strategy, the trigger formula, the collection tag, and the collection channel. At this time, after the above step S101, the method for uploading the collected data provided in the embodiment of the present application may also include the following steps: Insert the trigger policy into the policy data table.

[0050] Specifically, the vehicle side creates a strategy data table table_strategy, and after parsing the collection strategy sent by the cloud, the collection strategy can be inserted into the strategy data table table_strategy; wherein, when the cloud sends a new collection strategy, the strategy data table table_strategy can be updated.

[0051] In addition, the strategy data table table_strategy may also include upload priorities.

[0052] In the above solution, a policy data table may be introduced, in which data related to the trigger policy is stored. The policy data table may be updated when a new trigger policy is issued from the cloud.

[0053] The acquisition data table table_capture_data can be used to record data related to the acquisition tag. As an implementation, the above-mentioned acquisition data table may include the scene name corresponding to the functional scene, the trigger strategy ID corresponding to the trigger strategy, the acquisition tag, and the acquisition channel. At this time, after the above-mentioned step S101, the method for uploading the acquisition data provided in the embodiment of the present application may also include the following steps: Insert the trigger strategy into the acquisition data table.

[0054] Specifically, the vehicle side may create a collection data table table_capture_data during initialization, wherein the collection data table table_capture_data may be updated synchronously when the strategy data table table_strategy is updated.

[0055] In the above solution, a collection data table may be introduced, in which data related to the collection tags are stored. The collection data table may be updated when a new trigger strategy is issued from the cloud.

[0056] The trigger signal data table table_capture_signal can be used to record trigger data related to the trigger signal. As an implementation, the trigger signal data table may include a scene name corresponding to the functional scene, a trigger strategy ID corresponding to the trigger strategy, a trigger formula, and a trigger signal. At this time, after the above step S101, the method for uploading the collected data provided in the embodiment of the present application may also include the following steps: Insert the trigger strategy into the trigger signal data table.

[0057] Specifically, the vehicle side can create a trigger signal data table table_capture_signal during initialization, and synchronously update the trigger signal data table table_capture_signal when the strategy data table table_strategy is updated.

[0058] In the above solution, a trigger signal data table may be introduced, in which data related to the trigger signal is stored. The trigger signal data table may be updated when a new trigger strategy is issued from the cloud.

[0059] The trigger signal status data table table_signal_status can be used to record data related to the trigger signal status. As an implementation, the trigger signal status data table may include a scene name corresponding to the functional scene, a trigger strategy ID corresponding to the trigger strategy, a trigger signal, and a trigger signal status. At this time, after the above step S102, the method for uploading collected data provided in the embodiment of the present application may also include the following steps: When the state of the trigger signal changes, the trigger signal state in the trigger signal state data table is updated.

[0060] Specifically, the vehicle side may create a trigger signal status data table table_signal_status during initialization, wherein the trigger signal status data table table_signal_status is synchronously updated when the strategy data table table_strategy is updated, or the trigger signal status data table table_signal_status is updated when the trigger signal status changes.

[0061] In the above scheme, a trigger signal status data table may be introduced, in which data related to the trigger signal status is stored. The trigger signal status data table may be updated when a new trigger strategy is issued by the cloud or when the trigger signal status changes.

[0062] The strategy state data table table_strategy_state can be used to record data related to the trigger state. As an implementation method, the above-mentioned strategy state data table may include the scenario name corresponding to the functional scenario, the trigger strategy ID corresponding to the trigger strategy, and the trigger state; when the trigger signal satisfies the trigger formula, or after the step of writing the collected data to the disk as a file according to the collection tag in the above-mentioned step S103, the method for uploading collected data provided in the embodiment of the present application may also include the following steps: Update the trigger status in the policy status data table.

[0063] Specifically, the vehicle side can create a strategy state data table table_strategy_state during initialization, synchronously update the strategy state data table table_strategy_state when the strategy data table table_strategy is updated, or update the strategy state data table table_strategy_state when a state change is triggered.

[0064] In the above solution, a policy status data table may be introduced, in which data related to the trigger status is stored. The policy status data table may be updated when a new trigger policy is issued by the cloud or when the trigger status changes.

[0065] The file upload data table table_upload_file can be used to record data related to the collected data file. As an implementation method, the above-mentioned file upload data table may include the scene name corresponding to the functional scene, the trigger strategy ID corresponding to the trigger strategy, the collection tag, and the collected data file. After the step of writing the collected data to the disk as a file according to the collection tag in the above-mentioned step S103, the method for uploading collected data provided in the embodiment of the present application may also include the following steps: Insert the file address information corresponding to the file into the collected data file of the file upload data table.

[0066] After uploading the file to the cloud in step S103, the method for uploading collected data provided in the embodiment of the present application may further include the following steps: Upload the corresponding file to the cloud according to the collected data file in the file upload data table, and delete the file address information corresponding to the file from the collected data file in the file upload data table.

[0067] Specifically, the vehicle side can create a file upload data table table_upload_file during initialization; when a trigger policy is triggered, the collected data is written to the disk, and a current trigger policy upload record is inserted in the file upload data table table_upload_file. When the data upload is completed, this record is deleted from the file upload data table table_upload_file.

[0068] In addition, the file upload data table table_upload_file may also include an upload priority.

[0069] In the above solution, a file upload data table may be introduced, in which data related to the collected data file is stored. The file upload data table may be updated after the collected data is saved to a disk as a file or after the file is uploaded to the cloud.

[0070] Please refer to Figure 3 , Figure 3 This is a structural block diagram of a data collection upload system provided in an embodiment of the present application, and the data collection upload system includes a cloud, a gateway, and a vehicle. The cloud includes a cloud policy configuration center and a cloud data center; the cloud policy configuration center includes functions such as configuring policies and issuing policies, and the cloud data center is mainly used to receive data uploaded by the vehicle, and classify and label the data.

[0071] The vehicle side includes a vehicle side collector, a vehicle side trigger, and a vehicle side upload service. Among them, the vehicle side collector receives data from various data sources on the vehicle side (for example: data source A, data source B, data source N) through various communication protocols; the vehicle side trigger receives the trigger signal source, performs semantic analysis on the trigger formula through the trigger parser, and stores the analysis result, i.e., the trigger status, in the trigger status queue; the vehicle side upload service manages files, obtains the triggered strategy from the trigger status queue, stores the collected data of the strategy on the disk, and stores the files in the upload queue after the data is stored on the disk. The upload thread continuously uploads the collected data files in the upload queue to the cloud through encrypted communication.

[0072] Please refer to Figure 4 , Figure 4 A structural block diagram of a data collection upload device provided in an embodiment of the present application. The data collection upload device is applied to the vehicle side and may include the following modules: a cloud policy configuration center, a cloud data center, a gateway, a policy management module, a data collection module, a trigger signal collection module, a state machine module, a trigger condition analysis module, a storage module and an upload module.

[0073] Specifically, the cloud policy configuration center is used for scene configuration, collection tag configuration, collection channel configuration, policy display, collection policy configuration and collection policy distribution; the cloud data center is used for data display, data mining, data query and receiving data uploaded by the vehicle.

[0074] The strategy management module Strategy Manager is used to obtain collection strategies, analyze collection strategies, save configuration files to disk, and manage strategy data tables. The trigger strategy includes functional scenarios, trigger formulas corresponding to functional scenarios, and collection tags corresponding to functional scenarios. The collection tags correspond to at least one collection channel, and each collection channel corresponds to a data source.

[0075] The data acquisition module Data Capture is used to manage the acquisition data table and establish data acquisition channels 1...n, wherein the acquisition data corresponding to the functional scenario can be obtained from various data sources according to the acquisition tags.

[0076] The trigger signal acquisition module Signal Capture is used to manage the trigger signal data table and establish trigger signal acquisition channels 1...n, wherein the trigger signal corresponding to the functional scenario can be obtained from various data sources according to the acquisition label.

[0077] The state machine module State Machine is used to define the policy trigger state machine and manage the policy state data table. The different trigger states include: initialization, capturing, saving, saved, uploading, uploaded and other states.

[0078] The trigger condition parsing module Condition Parser is used to manage the trigger signal status data table and the policy trigger condition semantic analysis to determine whether the trigger signal satisfies the trigger formula.

[0079] The storage module is used to store the collected data as a file according to the collection tag when the trigger signal meets the trigger formula. As an implementation method, when the policies triggered at the same time have repeated label data, the label data is only stored once to avoid repeated storage and transmission of data, reducing the vehicle-side load and bandwidth pressure.

[0080] The upload module Uploader is used to manage the upload data table and upload the collected files to the cloud through encrypted communication. As an implementation method, the collection tag is used to upload a list of files to be uploaded with a higher priority, and key tag data is uploaded first.

[0081] In the above scheme, the cloud can send a trigger strategy to the vehicle side, and the vehicle side can upload different collected data to the cloud under different functional scenarios based on the above trigger strategy, so as to quickly and efficiently upload the data required by the cloud. Specifically, when the trigger signal meets the trigger formula, the collected data can be written to the disk as a file. In the process of writing to the disk, the data can be written to the disk based on the collection tag, so as to avoid repeated writing and returning of data, and reduce the load and bandwidth pressure on the vehicle side.

[0082] Furthermore, based on the above embodiments, the strategy management module Strategy Manager is also used to maintain the strategy data table table_strategy, the data acquisition module Data Capture is also used to maintain the acquisition data table table_capture_data, the trigger signal acquisition module Signal Capture is also used to maintain the trigger signal data table table_strategy_signal, the state machine module State Machine is also used to maintain the strategy status data table table_strategy_state, the trigger condition parsing module Condition Parser is also used to maintain the trigger signal status data table table_signal_status, and the upload module Uploader is also used to maintain the upload data table table_upload_file.

[0083] In the above solution, each module has independent functions and maintains its own data table, which facilitates future function iterations.

[0084] The following takes issuing two AEB strategies as an example to introduce the method for uploading collected data provided in the embodiment of the present application.

[0085] Step 1): The cloud sends a collection strategy to the vehicle. For example, two AEB collection strategies are sent: AEB_A and AEB_B.

[0086] Step 2), the strategy management module Strategy Manager in the vehicle-side trigger completes initialization, actively obtains the collection strategy, creates a strategy data table table_strategy, and inserts the current strategy information according to the collection strategy. For example, when sending two AEB collection strategies AEB_A and AEB_B information, the strategy data table table_strategy is as shown in Table 1.

[0087]

[0088] Table 1 Strategy data table table_strategy Step 3), the data acquisition module Data Capture in the vehicle-side collector completes initialization, creates a collection data table table_capture_data, and inserts the collection data information according to the vehicle collection strategy. For example, when two AEB collection strategies AEB_A and AEB_B are issued, the collection data table table_capture_data is as shown in Table 2.

[0089]

[0090] Table 2 Collection data table table_capture_data Step 4), the data acquisition module Data Capture establishes connections with various data sources and continuously receives and collects data.

[0091] Step 5), the upload module Uploader in the vehicle upload service completes initialization and creates a file upload data table table_upload_file. For example, when two AEB acquisition strategies AEB_A and AEB_B are issued, the upload data table table_upload_file is shown in Table 3.

[0092]

[0093] Table 3 Upload data table table_upload_file Step 6), the state machine module State Machine in the vehicle-side trigger creates a strategy state data table table_strategy_state and sets the current strategy state to init. For example, when two AEB acquisition strategies AEB_A and AEB_B are issued, the strategy state data table table_strategy_state is as shown in Table 4.

[0094]

[0095] Table 4 Strategy state data table table_strategy_state Step 7), the trigger signal acquisition module Signal Capture in the vehicle-side trigger creates a trigger signal data table table_capture_signal data table, and inserts the current strategy trigger signal information according to the vehicle acquisition strategy. For example, when two AEB acquisition strategies AEB_A and AEB_B are issued, the trigger signal data table table_capture_signal is as shown in Table 5.

[0096]

[0097] Table 5 Trigger signal data table table_capture_signal Step 8), the trigger condition parsing module CondtionParser in the vehicle-side trigger creates the trigger signal status data table table_signal_status and sets the default value of the trigger signal. For example, when two AEB acquisition strategies AEB_A and AEB_B are issued, the trigger signal status data table table_signal_status is as shown in Table 6.

[0098]

[0099] Table 6 Trigger signal status data table table_signal_status Step 9), the above modules in the vehicle-side trigger complete initialization, establish connections with various data sources, and continue to receive trigger signals.

[0100] Step 10), the vehicle-side trigger updates the trigger signal status data table table_signal_status according to the received trigger signal value. When the received trigger signal warningSts is 1, the trigger signal status data table table_signal_status is updated as shown in Table 7.

[0101]

[0102] Table 7 Updated trigger signal status data table table_signal_status Step 11), the vehicle-side trigger continuously determines whether the strategy trigger condition is met, and updates the strategy state data table table_strategy_state when the trigger formula analysis result is true. For example: when the trigger signal warningSts is 1, the analysis results of the trigger formula (aebSts==1)||(warningSts==1) corresponding to the acquisition strategy AEB_A and the trigger formula (aebSts==2)||(warningSts==1) corresponding to the acquisition strategy AEB_B are both true, and the strategy state data table table_strategy_state is updated as shown in Table 8.

[0103]

[0104] Table 8 Updated strategy state data table table_strategy_state Step 12), the vehicle-side trigger notifies the vehicle-side collector to write the collected data of the collection strategy to the disk as a file and update the strategy state data table_strategy_state. For example: when AEB_A and AEB_B both meet the trigger conditions, since AEB_A and AEB_B both have the collection tag Camera, the Camera-related collection channels AEB_A_Camera_A.record and AEB_A_Camera_B.record of AEB_A are written to the disk, and the Camera-related collection channels AEB_B_Camera_A.record and AEB_B_Camera_B.record of AEB_B are not written to the disk to avoid repeated data being written to the disk. The collected data files are shown in Tables 9 and 10.

[0105] When the collection is finished and the disk is started, the update status is as follows.

[0106]

[0107] Table 9: Strategy status data table table_strategy_state when the collection ends and the disk starts The update status after the disk placement is completed is as follows.

[0108]

[0109] Table 10 Strategy status data table at the end of the transaction table_strategy_state Step 13), after the vehicle-side collector finishes storing the data on disk, the vehicle-side upload service updates the upload data table table_upload_file, and updates the disk file address information corresponding to each collection channel of the trigger strategy, which is used for the upload service to upload the file, for example: updating the upload data table table_upload_file as shown in Table 11.

[0110]

[0111] Table 11 Updated upload data table table_upload_file Step 14), the vehicle upload service uploads the disk file of the trigger strategy collection data to the cloud according to the file priority. For example: when both AEB_A and AEB_B meet the trigger conditions, since AEB_A has a higher upload priority 1, the disk file of AEB_A is uploaded first. When the upload starts, the strategy state data table table_strategy_state is as shown in Table 12.

[0112]

[0113] Table 12: Strategy state data table when starting to upload table_strategy_state At the end of uploading, the strategy state data table table_strategy_state is as shown in Table 13.

[0114]

[0115] Table 13 Strategy status data table at the end of upload table_strategy_state Step 15), the cloud receives the vehicle-side trigger strategy to collect uploaded data.

[0116] Please refer to Figure 5 , Figure 5The structural block diagram of an electronic device provided in an embodiment of the present application, the electronic device 500 includes: at least one processor 501, at least one communication interface 502, at least one memory 503 and at least one communication bus 504. Among them, the communication bus 504 is used to realize the direct connection and communication of these components, the communication interface 502 is used to communicate signaling or data with other node devices, and the memory 503 stores machine-readable instructions executable by the processor 501. When the electronic device 500 is running, the processor 501 communicates with the memory 503 through the communication bus 504, and the machine-readable instructions are called by the processor 501 to execute the above-mentioned method for uploading collected data.

[0117] For example, the processor 501 of the embodiment of the present application reads a computer program from the memory 503 through the communication bus 504 and executes the computer program to implement the following method: Step S101: Obtain the trigger strategy issued by the cloud, wherein the trigger strategy includes a functional scenario, a trigger formula corresponding to the functional scenario, and a collection tag corresponding to the functional scenario, and the collection tag corresponds to at least one collection channel, and each collection channel corresponds to a data source. Step S102: Obtain the collection data and trigger signal corresponding to the functional scenario from each data source according to the collection tag. Step S103: When the trigger signal satisfies the trigger formula, the collected data is stored as a file according to the collection tag, and the file is uploaded to the cloud.

[0118] The processor 501 includes one or more, which may be an integrated circuit chip with signal processing capability. The above-mentioned processor 501 may be a general-purpose processor, including a central processing unit (CPU), a microcontroller unit (MCU), a network processor (NP), or other conventional processors; it may also be a dedicated processor, including a neural network processor (NPU), a graphics processor (GPU), a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components. Moreover, when there are multiple processors 501, some of them may be general-purpose processors, and the other part may be dedicated processors.

[0119] The memory 503 includes one or more, which may be, but not limited to, a random access memory (RAM), a read only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), etc.

[0120] Understandably, Figure 5 The structure shown is for illustration only. The electronic device 500 may also include Figure 5 More or fewer components as shown, or with Figure 5 Different configurations shown. Figure 5 Each component shown in can be implemented by hardware, software or a combination thereof. In the embodiment of the present application, the electronic device 500 can be, but is not limited to, a physical device such as a desktop computer, a laptop computer, a smart phone, a smart wearable device, a vehicle-mounted device, etc., and can also be a virtual device such as a virtual machine. In addition, the electronic device 500 is not necessarily a single device, but can also be a combination of multiple devices, such as a server cluster, etc.

[0121] The method in the present application can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented by software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer programs or instructions. When the computer program or instruction is loaded and executed on a computer, the process or function described in the present application is executed in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, a network device, a user device, a core network device, an OAM or other programmable device.

[0122] The computer program or instructions may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer program or instructions may be transmitted from one website, computer, server or data center to another website, computer, server or data center by wired or wireless means. The computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server or data center that integrates one or more available media. The available medium may be a magnetic medium, such as a floppy disk, a hard disk, or a magnetic tape; it may also be an optical medium, such as a digital video disk; it may also be a semiconductor medium, such as a solid-state drive. The computer-readable storage medium may be a volatile or non-volatile storage medium, or may include both volatile and non-volatile types of storage media.

[0123] An embodiment of the present application also provides a vehicle, comprising the electronic device of the aforementioned embodiment.

[0124] The embodiment of the present application further provides a computer-readable storage medium, wherein the computer-readable storage medium stores computer program instructions. When the computer program instructions are executed by a computer, the computer executes the method for uploading collected data described in the aforementioned method embodiment.

[0125] In the embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. The device embodiments described above are merely schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some communication interfaces, and the indirect coupling or communication connection of the devices or units can be electrical, mechanical or other forms.

[0126] In addition, the units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0127] Furthermore, the functional modules in the various embodiments of the present application may be integrated together to form an independent part, or each module may exist separately, or two or more modules may be integrated to form an independent part.

[0128] It should be noted that if the function is implemented in the form of a software function module and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium, including a number of instructions to enable a computer device (which can be a personal computer, server, or network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), disk or optical disk, and other media that can store program codes.

[0129] In this document, relational terms such as first and second, etc. are used merely to distinguish one entity or operation from another entity or operation, but do not necessarily require or imply any such actual relationship or order between these entities or operations.

[0130] The above description is only an embodiment of the present application and is not intended to limit the protection scope of the present application. For those skilled in the art, the present application may have various modifications and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application shall be included in the protection scope of the present application.

Claims

1. A method for uploading collected data, It is characterized in that include: Obtaining a trigger strategy issued by the cloud, wherein the trigger strategy includes a functional scenario, a trigger formula corresponding to the functional scenario, and a collection tag corresponding to the functional scenario, the collection tag corresponds to at least one collection channel, and each collection channel corresponds to a data source; Acquire the collected data and trigger signal corresponding to the functional scenario from various data sources according to the collected tags; When the trigger signal satisfies the trigger formula, the collected data is written to the disk as a file according to the collection tag, and the file is uploaded to the cloud.

2. The method for uploading collected data according to claim 1, It is characterized in that The step of storing the collected data into a file according to the collected tag includes: Determine whether the collected data corresponding to the collection tag has been saved to the disk; If the collected data corresponding to the collection tag has not been saved to the disk, the collected data is saved to the disk as the file.

3. The method for uploading collected data according to claim 1, It is characterized in that The collection tag also corresponds to a priority, and uploading the file to the cloud includes: Traversing the priorities respectively corresponding to the plurality of collected data; Upload multiple files corresponding to the collected data to the cloud in order of priority from high to low.

4. The method for uploading collected data according to any one of claims 1 to 3, It is characterized in that After obtaining the trigger strategy sent from the cloud, the method further includes: Inserting the trigger strategy into at least one of a strategy data table, an acquisition data table, and a trigger signal data table; The strategy data table is used to record data related to the trigger strategy, the acquisition data table is used to record data related to the acquisition tag, and the trigger signal data table is used to record trigger data related to the trigger signal.

5. The method for uploading collected data according to any one of claims 1 to 3, It is characterized in that The method further comprises: When the state of the trigger signal has changed, updating the state of the trigger signal in a trigger signal state data table, wherein the trigger signal state data table is used to record data related to the state of the trigger signal; or, When the trigger signal satisfies the trigger formula, or after the collected data is written to the disk as a file according to the collection tag, the trigger state in the policy state data table is updated, and the policy state data table is used to record data related to the trigger state.

6. The method for uploading collected data according to any one of claims 1 to 3, It is characterized in that The method further comprises: After the collected data is written to a disk as a file according to the collection tag, the file address information corresponding to the file is inserted into the collected data file of the file upload data table, and the file upload data table is used to record data related to the collected data file; The uploading the file to the cloud comprises: According to the collected data file in the file upload data table, the corresponding file is uploaded to the cloud, and the file address information corresponding to the file is deleted from the collected data file in the file upload data table.

7. A device for uploading collected data, It is characterized in that include: A policy management module, used to obtain a trigger policy issued by the cloud, wherein the trigger policy includes a functional scenario, a trigger formula corresponding to the functional scenario, and a collection tag corresponding to the functional scenario, wherein the collection tag corresponds to at least one collection channel, and each collection channel corresponds to a data source; A data collection module, used to obtain the collection data corresponding to the functional scenario from various data sources according to the collection tags; A trigger signal acquisition module, used to acquire a trigger signal corresponding to the functional scenario from various data sources according to the acquisition tag; State machine module, used to define different trigger states; A trigger condition analysis module, used to determine whether the trigger signal satisfies the trigger formula; A storage module, configured to store the collected data into a disk as a file according to the collection tag when the trigger signal satisfies the trigger formula; The upload module is used to upload the file to the cloud.

8. The device for uploading collected data according to claim 7, It is characterized in that The policy management module is also used to maintain the policy data table, the data acquisition module is also used to maintain the acquisition data table, the trigger signal acquisition module is also used to maintain the trigger signal data table, the state machine module is also used to maintain the policy status data table, the trigger condition analysis module is also used to maintain the trigger signal status data table, and the upload module is also used to maintain the upload data table.

9. An electronic device, It is characterized in that include: Processor and memory; The memory stores computer program instructions that can be executed by the processor, and the processor calls the computer program instructions to execute the method for uploading collected data as described in any one of claims 1 to 6.

10. A vehicle, It is characterized in that Comprising the electronic device as claimed in claim 9.

11. A computer program product, It is characterized in that The computer program product includes instructions, and when the instructions are executed by a computer, the computer implements the method for uploading collected data according to any one of claims 1 to 6.

Images