A Vehicle Communication Method, Device and Medium

Abstract

The present application relates to the field of vehicle network technology, and discloses a vehicle communication method, device and medium. The method includes: The device includes an in-vehicle information management module, an MCU management module, and an MCU. The method includes: establishing a Socket connection between the in-vehicle device and the TBOX device; obtaining, by the in-vehicle information management module, a vehicle identification code acquisition request sent by the in-vehicle device; forwarding, by the in-vehicle information management module, the vehicle identification code acquisition request to the MCU management module, and forwarding, by the MCU management module, the vehicle identification code acquisition request to the MCU to obtain a vehicle identification code from the MCU; after the MCU management module obtains the vehicle identification code from the MCU, forwarding, by the MCU management module, the vehicle identification code to the in-vehicle information management module; and forwarding, by the in-vehicle information management module, the vehicle identification code to the in-vehicle device to confirm whether the vehicle identification codes of the in-vehicle device and the TBOX device are consistent. The present application divides each independent module inside the T-BOX, improving the reliability of information interaction between the in-vehicle device and the TBOX.

Description

Technical Field

[0001] This application relates to the technical field of vehicle networks, and in particular, to a vehicle communication method, device, and medium. Background Art

[0002] In the prior art, a comparative document with the publication number CN114095299A discloses an in-vehicle fault intelligent reminder system, method, device, and storage medium, belonging to the technical field of in-vehicle intelligent networking. It includes an instrument, an audio host, a cloud platform, a remote communication terminal, and a gateway. The instrument is used to display fault information and transmit the fault information to the audio host through LVDS. The audio host receives the fault information of the instrument and transmits it to the cloud platform through the gateway and Tbox for processing, and displays the fault information and push suggestions to the user. The cloud platform is used to process information from the vehicle end and push the interpretation and processing opinions of the fault information. The remote communication terminal provides a network link for the system. The gateway performs signal routing and forwarding. This system can vividly display vehicle fault information, which helps users understand the fault information, optimizes the user experience, and can timely remind more fault items, enabling the driver to comprehensively understand the vehicle condition and improve driving safety.

[0003] The comparative document does not reflect exception handling such as communication timeouts, and does not divide the individual modules inside the T-BOX independently, making it difficult to ensure the reliability of its functions. Summary of the Invention

[0004] The purpose of this application is to provide a vehicle communication method, device, and medium, which divides the individual modules inside the T-BOX independently and designs corresponding timeout and retry mechanisms, improving the reliability of information interaction between the vehicle head unit and the T-BOX.

[0005] Other features and advantages of this application will become apparent through the following detailed description, or be learned in part through the practice of this application.

[0006] According to one aspect of the embodiments of the present application, a vehicle communication method is provided. The method is executed on a TBOX device, which includes a vehicle information management module, an MCU management module, and an MCU. The method includes: establishing a Socket connection between the in-vehicle device and the TBOX device; obtaining, by the vehicle information management module, a vehicle identification code acquisition request sent by the in-vehicle device; forwarding, by the vehicle information management module, the vehicle identification code acquisition request to the MCU management module, and forwarding, by the MCU management module, the vehicle identification code acquisition request to the MCU to obtain a vehicle identification code from the MCU; after the MCU management module obtains the vehicle identification code from the MCU, forwarding, by the MCU management module, the vehicle identification code to the vehicle information management module; and forwarding, by the vehicle information management module, the vehicle identification code to the in-vehicle device to confirm whether the vehicle identification codes of the in-vehicle device and the TBOX device are consistent.

[0007] In some embodiments, before forwarding, by the vehicle information management module, the vehicle identification code acquisition request to the MCU management module, the method further includes: in response to the power-on of the vehicle, sending, by the in-vehicle device, a handshake request to the vehicle information management module; after the vehicle information management module receives the handshake request, sending, by the vehicle information management module, a handshake response to the in-vehicle device to maintain the Socket connection between the in-vehicle device and the TBOX device.

[0008] In some embodiments, after forwarding, by the MCU management module, the vehicle identification code acquisition request to the MCU, the method further includes: if the MCU management module obtains null data from the MCU, re-forwarding the vehicle identification code acquisition request to the MCU; if the number of times the MCU management module obtains null data from the MCU exceeds a first threshold, sending a preset default value to the vehicle information management module; and sending, by the vehicle information management module, the preset default value to the in-vehicle device.

[0009] In some embodiments, the method further includes: obtaining, by the vehicle information management module, a version number acquisition request sent by the in-vehicle device; forwarding, by the vehicle information management module, the version number acquisition request to the MCU management module, and forwarding, by the MCU management module, the version number acquisition request to the MCU to obtain a version number from the MCU; after the MCU management module obtains the version number from the MCU, forwarding, by the MCU management module, the version number to the vehicle information management module; and forwarding, by the vehicle information management module, the version number to the in-vehicle device.

[0010] In some embodiments, after the MCU management module forwards the version number acquisition request to the MCU, the method further includes: if the MCU management module obtains null data from the MCU, re-forwarding the version number acquisition request to the MCU; if the number of times the MCU management module obtains null data from the MCU exceeds a second threshold, sending a preset default value to the vehicle information management module; and the vehicle information management module sending the preset default value to the in-vehicle device.

