Log data transmission method and system, computer equipment and medium

Abstract

The invention provides a log data transmission method and system, computer equipment and a medium, and the method comprises the steps: obtaining a PID and a VID of a data transmission interface of mobile terminal equipment, matching a drive file of the mobile terminal equipment based on the PID and the VID, and recognizing a connection state of the data transmission interface of the mobile terminal equipment and a data transmission interface of vehicle-mounted terminal equipment, and when the connection state is a hot plug state, dynamically allocating a network sharing address of the mobile terminal equipment based on the driving file, so that the vehicle-mounted terminal equipment transmits the target log data to the server according to the network sharing address. By establishing the network communication connection between the vehicle-mounted terminal equipment and the mobile terminal equipment, the vehicle-mounted terminal equipment can share the network of the mobile terminal equipment in a scene without other networks, so that the vehicle-mounted equipment operating system can share the network with the mobile terminal equipment through the corresponding data transmission interface; therefore, the target log data is transmitted to the server, and data exchange transmission and internet access are realized.

Description

Technical Field

[0001] The present application relates to the technical field of data transmission, and in particular to a log data transmission method and system, computer equipment and medium. Background Art

[0002] The Vehicle History Report (VHR) contains the vehicle's Controller Area Network (CAN) message data and the controller's system log. Uploading VHR to the server for big data analysis can not only monitor the vehicle's health status and optimize the functional defects of the software layer, but also facilitate the better development of the vehicle. However, VHR has not yet been reasonably utilized on most vehicle models. Only vehicles equipped with Ethernet network modules or vehicles with wireless network function modules have the function of uploading VHR-related logs, but the network hardware cost of related vehicles is still at a high stage. Therefore, the vehicle health parameters of most models are not fully utilized. Summary of the invention

[0003] In view of the above-mentioned shortcomings of the prior art, the purpose of the present application is to provide a log data transmission method and system, computer equipment and medium, which are used to solve the technical problems existing in the prior art.

[0004] To achieve the above 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] Compiling and configuring the operating system kernel of the mobile terminal device based on the product identification code and the supplier identification code, and matching the driver file of the mobile terminal device based on the operating system kernel compilation and configuration result; wherein the operating system kernel compilation and configuration result includes the network sharing configuration of the mobile terminal device;

[0007] 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.

[0008] In one 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 includes:

[0009] Using a cross-compilation tool to sequentially cross-compile the dependencies of the vehicle operating system, generating an executable program for the vehicle operating system architecture, recorded as a first executable program; wherein the vehicle terminal device is configured with the vehicle operating system;

[0010] The first execution program is embedded into the vehicle operating system, and a network sharing address of the mobile terminal device is dynamically allocated based on the driver file of the mobile terminal device and the first execution program.

[0011] In one embodiment of the present application, the process of the vehicle-mounted terminal device transmitting the target log data to the server according to the network shared address includes:

[0012] Download the program source code of the intranet penetration tool, and use the 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;

[0013] 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,

[0014] 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 vehicle-mounted terminal device responds to the target log data transmission request, and transmits the target log data to the server according to the target log data transmission request result and the network sharing address.

[0015] In one embodiment of the present application, 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:

[0016] Capturing the connection action of the mobile terminal device through a rule file pre-set in the vehicle operating system, and determining whether the mobile terminal device is connected to the vehicle-mounted terminal device; and

[0017] 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,

[0018] 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.

[0019] In one 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] By calling a device information query instruction in the vehicle operating system, the product identification code and the supplier identification code of the data transmission interface of the mobile terminal device are obtained; and / or,

[0021] By querying the specification sheet of the mobile terminal device in the vehicle operating system, the product identification code and the supplier identification code of the data transmission interface of the mobile terminal device are obtained.

[0022] In one embodiment of the present application, after the target log data is transmitted to the server, the method further includes:

[0023] Reading, through the server, hardware device parameter information used to characterize the status of the vehicle hardware device in the target log data, and reading software system data used to characterize the status of the vehicle software system in the target log data;

[0024] The current state of the vehicle is determined based on the hardware device parameter information and the software system data diagnosis; 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.

[0025] In one 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 interconnection 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, the system comprising:

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

[0028] a driver configuration module, configured to compile and configure the operating system kernel of 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 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.

[0030] The present application also provides a computer device, including a memory, a processor, and a computer program stored in the memory, wherein the processor executes the computer program to implement the steps of any one of the log data transmission methods described above.

[0031] The present application also provides a computer-readable storage medium on which a computer program is stored. When the computer program is executed by a processor, the steps of any one of the log data transmission methods described above are implemented.

