Data backhaul control method and apparatus, vehicle, storage medium, and program product

Abstract

The application relates to the technical field of vehicles, in particular to a data backhaul control method and device, a vehicle, a storage medium and a program product, wherein the method comprises the following steps: obtaining a trigger strategy file of a target vehicle; triggering at least one target scene according to trigger logic of a scene in the trigger strategy file, and obtaining data information of the at least one target scene triggered within a preset time; and controlling data backhaul of the at least one target scene according to the data information. Therefore, the problems that data backhaul cannot be adaptively adjusted according to requirements in the related art, and that too much backhaul data affects the generalization of cloud data are solved.

Description

Technical Field

[0001] This application relates to the field of vehicle technology, and in particular to a control method, device, vehicle, storage medium, and program product for data transmission. Background Technology

[0002] As intelligent driving gradually transitions from L2 to L3, intelligent driving scenarios are becoming increasingly complex, posing a risk of insufficient test and verification datasets and omissions in perception training datasets.

[0003] Currently, automakers and intelligent driving suppliers are all using data feedback to collect corner case scenarios. This data feedback process acquires scenario video data and vehicle control data, and through cloud data processing, a more comprehensive set of test scenarios and perception training datasets are constructed.

[0004] Data transmission involves sensitive image information, location information, and trajectory information. Before uploading, the data needs to be de-identified, encrypted, and packaged on the vehicle side. Then, it needs to be uploaded via a VPN (Virtual Private Network) dedicated line. The data is obtained from the cloud and stored in the map provider's proprietary classified data center. Afterward, the data is processed and analyzed by dedicated personnel in the classified data center. This process is costly, and the upload speed is limited by the bandwidth of the communication service provider. Data that cannot be uploaded to the vehicle side in a timely manner will be discarded.

[0005] Currently, most automakers or intelligent driving suppliers use data backhaul mechanisms that trigger data backhaul through specific rules. However, these triggering rules cannot be updated in a timely manner and can only be updated by following the software OTA (Over-the-Air Technology) of the intelligent driving domain controller. Furthermore, they cannot quickly adjust the data backhaul according to the demand for backhauled data, meaning they cannot adaptively adjust the data backhaul. This results in too much backhauled data being received by the cloud, affecting the generalization of cloud data. Summary of the Invention

[0006] This application provides a control method, device, vehicle, storage medium, and program product for data backhaul, in order to solve the problems in related technologies such as the inability to adaptively adjust data backhaul according to demand, resulting in a large amount of backhauled data affecting the generalization of cloud data.

[0007] The first aspect of this application provides a data backhaul control method, comprising the following steps: obtaining a triggering strategy file of a target vehicle; triggering at least one target scenario according to the triggering logic of the scenario in the triggering strategy file, and obtaining data information of the at least one target scenario being triggered within a preset time; and controlling the data backhaul of at least one target scenario according to the data information.

[0008] Optionally, the data information includes at least one of the following: the number of times the target scenario is triggered, the geographical location when the target scenario is triggered, the time interval between the triggering of the target scenario, and driver information when the target scenario is triggered.

[0009] Optionally, before controlling the data feedback of the target scenario based on the data information, the method further includes: summarizing the data information to obtain the number of times the target scenario is triggered, the radius of the distribution range of the preset number of times the target scenario is triggered, the time interval of the preset number of times the target scenario is triggered, the driver information when the target scenario is triggered, and the danger level of the target scenario.

[0010] Optionally, controlling the data feedback of at least one target scenario based on data information includes: stopping the data feedback of at least one target scenario if the number of triggers is greater than or equal to a preset number, the distribution radius is less than or equal to a preset radius, the interval time is less than or equal to a preset time, the driver information is the same or different, and the danger level is greater than or equal to the first level; stopping the data feedback of at least one target scenario if the number of triggers is greater than or equal to a preset number, the distribution radius is greater than or equal to a preset radius, the interval time is less than or equal to a preset time, the driver information is the same or different, and the danger level is greater than or equal to the first level; stopping the data feedback of at least one target scenario if the number of triggers is greater than or equal to a preset number, the distribution radius is less than a preset radius, the interval time is less than or equal to a preset time, the driver information is different or the same, and the danger level is less than or equal to the second level; otherwise, maintaining the data feedback of at least one target scenario.

[0011] Optionally, the trigger strategy file for the target vehicle can be obtained, including: obtaining the vehicle model of the target vehicle; and matching the trigger strategy file according to the vehicle model.