[0011] In some embodiments, the version number includes a hardware version number and / or a software version number.

[0012] In some embodiments, the TBOX device further includes an Internet access module and a module management module, and the method further includes: the vehicle information management module obtaining an Internet access identification information acquisition request sent by the in-vehicle device; the vehicle information management module forwarding the Internet access identification information acquisition request to the module management module, and the module management module forwarding the Internet access identification information acquisition request to the Internet access module to obtain Internet access identification information from the Internet access module; after the module management module obtains the Internet access identification information from the Internet access module, the module management module forwarding the Internet access identification information to the vehicle information management module; and the vehicle information management module forwarding the Internet access identification information to the in-vehicle device.

[0013] In some embodiments, after the module management module forwards the Internet access identification information acquisition request to the Internet access module, the method further includes: if the module management module obtains null data from the Internet access module, re-forwarding the Internet access identification information acquisition request to the Internet access module; if the number of times the module management module obtains null data from the Internet access module exceeds a third threshold, sending a preset default value to the vehicle information management module; and the vehicle information management module sending the preset default value to the in-vehicle device.

[0014] In some embodiments, the Internet access identification information includes a SIM card number and / or an International Mobile Subscriber Identity.

[0015] In some embodiments, the TBOX device further includes a cloud communication module, and the method further includes: establishing a Socket connection between the cloud communication module and the cloud, and obtaining vehicle-mounted device management remote configuration information sent by the cloud; the cloud communication module forwarding the device management remote configuration information to the vehicle information management module, and the vehicle information management module forwarding the device management remote configuration information to the in-vehicle device.

[0016] In some embodiments, after the vehicle information management module forwards the device management remote configuration information to the in-vehicle device, the method further includes: obtaining the update success information for the device management remote configuration information sent by the in-vehicle device; the vehicle information management module forwarding the update success information to the cloud communication module, and the cloud communication module feeding back the update success information to the cloud.

[0017] In some embodiments, after the vehicle information management module forwards the device management remote configuration information to the in-vehicle device, the method further includes: if the update success information for the device management remote configuration information sent by the in-vehicle device is not obtained within a preset time, the vehicle information management module forwards the device management remote configuration information to the in-vehicle device again; if the number of times the vehicle information management module forwards the device management remote configuration information to the in-vehicle device again exceeds a fourth threshold, the cloud communication module feeds back the update failure information to the cloud.

[0018] In some embodiments, the device management remote configuration information includes in-vehicle language configuration information and / or WIFI configuration information.

[0019] According to one aspect of the embodiments of the present application, there is provided a computer-readable medium having a computer program stored thereon, and when the computer program is executed by a processor, it implements the vehicle communication method as described in the above embodiments.

[0020] According to one aspect of the embodiments of the present application, there is provided an electronic device, including: one or more processors; a memory for storing executable instructions of the processor, and when the executable instructions are executed by the one or more processors, the one or more processors implement the vehicle communication method as described in the above embodiments.

[0021] With the technical solution of the present application above, compared with the prior art, its significant beneficial effect lies in that: in the traditional vehicle communication method, abnormal processing such as communication timeout is not reflected, and the internal T-BOX is not divided into independent modules, making it difficult to ensure the reliability of its functions. Through the design of modules such as the vehicle information management module, MCU management module, MCU, Internet access module, and module management module inside the T-BOX in the present application, reliable interaction for obtaining device information between the T-BOX and the in-vehicle device is completed, and corresponding timeout and retry mechanisms are designed, improving the reliability of information interaction between the in-vehicle device and the T-BOX.

[0022] It should be understood that the above general description and the following detailed description are only exemplary and explanatory, and cannot limit the present application. Description of the Drawings

[0023] The above and other features and advantages of the present application will become more apparent by describing its exemplary embodiments in detail with reference to the accompanying drawings.

[0024] Figure 1 A schematic block diagram showing the interaction principle between an in-vehicle device and a TBOX according to an embodiment of the present application;

[0025] Figure 2 A flowchart showing the acquisition of a vehicle identification code according to an embodiment of the present application;

[0026] Figure 3 Another flowchart showing the acquisition of a vehicle identification code according to an embodiment of the present application;

[0027] Figure 4 A flowchart showing the acquisition of a version number according to an embodiment of the present application;

[0028] Figure 5 A flowchart showing the acquisition of Internet access identification information according to an embodiment of the present application;

[0029] Figure 6 A flowchart showing the acquisition of device management remote configuration information according to an embodiment of the present application;

[0030] Figure 7 A schematic structural diagram of a computer system of an electronic device according to an embodiment of the present application. Detailed implementation manners

[0031] Example embodiments will now be described more fully with reference to the accompanying drawings. However, the example embodiments can be implemented in various forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided so that this application will be more complete and comprehensive, and will fully convey the concept of the example embodiments to those skilled in the art.

[0032] In addition, the described features, structures, or characteristics can be combined in any suitable manner in one or more embodiments. In the following description, numerous specific details are provided to give a thorough understanding of the embodiments of the present application. However, those skilled in the art will recognize that the technical solutions of the present application can be practiced without one or more of the specific details, or other methods, components, devices, steps, etc. can be used. In other cases, well-known methods, devices, implementations, or operations are not shown or described in detail to avoid obscuring aspects of the present application.

