Data acquisition method and device, electronic equipment and storage medium

Abstract

The embodiment of the invention provides a data acquisition method and device, electronic equipment and a storage medium, which can improve the data quality of transmitted data in the process of multiplexing an intelligent driving domain controller to perform data acquisition and transmitting the data to the data acquisition equipment under the condition of limited bandwidth, and improve the data transmission efficiency. And the storage space utilization rate of the data storage equipment is improved. The data acquisition method comprises the following steps: receiving image data from multiple paths of vehicle-mounted cameras; determining the actual driving distance of the vehicle; and in response to the fact that the actual driving distance reaches the positive integer multiple of the set spacing distance every time, image data in the actual driving distance are sent to the data acquisition equipment.

Description

Technical Field

[0001] The present application relates to the field of vehicle technology, and in particular to a data acquisition method, device, electronic device, and storage medium. Background Art

[0002] At present, in order to train intelligent driving models, a large amount of data collection is usually required. For example, data is collected by reusing the intelligent driving domain controller and transmitted to the data acquisition device. However, due to the large amount of collected data and the limited bandwidth between the intelligent driving domain controller and the data acquisition device, the transmitted data can only be compressed, resulting in poor data quality in the data acquisition device and occupying more storage space. Summary of the Invention

[0003] The embodiments of the present application provide a data acquisition method, apparatus, electronic device, and storage medium, which can improve the data quality of the transmitted data and the storage space utilization of the data storage device when multiplexing an intelligent driving domain controller to collect data and transmit it to a data storage device under limited bandwidth.

[0004] In a first aspect, an embodiment of the present application provides a data acquisition method, which is applied to an intelligent driving domain controller, wherein the intelligent driving domain controller is communicatively connected to a data acquisition device, and the method includes: Receive image data from multiple vehicle-mounted cameras; Get the actual driving distance of the vehicle; In response to each time the actual driving distance reaches a positive integer multiple of a set interval distance, image data at the actual driving distance is sent to the data acquisition device.

[0005] In an embodiment of the present application, the intelligent driving domain controller receives image data from multiple vehicle-mounted cameras in real time, and detects the actual driving distance in real time. When the actual driving distance reaches a positive integer multiple of the set interval distance, that is, every time the set interval distance is reached, the image data at the actual driving distance is sent to the data acquisition device. Therefore, while ensuring the availability of the transmitted image data, the amount of image data transmitted between the intelligent driving domain controller and the image acquisition device is reduced, so that when the bandwidth is limited, there is no need to compress the transmitted image data, thereby ensuring the quality of the transmitted image data and improving the storage space utilization of the data acquisition device.

[0006] Optionally, in response to the actual driving distance reaching a positive integer multiple of a set interval distance, sending image data at the actual driving distance to the data acquisition device includes: determining the actual driving time when the actual driving distance reaches a positive integer multiple of the set interval distance; The image data at the actual driving time is sent to the data acquisition device.

[0007] In an embodiment of the present application, the actual driving time corresponding to each time the actual driving distance of the vehicle reaches a positive integer multiple of the set interval distance is determined in real time, and then the image data corresponding to the actual driving time is sent to the data acquisition device. Therefore, while ensuring the availability of the transmitted image data, the amount of image transmission data between the intelligent driving domain controller and the image acquisition device is reduced, so that even in the case of limited bandwidth, there is no need to compress the transmitted image data, thereby ensuring the quality of the transmitted image data and improving the storage space utilization of the data acquisition device.

[0008] Optionally, determining the actual driving time when the actual driving distance reaches a positive integer multiple of the set interval distance includes: The actual driving time when the actual driving distance reaches a positive integer multiple of the set interval distance is determined according to the wheel speed mileage calculation method.

[0009] In the embodiment of the present application, the actual driving time when the actual driving distance reaches a positive integer multiple of the set interval distance can be accurately determined based on the wheel speed mileage calculation method.

[0010] Optionally, sending the image data at the actual driving time to the data acquisition device includes: Assigning time stamps to the image data from the multiple vehicle-mounted cameras respectively; The image data having the timestamp close to the actual driving time is sent to the data acquisition device.

[0011] In an embodiment of the present application, image data from multiple vehicle-mounted cameras are assigned timestamps respectively, and then the image data collected by each vehicle-mounted camera, whose timestamp is close to the actual driving time, is sent to the data acquisition device, thereby ensuring the synchronization of the image data sent to the data acquisition device.