[0032] As described above, the present application provides a log data transmission method and system, computer equipment and medium, which have the following beneficial effects: the present application obtains the product identification code and supplier identification code of the data transmission interface of the mobile terminal device, and then compiles and configures the operating system kernel of 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 and configuration result; then identifies 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 the vehicle history record report log data. It can be seen from this that the present application can establish a network communication connection between the vehicle-mounted terminal device and the mobile terminal device, and in the scenario where there is no other network, the vehicle-mounted terminal device can share the network of the mobile terminal device, so that the vehicle-mounted terminal device can share the network 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. Therefore, the present application does not need to set up an additional mobile network module or a wired Ethernet with limited usage scenarios in the vehicle. By utilizing the communication network of the mobile terminal device, the vehicle operating system in the vehicle can communicate with the outside world through the network, so that the server can remotely obtain the vehicle history report log data on the vehicle side, thereby facilitating the subsequent big data analysis of the vehicle health status and optimizing the vehicle performance parameters. Moreover, for vehicles in the testing phase or emergency problems that arise on site when users actually use the vehicle, developers can remotely maintain and handle related issues, thereby saving the time of copying relevant information to the storage medium and then forwarding it to the developer for problem analysis, thereby improving the efficiency of handling vehicle fault problems. In addition, the present application can realize direct access of the server backend to the vehicle-side system through the intranet penetration technology, and then view the real-time relevant parameters of the vehicle and the performance parameters of the software system; at the same time, the power consumption of the vehicle operating system can be reduced through hot plugging. BRIEF DESCRIPTION OF THE DRAWINGS

[0033] Figure 1A flow chart of a log data transmission method provided in an embodiment of the present application;

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

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

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

[0037] The following is an explanation of the embodiments of the present application by specific specific examples, and those skilled in the art can easily understand other advantages and effects of the present application from the content disclosed in this specification. The present application can also be implemented or applied by other different specific embodiments, and the details in this specification can also be based on different viewpoints and applications, without departing from the spirit of the present application. Various modifications or changes are made. It is understood that, in the absence of conflict, the following embodiments and the features in the embodiments can be combined with each other. In addition, it is understood that the illustrations 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 drawings rather than the number, shape and size of the components during the actual implementation. The type, quantity and ratio of each component during its actual implementation can be a random change, and its component layout type may also be more complicated.

[0038] Since the method of uploading diagnostic data of some vehicles to the backend server is not applicable to most models, the VHR of most models has not been more effectively collected and analyzed. However, the USB (Universal Serial Bus, referred to as USB) interface is functionally adapted for most models. If the USB network sharing function is realized, embedded devices that only support USB connection but not 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 backend for analysis and resolution in time, there is no need to recall the faulty vehicle and then extract the relevant data for analysis, which can greatly improve the user 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 in the software. If the function of remote network access to the vehicle system is realized, developers can analyze and optimize related functions in real time and improve development efficiency. In the later vehicle maintenance process, if the function of remote network access to the vehicle system is realized, it is not limited to the detection of core parameters by traditional test equipment, but also the detection and necessary optimization of 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 each vehicle's intelligent driving can be transmitted to the backend, the data set of the training model can be rapidly expanded, which is conducive to the development of intelligent driving technology. Although most types of smartphones currently have the USB network sharing function, it is not plug-and-play in the embedded field.

[0039] In view of the above description, Figure 1 A flow chart of a log data transmission method is shown. Specifically, in an exemplary embodiment, Figure 1 As shown, this embodiment provides a log data transmission method, which includes the following steps:

[0040] S110, obtaining the product identification code (Product ID, PID for short) and the vendor identification code (Vender ID, VID for short) of the data transmission interface of the mobile terminal device. In this embodiment or other embodiments, the mobile terminal device may be a mobile terminal device running an iOS system, referred to as an iOS device. In addition, the mobile terminal device may 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. As an example, the mobile terminal device in this embodiment may be a mobile phone running an iOS system, referred to as an iOS mobile phone. In this embodiment or other embodiments, the data transmission interface includes but is not limited to a Universal Serial Bus (USB) interface.

[0041] S120, compile and configure the operating system kernel of the mobile terminal device based on 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. As an example, if the mobile terminal device in this embodiment is a mobile phone running the iOS system, then this embodiment can configure CONFIG_USB_IPHETH through Menuconfig, and compile the kernel Kernel to generate a driver file ipheth.ko. Among them, Menuconfig is a graphical tool for configuring the kernel or other software components in the Linux system. It provides a text-based graphical user interface, allowing users to 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 when compiling. CONFIG_USB_IPHETH is a configuration option in the Linux kernel, which is used to enable support for iPhone USB network (IP overUSB Ethernet, referred to as IPHETH). When the CONFIG_USB_IPHETH option is enabled and compiled into the kernel, the Linux system configured in the vehicle terminal device can recognize the iOS phone connected via the USB interface, thereby realizing network sharing between the iOS phone and the vehicle terminal device. Kernel is the main component of the operating system, responsible for managing the computer's hardware resources and providing system services, including but not limited to memory management, process management, file system management, and device drivers. Kernel is the interface between the operating system and the hardware, and all software applications must access hardware resources through Kernel.

[0042] S130, identifying the connection status between the data transmission interface of the mobile terminal device and the data transmission interface of the vehicle terminal device, and when the connection status is a hot-swap 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 includes vehicle history report (VHR) log data. In this embodiment or other embodiments, hot swapping (Hot Swap) can also be referred to as hot plugging, which is a method that allows hardware devices to be dynamically inserted or removed during the operation of the operating system.