[0033] The block diagrams shown in the drawings are only functional entities and do not necessarily correspond to physically independent entities. That is, these functional entities can be implemented in software form, or implemented in one or more hardware modules or integrated circuits, or implemented in different networks and / or processor devices and / or microcontroller devices.

[0034] The flowcharts shown in the drawings are only exemplary descriptions, and do not necessarily include all content and operations / steps, nor do they necessarily need to be executed in the described order. For example, some operations / steps can be decomposed, while some operations / steps can be combined or partially combined. Therefore, the actual execution order may change according to the actual situation.

[0035] According to some embodiments, as Figure 1 shown, Figure 1 a schematic block diagram 100 of the interaction between the in-vehicle device 1 and the TBOX is shown. The TBOX device includes an in-vehicle device management communication module, and the in-vehicle device management communication module includes an in-vehicle information management module 2 (IVI_MANAGER), an MCU management module 3 (MCU_MANAGER), and a module management module 5 (MODEM Manager). The in-vehicle information management module 2 is the docking window of the in-vehicle device 1, used to receive data from the in-vehicle device 1 and perform data parsing. After data parsing, it is distributed to the corresponding sub-modules, such as module information and vehicle information. The module information mainly obtains the T-BOX 4G / 5G module information from the module management module 5 to realize the connection with the module management module 5 and information acquisition, etc. The vehicle information is mainly obtained from the MCU management module 3 to realize the connection with the MCU management module 3 and information acquisition, etc. The module management module 5 stores and manages the information of the communication Internet module 6 (MODEM), such as the ICCID and IMSI information of the 4G / 5G module. The MCU management module 3 stores and manages the information from the vehicle, including information from the VIN code, etc.

[0036] According to some embodiments, the present application provides a vehicle communication method, which is executed on a TBOX device. The device includes a vehicle information management module 2, an MCU management module 3, and an MCU 4. The method includes: Step 201, establish a Socket connection between the in-vehicle device 1 and the TBOX device; Step 202, the vehicle information management module 2 obtains a vehicle identification code acquisition request sent by the in-vehicle device 1; Step 203, the vehicle information management module 2 forwards the vehicle identification code acquisition request to the MCU management module 3, and the MCU management module 3 forwards the vehicle identification code acquisition request to the MCU 4 to obtain a vehicle identification code from the MCU 4; Step 204, after the MCU management module 3 obtains the vehicle identification code from the MCU 4, the MCU management module 3 forwards the vehicle identification code to the vehicle information management module 2; Step 205, the vehicle information management module 2 forwards the vehicle identification code to the in-vehicle device 1 to confirm whether the vehicle identification codes of the in-vehicle device 1 and the TBOX device are the same.

[0037] Based on the above embodiments, as Figure 2 shown, Figure 2 The flowchart for obtaining the vehicle identification code is presented. Before Step 201 starts, vehicle preparation work needs to be done. First, the vehicle needs to be powered on. After power-on, enter Step 201. In Step 201, after the in-vehicle device 1 is normally connected to the TBOX device through USB, a Socket connection is established between the in-vehicle device 1 and the TBOX device.

[0038] Further, in Step 202, when the in-vehicle device 1 needs to obtain the VIN code in the TBOX device, it sends a vehicle identification code acquisition request to the vehicle information management module 2 in the TBOX device, and the vehicle information management module 2 receives the vehicle identification code acquisition request sent by the in-vehicle device 1.

[0039] Further, in Step 203, after the vehicle information management module 2 receives the vehicle identification code acquisition request, the vehicle information management module 2 forwards the vehicle identification code acquisition request to the MCU management module 3. After the MCU management module 3 receives the vehicle identification code acquisition request, it forwards the vehicle identification code acquisition request to the MCU 4. The vehicle identification code is stored in the MCU 4. After the MCU 4 receives the vehicle identification code acquisition request sent by the MCU management module 3, the MCU 4 sends the vehicle identification code to the MCU management module 3.

[0040] Further, in Step 204, after the MCU 4 sends the vehicle identification code to the MCU management module 3, after the MCU management module 3 receives the vehicle identification code from the MCU 4, the MCU management module 3 forwards the vehicle identification code to the vehicle information management module 2.

[0041] Further, in step 205, after the vehicle information management module 2 receives the vehicle identification code sent by the MCU management module 3, the vehicle information management module 2 forwards the vehicle identification code to the in-vehicle device 1. After the in-vehicle device 1 receives the vehicle identification code of the TBOX device, it compares its own vehicle identification code with that of the TBOX device to confirm whether the vehicle identification codes of the in-vehicle device 1 and the TBOX device are consistent, preventing matching errors.

[0042] According to some embodiments, before the vehicle information management module 2 forwards the vehicle identification code acquisition request to the MCU management module 3 in step 203, the method further includes: in response to the vehicle's power-on, the in-vehicle device 1 sends a handshake request to the vehicle information management module 2; after the vehicle information management module 2 receives the handshake request, the vehicle information management module 2 sends a handshake response to the in-vehicle device 1 to maintain the Socket connection between the in-vehicle device 1 and the TBOX device.

