Methods, apparatus, equipment, and storage media for determining vehicle data collection costs

By calculating the data parameters and cost parameters of vehicle data, the unit collection flow and collection cost are determined, which solves the cost control problem in vehicle data collection and realizes the rational use of resources and accurate monitoring of costs.

CN117041281BActive Publication Date: 2026-11-17GREAT WALL MOTOR CO LTD
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
CN202310680897.6
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2023-06-09
Publication Date
2026-11-17
Estimated Expiration
2043-06-09

AI Technical Summary

Technical Problem

During the vehicle data collection process, the collection costs cannot be effectively quantified and controlled, resulting in unreasonable resource consumption.

Method used

By determining the data parameters of the target vehicle data, the unit acquisition traffic and acquisition cost are calculated, including data packet headers, identifiers, timestamps, acquisition cycles, and fixed signal length of the controller area network. Combined with cost parameters and data acquisition duration, bandwidth and storage costs are calculated, providing visualized cost monitoring and alerts.

Benefits of technology

It enables accurate monitoring and control of vehicle data collection costs, avoids resource waste, provides intelligent cost budgeting and overspending alerts, and ensures the smooth progress of the data collection process.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN117041281B_ABST
    Figure CN117041281B_ABST
Patent Text Reader

Abstract

This application provides a method, apparatus, device, and storage medium for determining the cost of vehicle data acquisition. The method, applied in the field of vehicle data acquisition, includes: responding to a data acquisition request for a target vehicle model, determining the data parameters for acquiring target vehicle data; determining the unit acquisition traffic consumed in acquiring the target vehicle data based on the data parameters; and determining the acquisition cost consumed in acquiring the target vehicle data based on the unit acquisition traffic, the cost parameters corresponding to the target vehicle model, and the data acquisition duration. This method can determine the acquisition cost required for the current acquisition by using the data parameters of the target vehicle data when it is necessary to acquire target vehicle data. The above process enables cost estimation and monitoring of target vehicle data, allowing acquisition personnel to accurately understand the cost consumption overview of the target vehicle data.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This application relates to the field of vehicle data acquisition, and more specifically, to a method, apparatus, device, and storage medium for determining the cost of vehicle data acquisition in the field of vehicle data acquisition. Background Technology

[0002] Currently, in the automotive field, with the development of the Internet era, Internet of Vehicles (IoV) technology has been widely used in vehicles.

[0003] In the connected vehicle ecosystem, the Telematics Service Provider (TSP, also known as in-vehicle terminal service) platform is the core of connected vehicles, responsible for data supply between vehicles and service providers and data collection from vehicles.

[0004] In one possible implementation, the process of collecting vehicle data mainly involves a data transmission application → manual approval → uploading to the TSP platform to upload the collected vehicle data to the TSP platform.

[0005] During the aforementioned process of transmitting vehicle data, the cost of collecting vehicle data cannot be obtained, which makes it impossible to statistically analyze and control the cost of collecting vehicle data.

[0006] In summary, how to calculate the cost of vehicle data collection has become an urgent problem to be solved during the process of collecting vehicle data. Summary of the Invention

[0007] This application provides a method, apparatus, device, and storage medium for determining the cost of vehicle data collection. The method can determine the required collection cost based on the data parameters of the target vehicle data when it is necessary to collect target vehicle data. The above process enables cost estimation and monitoring of target vehicle data, allowing collection personnel to accurately understand the cost profile of the target vehicle data.

[0008] Firstly, a method for determining vehicle data collection costs is provided. The method includes: in response to a data collection request for a target vehicle model, determining data parameters for collecting target vehicle data of the target vehicle model, the data parameters representing the data structure of the target vehicle data; determining, based on the data parameters, a unit collection flow rate consumed in collecting the target vehicle data, the unit collection flow rate representing the flow rate consumed in a single collection of the target vehicle data, the target vehicle being any vehicle under the target vehicle model; and determining the collection cost consumed in collecting the target vehicle data based on the unit collection flow rate, a cost parameter corresponding to the target vehicle model, and a data collection duration, the cost parameter representing the resource consumption for collecting the target vehicle data of the target vehicle model within the data collection duration.

[0009] In the above technical solution, this application proposes a method for determining the cost of vehicle data collection during the process of collecting vehicle data. The specific process is as follows: First, in response to a data collection request for a target vehicle model, data parameters related to the target vehicle data under the target model are determined. These data parameters can be used to represent the data structure of the target vehicle data, or they can be understood as the data parameters constituting the target vehicle data. After obtaining the data parameters of the target vehicle data, this application can calculate the unit collection traffic consumed in collecting the target vehicle data using these parameters. The unit collection traffic refers to the traffic consumed in a single collection of target vehicle data for any vehicle under the target model. Target vehicle data typically corresponds to a data collection duration. Furthermore, based on the unit collection traffic, the cost parameters corresponding to the target model, and the data collection duration, this application can determine the collection cost consumed in collecting the target vehicle data. The cost parameter can represent the resource consumption status of collecting target vehicle data for the target model within the data collection duration. In the process of collecting target vehicle data for the target model, the above method can monitor the cost of target vehicle data collection according to the data parameters, cost parameters, and data collection duration related to the target vehicle data, providing a smart cost budgeting solution for data collection personnel. This avoids the resource consumption problem caused by excessive collection costs during the process of collecting vehicle data.

[0010] In conjunction with the first aspect, in some possible implementations, the data parameters include a data packet header, an identifier of the target vehicle data, a timestamp, a collection period, and a fixed signal length of the controller area network. Determining the unit collection traffic consumed in collecting the target vehicle data based on these data parameters includes: determining a first data size occupied by the target vehicle data collected in the collection period; determining a second data size occupied by the data packet header, a third data size occupied by the identifier of the target vehicle data, a fourth data size occupied by the timestamp, and a fifth data size occupied by the fixed signal length of the controller area network; and determining the unit collection traffic based on the first, second, third, fourth, and fifth data sizes.

[0011] In the aforementioned technical solution, this application proposes a specific method for determining the unit acquisition traffic based on data parameters. These data parameters include the data packet header, the target vehicle data identifier, the timestamp, the acquisition period, and the fixed signal length of the controller area network (SAR). Since the data parameters represent the data structure of the target vehicle data, the data size corresponding to each of the above data parameters can be calculated separately during the calculation of the unit acquisition traffic. For example, the data size occupied by the target vehicle data acquired during the acquisition period is the first data size, the data packet header is the second data size, the target vehicle data identifier is the third data size, the timestamp is the fourth data size, and the fixed signal length of the SAR is the fifth data size. Furthermore, the unit acquisition traffic is determined based on these five data sizes.

[0012] Since the target vehicle data is closely related to the vehicle model and data collection requirements, the above method of calculating the unit data collection flow based on the data parameters of the target vehicle data can ensure that the corresponding unit data collection flow is accurately calculated according to different vehicle models and data collection requirements.

[0013] In conjunction with the first aspect and the above implementation methods, in some possible implementation methods, the collection cycle includes a first collection cycle and a second collection cycle. Determining the first data size occupied by the target vehicle data collected in the collection cycle includes: determining a sixth data size occupied by the target vehicle data collected in the first collection cycle and a seventh data size occupied by the target vehicle data collected in the second collection cycle; determining the sum of the sixth data size and the seventh data size as the first data size; and determining the unit collection flow based on the first data size, the second data size, the third data size, the fourth data size, and the fifth data size includes: determining the sum of the first data size, the second data size, the third data size, the fourth data size, and the fifth data size as the unit collection flow.

[0014] In the above technical solution, the data collection period for the target vehicle is generally divided into two types: a first collection period and a second collection period. Based on this, when calculating the first data size of the target vehicle data collected in each collection period, this application can calculate the sixth data size occupied by the target vehicle data corresponding to the first collection period and the seventh data size occupied by the target vehicle data corresponding to the second collection period. The sixth and seventh data sizes are then summed to obtain the first data size. Furthermore, the first, second, third, fourth, and fifth data sizes are summed to obtain the unit collection flow rate.

[0015] In combination with the first aspect and the above implementation methods, in some possible implementation methods, the collection cost consumed in collecting data of the target vehicle is determined based on the unit collection traffic, the cost parameters corresponding to the target vehicle model, and the data collection duration. This includes: determining the bandwidth cost and storage cost consumed in collecting data of the target vehicle based on the unit collection traffic, the cost parameters, and the data collection duration; and determining the collection cost based on the bandwidth cost and the storage cost.

[0016] In the above technical solution, after determining the unit collection traffic, this application proposes a step for determining the collection cost. The collection cost in this application comprises two parts: the transmission cost of the target vehicle data (bandwidth cost) and the storage cost of the target vehicle data. Therefore, when calculating the collection cost, the bandwidth cost and storage cost consumed by the target vehicle data can be determined based on the unit collection traffic, cost parameters, and data collection duration. Then, the collection cost is determined based on the bandwidth cost and storage cost. This method of determining the collection cost considers both the cost of transmitting and storing the target vehicle data, achieving accurate control and monitoring of the collection cost during the data collection process, and ensuring the rationality and accuracy of the collection cost calculation.