[0012] Optionally, assigning timestamps to the image data from the multiple vehicle-mounted cameras respectively includes: The image data from the multiple vehicle-mounted cameras are respectively given time stamps according to the hardware time.

[0013] In the embodiment of the present application, a timestamp is assigned to the image data of each vehicle-mounted camera according to the hardware time, thereby ensuring the accuracy of the assigned timestamp.

[0014] Optionally, the intelligent driving domain controller is communicatively connected to the data acquisition device through an on-board diagnostic system interface.

[0015] In the embodiment of the present application, since the interface of the intelligent driving domain controller is exposed through the on-board diagnostic system interface, the intelligent driving domain controller can communicate with the data acquisition device through the vehicle's own on-board diagnostic system interface, thereby avoiding dismantling and modification of the vehicle.

[0016] Optionally, the intelligent driving domain controller and the data acquisition device run the same operating system.

[0017] In an embodiment of the present application, the intelligent driving domain controller and the data acquisition device run the same operating system, so that the intelligent domain controller and the data acquisition device can use the same method to analyze image data.

[0018] In a second aspect, an embodiment of the present application provides a data acquisition device, which is applied to an intelligent driving domain controller, wherein the intelligent driving domain controller is communicatively connected to a data acquisition device, and the method includes: A data receiving unit, used for receiving image data from multiple vehicle-mounted cameras; a distance determination unit, for determining an actual travel distance of the vehicle; The data sending unit is used to send image data at the actual driving distance to the data acquisition device in response to the actual driving distance reaching a positive integer multiple of the set interval distance.

[0019] Optionally, the data sending unit includes: a driving time determining unit, configured to determine the actual driving time when the actual driving distance reaches a positive integer multiple of the set interval distance; An image data sending unit is used to send the image data at the actual driving time to the data acquisition device.

[0020] Optionally, the travel time determination unit is specifically configured to: The actual driving time when the actual driving distance reaches a positive integer multiple of the set interval distance is determined according to the wheel speed mileage calculation method.

[0021] Optionally, the image data sending unit includes: A timestamp assigning subunit, configured to assign timestamps to the image data from the multiple vehicle-mounted cameras respectively; The image data sending subunit is used to send the image data with the timestamp close to the actual driving time to the data acquisition device.

[0022] Optionally, the timestamp assigning subunit is specifically used for: The image data from the multiple vehicle-mounted cameras are respectively given time stamps according to the hardware time.

[0023] Optionally, the intelligent driving domain controller is communicatively connected to the data acquisition device through an on-board diagnostic system interface.

[0024] Optionally, the intelligent driving domain controller and the data acquisition device run the same operating system.

[0025] In a third aspect, an embodiment of the present application provides an electronic device, comprising a memory for storing a computer program and a processor for executing the computer program, wherein, when the computer program is executed by the processor, the electronic device is triggered to execute the steps of the method described in any embodiment of the first aspect.

[0026] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, which is used to store a computer program. When the computer program is executed by a processor, the processor executes the steps of the method described in any embodiment of the first aspect.

[0027] It should be understood that the second to fourth aspects of the embodiments of the present application are consistent with the technical solutions of the first aspect of the embodiments of the present application, and the beneficial effects achieved by each aspect and the corresponding feasible implementation methods are similar and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0028] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the following briefly introduces the drawings required for use in the embodiments. Obviously, the drawings described below are only some embodiments of this specification. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0029] Figure 1 An architectural diagram of a data acquisition system provided in an embodiment of the present application; Figure 2 An architectural diagram of another data acquisition system provided in an embodiment of the present application; Figure 3 A flow chart of a data collection method provided in an embodiment of the present application; Figure 4 A flowchart of a method for an intelligent driving domain controller to send image data to a data acquisition device provided in an embodiment of the present application; Figure 5 A flowchart of another method for an intelligent driving domain controller to send image data to a data acquisition device provided in an embodiment of the present application; Figure 6A schematic diagram of the structure of a data acquisition device provided in an embodiment of the present application; Figure 7 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0030] In order to better understand the technical solutions of this specification, the embodiments of the present application are described in detail below with reference to the accompanying drawings.

[0031] It should be clear that the embodiments described are only part of the embodiments of this specification, not all of the embodiments. Based on the embodiments in this specification, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this specification.