[0043] Based on the above embodiments, as Figure 3 shown, Figure 3 A more detailed flowchart for obtaining the vehicle identification code is shown. Before step 203, that is, before the vehicle information management module 2 forwards the vehicle identification code acquisition request to the MCU management module 3, the in-vehicle device 1 sends a handshake request to the vehicle information management module 2. After the vehicle information management module 2 receives the handshake request from the in-vehicle device 1, the vehicle information management module 2 sends a handshake response to the in-vehicle device 1 to maintain the Socket connection between the in-vehicle device 1 and the TBOX device, facilitating communication between the in-vehicle device 1 and the TBOX device.

[0044] According to some embodiments, after the MCU management module 3 forwards the vehicle identification code acquisition request to the MCU4 in step 203, the method further includes: if the MCU management module 3 obtains null data from the MCU4, it forwards the vehicle identification code acquisition request to the MCU4 again; if the number of times the MCU management module 3 obtains null data from the MCU4 exceeds a first threshold, it sends a preset default value to the vehicle information management module 2; and the vehicle information management module 2 sends the preset default value to the in-vehicle device 1.

[0045] Based on the above embodiments, as Figure 3 shown, Figure 3A more detailed flowchart for obtaining the vehicle identification number is presented. If the MCU management module 3 obtains null data from the MCU 4, the MCU management module 3 forwards the vehicle identification number acquisition request to the MCU 4 again. In some embodiments, after the MCU management module 3 forwards the vehicle identification number acquisition request to the MCU 4, if the MCU 4 does not reply and exceeds the set duration, the MCU management module 3 also treats it as if the MCU 4 replied with null data, and the MCU management module 3 forwards the vehicle identification number acquisition request to the MCU 4 again.

[0046] Furthermore, if the number of times the MCU management module 3 obtains null data from the MCU 4 exceeds the first threshold, that is, the number of times the MCU management module 3 forwards the vehicle identification number acquisition request to the MCU 4 exceeds the first threshold, a preset default value is sent to the vehicle information management module 2; the vehicle information management module 2 sends the preset default value to the in-vehicle device 1. Among them, the first threshold can be set according to actual needs. In some embodiments, the first threshold is set to 2, that is, when the number of times the MCU management module 3 forwards the vehicle identification number acquisition request to the MCU 4 reaches 2 times, and null data is still obtained after 2 times, a preset default value is sent to the vehicle information management module 2.

[0047] Furthermore, if the number of times the MCU 4 does not reply exceeding the set duration reaches 2 times, or the number of times null data is obtained reaches 2 times, it can be set that the MCU management module 3 sends a preset default value to the vehicle information management module 2.

[0048] If the number of times null data is obtained reaches 2 times, it can be set that the MCU 4 replies with a preset default value to the MCU management module 3, and the MCU management module 3 sends the preset default value to the vehicle information management module 2.

[0049] According to some embodiments, the method further includes: step S401, the vehicle information management module 2 obtains the version number acquisition request sent by the in-vehicle device 1; step S402, the vehicle information management module 2 forwards the version number acquisition request to the MCU management module 3, and the MCU management module 3 forwards the version number acquisition request to the MCU 4 to obtain the version number from the MCU 4; step S403, after the MCU management module 3 obtains the version number from the MCU 4, the MCU management module 3 forwards the version number to the vehicle information management module 2; step S404, the vehicle information management module 2 forwards the version number to the in-vehicle device 1.

[0050] Based on the above embodiments, as Figure 4 shown, Figure 4A flowchart for obtaining the version number is presented, which can specifically be used to obtain the hardware version number and software version number of the T-BOX. When it is necessary to obtain the hardware version number and software version number of the T-BOX, step S401 is entered. The vehicle head unit device 1 sends a version number acquisition request to the vehicle information management module 2. After the vehicle information management module 2 receives the version number acquisition request sent by the vehicle head unit device 1, step S402 is entered. The vehicle information management module 2 forwards the version number acquisition request to the MCU management module 3. After the MCU management module 3 receives the version number acquisition request sent by the vehicle information management module 2, the version number acquisition request is forwarded to the MCU 4 to obtain the hardware version number and software version number of the T-BOX from the MCU 4. The hardware version number and software version number of the T-BOX are stored in the MCU 4. After the MCU 4 receives the version number acquisition request from the MCU management module 3, the hardware version number and software version number of the T-BOX are sent to the MCU management module 3. In step S403, after the MCU management module 3 obtains the version number from the MCU 4, the MCU management module 3 forwards the version number to the vehicle information management module 2. In step S404, after the vehicle information management module 2 receives the hardware version number and software version number of the T-BOX forwarded by the MCU management module 3, the vehicle information management module 2 forwards the hardware version number and software version number of the T-BOX to the vehicle head unit device 1.

[0051] According to some embodiments, after the MCU management module 3 forwards the version number acquisition request to the MCU 4, the method further includes: if the MCU management module 3 obtains null data from the MCU 4, the version number acquisition request is re-forwarded to the MCU 4; if the number of times the MCU management module 3 obtains null data from the MCU 4 exceeds a second threshold, a preset default value is sent to the vehicle information management module 2; and the vehicle information management module 2 sends the preset default value to the vehicle head unit device 1.