[0012] Optionally, before obtaining the trigger strategy file of the target vehicle, the method further includes: detecting the version of the trigger strategy file of the target vehicle; if the version is not the latest version, downloading the latest version of the trigger strategy file of the target vehicle from the cloud, wherein the trigger strategy file includes trigger strategies for multiple scenarios, and the update of the trigger strategy file supports the individual update of the trigger strategies for multiple scenarios.

[0013] A second aspect of this application provides a control device for data backhaul, comprising: an acquisition module for acquiring a triggering strategy file of a target vehicle; a triggering module for triggering at least one target scenario according to the triggering logic in the triggering strategy file, and acquiring data information of at least one target scenario being triggered within a preset time; and a control module for controlling the data backhaul of at least one target scenario according to the data information.

[0014] Optionally, the data information includes at least one of the following: the number of times the target scenario is triggered, the geographical location when the target scenario is triggered, the time interval between the triggering of the target scenario, and driver information when the target scenario is triggered.

[0015] Optionally, it also includes: a summarization module, used to summarize the data information before controlling the data feedback of the target scenario based on the data information, to obtain the number of times the target scenario is triggered, the radius of the distribution range of the preset number of times the target scenario is triggered, the time interval of the preset number of times the target scenario is triggered, the driver information when the target scenario is triggered, and the danger level of the target scenario.

[0016] Optionally, the control module is further configured to: stop data transmission for at least one target scenario if the number of triggers is greater than or equal to a preset number, the distribution radius is less than or equal to a preset radius, the interval time is less than or equal to a preset time, the driver information is the same or different, and the danger level is greater than or equal to the first level; stop data transmission for at least one target scenario if the number of triggers is greater than or equal to a preset number, the distribution radius is greater than or equal to a preset radius, the interval time is less than or equal to a preset time, the driver information is the same or different, and the danger level is greater than or equal to the first level; stop data transmission for at least one target scenario if the number of triggers is greater than or equal to a preset number, the distribution radius is less than a preset radius, the interval time is less than or equal to a preset time, the driver information is different or the same, and the danger level is less than or equal to the second level; otherwise, maintain data transmission for at least one target scenario.

[0017] Optionally, the acquisition module is further configured to: acquire the triggering strategy file of the target vehicle, including: acquiring the vehicle model of the target vehicle; and matching the triggering strategy file according to the vehicle model.

[0018] Optionally, it also includes: a detection module, used to detect the version of the trigger strategy file of the target vehicle before obtaining the trigger strategy file of the target vehicle; if the version is not the latest version, download the latest version of the trigger strategy file of the target vehicle from the cloud, wherein the trigger strategy file includes trigger strategies for multiple scenarios, and the update of the trigger strategy file supports the individual update of the trigger strategies for multiple scenarios.

[0019] A third aspect of this application provides a vehicle, including: a memory, a processor, and a computer program stored in the memory and executable on the processor. The processor executes the computer program to perform a data return control method as described in the above embodiments.

[0020] A fourth aspect of this application provides a computer-readable storage medium having a computer program or instructions stored thereon, which, when executed by a processor, performs the data return control method as described in the above embodiments.

[0021] A fifth aspect of this application provides a computer program product, including a computer program or instructions, which, when executed, implement the data return control method as described in the above embodiments.

[0022] Therefore, this application has at least the following beneficial effects:

[0023] This application embodiment can acquire data information when a target scenario of a vehicle is triggered, and control the data backhaul of the target scenario based on the data information. This achieves adaptive control of the data backhaul of the target scenario according to the data information, avoiding excessive backhaul data received by the cloud or target terminal, which affects the generalization of data backhaul, and saving data backhaul costs. Therefore, it solves the technical problems in related technologies, such as the inability to adaptively adjust data backhaul according to needs, leading to excessive backhaul data affecting the generalization of cloud data.

[0024] Additional aspects and advantages of this application will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of this application. Attached Figure Description

[0025] The above and / or additional aspects and advantages of this application will become apparent and readily understood from the following description of the embodiments taken in conjunction with the accompanying drawings, wherein:

[0026] Figure 1 This is a flowchart of a data return control method provided according to an embodiment of this application;

[0027] Figure 2 This is a diagram showing the module composition for data transmission according to the embodiments of this application;

[0028] Figure 3 This is a diagram showing the composition of a Trigger policy file provided according to an embodiment of this application;

[0029] Figure 4 A schematic diagram illustrating the configuration information of scene groups provided in the embodiments of this application;

[0030] Figure 5 A flowchart of Trigger policy file download provided in the embodiments of this application;

[0031] Figure 6 Example diagram of a control device for data return according to an embodiment of this application;

[0032] Figure 7 A schematic diagram of the structure of an electronic device provided in the embodiments of this application. Detailed Implementation