[0017] In conjunction with the first aspect and the above-mentioned implementation methods, in some possible implementation methods, the cost parameter includes the average peak online vehicle count of the target vehicle model within the data collection period, bandwidth unit resource consumption, daily runtime, estimated sales volume of the target vehicle model within the data collection period, upload cycle of the target vehicle data, and storage unit resource consumption. The average peak online vehicle count of the target vehicle model within the data collection period is used to represent the average value of the peak online vehicle count of the target vehicle model within the data collection period. Determining the bandwidth cost and storage cost consumed in collecting the target vehicle data based on the unit collection traffic, the cost parameter, and the data collection period includes: determining the target bandwidth unit resource consumption and target storage unit resource consumption corresponding to the data collection period; determining the bandwidth cost based on the unit collection traffic, the average peak online vehicle count, and the target bandwidth unit resource consumption; and determining the storage cost based on the unit collection traffic, the daily runtime, the upload cycle, the estimated sales volume, the target storage unit resource consumption, and the data collection period.

[0018] In the aforementioned technical solution, the cost parameters for calculating bandwidth and storage costs primarily include the average peak number of online vehicles for the target vehicle model, bandwidth resource consumption per unit, daily runtime, estimated sales volume of the target vehicle model within the data collection period, upload cycle, and storage resource consumption per unit. The bandwidth resource consumption per unit and storage resource consumption per unit vary depending on the data collection period. For example, if the data collection period is monthly, the bandwidth resource consumption per unit and storage resource consumption per unit are calculated on a monthly basis. If the data collection period is yearly, the bandwidth resource consumption per unit and storage resource consumption per unit are calculated on an annual basis.

[0019] Therefore, when calculating bandwidth and storage costs, this application can first determine the corresponding target bandwidth unit resource consumption and target storage unit resource consumption based on the data collection duration.

[0020] Furthermore, bandwidth costs can be obtained by calculating unit traffic volume, average peak online traffic, and target bandwidth unit resource consumption. Storage costs can be obtained by calculating unit traffic volume, daily runtime, upload cycle, estimated sales volume, target storage unit resource consumption, and data collection duration.

[0021] In conjunction with the first aspect and the above implementation methods, in some possible implementation methods, the method further includes: displaying a data acquisition cost display interface; if the data acquisition cost is greater than a preset data acquisition cost, generating a first prompt message based on the data acquisition cost and the preset data acquisition cost; and displaying the first prompt message on the data acquisition cost display interface.

[0022] In the above technical solution, when calculating the data collection cost, this application also provides a visual cost viewing method, specifically, a data collection cost display interface. This application can pre-set corresponding preset data collection costs for vehicle data of different models. After calculating the data collection cost, the cost can be compared with the preset cost to determine whether the current cost exceeds the budget. If the cost exceeds the preset cost, a prompt message is displayed on the data collection cost display interface so that data collection personnel can clearly understand the specific overspending situation.

[0023] In combination with the first aspect and the above implementation methods, in some possible implementation methods, the method further includes: displaying the unit collection traffic on the collection cost display interface; generating a second prompt message when the sum of the unit collection traffic and the bandwidth peak is greater than a preset bandwidth; and displaying the second prompt message on the collection cost display interface.

[0024] In addition to displaying cost overruns, the above technical solution can also calculate whether the peak bandwidth reached during vehicle data transmission and the unit data collection flow rate have exceeded the preset bandwidth. If so, a second prompt message can be displayed on the data collection cost display interface to remind the data collection personnel to expand the preset bandwidth to ensure the smooth progress of the data collection process.

[0025] In summary, this application proposes a method for determining vehicle data collection costs during the vehicle data collection process. The specific process is as follows: First, in response to a data collection request for a target vehicle model, data parameters related to the target vehicle data under that target model are determined. These data parameters can be used to represent the data structure of the target vehicle data, or they can be understood as the data parameters constituting the target vehicle data. After obtaining the data parameters of the target vehicle data, this application can calculate the unit collection traffic consumed in collecting the target vehicle data using these parameters. The unit collection traffic refers to the traffic consumed in a single collection of target vehicle data for any vehicle under the target model. Target vehicle data typically corresponds to a data collection duration. Furthermore, based on the unit collection traffic, the cost parameters corresponding to the target model, and the data collection duration, this application can determine the collection cost consumed in collecting the target vehicle data. The cost parameter can represent the resource consumption status of collecting target vehicle data for the target model within the data collection duration. The above-mentioned method for monitoring the target vehicle data collection cost during the target vehicle data collection process can be achieved by using data parameters, cost parameters, and data collection duration related to the target vehicle data, providing a smart cost budgeting solution for data collection personnel. This avoids the resource consumption problem caused by excessive collection costs during the process of collecting vehicle data.

[0026] This application proposes a specific method for determining the unit acquisition traffic based on data parameters. These data parameters include the data packet header, the target vehicle data identifier, the timestamp, the acquisition period, and the fixed signal length of the controller area network (SAR). Since the data parameters represent the data structure of the target vehicle data, the data size corresponding to each of the above data parameters can be calculated separately during the calculation of the unit acquisition traffic. For example, the data size occupied by the target vehicle data acquired during the acquisition period is the first data size, the data packet header is the second data size, the target vehicle data identifier is the third data size, the timestamp is the fourth data size, and the fixed signal length of the SAR is the fifth data size. Furthermore, the unit acquisition traffic is determined based on these five data sizes.

[0027] Since the target vehicle data is closely related to the vehicle model and data collection requirements, the above method of calculating the unit data collection flow based on the data parameters of the target vehicle data can ensure that the corresponding unit data collection flow is accurately calculated according to different vehicle models and data collection requirements.

[0028] In this application, the data collection period for target vehicle data is generally divided into two types: a first collection period and a second collection period. Based on this, when calculating the first data size of the target vehicle data collected in each collection period, this application can calculate the sixth data size occupied by the target vehicle data corresponding to the first collection period and the seventh data size occupied by the target vehicle data corresponding to the second collection period. The sixth and seventh data sizes are then summed to obtain the first data size. Furthermore, the first, second, third, fourth, and fifth data sizes are summed to obtain the unit collection flow rate.

[0029] After determining the unit data collection traffic, this application proposes a step for determining the collection cost. The collection cost in this application comprises two parts: the transmission cost of the target vehicle data (bandwidth cost) and the storage cost of the target vehicle data. Therefore, when calculating the collection cost, the bandwidth cost and storage cost consumed by the target vehicle data can be determined based on the unit data collection traffic, cost parameters, and data collection duration. Then, the collection cost is determined based on the bandwidth cost and storage cost. This method of determining the collection cost considers both the cost of transmitting and storing the target vehicle data, enabling accurate control and monitoring of the collection cost during the data collection process, and ensuring the rationality and accuracy of the collection cost calculation.

[0030] Specifically, in calculating bandwidth and storage costs, the main cost parameters include the average peak number of online vehicles for the target vehicle model, bandwidth consumption per unit, daily runtime, estimated sales volume of the target vehicle model within the data collection period, upload cycle, and storage consumption per unit. The bandwidth and storage consumption per unit vary depending on the data collection period. For example, if the data collection period is monthly, the bandwidth and storage consumption per unit are calculated on a monthly basis. If the data collection period is yearly, the bandwidth and storage consumption per unit are calculated on an annual basis.

[0031] Therefore, when calculating bandwidth and storage costs, this application can first determine the corresponding target bandwidth unit resource consumption and target storage unit resource consumption based on the data collection duration.

[0032] Furthermore, bandwidth costs can be obtained by calculating unit traffic volume, average peak online traffic, and target bandwidth unit resource consumption. Storage costs can be obtained by calculating unit traffic volume, daily runtime, upload cycle, estimated sales volume, target storage unit resource consumption, and data collection duration.

[0033] In calculating data collection costs, this application also provides a visual cost viewing method, specifically a data collection cost display interface. This application allows for pre-setting corresponding preset data collection costs for different vehicle models. After calculating the data collection cost, it can be compared with the preset cost to determine if the current cost exceeds the budget. If the cost exceeds the preset cost, a prompt message is displayed on the data collection cost display interface so that data collection personnel can clearly understand the specific overrun situation.

[0034] In addition to displaying cost overruns, this application can also calculate whether the peak bandwidth reached during vehicle data transmission and the current unit collection traffic volume have exceeded the preset bandwidth. If exceeded, a second prompt message can be displayed on the collection cost display interface to remind the collection personnel to expand the preset bandwidth to ensure the smooth progress of the collection process.

[0035] Secondly, an apparatus for determining the cost of vehicle data collection is provided. The apparatus includes: a determining module, configured to, in response to a data collection request for a target vehicle model, determine data parameters for collecting target vehicle data of the target vehicle model, the data parameters representing the data structure of the target vehicle data; based on the data parameters, determine the unit collection flow consumed in collecting the target vehicle data, the unit collection flow representing the flow consumed in a single collection of the target vehicle data, the target vehicle being any vehicle under the target vehicle model; and based on the unit collection flow, the cost parameters corresponding to the target vehicle model, and the data collection duration, determine the collection cost consumed in collecting the target vehicle data, the cost parameters representing the resource consumption of collecting the target vehicle data of the target vehicle model within the data collection duration.

