A log data transmission method and system, a computer device and a medium

Abstract

The application provides a log data transmission method and system, a computer device and a medium, comprising: acquiring the PID and VID of the data transmission interface of the mobile terminal device, matching the drive file of the mobile terminal device based on the PID and VID, identifying the connection state of the data transmission interface of the mobile terminal device and the data transmission interface of the vehicle-mounted terminal device, and when the connection state is a hot plug state, dynamically allocating the network sharing address of the mobile terminal device based on the drive file, so that the vehicle-mounted terminal device transmits the target log data to the server according to the network sharing address. Through the establishment of the network communication connection between the vehicle-mounted terminal device and the mobile terminal device, in the scene without other networks, the vehicle-mounted terminal device can share the network of the mobile terminal device, so that the vehicle machine operating system can perform network sharing with the mobile terminal device through the corresponding data transmission interface, thereby transmitting the target log data to the server, realizing data exchange transmission and internet access.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of data transmission, and particularly relates to a log data transmission method and system, a computer device and a medium. BACKGROUND

[0002] A vehicle history report (VHR) contains controller area network (CAN) message data and controller system logs of the whole vehicle. After uploading the VHR to a server and performing big data analysis, not only can the vehicle health status be monitored and the functional defects of the software layer be optimized, but also the development of the vehicle can be better. However, at present, the VHR has not been reasonably utilized on most vehicle models, and only on vehicles equipped with an Ethernet module or a wireless network function module, the uploading function of the VHR related logs is available, but the network hardware cost of the related vehicles is still at a high stage. Therefore, the vehicle health parameters of most vehicle models are not fully utilized. SUMMARY

[0003] In view of the above-mentioned defects of the prior art, the present application aims to provide a log data transmission method and system, a computer device and a medium, which can solve the technical problems existing in the prior art.

[0004] To achieve the above-mentioned purpose and other related purposes, the present application provides a log data transmission method, comprising the following steps:

[0005] obtaining a product identification code and a supplier identification code of a data transmission interface of a mobile terminal device;

[0006] performing operating system kernel compilation configuration on the mobile terminal device based on the product identification code and the supplier identification code, and matching a driver file of the mobile terminal device based on an operating system kernel compilation configuration result, wherein the operating system kernel compilation configuration result comprises a network sharing configuration of the mobile terminal device;

[0007] identifying a connection state of the data transmission interface of the mobile terminal device and a data transmission interface of a vehicle terminal device, and when the connection state is a hot plug state, dynamically allocating a network sharing address of the mobile terminal device based on the driver file, so that the vehicle terminal device transmits target log data to a server according to the network sharing address; wherein the target log data comprises vehicle history report log data.

[0008] In an embodiment of the present application, the process of dynamically allocating the network sharing address of the mobile terminal device based on the driver file further comprises:

[0009] cross-compile the dependencies of the car machine operating system in sequence by using a cross-compile tool to generate an executable program for the architecture of the car machine operating system, denoted as a first executable program; wherein the vehicle terminal device is configured with the car machine operating system;

[0010] embed the first executable program into the car machine operating system, and dynamically allocate a network sharing address of the mobile terminal device based on the drive file of the mobile terminal device and the first executable program.

[0011] In an embodiment of the present application, the process of transmitting target log data to a server by the vehicle terminal device according to the network sharing address includes:

[0012] download the program source code of the intranet penetration tool, and cross-compile the program source code by using a cross-compile tool to generate an executable program of the intranet penetration tool for the architecture of the central processing unit, denoted as a second executable program;

[0013] modify the configuration text file of the intranet penetration tool, and run the second executable program in the startup script of the car machine operating system; and,

[0014] transmit target log data to a server according to the target log data transmission request result and the network sharing address.

[0015] In an embodiment of the present application, the process of identifying the connection state of the data transmission interface of the mobile terminal device and the data transmission interface of the vehicle terminal device includes:

[0016] capture the connection action of the mobile terminal device by using a rule file pre-set in the car machine operating system, and determine whether the mobile terminal device is connected to the vehicle terminal device; and,

[0017] after the mobile terminal device is connected to the vehicle terminal device, identify whether the mobile terminal device and the vehicle terminal device are connected through the data transmission interface by using the rule file; wherein the data transmission interface includes a universal serial bus interface; and,

[0018] when the mobile terminal device and the vehicle terminal device are connected through the data transmission interface, determine that the connection state of the data transmission interface of the vehicle terminal device and the data transmission interface of the mobile terminal device is a hot plug state.

[0019] In an embodiment of the present application, the process of obtaining the product identification code and the supplier identification code of the data transmission interface of the mobile terminal device includes:

[0020] obtaining the product identification code and the supplier identification code of the data transmission interface of the mobile terminal device by calling a device information query instruction in the car machine operating system; and / or,

[0021] obtaining the product identification code and the supplier identification code of the data transmission interface of the mobile terminal device by querying the specification of the mobile terminal device in the car machine operating system.

[0022] In an embodiment of the present application, when the target log data is transmitted to the server, the method further comprises:

[0023] reading, by the server, hardware device parameter information in the target log data for representing the state of the hardware device of the vehicle, and reading software system data in the target log data for representing the state of the software system of the vehicle;

[0024] diagnosing and determining the current state of the vehicle according to the hardware device parameter information and the software system data; and inputting the hardware device parameter information and the software system data as training data into a neural network architecture established in advance or in real time for training, to generate an intelligent driving model for driving control of the vehicle.

[0025] In an embodiment of the present application, if the intranet penetration tool includes a reverse proxy tool, the process of modifying the configuration text file of the reverse proxy tool includes: modifying the Internet Protocol of the reverse proxy tool, and modifying the listening port of the reverse proxy tool.

[0026] The present application also provides a log data transmission system, which comprises:

[0027] a data acquisition module, configured to obtain the product identification code and the supplier identification code of the data transmission interface of the mobile terminal device;

[0028] a driver configuration module, configured to perform operating system kernel compilation configuration on the mobile terminal device according to the product identification code and the supplier identification code, and match the driver file of the mobile terminal device based on the operating system kernel compilation configuration result; wherein the operating system kernel compilation configuration result includes the network sharing configuration of the mobile terminal device;

[0029] a log data transmission module, configured to identify the connection state of the data transmission interface of the mobile terminal device and the data transmission interface of the vehicle-mounted terminal device, and dynamically allocate the network sharing address of the mobile terminal device based on the driver file when the connection state is a hot plug state, so that the vehicle-mounted terminal device transmits target log data to a server according to the network sharing address; wherein the target log data includes vehicle history record report log data.

[0030] The application further provides a computer device comprising a memory, a processor and a computer program stored in the memory, wherein the processor executes the computer program to implement the steps of the log data transmission method according to any one of the preceding embodiments.

[0031] The application further provides a computer readable storage medium, which stores a computer program, wherein the computer program is executed by a processor to implement the steps of the log data transmission method according to any one of the preceding embodiments.