[0043] It can be seen that, in this embodiment, by establishing a network communication connection between the vehicle-mounted terminal device and the mobile terminal device, in the absence of other networks, the vehicle-mounted terminal device can share the network of the mobile terminal device, so that the vehicle-mounted 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, realizing data exchange transmission and Internet access. Therefore, in this embodiment, there is no need to set up an additional mobile network module or a wired Ethernet with limited usage scenarios in the vehicle. By using the communication network of the mobile terminal device, the vehicle-mounted operating system in the vehicle can communicate with the outside through the network, so that the server can remotely obtain the vehicle history report log record data on the vehicle side, thereby facilitating the subsequent big data analysis of the vehicle health status and optimizing the vehicle performance parameters. Moreover, for vehicles in the test phase or emergency problems that occur on site when users actually use the vehicle, developers can remotely maintain and handle related problems, thereby saving the time of copying relevant information to the storage medium and then forwarding it to the developer to analyze the problem, and improving the efficiency of handling vehicle fault problems. At the same time, the power consumption of the vehicle-mounted operating system can also be reduced by hot plugging.

[0044] In an exemplary embodiment, the process of dynamically allocating the network sharing address of the mobile terminal device based on the driver file also includes: using a cross-compilation tool to sequentially cross-compile the dependencies of the vehicle operating system to generate an executable program for the vehicle operating system architecture, recorded as a first execution program; embedding the first execution program into the vehicle operating system, and dynamically allocating the network sharing address of the mobile terminal device based on the driver file and the first execution program of the mobile terminal device. Among them, the vehicle-mounted terminal device is configured with a vehicle operating system. Cross-compilation refers to the process of compiling a code that can be run on another computer architecture (usually a target machine, Target) on a computer architecture (usually a host machine, Host). As an example, this embodiment can use a cross-compilation tool of the ARM architecture to sequentially 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, and generate an executable program that conforms to the vehicle operating system architecture. Among them, the ARM architecture, whose full name is Advanced RISC Machine, also known as advanced reduced instruction set machine, is a widely used processor architecture.

[0045] Specifically, in the present embodiment, libtool-bin is a general library support script for creating and calling dynamic libraries on different platforms. In the process of software development and compilation, libtool-bin can help developers manage dynamic libraries more conveniently, including operations such as creation, linking and installation. libplist is a library for reading and writing Apple's binary and XML property list formats. libplist-dev is a development kit for libplist, which contains header files and library files required in the development process. It is commonly used in applications and tools that communicate with iOS devices as part of the libimobiledevice stack. libusbmuxd is a library for handling USB multiplexing (muxing) and forwarding, especially communications related to iOS devices. libusbmuxd-dev is a development kit for libusbmuxd, which contains header files and library files required in the development process. It is commonly used to implement the function of communicating with iOS devices via 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 in the development process. 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 native libimobiledevice-dev package is unavailable or incompatible with other libraries. libimobiledevice-glue-dev is the development package of libimobiledevice-glue, which contains the header files and library files required in the development process. It is usually used in conjunction with libimobiledevice to ensure that communication with iOS devices can proceed smoothly. libusb is a user space library for accessing USB devices. It provides basic access capabilities to USB devices, including device enumeration, configuration, interface declaration, data transfer, etc. libusb-1.0-0-dev is the development package of libusb, which contains the header files and library files required in the development process. It is usually used to develop applications or tools that need to communicate with USB devices.

[0046] In an exemplary embodiment, the process of the vehicle terminal device transmitting the target log data to the server according to the network sharing address includes: downloading the program source code of the intranet penetration tool, and using the cross-compilation tool to cross-compile and generate the intranet penetration tool execution program for the central processing unit structure, recorded as the second execution program; modifying the configuration text file of the intranet penetration tool, and running the second execution program in the startup script of the vehicle operating system; and, sending a target log data transmission request to the vehicle terminal device, and after the network sharing configuration of the mobile terminal device is triggered, responding to the target log data transmission request through the vehicle terminal device, and transmitting the target log data to the server according to the target log data transmission request result and the 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 the Internet interconnection protocol of the reverse proxy tool and modifying the listening port of the reverse proxy tool.

[0047] In this embodiment or other embodiments, the intranet penetration tool includes but is not limited to FRP (Fast Reverse Proxy, high-performance reverse proxy, referred to as FRP), ngrok, ngrok, etc. FRP has high performance and low resource usage, can carry multiple requests on a single connection, reduce connection establishment time, and reduce request latency; it also has disconnection reconnection and heartbeat keep-alive, ensuring the stability and reliability of FRP during intranet penetration, and can maintain connection even in poor network conditions; and supports SSL (Secure Socket Layer, Secure Socket Layer, referred to as SSL) / TLS (Transport Layer Security, Secure Transport Layer Protocol, referred to as TLS) encrypted access to ensure the security of data during network transmission and prevent data from being stolen or tampered with. Under the same hardware conditions, FRP may be able to handle more concurrent connections and data transmissions while maintaining lower CPU (Central Processing Unit, Central Processing Unit, referred to as CPU) and memory usage. This is particularly important for embedded applications such as low CPU performance and memory resources; FRP has good open source and does not require additional software licensing fees, and has rich help documents, which helps to quickly solve problems encountered in development. Combined with the characteristics of intranet penetration, the network link between the backend server and the vehicle is established by supporting multiple protocols such as TCP (Transmission Control Protocol, TCP for short), UDP (User Datagram Protocol, UDP for short), HTTP (Hyper Text Transfer Protocol, HTTP for short) and the FRP framework with the characteristics of intranet penetration high-performance reverse proxy. The network link for log data transmission established based on the intranet penetration tool FRP is as follows: Figure 2 As shown. As an example, in this embodiment, if the intranet penetration tool is FRP, this embodiment may also include: downloading the frpc program source code from the FRP official website, cross-compiling the frpc executable program suitable for the CPU architecture, recorded as the second executable program. Modify the configuration text file frpc.ini of the frpc client, including modifying the IP and listening port used by 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. Among them, frpc is the 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 with the FRPS server on the public network.

