Collecting and playing system for intelligent driving data

Abstract

The invention relates to an intelligent driving data collecting and playing system, and relates to the technical field of intelligent driving. The system comprises an intelligent driving data collecting and playing tool deployed based on a containerized platform and a domain controller, wherein the tool comprises a Web access module, a back-end processing module and a storage module; wherein the Web access module is used for sending a domain controller configuration file storage path and a domain controller control instruction to the back-end processing module; the back-end processing module is used for searching the configuration file and modifying a packet recording state value in the configuration file; the domain controller is used for starting to collect the intelligent driving data when the packet recording state value is the first state value and stopping collecting the intelligent driving data when the packet recording state value is the second state value; the back-end processing module is also used for sending the intelligent driving data to the Web access module; the Web access module is also used for playing the intelligent driving data; and the storage module is used for storing the intelligent driving data. According to the invention, the data acquisition and management efficiency can be improved.

Description

Technical Field

[0001] The present application relates to the field of intelligent driving technology, and in particular to a system for collecting and playing intelligent driving data. Background Art

[0002] At present, in the process of intelligent driving algorithm development and testing, it is usually necessary to collect, store, classify and replay multi-source data (such as images, lidar point clouds, CAN bus data, etc.) to support algorithm debugging and verification.

[0003] However, in the process of intelligent driving data collection and playback, there are problems such as complex multi-tool operation, decentralized data storage and lack of real-time performance, which makes it difficult to achieve efficient management, synchronous processing and convenient use of multi-source data. Summary of the invention

[0004] Based on this, it is necessary to provide a smart driving data collection and playback system for the above technical problems. The system includes a smart driving data collection and playback tool and a domain controller deployed on a containerized platform. The smart driving data collection and playback tool includes a Web access module, a backend processing module and a storage module; wherein,

[0005] The Web access module is used to send a domain controller configuration file storage path and a domain controller control instruction to the back-end processing module;

[0006] The back-end processing module is used to search for a configuration file in the domain controller according to the storage path of the domain controller configuration file, and to modify a packet recording status value in the configuration file according to a control instruction of the domain controller;

[0007] The domain controller is used to start collecting intelligent driving data when the packet recording state value is a preset first state value, and stop collecting the intelligent driving data when the packet recording state value is a preset second state value;

[0008] The backend processing module is further used to send the intelligent driving data to the Web access module;

[0009] The Web access module is also used to receive and play the intelligent driving data;

[0010] The storage module is used to store the intelligent driving data.

[0011] As an optional implementation, the Web access module is further used to receive domain controller configuration parameters input by a user, and send the domain controller configuration parameters to the backend processing module;

[0012] The backend processing module is further used to connect to the domain controller according to the domain controller configuration parameters.

[0013] As an optional implementation, the domain controller configuration parameters include a domain controller IP address, an operating system account, and a password.

[0014] As an optional implementation, the back-end processing module is also used to modify the packet recording status value to the first status value when the domain controller control instruction is a start packet recording instruction, and to modify the packet recording status value to the second status value when the domain controller control instruction is a stop packet recording instruction.

[0015] As an optional implementation, the back-end processing module is also used to obtain the packet recording path of the intelligent driving data and mount the packet recording path to the containerized platform.

[0016] As an optional implementation manner, the Web access module is further configured to send a disconnection instruction to the backend processing module;

[0017] The back-end processing module is also used to uninstall the packet recording path of the intelligent driving data and disconnect the connection with the domain controller after receiving the disconnection instruction.

[0018] As an optional implementation, the Web access module is further used to classify the intelligent driving data according to a preset classification rule, and save the intelligent driving data to a play queue in a timestamp order.

[0019] As an optional implementation manner, the Web access module is further used to send the data information of the intelligent driving data and the data saving instruction input by the user to the back-end processing module;

[0020] The back-end processing module is also used to store the intelligent driving data and the data information in the storage module.

[0021] As an optional implementation, the storage module includes a relational database and an object storage system; wherein,