[0052] Based on the above embodiments, if the MCU management module 3 obtains null data from the MCU 4, the MCU management module 3 re-forwards the version number acquisition request to the MCU 4. In some embodiments, after the MCU management module 3 forwards the version number acquisition request to the MCU 4, if the MCU 4 does not reply and exceeds a set time duration, the MCU management module 3 also treats it as if the MCU 4 replied with null data, and the MCU management module 3 re-forwards the version number acquisition request to the MCU 4.

[0053] Further, if the number of times the MCU management module 3 obtains null value data from the MCU 4 exceeds a second threshold, that is, the number of times the MCU management module 3 forwards the version number acquisition request to the MCU 4 exceeds the second threshold, it sends a preset default value to the vehicle information management module 2; the vehicle information management module 2 sends the preset default value to the in-vehicle device 1. Among them, the second threshold can be set according to actual needs. In some embodiments, the second threshold is set to 2, that is, when the number of times the MCU management module 3 forwards the version number acquisition request to the MCU 4 reaches 2 times and still obtains null value data for the second time, it sends a preset default value to the vehicle information management module 2.

[0054] Further, if the number of times that the MCU 4 does not reply after exceeding the set duration reaches 2 times, or the number of times of obtaining null value data reaches 2 times, it can be set that the MCU management module 3 sends a preset default value to the vehicle information management module 2.

[0055] If the number of times of obtaining null value data reaches 2 times, it can be set that the MCU 4 replies with a preset default value to the MCU management module 3, and the MCU management module 3 sends the preset default value to the vehicle information management module 2.

[0056] According to some embodiments, the version number includes a hardware version number and / or a software version number.

[0057] Based on the above embodiments, the version number can be the hardware version number and software version number of the T-BOX, or the hardware version number of the T-BOX, or the software version number of the T-BOX.

[0058] According to some embodiments, the TBOX device further includes an Internet access module 6 and a module management module 5, and the method further includes: Step S501, the vehicle information management module 2 obtains an Internet access identification information acquisition request sent by the in-vehicle device 1; Step S502, the vehicle information management module 2 forwards the Internet access identification information acquisition request to the module management module 5, and the module management module 5 forwards the Internet access identification information acquisition request to the Internet access module 6 to obtain Internet access identification information from the Internet access module 6; Step S503, after the module management module 5 obtains the Internet access identification information from the Internet access module 6, the module management module 5 forwards the Internet access identification information to the vehicle information management module 2; Step S504, the vehicle information management module 2 forwards the Internet access identification information to the in-vehicle device 1.

[0059] Based on the above embodiments, as Figure 5 shown, Figure 5The flowchart for obtaining Internet access identification information is presented. The TBOX device further includes an Internet access module 6 and a module management module 5. When the in-vehicle device 1 needs to obtain Internet access identification information from the TBOX device, such as ICCID, IMSI, etc., it enters step S501. The in-vehicle device 1 sends an Internet access identification information acquisition request to the vehicle information management module 2. After the vehicle information management module 2 receives the Internet access identification information acquisition request sent by the in-vehicle device 1, it enters step S502. The vehicle information management module 2 forwards the Internet access identification information acquisition request to the module management module 5. After the module management module 5 receives the Internet access identification information acquisition request sent by the vehicle information management module 2, it forwards the Internet access identification information acquisition request to the Internet access module 6 for obtaining Internet access identification information from the Internet access module 6. In step S503, after the Internet access module 6 receives the Internet access identification information acquisition request sent by the module management module 5, it sends the internally stored Internet access identification information to the module management module 5. After the module management module 5 receives the Internet access identification information from the Internet access module 6, the module management module 5 forwards the Internet access identification information to the vehicle information management module 2. In step S504, after the vehicle information management module 2 receives the Internet access identification information sent by the module management module 5, the vehicle information management module 2 forwards the Internet access identification information to the in-vehicle device 1.

[0060] According to some embodiments, after the module management module 5 forwards the Internet access identification information acquisition request to the Internet access module 6, the method further includes: if the module management module 5 obtains null data from the Internet access module 6, it forwards the Internet access identification information acquisition request to the Internet access module 6 again; if the number of times the module management module 5 obtains null data from the Internet access module 6 exceeds a third threshold, it sends a preset default value to the vehicle information management module 2; and the vehicle information management module 2 sends the preset default value to the in-vehicle device 1.

[0061] Based on the above embodiments, if the module management module 5 obtains null data from the Internet access module 6, the module management module 5 forwards the Internet access identification information acquisition request to the Internet access module 6 again. In some embodiments, after the module management module 5 forwards the Internet access identification information acquisition request to the Internet access module 6, if the Internet access module 6 does not reply and exceeds a set duration, the module management module 5 also treats it as if the Internet access module 6 replied with null data, and the module management module 5 forwards the Internet access identification information acquisition request to the Internet access module 6 again.

[0062] In some embodiments, the third threshold is set to 3 times. If the number of times the module management module 5 obtains null data from the Internet access module 6 reaches 3 times and null data is still obtained after 3 times, it sends a preset default value to the vehicle information management module 2.

[0063] Further, if the number of times that the Internet access module 6 fails to reply after exceeding the set duration reaches 3 times, or the number of times of obtaining null value data reaches 3 times, it can be set that the module management module 5 sends a preset default value to the vehicle information management module 2.