[0032] As described above, the application provides a log data transmission method and system, a computer device and a medium, which have the following beneficial effects: the application obtains the product identification code and the supplier identification code of the data transmission interface of the mobile terminal device, then performs operating system kernel compilation configuration on the mobile terminal device based on the product identification code and the supplier identification code, and matches the driver file of the mobile terminal device based on the operating system kernel compilation configuration result; then the application identifies the connection state of the data transmission interface of the mobile terminal device and the data transmission interface of the vehicle terminal device, and when the connection state is a hot plug state, dynamically allocates the network sharing address of the mobile terminal device based on the driver file, so that the vehicle terminal device transmits the target log data to the server according to the network sharing address; wherein the target log data comprises vehicle history record report log data. Therefore, the application can establish the network communication connection between the vehicle terminal device and the mobile terminal device, and in the scenario without other networks, the vehicle terminal device can share the network of the mobile terminal device, so that the vehicle operating system can perform network sharing with the mobile terminal device through the corresponding data transmission interface, thereby transmitting the target log data to the server to realize data exchange transmission and internet access. Therefore, the application does not need to set an additional mobile network module in the vehicle or use a wired Ethernet network with limited scenarios, and by using the communication network of the mobile terminal device, the vehicle operating system in the vehicle can perform network communication with the outside, so that the server can remotely obtain the vehicle history record report log data of the vehicle terminal, thereby facilitating subsequent big data analysis on the health status of the vehicle and optimization of the performance parameters of the vehicle. Moreover, for the vehicle in the test stage or the emergency problem of the vehicle in actual use by the user, the developer can remotely maintain and process the related problems, thereby saving the time for copying the related information to the storage medium and then forwarding the information to the developer to analyze the problems, and improving the processing efficiency of the vehicle fault problems. In addition, the application can realize direct access of the server backend to the vehicle terminal system through the intranet penetration technology, thereby viewing the real-time related parameters of the vehicle and the performance parameters of the software system; meanwhile, the application can also reduce the power consumption of the vehicle operating system through hot plug. BRIEF DESCRIPTION OF DRAWINGS

[0033] Figure 1A flowchart of a log data transmission method provided by an embodiment of the present application;

[0034] Figure 2 A network link diagram of log data transmission provided by an embodiment of the present application;

[0035] Figure 3 A hardware structure diagram of a log data transmission system provided by an embodiment of the present application;

[0036] Figure 4 A hardware structure diagram of a computer device suitable for implementing one or more embodiments of the present application. DETAILED DESCRIPTION

[0037] The present application will be described by specific embodiments below, and those skilled in the art can easily understand other advantages and effects of the present application from the disclosure of the present specification. The present application can also be implemented or applied by other different specific embodiments, and the details in the present specification can be modified or changed based on different views and applications without departing from the spirit of the present application. It can be understood that the following embodiments and features in the embodiments can be combined with each other without conflict. In addition, it can be understood that the diagrams provided in the following embodiments only illustrate the basic concept of the present application in a schematic manner, and only the components related to the present application are shown in the diagrams, not the number, shape and size of the components when actually implemented. The type, number and ratio of each component in actual implementation can be arbitrarily changed, and the layout type of the components can be more complex.

[0038] Since the way of uploading the diagnostic data of part of the vehicles to the background server is not suitable for most vehicle models, the VHR of most vehicle models cannot be more effectively collected and analyzed. However, the USB (Universal Serial Bus) interface is functionally adapted to most vehicle models, and if the USB network sharing function is realized, the embedded device that only supports USB connection and does not support network connection can have the ability to access the network. When facing the user's on-site problems, if they can be transmitted to the background for analysis and solved in time, there is no need to recall the faulty vehicle to take out the relevant data for analysis, which can greatly improve the user's experience and the optimization efficiency of vehicle functions. Especially in the early stage of new function development, it is inevitable that there will be parts that need to be optimized on the software. If the function of remotely accessing the vehicle system network is realized, the developer can analyze and optimize the relevant functions in real time, improving the development efficiency. In the later vehicle maintenance process, if the function of remotely accessing the vehicle system network is realized, it is not limited to the detection of core parameters by traditional test equipment, but also can detect and optimize the health parameter data of the whole vehicle. Especially in the stage of rapid development of intelligent driving technology, if the training data and important parameters of intelligent driving of each vehicle can be transmitted to the backend to rapidly expand the data set of the training model, it is beneficial to the development of intelligent driving technology. Although most types of smartphones currently have the function of USB network sharing, it is not plug-and-play in the embedded field.

[0039] In view of the above description, Figure 1 A flowchart of a log data transmission method is shown. Specifically, in an example embodiment, as shown in Figure 1 The embodiment provides a log data transmission method, which includes the following steps:

[0040] S110, obtaining the product identification code (Product ID, PID) and the supplier identification code (Vender ID, VID) of the data transmission interface of the mobile terminal device. In this or other embodiments, the mobile terminal device can be a mobile terminal device running the iOS system, referred to as an iOS device. In addition, the mobile terminal device can also be a mobile terminal device running the Android system, the HarmonyOS system, the Symbian system, the Windows Phone system or the BlackBerry OS system, etc. As an example, the mobile terminal device in this embodiment can be a mobile phone running the iOS system, referred to as an iOS mobile phone. In this or other embodiments, the data transmission interface includes but is not limited to the universal serial bus (Universal Serial Bus, USB) interface.

[0041] S120, performing operating system kernel compilation configuration on the mobile terminal device based on the product identification code and the supplier identification code, and matching a driver file of the mobile terminal device based on an operating system kernel compilation configuration result; wherein the operating system kernel compilation configuration result comprises a network sharing configuration of the mobile terminal device. As an example, if the mobile terminal device in the embodiment is a mobile phone running an iOS system, the embodiment can configure CONFIG USB IPHETH through Menuconfig to generate a driver file as ipheth.ko by compiling the kernel. Menuconfig is an image tool for configuring the kernel or other software components in the Linux system, which provides a text-based graphical user interface, so that users can configure the Linux kernel, U-Boot or other software components through an intuitive interface. The main function of Menuconfig is to read and modify configuration files (such as.config), which determine various options and parameters of the software during compilation. CONFIG USB IPHETH is a configuration option in the Linux kernel, which is used to enable support for iPhone USB network (IP over USB Ethernet, IPHETH for short). When the CONFIG USB IPHETH option is enabled and compiled into the kernel, the Linux system configured by the vehicle terminal device can recognize the iOS mobile phone connected through the USB interface, so as to realize network sharing between the iOS mobile phone and the vehicle terminal device. Kernel is the main component of the operating system, which is responsible for managing the hardware resources of the computer and providing system services, including but not limited to memory management, process management, file system management, and device drivers. Kernel serves as an interface between the operating system and hardware, and all software applications must access hardware resources through Kernel.

[0042] S130, identifying the connection state of the data transmission interface of the mobile terminal device and the data transmission interface of the vehicle terminal device, and when the connection state is a hot plug state, dynamically allocating a network sharing address of the mobile terminal device based on the driver file, so that the vehicle terminal device transmits the target log data to the server according to the network sharing address; wherein the target log data comprises Vehicle History Report (VHR) log data. In the embodiment or other embodiments, hot plug (Hot Swap) can also be referred to as live plug, which is a kind of hardware device that allows dynamic insertion or removal during operation of the operating system.