[0022] The relational database is used to store data information of the intelligent driving data, wherein the data information includes the collection time, data label and data file name of the intelligent driving data;

[0023] The object storage system is used to store the intelligent driving data.

[0024] As an optional implementation, the Web access module includes a reverse proxy server and a Web static program.

[0025] The present application provides a system for collecting and playing intelligent driving data, the system comprising an intelligent driving data collection and playback tool and a domain controller deployed on a containerized platform, the intelligent driving data collection and playback tool comprising a Web access module, a backend processing module and a storage module; wherein the Web access module is used to send a domain controller configuration file storage path and a domain controller control instruction to the backend processing module; the backend processing module is used to search for a configuration file in the domain controller according to the domain controller configuration file storage path, and modify the recording package status value in the configuration file according to the domain controller control instruction; the domain controller is used to start collecting intelligent driving data when the recording package status value is a preset first status value, and stop collecting the intelligent driving data when the recording package status value is a preset second status value; the backend processing module is also used to send the intelligent driving data to the Web access module; the Web access module is also used to receive and play the intelligent driving data; the storage module is used to store the intelligent driving data. This system not only improves the efficiency of data collection and management, but also provides convenient tool support for the development and testing of intelligent driving algorithms.

[0026] It should be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0027] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0028] Figure 1 A schematic diagram of the structure of a system for collecting and playing intelligent driving data provided in an embodiment of the present application. DETAILED DESCRIPTION

[0029] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0030] The following will describe in detail a system for collecting and playing intelligent driving data provided by an embodiment of the present application in conjunction with a specific implementation method. Figure 1 A schematic diagram of the structure of a system for collecting and playing intelligent driving data provided in an embodiment of the present application is shown in FIG. Figure 1As shown, the system includes an intelligent driving data acquisition and playback tool 1 and a domain controller 2 deployed on a containerized platform. The intelligent driving data acquisition and playback tool 1 includes a Web access module 11, a backend processing module 12 and a storage module 13; wherein,

[0031] The Web access module 11 is used to send the domain controller configuration file storage path and the domain controller control instruction to the back-end processing module 12;

[0032] The back-end processing module 12 is used to search the configuration file in the domain controller 2 according to the storage path of the domain controller configuration file, and modify the packet recording state value in the configuration file according to the control instruction of the domain controller;

[0033] Domain controller 2, used for starting to collect intelligent driving data when the packet recording state value is a preset first state value, and stopping collecting intelligent driving data when the packet recording state value is a preset second state value;

[0034] The backend processing module 12 is also used to send the intelligent driving data to the Web access module 11;

[0035] The web access module 11 is also used to receive and play the intelligent driving data;

[0036] The storage module 13 is used to store intelligent driving data.

[0037] In implementation, the containerization platform can provide environmental isolation and easy deployment capabilities. Through containerization platforms such as Docker, the intelligent driving data collection and playback tool 1 is deployed in a modular manner. The domain controller 2 is responsible for the collection of intelligent driving data. For example: the collection and playback tool is deployed using Docker containers, and the images of modules including Nginx reverse proxy server, Web static program, Java backend program, MySQL relational database, Redis cache database and MinIO object storage system are run in the container. The domain controller 2 is a computing device installed with a specific collection program, which is used to collect intelligent driving data obtained by vehicle-mounted sensors. The Web access module 11 receives user input information through the front-end interface, such as the configuration file path and the start / stop recording package instruction, and transmits it to the back-end processing module 12 through the HTTP or WebSocket protocol. For example: users, such as intelligent driving algorithm developers, can enter the domain controller configuration file storage path (such as / etc / recording / config.json) in the interactive interface of the Web access module 11. After the user clicks the "Start Recording Package" button in the interactive interface, the Web access module 11 sends an HTTP request to start recording the package to the back end. The back-end processing module 12, such as a Java back-end program, can connect to the domain controller 2 through the SSH protocol, search for the configuration file specified by the user, and modify the recording status value (such as status) used for the recording status mark. For example: the back-end processing module 12 can connect to the IP address 192.168.1.100 of the domain controller 2 through SSH, and then access the configuration file in the configuration file path / etc / recording / config.json. The back-end processing module 12 can modify the value of the recording status value status to a preset first status value, such as "start", indicating that the domain controller 2 starts recording packets. The recording program in the domain controller 2 can periodically read the recording status value in the configuration file, and decide to start or stop the data collection task according to the recording status value. For example: the recording program can detect the status field in / etc / recording / config.json every second, call the camera, radar and other sensors to start data collection when the recording status value is "start", and close the collection thread when the recording status value is "stop". The back-end processing module 12 can access the recording file in the domain controller through the mounting mechanism, and pass the data to the Web access module 11 through the WebSocket protocol for display or storage. The web access module 11 can display the intelligent driving data in the order of timestamps through the player component of the front-end page. For example, after the web access module 11 receives the intelligent driving data such as CAN data, image frames and point cloud data, it can play them synchronously according to the time axis through the front-end JavaScript program.