[0064] If the number of times of obtaining null value data reaches 3 times, it can be set that the Internet access module 6 replies a preset default value to the module management module 5, and the module management module 5 sends the preset default value to the vehicle information management module 2.

[0065] Further, the Internet access identification information includes the SIM card number and / or the International Mobile Subscriber Identity, etc.

[0066] According to some embodiments, the TBOX device further includes a cloud communication module 7, and the method further includes: Step 601, establish a Socket connection between the cloud communication module 7 and the cloud 8, and obtain the vehicle device 1 management remote configuration information sent by the cloud 8; Step 602, the cloud communication module 7 forwards the device management remote configuration information to the vehicle information management module 2, and the vehicle information management module 2 forwards the device management remote configuration information to the vehicle device 1.

[0067] Based on the above embodiments, as Figure 6 shown, Figure 6 A flowchart of obtaining the device management remote configuration information is shown. The TBOX device further includes a cloud communication module 7. When the vehicle device 1 needs remote configuration information, it enters Step 601 to establish a Socket connection between the cloud communication module 7 and the cloud 8. After the Socket connection is successful, the vehicle device management remote configuration information sent by the cloud 8 is received by the cloud communication module 7. Then it enters Step 602. The cloud communication module 7 forwards the device management remote configuration information to the vehicle information management module 2. After the vehicle information management module 2 receives the device management remote configuration information sent by the cloud communication module 7, it forwards the device management remote configuration information to the vehicle device 1.

[0068] According to some embodiments, after the vehicle information management module 2 forwards the device management remote configuration information to the vehicle device 1, the method further includes: obtaining the update success information sent by the vehicle device 1 for the device management remote configuration information; the vehicle information management module 2 forwards the update success information to the cloud communication module 7, and the cloud communication module 7 feeds back the update success information to the cloud 8.

[0069] Based on the above embodiments, after the vehicle information management module 2 forwards the device management remote configuration information to the in-vehicle device 1, the in-vehicle device 1 needs to perform a configuration update. After the update is completed, the in-vehicle device 1 sends a successful update message for the device management remote configuration information to the vehicle information management module 2. After the vehicle information management module 2 receives the successful update message for the device management remote configuration information sent by the in-vehicle device 1, the vehicle information management module 2 forwards the successful update message to the cloud communication module 7. After the cloud communication module 7 receives the successful update message sent by the vehicle information management module 2, it feeds back the successful update message to the cloud 8.

[0070] According to some embodiments, after the vehicle information management module 2 forwards the device management remote configuration information to the in-vehicle device 1, the method further includes: if the vehicle information management module 2 does not obtain a successful update message for the device management remote configuration information sent by the in-vehicle device 1 within a preset time, the vehicle information management module 2 forwards the device management remote configuration information to the in-vehicle device 1 again; if the number of times the vehicle information management module 2 forwards the device management remote configuration information to the in-vehicle device 1 again exceeds a fourth threshold, the cloud communication module 7 feeds back an update failure message to the cloud 8.

[0071] Based on the above embodiments, after the vehicle information management module 2 forwards the device management remote configuration information to the in-vehicle device 1, if the vehicle information management module 2 does not obtain a successful update message for the device management remote configuration information sent by the in-vehicle device 1 within a preset time, the vehicle information management module 2 forwards the device management remote configuration information to the in-vehicle device 1 again. Among them, the preset time can be set according to actual needs. In some embodiments, the preset time is set to 3 seconds. After the vehicle information management module 2 forwards the device management remote configuration information to the in-vehicle device 1, if the vehicle information management module 2 does not obtain a successful update message for the device management remote configuration information sent by the in-vehicle device 1 within 3 seconds, the vehicle information management module 2 forwards the device management remote configuration information to the in-vehicle device 1 again.

[0072] In some embodiments, the fourth threshold is set to 5 times. When the number of repetitions of the vehicle information management module 2 forwarding the device management remote configuration information to the in-vehicle device 1 again reaches the 5th time and the vehicle information management module 2 still does not obtain a successful update message for the device management remote configuration information sent by the in-vehicle device 1 within the preset time at the 5th time, the vehicle information management module 2 feeds back an update failure message to the cloud 8 through the cloud communication module 7.

[0073] According to some embodiments, the device management remote configuration information includes in-vehicle language configuration information and / or WIFI configuration information.

[0074] In traditional vehicle communication methods, abnormal handling such as communication timeouts is not reflected, and the internal parts of the T-BOX are not divided into independent modules, making it difficult to ensure the reliability of its functions. In this application, through the design of modules such as the in-vehicle information management module, MCU management module, MCU, Internet access module, and module management module inside the T-BOX, reliable interaction for the T-BOX to obtain device information from the in-vehicle unit is completed, and corresponding timeout and retry mechanisms are designed to improve the reliability of information interaction between the in-vehicle unit and the T-BOX.

[0075] Figure 7 The structural schematic diagram of a computer system of an electronic device suitable for implementing the embodiments of the present application is shown.

[0076] It should be noted that Figure 7 The computer system 700 of the electronic device shown is only an example and should not impose any limitations on the functions and usage scope of the embodiments of the present application.