[0043] Therefore, the embodiment does not need to set an additional mobile network module in the vehicle or use a wired Ethernet network with limited use scenarios, and network communication between the vehicle infotainment system and the outside can be realized by using the communication network of the mobile terminal device, so that the server can remotely acquire vehicle history record report log data of the vehicle end, thereby facilitating subsequent big data analysis of the vehicle health status and optimization of vehicle performance parameters. Moreover, for vehicles in the test phase or emergency problems of the vehicle in actual use by the user, the developer can remotely maintain and handle the related problems, thereby saving the time of copying the related information to the storage medium and then forwarding it to the developer for analysis of the problem, and improving the processing efficiency of vehicle fault problems. Meanwhile, the power consumption of the vehicle infotainment system can be reduced through hot plugging.

[0044] In an example embodiment, the process of dynamically allocating the network sharing address of the mobile terminal device based on the driver file further includes: cross-compiling the dependencies of the vehicle infotainment system in sequence by using a cross-compilation tool to generate an executable program for the vehicle infotainment system architecture, denoted as a first executable program; embedding the first executable program into the vehicle infotainment system, and dynamically allocating the network sharing address of the mobile terminal device based on the driver file and the first executable program. The vehicle terminal device is configured with the vehicle infotainment system. Cross-compilation refers to a process of compiling code that can run on another computer architecture (usually target machine, Target) on a computer architecture (usually host, Host). As an example, the embodiment can use an ARM architecture cross-compilation tool to cross-compile the dependencies of the mobile terminal device: libtool-bin, libplist-dev, libusbmuxd-dev, libimobiledevice-dev, libimobiledevice-glue-dev, libusb-1.0-0-dev, to generate an executable program conforming to the vehicle infotainment system architecture. The ARM architecture, also known as Advanced RISC Machine, is a widely used processor architecture.

[0045] Specifically, in this embodiment, libtool-bin is a general library support script used to create and invoke dynamic libraries on different platforms. During software development and compilation, libtool-bin can help developers more conveniently manage dynamic libraries, including operations such as creation, linking, and installation. libplist is a library used to read and write Apple's binary and XML property list formats. libplist-dev is the development package of libplist, which contains the header files and library files required during development. It is usually used in applications and tools that communicate with iOS devices as part of the libimobiledevice stack. libusbmuxd is a library used to handle USB multiplexing (muxing) and forwarding, especially for communications related to iOS devices. libusbmuxd-dev is the development package of libusbmuxd, which contains the header files and library files required during development. It is usually used to implement the function of communicating with iOS devices through USB. libimobiledevice is an open-source software library that can directly communicate with iOS devices using system native protocols. libimobiledevice-dev is the development package of libimobiledevice, which contains the header files, library files, and related tools required during development. It allows developers to implement functions such as communication with iOS devices, information collection, and file backup without relying on iOS private libraries. libimobiledevice-glue is a "glue" library used to solve the problem that the original libimobiledevice-dev package is not available or incompatible with other libraries. libimobiledevice-glue-dev is the development package of libimobiledevice-glue, which contains the header files and library files required during development. It is usually used in conjunction with libimobiledevice to ensure smooth communication with iOS devices. libusb is a user space library used to access USB devices. It provides basic access capabilities to USB devices, including device enumeration, configuration, interface declaration, data transmission, etc. libusb-1.0-0-dev is the development package of libusb, which contains the header files and library files required during development. It is usually used to develop applications or tools that need to communicate with USB devices.

[0046] In an exemplary embodiment, the process of transmitting the target log data to the server by the vehicle terminal device according to the network sharing address includes: downloading a program source code of the intranet penetration tool, and cross- compiling the program source code to generate an execution program of the intranet penetration tool for a central processing unit structure, denoted as a second execution program; modifying a configuration text file of the intranet penetration tool, and running the second execution program in a startup script of the vehicle operating system; and sending a target log data transmission request to the vehicle terminal device, and after a network sharing configuration of the mobile terminal device is triggered, responding to the target log data transmission request by the vehicle terminal device, and transmitting the target log data to the server according to a target log data transmission request result and a network sharing address. In this embodiment, if the intranet penetration tool includes a reverse proxy tool, the process of modifying the configuration text file of the reverse proxy tool includes: modifying an Internet Protocol of the reverse proxy tool, and modifying a listening port of the reverse proxy tool.

[0047] In the present embodiment or other embodiments, the intranet penetration tool includes, but is not limited to, FRP (Fast Reverse Proxy), ngrok, cpolar, etc. FRP has high performance and low resource occupation, can carry multiple requests on a single connection, reduces connection establishment time and reduces request delay; at the same time, it has disconnection reconnection and heartbeat keep-alive, ensuring the stability and reliability of FRP in the intranet penetration process, even in poor network conditions. It can also maintain connection; and supports SSL (Secure Socket Layer) / TLS (Transport Layer Security) encrypted access, ensuring the security of data during network transmission, preventing data from being stolen or tampered with. Under the same hardware conditions, FRP can handle more concurrent connections and data transmission while maintaining a low CPU (Central Processing Unit) and memory usage. This is particularly important for embedded applications with low CPU performance and memory resources; FRP has good open source properties, does not require additional software license fees, and has rich help documentation, which helps to quickly solve problems encountered during development. Combined with the characteristics of intranet penetration, the network link between the backend server and the vehicle end is established by supporting multiple protocols such as TCP (Transmission Control Protocol), UDP (User Datagram Protocol), HTTP (Hyper Text Transfer Protocol), and the FRP framework with the characteristics of high-performance reverse proxy of intranet penetration. The network link for log data transmission established based on the intranet penetration tool FRP is shown in FIG. 10. Figure 2 As an example, in the present embodiment, if the intranet penetration tool is FRP, the present embodiment can further include: downloading the frpc program source code from the FRP official website, cross-compiling the frpc execution program suitable for the CPU architecture, denoted as a second execution program. Modify the configuration text file frpc.ini of the frpc client, including modifying the ip and listening port of the frpc client server. And run the frpc client program in the background in the startup script of the vehicle operating system, so that the frpc client can communicate with the server. Wherein, frpc is a client component in the FRP project. FRP is a high-performance reverse proxy application that can easily penetrate the intranet, provide services to the external network, or perform remote desktop, SSH access, etc. The frpc client is usually deployed on an intranet machine and works in cooperation with the FRPS server located on the public network.

[0048] In an exemplary embodiment, the process of identifying the connection state of the data transmission interface of the mobile terminal device and the data transmission interface of the vehicle terminal device includes: capturing the connection action of the mobile terminal device through a rule file preset in the vehicle machine operating system, determining whether the mobile terminal device is connected with the vehicle terminal device; and after the mobile terminal device is connected with the vehicle terminal device, identifying whether the mobile terminal device and the vehicle terminal device are connected through the data transmission interface through the rule file; wherein the data transmission interface includes a universal serial bus interface; and when the mobile terminal device and the vehicle terminal device are connected through the data transmission interface, it is determined that the connection state of the data transmission interface of the vehicle terminal device and the data transmission interface of the mobile terminal device is a hot plug state.