[0038] As an optional implementation, the Web access module 11 is further used to receive the domain controller configuration parameters input by the user, and send the domain controller configuration parameters to the backend processing module 12;

[0039] The backend processing module 12 is also used to connect to the domain controller 2 according to the domain controller configuration parameters.

[0040] In implementation, the Web access module 11 can transmit the IP address, account number, password and other information entered by the user to the backend processing module 12 via HTTP, and the backend processing module 12 uses this information to establish a connection with the domain controller 2. For example: the user can enter the domain controller 2's IP 192.168.1.100, account number admin, password password123 and other domain controller configuration parameters in the interactive interface, and the Web access module 11 sends the domain controller configuration parameters to the backend processing module 12. The backend processing module 12 uses the SSH protocol to establish a connection with the domain controller 2 via the IP address, account number and password. For example: the backend processing module 12 connects to the domain controller 2 via the SSH command, and accesses the configuration file after successfully verifying the account number and password. If the connection fails (such as an IP error, the account number and password do not match), an error prompt message is returned to the Web access module 11.

[0041] As an optional implementation, the domain controller configuration parameters include the domain controller IP address, operating system account and password.

[0042] As an optional implementation, the back-end processing module 12 is also used to modify the packet recording status value to a first status value when the domain controller control instruction is a start packet recording instruction, and to modify the packet recording status value to a second status value when the domain controller control instruction is a stop packet recording instruction.

[0043] In implementation, the back-end processing module 12 receives a control instruction from the domain controller (such as an instruction to start or stop packet recording) and dynamically modifies the packet recording status value in the domain controller configuration file based on the instruction. The field in the configuration file used to mark the packet recording status (such as status) will be set to a "first status value" (such as start) or a "second status value" (such as stop). The packet recording program in the domain controller 2 periodically reads the packet recording status value of the configuration file and controls the start or stop of the packet recording operation according to the packet recording status value. This mechanism achieves remote control of the acquisition operation of the domain controller 2 through a simple configuration file status change. For example: the back-end processing module 12 receives a "start packet recording" instruction sent by the user through the Web access module 11. The back-end processing module 12 can connect to the domain controller 2 via the SSH protocol and locate the configuration file path (such as / etc / recording / config.json). The back-end processing module 12 modifies the value of the field status in the configuration file from stop to start. When the packet recording program on domain controller 2 finds that status = start during the next periodic check, it immediately starts the collection tasks of sensors such as cameras, radars, and GPS, and stores the data in the specified path (such as / mnt / data / recording). Another example: the back-end processing module 12 receives a "stop packet recording" instruction sent by the user. The back-end processing module 12 locates the same configuration file path through the same SSH connection mechanism. Modify the value of the field status from start to stop. After the packet recording program of domain controller 2 detects that the packet recording status value has been changed to stop, it immediately terminates the current collection task and writes the data in the cache to the packet recording file to ensure data integrity. The start and stop process of packet recording does not require direct intervention in domain controller 2, and can be completed by modifying the configuration file, which improves the flexibility and automation of the operation.