[0048] In an exemplary embodiment, the process of identifying the connection status between the data transmission interface of a mobile terminal device and the data transmission interface of a vehicle-mounted terminal device includes: capturing the connection action of the mobile terminal device through a rule file pre-set in the vehicle-mounted terminal device operating system, and determining 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 through the rule file whether the mobile terminal device and the vehicle-mounted terminal device are connected through the data transmission interface; wherein the data transmission interface includes a universal serial bus interface; and, when the mobile terminal device and the vehicle-mounted terminal device are connected through the data transmission interface, determining that the connection status between the data transmission interface of the vehicle-mounted terminal device and the data transmission interface of the mobile terminal device is a hot-swappable state.

[0049] Specifically, this embodiment can identify the connection status 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 in 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 operation mode of the system and are a key part of the management and maintenance of the Linux system. The files in the etc directory are usually stored in plain text and can be modified by the user. These files are configuration files necessary for the operation of the system and are used to specify system parameters, network configuration, service configuration, etc. The system administrator can configure and manage the system by modifying these files. In the Linux system, the / etc / udev / rules.d / directory contains files for defining udev rules. These rule files determine how udev should handle these devices when the device is connected to the system. Udev is a tool for managing device files in the Linux system. It runs as a daemon process and manages the device files in the / dev directory by monitoring the uevent issued by the kernel. Udev rules are configuration files for instructing udev on how to handle specific devices. These rules consist of a series of key / value pairs, and the key / value pairs are separated by commas. As an example, a new USB rule file / etc / udev / rules.d / 99-USB-share-network.rules can be created, and the content is as follows: ACTION=="add", SUBSYSTEM=="USB", ATTRS{idVendor}=="Vendor ID", ATTRS{idProduct}=="Product ID", RUN+="user_script.sh". Among them, ACTION=="add" means that the vehicle system captures the action judgment of the USB slave device insertion; SUBSYSTEM=="USB" means whether the inserted device type is a USB type judgment. Then run the driver file ipheth.ko generated by the above embodiment and run the first execution program generated by the cross-compilation of the above embodiment three in the user_script.sh script, so as to realize the dynamic loading of the driver.

[0050] In an exemplary 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 the device information query instruction in the vehicle 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 operating system. As an example, if the mobile terminal device in this embodiment is a mobile phone running the 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. Among them, the lsusb command is used to display the USB device list of the local machine and the detailed information of the USB device, and the USB device information displayed by the lsusb command comes from the corresponding file in the " / proc / bus / usb" directory. As another example, if the mobile terminal device in this embodiment is a mobile phone running the iOS system or other systems, the specification of each mobile phone model can be queried under the Linux system to obtain the PID and VID of the corresponding mobile phone USB interface.

[0051] In an exemplary embodiment, after the target log data is transmitted to the server, the embodiment may further include: reading the hardware device parameter information used to characterize the state of the vehicle hardware device in the target log data through the server, and reading the software system data used to characterize the state of the vehicle software system in the target log data; diagnosing and determining the current state of the vehicle according to the hardware device parameter information and the software system data; and using the hardware device parameter information and the software system data as training data, inputting them into a pre-established or real-time neural network architecture for training, and generating 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 may include: if the hardware device parameter information in the target log data is inconsistent with the hardware device standard parameter information, and / or, if the software system data in the target log data is inconsistent with the software system standard data, it can be determined that the current state of the vehicle is an unhealthy state. As an example, in this embodiment, the process of using hardware device parameter information and software system data as training data to generate an intelligent driving model for driving control of a vehicle can be: using hardware device parameter information and software system data as training data, and then inputting them into neural network structures such as Convolutional Neural Networks (CNN), Deep Neural Networks (DNN), Feedforward Neural Networks (FNN), and Long Short-Term Memory (LSTM) for training to generate an intelligent driving model for driving control of a vehicle. The specific process of the above-mentioned neural network structure training the hardware device parameter information and software system data will not be repeated in this embodiment.

[0052] In summary, the present application provides a log data transmission method, which obtains the product identification code and supplier identification code of the data transmission interface of the mobile terminal device, and then compiles and configures the operating system kernel of 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 and configuration result; then identifies 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 the vehicle history report log data. It can be seen from this that the present method can establish a network communication connection between the vehicle-mounted terminal device and the mobile terminal device, and in the scenario where there is no other network, the vehicle-mounted terminal device can share the network of the mobile terminal device, so that the vehicle-mounted terminal device can share the network 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. Therefore, this method does not require the installation of additional mobile network modules or wired Ethernet with limited usage scenarios in the vehicle. By utilizing the communication network of mobile terminal devices, the vehicle operating system in the vehicle can communicate with the outside world through the network, so that the server can remotely obtain the vehicle history report log data on the vehicle side, thereby facilitating the subsequent big data analysis of the vehicle health status and optimizing the vehicle performance parameters. Moreover, for vehicles in the testing phase or emergency problems that occur on site when users actually use the vehicle, developers can remotely maintain and handle related issues, thereby saving the time of copying relevant information to the storage medium and then forwarding it to the developer for problem analysis, thereby improving the efficiency of handling vehicle fault problems. At the same time, the power consumption of the vehicle operating system can also be reduced by hot plugging.