[0049] Specifically, the embodiment can identify the connection state of the data transmission interface of the mobile terminal device and the data transmission interface of the vehicle-mounted terminal device through the rules rule file involved in the USB hot plug under the etc directory. In the Linux system, the etc directory is a very important system directory, which is mainly used to store system configuration files. These configuration files determine the behavior and running mode of the system, and are the key part of Linux system management and maintenance. The files in the etc directory are usually stored in plaintext form and can be modified by users. These files are necessary configuration files for system operation, used to specify system parameters, network configuration, service configuration, etc. System administrators can configure and manage the system by modifying these files. In the Linux system, the / etc / udev / rules.d / directory contains files used to define udev rules. These rule files determine how udev should handle devices when they are connected to the system. Udev is a tool in the Linux system for managing device files, which runs in the form of a daemon and manages device files under the / dev directory by listening to uevents issued by the kernel. Udev rules are configuration files that guide udev on how to handle specific devices. These rules consist of a series of key / value pairs, separated by commas. As an example, a new rule file for USB can be created, / etc / udev / rules.d / 99-USB-share-network.rules, with the following content: ACTION == "add", SUBSYSTEM == "USB", ATTRS {idVendor} == "vendor ID", ATTRS {idProduct} == "product ID", RUN += "user_script.sh". Among them, ACTION == "add" indicates that the car system captures the action judgment of the USB slave device insertion; SUBSYSTEM == "USB" indicates whether the inserted device type is USB type judgment. Then run the driver file ipheth.ko generated in the above embodiment and the first execution program generated by cross-compiling in Embodiment 3 in the user_script.sh script, and then realize the dynamic loading of the driver.

[0050] In an example embodiment, the process of obtaining the product identification code and the supplier identification code of the data transmission interface of the mobile terminal device includes: obtaining the product identification code and the supplier identification code of the data transmission interface of the mobile terminal device by calling a device information query instruction in the vehicle machine operating system; and / or obtaining the product identification code and the supplier identification code of the data transmission interface of the mobile terminal device by querying the specification of the mobile terminal device in the vehicle machine operating system. As an example, if the mobile terminal device in the present embodiment is a mobile phone running an iOS system, the PID and VID of the USB interface of the iOS mobile phone can be obtained by the lsusb query command under the Linux system. The lsusb command is used to display the USB device list and detailed information of the USB device of the local machine, and the USB device information displayed by the lsusb command comes from the corresponding file under the “ / proc / bus / usb” directory. As another example, if the mobile terminal device in the present embodiment is a mobile phone running an iOS system or other system, the PID and VID of the USB interface of the corresponding mobile phone can be obtained by querying the specification of each mobile phone model under the Linux system.

[0051] In an example embodiment, after the target log data is transmitted to the server, the embodiment can further include: reading, by the server, hardware device parameter information in the target log data for representing a state of a hardware device of the vehicle, and reading software system data in the target log data for representing a state of a software system of the vehicle; diagnosing and determining the current state of the vehicle according to the hardware device parameter information and the software system data; and inputting the hardware device parameter information and the software system data as training data into a neural network architecture established in advance or in real time for training, to generate an intelligent driving model for driving control of the vehicle. As an example, in the embodiment, the specific process of diagnosing and determining the current state of the vehicle according to the hardware device parameter information and the software system data can include: if the hardware device parameter information in the target log data is inconsistent with hardware device standard parameter information, and / or if the software system data in the target log data is inconsistent with software system standard data, it can be determined that the current state of the vehicle is an unhealthy state. As an example, in the embodiment, the process of inputting the hardware device parameter information and the software system data as training data to generate the intelligent driving model for driving control of the vehicle can be: inputting the hardware device parameter information and the software system data as training data, and then inputting into a neural network structure such as a convolutional neural network (CNN), a deep neural network (DNN), a feedforward neural network (FNN), a long short-term memory network (LSTM), etc. for training, to generate an intelligent driving model for driving control of the vehicle. The specific process of training the hardware device parameter information and the software system data by the neural network structure is not described herein.

[0052] In summary, the application provides a log data transmission method. The product identification code and the supplier identification code of the data transmission interface of the mobile terminal device are obtained, and then the mobile terminal device is operated based on the product identification code and the supplier identification code for kernel compilation configuration of the operating system, and the drive file of the mobile terminal device is matched based on the kernel compilation configuration result of the operating system. Then, the connection state of the data transmission interface of the mobile terminal device and the data transmission interface of the vehicle terminal device is identified, and when the connection state is a hot plug state, the network sharing address of the mobile terminal device is dynamically allocated based on the drive file, so that the vehicle terminal device transmits the target log data to the server according to the network sharing address; wherein the target log data includes vehicle history record report log data. Therefore, the method can establish a network communication connection between the vehicle terminal device and the mobile terminal device, and in the absence of other networks, the vehicle terminal device can share the network of the mobile terminal device, so that the vehicle operating system can share the network with the mobile terminal device through the corresponding data transmission interface, thereby transmitting the target log data to the server to realize data exchange transmission and Internet access. Therefore, the method does not need to set an additional mobile network module in the vehicle or use a wired Ethernet network with limited scenarios, and by using the communication network of the mobile terminal device, the vehicle operating system in the vehicle can communicate with the outside network, so that the server can remotely obtain the vehicle history record report log data of the vehicle terminal, thereby facilitating subsequent big data analysis of the vehicle health status and optimization of the vehicle performance parameters. Moreover, for the vehicle in the test stage or the emergency problem of the vehicle in actual use by the user, the developer can remotely maintain and handle the related problems, thereby saving the time of copying the related information to the storage medium and then forwarding it to the developer for analysis of the problem, and improving the processing efficiency of the vehicle fault problem. Meanwhile, the power consumption of the vehicle operating system can be reduced through hot plug.

[0053] In addition, the method takes the vehicle terminal device as a master device for data transmission and takes the mobile terminal device as a slave device for data transmission. If the vehicle terminal device and the mobile terminal device are connected through a USB interface, the USB device of the vehicle terminal device can be taken as a USB master device and the mobile phone can be taken as a USB slave device. Then, a driver file that is developed based on the USB interface and is compatible with an iOS system mobile product is loaded to achieve that the vehicle terminal device can share the network of the mobile phone. That is, in a scenario without other networks, the USB master device can share the network of the USB slave device, so that the Linux system can share the network with the iOS device through the interface, and data exchange and transmission and internet access are achieved. Therefore, the method can design a USB network sharing function of the iOS system mobile terminal, so that the vehicle can communicate with the external network to transmit vehicle historical record report log data. Moreover, through an FRP internal network penetration technology, a server backend can directly access the vehicle terminal system, and then real-time related parameters of the vehicle and performance parameters of the software system can be viewed.

[0054] In another example embodiment of the present application, as shown in Figure 3 The log data transmission system comprises:

[0055] The data collection module 310 is configured to acquire a product identification code and a supplier identification code of a data transmission interface of the mobile terminal device. In the embodiment or other embodiments, the mobile terminal device can be a mobile terminal device running an iOS system, referred to as an iOS device. In addition, the mobile terminal device can also be a mobile terminal device running an Android system, a HarmonyOS system, a Symbian system, a Windows Phone system or a BlackBerry OS system, etc. As an example, the mobile terminal device in the embodiment can be a mobile phone running an iOS system, referred to as an iOS mobile phone. In the embodiment or other embodiments, the data transmission interface includes but is not limited to a USB interface.

[0056] The driving configuration module 320 is configured to perform operating system kernel compilation configuration on the mobile terminal device according to the product identification code and the supplier identification code, and match the driving file of the mobile terminal device based on the operating system kernel compilation configuration result. The operating system kernel compilation configuration result includes the network sharing configuration of the mobile terminal device. As an example, if the mobile terminal device in the embodiment is a mobile phone running the iOS system, the embodiment can configure CONFIG USB IPHETH through Menuconfig to generate the driving file as ipheth.ko by compiling the kernel. Menuconfig is an image tool for configuring the kernel or other software components in the Linux system, which provides a text-based graphical user interface, so that the user can configure the Linux kernel, U-Boot or other software components through an intuitive interface. The main function of Menuconfig is to read and modify configuration files (such as.config), which determine various options and parameters of the software during compilation. CONFIG USB IPHETH is a configuration option in the Linux kernel, which is used to enable support for iPhone USB network (IP over USB Ethernet, IPHETH for short). When the CONFIG USB IPHETH option is enabled and compiled into the kernel, the Linux system configured by the vehicle terminal device can identify the iOS mobile phone connected through the USB interface, so as to realize network sharing between the iOS mobile phone and the vehicle terminal device. The kernel is the main component of the operating system, which is responsible for managing the hardware resources of the computer and providing system services, including but not limited to memory management, process management, file system management, and device drivers. The kernel serves as an interface between the operating system and the hardware, and all software applications must access hardware resources through the kernel.

[0057] The log data transmission module 330 is configured to identify the connection state of the data transmission interface of the mobile terminal device and the data transmission interface of the vehicle terminal device, and when the connection state is a hot plug state, dynamically allocate the network sharing address of the mobile terminal device based on the driving file, so that the vehicle terminal device transmits the target log data to the server according to the network sharing address. The target log data includes Vehicle History Report (VHR) log data. In the embodiment or other embodiments, hot plug (Hot Swap) can also be called hot plug, which is a kind of hardware device that allows dynamic insertion or removal during operation of the operating system.

[0058] Therefore, the embodiment does not need to set an additional mobile network module in the vehicle or use a wired Ethernet network with limited use scenarios, and network communication between the vehicle infotainment system and the outside can be realized by using the communication network of the mobile terminal device, so that the server can remotely acquire vehicle history record report log data of the vehicle end, thereby facilitating subsequent big data analysis of the vehicle health status and optimization of vehicle performance parameters. Moreover, for vehicles in the test phase or emergency problems of the vehicle in actual use by the user, the developer can remotely maintain and handle the related problems, thereby saving the time of copying the related information to the storage medium and then forwarding it to the developer for analysis of the problem, and improving the processing efficiency of vehicle fault problems. Meanwhile, the power consumption of the vehicle infotainment system can be reduced through hot plugging.

[0059] In an example embodiment, the process of dynamically allocating the network sharing address of the mobile terminal device based on the driver file further includes: cross-compiling the dependencies of the vehicle infotainment system in sequence by using a cross-compilation tool to generate an executable program for the vehicle infotainment system architecture, denoted as a first executable program; embedding the first executable program into the vehicle infotainment system, and dynamically allocating the network sharing address of the mobile terminal device based on the driver file and the first executable program. The vehicle terminal device is configured with the vehicle infotainment system. Cross-compilation refers to a process of compiling code that can run on another computer architecture (usually target machine, Target) on a computer architecture (usually host, Host). As an example, the embodiment can use an ARM architecture cross-compilation tool to cross-compile the dependencies of the mobile terminal device: libtool-bin, libplist-dev, libusbmuxd-dev, libimobiledevice-dev, libimobiledevice-glue-dev, libusb-1.0-0-dev, to generate an executable program conforming to the vehicle infotainment system architecture. The ARM architecture, also known as Advanced RISC Machine, is a widely used processor architecture.

[0060] Specifically, in this embodiment, libtool-bin is a general library support script used to create and invoke dynamic libraries on different platforms. During software development and compilation, libtool-bin can help developers more conveniently manage dynamic libraries, including operations such as creation, linking, and installation. libplist is a library used to read and write Apple's binary and XML property list formats. libplist-dev is the development package of libplist, which contains the header files and library files required during development. It is usually used in applications and tools that communicate with iOS devices as part of the libimobiledevice stack. libusbmuxd is a library used to handle USB multiplexing (muxing) and forwarding, especially for communications related to iOS devices. libusbmuxd-dev is the development package of libusbmuxd, which contains the header files and library files required during development. It is usually used to implement the function of communicating with iOS devices through USB. libimobiledevice is an open-source software library that can directly communicate with iOS devices using system native protocols. libimobiledevice-dev is the development package of libimobiledevice, which contains the header files, library files, and related tools required during development. It allows developers to implement functions such as communication with iOS devices, information collection, and file backup without relying on iOS private libraries. libimobiledevice-glue is a "glue" library used to solve the problem that the original libimobiledevice-dev package is not available or incompatible with other libraries. libimobiledevice-glue-dev is the development package of libimobiledevice-glue, which contains the header files and library files required during development. It is usually used in conjunction with libimobiledevice to ensure smooth communication with iOS devices. libusb is a user space library used to access USB devices. It provides basic access capabilities to USB devices, including device enumeration, configuration, interface declaration, data transmission, etc. libusb-1.0-0-dev is the development package of libusb, which contains the header files and library files required during development. It is usually used to develop applications or tools that need to communicate with USB devices.

[0061] In an exemplary embodiment, the process of transmitting the target log data to the server by the vehicle terminal device according to the network sharing address includes: downloading a program source code of the intranet penetration tool, and cross- compiling the program source code to generate an execution program of the intranet penetration tool for a central processing unit structure, denoted as a second execution program; modifying a configuration text file of the intranet penetration tool, and running the second execution program in a startup script of the vehicle operating system; and sending a target log data transmission request to the vehicle terminal device, and after a network sharing configuration of the mobile terminal device is triggered, responding to the target log data transmission request by the vehicle terminal device, and transmitting the target log data to the server according to a target log data transmission request result and a network sharing address. In this embodiment, if the intranet penetration tool includes a reverse proxy tool, the process of modifying the configuration text file of the reverse proxy tool includes: modifying an Internet Protocol of the reverse proxy tool, and modifying a listening port of the reverse proxy tool.