[0033] The embodiments of this application are described in detail below. Examples of these embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals denote the same or similar elements or elements having the same or similar functions throughout. The embodiments described below with reference to the accompanying drawings are exemplary and intended to explain this application, and should not be construed as limiting this application.

[0034] Before explaining the data backhaul control method proposed in this application, let's first describe the shortcomings of the current data backhaul triggering strategy and the impact of these shortcomings.

[0035] Related Technology 1 - Data backhaul link status monitoring method and system based on unmanned vehicles. This method starts from the last link of the entire data backhaul link and gradually traces back to other links, thereby realizing automatic monitoring of the status of the entire data backhaul link.

[0036] Related Technology 2 - Data Backhaul Method and System: This method provides a three-tier network architecture of vehicle-edge server-data center. The edge server controls the number of backhaul vehicles through a real-time resource table, ensuring smooth and orderly communication management. This guarantees full and rational utilization of bandwidth, ensuring orderly data reception and uploading. Simultaneously, it shares some of the responsibilities of the data center, ensuring its secure and stable operation.

[0037] Related Technology 3 - Data Backhaul Method, Data Retrieval Method and System: This method provides a data backhaul method, a data retrieval method and system to improve the reliability of vehicle status data reaching the vehicle control center.

[0038] However, the trigger strategy for data feedback in the aforementioned technologies does not support independent updates and is only updated during OTA updates of the intelligent driving software. This makes it impossible to achieve rapid and flexible strategy changes. For a single trigger scenario, it is impossible to configure and update the trigger strategy as needed. Furthermore, the triggering mechanism for data feedback is unreasonable. The shortcomings and their impacts are shown in Table 1.

[0039] Table 1

[0040]

[0041]

[0042] The following description, with reference to the accompanying drawings, outlines a data backhaul control method, apparatus, vehicle, storage medium, and program product according to embodiments of this application. Addressing the issue mentioned in the background art, where current data backhaul mechanisms trigger data backhaul through specific rules, and these triggering rules cannot be updated in a timely manner, only following the software OTA updates of the intelligent driving domain control, and cannot quickly adjust data backhaul according to the demand for backhauled data (i.e., cannot adaptively adjust data backhaul), leading to excessive backhauled data received by the cloud and affecting the generalization of cloud data, this application provides a data backhaul control method. In this method, data information of the vehicle when a target scenario is triggered can be obtained, and data backhaul of the target scenario can be controlled based on this data information to achieve adaptive control of the target scenario's data backhaul. This solves the problems in related technologies where the inability to adaptively adjust data backhaul according to demand leads to excessive backhauled data affecting the generalization of cloud data.

[0043] Specifically, Figure 1 This is a flowchart illustrating a data backhaul control method provided in an embodiment of this application.

[0044] like Figure 1 As shown, the control method for this data feedback includes the following steps:

[0045] In step S101, the triggering strategy file of the target vehicle is obtained.

[0046] The target vehicle is the vehicle that needs data back, and the trigger policy file, also known as the Trigger policy file, exists in the domain controller.

[0047] In the implementation of this application, obtaining the triggering strategy file of the target vehicle includes: obtaining the model of the target vehicle; and matching the triggering strategy file according to the model.

[0048] Since different vehicle models have different trigger strategy files, this application embodiment can obtain the vehicle model of the target vehicle and match the trigger strategy file according to the vehicle model of the target vehicle.

[0049] In this embodiment of the application, before obtaining the trigger strategy file of the target vehicle, the method further includes: detecting the version of the trigger strategy file of the target vehicle; if the version is not the latest version, downloading the latest version of the trigger strategy file of the target vehicle from the cloud, wherein the trigger strategy file includes trigger strategies for multiple scenarios, and the update of the trigger strategy file supports the individual update of the trigger strategies for multiple scenarios.

[0050] It is understood that, before obtaining the trigger strategy file, this application embodiment can first detect the version of the trigger strategy file of the target vehicle. If it is not the latest version, the latest version of the trigger strategy file is downloaded from the cloud. The trigger strategy file includes trigger strategies for multiple scenarios, and the update of the trigger strategy file supports the individual update of the trigger strategies for multiple scenarios.

[0051] In step S102, at least one target scenario is triggered according to the scenario triggering logic in the triggering strategy file, and data information of at least one target scenario being triggered within a preset time is obtained.

[0052] The data information includes at least one of the following: the number of times a target scenario is triggered, the geographical location when the target scenario is triggered, the time interval between the triggering of the target scenario, and driver information when the target scenario is triggered.