[0077] As Figure 7 shown, the computer system 700 includes a central processing unit (CPU) 701, which can perform various appropriate actions and processes according to the program stored in the read-only memory (ROM) 702 or the program loaded from the storage section 708 into the random access memory (RAM) 703, such as executing the vehicle communication method described in the above embodiments. In the RAM 703, various programs and data required for system operation are also stored. The CPU 701, ROM 702, and RAM 703 are connected to each other through a bus 704. The input / output (I / O) interface 705 is also connected to the bus 704.

[0078] The following components are connected to the I / O interface 705: an input section 706 including a keyboard, a mouse, etc.; an output section 707 including, for example, a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker, etc.; a storage section 708 including a hard disk, etc.; and a communication section 709 including a network interface card such as a LAN (Local Area Network) card, a modem, etc. The communication section 709 performs communication processing via a network such as the Internet. A drive 710 is also connected to the I / O interface 705 as needed. A removable medium 711, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 710 as needed so that a computer program read therefrom is installed into the storage section 708 as needed.

[0079] Specifically, according to an embodiment of the present application, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, an embodiment of the present application includes a computer program product that includes a computer program carried on a computer-readable medium, and the computer program includes program codes for performing the methods shown in the flowcharts. In such an embodiment, the computer program can be downloaded and installed from a network via the communication section 709, and / or installed from the removable medium 711. When the computer program is executed by a central processing unit (CPU) 701, various functions defined in the system of the present application are executed.

[0080] It should be noted that the computer-readable medium shown in the embodiments of the present application can be a computer-readable signal medium, a computer-readable storage medium, or any combination of the two. A computer-readable storage medium can be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the above. More specific examples of a computer-readable storage medium can include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM), a flash memory, an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present application, a computer-readable storage medium can be any tangible medium that contains or stores a program, and this program can be used by or in combination with an instruction execution system, apparatus, or device. In the present application, a computer-readable signal medium can include a data signal propagated in a baseband or as part of a carrier wave, which carries computer-readable program code. Such a propagated data signal can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. A computer-readable signal medium can also be any computer-readable medium other than a computer-readable storage medium, and this computer-readable medium can send, propagate, or transmit a program for use by or in combination with an instruction execution system, apparatus, or device. The program code contained on a computer-readable medium can be transmitted using any appropriate medium, including but not limited to: wireless, wired, etc., or any suitable combination of the above.

[0081] The flowcharts and block diagrams in the accompanying drawings illustrate the possible architectures, functions, and operations of systems, methods, and computer program products according to various embodiments of the present application. Among them, each block in the flowchart or block diagram can represent a module, a program segment, or a part of code, and the above module, program segment, or part of code contains one or more executable instructions for implementing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the blocks may occur in a different order from that marked in the accompanying drawings. For example, two consecutive blocks shown may actually be executed substantially in parallel, and they may sometimes be executed in the reverse order, depending on the functions involved. It should also be noted that each block in the block diagram or flowchart, and the combination of blocks in the block diagram or flowchart, can be implemented by a dedicated hardware-based system for performing the specified functions or operations, or can be implemented by a combination of dedicated hardware and computer instructions.

[0082] The units involved in the embodiments of the present application can be implemented in software or in hardware, and the described units can also be provided in a processor. In some cases, the names of these units do not constitute a limitation on the units themselves.

[0083] As another aspect, the present application also provides a computer program product or a computer program. The computer program product or the computer program includes computer instructions stored in a computer-readable storage medium. The processor of the electronic device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions to cause the electronic device to execute the vehicle communication method described in the above embodiments.

[0084] As another aspect, the present application also provides a computer-readable medium. The computer-readable medium may be included in the electronic device described in the above embodiments, or may exist separately without being assembled into the electronic device. The above computer-readable medium carries one or more programs. When the above one or more programs are executed by an electronic device, the electronic device is caused to implement the vehicle communication method described in the above embodiments.

[0085] It should be noted that although several modules or units of the device for action execution are mentioned in the above detailed description, this division is not mandatory. In fact, according to the embodiments of the present application, the features and functions of the two or more modules or units described above can be embodied in one module or unit. Conversely, the features and functions of one module or unit described above can be further divided and embodied by multiple modules or units.

[0086] From the description of the above embodiments, those skilled in the art can easily understand that the example embodiments described herein can be implemented in software or in a manner of software combined with necessary hardware. Therefore, the technical solutions according to the embodiments of the present application can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (such as a CD-ROM, a USB flash drive, a mobile hard disk, etc.) or on a network, including several instructions to cause a computing device (such as a personal computer, a server, a touch terminal, or a network device, etc.) to execute the vehicle communication method described in the above embodiments.

[0087] After considering the specification and practicing the disclosed embodiments herein, those skilled in the art will readily conceive of other embodiments of the present application. The present application is intended to cover any variations, uses, or adaptations of the present application, which follow the general principles of the present application and include known common knowledge or conventional technical means in the technical field not disclosed in the present application.

[0088] It should be understood that the present application is not limited to the exact structures described above and shown in the drawings, and various modifications and changes can be made without departing from its scope. The scope of the present application is only limited by the appended claims.

Claims