[0062] In the present embodiment or other embodiments, the intranet penetration tool includes, but is not limited to, FRP (Fast Reverse Proxy), ngrok, cpolar, etc. FRP has high performance and low resource occupation, can carry multiple requests on a single connection, reduces connection establishment time and reduces request delay; at the same time, it has disconnection reconnection and heartbeat keep-alive, ensuring the stability and reliability of FRP in the intranet penetration process, even in poor network conditions. It can also maintain connection; and supports SSL (Secure Socket Layer) / TLS (Transport Layer Security) encrypted access, ensuring the security of data during network transmission, preventing data from being stolen or tampered with. Under the same hardware conditions, FRP can handle more concurrent connections and data transmission while maintaining a low CPU (Central Processing Unit) and memory usage. This is particularly important for embedded applications with low CPU performance and memory resources; FRP has good open source properties, does not require additional software license fees, and has rich help documentation, which helps to quickly solve problems encountered during development. Combined with the characteristics of intranet penetration, the network link between the backend server and the vehicle end is established by supporting multiple protocols such as TCP (Transmission Control Protocol), UDP (User Datagram Protocol), HTTP (Hyper Text Transfer Protocol), and the FRP framework with the characteristics of high-performance reverse proxy of intranet penetration. The network link for log data transmission established based on the intranet penetration tool FRP is shown in FIG. 8. As an example, in the present embodiment, if the intranet penetration tool is FRP, the present embodiment can also include: downloading the frpc program source code from the FRP official website, cross-compiling the frpc execution program suitable for the CPU architecture, denoted as a second execution program. Modify the configuration text file frpc.ini of the frpc client, including modifying the ip and listening port of the frpc client server. And run the frpc client program in the background in the startup script of the vehicle operating system, so that the frpc client can communicate with the server. Wherein, frpc is a client component in the FRP project. FRP is a high-performance reverse proxy application that can easily penetrate the intranet and provide services to the external network, or perform remote desktop, SSH access, etc. The frpc client is usually deployed on an intranet machine and works in cooperation with the FRPS server located on the public network. Figure 2 As an example, in the present embodiment, if the intranet penetration tool is FRP, the present embodiment can also include: downloading the frpc program source code from the FRP official website, cross-compiling the frpc execution program suitable for the CPU architecture, denoted as a second execution program. Modify the configuration text file frpc.ini of the frpc client, including modifying the ip and listening port of the frpc client server. And run the frpc client program in the background in the startup script of the vehicle operating system, so that the frpc client can communicate with the server. Wherein, frpc is a client component in the FRP project. FRP is a high-performance reverse proxy application that can easily penetrate the intranet and provide services to the external network, or perform remote desktop, SSH access, etc. The frpc client is usually deployed on an intranet machine and works in cooperation with the FRPS server located on the public network.

[0063] In an exemplary embodiment, the process of identifying the connection state of the data transmission interface of the mobile terminal device and the data transmission interface of the vehicle terminal device includes: capturing the connection action of the mobile terminal device through a rule file preset in the vehicle machine operating system, determining whether the mobile terminal device is connected with the vehicle terminal device; and after the mobile terminal device is connected with the vehicle terminal device, identifying whether the mobile terminal device and the vehicle terminal device are connected through the data transmission interface through the rule file; wherein the data transmission interface includes a universal serial bus interface; and when the mobile terminal device and the vehicle terminal device are connected through the data transmission interface, it is determined that the connection state of the data transmission interface of the vehicle terminal device and the data transmission interface of the mobile terminal device is a hot plug state.

[0064] Specifically, the embodiment can identify the connection state of the data transmission interface of the mobile terminal device and the data transmission interface of the vehicle-mounted terminal device through the rules rule file involved in the USB hot plug under the etc directory. In the Linux system, the etc directory is a very important system directory, which is mainly used to store system configuration files. These configuration files determine the behavior and running mode of the system, and are the key part of Linux system management and maintenance. The files in the etc directory are usually stored in plaintext form and can be modified by users. These files are necessary configuration files for system operation, used to specify system parameters, network configuration, service configuration, etc. System administrators can configure and manage the system by modifying these files. In the Linux system, the / etc / udev / rules.d / directory contains files used to define udev rules. These rule files determine how udev should handle devices when they are connected to the system. Udev is a tool in the Linux system for managing device files, which runs in the form of a daemon and manages device files under the / dev directory by listening to uevents issued by the kernel. Udev rules are configuration files that guide udev on how to handle specific devices. These rules consist of a series of key / value pairs, separated by commas. As an example, a new rule file for USB can be created, / etc / udev / rules.d / 99-USB-share-network.rules, with the following content: ACTION == "add", SUBSYSTEM == "USB", ATTRS {idVendor} == "vendor ID", ATTRS {idProduct} == "product ID", RUN += "user_script.sh". Among them, ACTION == "add" indicates that the car system captures the action judgment of the USB slave device insertion; SUBSYSTEM == "USB" indicates whether the inserted device type is USB type judgment. Then run the driver file ipheth.ko generated in the above embodiment and the first execution program generated by cross-compiling in Embodiment 3 in the user_script.sh script, and then realize the dynamic loading of the driver.

[0065] In an example embodiment, the process of acquiring the product identification code and the supplier identification code of the data transmission interface of the mobile terminal device includes: acquiring the product identification code and the supplier identification code of the data transmission interface of the mobile terminal device by calling a device information query instruction in the vehicle machine operating system; and / or acquiring the product identification code and the supplier identification code of the data transmission interface of the mobile terminal device by querying the specification of the mobile terminal device in the vehicle machine operating system. As an example, if the mobile terminal device in the present embodiment is a mobile phone running an iOS system, the PID and VID of the USB interface of the iOS mobile phone can be acquired by the lsusb query command under the Linux system. The lsusb command is used to display the USB device list and detailed information of the USB device of the local machine, and the USB device information displayed by the lsusb command comes from the corresponding file under the “ / proc / bus / usb” directory. As another example, if the mobile terminal device in the present embodiment is a mobile phone running an iOS system or other system, the PID and VID of the USB interface of the corresponding mobile phone can be acquired by querying the specification of each mobile phone model under the Linux system.

[0066] In an example embodiment, after the target log data is transmitted to the server, the embodiment can further include: reading, by the server, hardware device parameter information in the target log data for representing a state of a hardware device of the vehicle, and reading software system data in the target log data for representing a state of a software system of the vehicle; diagnosing and determining the current state of the vehicle according to the hardware device parameter information and the software system data; and inputting the hardware device parameter information and the software system data as training data into a neural network architecture established in advance or in real time for training, to generate an intelligent driving model for driving control of the vehicle. As an example, in the embodiment, the specific process of diagnosing and determining the current state of the vehicle according to the hardware device parameter information and the software system data can include: if the hardware device parameter information in the target log data is inconsistent with hardware device standard parameter information, and / or if the software system data in the target log data is inconsistent with software system standard data, it can be determined that the current state of the vehicle is an unhealthy state. As an example, in the embodiment, the process of inputting the hardware device parameter information and the software system data as training data to generate the intelligent driving model for driving control of the vehicle can be: inputting the hardware device parameter information and the software system data as training data, and then inputting into a neural network structure such as a convolutional neural network (CNN), a deep neural network (DNN), a feedforward neural network (FNN), a long short-term memory network (LSTM), etc. for training, to generate an intelligent driving model for driving control of the vehicle. The specific process of training the hardware device parameter information and the software system data by the neural network structure is not described herein.