[0053] It is understood that, according to the triggering logic of the scenario in the triggering strategy file, at least one target scenario can be triggered, and data information of at least one target scenario being triggered within a preset time can be obtained. The preset time can be set according to specific circumstances, such as one day or two days.

[0054] In step S103, the data backhaul of at least one target scene is controlled according to the data information.

[0055] Among them, data backhaul refers to the target vehicle transmitting data information of at least one target scenario back to the cloud or other terminals.

[0056] It is understood that the embodiments of this application can control the data backhaul of the target scenario based on the data information in order to avoid excessive data backhaul, which would affect the generalization of the backhauled data and reduce the waste of data costs.

[0057] In this embodiment of the application, before controlling the data feedback of at least one target scenario based on the data information, the method further includes: summarizing the data information to obtain the number of times the at least one target scenario is triggered, the radius of the distribution range of the preset number of times the at least one target scenario is triggered, the time interval of the preset number of times the at least one target scenario is triggered, the driver information when the at least one target scenario is triggered, and the degree of danger of the at least one target scenario.

[0058] The preset number of triggers can be set according to specific circumstances, such as 10 times.

[0059] It is understood that the embodiments of this application can summarize the data information to obtain the number of times the target scene is triggered, the radius of the distribution range of the preset number of triggers, the time interval of the preset number of triggers, the driver information when the target scene is triggered, and the degree of danger of the target scene. The degree of danger can be divided into high danger level HS, low danger level LS, and other levels.

[0060] It should be noted that the distribution radius is also called the scatter radius. For example, if we statistically analyze the location distribution of 10 historical times, we can draw a circle and obtain the radius of this circle. The radius of the circle is the distribution radius (scatter radius).

[0061] For example, the data information obtained includes: the number of times the scenario was triggered; the geographical location when the scenario was triggered; the interval between scenario triggers; the driver's information when the scenario was triggered, which are summarized to obtain the number of times the scenario was triggered (A); the walking radius of the 10 historical scenario triggers (B); the interval between the 10 historical scenario triggers (C); the driver's information when the scenario was triggered (D); and the danger level of the scenario (E) (HS: high danger level, LS: low danger level, others).

[0062] In this embodiment of the application, controlling the data backhaul of at least one target scenario based on data information includes: stopping the data backhaul of at least one target scenario if the number of triggers is greater than or equal to a preset number, the distribution radius is less than or equal to a preset radius, the interval time is less than or equal to a preset time, the driver information is the same or different, and the danger level is greater than or equal to the first level; stopping the data backhaul of at least one target scenario if the number of triggers is greater than or equal to a preset number, the distribution radius is greater than or equal to a preset radius, the interval time is less than or equal to a preset time, the driver information is the same or different, and the danger level is greater than or equal to the first level; stopping the data backhaul of at least one target scenario if the number of triggers is greater than or equal to a preset number, the distribution radius is less than a preset radius, the interval time is less than or equal to a preset time, the driver information is different or the same, and the danger level is less than or equal to the second level; otherwise, maintaining the data backhaul of at least one target scenario.

[0063] The preset number of times, preset radius, and preset time can be set according to specific circumstances, and there are no specific limitations. The first level can be the high-risk level HS, and the second level can be the low-risk level LS.

[0064] It is understood that the embodiments of this application control the cessation of data backhaul for the target scenario under the following circumstances to avoid affecting the generalization of cloud data and reduce cost waste. Specific circumstances include:

[0065] 1. If the number of triggers A is greater than or equal to the preset number, the distribution radius B is less than or equal to the preset radius, the interval time C is less than or equal to the preset time, the driver information D is the same or different, and the danger level E is greater than or equal to the first level, stop data transmission.

[0066] 2. If the number of triggers A is greater than or equal to the preset number, the distribution radius B is greater than the preset radius, the interval time C is less than or equal to the preset time, the driver information D is the same or different, and the danger level E is greater than or equal to the first level, stop data transmission.

[0067] 3. If the number of triggers A is greater than or equal to the preset number, the distribution radius B is less than the preset radius, the interval time C is less than or equal to the preset time, the driver information D is different or the same, and the danger level E is less than or equal to the second level, then stop data transmission.

[0068] 4. Except for the above 1-3 situations, data should be transmitted back in all other situations.

[0069] For example, if the following conditions are met, the triggering of specific scenarios for the vehicle should be stopped, and specific vehicle information, driver information, and targeted interviews should be returned to achieve precise services. It is believed that the scenarios collected for the vehicle in a specific time and area are sufficient, and there is no need to collect more data, otherwise it will affect the generalization of the returned data.

[0070] 1. A ≥ XX times, B ≤ YY kilometers, C ≤ ZZ days, D is the same, and E ≥ HS grade;

