Vehicle communication method and device, automobile and storage medium
By obtaining terminal identification information and loading drivers, the communication connection between the vehicle and the target server is achieved, the problem of insufficient communication function of automobile network is solved, data transmission efficiency is improved, and the development of intelligent driving technology is supported.
Patent Information
- Application Number
- CN202410984476.7
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-07-22
- Publication Date
- 2024-11-22
AI Technical Summary
Existing cars lack wireless network modules and cannot easily upload vehicle operation information, resulting in low efficiency in diagnostic data collection and analysis, affecting the development of automobile health monitoring and intelligent driving technology.
By receiving network sharing requests sent by the terminal, obtaining the terminal's identification information, connecting to the target interface, obtaining the driver file and the target server address, loading the driver to realize the communication connection between the vehicle and the target server, and optimizing the network communication function.
Without the need to be equipped with a wireless network module, the car can realize network communication, timely transmit data and historical record and report logs, improve the efficiency of vehicle network communication, and support intelligent driving data transmission and performance optimization.
Smart Images

Figure CN119012162A_ABST
Abstract
Description
Technical Field
[0001] The embodiments of the present invention relate to the field of automobile technology, and in particular to a vehicle communication method, a vehicle communication device, a vehicle and a storage medium. Background Art
[0002] At present, most cars are not equipped with wireless network modules, and it is not convenient to connect to the network to upload the information recorded during the operation of the car to the server for analysis. For example, the vehicle history report (VHR) log is an important log for recording vehicle failures, operating indicators and other information. Currently, only on models that are adapted to wireless network modules can VHR be uploaded to a remote server through the network, and then the health of the car can be monitored and upgraded and the functions of defects can be optimized according to VHR. If a model without a wireless network module fails, it can only be recalled and VHR data can be obtained, and the related network hardware and traffic costs are high. Therefore, the VHR diagnostic information of the car is not limited to the hardware equipment parameter information and important data of the software system uploaded to the server. Efficient big data analysis is conducive to the better development of the car.
[0003] At present, because the method of uploading the diagnostic data of relevant vehicles to the backend server is not applicable to most models, VHR data has not been collected and analyzed more effectively. In particular, if the user's on-site problems can be transmitted to the backend for analysis and resolution in a timely manner, it can greatly improve the user experience and the optimization efficiency of vehicle performance. Especially in the stage of rapid development of intelligent driving technology, if the training data of each car's intelligent driving can be transmitted to the backend, the entire training model can be rapidly expanded through a large number of data sets, which will be conducive to promoting the development of intelligent driving technology.
[0004] Therefore, how to optimize the car's networking communication function to facilitate the transmission of vehicle data has become a pressing issue that needs to be resolved. Summary of the invention
[0005] In view of this, in order to solve the above technical problems or part of the technical problems, an embodiment of the present invention provides a vehicle communication method, device, vehicle and storage medium.
[0006] In a first aspect, an embodiment of the present invention provides a vehicle communication method, including:
[0007] When receiving a network sharing request sent by a terminal, obtaining identification information of the terminal, and connecting the vehicle to the terminal through a target interface;
[0008] Obtaining a driver file corresponding to the identification information, and obtaining a target address of a target server corresponding to the vehicle;
[0009] After the driver program in the driver file is loaded, the vehicle is controlled to communicate with the target server according to the target address and the driver program.
[0010] In a possible implementation manner, the acquiring identification information of the terminal includes:
[0011] determining whether the vehicle is connected to the terminal through the target interface;
[0012] If yes, obtaining the supplier identification code and product identification code of the terminal as the identification information;
[0013] If not, a prompt message is sent to the terminal, so as to prompt the terminal to switch the connection mode through the prompt message.
[0014] In a possible implementation, the driver file is generated in the following manner:
[0015] Obtain identification information corresponding to multiple terminals;
[0016] Adding each identification information to the source code of the embedded system of the vehicle, and modifying the embedded system configuration file;
[0017] After modification, the kernel of the embedded system is compiled to generate a driver file corresponding to each identification information.
[0018] In a possible implementation, the acquiring the driver file corresponding to the identification information includes:
[0019] Obtaining a rule file in the embedded system;
[0020] The driver file corresponding to the identification information is acquired according to the target field in the rule file, and the identification information and the driver file correspond one to one.
[0021] In a possible implementation, the rule file is generated in the following manner:
[0022] The first field is set to determine whether the terminal is connected to the vehicle, the second field is set to determine whether the terminal is connected through a target interface, the third field is set to the identification information, and the fourth field is set to load the driver file;
[0023] The rule file is generated according to the first field, the second field, the third field and the fourth field.
[0024] In a possible implementation, controlling the vehicle to communicate with the target server according to the target address and the driver includes:
[0025] Loading the driver and installing a target application corresponding to the vehicle;
[0026] Configuring a configuration file of the target application according to the target address;
[0027] A network link is established between the vehicle and the target server according to the configured target application program to establish a communication connection via the network link.
[0028] In a possible implementation manner, after communicating with the target server according to the target address, the method further includes:
[0029] Obtaining a history report log of the vehicle;
[0030] sending the history report log to the target server;
[0031] When a control instruction returned for the history report log is received, the vehicle is controlled according to the control instruction.
[0032] In a second aspect, an embodiment of the present invention provides a communication device for a vehicle, comprising:
[0033] A first acquisition module, configured to acquire identification information of a terminal when receiving a network sharing request sent by the terminal, the vehicle being connected to the terminal via a target interface;
[0034] A second acquisition module is used to acquire a driver file corresponding to the identification information and a target address of a target server corresponding to the vehicle;
[0035] The control module is used to control the communication connection between the vehicle and the target server according to the target address and the driver program after loading the driver program in the driver file.
[0036] In a third aspect, an embodiment of the present invention provides a car, comprising: a processor and a memory, wherein the processor is used to execute a vehicle communication program stored in the memory to implement the vehicle communication method described in any one of the first aspects above.
[0037] In a fourth aspect, an embodiment of the present invention provides a storage medium, wherein the storage medium stores one or more programs, and the one or more programs can be executed by one or more processors to implement the vehicle communication method described in any one of the first aspects above.
[0038] The vehicle communication scheme provided by the embodiment of the present invention obtains the identification information of the terminal when receiving a network sharing request sent by the terminal, and the vehicle is connected to the terminal through a target interface; obtains the driver file corresponding to the identification information, and obtains the target address of the target server corresponding to the vehicle; after loading the driver in the driver file, the vehicle is controlled to communicate with the target server according to the target address and the driver. Therefore, the corresponding driver and target address can be determined by obtaining the identification information of the terminal connected to the vehicle to control the communication connection between the vehicle and the server, so that the automobile system can communicate with the external network, optimizes the vehicle network communication function, and can communicate with the network without the vehicle being equipped with a wireless network module. The vehicle driving data and VHR can be sent to the server in a timely manner, which improves the efficiency of vehicle network communication. BRIEF DESCRIPTION OF THE DRAWINGS
[0039] Figure 1 A schematic flow chart of a vehicle communication method provided by an embodiment of the present invention;
[0040] Figure 2 A schematic flow chart of another vehicle communication method provided by an embodiment of the present invention;
[0041] Figure 3 A schematic diagram of the structure of a vehicle communication system provided by an embodiment of the present invention;
[0042] Figure 4 A schematic diagram of the structure of a vehicle communication device provided by an embodiment of the present invention;
[0043] Figure 5 A schematic structural diagram of a car provided by an embodiment of the present invention. DETAILED DESCRIPTION
[0044] In order to make the purpose, technical solution and advantages of the embodiments of the present invention clearer, the technical solution in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.
[0045] To facilitate understanding of the embodiments of the present invention, specific embodiments will be further explained below in conjunction with the accompanying drawings. The embodiments do not constitute a limitation on the embodiments of the present invention.
[0046] Figure 1 A flow chart of a vehicle communication method provided by an embodiment of the present invention is shown as follows: Figure 1 As shown, the method specifically includes:
[0047] S11. When a network sharing request sent by a terminal is received, identification information of the terminal is obtained, and the vehicle is connected to the terminal through a target interface.
[0048] The vehicle communication method provided by the embodiment of the present invention is applied to automobiles, which may include but are not limited to: new energy vehicles and fuel vehicles, etc. The method can be implemented through the control system of the automobile, and the control system can be an embedded system such as a Linux system. Specifically, the corresponding driver and target address are determined by obtaining the identification information of the terminal connected to the vehicle to control the communication connection between the vehicle and the server, so that the automobile system can communicate with the external network.
[0049] In this embodiment, the terminal can be a mobile phone, tablet computer and other devices. The terminal has a target interface and has Internet communication function. The vehicle and the terminal can be connected through the target interface. The target interface can be a USB interface. The terminal is inserted into the USB interface of the vehicle, and the USB device of the vehicle is used as the USB host. The terminal is used as the USB slave. The user can choose whether to share the network with the vehicle at present on the terminal. When the network sharing is determined, a network sharing request is sent to the vehicle. At this time, the vehicle obtains the identification information of the connected terminal. The identification information can represent the model and brand of the device. The acquisition method can include but is not limited to obtaining it through the lsusb query command under the Linux system, or obtaining it by querying the specification sheets of each terminal model.
[0050] S12: Obtain a driver file corresponding to the identification information, and obtain a target address of a target server corresponding to the vehicle.
[0051] In this embodiment, a remote network driver interface specification (RNDIS) driver compatible with various terminal models is pre-developed to achieve a shared terminal network. RNDIS is a driver framework that implements network communication between a USB host and a USB slave. In a scenario where there is no other network, the USB host can share the network of the USB slave, thereby achieving a shared network connection. The protocol used is mainly Ethernet over USB (Ethernet based on USB). Each identification information is pre-set with a corresponding driver file, which includes a driver program for controlling the vehicle shared terminal network. After the identification information is obtained, the driver file corresponding to the identification information is obtained, and the target server that the vehicle needs to communicate is pre-set. The target server can obtain and process the information sent by the vehicle (for example, VHR log). When it is necessary to connect to the server, the IP address of the target server corresponding to the vehicle is determined as the target address.
[0052] S13, after loading the driver program in the driver file, controlling the vehicle to communicate with the target server according to the target address and the driver program.
[0053] In this embodiment, the driver program in the driver file is loaded, and the system's DHCP command is executed to obtain the target address. The DHCP command is used to configure and manage the Dynamic Host Configuration Protocol (DHCP) server and client, allowing the vehicle to automatically obtain the corresponding IP address and other network configuration information, and control the vehicle to establish a communication connection with the target server based on the obtained driver program and the obtained IP address.
[0054] Specifically, download the target application (for example, a high-performance reverse proxy framework (Fast Reverse Proxy, frp)), set the network configuration information such as the IP used and the listening port of the target server corresponding to the vehicle by modifying the configuration file of the target application, establish a network link between the vehicle and the target application through the target application, and the vehicle can communicate with the target server.
[0055] The vehicle communication method provided by the embodiment of the present invention obtains the identification information of the terminal when receiving a network sharing request sent by the terminal, and the vehicle is connected to the terminal through a target interface; obtains the driver file corresponding to the identification information, and obtains the target address of the target server corresponding to the vehicle; after loading the driver in the driver file, the vehicle is controlled to communicate with the target server according to the target address and the driver. Therefore, the corresponding driver and target address can be determined by obtaining the identification information of the terminal connected to the vehicle to control the communication connection between the vehicle and the server, so that the automobile system can communicate with the external network, optimizes the vehicle network communication function, and can communicate with the network without the vehicle being equipped with a wireless network module. The vehicle driving data and VHR can be sent to the server in a timely manner, which improves the efficiency of vehicle network communication.
[0056] Figure 2 A flow chart of another vehicle communication method provided by an embodiment of the present invention is shown as follows: Figure 2 As shown, the method specifically includes:
[0057] S21. When receiving a network sharing request sent by a terminal, determine whether the vehicle and the terminal are connected through a target interface; if so, obtain the supplier identification code and product identification code of the terminal as identification information; if not, send a prompt message to the terminal to prompt the terminal to switch the connection mode through the prompt message.
[0058] In this embodiment, the terminal can be a mobile phone device of different models from different manufacturers. When the terminal establishes a connection with the vehicle, it can send a network sharing request to the vehicle so that the vehicle can communicate and connect with the target server through the terminal's network. When the vehicle receives the network sharing request sent by the terminal, it determines whether the current vehicle is connected to the terminal through the target interface, which is a USB interface. If so, the terminal's supplier identification code (ProductID, PID) and product identification code (VendorID, VID) are obtained as identification information. If not, a prompt message is sent to the terminal, which can be displayed on the terminal to prompt the user that the current connection method cannot be used for network sharing, and prompt the user to adjust the current connection method to connect through the target interface.
[0059] S22, obtaining a rule file in the embedded system; obtaining a driver file corresponding to the identification information according to a target field in the rule file, and obtaining a target address of a target server corresponding to the vehicle.
[0060] In this embodiment, the control system in the vehicle is a Linux system, a rule file is pre-configured, and driver files corresponding to different identification information are set. After the identification information of the terminal is obtained, the driver file is obtained according to the target field preset in the rule file. At the same time, the target address of the target server that needs to be connected for communication is obtained.
[0061] The rule file is generated in the following way:
[0062] The first field is set to determine whether the terminal is connected to the vehicle, the second field is set to determine whether the terminal is connected through the target interface, the third field is set to the identification information, and the fourth field is set to load the driver file; a rule file is generated according to the first field, the second field, the third field and the fourth field.
[0063] Specifically, the mechanism of hot plugging implemented by the Linux operating system is analyzed. In the startup process, the implementation through the user device udev rule is a widely used solution. The specific operation is to modify the rules file involved in USB hot plugging in the etc directory. When the operating system detects the hot plugging of the USB device, the user-designed program is executed. For example, a new rule file of USB with a lower priority is: / etc / udev / rules.d / 99-usb-share-network.rules. The content of the rule file is as follows: ACTION=="add", SUBSYSTEM=="usb", ATTRS{idVendor}=="your vendor ID", ATTRS{idProduct}=="your product ID", RUN+="user_script.sh". Among them, the first field is ACTION=="add", which means that the system captures the action judgment of USB device insertion, that is, whether the USB interface detects that a device is inserted; the second field is SUBSYSTEM=="usb", which means whether the inserted device is a USB type judgment, that is, whether the currently inserted device is a device that can use USB. The third field is: ATTRS{idVendor}=="your supplier ID", ATTRS{idProduct}=="your product ID", which is used to obtain the identification information of the currently connected terminal, determine the fourth field as the target field, and the fourth field is user_script.sh, load the driver files corresponding to different identification information in the user_script.sh script, and then realize the dynamic loading of RNDIS driver. And execute the dhcp system command to realize the dynamic allocation of IP.
[0064] Among them, the driver files corresponding to different identification information are pre-set in the system, and the driver files are generated in the following way:
[0065] Obtain identification information corresponding to multiple terminals; add each identification information to the source code of the vehicle's embedded system, and modify the embedded system configuration file; after modification, compile the kernel of the embedded system to generate a driver file corresponding to each identification information. The identification information and the driver file correspond one to one.
[0066] Specifically, obtain the identification information corresponding to terminals of different manufacturers and models in advance, and adapt the RNDIS driver of the Linux system: add the PID and VID in the identification information to the Linux source code drivers / usb / gadget / ether.c. Then check the RNDIS-related dependency configuration items through menuconfig or directly modify the kernel CONFIG configuration file, compile the kernel kernel to generate the relevant main driver files cdc.ko and rndis.ko. Among them, menuconfig is a graphical configuration interface that can be displayed on the terminal.
[0067] S23, loading a driver and installing a target application corresponding to the vehicle; configuring a configuration file of the target application according to the target address; establishing a network link between the vehicle and the target server according to the configured target application to establish a communication connection through the network link.
[0068] In this embodiment, after loading the driver in the driver file, a network link between the vehicle and the target server is constructed by supporting multiple protocols such as TCP, UDP, HTTP and the framework of the high-performance reverse proxy feature (Fast Reverse Proxy, frp) for intranet penetration. The target application can be pre-installed in the vehicle. The target application is to download the frpc client program source code from the frp official website and cross-compile the frpc executable program suitable for the system CPU architecture. When it is necessary to communicate with the target server, modify the configuration file frpc.ini of the frpc client, and modify the server's used IP, listening port, etc. in the configuration file according to the obtained target address. And run the frpc client program in the background in the system's startup script, thereby establishing a network link between the vehicle and the server, and communicating with the target server through the frpc client.
[0069] S24, obtaining a history record report log of the vehicle; sending the history record report log to a target server; and when receiving a control instruction returned for the history record report log, controlling the vehicle according to the control instruction.
[0070] In this embodiment, various information and data of the vehicle can be sent to a target server, and then sent to a backend for managing the vehicle through the target server. The vehicle data can be analyzed and managed through the backend.
[0071] Specifically, obtain the vehicle's historical record report log, that is, the VHR log. The design of VHR can be based on the interconnection characteristics of various modules of the car. The message interaction methods of various modules can include but are not limited to CAN, SPI, UART, etc., obtain the VHR logs collected by each module, and send them to the MPU processing unit in the system that can communicate with the server network. Finally, send it to the target server through the established network link between the server and the vehicle. The backend corresponding to the target server can analyze the VHR log and perform remote debugging of the vehicle in real time. When remote debugging is required, the backend generates a control instruction and sends the control instruction to the vehicle through the target server and the network link to control the vehicle according to the control instruction, and can adjust the parameters in the vehicle system.
[0072] The vehicle communication method provided by the embodiment of the present invention determines whether the vehicle and the terminal are connected through the target interface when receiving a network sharing request sent by the terminal; if so, the supplier identification code and product identification code of the terminal are obtained as identification information; if not, a prompt message is sent to the terminal to prompt the terminal to switch the connection mode through the prompt message. Obtain the rule file in the embedded system; obtain the driver file corresponding to the identification information according to the target field in the rule file, and obtain the target address of the target server corresponding to the vehicle. Load the driver program and install the target application corresponding to the vehicle; configure the configuration file of the target application according to the target address; establish a network link between the vehicle and the target server according to the configured target application to communicate through the network link. Obtain the historical record report log of the vehicle; send the historical record report log to the target server; when receiving the control instruction returned for the historical record report log, control the vehicle according to the control instruction. In this way, the function of enabling the automobile system to communicate with the external network based on the USB connection between the mobile phone and the car can be realized, and hot plugging can be realized in combination with the udev rule to reduce the system power consumption. Through the frp intranet penetration technology, the server backend can directly access the vehicle end system, and then view the real-time relevant parameters of the vehicle and the performance parameters of the software system. The remote server can obtain the VHR records of the vehicle, and can analyze and optimize the performance parameters of the vehicle through a large amount of data without the need for additional mobile network modules or wired Ethernet with limited usage scenarios. For vehicle models or user emergency on-site problems during the testing phase, developers can remotely maintain and handle related issues. This eliminates the need to copy relevant information to storage media and then analyze related issues, thereby improving the efficiency of problem handling. The vehicle networking communication function has been optimized, and the vehicle can communicate online without being equipped with a wireless network module. The vehicle's driving data and VHR can be sent to the server in a timely manner, improving the efficiency of vehicle networking communication.
[0073] like Figure 3FIG. 1 is a schematic diagram of a vehicle communication system according to an embodiment of the present invention, comprising:
[0074] The car side, mobile phone side, public server side and management system, the car side is the vehicle, the mobile phone side is the terminal, the public server is the target server, and the management system is the target service and its corresponding backend. Through the backend, the data sent by the vehicle can be viewed and analyzed, and the parameters of the vehicle can be adjusted. The car side and the mobile phone side are connected through USB, the corresponding identification information of the mobile phone side is obtained, the corresponding driver is obtained through the identification information, and the network link between the public server and the car side is established through the frp framework. The VHR log recorded by the car side is sent to the management system through the public server for analysis and processing. When the public server generates a control instruction for the vehicle, the control instruction can be sent to the car side through the public server.
[0075] Figure 4 FIG. 1 is a schematic diagram of a vehicle communication device provided by an embodiment of the present invention, wherein the device specifically includes:
[0076] A first acquisition module 41, configured to acquire identification information of a terminal when receiving a network sharing request sent by the terminal, the vehicle being connected to the terminal via a target interface;
[0077] A second acquisition module 42 is used to acquire a driver file corresponding to the identification information and a target address of a target server corresponding to the vehicle;
[0078] The control module 43 is used to control the communication connection between the vehicle and the target server according to the target address and the driver program after loading the driver program in the driver file.
[0079] In a possible implementation manner, the first acquisition module is specifically used to determine whether the vehicle is connected to the terminal through the target interface;
[0080] If yes, obtaining the supplier identification code and product identification code of the terminal as the identification information;
[0081] If not, a prompt message is sent to the terminal, so as to prompt the terminal to switch the connection mode through the prompt message.
[0082] In a possible implementation manner, the second acquisition module is specifically used to acquire a rule file in the embedded system;
[0083] The driver file corresponding to the identification information is acquired according to the target field in the rule file, and the identification information and the driver file correspond one to one.
[0084] In a possible implementation manner, the control module is specifically used to load the driver and install a target application corresponding to the vehicle;
[0085] Configuring a configuration file of the target application according to the target address;
[0086] A network link is established between the vehicle and the target server according to the configured target application program to establish a communication connection via the network link.
[0087] In a possible implementation manner, the control module is further used to obtain a history record report log of the vehicle;
[0088] sending the history report log to the target server;
[0089] When a control instruction returned for the history report log is received, the vehicle is controlled according to the control instruction.
[0090] The vehicle communication device provided in this embodiment may be as follows Figure 4 The device shown in FIG. 1 can perform the following steps: Figure 1-2 All the steps of the method in Figure 1-2 For details, please refer to the technical effect of the communication method of the vehicle shown in Figure 1-2 For the sake of brevity, the relevant description is not repeated here.
[0091] Figure 5 A schematic diagram of the structure of a car provided by an embodiment of the present invention, Figure 5 The automobile 500 shown includes: at least one processor 501, a memory 502, at least one network interface 504 and other user interfaces 503. The various components in the automobile 500 are coupled together via a bus system 505. It is understood that the bus system 505 is used to achieve connection and communication between these components. In addition to the data bus, the bus system 505 also includes a power bus, a control bus and a status signal bus. However, for the sake of clarity, the bus system 505 is not described in detail. Figure 5 Various buses are labeled as bus system 505 .
[0092] The user interface 503 may include a display, a keyboard, or a pointing device (eg, a mouse, a trackball, a touch pad, or a touch screen).
[0093] It can be understood that the memory 502 in the embodiment of the present invention can be a volatile memory or a non-volatile memory, or can include both volatile and non-volatile memories. Among them, the non-volatile memory can be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory can be a random access memory (RAM), which is used as an external cache. By way of example but not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM) and direct RAM bus random access memory (DRRAM). The memory 502 described herein is intended to include, but is not limited to, these and any other suitable types of memory.
[0094] In some implementations, the memory 502 stores the following elements, executable units or data structures, or a subset thereof, or an extended set thereof: an operating system 5021 and an application program 5022 .
[0095] The operating system 5021 includes various system programs, such as a framework layer, a core library layer, a driver layer, etc., which are used to implement various basic services and process hardware-based tasks. The application 5022 includes various application programs, such as a media player (Media Player), a browser (Browser), etc., which are used to implement various application services. The program for implementing the method of the embodiment of the present invention can be included in the application 5022.
[0096] In the embodiment of the present invention, by calling the program or instruction stored in the memory 502, specifically, the program or instruction stored in the application 5022, the processor 501 is used to execute the method steps provided by each method embodiment, for example, including:
[0097] When receiving a network sharing request sent by a terminal, obtaining identification information of the terminal, and connecting the vehicle to the terminal through a target interface;
[0098] Obtaining a driver file corresponding to the identification information, and obtaining a target address of a target server corresponding to the vehicle;
[0099] After the driver program in the driver file is loaded, the vehicle is controlled to communicate with the target server according to the target address and the driver program.
[0100] In a possible implementation, determining whether the vehicle is connected to the terminal through the target interface;
[0101] If yes, obtaining the supplier identification code and product identification code of the terminal as the identification information;
[0102] If not, a prompt message is sent to the terminal, so as to prompt the terminal to switch the connection mode through the prompt message.
[0103] In a possible implementation, obtaining identification information corresponding to multiple terminals;
[0104] Adding each identification information to the source code of the embedded system of the vehicle, and modifying the embedded system configuration file;
[0105] After modification, the kernel of the embedded system is compiled to generate a driver file corresponding to each identification information.
[0106] In a possible implementation, obtaining a rule file in the embedded system;
[0107] The driver file corresponding to the identification information is acquired according to the target field in the rule file, and the identification information and the driver file correspond one to one.
[0108] In a possible implementation, the first field is set to determine whether the terminal is connected to the vehicle, the second field is set to determine whether the terminal is connected through a target interface, the third field is set to the identification information, and the fourth field is set to load the driver file;
[0109] The rule file is generated according to the first field, the second field, the third field and the fourth field.
[0110] In a possible implementation, the driver is loaded, and a target application corresponding to the vehicle is installed;
[0111] Configuring a configuration file of the target application according to the target address;
[0112] A network link is established between the vehicle and the target server according to the configured target application program to establish a communication connection via the network link.
[0113] In one possible implementation, obtaining a history report log of the vehicle;
[0114] sending the history report log to the target server;
[0115] When a control instruction returned for the history report log is received, the vehicle is controlled according to the control instruction.
[0116] The method disclosed in the above embodiment of the present invention can be applied to the processor 501, or implemented by the processor 501. The processor 501 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method can be completed by the hardware integrated logic circuit in the processor 501 or the instruction in the form of software. The above processor 501 can be a general processor, a digital signal processor (Digital Signal Processor, DSP), an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), a field programmable gate array (Field Programmable Gate Array, FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components. The methods, steps and logic block diagrams disclosed in the embodiments of the present invention can be implemented or executed. The general processor can be a microprocessor or the processor can also be any conventional processor, etc. The steps of the method disclosed in the embodiment of the present invention can be directly embodied as a hardware decoding processor to execute, or the hardware and software units in the decoding processor can be executed. The software unit can be located in a mature storage medium in the field such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory or an electrically erasable programmable memory, a register, etc. The storage medium is located in the memory 502, and the processor 501 reads the information in the memory 502 and completes the steps of the above method in combination with its hardware.
[0117] It is understood that the embodiments described herein may be implemented in hardware, software, firmware, middleware, microcode, or a combination thereof. For hardware implementation, the processing unit may be implemented in one or more application specific integrated circuits (ASIC), digital signal processors (DSP), digital signal processing devices (DSPDevice, DSPD), programmable logic devices (PLD), field programmable gate arrays (FPGA), general purpose processors, controllers, microcontrollers, microprocessors, other electronic units for performing the functions described in the present application, or a combination thereof.
[0118] For software implementation, the technology described herein can be implemented by a unit that performs the functions described herein. The software code can be stored in a memory and executed by a processor. The memory can be implemented in the processor or outside the processor.
[0119] The automobile provided in this embodiment may be Figure 5 The car shown in , can be executed as Figure 1-2 All the steps of the method in Figure 1-2 For details, please refer to the technical effect of the communication method of the vehicle shown in Figure 1-2 For the sake of brevity, the relevant description is not repeated here.
[0120] The embodiment of the present invention also provides a storage medium (computer-readable storage medium). The storage medium here stores one or more programs. The storage medium may include a volatile memory, such as a random access memory; the memory may also include a non-volatile memory, such as a read-only memory, a flash memory, a hard disk or a solid-state drive; the memory may also include a combination of the above-mentioned types of memory.
[0121] When one or more programs in the storage medium can be executed by one or more processors to implement the above-mentioned vehicle communication method executed on the device side.
[0122] The processor is used to execute the vehicle communication program stored in the memory to implement the following steps of the vehicle communication method executed on the device side:
[0123] When receiving a network sharing request sent by a terminal, obtaining identification information of the terminal, and connecting the vehicle to the terminal through a target interface;
[0124] Obtaining a driver file corresponding to the identification information, and obtaining a target address of a target server corresponding to the vehicle;
[0125] After the driver program in the driver file is loaded, the vehicle is controlled to communicate with the target server according to the target address and the driver program.
[0126] In a possible implementation, determining whether the vehicle is connected to the terminal through the target interface;
[0127] If yes, obtaining the supplier identification code and product identification code of the terminal as the identification information;
[0128] If not, a prompt message is sent to the terminal, so as to prompt the terminal to switch the connection mode through the prompt message.
[0129] In a possible implementation, obtaining identification information corresponding to multiple terminals;
[0130] Adding each identification information to the source code of the embedded system of the vehicle, and modifying the embedded system configuration file;
[0131] After modification, the kernel of the embedded system is compiled to generate a driver file corresponding to each identification information.
[0132] In a possible implementation, obtaining a rule file in the embedded system;
[0133] The driver file corresponding to the identification information is acquired according to the target field in the rule file, and the identification information and the driver file correspond one to one.
[0134] In a possible implementation, the first field is set to determine whether the terminal is connected to the vehicle, the second field is set to determine whether the terminal is connected through a target interface, the third field is set to the identification information, and the fourth field is set to load the driver file;
[0135] The rule file is generated according to the first field, the second field, the third field and the fourth field.
[0136] In a possible implementation, the driver is loaded, and a target application corresponding to the vehicle is installed;
[0137] Configuring a configuration file of the target application according to the target address;
[0138] A network link is established between the vehicle and the target server according to the configured target application program to establish a communication connection via the network link.
[0139] In one possible implementation, obtaining a history report log of the vehicle;
[0140] sending the history report log to the target server;
[0141] When a control instruction returned for the history report log is received, the vehicle is controlled according to the control instruction.
[0142] The professionals should further realize that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented by electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, the composition and steps of each example have been generally described in the above description according to the function. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professionals and technicians can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of the present invention.
[0143] The steps of the method or algorithm described in conjunction with the embodiments disclosed herein may be implemented using hardware, a software module executed by a processor, or a combination of the two. The software module may be placed in a random access memory (RAM), a memory, a read-only memory (ROM), an electrically programmable ROM, an electrically erasable programmable ROM, a register, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.
[0144] The specific implementation methods described above further illustrate the objectives, technical solutions and beneficial effects of the present invention in detail. It should be understood that the above description is only a specific implementation method of the present invention and is not intended to limit the scope of protection of the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present invention should be included in the scope of protection of the present invention.
Claims
1. A vehicle communication method, characterized in that: include: When receiving a network sharing request sent by a terminal, obtaining identification information of the terminal, and connecting the vehicle to the terminal through a target interface; Obtaining a driver file corresponding to the identification information, and obtaining a target address of a target server corresponding to the vehicle; After the driver program in the driver file is loaded, the vehicle is controlled to communicate with the target server according to the target address and the driver program.
2. The method according to claim 1, characterized in that The acquiring identification information of the terminal includes: determining whether the vehicle is connected to the terminal through the target interface; If yes, obtaining the supplier identification code and product identification code of the terminal as the identification information; If not, a prompt message is sent to the terminal, so as to prompt the terminal to switch the connection mode through the prompt message.
3. The method according to claim 1, characterized in that The driver file is generated in the following way: Obtain identification information corresponding to multiple terminals; Adding each identification information to the source code of the embedded system of the vehicle, and modifying the embedded system configuration file; After modification, the kernel of the embedded system is compiled to generate a driver file corresponding to each identification information.
4. The method according to claim 3, characterized in that The step of obtaining the driver file corresponding to the identification information includes: Obtaining a rule file in the embedded system; The driver file corresponding to the identification information is acquired according to the target field in the rule file, and the identification information and the driver file correspond one to one.
5. The method according to claim 4, characterized in that The rule file is generated in the following way: The first field is set to determine whether the terminal is connected to the vehicle, the second field is set to determine whether the terminal is connected through a target interface, the third field is set to the identification information, and the fourth field is set to load the driver file; The rule file is generated according to the first field, the second field, the third field and the fourth field.
6. The method according to claim 3, characterized in that The step of controlling the vehicle to communicate with the target server according to the target address and the driver comprises: Loading the driver and installing a target application corresponding to the vehicle; Configuring a configuration file of the target application according to the target address; A network link is established between the vehicle and the target server according to the configured target application program to establish a communication connection via the network link.
7. The method according to claim 1, characterized in that After communicating and connecting with the target server according to the target address, the method further includes: Obtaining a history report log of the vehicle; sending the history report log to the target server; When a control instruction returned for the history report log is received, the vehicle is controlled according to the control instruction.
8. A vehicle communication device, characterized in that: include: A first acquisition module, configured to acquire identification information of a terminal when receiving a network sharing request sent by the terminal, the vehicle being connected to the terminal via a target interface; A second acquisition module is used to acquire a driver file corresponding to the identification information and a target address of a target server corresponding to the vehicle; The control module is used to control the communication connection between the vehicle and the target server according to the target address and the driver program after loading the driver program in the driver file.
9. A car, characterized in that: include: A processor and a memory, wherein the processor is used to execute a vehicle communication program stored in the memory to implement the vehicle communication method according to any one of claims 1 to 7.
10. A storage medium, characterized in that: The storage medium stores one or more programs, and the one or more programs can be executed by one or more processors to implement the vehicle communication method according to any one of claims 1 to 7.
Citation Information
Cited By
Log data transmission method and system, computer equipment and medium
CN119892614A
A log data transmission method and system, a computer device and a medium
CN119892614B
Network mode switching method and system
CN120835345A