1. A vehicle communication method, characterized in that, The method is executed on a TBOX device, which includes a vehicle information management module, an MCU management module, and an MCU. The method includes: Establish a Socket connection between the in-vehicle device and the TBOX device; The vehicle information management module obtains a vehicle identification code acquisition request sent by the in-vehicle device; The vehicle information management module forwards the vehicle identification code acquisition request to the MCU management module, and the MCU management module forwards the vehicle identification code acquisition request to the MCU to obtain a vehicle identification code from the MCU; After the MCU management module obtains the vehicle identification code from the MCU, the MCU management module forwards the vehicle identification code to the vehicle information management module; The vehicle information management module forwards the vehicle identification code to the in-vehicle device to confirm whether the vehicle identification codes of the in-vehicle device and the TBOX device are consistent; After the MCU management module forwards the vehicle identification code acquisition request to the MCU, the method further includes: If the MCU management module obtains null data from the MCU, the vehicle identification code acquisition request is re-forwarded to the MCU; If the number of times the MCU management module obtains null data from the MCU exceeds a first threshold, a preset default value is sent to the vehicle information management module; The vehicle information management module sends the preset default value to the in-vehicle device.

2. The method according to claim 1, wherein Before the vehicle information management module forwards the vehicle identification code acquisition request to the MCU management module, the method further includes: In response to the vehicle's power-on, the in-vehicle device sends a handshake request to the vehicle information management module; After the vehicle information management module receives the handshake request, the vehicle information management module sends a handshake response to the in-vehicle device to maintain the Socket connection between the in-vehicle device and the TBOX device.

3. The method according to claim 1, characterized in that, The method further includes: The vehicle information management module obtains a version number acquisition request sent by the in-vehicle device; The vehicle information management module forwards the version number acquisition request to the MCU management module, and the MCU management module forwards the version number acquisition request to the MCU to obtain a version number from the MCU; After the MCU management module obtains the version number from the MCU, the MCU management module forwards the version number to the vehicle information management module; The vehicle information management module forwards the version number to the in-vehicle device.

4. The method according to claim 3, characterized in that After the MCU management module forwards the version number acquisition request to the MCU, the method further includes: If the MCU management module obtains null data from the MCU, the version number acquisition request is re-forwarded to the MCU; If the number of times the MCU management module obtains null data from the MCU exceeds a second threshold, a preset default value is sent to the vehicle information management module; The vehicle information management module sends the preset default value to the in-vehicle device.

5. The method according to claim 3 or 4, characterized in that, The version number includes a hardware version number and / or a software version number.

6. The method according to claim 1, characterized in that The TBOX device further includes an Internet access module and a module management module, and the method further includes: The vehicle information management module obtains an Internet access identification information acquisition request sent by the in-vehicle device. The vehicle information management module forwards the Internet access identification information acquisition request to the module management module, and the module management module forwards the Internet access identification information acquisition request to the Internet access module to obtain Internet access identification information from the Internet access module. After the module management module obtains the Internet access identification information from the Internet access module, the module management module forwards the Internet access identification information to the vehicle information management module. The vehicle information management module forwards the Internet access identification information to the in-vehicle device.

7. The method according to claim 6, characterized in that, After the module management module forwards the Internet access identification information acquisition request to the Internet access module, the method further includes: If the module management module obtains null data from the Internet access module, the Internet access identification information acquisition request is resent to the Internet access module. If the number of times the module management module obtains null data from the Internet access module exceeds a third threshold, a preset default value is sent to the vehicle information management module. The vehicle information management module sends the preset default value to the in-vehicle device.

8. The method according to claim 6 or 7, characterized in that, The Internet access identification information includes a SIM card number and / or an International Mobile Subscriber Identity.

9. The method according to claim 1, characterized in that, The TBOX device further includes a cloud communication module, and the method further includes: A Socket connection is established between the cloud communication module and the cloud, and vehicle in-vehicle device management remote configuration information sent by the cloud is obtained. The cloud communication module forwards the device management remote configuration information to the vehicle information management module, and the vehicle information management module forwards the device management remote configuration information to the in-vehicle device.

10. The method according to claim 9, wherein After the vehicle information management module forwards the device management remote configuration information to the in-vehicle device, the method further includes: Obtaining update success information for the device management remote configuration information sent by the in-vehicle device. The vehicle information management module forwards the update success information to the cloud communication module, and the cloud communication module feeds back the update success information to the cloud.

11. The method according to claim 9, characterized in that, After the vehicle information management module forwards the device management remote configuration information to the in-vehicle device, the method further includes: If update success information for the device management remote configuration information sent by the in-vehicle device is not obtained within a preset time, the vehicle information management module forwards the device management remote configuration information to the in-vehicle device again. If the number of times the vehicle information management module forwards the device management remote configuration information to the in-vehicle device again exceeds a fourth threshold, update failure information is fed back to the cloud through the cloud communication module.

12. The method according to any one of claims 9 to 11, characterized in that, The device management remote configuration information includes in-vehicle unit language configuration information and / or WIFI configuration information.

13. A computer-readable storage medium, characterized in that, At least one program code is stored in the computer-readable storage medium, and the at least one program code is loaded and executed by a processor to implement the operations performed by the method according to any one of claims 1 to 12.

14. An electronic device, characterized in that, The electronic device includes one or more processors and one or more memories. At least one program code is stored in the one or more memories, and the at least one program code is loaded and executed by the one or more processors to implement the operations performed by the method according to any one of claims 1 to 12.

Images