[0071] 2. A ≥ XX times, B ≤ YY kilometers, C ≤ ZZ days, D are different, and E ≥ HS grade;

[0072] 3. A ≥ XX times, B ≥ YY kilometers, C ≤ ZZ days, D is the same, and E ≥ HS grade;

[0073] 4. A ≥ XX times, B ≥ YY kilometers, C ≤ ZZ days, D are different, and E ≥ HS grade;

[0074] 5. A ≥ XX times, B ≤ YY kilometers, C ≤ ZZ days, D are different, and E ≤ LS level;

[0075] 6. A ≥ XX times, B ≤ YY kilometers, C ≤ ZZ days, D is the same, and E ≤ LS level.

[0076] 7. For other combinations, the triggering of data return should continue.

[0077] It should be noted that currently, data feedback based on mass-produced vehicles requires comprehensive consideration of the following aspects to obtain the optimal solution.

[0078] 1. The number of mass-produced vehicles is huge, and the daily collection of scenario data is enormous. There is a lot of duplicate / similar data. Uploading all this data to the cloud is time-consuming, labor-intensive, and not cost-effective.

[0079] 2. The requirements for data transmission differ at each stage. Scenario A is required at time T0, while scenario B is required at time T1. How to quickly adjust according to these requirements is a key consideration.

[0080] 3. In mass-production software, it is difficult to design a perfect / flawless data return trigger mechanism.

[0081] Therefore, this application can support rapid cloud updates of trigger strategies, support multi-level configuration of trigger strategies for specific scenarios, and enable the vehicle to transmit historical data statistics based on its own data and combine them with the trigger mechanism to achieve adaptive trigger mechanism, decide whether to follow the trigger mechanism, and improve the generalization of cloud data.

[0082] The following specific embodiment illustrates the data return control method, which mainly includes three parts, such as... Figure 2 As shown, it includes:

[0083] 1. All data feedback trigger strategies are parameterized, supporting independent calibration. Calibration files are distributed from the cloud, and the vehicle end automatically updates the calibration values.

[0084] 2. The vehicle-side Trigger configuration management module is responsible for managing calibration files, querying new versions, downloading new versions, updating new versions, and updating new versions.

[0085] 3. Vehicle-side Trigger Strategy Adaptive Module.

[0086] The specific applications of the above three parts are explained below.

[0087] I. Trigger Policy File

[0088] The data backhaul trigger strategy is stored as a separate calibration file in the domain controller. The data backhaul module retrieves this calibration file every time the IDCU (Integrated Domain Control Unit) is powered on.

[0089] The Trigger policy file includes the following sections, such as: Figure 3 As shown:

[0090] 1. Overall version information, vehicle model matching information, and verification information.

[0091] 2. Scene group configuration information: This level only includes the on / off switch and trigger count configuration; enabling quick configuration of specific scene groups.

[0092] 3. Specific scenario configuration information, which is a sub-item of the scenario group, including secondary configuration information: primary trigger logic configuration item and secondary recording channel configuration item, which realizes detailed configuration of the specific scenario trigger.

[0093] For example, the specific application of scene group configuration information is as follows. Assuming scene group A has 20 specific scenes, namely A1, A2...A20, the scene configuration settings are shown in Table 2. Table 2 is the scene configuration settings table.

[0094] Table 2

[0095] Scene Group A1 A2 A3 …… A18 A19 A20 Switch item Byte1.1 Byte1.2 Byte 1.3 …… Byte3.4 Byte 3.5 Byte3.6

[0096] The switch item uses a 4-byte configuration word, with each bit representing a specific scenario. Bit = 1 indicates the scenario is enabled, and bit = 0 indicates it is disabled. The scenario group trigger count is represented by an array, with each specific scenario identified by a single byte. The high byte (bits 7-8) indicates the time limit for the trigger count (daily, weekly, monthly, yearly); bits 1-6 indicate the trigger count limit. Specific scenario group configurations are as follows... Figure 4 As shown.

[0097] II. Trigger Policy File Update Mechanism

[0098] Each time the IDCU powers on, the Trigger configuration management module queries the TSP (Telematics Service Provider) cloud server for new version information. If a new version exists, the Trigger configuration management module triggers the download of the new version; the IDCU should support retrying if the download fails. The IDCU implements integrity verification of the new version of the Trigger policy file. The IDCU performs only one round of configuration update query each time it powers on; the complete download process is as follows: Figure 5 As shown, this enables rapid updates to the data feedback mechanism, with the fastest update frequency being once a day, quickly collecting the training data required for perception.

[0099] III. Vehicle-side Trigger Strategy Adaptive Module