[0067] In summary, the application provides a log data transmission system, which obtains product identification code and supplier identification code of a data transmission interface of a mobile terminal device, then performs operating system kernel compilation configuration on the mobile terminal device based on the product identification code and the supplier identification code, and matches a drive file of the mobile terminal device based on the operating system kernel compilation configuration result; then identifies the connection state of the data transmission interface of the mobile terminal device and a data transmission interface of a vehicle-mounted terminal device, and when the connection state is a hot plug state, dynamically allocates a network sharing address of the mobile terminal device based on the drive file, so that the vehicle-mounted terminal device transmits target log data to a server according to the network sharing address; wherein the target log data includes vehicle history record report log data. It can be seen that the system can establish a network communication connection between the vehicle-mounted terminal device and the mobile terminal device, and in the absence of other networks, the vehicle-mounted terminal device can share the network of the mobile terminal device, so that the vehicle machine operating system can perform network sharing with the mobile terminal device through the corresponding data transmission interface, thereby transmitting the target log data to the server to realize data exchange transmission and Internet access. Therefore, the system does not need to set an additional mobile network module in the vehicle or use a wired Ethernet network with limited use scenarios, and by using the communication network of the mobile terminal device, the vehicle machine operating system in the vehicle can perform network communication with the outside, so that the server can remotely obtain vehicle history record report log data of the vehicle end, thereby facilitating subsequent big data analysis of the vehicle health state and optimization of vehicle performance parameters. Moreover, for vehicles in the test phase or emergency problems of vehicles in actual use by users in the field, developers can remotely maintain and handle related problems, thereby saving the time of copying related information to a storage medium and then forwarding it to developers for problem analysis, improving the processing efficiency of vehicle fault problems. Meanwhile, the hot plug can reduce the power consumption of the vehicle machine operating system.

[0068] In addition, the system takes the vehicle terminal device as a data transmission master device and a mobile terminal device as a data transmission slave device. If the vehicle terminal device and the mobile terminal device are connected through a USB interface, the USB device of the vehicle terminal device can be taken as a USB master device and the mobile phone can be taken as a USB slave device. Then, a driver file developed based on the USB interface and compatible with the iOS system mobile product is loaded to achieve that the vehicle terminal device can share the network of the mobile phone. That is, in a scenario without other networks, the USB master device can share the network of the USB slave device, so that the Linux system can share the network with the iOS device through the interface to realize data exchange transmission and Internet access. Therefore, the system can design the USB network sharing function of the iOS system mobile terminal, so that the vehicle can communicate with the external network to transmit vehicle historical record report log data. Moreover, through the FRP internal network penetration technology, the server backend can directly access the vehicle terminal system to view real-time related parameters and performance parameters of the software system of the vehicle.

[0069] It can be understood that the log data transmission system provided by the above embodiment and the log data transmission method provided by the above embodiment belong to the same concept, wherein the specific manner in which the log data transmission method performs operations has been described in detail in the above method embodiments, which will not be repeated here. In actual application, the functions of the log data transmission system provided by the above embodiment can be completed by different functional modules according to needs, that is, the internal structure of the log data transmission system is divided into different functional modules, and then all or part of the functions of the corresponding functional modules are implemented through the log data transmission method described in the above embodiments, which will not be specifically limited here.

[0070] The embodiments of the present application also provide a computer device, which can include a memory, a processor and a computer program stored in the memory, wherein the processor executes the computer program to enable the computer device to perform the log data transmission method. Figure 1 The steps of the log data transmission method. Figure 4 A structural schematic diagram of a computer device 1000 is shown. Referring to Figure 4 As shown, the computer device 1000 includes a processor 1010, a memory 1020, a power supply 1030, a display unit 1040 and an input unit 1060.

[0071] The processor 1010 is the control center of the computer device 1000, which connects various components through various interfaces and lines, executes computer programs / instructions stored in the memory 1020, performs various functions of the computer device 1000, and thus monitors the computer device 1000 as a whole. In the embodiments of the present application, the processor 1010 executes the log data transmission method when calling the computer program stored in the memory 1020. Figure 1 The steps of the log data transmission method. Optionally, the processor 1010 may include one or more processing units; preferably, the processor 1010 may integrate an application processor and a modem processor, wherein the application processor mainly processes the operating system, user interface, and applications, and the modem processor mainly processes wireless communications. In some embodiments, the processor and memory can be implemented on a single chip, and in some embodiments, they can also be implemented separately on separate chips.

[0072] The memory 1020 may primarily include a program storage area and a data storage area. The program storage area may store an operating system, various applications, and the like; the data storage area may store instruction data and the like generated based on the use of the computer device 1000. Furthermore, the memory 1020 may include a high-speed random access memory and a non-volatile memory, such as at least one disk storage device, a flash memory device, or other non-volatile solid-state storage device.

[0073] The computer device 1000 also includes a power supply 1030 (such as a battery) for supplying power to various components. The power supply can be logically connected to the processor 1010 through a power management system, thereby managing functions such as charging, discharging, and power consumption through the power management system.

[0074] The display unit 1040 can be used to display information input by the user or information provided to the user, as well as various menus of the computer device 1000. In the embodiment of the present application, it is mainly used to display the display interface of each application in the computer device 1000 and objects such as text and pictures displayed on the display interface. The display unit 1040 may include a display panel 1050. The display panel 1050 can be configured in the form of a liquid crystal display (LCD), an organic light-emitting diode (OLED), etc.

[0075] The input unit 1060 can be used to receive information such as numbers or characters input by the user. The input unit 1060 may include a touch panel 1070 and other input devices 1080. The touch panel 1070, also known as a touch screen, can receive user touch operations on or near it (for example, operations performed by the user using a finger, a stylus, or any other suitable object or accessory on or near the touch panel 1070).

[0076] In particular, the touch panel 1070 can detect a user's touch operation, and detect signals resulting from the touch operation, convert the signals into touch coordinates, transmit the touch coordinates to the processor 1010, and receive commands from the processor 1010 and execute the commands. In addition, the touch panel 1070 can be implemented in various types such as a resistive type, a capacitive type, an infrared type, and a surface acoustic wave type. The other input device 1080 can include one or more of a physical keyboard, function keys (such as volume control buttons, power on / off buttons, etc.), a trackball, a mouse, a joystick, etc.

[0077] Of course, the touch panel 1070 can cover the display panel 1050, and when the touch panel 1070 detects a touch operation thereon or in the vicinity thereof, transmit the touch operation to the processor 1010 to determine a type of the touch event, and then the processor 1010 provides a corresponding visual output on the display panel 1050 according to the type of the touch event. Although in the above description, the touch panel 1070 and the display panel 1050 are implemented as two independent components to realize the input and output functions of the computer device 1000, in some embodiments, the touch panel 1070 and the display panel 1050 can be integrated to realize the input and output functions of the computer device 1000. Figure 4

[0078] The computer device 1000 can further include one or more sensors, such as a pressure sensor, a gravity acceleration sensor, a proximity light sensor, etc. Of course, according to the needs in specific applications, the above computer device 1000 can further include a camera and other components.