[0053] In addition, this method uses the vehicle-mounted terminal device as the data transmission master device and the mobile terminal device as the data transmission slave device. If the vehicle-mounted terminal device and the mobile terminal device are connected using a USB interface, the vehicle-side USB device can be used as a USB master device and the mobile phone as a USB slave device. Then, the driver is loaded according to the driver file pre-developed based on the USB interface compatible with the iOS system mobile product, so that the vehicle-mounted terminal device can share the mobile phone end network. That is, in a scenario where there is no other network, 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 this interface, and realize data exchange transmission and Internet access. Therefore, this method can design the USB network sharing function of the iOS system mobile terminal, so that the vehicle can transmit the vehicle history report log data after communicating with the external network. Moreover, through the FRP intranet penetration technology, the server backend can directly access the vehicle-side system, and then view the real-time relevant parameters of the vehicle and the performance parameters of the software system.

[0054] In another exemplary embodiment of the present application, Figure 3 As shown, this embodiment also provides a log data transmission system, including:

[0055] The data acquisition module 310 is used to obtain the product identification code and supplier identification code of the data transmission interface of the mobile terminal device. In this embodiment or other embodiments, the mobile terminal device may be a mobile terminal device running the iOS system, referred to as an iOS device. In addition, the mobile terminal device may 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. As an example, the mobile terminal device in this embodiment may be a mobile phone running the iOS system, referred to as an iOS phone. In this embodiment or other embodiments, the data transmission interface includes but is not limited to a USB interface.

[0056] The driver configuration module 320 is used to compile and configure the operating system kernel of 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; 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 this embodiment is a mobile phone running the iOS system, this embodiment can configure CONFIG_USB_IPHETH through Menuconfig, and compile the kernel Kernel to generate a driver file ipheth.ko. Among them, Menuconfig is a graphical tool for configuring the kernel or other software components in the Linux system. It provides a text-based graphical user interface, allowing users to 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 when compiling. CONFIG_USB_IPHETH is a configuration option in the Linux kernel, which is used to enable support for iPhoneUSB network (IP over USB Ethernet, referred to as IPHETH). When the CONFIG_USB_IPHETH option is enabled and compiled into the kernel, the Linux system configured in the vehicle terminal device can recognize the iOS phone connected via the USB interface, thereby realizing network sharing between the iOS phone and the vehicle terminal device. Kernel is the main component of the operating system, responsible for managing the computer's hardware resources and providing system services, including but not limited to memory management, process management, file system management, and device drivers. Kernel is the interface between the operating system and the hardware, and all software applications must access hardware resources through Kernel.

[0057] The log data transmission module 330 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 terminal device, and when the connection status is hot plug, dynamically allocate 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 includes the vehicle history report (VHR) log data. In this embodiment or other embodiments, hot swapping can also be called live plugging, which is a method that allows hardware devices to be dynamically inserted or removed during the operation of the operating system.

[0058] It can be seen that, in this embodiment, by establishing a network communication connection between the vehicle-mounted terminal device and the mobile terminal device, in the absence of other networks, the vehicle-mounted terminal device can share the network of the mobile terminal device, so that the vehicle-mounted 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, realizing data exchange transmission and Internet access. Therefore, in this embodiment, there is no need to set up an additional mobile network module or a wired Ethernet with limited usage scenarios in the vehicle. By using the communication network of the mobile terminal device, the vehicle-mounted operating system in the vehicle can communicate with the outside through the network, so that the server can remotely obtain the vehicle history report log record data on the vehicle side, thereby facilitating the subsequent big data analysis of the vehicle health status and optimizing the vehicle performance parameters. Moreover, for vehicles in the test phase or emergency problems that occur on site when users actually use the vehicle, developers can remotely maintain and handle related problems, thereby saving the time of copying relevant information to the storage medium and then forwarding it to the developer to analyze the problem, and improving the efficiency of handling vehicle fault problems. At the same time, the power consumption of the vehicle-mounted operating system can also be reduced by hot plugging.

[0059] In an exemplary embodiment, the process of dynamically allocating the network sharing address of the mobile terminal device based on the driver file also includes: using a cross-compilation tool to sequentially cross-compile the dependencies of the vehicle operating system to generate an executable program for the vehicle operating system architecture, recorded as a first execution program; embedding the first execution program into the vehicle operating system, and dynamically allocating the network sharing address of the mobile terminal device based on the driver file and the first execution program of the mobile terminal device. Among them, the vehicle-mounted terminal device is configured with a vehicle operating system. Cross-compilation refers to the process of compiling a code that can be run on another computer architecture (usually a target machine, Target) on a computer architecture (usually a host machine, Host). As an example, this embodiment can use a cross-compilation tool of the ARM architecture to sequentially 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, and generate an executable program that conforms to the vehicle operating system architecture. Among them, the ARM architecture, whose full name is Advanced RISC Machine, also known as advanced reduced instruction set machine, is a widely used processor architecture.