[0036] In conjunction with the second aspect, in some possible implementations, the data parameters include a data packet header, the identifier of the target vehicle data, a timestamp, a collection period, and the fixed signal length of the controller area network. The determining module is specifically used to: determine the first data size occupied by the target vehicle data collected in the collection period; determine the second data size occupied by the data packet header, the third data size occupied by the identifier of the target vehicle data, the fourth data size occupied by the timestamp, and the fifth data size occupied by the fixed signal length of the controller area network; and determine the unit collection traffic based on the first data size, the second data size, the third data size, the fourth data size, and the fifth data size.

[0037] In conjunction with the second aspect and the above implementation methods, in some possible implementation methods, the collection cycle includes a first collection cycle and a second collection cycle. The determining module is further configured to: determine the sixth data size occupied by the target vehicle data collected in the first collection cycle and the seventh data size occupied by the target vehicle data collected in the second collection cycle; determine the sum of the sixth data size and the seventh data size as the first data size; and determine the sum of the first data size, the second data size, the third data size, the fourth data size and the fifth data size as the unit collection flow.

[0038] In conjunction with the second aspect and the above implementation methods, in some possible implementation methods, the determining module is further used to: determine the bandwidth cost and storage cost consumed in collecting the target vehicle data based on the unit collection traffic, the cost parameter and the data collection duration; and determine the collection cost based on the bandwidth cost and the storage cost.

[0039] In conjunction with the second aspect and the above implementation methods, in some possible implementation methods, the cost parameter includes the average peak online vehicle count of the target vehicle model within the data collection period, bandwidth unit resource consumption, daily runtime, estimated sales volume of the target vehicle model within the data collection period, upload cycle of the target vehicle data, and storage unit resource consumption. The average peak online vehicle count of the target vehicle model within the data collection period is used to represent the average value of the peak online vehicle count of the target vehicle model within the data collection period. The determining module is further used to: determine the target bandwidth unit resource consumption and target storage unit resource consumption corresponding to the data collection period; determine the bandwidth cost based on the unit collection traffic, the average peak online vehicle count, and the target bandwidth unit resource consumption; and determine the storage cost based on the unit collection traffic, the daily runtime, the upload cycle, the estimated sales volume, the target storage unit resource consumption, and the data collection period.

[0040] In conjunction with the second aspect and the above implementation methods, in some possible implementation methods, the device further includes: a first processing module, used to display a data acquisition cost display interface; when the data acquisition cost is greater than a preset data acquisition cost, to generate a first prompt message based on the data acquisition cost and the preset data acquisition cost; and to display the first prompt message on the data acquisition cost display interface.

[0041] In conjunction with the second aspect and the above implementation methods, in some possible implementation methods, the device further includes: a second processing module, configured to display the unit collection traffic on the collection cost display interface; generate a second prompt message when the sum of the unit collection traffic and the bandwidth peak value is greater than a preset bandwidth; and display the second prompt message on the collection cost display interface.

[0042] Thirdly, a data acquisition and control device is provided, including a memory and a processor. The memory is used to store executable program code, and the processor is used to call and run the executable program code from the memory, causing the data acquisition and control device to perform the methods in the first aspect or any possible implementation thereof.

[0043] Fourthly, a computer program product is provided, comprising: computer program code, which, when run on a computer, causes the computer to perform the methods described in the first aspect or any possible implementation thereof.

[0044] Fifthly, a computer-readable storage medium is provided that stores computer program code, which, when executed on a computer, causes the computer to perform the methods described in the first aspect or any possible implementation thereof. Attached Figure Description

[0045] Figure 1 This is a schematic diagram of a scenario for collecting vehicle data provided in an embodiment of this application;

[0046] Figure 2 This is a schematic flowchart illustrating a method for determining vehicle data collection costs provided in an embodiment of this application;

[0047] Figure 3 This is a schematic diagram of a scenario for configuring target vehicle data provided in an embodiment of this application;

[0048] Figure 4 This is a schematic diagram illustrating a scenario for calculating data acquisition costs, provided in an embodiment of this application.

[0049] Figure 5 This is a schematic diagram of the structure of vehicle data provided in an embodiment of this application;

[0050] Figure 6 This is a schematic diagram of a device for determining vehicle data collection costs provided in an embodiment of this application;

[0051] Figure 7 This is a schematic diagram of the structure of a data acquisition and control device provided in an embodiment of this application. Detailed Implementation

[0052] The technical solutions in this application will be clearly and thoroughly described below with reference to the accompanying drawings. In the description of the embodiments of this application, unless otherwise stated, " / " means "or," for example, A / B can mean A or B. "And / or" in the text is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, and B existing alone. Furthermore, in the description of the embodiments of this application, "multiple" refers to two or more than two.

[0053] Hereinafter, the terms "first" and "second" are used for descriptive purposes only and should not be construed as implying or suggesting relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of that feature.

[0054] Figure 1 This is a schematic diagram of a scenario for collecting vehicle data provided in an embodiment of this application.

[0055] For example, such as Figure 1 As shown, during the driving process of vehicle 103, vehicle 103 has various vehicle data, such as vehicle speed, engine speed, battery charge, accelerator pedal opening, air conditioning temperature, wheel temperature, tire pressure, and other vehicle data.

[0056] With the continuous development of vehicle-to-everything (V2X) technology, vehicles 103 can utilize network communication technology to achieve mutual transmission of vehicle data. TSP102, as a crucial component of the V2X system, is a platform providing remote monitoring, control, navigation, and entertainment services for vehicle 103. The main functions of TSP102 include remote monitoring and diagnostics of vehicle 103, remote control and adjustment of vehicle 103, navigation and route planning for vehicle 103, and entertainment and media services for vehicle 103, aiming to provide drivers and passengers with a comfortable and pleasant driving experience.

[0057] Therefore, based on the functions of TSP102, vehicle 103 can send vehicle data to TSP102 so that TSP102 can monitor and control vehicle 103 based on the vehicle data.

[0058] In one possible implementation, vehicle 103 can send vehicle data to TSP102 via a telematics box (T-Box, also known as a remote communication terminal, vehicle terminal, remote communication module, etc.) inside the vehicle.

[0059] It should be understood that the vehicle data that TSP102 needs to collect varies depending on the monitoring scenario and data collection requirements. For example, in scenarios where remote monitoring and diagnostics of vehicle 103 are required, TSP102 may need to obtain information such as vehicle speed, fuel level, battery charge, and tire pressure. When entertainment and media control of vehicle 103 is required, TSP102 needs to obtain multimedia-related information of vehicle 103, such as the status of the multimedia host.

[0060] In addition, depending on the different data collection requirements, the model of vehicle 103 (hereinafter referred to as "vehicle type") and the type of vehicle data will also vary.

[0061] Therefore, before collecting vehicle data, the personnel can pre-configure the target vehicle models to be collected, as well as which target vehicle data under the target models, in the data collection and control device 101. The data collection and control device 101 and TSP102 can communicate with each other.

[0062] Specifically, the data acquisition and control equipment 101 is equipped with a data acquisition and control system, and the data acquisition personnel can configure the target vehicle model and target vehicle data in the display interface of the data acquisition and control system.

[0063] After configuration, the data acquisition and control device 101 can send the configuration operations of the data acquisition personnel to the TSP 102 in the form of a display request, so that the TSP 102 can collect the corresponding vehicle data according to the configured requirements. In addition, during the data acquisition process, the data acquisition and control device 101 can also calculate the data acquisition cost consumed in this data acquisition process to achieve data acquisition cost monitoring.

[0064] After introducing the scenarios for collecting vehicle data, the following describes a method for determining the cost of vehicle data collection provided by an embodiment of this application.

[0065] Figure 2 This is a schematic flowchart illustrating a method for determining vehicle data collection costs according to an embodiment of this application. It should be understood that this method can be applied to, for example... Figure 1 The scenario shown is specifically applied to Figure 1 The data acquisition and control equipment 101 in the middle.

[0066] For example, such as Figure 2 As shown, the method 200 includes:

[0067] 201. In response to the data collection request for the target vehicle model, determine the data parameters for the target vehicle data to be collected. The data parameters are used to represent the data structure of the target vehicle data.

[0068] It should be understood that vehicle data is typically sent to a TSP (Traffic Support Service) platform for storage. On one hand, the TSP can analyze and process vehicle data; on the other hand, based on the TSP's storage, drivers and passengers can retrieve vehicle data from the TSP using their terminal devices (e.g., vehicle applications / apps) based on the vehicle's identifier (e.g., Vehicle Identification Number, VIN) for easy viewing and processing. Alternatively, drivers and passengers can control the vehicle through their terminal devices and the TSP.

[0069] Among them, vehicle data refers to vehicle data obtained after the vehicle's driver has been authorized.

[0070] Optionally, vehicle data includes vehicle status information and driving parameters. Status information may include the status of vehicle components, such as the status of doors and windows. Driving parameters represent the driving values ​​of vehicle components, such as vehicle speed, wheel speed, engine speed, and the opening (or travel) of the accelerator pedal (or throttle).