[0032] The terms used in the examples of this application are for the purpose of describing specific embodiments only and are not intended to limit this specification. The singular forms "a," "an," "the," and "the" used in the examples of this application and the appended claims are also intended to include the plural forms unless the context clearly indicates otherwise.

[0033] Currently, training intelligent driving models typically requires large amounts of data collection. For example, to train an automated parking model in the intelligent driving field, data can be collected by reusing an intelligent driving domain controller (DDC) and transmitted to a data acquisition device. Subsequently, image samples with discrepancies are used for model training. However, due to the large amount of data collected by the DDC and the limited bandwidth between the DDC and the data acquisition device, the transmitted data must be compressed, resulting in poor data quality in the data acquisition device and requiring more storage space.

[0034] In view of this, an embodiment of the present application provides a data acquisition method, in which every time the vehicle travels a certain distance, the intelligent driving domain controller sends image data collected by multiple vehicle-mounted cameras at that location to the data acquisition device. This reduces the amount of data transmitted between the intelligent driving domain controller and the image acquisition device while ensuring that the data acquisition device can collect different image data. This eliminates the need to compress the transmitted image data even when bandwidth is limited, thereby ensuring the quality of the transmitted image data and improving the storage space utilization of the data acquisition device.

[0035] The technical solution protected by this application is described in detail below with reference to the accompanying drawings.

[0036] See Figure 1 , is an architecture diagram of a data acquisition system provided in an embodiment of the present application. Figure 1As shown, the data acquisition system includes an intelligent driving domain controller 101 and a data acquisition device 102. The intelligent driving domain controller 101 can receive image data from multiple onboard cameras. The intelligent driving domain controller 101 and the data acquisition device 102 share the same data transmission interface, including but not limited to an Ethernet interface or a wireless network transmission interface. For example, the Ethernet interface of the intelligent driving domain controller 101 is exposed through the on-board diagnostics (OBD) interface, allowing the intelligent driving domain controller 101 to communicate with the Ethernet interface of the data acquisition device 102 via the OBD interface, thus avoiding the need to dismantle or modify the vehicle. Furthermore, the intelligent driving domain controller 101 can send image data to the data acquisition device 102 via the OBD interface. Furthermore, the intelligent driving domain controller 101 and the data acquisition device 102 use the same operating system, for example, both running the Linux operating system. This allows data to be parsed using the same method when data is transmitted between the intelligent driving domain controller 101 and the data acquisition device 102. Furthermore, the storage module in the data acquisition device 102 must be robust against vibration and shock. Therefore, it can utilize an SSD with a storage capacity greater than 4TB. It should be understood that the data stored in the data acquisition device 102 can be later used to train intelligent driving models. The data acquisition device 102 can be powered by a 12V DC power supply, which, while achieving low power consumption, meets the power requirements of the OBD data interface.

[0037] See Figure 2 , is an architecture diagram of another data acquisition system provided in an embodiment of the present application. Figure 1 compared to, Figure 2 The main difference is that data acquisition device 102 can also be equipped with another Ethernet interface to achieve communication between data acquisition device 102 and host computer 103. On this basis, data acquisition device 102 can route image data and other necessary data (such as intermediate data of image processing algorithms) from intelligent driving domain controller 101 to host computer 103, so that testers can debug the data acquisition system.

[0038] See Figure 3 , is a flow chart of a data collection method provided in an embodiment of the present application. The method is applied to Figure 1 or Figure 2 The process of the intelligent driving domain controller in the method is described as follows: Step 201: Receive image data from multiple vehicle-mounted cameras.

[0039] In the embodiment of the present application, multiple on-board cameras are configured around the vehicle. For example, the multiple on-board cameras include a forward-facing camera, a rear-facing camera, a left-side camera, and a right-side camera, etc. This application does not impose any particular restrictions on this. The image data collected by each of the multiple on-board cameras is sent to the intelligent driving domain controller.

[0040] It is worth noting that the intelligent driving domain controller uses image data from multiple on-board cameras to complete the task of identifying objects in the surrounding environment, including but not limited to: identifying parking space boundaries, pedestrians, ground locks, vehicles, etc. in the parking function, and identifying lane lines, traffic participants, traffic lights, etc. during intelligent driving on the road.

[0041] Step 202: Obtain the actual driving distance of the vehicle.

[0042] In embodiments of the present application, the intelligent driving domain controller can obtain the actual distance traveled during vehicle operation. For example, the intelligent driving domain controller can obtain the vehicle's rotational speed through a wheel speed sensor and then, combined with the wheel's circumference information, calculate the vehicle's distance traveled. For example, if the wheel's circumference is C and the number of wheel rotations in a given period is n, then the distance traveled s = C × n.