[0060] Specifically, in the present embodiment, libtool-bin is a general library support script for creating and calling dynamic libraries on different platforms. In the process of software development and compilation, libtool-bin can help developers manage dynamic libraries more conveniently, including operations such as creation, linking and installation. libplist is a library for reading and writing Apple's binary and XML property list formats. libplist-dev is a development kit for libplist, which contains header files and library files required in the development process. It is commonly used in applications and tools that communicate with iOS devices as part of the libimobiledevice stack. libusbmuxd is a library for handling USB multiplexing (muxing) and forwarding, especially communications related to iOS devices. libusbmuxd-dev is a development kit for libusbmuxd, which contains header files and library files required in the development process. It is commonly used to implement the function of communicating with iOS devices via 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 in the development process. 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 native libimobiledevice-dev package is unavailable or incompatible with other libraries. libimobiledevice-glue-dev is the development package of libimobiledevice-glue, which contains the header files and library files required in the development process. It is usually used in conjunction with libimobiledevice to ensure that communication with iOS devices can proceed smoothly. libusb is a user space library for accessing USB devices. It provides basic access capabilities to USB devices, including device enumeration, configuration, interface declaration, data transfer, etc. libusb-1.0-0-dev is the development package of libusb, which contains the header files and library files required in the development process. It is usually used to develop applications or tools that need to communicate with USB devices.

[0061] In an exemplary embodiment, the process of the vehicle terminal device transmitting the target log data to the server according to the network sharing address includes: downloading the program source code of the intranet penetration tool, and using the cross-compilation tool to cross-compile and generate the intranet penetration tool execution program for the central processing unit structure, recorded as the second execution program; modifying the configuration text file of the intranet penetration tool, and running the second execution program in the startup script of the vehicle operating system; and, sending a target log data transmission request to the vehicle terminal device, and after the network sharing configuration of the mobile terminal device is triggered, responding to the target log data transmission request through the vehicle terminal device, and transmitting the target log data to the server according to the target log data transmission request result and the 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 the Internet interconnection protocol of the reverse proxy tool and modifying the listening port of the reverse proxy tool.

[0062] In this embodiment or other embodiments, the intranet penetration tool includes but is not limited to FRP (Fast Reverse Proxy, high-performance reverse proxy, referred to as FRP), ngrok, ngrok, etc. FRP has high performance and low resource usage, can carry multiple requests on a single connection, reduce connection establishment time, and reduce request latency; it also has disconnection reconnection and heartbeat keep-alive, ensuring the stability and reliability of FRP during intranet penetration, and can maintain connection even in poor network conditions; and supports SSL (Secure Socket Layer, Secure Socket Layer, referred to as SSL) / TLS (Transport Layer Security, Secure Transport Layer Protocol, referred to as TLS) encrypted access to ensure the security of data during network transmission and prevent data from being stolen or tampered with. Under the same hardware conditions, FRP may be able to handle more concurrent connections and data transmissions while maintaining lower CPU (Central Processing Unit, Central Processing Unit, referred to as CPU) and memory usage. This is particularly important for embedded applications such as low CPU performance and memory resources; FRP has good open source and does not require additional software licensing fees, and has rich help documents, which helps to quickly solve problems encountered in development. Combined with the characteristics of intranet penetration, the network link between the backend server and the vehicle is established by supporting multiple protocols such as TCP (Transmission Control Protocol, TCP for short), UDP (User Datagram Protocol, UDP for short), HTTP (Hyper Text Transfer Protocol, HTTP for short) and the FRP framework with the characteristics of intranet penetration high-performance reverse proxy. The network link for log data transmission established based on the intranet penetration tool FRP is as follows: Figure 2 As shown. As an example, in this embodiment, if the intranet penetration tool is FRP, this embodiment may also include: downloading the frpc program source code from the FRP official website, cross-compiling the frpc executable program suitable for the CPU architecture, recorded as the second executable program. Modify the configuration text file frpc.ini of the frpc client, including modifying the IP and listening port used by 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. Among them, frpc is the 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 with the FRPS server on the public network.

[0063] In an exemplary embodiment, the process of identifying the connection status between the data transmission interface of a mobile terminal device and the data transmission interface of a vehicle-mounted terminal device includes: capturing the connection action of the mobile terminal device through a rule file pre-set in the vehicle-mounted terminal device operating system, and determining 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 through the rule file whether the mobile terminal device and the vehicle-mounted terminal device are connected through the data transmission interface; wherein the data transmission interface includes a universal serial bus interface; and, when the mobile terminal device and the vehicle-mounted terminal device are connected through the data transmission interface, determining that the connection status between the data transmission interface of the vehicle-mounted terminal device and the data transmission interface of the mobile terminal device is a hot-swappable state.

[0064] Specifically, this embodiment can identify the connection status 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 in 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 operation mode of the system and are a key part of the management and maintenance of the Linux system. The files in the etc directory are usually stored in plain text and can be modified by the user. These files are configuration files necessary for the operation of the system and are used to specify system parameters, network configuration, service configuration, etc. The system administrator can configure and manage the system by modifying these files. In the Linux system, the / etc / udev / rules.d / directory contains files for defining udev rules. These rule files determine how udev should handle these devices when the device is connected to the system. Udev is a tool for managing device files in the Linux system. It runs as a daemon process and manages the device files in the / dev directory by monitoring the uevent issued by the kernel. Udev rules are configuration files for instructing udev on how to handle specific devices. These rules consist of a series of key / value pairs, and the key / value pairs are separated by commas. As an example, a new USB rule file / etc / udev / rules.d / 99-USB-share-network.rules can be created, and the content is as follows: ACTION=="add", SUBSYSTEM=="USB", ATTRS{idVendor}=="Vendor ID", ATTRS{idProduct}=="Product ID", RUN+="user_script.sh". Among them, ACTION=="add" means that the vehicle system captures the action judgment of the USB slave device insertion; SUBSYSTEM=="USB" means whether the inserted device type is a USB type judgment. Then run the driver file ipheth.ko generated by the above embodiment and run the first execution program generated by the cross-compilation of the above embodiment three in the user_script.sh script, so as to realize the dynamic loading of the driver.