[0044] As an optional implementation, the backend processing module 12 is also used to obtain the packet recording path of the intelligent driving data and mount the packet recording path to the containerized platform.

[0045] In implementation, the backend processing module 12 can access the recording file in the domain controller 2 through the mounting mechanism, and can pass the data to the Web access module 11 through the WebSocket protocol for display or storage. For example: the backend processing module 12 mounts the domain control path / mnt / recording / XXXX-XX-XX to the / data / recording directory inside the Docker container, and accesses the intelligent driving data of the recording file through the mirroring method.

[0046] As an optional implementation, the Web access module 11 is further configured to send a disconnection instruction to the backend processing module 12;

[0047] The back-end processing module 12 is also used to uninstall the packet recording path of the intelligent driving data and disconnect the connection with the domain controller 2 after receiving the disconnection instruction.

[0048] In implementation, the Web access module 11 may send a disconnection instruction, and the backend processing module 12, such as a Java program, will uninstall the recorded package file path and disconnect the SSH connection with the domain controller 2 after receiving the disconnection instruction.

[0049] As an optional implementation, the Web access module 11 is also used to classify the intelligent driving data according to a preset classification rule, and save the intelligent driving data to a play queue in the order of timestamps.

[0050] In implementation, the web access module 11 can classify the intelligent driving data by parsing the data type field (such as image, radar, CAN data), and store them in the play queue in order of timestamp. For example, the web access module 11 stores the image frame with the timestamp of XXXX-XX-XX00:00:01 in the image play queue, and stores the radar data in another play queue.

[0051] As an optional implementation, the Web access module 11 is also used to send the data information of the intelligent driving data and the data saving instruction input by the user to the back-end processing module 12;

[0052] The back-end processing module 12 is also used to store the intelligent driving data and data information in the storage module 13 .

[0053] In implementation, the Web access module 11 is responsible for interacting with the user. When the user completes the data recording task, the recorded data file can be managed through the Web interface, including operations such as adding descriptive tags and saving instructions. The Web access module 11 encapsulates the information entered by the user into a data saving instruction (including data file name, tag, time and other information), and sends it to the back-end processing module 12 through HTTP or WebSocket protocol. After receiving the instruction, the back-end processing module 12 stores the intelligent driving data and its related data information in the storage module 13. The storage module 13 usually includes a relational database and an object storage system, which are used to store data information (such as timestamps, tags) and original data files (such as sensor data) respectively. For example: the user selects a section of recorded intelligent driving data (such as record_XXXXXXXX.json) through the interactive interface of the Web access module 11. The user can enter the label (such as "rainy road test data") and description (such as "used to evaluate the impact of rainy driving on vehicle radar") of the intelligent driving data on the interactive interface. The user can click the "Save Data" button. The Web access module 11 can encapsulate the instruction to save data (including the data file name record_XXXXXXXX.json, the label "rainy road test data", and the description "used to evaluate the impact of rainy driving on vehicle radar") into JSON format and send it to the back-end processing module 12 via HTTP or WebSocket. After receiving the save instruction, the back-end processing module 12 parses the file name, label, description and other information, and accesses the intelligent driving data file recorded by the domain controller 2 through the obtained file path (such as / mnt / data / recording / record_XXXXXXXX.json). The back-end processing module 12 can upload the file to the object storage system in the storage module 13 and generate a unique storage path, such as minio: / / driving-data / XXXXXXXX / record_XXXXXXXX.json). The back-end processing module 12 can also store the file storage path, acquisition time, user-entered labels and descriptions and other information in the relational database to complete the storage operation. Subsequent users can query the stored intelligent driving data through the Web access module 11, search by label or time range, and play back the collected content according to the data file name. Through this implementation method, users can easily manage intelligent driving data, ensure clear data organization and storage, and provide flexible support for subsequent data analysis and use.