[0100] The vehicle-side trigger strategy adaptive module targets low-value data for specific scenarios, vehicles, and drivers. The vehicle-side adaptively disables data backhaul for that scenario to avoid affecting the generalization of cloud data and reduce cost waste.

[0101] The vehicle-side trigger strategy adaptive module collects the following information: the number of times each trigger scenario is triggered; the geographical location when each scenario is triggered; the interval between each scenario triggers; and the driver's information when each scenario is triggered.

[0102] The following information is summarized: A) Number of times each scenario is triggered; B) Walking radius of each scenario in the past 10 triggers; C) Interval time of each scenario in the past 10 triggers; D) Driver information when each scenario is triggered; E) Danger level of each scenario (HS: High danger level, LS: Low danger level, others).

[0103] The adaptive decision-making mechanism is as follows:

[0104] 1. The following should be stopped from triggering data:

[0105] If the following conditions are met, the triggering of specific scenarios for the vehicle should be stopped, and specific vehicle information, driver information, and targeted interviews should be sent back to achieve precise services. This can eliminate a large amount of meaningless or low-value data and reduce cost waste.

[0106] A≥XX times and B≤YY kilometers and C≤ZZ days and D is the same and E≥HS level;

[0107] A≥XX times and B≤YY kilometers and C≤ZZ days and D are different and E≥HS level;

[0108] A≥XX times and B≥YY kilometers and C≤ZZ days and D is the same and E≥HS level;

[0109] A≥XX times, B≥YY kilometers, C≤ZZ days, D is different, and E≥HS level.

[0110] 2. If the following conditions are met, the triggering of specific scenarios for the vehicle should be stopped, as it is considered that the scenarios collected by the vehicle in a specific time and area are sufficient and no further collection is necessary, otherwise it will affect the generalization of the returned data.

[0111] A≥XX times and B≤YY kilometers and C≤ZZ days and D are different and E≤LS level;

[0112] A ≥ XX times, B ≤ YY kilometers, C ≤ ZZ days, D is different, and E ≤ LS level.

[0113] 3. For other combinations, the triggering of data return should continue.

[0114] According to the data backhaul control method proposed in the embodiments of this application, data information of the vehicle when the target scene is triggered can be obtained, and the data backhaul of the target scene can be controlled based on the data information to achieve adaptive control of the data backhaul of the target scene according to the data information, thereby avoiding the cloud or other receiving terminals receiving too much backhaul data, affecting the generalization of data backhaul, and saving the cost of data backhaul.

[0115] Next, the control device for data transmission according to the embodiments of this application is described with reference to the accompanying drawings.

[0116] Figure 6 This is a block diagram of a control device for data return according to an embodiment of this application.

[0117] like Figure 6 As shown, the control device 10 for data feedback includes: an acquisition module 100, a trigger module 200, and a control module 300.

[0118] The acquisition module 100 is used to acquire the triggering strategy file of the target vehicle; the triggering module 200 is used to trigger at least one target scenario according to the triggering logic in the triggering strategy file, and acquire data information of at least one target scenario being triggered within a preset time; the control module 300 is used to control the data feedback of at least one target scenario according to the data information.

[0119] In this application embodiment, the data information includes at least one of the following: the number of times a target scenario is triggered, the geographical location when the target scenario is triggered, the time interval between the triggering of the target scenario, and driver information when the target scenario is triggered.

[0120] In this embodiment of the application, the apparatus 10 further includes a summarizing module.

[0121] The aggregation module is used to aggregate the data information before controlling the data feedback of at least one target scenario, and obtain the number of times the target scenario is triggered, the radius of the distribution range of the preset number of times the target scenario is triggered, the time interval of the preset number of times the target scenario is triggered, the driver information when the target scenario is triggered, and the danger level of the target scenario.

[0122] In this embodiment, the control module 300 is further configured to: stop data transmission for at least one target scenario if the number of triggers is greater than or equal to a preset number, the distribution radius is less than or equal to a preset radius, the interval time is less than or equal to a preset time, the driver information is the same or different, and the danger level is greater than or equal to the first level; stop data transmission for at least one target scenario if the number of triggers is greater than or equal to a preset number, the distribution radius is greater than or equal to a preset radius, the interval time is less than or equal to a preset time, the driver information is the same or different, and the danger level is greater than or equal to the first level; stop data transmission for at least one target scenario if the number of triggers is greater than or equal to a preset number, the distribution radius is less than a preset radius, the interval time is less than or equal to a preset time, the driver information is different or the same, and the danger level is less than or equal to the second level; otherwise, maintain data transmission for at least one target scenario.