[0065] In an exemplary 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 the device information query instruction in the vehicle 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 operating system. As an example, if the mobile terminal device in this embodiment is a mobile phone running the 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. Among them, the lsusb command is used to display the USB device list of the local machine and the detailed information of the USB device, and the USB device information displayed by the lsusb command comes from the corresponding file in the " / proc / bus / usb" directory. As another example, if the mobile terminal device in this embodiment is a mobile phone running the iOS system or other systems, the specification of each mobile phone model can be queried under the Linux system to obtain the PID and VID of the corresponding mobile phone USB interface.

[0066] In an exemplary embodiment, after the target log data is transmitted to the server, the embodiment may further include: reading the hardware device parameter information used to characterize the state of the vehicle hardware device in the target log data through the server, and reading the software system data used to characterize the state of the vehicle software system in the target log data; diagnosing and determining the current state of the vehicle according to the hardware device parameter information and the software system data; and using the hardware device parameter information and the software system data as training data, inputting them into a pre-established or real-time neural network architecture for training, and generating 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 may include: if the hardware device parameter information in the target log data is inconsistent with the hardware device standard parameter information, and / or, if the software system data in the target log data is inconsistent with the software system standard data, it can be determined that the current state of the vehicle is an unhealthy state. As an example, in this embodiment, the process of using hardware device parameter information and software system data as training data to generate an intelligent driving model for driving control of a vehicle can be: using hardware device parameter information and software system data as training data, and then inputting them into neural network structures such as Convolutional Neural Networks (CNN), Deep Neural Networks (DNN), Feedforward Neural Networks (FNN), and Long Short-Term Memory (LSTM) for training to generate an intelligent driving model for driving control of a vehicle. The specific process of the above-mentioned neural network structure training the hardware device parameter information and software system data will not be repeated in this embodiment.

[0067] In summary, the present application provides a log data transmission system, which obtains the product identification code and supplier identification code of the data transmission interface of the mobile terminal device, and then compiles and configures the operating system kernel of 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 identifies 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 the vehicle history record report log data. It can be seen from this that the present system can establish a network communication connection between the vehicle-mounted terminal device and the mobile terminal device. In the scenario where there is no other network, the vehicle-mounted terminal device can share the network of the mobile terminal device, so that the vehicle-mounted terminal device can share the network 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. Therefore, this system does not need to set up additional mobile network modules or wired Ethernet with limited usage scenarios in the vehicle. By using the communication network of mobile terminal devices, the vehicle operating system in the vehicle can communicate with the outside world, so that the server can remotely obtain the vehicle history report log data on the vehicle side, thereby facilitating the subsequent big data analysis of the vehicle health status and optimizing the vehicle performance parameters. Moreover, for vehicles in the testing phase or emergency problems that occur on site when users actually use the vehicle, developers can remotely maintain and handle related problems, thereby saving the time of copying relevant information to storage media and then forwarding it to developers for problem analysis, improving the efficiency of handling vehicle fault problems. At the same time, the power consumption of the vehicle operating system can be reduced by hot plugging.

[0068] In addition, this system uses the vehicle-mounted terminal device as the data transmission master device and the mobile terminal device as the data transmission slave device. If the vehicle-mounted terminal device and the mobile terminal device are connected using a USB interface, the vehicle-side USB device can be used as the USB master device and the mobile phone as the USB slave device. Then, the driver file pre-developed based on the USB interface compatible with iOS system mobile products is loaded to achieve the vehicle-mounted terminal device can share the mobile phone end network. That is, in the scenario where there is no other network, 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 this interface to achieve data exchange transmission and Internet access. Therefore, this system can design the USB network sharing function of the iOS system mobile terminal, so that the vehicle can transmit the vehicle history report log data after communicating with the external network. Moreover, through the FRP intranet penetration technology, the server backend can directly access the vehicle-side system, and then view the real-time relevant parameters of the vehicle and the performance parameters of the software system.

[0069] It can be understood that the log data transmission system provided in the above embodiment and the log data transmission method provided in the above embodiment belong to the same concept, wherein the specific manner in which the log data transmission method performs the operation has been described in detail in the above method embodiment, and will not be repeated here. In practical applications, the log data transmission system provided in the above embodiment can distribute the above functions to different functional modules as needed, that is, divide the internal structure of the log data transmission system into different functional modules, and then implement all or part of the functions of the corresponding functional modules through the log data transmission method described in the above embodiment, and this is not specifically limited here.