[0054] As an optional implementation, the storage module 13 includes a relational database 131 and an object storage system 132; wherein,

[0055] A relational database 131 is used to store data information of the intelligent driving data, where the data information includes the collection time, data label and data file name of the intelligent driving data;

[0056] The object storage system 132 is used to store intelligent driving data.

[0057] In implementation, relational databases can be used to store structured metadata information, and object storage systems can be used to save unstructured large files. Developers can tag the intelligent driving data in the Web access module 11 and issue file saving instructions. The back-end processing module 12, such as the Java program, uploads the recorded package file to the MinIO object storage system after receiving the instruction, and records the time, label and file name of the data collection in the MySQL relational database for subsequent retrieval and playback. For example: the intelligent driving data with the file name test_case_a.log can be recorded in the MySQL relational database, and the collection time can be recorded as XXXX-XX-XX. The intelligent driving data in the file is saved in the MinIO object storage system.

[0058] As an optional implementation, the Web access module 11 includes a reverse proxy server 111 and a Web static program 112 .

[0059] In implementation, the function of the Web access module 11 is to provide a communication bridge between the user interface and the back-end module. In order to achieve efficient access and secure data transmission, the Web access module is usually composed of a reverse proxy server 111 and a Web static program 112: the reverse proxy server 111, such as Nginx, is used to process requests from users and forward them to the back-end processing module 12. The reverse proxy server 111 can improve system performance (through load balancing and caching), enhance security (hide the real address of the back-end) and provide a unified interface entry (through SSL encryption or domain name resolution). The Web static program 112 is a front-end application for hosting and providing a user access interface, including HTML, CSS, JavaScript files, etc. These static resources are responsible for rendering the user interface, supporting users to input parameters, send instructions and display collected data. The Web static program 112 is usually deployed behind the reverse proxy server 111 through a CDN or storage server to provide a fast response.

[0060] As an optional implementation, the storage module 13 also includes a cache database 133 .

[0061] In implementation, the cache database 133, such as the Redis cache database, stores the smart driving data in memory to achieve fast access. The Web access module can establish a connection with Redis. The back-end processing module 12 can push the smart driving data to the Web access module 11 in real time via WebSocket, and the Web access module can obtain cache data from Redis. The smart driving data is read from the Redis cache database 133 to the front end of the Web access module 11 for display.

[0062] The embodiment of the present application provides a system for collecting and playing intelligent driving data. The system includes an intelligent driving data collection and playback tool and a domain controller deployed on a containerized platform. The intelligent driving data collection and playback tool includes a Web access module, a back-end processing module, and a storage module. Among them, the Web access module is used to send the domain controller configuration file storage path and the domain controller control instruction to the back-end processing module. The back-end processing module is used to search for the configuration file in the domain controller according to the domain controller configuration file storage path, and modify the recording package status value in the configuration file according to the domain controller control instruction. The domain controller is used to start collecting intelligent driving data when the recording package status value is a preset first status value, and stop collecting intelligent driving data when the recording package status value is a preset second status value. The back-end processing module is also used to send the intelligent driving data to the Web access module. The Web access module is also used to receive and play the intelligent driving data. The storage module is used to store the intelligent driving data. The embodiment of the present application provides an efficient and integrated intelligent driving data collection and playback solution through the design of an intelligent driving data collection and playback tool based on a containerized platform. The tool is deployed using a containerized platform, which simplifies the installation and update process of the tool, and improves the efficiency and operability of version control through Docker tag management. Combined with the interactive interface of the Web access module, the user can flexibly configure the domain controller 2 and conveniently operate the tool, lowering the threshold for using the tool. Through the communication between the back-end processing module and the domain controller, the recording status is controlled in real time, and the recording data is efficiently accessed through the mounting mechanism, which improves the reliability and real-time performance of data acquisition. Through the playback queue sorted by classification rules and timestamps, accurate alignment and visual playback of multi-source data can be achieved, meeting the needs of intelligent driving algorithm developers for data analysis and verification. In addition, the introduction of the storage module effectively solves the problem of scattered data storage and difficult retrieval, and uses the combination of object storage and relational databases to ensure the security and scalability of data storage, while supporting quick search and playback of recording files by tags. The embodiment of the present application not only improves the efficiency of data collection and management, but also provides convenient tool support for the development and testing of intelligent driving algorithms.