[0071] It should also be understood that the vehicle data that the TSP needs to acquire varies depending on the data collection requirements and the type of vehicle data. For example, in scenarios where remote monitoring and diagnostics of vehicle 103 are required, the TSP may need to acquire vehicle 103's speed, fuel level, battery charge, tire pressure, etc.; when entertainment and media control of the vehicle is required, the TSP needs to acquire multimedia-related information of the vehicle, such as the status of the multimedia host, etc.

[0072] Therefore, before the TSP collects vehicle data, this embodiment of the application first needs to pre-configure the target vehicle model and the target vehicle data under the target vehicle model based on the collection and control equipment.

[0073] Figure 3 This is a schematic diagram of a scenario for configuring target vehicle data provided in an embodiment of this application.

[0074] For example, such as Figure 3 As shown, combined with Figure 1 The data acquisition and control device 101 is equipped with a data acquisition and control system. When configuring target vehicle data on the data acquisition and control device 101, the data acquisition personnel can first log in to the data acquisition and control system using their own identification (such as phone number, ID number, employee number, company email address, etc.) to request TSP102 to verify the identity of the data acquisition personnel.

[0075] Once the data collection personnel's identity is verified, they can access the data collection and control system. The display area of ​​the data collection and control device 101 can display the function menu interface of the data collection and control system, which includes multiple function controls, such as "Settings" control, "Display" control, and "Vehicle Data Configuration" control.

[0076] Furthermore, the data acquisition personnel can select the "Vehicle Data Configuration" control in the function menu interface through a trigger operation. Based on this trigger operation, the data acquisition and control device 101 can send the trigger operation to the TSP 102 in the form of a display request, so that the TSP 102 can generate corresponding display instructions according to the display request.

[0077] Optionally, the triggering operation includes any one of the following operations: click operation, voice command, and gesture adjustment operation. The following embodiments of this application will use a click operation as an example for explanation.

[0078] like Figure 3 As shown, in response to the display command sent by TSP102, the data acquisition and control device 101 displays the vehicle data configuration interface 301 in the display area. The vehicle data configuration interface 301 includes a target vehicle model configuration area 3011, a target vehicle data configuration area 3012, and a data acquisition duration configuration area 3013.

[0079] The data collection duration can be understood as the time interval between the start and end times of data collection for the target vehicle.

[0080] Optionally, the data collection period can be one month, one day, one quarter, two months, one year, or other durations. This application embodiment does not limit this. The following embodiment of this application uses a data collection period of one month as an example for illustration.

[0081] Due to different data collection needs, the target vehicle models, target vehicle data, and data collection time will also vary.

[0082] like Figure 3 As shown, the target vehicle configuration area 3011 displays multiple vehicle models, namely model A, model B, model C, and model D. Data collectors can select model A as the target vehicle by clicking within the target vehicle configuration area 3011.

[0083] Furthermore, after configuring the target vehicle model, the data collector can also configure the target vehicle data under the target vehicle model in the target vehicle data configuration area 3012.

[0084] One possible implementation is based on multiple Domain Control Units (DCUs, also known as domain controllers) of the vehicle—chassis DCU, body DCU, powertrain DCU, cockpit DCU, and Advanced Driving Assistance System (ADAS) DCU. Embodiments of this application can classify vehicle data according to the aforementioned domain controllers, including chassis data, body data, powertrain data, cockpit data, and driver assistance system data.

[0085] like Figure 3 As shown, data collectors can select chassis-related data as target vehicle data by clicking on it.

[0086] In the data collection duration configuration area 3013, various data collection durations are displayed, namely one month, one quarter, one day, one year, and other durations. For example... Figure 3 As shown, the data collector can select one month as the data collection duration in this embodiment of the application by clicking in the data collection duration configuration area 3013.

[0087] The above configuration process for target vehicle data, target model, and data collection duration is only an illustrative example. Other classification, display, and configuration methods are also possible, and this application embodiment does not limit them.

[0088] After selecting the target vehicle model, target vehicle data, and data collection duration, the data collector can complete the configuration process by clicking the "Confirm" control in the vehicle data configuration interface 301.

[0089] After configuring the target vehicle model, target vehicle data, and data collection duration, the data collection and control equipment can generate a data collection request and determine the data parameters of the target vehicle model based on the data collection request.

[0090] It should be understood that, in this embodiment, vehicle data for different vehicle models are typically stored separately in different types of TSPs. For example, vehicle data for model A is stored in TSP1, and vehicle data for model B is stored in TSP2. Therefore, after configuration, vehicle data adaptation is required before the TSP collects target vehicle data for the target model.

[0091] In one possible implementation, vehicle data adaptation includes storage adaptation and data parameter adaptation.

[0092] Specifically, different types of TSPs can be managed by a main TSP, and different types of TSPs can be understood as sub-TSPs under the main TSP. The specific process of storage adaptation is as follows: the main TSP, based on the preset correspondence between different vehicle models and TSP types, and according to the data collection request sent by the data collection and control equipment, obtains the identifier of the target vehicle model (e.g., "Vehicle Model A") contained in the data collection request, and determines the corresponding sub-TSP based on the target vehicle model.

[0093] For data parameter matching, vehicle data must adhere to corresponding technical specifications (such as communication protocols and data formats) during the acquisition process. Therefore, after determining the sub-TSP corresponding to the target vehicle model, the sub-TSP can determine the data parameters related to the target vehicle data. These data parameters can be understood as the data structure of the target vehicle data.

[0094] Furthermore, after the adaptation is complete, the TSP can send the data parameters to the acquisition and control device in the form of a configuration file, so that the acquisition and control device can evaluate the acquisition cost consumed in this acquisition process based on the data parameters.

[0095] In this embodiment of the application, a visual method for calculating the collection cost can also be provided, based on the visualization of the target vehicle model, target vehicle data, and data collection duration.

[0096] In one possible implementation, when calculating the acquisition cost, an acquisition cost display interface can be shown.

[0097] Figure 4This is a schematic diagram of a scenario for calculating acquisition costs provided in an embodiment of this application.

[0098] For example, such as Figure 4 As shown, after configuring the target vehicle model, target vehicle data, and data collection duration, the data acquisition and control equipment responds to the display command sent by the TSP. The data acquisition and control device can display the current data acquisition cost display interface 401 in the display area. The current data acquisition cost display interface 401 displays a "Data Acquisition Cost Calculation" control.

[0099] In the cost display interface 401, the data acquisition personnel can click to select the "Data Acquisition Cost Calculation" control, and the data acquisition control equipment will begin calculating the data acquisition cost.

[0100] 202. Based on the data parameters, determine the unit acquisition flow consumed in collecting target vehicle data. The unit acquisition flow is used to represent the flow consumed in a single collection of target vehicle data. The target vehicle is any vehicle under the target vehicle model.

[0101] In step 201, the data acquisition and control device receives data parameters sent from the TSP corresponding to the target vehicle model. Both target vehicle data acquisition and uploading are achieved through a communication network. For this network, bandwidth plays a crucial role, representing the number of bytes (B) or bits (b) consumed by the target vehicle data. Therefore, when calculating the acquisition cost, it is first necessary to determine the acquisition bandwidth consumed during the acquisition process.

[0102] In one possible implementation, for multiple vehicles under the target model, the target vehicle data is identical, and the collection and uploading of the target vehicle data are also the same. Furthermore, within the data collection duration, based on the target vehicle data collection cycle, the TSP can perform multiple cyclical collections of the target vehicle data. Therefore, for the collection traffic of the target model, the collection control equipment can first calculate the unit collection traffic under the target model based on data parameters. The unit collection traffic is the traffic consumed in a single collection of target vehicle data for any vehicle under the target model (i.e., the target vehicle), which is also the traffic consumed in collecting target vehicle data for the target vehicle in one collection cycle.

[0103] For example, when the collection period is 1 second, the unit collection flow is the flow generated by the target vehicle data of the target vehicle under model A collected in 1 second; when the collection period is 10 seconds, the unit collection flow is the flow generated by the target vehicle data of the target vehicle under model A collected in 10 seconds.

[0104] Another example is that there can be multiple collection periods at the same time. For example, when the data collection period is 1s and 10s, the unit collection flow is the flow generated by the target vehicle data of the target vehicle under model A collected together in 1s and 10s.

[0105] Optional data parameters include data packet header, target vehicle data identifier, timestamp, acquisition period, and controller area network fixed signal length.

[0106] The packet header is mainly used to identify the beginning of a packet frame.

[0107] It should be understood that the data transmission and uploading process of the target vehicle mainly relies on the communication between multiple electronic control units (ECUs, also known as controllers) in the target vehicle, or the communication between the ECU and the T-Box.

[0108] Optionally, the ECU in the target vehicle may include an engine control module (ECM) or engine control unit (ECU), hybrid control unit (HCU), battery management system (BMS), automatic transmission control unit (TCU), anti-lock braking system (ABS) controller, etc.

[0109] Optionally, the target vehicle supports communication methods including Controller Area Network (CAN) communication, Local Interconnect Network (LIN) communication, FlexRay communication, Media Oriented Systems Transport (MOST) communication, and Ethernet communication. The embodiments described below will use CAN communication as an example.