[0043] Step 203: In response to the actual driving distance reaching a positive integer multiple of the set interval distance, image data at the actual driving distance is sent to the data acquisition device.

[0044] In the embodiments of this application, as the vehicle continues to travel, the actual distance traveled by the vehicle gradually increases. Whenever the actual distance traveled reaches a positive integer multiple of a set interval distance, the intelligent driving domain controller transmits image data at that location to the data acquisition device. It should be understood that the set interval distance can be set based on actual needs and is not specifically limited in this application.

[0045] For example, in order to collect image data in a parking scenario, the interval distance can be set to 0.5m. Then, when the actual driving distance reaches 0.5m, 1m, 1.5m, 2m, 2.5m, 3m... and so on, the image data collected by multiple on-board cameras at the above positions can be sent to the data acquisition device, while the image data collected at positions other than the above positions does not need to be sent to the data acquisition device. For example, after the intelligent driving domain controller sends the image data at 0.5m to the data acquisition device, since the position of the vehicle when it is in the (0.5m, 1m) interval has little change from the position when the vehicle is at 0.5m, it can be considered that the image data collected when the vehicle is in the (0.5m, 1m) interval is relatively similar to the image data collected when the vehicle is at 0.5m, so there is no need to send the image data collected when the vehicle is in the (0.5m, 1m) interval to the data acquisition device.

[0046] In the above embodiment, image data at different positions at a certain interval are sent to the data acquisition device, which reduces the amount of image data transmitted between the intelligent driving domain controller and the image acquisition device. In the case of limited bandwidth, there is no need to compress the transmitted image data, thereby ensuring the quality of the transmitted image data and improving the storage space utilization of the data acquisition device.

[0047] See Figure 4 , which is a flow chart of a method for an intelligent driving domain controller to send image data to a data acquisition device according to an embodiment of the present application. Step 203 can be implemented by executing sub-steps 2031 and 2032: Step 2031: Determine the actual driving time each time the actual driving distance reaches a positive integer multiple of the set interval distance.

[0048] In an embodiment of the present application, the intelligent driving domain controller can determine in real time the actual driving time corresponding to each time the actual driving distance of the vehicle reaches a positive integer multiple of the set interval distance. As a possible implementation method, the intelligent driving domain controller can determine the actual driving time corresponding to each time the actual driving distance reaches a positive integer multiple of the set interval distance by using a wheel speed mileage calculation method. The specific calculation method is shown in formula (1): (1) Where s is the actual driving distance, w is the wheel angular velocity, r is the wheel radius, t1 is the time when the previous image data is transmitted, and t2 is the time when the next image data is transmitted to be solved.

[0049] Step 2032: Send image data at the actual driving time to the data acquisition device.

[0050] In an embodiment of the present application, the image data corresponding to the actual driving time is sent to the data acquisition device, that is, the intelligent driving domain controller sends the image data collected by multiple vehicle-mounted cameras to the data acquisition device at regular intervals, thereby reducing the amount of image transmission data between the intelligent driving domain controller and the image acquisition device while ensuring the availability of the transmitted image data. In the case of limited bandwidth, there is no need to compress the transmitted image data, thereby ensuring the quality of the transmitted image data and improving the storage space utilization of the data acquisition device.

[0051] Taking the set interval distance as 0.5m and the actual driving distance reaching 1m as an example, when the actual driving distance reaches 1m, it is exactly twice the set interval distance. The corresponding actual driving time t here is 1.2s. Then the multiple image data collected by the multiple vehicle-mounted cameras at 1.2s are sent to the data acquisition device.

[0052] See Figure 5 , which is a flow chart of another method for an intelligent driving domain controller to send image data to a data acquisition device according to an embodiment of the present application. Step 2032 can be implemented by executing sub-steps 301 to 302: Step 301: assigning time stamps to image data from multiple vehicle-mounted cameras respectively.

[0053] In an embodiment of the present application, the intelligent driving domain controller can use multiple threads to assign timestamps to image data from multiple on-board cameras. It is worth noting that the timestamps here can be derived from the intelligent driving domain controller's hardware time (e.g., crystal oscillator time) or software time (e.g., time obtained via the network), and this application does not impose any specific restrictions on this.