[0123] In this embodiment of the application, the acquisition module 100 is further configured to: acquire the triggering strategy file of the target vehicle, including: acquiring the model of the target vehicle; and matching the triggering strategy file according to the model.

[0124] In this embodiment of the application, the apparatus 10 further includes a detection module.

[0125] The detection module is used to detect the version of the trigger strategy file of the target vehicle before obtaining the trigger strategy file of the target vehicle; if the version is not the latest version, the latest version of the trigger strategy file of the target vehicle is downloaded from the cloud. The trigger strategy file includes trigger strategies for multiple scenarios, and the update of the trigger strategy file supports the individual update of the trigger strategies for multiple scenarios.

[0126] It should be noted that the foregoing explanation of the control method embodiment for data backhaul also applies to the control device for data backhaul in this embodiment, and will not be repeated here.

[0127] According to the data backhaul control device proposed in the embodiments of this application, the data information of the vehicle when the target scene is triggered can be obtained, and the data backhaul of the target scene can be controlled based on the data information to realize adaptive control of the data backhaul of the target scene according to the data information, so as to avoid the cloud or other receiving terminals receiving too much backhaul data, affecting the generalization of data backhaul, and saving the cost of data backhaul.

[0128] Figure 7 A schematic diagram of the structure of a vehicle provided in an embodiment of this application. The vehicle may include:

[0129] The memory 701, the processor 702, and the computer program stored on the memory 701 and executable on the processor 702.

[0130] When the processor 702 executes the program, it implements the data return control method provided in the above embodiments.

[0131] Furthermore, the vehicle also includes:

[0132] Communication interface 703 is used for communication between memory 701 and processor 702.

[0133] The memory 701 is used to store computer programs that can run on the processor 702.

[0134] The memory 701 may include high-speed RAM memory, and may also include non-volatile memory, such as at least one disk storage device.

[0135] If the memory 701, processor 702, and communication interface 703 are implemented independently, then the communication interface 703, memory 701, and processor 702 can be interconnected via a bus to complete communication between them. The bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. Buses can be categorized as address buses, data buses, control buses, etc. For ease of representation, Figure 7 The bus is represented by a single thick line, but this does not mean that there is only one bus or one type of bus.

[0136] Optionally, in a specific implementation, if the memory 701, processor 702, and communication interface 703 are integrated on a single chip, then the memory 701, processor 702, and communication interface 703 can communicate with each other through an internal interface.

[0137] The processor 702 may be a central processing unit (CPU), an application specific integrated circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of this application.

[0138] This application also provides a computer-readable storage medium storing a computer program or instructions thereon, which, when executed by a processor, implements the above-described data return control method.

[0139] This application also provides a computer program product, including a computer program or instructions, which, when executed, implement the above-described control method for data return.

[0140] In the description of this specification, the references to terms such as "one embodiment," "some embodiments," "example," "specific example," or "some examples," etc., indicate that a specific feature, structure, material, or characteristic described in connection with that embodiment or example is included in at least one embodiment or example of this application. In this specification, the illustrative expressions of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in one or more embodiments or examples. Moreover, without contradiction, those skilled in the art can combine and integrate the different embodiments or examples described in this specification, as well as the features of different embodiments or examples.

[0141] Furthermore, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one of that feature. In the description of this application, "N" means at least two, such as two, three, etc., unless otherwise explicitly specified.

[0142] Any process or method described in the flowchart or otherwise herein can be understood as representing a module, segment, or portion of code comprising one or N executable instructions for implementing custom logic functions or processes, and the scope of the preferred embodiments of this application includes additional implementations in which functions may be performed not in the order shown or discussed, including substantially simultaneously or in reverse order depending on the functions involved, as should be understood by those skilled in the art to which embodiments of this application pertain.

[0143] It should be understood that the various parts of this application can be implemented using hardware, software, firmware, or a combination thereof. In the above embodiments, the N steps or methods can be implemented using software or firmware stored in memory and executed by a suitable instruction execution system. For example, if implemented in hardware, as in another embodiment, it can be implemented using any one or more of the following techniques known in the art: discrete logic circuits having logic gates for implementing logical functions on data signals, application-specific integrated circuits (ASICs) having suitable combinational logic gates, programmable gate arrays (PGAs), field-programmable gate arrays (FPGAs), etc.

[0144] Those skilled in the art will understand that all or part of the steps of the methods in the above embodiments can be implemented by a program instructing related hardware. The program can be stored in a computer-readable storage medium, and when executed, the program includes one or a combination of the steps of the method embodiments.

Claims