[0070] The present application also provides a computer device, which may include a memory, a processor, and a computer program stored in the memory, wherein the processor executes the computer program so that the computer device executes Figure 1 The steps of the log data transmission method. Figure 4 FIG. 1 is a schematic diagram showing a structure of a computer device 1000. 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. It uses various interfaces and lines to connect various components, and executes various functions of the computer device 1000 by running or executing computer programs / instructions stored in the memory 1020, thereby monitoring the computer device 1000 as a whole. In the embodiment of the present application, when the processor 1010 calls the computer program stored in the memory 1020, the following is executed: 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 application, etc., and the modem processor mainly processes wireless communication. In some embodiments, the processor and memory may be implemented on a single chip, and in some embodiments, they may also be implemented separately on separate chips.

[0072] The memory 1020 may mainly include a program storage area and a data storage area, wherein the program storage area may store an operating system, various applications, etc.; the data storage area may store instruction data, etc. created according to the use of the computer device 1000. In addition, the memory 1020 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, or other non-volatile solid-state storage devices, etc.

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

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

[0075] The input unit 1060 may 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, may collect touch operations of the user on or near it (such as operations of the user using a finger, a stylus, or any other suitable object or accessory on or near the touch panel 1070).

[0076] Specifically, the touch panel 1070 can detect the user's touch operation, detect the signal brought by the touch operation, convert these signals into touch point coordinates, send them to the processor 1010, and receive and execute the command sent by the processor 1010. In addition, the touch panel 1070 can be implemented in various types such as resistive, capacitive, infrared and surface acoustic wave. Other input devices 1080 can include but are not limited to one or more of a physical keyboard, function keys (such as volume control keys, power on / off keys, etc.), a trackball, a mouse, a joystick, etc.

[0077] Of course, the touch panel 1070 can cover the display panel 1050. When the touch panel 1070 detects a touch operation on or near it, it is transmitted to the processor 1010 to determine the type of touch event, and then the processor 1010 provides a corresponding visual output on the display panel 1050 according to the type of touch event. Figure 4 In the embodiment, the touch panel 1070 and the display panel 1050 are two independent components to implement the input and output functions of the computer device 1000, but in some embodiments, the touch panel 1070 and the display panel 1050 can be integrated to implement the input and output functions of the computer device 1000.

[0078] The computer device 1000 may 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 of specific applications, the computer device 1000 may also include other components such as a camera.

[0079] The embodiment of the present application also provides a computer-readable storage medium, in which a computer program / instruction is stored. When the computer program / instruction is executed by a processor, the above-mentioned device can perform the above-mentioned Figure 1 The steps of the log data transmission method.

[0080] It can be understood by those skilled in the art that Figure 4 This is only an example of a computer device and does not constitute a limitation on the device. The device may include more or fewer components than shown in the figure, or combine certain components, or different components. For the convenience of description, the above parts are divided into modules (or units) according to their functions and described separately. Of course, when implementing this application, the functions of each module (or unit) can be implemented in the same or multiple software or hardware.

[0081] Those skilled in the art will appreciate 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, and it should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the 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 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 an instruction device, which implements the functions 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, so that the instructions executed on the computer or other programmable device provide for implementing the process in the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0082] It is understood that, although the terms first, second, etc. may be used to describe execution programs, etc. in the embodiments of the present application, these terms are only used to distinguish execution programs from each other. For example, without departing from the scope of the embodiments of the present application, the first execution program may also be referred to as the second execution program, and similarly, the second execution program may also be referred to as the first execution program.

[0083] The above embodiments are merely illustrative of the principles and effects of the present application and are not intended to limit the present application. Anyone familiar with the technology may modify or change the above embodiments without violating the spirit and scope of the present application. Therefore, all equivalent modifications or changes made by a person of ordinary skill in the art without departing from the spirit and technical ideas disclosed in the present application shall still be covered by the claims of the present application.

Claims

1. A log data transmission method, characterized in that: The method comprises the following steps: Obtaining a product identification code and a supplier identification code of a data transmission interface of a mobile terminal device; Compiling and configuring the operating system kernel of the mobile terminal device based on the product identification code and the supplier identification code, and matching the driver file of the mobile terminal device based on the operating system kernel compilation and configuration result; wherein the operating system kernel compilation and configuration result includes the network sharing configuration of 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 sharing address of the mobile terminal device based on the driver file also includes: Using a cross-compilation tool to sequentially cross-compile the dependencies of the vehicle operating system, generating an executable program for the vehicle operating system architecture, 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 sharing 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 sharing address by the vehicle terminal device includes: Download the program source code of the intranet penetration tool, and use the 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 vehicle-mounted terminal device responds to the target log data transmission request, and transmits the target log data 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, and determining 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: By calling a device information query instruction in the vehicle operating system, the product identification code and the supplier identification code of the data transmission interface of the mobile terminal device are obtained; and / or, By querying the specification sheet of the mobile terminal device in the vehicle operating system, the product identification code and the 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, through the server, hardware device parameter information used to characterize the status of the vehicle hardware device in the target log data, and software system data used to characterize the status of the vehicle software system in the target log data; The current state of the vehicle is determined based on the hardware device parameter information and the software system data diagnosis; 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 Internet interconnection 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 comprises: A data acquisition module, used to obtain a product identification code and a supplier identification code of a data transmission interface of a mobile terminal device; a driver configuration module, configured to compile and configure the operating system kernel of 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; 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 described in any one of claims 1 to 7 are implemented.

Images