[0063] It can be understood that the same / similar parts between the various embodiments of the above method in this specification can refer to each other, and each embodiment focuses on the differences from other embodiments. For related points, please refer to the description of other method embodiments.

[0064] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to memory, storage, database or other media used in the embodiments provided in this application can include non-volatile and / or volatile memory. Non-volatile memory can include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM) or flash memory. Volatile memory can include random access memory (RAM) or external cache memory. As an illustration and not limitation, RAM is available in many forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link (Synchlink) DRAM (SLDRAM), memory bus (Rambus) direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).

[0065] It should be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the existence of other identical elements in the process, method, article or device including the elements.

[0066] It should also be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for display, data for analysis, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties.

[0067] Each embodiment in this specification is described in a related manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the system embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.

[0068] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0069] The above-mentioned embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the invention patent. It should be pointed out that, for a person of ordinary skill in the art, several variations and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the patent of the present application shall be subject to the attached claims.

Claims

1. A system for collecting and playing intelligent driving data, characterized in that: The system includes an intelligent driving data collection and playback tool and a domain controller deployed on a containerized platform, wherein the intelligent driving data collection and playback tool includes a Web access module, a backend processing module and a storage module; wherein, The Web access module is used to send a domain controller configuration file storage path and a domain controller control instruction to the back-end processing module; The back-end processing module is used to search for a configuration file in the domain controller according to the storage path of the domain controller configuration file, and to modify a packet recording status value in the configuration file according to a control instruction of the domain controller; The domain controller is used to start collecting intelligent driving data when the packet recording state value is a preset first state value, and stop collecting the intelligent driving data when the packet recording state value is a preset second state value; The backend processing module is further used to send the intelligent driving data to the Web access module; The Web access module is also used to receive and play the intelligent driving data; The storage module is used to store the intelligent driving data.

2. The system according to claim 1, characterized in that The Web access module is further used to receive domain controller configuration parameters input by a user and send the domain controller configuration parameters to the backend processing module; The backend processing module is further used to connect to the domain controller according to the domain controller configuration parameters.

3. The system according to claim 2, characterized in that The domain controller configuration parameters include the domain controller IP address, operating system account and password.

4. The system according to claim 1, characterized in that The back-end processing module is also used to modify the packet recording status value to the first status value when the domain controller control instruction is a packet recording start instruction, and to modify the packet recording status value to the second status value when the domain controller control instruction is a packet recording stop instruction.

5. The system according to claim 1, characterized in that The back-end processing module is also used to obtain the packet recording path of the intelligent driving data and mount the packet recording path to the containerized platform.

6. The system according to claim 5, characterized in that The Web access module is further used to send a disconnection instruction to the back-end processing module; The back-end processing module is also used to uninstall the packet recording path of the intelligent driving data and disconnect the connection with the domain controller after receiving the disconnection instruction.

7. The system according to claim 1, characterized in that The Web access module is further used to classify the intelligent driving data according to a preset classification rule, and save the intelligent driving data to a play queue in a timestamp order.

8. The system according to claim 1, characterized in that The Web access module is further used to send the data information of the intelligent driving data and the data saving instruction input by the user to the back-end processing module; The back-end processing module is also used to store the intelligent driving data and the data information in the storage module.

9. The system according to claim 8, characterized in that The storage module includes a relational database and an object storage system; wherein, The relational database is used to store data information of the intelligent driving data, wherein the data information includes the collection time, data label and data file name of the intelligent driving data; The object storage system is used to store the intelligent driving data.

10. The system according to claim 1, characterized in that The Web access module includes a reverse proxy server and a Web static program.

Images