[0110] During the target vehicle data acquisition process, data is primarily obtained through different ECUs. For example, the ABS controller acquires vehicle speed, the BMS acquires battery level, and so on. This data is then transmitted to the T-Box via the CAN bus, which in turn forwards it to the TSP. Specifically, the target vehicle data is mainly transmitted between ECUs and between ECUs and the T-Box in the form of CAN data packets.

[0111] The identifier for the target vehicle data can be understood as the name of the configuration file during the target vehicle data collection process.

[0112] A timestamp is used to identify when a specific event occurs. In this embodiment, the timestamp is the time when the target vehicle data was collected.

[0113] The data collection period is the time interval at which data on the target vehicle is collected.

[0114] The CAN fixed signal length refers to the fixed parameters associated with each CAN data packet during its generation. Optionally, the CAN fixed signal length includes the CAN data packet generation time, the CAN data packet serial number, and the data compression identifier.

[0115] In one possible implementation, when calculating the unit acquisition flow rate based on data parameters, the data size (i.e., number of bits) occupied by each data parameter can be calculated separately, specifically including:

[0116] Determine the initial data size occupied by the target vehicle data collected during the data collection period;

[0117] The second data size occupied by the data packet header, the third data size occupied by the identifier of the target vehicle data, the fourth data size occupied by the timestamp, and the fifth data size occupied by the fixed signal length of the controller area network are determined.

[0118] The unit collection flow rate is determined based on the first, second, third, fourth, and fifth data sizes.

[0119] For example, after obtaining data parameters, the data acquisition and control equipment may have predefined bit counts for some parameters, or the bit counts for others can be calculated based on the target vehicle data. Therefore, the data acquisition and control equipment can directly obtain the bit counts for each type of data parameter.

[0120] The number of bits occupied by each data parameter is described below.

[0121] For the data packet header, optionally, the data packet header in this embodiment of the application includes a start character, a command identifier, a response identifier, a VIN, a data unit encryption method, a data unit length, and a block check character (BCC, also known as a message group check code or BCC check code).

[0122] Table 1 is an illustrative table showing the correspondence between a data packet header and the number of bytes occupied, provided in an embodiment of this application.

[0123] Table 1

[0124] Data packet header composition Number of bytes occupied (B) start symbol 2 Command identifier 1 Response identifier 1 VIN 17 Data unit encryption method 1 Data unit length 2 BCC verification code 1

[0125] For example, as shown in Table 1, the data packet header structure allows the acquisition and control device to obtain the number of bits occupied by the data packet header (second data size) as: 2+1+1+17+1++2+1=25*8=200b.

[0126] The number of bits occupied by the identifier of the target vehicle data (third data size) is 2*8=16b.

[0127] The number of bits occupied by the timestamp (the fourth data size) is 6 * 8 = 48 bits.

[0128] For a fixed CAN signal length, the total number of bits (fifth data size) occupied by the CAN data packet generation time, CAN data packet serial number, and data compression identifier is 9*8=72b.

[0129] In one possible implementation, the first data size occupied by the target vehicle data collected during the collection period, in this embodiment of the application, includes a first collection period and a second collection period, and the specific determination process includes:

[0130] Determine the sixth data size occupied by the target vehicle data collected in the first collection cycle, and the seventh data size occupied by the target vehicle data collected in the second collection cycle;

[0131] The sum of the sixth and seventh data sizes is determined as the first data size.

[0132] It should be understood that the target vehicle data is not a specific piece of data, but rather a type of data, such as... Figure 3 The target vehicle data configured in the system is chassis data, which can include various vehicle data such as vehicle speed, steering angle, and braking force.

[0133] Depending on the type of target vehicle data, some vehicle data is required to be collected once every first collection cycle, while other vehicle data is required to be collected once every second collection cycle.

[0134] Optionally, the first acquisition cycle is 1 second, and the second acquisition cycle is 10 seconds.

[0135] The data acquisition and control equipment can calculate the sixth data size occupied by the target vehicle data collected in the first acquisition cycle and the seventh data size occupied by the target vehicle data collected in the second acquisition cycle based on the vehicle data upload format between the T-Box and the sub-TSP.

[0136] Figure 5 This is a schematic diagram of the structure of vehicle data provided in an embodiment of this application.

[0137] For example, such as Figure 5 As shown, based on the vehicle data upload format, the number of bits occupied by the target vehicle data collected in the first collection cycle (sixth data size) can be expressed by the following formula (1):

[0138] The sixth data size = 4 * 8 + {(length of data 1-1 + length of data 1-2) + significant bits of data 1-1 + significant bits of data 1-2} * upload period; Formula (1)

[0139] In formula (1):

[0140] 4*8 represents the number of target vehicle data in the first collection cycle, and the total number of bits occupied in the first collection cycle.

[0141] The length of data 1-1: indicates the length of the first target vehicle data collected in the first collection cycle, usually in bytes (b).

[0142] The valid bit usually refers to whether the target vehicle data is correct and valid, and is generally 1 bit.

[0143] The valid bits of data 1-1 represent the valid bits of the first target vehicle data collected in the first collection cycle, 1 byte;

[0144] Length of Data 1-2: This indicates the length of the second target vehicle data collected in the first collection cycle, usually in bytes (b).

[0145] The valid bits of data 1-2 represent the valid bits of the second target vehicle data collected in the first acquisition cycle, usually in bits (b).

[0146] Upload cycle: This refers to the cycle in which target vehicle data is uploaded to the T-Box. In this embodiment, the upload cycle is 10 seconds. That is, although data 1-1 and data 1-2 are collected every 1 second, the time interval between reporting to the T-Box or the TSP is 10 seconds.

[0147] Similarly, the number of bits occupied by the target vehicle data collected in the second collection cycle (the seventh data size) can be expressed by the following formula (2):

[0148] The size of the seventh data point = 4 * 8 + {(length of data 2-1 + length of data 2-2) + significant bits of data 2-1 + significant bits of data 2-2}; Formula (2)

[0149] In formula (2):

[0150] 4*8 represents the number of target vehicle data in the second acquisition cycle, and the total number of bits occupied in the second acquisition cycle.

[0151] Data 2-1 length: indicates the length of the first target vehicle data collected in the second collection cycle, usually in bytes (b).

[0152] The valid bits of data 2-1 represent the valid bits of the first target vehicle data collected in the second acquisition cycle, 1 bit;

[0153] Data 2-2 length: indicates the length of the second target vehicle data collected in the second collection cycle, usually in bytes;

[0154] The valid bits in data 2-2 represent the valid bits of the second target vehicle data collected in the second acquisition cycle, usually in bits (b).

[0155] Since the second acquisition period in this embodiment is 10 seconds, which is the same as the upload period of 10 seconds, the target vehicle data is acquired during the second acquisition period, and the interval between acquisition and upload times is the same.

[0156] The above are just illustrative examples. The specific collection cycle, the amount of target vehicle data, the length of target vehicle data, and the upload cycle can be adjusted adaptively according to the collection needs.

[0157] Using the above formulas (1)-(2), the data acquisition and control equipment can obtain the first data size of the target vehicle data collected during the acquisition cycle.

[0158] Furthermore, when determining the unit collection flow rate based on the first, second, third, fourth, and fifth data sizes, the data can be summed cumulatively, i.e.:

[0159] Unit data collection volume = first data size + second data size + third data size + fourth data size + fifth data size.

[0160] In the aforementioned technical solution, this application proposes a specific method for determining the unit acquisition traffic based on data parameters. These data parameters include the data packet header, the target vehicle data identifier, the timestamp, the acquisition period, and the fixed signal length of the controller area network (SAR). Since the data parameters represent the data structure of the target vehicle data, the data size corresponding to each of the above data parameters can be calculated separately during the calculation of the unit acquisition traffic. For example, the data size occupied by the target vehicle data acquired during the acquisition period is the first data size, the data packet header is the second data size, the target vehicle data identifier is the third data size, the timestamp is the fourth data size, and the fixed signal length of the SAR is the fifth data size. Furthermore, the unit acquisition traffic is determined based on these five data sizes.

[0161] Since the target vehicle data is closely related to the vehicle model and data collection requirements, the above method of calculating the unit collection flow based on the data parameters and data collection duration of the target vehicle data can ensure that the corresponding unit collection flow is accurately calculated according to different vehicle models and data collection requirements.

[0162] In this application, the data collection period for target vehicle data is generally divided into two types: a first collection period and a second collection period. Based on this, when calculating the first data size of the target vehicle data collected in each collection period, this application can calculate the sixth data size occupied by the target vehicle data corresponding to the first collection period and the seventh data size occupied by the target vehicle data corresponding to the second collection period. The sixth and seventh data sizes are then summed to obtain the first data size. Furthermore, the first, second, third, fourth, and fifth data sizes are summed to obtain the unit collection flow rate.

[0163] It should be understood that the target vehicle data is transmitted over a network, and the network bandwidth determines the maximum amount of data (peak value) that the target vehicle data can be transmitted per unit time.

[0164] In one possible implementation, after calculating the unit collection traffic, it can be compared with the preset bandwidth (i.e., network bandwidth) in the embodiments of this application to determine whether it exceeds the preset bandwidth. Specifically, this includes:

[0165] The unit collection flow rate is displayed on the collection cost display interface;