[0054] Step 302: Send image data with a timestamp close to the actual driving time to the data acquisition device.

[0055] In an embodiment of the present application, the image data collected by each vehicle-mounted camera, whose timestamp is close to the actual driving time, is packaged and sent to the data acquisition device, thereby ensuring the synchronization of the image data sent to the data acquisition device.

[0056] It is worth noting that after receiving the above image data, the data acquisition device will uniformly encapsulate the synchronized image data from multiple vehicle-mounted cameras. These synchronized image data can subsequently be used as training samples for training the automatic parking model.

[0057] See Figure 6Based on the same inventive concept, an embodiment of the present application further provides a data acquisition device, which is applied to an intelligent driving domain controller. The intelligent driving domain controller is communicatively connected to a data acquisition device. The device includes: The data receiving unit 401 is used to receive image data from multiple vehicle-mounted cameras; The distance obtaining unit 402 is used to obtain the actual travel distance of the vehicle; The data sending unit 403 is configured to send image data at the actual driving distance to the data acquisition device in response to the actual driving distance reaching a positive integer multiple of the set interval distance.

[0058] Optionally, the data sending unit 403 includes: a driving time determination unit, for determining the actual driving time when the actual driving distance reaches a positive integer multiple of the set interval distance; The image data sending unit is used to send the image data at the actual driving time to the data acquisition device.

[0059] Optionally, the travel time determination unit is specifically configured to: The actual driving time when the actual driving distance reaches a positive integer multiple of the set interval distance is determined according to the wheel speed mileage calculation method.

[0060] Optionally, the image data sending unit includes: A timestamp assigning subunit, used to assign timestamps to image data from multiple vehicle-mounted cameras respectively; The image data sending subunit is used to send image data with a timestamp close to the actual driving time to the data acquisition device.

[0061] Optionally, the timestamp assignment subunit is specifically used for: The image data from multiple vehicle-mounted cameras are given timestamps according to the hardware time.

[0062] Optionally, the intelligent driving domain controller is connected to the data acquisition device through an on-board diagnostic system interface.

[0063] Optionally, the intelligent driving domain controller and the data acquisition device run the same operating system.

[0064] The device provided in the above embodiment can be, for example, a chip or a chip module. The device provided in the above embodiment is used to implement the technical solution of the above method embodiment. Its implementation principle and technical effects can be further referred to the relevant description in the method embodiment, which will not be repeated here.

[0065] Regarding the various modules / units contained in the various devices described in the above embodiments, they can be software modules / units, hardware modules / units, or part of them can be software modules / units and part of them can be hardware modules / units. For example, for various devices applied to or integrated in a chip, the various modules / units contained therein can all be implemented in the form of hardware such as circuits, or at least part of the modules / units can be implemented in the form of software programs, which run on the processor integrated inside the chip, and the remaining modules / units can be implemented in the form of hardware such as circuits; for various devices applied to or integrated in a chip module, the various modules / units contained therein can all be implemented in the form of hardware such as circuits, and different modules / units can be located in the same component of the chip module (such as a chip, circuit module, etc.) or in different components, or at least part of the modules / units can be implemented in the form of software programs. The software program runs on the processor integrated in the chip module, and the remaining modules / units can be implemented in hardware such as circuits; for each device applied to or integrated in the electronic terminal equipment, the various modules / units contained therein can be implemented in hardware such as circuits, and different modules / units can be located in the same component (for example, chip, circuit module, etc.) or different components in the electronic terminal equipment, or at least some modules / units can be implemented in software program, which runs on the processor integrated in the electronic terminal equipment, and the remaining (if any) modules / units can be implemented in hardware such as circuits.

[0066] See Figure 7 , is an electronic device provided in an embodiment of the present application, the electronic device includes at least one processor 501, the processor 501 is used to execute a computer program stored in a memory, and implement the embodiment of the present application as provided in the following Figure 1-5 Schematic flow chart of the data acquisition method steps shown.

[0067] Optionally, the processor 501 may specifically be a central processing unit, a specific ASIC, or one or more integrated circuits for controlling program execution.

[0068] Optionally, the electronic device may further include a memory 502 connected to the at least one processor 501. The memory 502 may include ROM, RAM, and disk storage. The memory 502 is used to store data required by the processor 501 when it is running, that is, it stores instructions that can be executed by the at least one processor 501. The at least one processor 501 executes the instructions stored in the memory 502 to execute the following operations: Figure 1-5 The method shown in FIG. 1 . The number of the memory 502 is one or more. The number of the memory 502 is one or more.