1. A control method of data backhauling, characterized by, The method comprises the following steps: obtaining a trigger strategy file of a target vehicle; triggering at least one target scene according to trigger logic of a scene in the trigger strategy file, and obtaining data information of triggering of the at least one target scene within a preset time, wherein the data information comprises at least one of a triggering frequency of the at least one target scene, a geographical position when the at least one target scene is triggered, a time interval when the at least one target scene is triggered, and driver information when the at least one target scene is triggered; controlling data return of the at least one target scene according to the data information; before the data return of the at least one target scene is controlled according to the data information, the method further comprises: aggregating the data information to obtain a triggering frequency of the at least one target scene, a distribution range radius of a preset triggering frequency of the at least one target scene, a time interval of the preset triggering frequency of the at least one target scene, driver information when the at least one target scene is triggered, and a danger level of the at least one target scene; the controlling of the data return of the at least one target scene according to the data information comprises: if the triggering frequency is greater than or equal to a preset triggering frequency, the distribution range radius is less than or equal to a preset radius, the time interval is less than or equal to a preset time, the driver information is the same or different, and the danger level is greater than or equal to a first level, then the data return of the at least one target scene is stopped; if the triggering frequency is greater than or equal to the preset triggering frequency, the distribution range radius is greater than the preset radius, the time interval is less than or equal to the preset time, the driver information is the same or different, and the danger level is greater than or equal to the first level, then the data return of the at least one target scene is stopped; if the triggering frequency is greater than or equal to the preset triggering frequency, the distribution range radius is less than the preset radius, the time interval is less than or equal to the preset time, the driver information is different or the same, and the danger level is less than or equal to a second level, then the data return of the at least one target scene is stopped; otherwise, the data return of the at least one target scene is maintained. 2.The control method of data backhauling according to claim 1, wherein, The obtaining of the trigger strategy file of the target vehicle comprises: obtaining a vehicle model of the target vehicle; matching the trigger strategy file according to the vehicle model. 3.The control method of data backhauling according to claim 1, wherein, Before the obtaining of the trigger strategy file of the target vehicle, the method further comprises: detecting a version of the trigger strategy file of the target vehicle; if the version is not a latest version, then downloading a trigger strategy file of a latest version of the target vehicle from a cloud, wherein the trigger strategy file comprises trigger strategies of a plurality of scenes, and updating of the trigger strategy file supports individual updating of the trigger strategies of the plurality of scenes.

4. A control device of data backhauling, characterized by, The method comprises: an obtaining module configured to obtain a trigger strategy file of a target vehicle; triggering at least one target scene according to the triggering logic of a scene in the triggering strategy file, and obtaining data information of the at least one target scene triggered in a preset time, wherein the data information comprises at least one of a triggering number of the at least one target scene, a geographical position when the at least one target scene is triggered, a time interval when the at least one target scene is triggered, and driver information when the at least one target scene is triggered; controlling data backhaul of the at least one target scene according to the data information; before the data backhaul of the at least one target scene is controlled according to the data information, the data information is further aggregated to obtain a triggering number of the at least one target scene, a distribution range radius of a preset triggering number of the at least one target scene, a time interval of the preset triggering number of the at least one target scene, driver information when the at least one target scene is triggered, and a danger level of the at least one target scene; the controlling of the data backhaul of the at least one target scene according to the data information comprises: if the triggering number is greater than or equal to a preset triggering number, the distribution range radius is less than or equal to a preset radius, the time interval is less than or equal to a preset time, the driver information is the same or different, and the danger level is greater than or equal to a first level, the data backhaul of the at least one target scene is stopped; if the triggering number is greater than or equal to the preset triggering number, the distribution range radius is greater than the preset radius, the time interval is less than or equal to the preset time, the driver information is the same or different, and the danger level is greater than or equal to the first level, the data backhaul of the at least one target scene is stopped; if the triggering number is greater than or equal to the preset triggering number, the distribution range radius is less than the preset radius, the time interval is less than or equal to the preset time, the driver information is different or the same, and the danger level is less than or equal to a second level, the data backhaul of the at least one target scene is stopped; otherwise, the data backhaul of the at least one target scene is maintained.

5. A vehicle characterized by comprising: comprise: a memory, a processor, and a computer program stored in the memory and executable on the processor, the processor executing the computer program to implement the control method of data backhaul according to any one of claims 1-3.

6. A computer readable storage medium having stored thereon a computer program or instructions, characterized in that, the computer program or instructions are executed by the processor to implement the control method of data backhaul according to any one of claims 1-3.

7. A computer program product comprising computer programs or instructions, characterized in that, the computer program or instructions are executed to implement the control method of data backhaul according to any one of claims 1-3.

Images