[0166] If the sum of the unit collected traffic and bandwidth peak value is greater than the preset bandwidth, a second prompt message will be generated;

[0167] The second prompt message is displayed on the cost collection display interface.

[0168] For example, such as Figure 4 As shown, it is assumed that the preset bandwidth in this embodiment is 300Mb. Assume that through the above process, the data acquisition and control device calculates a unit acquisition traffic of 16Mb. However, in the past week, the peak bandwidth has reached 290Mb. By summing these values, it can be determined that the bandwidth required for the target vehicle to upload its data may reach 306Mb, exceeding the preset bandwidth of 300Mb. To ensure the smooth upload of the target vehicle data, the data acquisition and control device can prompt the acquisition personnel to perform a bandwidth expansion operation.

[0169] In one scenario, the data acquisition and control equipment can display a second prompt message on the current data acquisition cost display interface 401, such as... Figure 4 The data collected this time is 16Mb, and the peak bandwidth in the past week has reached 290Mb. This data collection is expected to exceed the preset bandwidth by 300Mb.

[0170] In another scenario, the data acquisition and control equipment can also use the identifiers of the data acquisition personnel associated with the data acquisition and control system (such as phone numbers, corporate email addresses, etc.) to send the bandwidth comparison results to the data acquisition personnel's terminal devices.

[0171] In the above technical solution, this application can also calculate whether the peak bandwidth reached during vehicle data transmission and the current unit collection traffic volume have exceeded the preset bandwidth. If they have, a second prompt message can be displayed on the collection cost display interface to remind the collection personnel to expand the preset bandwidth to ensure the smooth progress of the collection process.

[0172] 203. Based on the unit collection traffic, the cost parameters corresponding to the target vehicle model, and the data collection duration, determine the collection cost consumed in collecting data of the target vehicle model. The cost parameters are used to represent the resource consumption of collecting data of the target vehicle model within the data collection duration.

[0173] After obtaining the unit data collection traffic of the target vehicle, the data collection and control equipment can further determine the data collection cost incurred in this collection based on the cost parameters corresponding to the target vehicle model and the data collection duration.

[0174] Data acquisition costs are generally divided into bandwidth costs and storage costs. Bandwidth costs represent the network costs required to transmit vehicle data from the target vehicle to the distributed TSP. Storage costs represent the expenses incurred in occupying storage space when storing data at the distributed TSP. Therefore, cost parameters can represent the resource consumption of collecting target vehicle data of the target model within the data acquisition period, such as the unit price of bandwidth and the unit price of storage during the acquisition process.

[0175] Therefore, the data acquisition and control equipment can calculate the bandwidth cost and storage cost separately, and then obtain the data acquisition cost, including:

[0176] Based on the unit data collection traffic, cost parameters, and data collection duration, determine the bandwidth and storage costs consumed in collecting data from the target vehicles.

[0177] The acquisition cost is determined based on bandwidth and storage costs.

[0178] In the above technical solution, after determining the unit collection traffic, this application proposes a step for determining the collection cost. The collection cost in this application comprises two parts: the transmission cost of the target vehicle data (bandwidth cost) and the storage cost of the target vehicle data. Therefore, when calculating the collection cost, the bandwidth cost and storage cost consumed by the target vehicle data can be determined based on the unit collection traffic, cost parameters, and data collection duration. Then, the collection cost is determined based on the bandwidth cost and storage cost. This method of determining the collection cost considers both the cost of transmitting and storing the target vehicle data, achieving accurate control and monitoring of the collection cost during the data collection process, and ensuring the rationality and accuracy of the collection cost calculation.

[0179] Specifically, cost parameters include the average peak number of online vehicles for the target vehicle model within the data collection period, bandwidth consumption per unit, daily runtime, estimated sales volume of the target vehicle model within the data collection period, upload cycle of target vehicle data, and storage consumption per unit. The average peak number of online vehicles for the target vehicle model within the data collection period represents the average of the peak online vehicles for the target vehicle model within that period. For example, if the data collection period is one month, the average peak number of online vehicles represents the average of the peak online vehicles for the target vehicle model within that month.

[0180] Combination Figure 3 The data collection duration is set during the configuration process.

[0181] After obtaining the cost parameters, specifically, when calculating bandwidth and storage costs, the following steps are included:

[0182] Determine the target bandwidth unit resource consumption and target storage unit resource consumption corresponding to the data acquisition duration;

[0183] The bandwidth cost is determined based on the unit traffic volume collected, the average peak online vehicle volume, and the target bandwidth unit resource consumption.

[0184] The storage cost is determined based on the unit data collection traffic, daily runtime, upload cycle, estimated sales volume, target storage unit resource consumption, and data collection duration.

[0185] For example, when the data collection period is one month, the bandwidth cost and storage cost can be calculated using the following formulas (3)-(4):

[0186] Bandwidth cost = Unit collection traffic * Monthly average online vehicle peak * Target bandwidth unit price Formula (3) Storage cost = Unit collection traffic * (Daily runtime / Upload cycle) * 30 * Estimated actual sales volume of target vehicle model within one month * Target storage unit price Formula (4)

[0187] Wherein: 30 indicates that the data collection period in this embodiment is one month, which is 30 days. The monthly average peak online vehicle count is the average peak online vehicle count of the target vehicles within one month.

[0188] The target bandwidth unit resource consumption is the target bandwidth unit price, and the target storage unit resource consumption is the target storage unit price; both are related to the data acquisition duration.

[0189] For example, such as Figure 4 As shown, when the data collection period is one month, the target bandwidth unit price is xxx yuan / MB / month. Similarly, the target storage unit price is xxx yuan / month.

[0190] When the data collection period is one quarter, the target bandwidth unit price is xxx yuan / MB / quarter. Similarly, the target storage unit price is xxx yuan / quarter.

[0191] It should be understood that when calculating bandwidth costs, bandwidth represents the maximum amount of target vehicle data that can be transmitted per unit time. Therefore, when calculating bandwidth costs, it is necessary to focus on the average peak value of online vehicles under the target vehicle model. Online vehicles refer to vehicles that are powered on. Furthermore, in this embodiment, regardless of the number of data collections, the bandwidth per collection is the same. Therefore, the bandwidth cost consumed in each collection process is also the same. When calculating bandwidth costs, this embodiment only needs to calculate the bandwidth cost consumed in a single collection process.

[0192] When storing target vehicle data, the TSP stores data for all online vehicles under the target model. Therefore, when calculating storage costs, the focus is on the estimated actual sales volume for the target model. This value can be estimated from the actual sales volume of the target model in the previous year and is displayed in the estimated monthly cost display interface 401 of this application.

[0193] In another scenario, if the data collection time changes, it can be deduced according to the above calculation process, which will not be elaborated in this embodiment.

[0194] In the aforementioned technical solution, the cost parameters for calculating bandwidth and storage costs primarily include the average peak number of online vehicles for the target vehicle model, bandwidth resource consumption per unit, daily runtime, estimated sales volume of the target vehicle model within the data collection period, upload cycle, and storage resource consumption per unit. The bandwidth resource consumption per unit and storage resource consumption per unit vary depending on the data collection period. For example, if the data collection period is monthly, the bandwidth resource consumption per unit and storage resource consumption per unit are calculated on a monthly basis. If the data collection period is yearly, the bandwidth resource consumption per unit and storage resource consumption per unit are calculated on an annual basis.

[0195] Therefore, when calculating bandwidth and storage costs, this application can first determine the corresponding target bandwidth unit resource consumption and target storage unit resource consumption based on the data collection duration.

[0196] Furthermore, bandwidth costs can be obtained by calculating unit traffic volume, average peak online traffic, and target bandwidth unit resource consumption. Storage costs can be obtained by calculating unit traffic volume, daily runtime, upload cycle, estimated sales volume, target storage unit resource consumption, and data collection duration.

[0197] After obtaining the bandwidth cost and storage cost, the bandwidth cost and storage cost can be summed to obtain the final acquisition cost.

[0198] In one possible implementation, the data collectors can pre-set the preset data collection cost for all vehicles of each vehicle model, according to the different vehicle models and vehicle data.

[0199] For example, such as Figure 3 As shown, the data acquisition personnel configure the preset acquisition costs for chassis, body, powertrain, cabin, and driver assistance data under vehicle model A, vehicle model B, vehicle model C, vehicle model C, and vehicle model D through configuration operations in the data acquisition and management system.

[0200] In response to the configuration operations of the data acquisition personnel, the data acquisition and control equipment sends all the preset data acquisition costs for each vehicle type to the corresponding TSP for each vehicle type for storage.

[0201] After the data collection personnel have configured the target vehicle model and target vehicle data, the data collection and control system can obtain the preset data collection cost corresponding to the target vehicle data under the target vehicle model through the sub-TSP corresponding to the target vehicle model.

[0202] After calculating the data collection cost, the data collection and control equipment can further determine whether the data collection exceeds the budget through comparison, specifically including:

[0203] If the data collection cost is greater than the preset data collection cost, a first prompt message is generated based on the data collection cost and the preset data collection cost.

[0204] The first prompt message is displayed on the cost collection display interface.