[0069] The embodiment of the present application further provides a computer storage medium, wherein the computer storage medium stores a computer program, and when the computer program is run on a processor, the processor executes the following Figure 1-5 method.

[0070] The computer-readable storage medium may be any combination of one or more computer-readable media. The computer-readable medium may be a computer-readable signal medium or a computer-readable storage medium. The computer-readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples (a non-exhaustive list) of computer-readable storage media include: an electrical connection having one or more conductors, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM) or flash memory, optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof. In this document, a computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, apparatus, or device.

[0071] A computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, which carries computer-readable program code. Such a propagated data signal may take a variety of forms, including, but not limited to, electromagnetic signals, optical signals, or any suitable combination thereof. A computer-readable signal medium may also be any computer-readable medium other than a computer-readable storage medium that can transmit, propagate, or transport a program for use by or in conjunction with an instruction execution system, apparatus, or device.

[0072] Program code embodied on a computer-readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, radio frequency (RF), etc., or any suitable combination of the foregoing.

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

[0074] The foregoing description of this specification describes specific embodiments. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims can be performed in an order different from that described in the embodiments and still achieve the desired results. Furthermore, the processes depicted in the accompanying drawings do not necessarily require the specific order shown or the sequential order to achieve the desired results. In certain embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0075] In the several embodiments provided in this specification, it should be understood that the disclosed systems, devices, and methods can be implemented in other ways. For example, the device embodiments described above are merely illustrative. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed may be through some interface, indirect coupling or communication connection of devices or units, which may be electrical, mechanical or other forms.

[0076] In addition, the functional units in the various embodiments of this specification may be integrated into a single processing unit, each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or hardware plus software functional units.

[0077] The above description is only a preferred embodiment of this specification and is not intended to limit this specification. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of this specification should be included in the scope of protection of this specification.

Claims

1. A data collection method, characterized in that: Applied to an intelligent driving domain controller, the intelligent driving domain controller is communicatively connected to a data acquisition device, and the method includes: Receive image data from multiple vehicle-mounted cameras; Determine the actual distance traveled by the vehicle; In response to each time the actual driving distance reaches a positive integer multiple of a set interval distance, image data at the actual driving distance is sent to the data acquisition device.

2. The method according to claim 1, characterized in that In response to the actual driving distance reaching a positive integer multiple of the set interval distance each time, sending image data at the actual driving distance to the data acquisition device, including: determining the actual driving time when the actual driving distance reaches a positive integer multiple of the set interval distance; The image data at the actual driving time is sent to the data acquisition device.

3. The method according to claim 2, characterized in that Determining the actual driving time when the actual driving distance reaches a positive integer multiple of the set interval distance includes: The actual driving time when the actual driving distance reaches a positive integer multiple of the set interval distance is determined according to the wheel speed mileage calculation method.

4. The method according to claim 2, characterized in that Sending image data at the actual driving time to the data acquisition device includes: Assigning time stamps to the image data from the multiple vehicle-mounted cameras respectively; The image data having the timestamp close to the actual driving time is sent to the data acquisition device.

5. The method according to claim 4, characterized in that Assigning timestamps to the image data from the multiple vehicle-mounted cameras respectively, including: The image data from the multiple vehicle-mounted cameras are respectively given time stamps according to the hardware time.

6. The method according to any one of claims 1 to 5, characterized in that The intelligent driving domain controller is communicatively connected to the data acquisition device via an on-board diagnostic system interface.

7. The method according to any one of claims 1 to 5, characterized in that The intelligent driving domain controller and the data acquisition device run the same operating system.

8. A data acquisition device, characterized in that: Applied to an intelligent driving domain controller, the intelligent driving domain controller is communicatively connected to a data acquisition device, and the method includes: A data receiving unit, used for receiving image data from multiple vehicle-mounted cameras; a distance determination unit, for determining an actual travel distance of the vehicle; The data sending unit is used to send image data at the actual driving distance to the data acquisition device in response to the actual driving distance reaching a positive integer multiple of the set interval distance.

9. An electronic device, characterized in that: comprising a memory and a processor, wherein: The memory is used to store computer programs; The processor is configured to execute the computer program to implement the method according to any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that Used to store a computer program, wherein when the computer program is executed by a processor, the method according to any one of claims 1 to 7 is implemented.

Images