[0079] The embodiments of the present application also provide a computer readable storage medium, which stores computer programs / instructions, and when the computer programs / instructions are executed by a processor, the above device can perform the steps of the log data transmission method as described in the embodiments of the present application. Figure 1

[0080] Those skilled in the art can understand that, Figure 4 The above is only an example of the computer device, and does not constitute a limitation on the device, which can include more or fewer components than the illustration, or combine certain components, or different components. For the convenience of description, the above parts are divided into modules (or units) according to functions and described respectively. Of course, in the implementation of the present application, the functions of the modules (or units) can be implemented in the same or multiple software or hardware.

[0081] ​​It will be understood by those skilled in the art that the present application may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code. The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be applied to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the functions in the process. Figure 1 a process or multiple processes and / or boxes Figure 1 These computer program instructions can also be stored in a computer-readable memory that can guide a computer or other programmable data processing device to work in a specific way, so that the instructions stored in the computer-readable memory produce a product including the instruction device, which implements the function specified in the process. Figure 1 a process or multiple processes and / or boxes Figure 1 These computer program instructions can also be loaded onto a computer or other programmable data processing device, so that a series of operation steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process in the process. Figure 1 a process or multiple processes and / or boxes Figure 1 A step that specifies a function in one or more boxes.

[0082] It should be understood that although the terms "first," "second," etc. may be used to describe execution programs in the embodiments of this application, these terms are merely used to distinguish one execution program from another. For example, a first execution program may be referred to as a second execution program, and similarly, a second execution program may be referred to as a first execution program without departing from the scope of the embodiments of this application.

[0083] The above embodiments are merely illustrative of the principles and effects of this application and are not intended to limit this application. Anyone skilled in the art may modify or alter the above embodiments without departing from the spirit and scope of this application. Therefore, all equivalent modifications or alterations made by one of ordinary skill in the art without departing from the spirit and technical concepts disclosed in this application shall be covered by the claims of this application.

Claims

1. A log data transmission method, characterized in that: The method comprises the following steps: Obtain the product identification code and supplier identification code of the data transmission interface of the mobile terminal device; Compiling and configuring an operating system kernel for the mobile terminal device based on the product identification code and the vendor identification code, and matching a driver file for the mobile terminal device based on the operating system kernel compilation and configuration result; wherein the operating system kernel compilation and configuration result includes a network sharing configuration for the mobile terminal device; Identify the connection status between the data transmission interface of the mobile terminal device and the data transmission interface of the vehicle-mounted terminal device, and when the connection status is a hot-plug state, dynamically allocate the network sharing address of the mobile terminal device based on the driver file, so that the vehicle-mounted terminal device transmits the target log data to the server according to the network sharing address; wherein, the target log data includes vehicle history record report log data.

2. The log data transmission method according to claim 1, characterized in that: The process of dynamically allocating the network shared address of the mobile terminal device based on the driver file further includes: Cross-compiling the dependencies of the vehicle operating system in sequence using a cross-compilation tool to generate an executable program for the vehicle operating system architecture, which is recorded as a first executable program; wherein the vehicle terminal device is configured with the vehicle operating system; The first execution program is embedded into the vehicle operating system, and a network shared address of the mobile terminal device is dynamically allocated based on the driver file of the mobile terminal device and the first execution program.

3. The log data transmission method according to claim 1, characterized in that: The process of transmitting the target log data to the server according to the network shared address by the vehicle terminal device includes: Download the program source code of the intranet penetration tool, and use a cross-compilation tool to cross-compile and generate an intranet penetration tool execution program for the central processing unit structure, which is recorded as the second execution program; Modify the configuration text file of the intranet penetration tool and run the second execution program in the startup script of the vehicle operating system; and A target log data transmission request is issued to the vehicle-mounted terminal device, and after the network sharing configuration of the mobile terminal device is triggered, the target log data transmission request is responded to by the vehicle-mounted terminal device, and the target log data is transmitted to the server according to the target log data transmission request result and the network sharing address.

4. The log data transmission method according to claim 1, characterized in that: The process of identifying the connection status between the data transmission interface of the mobile terminal device and the data transmission interface of the vehicle-mounted terminal device includes: Capturing the connection action of the mobile terminal device through a rule file pre-set in the vehicle operating system to determine whether the mobile terminal device is connected to the vehicle-mounted terminal device; and After the mobile terminal device is connected to the vehicle-mounted terminal device, identifying whether the mobile terminal device and the vehicle-mounted terminal device are connected via the data transmission interface through the rule file; wherein the data transmission interface includes a universal serial bus interface; and When the mobile terminal device is connected to the vehicle-mounted terminal device via the data transmission interface, it is determined that the connection state between the data transmission interface of the vehicle-mounted terminal device and the data transmission interface of the mobile terminal device is a hot plug state.

5. The log data transmission method according to claim 1, characterized in that: The process of obtaining the product identification code and the supplier identification code of the data transmission interface of the mobile terminal device includes: Obtaining the product identification code and supplier identification code of the data transmission interface of the mobile terminal device by calling a device information query instruction in the vehicle operating system; and / or, By querying the specification sheet of the mobile terminal device in the vehicle operating system, the product identification code and supplier identification code of the data transmission interface of the mobile terminal device are obtained.

6. The log data transmission method according to claim 1 or 3, characterized in that: After the target log data is transmitted to the server, the method further includes: Reading, by the server, hardware device parameter information used to characterize the status of the vehicle hardware device from the target log data, and software system data used to characterize the status of the vehicle software system from the target log data; The current state of the vehicle is determined based on the diagnosis of the hardware device parameter information and the software system data; and the hardware device parameter information and the software system data are used as training data and input into a pre- or real-time established neural network architecture for training to generate an intelligent driving model for driving control of the vehicle.

7. The log data transmission method according to claim 3, characterized in that: If the intranet penetration tool includes a reverse proxy tool, the process of modifying the configuration text file of the reverse proxy tool includes: modifying the internetworking protocol of the reverse proxy tool and modifying the listening port of the reverse proxy tool.

8. A log data transmission system, characterized in that: The system includes: A data acquisition module, used to obtain the product identification code and supplier identification code of the data transmission interface of the mobile terminal device; a driver configuration module, configured to compile and configure an operating system kernel for the mobile terminal device according to the product identification code and the vendor identification code, and match a driver file for the mobile terminal device based on the operating system kernel compilation and configuration result; wherein the operating system kernel compilation and configuration result includes a network sharing configuration for the mobile terminal device; A log data transmission module is used to identify the connection status between the data transmission interface of the mobile terminal device and the data transmission interface of the vehicle-mounted terminal device, and when the connection status is a hot-plug state, dynamically allocates the network sharing address of the mobile terminal device based on the driver file, so that the vehicle-mounted terminal device transmits the target log data to the server according to the network sharing address; wherein, the target log data includes vehicle history record report log data.

9. A computer device, characterized in that: The method comprises a memory, a processor and a computer program stored in the memory, wherein the processor executes the computer program to implement the steps of the log data transmission method according to any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that A computer program is stored thereon, and when the computer program is executed by a processor, the steps of the log data transmission method according to any one of claims 1 to 7 are implemented.

Images