[0205] For example, such as Figure 4 As shown, assuming the data acquisition and control equipment calculates the cost of this data acquisition to be 289 yuan, the corresponding preset cost of data acquisition is 250 yuan. The cost of this data acquisition exceeds the preset cost.

[0206] In one scenario, the data collection and control equipment can generate an initial alert message, such as... Figure 4 As shown, the first prompt message is: "The cost of this data collection is 289 yuan, which exceeds the preset data collection cost of 250 yuan."

[0207] In another scenario, the data acquisition and control equipment can also use voice prompts, such as playing a voice message through the corresponding audio playback device that says, "The cost of this data acquisition is 289 yuan, which exceeds the preset cost of 250 yuan."

[0208] In another scenario, the data acquisition and control equipment can also use the identifiers of the data acquisition personnel associated with the data acquisition and control system (such as phone numbers, corporate email addresses, etc.) to send the calculation results to the data acquisition personnel's terminal devices.

[0209] In the above technical solution, when calculating the data collection cost, this application also provides a visual cost viewing method, specifically, a data collection cost display interface. This application can pre-set corresponding preset data collection costs for vehicle data of different models. After calculating the data collection cost, the cost can be compared with the preset cost to determine whether the current cost exceeds the budget. If the cost exceeds the preset cost, a prompt message is displayed on the data collection cost display interface so that data collection personnel can clearly understand the specific overspending situation.

[0210] In summary, this application proposes a method for determining vehicle data collection costs during the vehicle data collection process. The specific process is as follows: First, in response to a data collection request for a target vehicle model, data parameters related to the target vehicle data under that target model are determined. These data parameters can be used to represent the data structure of the target vehicle data, or they can be understood as the data parameters constituting the target vehicle data. After obtaining the data parameters of the target vehicle data, this application can calculate the unit collection traffic consumed in collecting the target vehicle data using these parameters. The unit collection traffic refers to the traffic consumed in a single collection of target vehicle data for any vehicle under the target model. Target vehicle data typically corresponds to a data collection duration. Furthermore, based on the unit collection traffic, the cost parameters corresponding to the target model, and the data collection duration, this application can determine the collection cost consumed in collecting the target vehicle data. The cost parameter can represent the resource consumption status of collecting target vehicle data for the target model within the data collection duration. The above-mentioned method for monitoring the target vehicle data collection cost during the target vehicle data collection process can be achieved by using data parameters, cost parameters, and data collection duration related to the target vehicle data, providing a smart cost budgeting solution for data collection personnel. This avoids the resource consumption problem caused by excessive collection costs during the process of collecting vehicle data.

[0211] This application proposes a specific method for determining the unit acquisition traffic based on data parameters. These data parameters include the data packet header, the target vehicle data identifier, the timestamp, the acquisition period, and the fixed signal length of the controller area network (SAR). Since the data parameters represent the data structure of the target vehicle data, the data size corresponding to each of the above data parameters can be calculated separately during the calculation of the unit acquisition traffic. For example, the data size occupied by the target vehicle data acquired during the acquisition period is the first data size, the data packet header is the second data size, the target vehicle data identifier is the third data size, the timestamp is the fourth data size, and the fixed signal length of the SAR is the fifth data size. Furthermore, the unit acquisition traffic is determined based on these five data sizes.

[0212] Since the target vehicle data is closely related to the vehicle model and data collection requirements, the above method of calculating the unit data collection flow based on the data parameters of the target vehicle data can ensure that the corresponding unit data collection flow is accurately calculated according to different vehicle models and data collection requirements.

[0213] In this application, the data collection period for target vehicle data is generally divided into two types: a first collection period and a second collection period. Based on this, when calculating the first data size of the target vehicle data collected in each collection period, this application can calculate the sixth data size occupied by the target vehicle data corresponding to the first collection period and the seventh data size occupied by the target vehicle data corresponding to the second collection period. The sixth and seventh data sizes are then summed to obtain the first data size. Furthermore, the first, second, third, fourth, and fifth data sizes are summed to obtain the unit collection flow rate.

[0214] After determining the unit data collection traffic, this application proposes a step for determining the collection cost. The collection cost in this application comprises two parts: the transmission cost of the target vehicle data (bandwidth cost) and the storage cost of the target vehicle data. Therefore, when calculating the collection cost, the bandwidth cost and storage cost consumed by the target vehicle data can be determined based on the unit data collection traffic, cost parameters, and data collection duration. Then, the collection cost is determined based on the bandwidth cost and storage cost. This method of determining the collection cost considers both the cost of transmitting and storing the target vehicle data, enabling accurate control and monitoring of the collection cost during the data collection process, and ensuring the rationality and accuracy of the collection cost calculation.

[0215] Specifically, in calculating bandwidth and storage costs, the main cost parameters include the average peak number of online vehicles for the target vehicle model, bandwidth consumption per unit, daily runtime, estimated sales volume of the target vehicle model within the data collection period, upload cycle, and storage consumption per unit. The bandwidth and storage consumption per unit vary depending on the data collection period. For example, if the data collection period is monthly, the bandwidth and storage consumption per unit are calculated on a monthly basis. If the data collection period is yearly, the bandwidth and storage consumption per unit are calculated on an annual basis.

[0216] Therefore, when calculating bandwidth and storage costs, this application can first determine the corresponding target bandwidth unit resource consumption and target storage unit resource consumption based on the data collection duration.

[0217] Furthermore, bandwidth costs can be obtained by calculating unit traffic volume, average peak online traffic, and target bandwidth unit resource consumption. Storage costs can be obtained by calculating unit traffic volume, daily runtime, upload cycle, estimated sales volume, target storage unit resource consumption, and data collection duration.

[0218] In calculating data collection costs, this application also provides a visual cost viewing method, specifically a data collection cost display interface. This application allows for pre-setting corresponding preset data collection costs for different vehicle models. After calculating the data collection cost, it can be compared with the preset cost to determine if the current cost exceeds the budget. If the cost exceeds the preset cost, a prompt message is displayed on the data collection cost display interface so that data collection personnel can clearly understand the specific overrun situation.

[0219] In addition to displaying cost overruns, this application can also calculate whether the peak bandwidth reached during vehicle data transmission and the current unit collection traffic volume have exceeded the preset bandwidth. If exceeded, a second prompt message can be displayed on the collection cost display interface to remind the collection personnel to expand the preset bandwidth to ensure the smooth progress of the collection process.

[0220] Figure 6 This is a schematic diagram of a device for determining the cost of vehicle data collection, provided in an embodiment of this application.

[0221] For example, such as Figure 6 As shown, the device 600 includes:

[0222] The determination module 601 is used to respond to a data collection request for a target vehicle model, determine the data parameters for collecting target vehicle data of the target vehicle model, the data parameters being used to represent the data structure of the target vehicle data; based on the data parameters, determine the unit collection traffic consumed in collecting the target vehicle data, the unit collection traffic being used to represent the traffic consumed in a single collection of the target vehicle data, the target vehicle being any vehicle under the target vehicle model; based on the unit collection traffic, the cost parameters corresponding to the target vehicle model, and the data collection duration, determine the collection cost consumed in collecting the target vehicle data, the cost parameters being used to represent the resource status consumed in collecting the target vehicle data of the target vehicle model within the data collection duration.

[0223] In one possible implementation, the data parameters include a data packet header, an identifier of the target vehicle data, a timestamp, a collection period, and a fixed signal length of the controller area network. The determining module 601 is specifically used to: determine a first data size occupied by the target vehicle data collected in the collection period; determine a second data size occupied by the data packet header, a third data size occupied by the identifier of the target vehicle data, a fourth data size occupied by the timestamp, and a fifth data size occupied by the fixed signal length of the controller area network; and determine the unit collection traffic based on the first data size, the second data size, the third data size, the fourth data size, and the fifth data size.

[0224] In one possible implementation, the acquisition cycle includes a first acquisition cycle and a second acquisition cycle. The determining module 601 is further configured to: determine the sixth data size occupied by the target vehicle data acquired in the first acquisition cycle and the seventh data size occupied by the target vehicle data acquired in the second acquisition cycle; determine the sum of the sixth data size and the seventh data size as the first data size; and determine the sum of the first data size, the second data size, the third data size, the fourth data size and the fifth data size as the unit acquisition flow rate.

[0225] In one possible implementation, the determining module 601 is further configured to: determine the bandwidth cost and storage cost consumed in collecting the target vehicle data based on the unit collection traffic, the cost parameter, and the data collection duration; and determine the collection cost based on the bandwidth cost and the storage cost.

[0226] In one possible implementation, the cost parameters include the average peak online vehicle count of the target vehicle model within the data collection period, bandwidth unit resource consumption, daily runtime, estimated sales volume of the target vehicle model within the data collection period, upload cycle of the target vehicle data, and storage unit resource consumption. The average peak online vehicle count of the target vehicle model within the data collection period represents the average value of the peak online vehicle count of the target vehicle model within the data collection period. The determining module 601 is further configured to: determine the target bandwidth unit resource consumption and target storage unit resource consumption corresponding to the data collection period; determine the bandwidth cost based on the unit collection traffic, the average peak online vehicle count, and the target bandwidth unit resource consumption; and determine the storage cost based on the unit collection traffic, the daily runtime, the upload cycle, the estimated sales volume, the target storage unit resource consumption, and the data collection period.

[0227] Optionally, the device further includes: a first processing module, configured to display a data acquisition cost display interface; generate a first prompt message based on the data acquisition cost and the preset data acquisition cost when the data acquisition cost is greater than the preset data acquisition cost; and display the first prompt message on the data acquisition cost display interface.

[0228] Optionally, the device further includes: a second processing module, configured to display the unit collection traffic on the collection cost display interface; generate a second prompt message if the sum of the unit collection traffic and the bandwidth peak exceeds a preset bandwidth; and display the second prompt message on the collection cost display interface.

[0229] Figure 7 This is a schematic diagram of the structure of a data acquisition and control device provided in an embodiment of this application.

[0230] For example, such as Figure 7 As shown, the data acquisition and control device 101 includes a memory 701 and a processor 702. The memory 701 stores executable program code 7011, and the processor 702 is used to call and execute the executable program code 7011 to perform a method for determining the cost of vehicle data acquisition.

[0231] This embodiment can divide the data acquisition and control equipment into functional modules according to the above method example. For example, each module can correspond to a separate function, or two or more functions can be integrated into one processing module. The integrated module can be implemented in hardware. It should be noted that the module division in this embodiment is illustrative and only represents one logical functional division. In actual implementation, there may be other division methods.

[0232] When each functional module is divided according to its corresponding function, the data acquisition and control device may include: a determination module, etc. It should be noted that all relevant content of each step involved in the above method embodiments can be referenced from the functional description of the corresponding functional module, and will not be repeated here.

[0233] The data acquisition and control device provided in this embodiment is used to execute the above-described method for determining the cost of vehicle data acquisition, and thus can achieve the same effect as the above-described implementation method.

[0234] When using integrated units, the data acquisition and control equipment may include a processing module and a storage module. The processing module is used to control and manage the actions of the data acquisition and control equipment. The storage module supports the execution of program code and data by the data acquisition and control equipment.

[0235] The processing module may be a processor or a controller, which can implement or execute various exemplary logic blocks, modules, and circuits as disclosed in this application. The processor may also be a combination of computing functions, such as a combination of one or more microprocessors, a combination of digital signal processing (DSP) and microprocessors, etc., and the storage module may be a memory.

[0236] This embodiment also provides a computer-readable storage medium storing computer program code. When the computer program code is run on a computer, the computer executes the above-described method steps to implement a method for determining vehicle data collection costs as described in the above embodiment.

[0237] This embodiment also provides a computer program product that, when run on a computer, causes the computer to perform the aforementioned steps to implement a method for determining vehicle data collection costs as described in the above embodiment.

[0238] In addition, the data acquisition and control device provided in the embodiments of this application may specifically be a chip, component or module. The electronic device may include a connected processor and a memory. The memory is used to store instructions. When the data acquisition and control device is running, the processor may call and execute the instructions to make the chip execute a method for determining the cost of vehicle data acquisition in the above embodiments.

[0239] In this embodiment, the data acquisition and control device, computer-readable storage medium, computer program product or chip are all used to execute the corresponding methods provided above. Therefore, the beneficial effects that can be achieved can be referred to the beneficial effects of the corresponding methods provided above, and will not be repeated here.

[0240] Through the above description of the embodiments, those skilled in the art will understand that, for the sake of convenience and brevity, only the division of the above functional modules is used as an example. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above.

[0241] In the embodiments provided in this application, it should be understood that the disclosed apparatus and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of modules or units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another device, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between devices or units may be electrical, mechanical, or other forms.

[0242] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A method of determining the cost of vehicle data collection, characterized by, The method includes: In response to a data collection request for a target vehicle model, data parameters for collecting target vehicle data of the target vehicle model are determined, wherein the data parameters are used to represent the data structure of the target vehicle data; Based on the data parameters, the unit collection flow rate consumed in collecting the target vehicle data is determined. The unit collection flow rate is used to represent the flow rate consumed in a single collection of the target vehicle data. The target vehicle is any vehicle under the target vehicle model. Based on the unit collection traffic, cost parameters, and data collection duration, the bandwidth cost and storage cost consumed in collecting the target vehicle data are determined. The cost parameters are used to represent the resource consumption status of collecting the target vehicle data of the target vehicle model within the data collection duration. The acquisition cost is determined based on the bandwidth cost and the storage cost; The cost parameters include the average peak number of online vehicles for the target vehicle model within the data collection period, bandwidth unit resource consumption, daily runtime, estimated sales volume of the target vehicle model within the data collection period, upload cycle of the target vehicle data, and storage unit resource consumption. The average peak number of online vehicles for the target vehicle model within the data collection period represents the average value of the peak number of online vehicles for the target vehicle model within the data collection period. Determining the bandwidth cost and storage cost consumed in collecting the target vehicle data based on the unit collection traffic, the cost parameters, and the data collection period includes: Determine the target bandwidth unit resource consumption and the target storage unit resource consumption corresponding to the data acquisition duration; The bandwidth cost is determined based on the unit traffic volume collected, the average peak online vehicle volume, and the target bandwidth unit resource consumption. The storage cost is determined based on the unit data collection traffic, the daily runtime, the upload cycle, the estimated actual sales volume, the target storage unit resource consumption, and the data collection duration.

2. The method of claim 1, wherein, The data parameters include a data packet header, an identifier for the target vehicle data, a timestamp, a collection period, and a fixed signal length in the controller area network. Determining the unit collection traffic consumed in collecting the target vehicle data based on these data parameters includes: Determine the first data size occupied by the target vehicle data collected during the collection period; The second data size occupied by the data packet header, the third data size occupied by the identifier of the target vehicle data, the fourth data size occupied by the timestamp, and the fifth data size occupied by the fixed signal length of the controller area network are determined. The unit collection flow rate is determined based on the first data size, the second data size, the third data size, the fourth data size, and the fifth data size.

3. The method of claim 2, wherein, The data acquisition cycle includes a first data acquisition cycle and a second data acquisition cycle. Determining the first data size occupied by the target vehicle data acquired in the data acquisition cycle includes: Determine the sixth data size occupied by the target vehicle data collected in the first collection cycle, and the seventh data size occupied by the target vehicle data collected in the second collection cycle; The sum of the sixth data size and the seventh data size is determined as the first data size; And, determining the unit collection flow rate based on the first data size, the second data size, the third data size, the fourth data size, and the fifth data size includes: The summation of the first data size, the second data size, the third data size, the fourth data size, and the fifth data size is determined as the unit collection flow rate.

4. The method of claim 1, wherein, The method further includes: Display the cost collection interface; If the acquisition cost is greater than the preset acquisition cost, a first prompt message is generated based on the acquisition cost and the preset acquisition cost. The first prompt message is displayed on the cost collection display interface.

5. The method of claim 4, wherein, The method further includes: The unit collection flow rate is displayed on the collection cost display interface; If the sum of the unit's collected traffic and bandwidth peak value is greater than the preset bandwidth, a second prompt message is generated; The second prompt message is displayed on the cost collection display interface.

6. An apparatus for determining the cost of vehicle data collection, characterized by The device includes: A determination module is configured to, in response to a data collection request for a target vehicle model, determine the data parameters for collecting target vehicle data of the target vehicle model, wherein the data parameters represent the data structure of the target vehicle data; based on the data parameters, determine the unit collection traffic consumed in collecting the target vehicle data, wherein the unit collection traffic represents the traffic consumed in a single collection of target vehicle data of the target vehicle, wherein the target vehicle is any vehicle under the target vehicle model; based on the unit collection traffic, cost parameters, and data collection duration, determine the bandwidth cost and storage cost consumed in collecting the target vehicle data, wherein the cost parameters represent the resource consumption status in collecting the target vehicle data of the target vehicle model within the data collection duration; and based on the bandwidth cost and the storage cost, determine the collection cost. The cost parameters include the average peak online vehicle count of the target vehicle model within the data collection period, bandwidth unit resource consumption, daily runtime, estimated actual sales volume of the target vehicle model within the data collection period, upload cycle of the target vehicle data, and storage unit resource consumption. The average peak online vehicle count of the target vehicle model within the data collection period represents the average value of the peak online vehicle count of the target vehicle model within the data collection period. The determining module is specifically used for: Determine the target bandwidth unit resource consumption and the target storage unit resource consumption corresponding to the data acquisition duration; The bandwidth cost is determined based on the unit traffic volume collected, the average peak online vehicle volume, and the target bandwidth unit resource consumption. The storage cost is determined based on the unit data collection traffic, the daily runtime, the upload cycle, the estimated actual sales volume, the target storage unit resource consumption, and the data collection duration.

7. A collection management device, characterized by The data acquisition and control equipment includes: Memory, used to store executable program code; A processor is configured to call and run the executable program code from the memory, causing the acquisition and control device to perform the method as described in any one of claims 1 to 5.

8. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed, implements the method as described in any one of claims 1 to 5.

Citation Information

Patent Citations

  • Data processing job scheduling method and device, computer equipment and storage medium

    CN110297701A

  • Method and device for determining transmission resources and storage medium

    CN111447592A