Communication method of vehicle-mounted terminal equipment and server, TSP signaling channel and equipment
By using a Java-based TSP signaling channel and AKKA to achieve data synchronization between MQTT Broker nodes, the high cost and difficulty in customization of vehicle equipment terminals are solved, enabling high-throughput, low-latency vehicle data transmission and stable control.
Patent Information
- Application Number
- CN202510788367.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-06-12
- Publication Date
- 2025-10-31
AI Technical Summary
In existing technologies, the EMQ of vehicle equipment terminals has high usage costs, high learning and maintenance costs, and is difficult to customize, resulting in unstable real-time reporting of vehicle data and transmission of control commands.
It adopts a TSP signaling channel based on Java, uses AKKA to realize data synchronization between MQTT Broker nodes, supports dynamic expansion and contraction of nodes, provides message level support for MQTT protocol QoS0, QoS1, and QoS2, provides heartbeat keep-alive capability and device shadow capability, and saves resource overhead.
It achieves high-throughput, low-latency vehicle data transmission, reduces resource consumption, supports dynamic device connectivity and customized development, and improves system stability and flexibility.
Smart Images
Figure CN120881089A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of vehicle technology, and in particular to a communication method between an in-vehicle terminal device and a server, a TSP signaling channel and device. Background Technology
[0002] In the field of vehicle networking, vehicle national standard data, vehicle basic management data, and vehicle fault alarm data need to be reported, analyzed, and monitored in real time, while also meeting the requirements for vehicle cloud control. However, vehicles are constantly in motion, and weak signals, insufficient computing power, and limited network bandwidth are characteristics of vehicle device terminals. This means that devices receiving vehicle data must simultaneously meet the characteristics of real-time and continuous data reporting. Traditional HTTP services have excessively large data packet headers, wasting bandwidth and easily causing data upload delays when signals are weak. Existing technologies can achieve this using EMQ combined with message queues. The main process is as follows: the vehicle device terminal interacts with the backend application through EMQ, uploading data; the backend application analyzes and monitors the vehicle data; the backend application sends control commands to the vehicle device terminal through EMQ, and the vehicle executes the control commands. However, the following technical problems exist:
[0003] EMQ is commercial software, and for startups, the cost of using it is an important expense to consider in order to provide stable service. EMQ is implemented in Erlang, which means that the learning and maintenance costs are high for Java or other language developers. There is also the issue of customization; for Java developers, it is difficult to customize EMQ to their own business needs. Summary of the Invention
[0004] Based on this, it is necessary to address the aforementioned technical issues by providing a communication method between the vehicle-mounted terminal device and the server, a TSP signaling channel and device, and a high-throughput, low-latency TSP signaling channel implemented in Java. This signaling channel uses AKKA to implement data synchronization between MQTT Broker nodes, supports dynamic node expansion and contraction, supports several versions of device registration and connection, provides support for MQTT protocol QoS0, QoS1, and QoS2 message levels, provides heartbeat keep-alive capability to save unnecessary resource overhead, provides an MQTT event synchronization mechanism to enable users to handle business logic based on MQTT events, provides device shadow capability, and provides mutual disconnection capability when devices are connected.
[0005] Firstly, a communication method for an in-vehicle terminal device and a server is provided. The in-vehicle terminal device and the server communicate based on a TSP signaling channel implemented in Java. The TSP signaling channel includes an MQTT server, an MQ message middleware, and a Worker service. The communication method includes:
[0006] The Worker service listens for MQTT events and uplink / downlink messages;
[0007] After receiving an uplink message from the vehicle terminal device, the uplink message is decoded and sent to the server.
[0008] Upon receiving a downlink message from the server, the downlink message is encoded and sent to the MQTT server via the MQ message middleware, so that the MQTT server can send it to the vehicle terminal device.
[0009] In some examples, the MQTT server includes multiple MQTT Broker nodes, the MQTT Broker nodes use AKKA to achieve data synchronization between the MQTT Broker nodes, and the MQTT server communicates with the vehicle terminal device.
[0010] The MQ message middleware communicates with the MQTT server;
[0011] The Worker service is used to listen for MQTT events and uplink and downlink messages, decode uplink messages from the vehicle terminal device and send them to the server, encode downlink messages from the server and send them to the MQTT server through the MQ message middleware, so that the MQTT server can forward them to the vehicle terminal device.
[0012] In some examples, it also includes:
[0013] The vehicle-mounted terminal device establishes a connection with the MQTT server and sends data or heartbeats to keep the device alive.
[0014] After receiving the message sent by the vehicle terminal, the MQTT server synchronizes the message to each MQTTBroker node. If the message is a connection establishment message, the server searches for a vehicle terminal device with the same ID on each MQTT Broker node. If a connection is found, the connection is closed, and the new connection is reserved.
[0015] If the message is a unicast message, the MQTT server will forward the message directly to the MQ message middleware;
[0016] The Worker service listens for uplink messages from the vehicle terminal device, decodes them, and sends them to the server so that the server can respond.
[0017] In some examples, it also includes:
[0018] After establishing a connection with the MQTT server, the vehicle-mounted terminal device reports data;
[0019] The MQTT server verifies the TOPIC publishing permission of the vehicle terminal device. If the verification is successful, it sends a success ACK to the vehicle terminal device; otherwise, it sends a failure ACK and error code to the vehicle terminal device.
[0020] After successful verification, the MQTT server sends the data to the Worker service for decoding and filtering, and then forwards it to the server.
[0021] In some examples, when the MQTT server sends data to the Worker service for decoding and filtering, and then forwards it to the server, it also includes: sending a response message to the vehicle terminal device.
[0022] In some examples, it also includes:
[0023] After receiving a user's operation, the server performs permission verification. If the verification is successful, the message is forwarded to the Worker service.
[0024] The Worker service encodes the message and then forwards it to the MQTT server;
[0025] After receiving the message, the MQTT server caches it and searches for the corresponding vehicle terminal device connection in each MQTT Broker node. If the connection is found, a message is sent to the vehicle terminal device.
[0026] The vehicle-mounted terminal device responds and sends a reply to the MQTT server;
[0027] After receiving the response, the MQTT server clears its cache and returns the execution result of the vehicle terminal device to the server.
[0028] Secondly, a Java-based TSP signaling channel is provided, comprising: an MQTT server, an MQ message middleware, and a Worker service, wherein:
[0029] The MQTT server includes multiple MQTT Broker nodes, and the MQTT Broker nodes use AKKA to achieve data synchronization between each MQTT Broker node. The MQTT server communicates with the vehicle terminal device.
[0030] The MQ message middleware communicates with the MQTT server;
[0031] The Worker service is used to listen for MQTT events and uplink and downlink messages, decode uplink messages from the vehicle terminal device and send them to the server, encode downlink messages from the server and send them to the MQTT server through the MQ message middleware, so that the MQTT server can forward them to the vehicle terminal device.
[0032] Thirdly, a computer device is provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the program, it implements the steps of a communication method between an in-vehicle terminal device and a server, as described in the first aspect and any possible implementation of the first aspect.
[0033] Fourthly, a computer-readable storage medium is provided, on which a computer program is stored, which, when executed by a processor, implements the steps of the communication method between the vehicle-mounted terminal device and the server of the first aspect and any possible implementation thereof.
[0034] Fifthly, a computer program product is provided, on which a computer program is stored, which, when executed by a processor, implements the steps of the communication method between the vehicle-mounted terminal device and the server in the first aspect and any possible implementation of the first aspect.
[0035] The embodiments of this application employ a high-throughput, low-latency TSP signaling channel implemented in Java. This signaling channel uses AKKA to implement data synchronization between MQTT Broker nodes, supports dynamic node expansion and contraction, supports several versions of device registration and connection, provides support for MQTT protocol QoS0, QoS1, and QoS2 message levels, provides heartbeat keep-alive capability to save unnecessary resource overhead, provides an MQTT event synchronization mechanism to enable users to process business logic based on MQTT events, provides device shadow capability, and provides mutual disconnection capability when devices are connected. Attached Figure Description
[0036] Other features, objects, and advantages of this application will become more apparent from the following detailed description of non-limiting embodiments with reference to the accompanying drawings:
[0037] Figure 1 This is a flowchart illustrating the communication method between the vehicle-mounted terminal device and the server provided in the embodiments of this application.
[0038] Figure 2 This is a schematic diagram of the TSP signaling channel for the communication method between the vehicle-mounted terminal device and the server provided in the embodiments of this application;
[0039] Figure 3This is a flowchart illustrating the uplink message processing of the communication method between the vehicle-mounted terminal device and the server provided in this embodiment.
[0040] Figure 4 This is a flowchart illustrating the downlink message processing of the communication method between the vehicle-mounted terminal device and the server provided in this application embodiment.
[0041] Figure 5 This is a structural block diagram of the computer device provided in the embodiments of this application. Detailed Implementation
[0042] The present application will now be described in further detail with reference to the embodiments and accompanying drawings. It should be understood that the specific embodiments described herein are for illustrative purposes only and are not intended to limit the application. Furthermore, it should be noted that, for ease of description, only the parts relevant to the application are shown in the accompanying drawings.
[0043] It should be noted that, unless otherwise specified, the embodiments and features of the embodiments in this application can be combined with each other. This application will now be described in detail with reference to the accompanying drawings and embodiments.
[0044] The following describes in detail, with reference to the accompanying drawings, the communication method of the vehicle-mounted terminal device and the server, the TSP signaling channel and the device according to embodiments of this application.
[0045] Figure 1 This is a flowchart illustrating a communication method between an in-vehicle terminal device and a server according to an embodiment of this application. The communication method involves the in-vehicle terminal device and the server communicating via a Java-implemented TSP signaling channel. Figure 2 As shown, the TSP signaling channel, implemented in Java, includes an MQTT server, an MQ message middleware, and a Worker service.
[0046] like Figure 1 As shown, the communication method between the vehicle-mounted terminal equipment and the server includes the following steps:
[0047] S101: The Worker service listens for MQTT events and upstream and downstream messages.
[0048] S102: After receiving an uplink message from the vehicle terminal device, decode the uplink message and send it to the server.
[0049] S103: After receiving a downlink message from the server, the downlink message is encoded and sent to the MQTT server through the MQ message middleware, so that the MQTT server can send it to the vehicle terminal device.
[0050] Among them: combination Figure 2As shown, the MQTT server includes multiple MQTT Broker nodes. The MQTT Broker nodes synchronize data between each MQTT Broker node through AKKA. The MQTT server communicates with the vehicle terminal device. The MQ message middleware communicates with the MQTT server. The Worker service listens for MQTT events and uplink / downlink messages, decodes uplink messages from the vehicle terminal device and sends them to the server, encodes downlink messages from the server and sends them to the MQTT server through the MQ message middleware, so that the MQTT server can forward them to the vehicle terminal device.
[0051] Specifically, the communication method between the vehicle terminal device and the server in this application embodiment utilizes a high-throughput, low-latency TSP signaling channel implemented in Java. The underlying layer of this signaling channel can adopt the non-blocking Netty framework to improve concurrency capabilities, use AKKA to implement data synchronization between MQTT Broker nodes, support dynamic expansion and contraction of nodes, support several versions of device registration and connection, provide support for MQTT protocol QoS0, QoS1, and QoS2 message levels, provide heartbeat keep-alive capability to save unnecessary resource overhead, provide an MQTT event synchronization mechanism to enable users to process business logic based on MQTT events, provide device shadow capability, and provide mutual disconnection capability when devices are connected.
[0052] In one embodiment of this application, a communication method between an in-vehicle terminal device and a server includes: the in-vehicle terminal device establishing a connection with an MQTT server and sending data or a heartbeat keep-alive mechanism; after receiving a message sent by the in-vehicle terminal, the MQTT server synchronizes the message to each MQTT Broker node, wherein if the message is a connection establishment message, the server searches for an in-vehicle terminal device with the same ID on each MQTT Broker node, closes the connection when found, and retains the new connection; if the message is a unicast message, the MQTT server directly forwards the message to the MQ message middleware; the Worker service listens for uplink messages from the in-vehicle terminal device, decodes them, and sends them to the server so that the server can respond.
[0053] Combination Figure 2As shown, the device establishes a connection with the MQTT Broker and sends data or heartbeats to keep it alive. Upon receiving a message, the MQTT server synchronizes it to the cluster nodes. If it's a connection establishment message, it searches for a client with the same clientID across the cluster, closes that client, and retains the new connection. If it's a unicast message (such as GBT32960 or vehicle alarm data), the Broker directly forwards it to the MQ message middleware for processing by the backend application. The Worker service listens for MQTT events and uplink / downlink messages, decodes uplink messages and forwards them to the backend, encodes downlink messages and forwards them to the MQTT server, which then forwards them to the device. The backend application performs statistical analysis and storage of the data. Here, "backend application" refers to the server, and "device" refers to the in-vehicle terminal device.
[0054] In one embodiment of this application, the communication method between the vehicle-mounted terminal device and the server further includes: after the vehicle-mounted terminal device establishes a connection with the MQTT server, it reports data; the MQTT server verifies the TOPIC publishing permission of the vehicle-mounted terminal device, and if the verification passes, it replies with a success ACK to the vehicle-mounted terminal device; otherwise, it replies with a failure ACK and an error code to the vehicle-mounted terminal device; after the verification passes, the MQTT server sends the data to the Worker service for decoding and filtering, and then forwards it to the server.
[0055] Furthermore, when the MQTT server sends data to the Worker service for decoding and filtering, and then forwards it to the server, it also includes: sending a response message to the vehicle terminal device.
[0056] Specifically, combining Figure 3 As shown, after the device establishes a connection, it begins to report data. The Broker verifies the device's TOPIC publishing permission. If successful, it replies with a success ACK; if unsuccessful, it replies with a failure ACK and an error code. The Broker then forwards the data to the Worker layer for decoding and filtering (and, if necessary, replies with a response message to the device) and forwards it to the backend application.
[0057] In one embodiment of this application, the communication method between the vehicle-mounted terminal device and the server further includes: after receiving a user operation, the server performs permission verification, and if the verification is successful, forwards the message to the Worker service; the Worker service encodes the message and forwards it to the MQTT server; after receiving the message, the MQTT server caches it and searches for the corresponding vehicle-mounted terminal device connection in each MQTTBroker node; if found, it sends a message to the vehicle-mounted terminal device; the vehicle-mounted terminal device responds and sends a reply to the MQTT server; after receiving the reply, the MQTT server clears the cache and returns the execution result of the vehicle-mounted terminal device to the server.
[0058] Specifically, such as Figure 4 As shown, the backend application receives user operations and performs permission verification. If the verification is successful, the application forwards the command to the Worker. The Worker encodes the data and forwards it to the Broker. Upon receiving the command, the Broker caches it and searches for client connections within the cluster. If a connection is found, the Broker sends a message to the terminal. The terminal executes the command and sends an ACK response to the Broker. Upon receiving the ACK, the Broker clears the command cache and returns the execution result to the backend application.
[0059] The communication method between the vehicle-mounted terminal device and the server in this application is implemented in Java and uses the non-blocking Netty framework, providing high concurrency capabilities. Data synchronization between nodes is achieved using AKKA, supporting horizontal scaling and effectively improving high availability. It is Java developer-friendly, easy to learn, and allows for customization. Encoding and decoding capabilities are entirely handled by the Worker layer, making the Broker more stable and reliable, requiring no logic modification or redeployment under normal circumstances. MQTT event notifications facilitate application-level business logic processing for specific event types. A robust logging system makes it easier to locate potential anomalies and help terminal devices locate unknown anomalies. It also supports large file chunked uploads and fast file transfers using the MQTT protocol, simplifying large-volume data transfers for users.
[0060] The communication method between the vehicle terminal device and the server according to the embodiments of this application is based on a high-throughput, low-latency TSP signaling channel implemented in Java. This signaling channel uses AKKA to implement data synchronization between MQTT Broker nodes, supports dynamic expansion and contraction of nodes, supports several versions of device registration and connection, provides support for MQTT protocol QoS0, QoS1, and QoS2 message levels, provides heartbeat keep-alive capability, saves unnecessary resource overhead, provides an MQTT event synchronization mechanism, provides device shadow capability for users to process business logic based on MQTT events, and provides mutual disconnection capability when devices are connected.
[0061] Combination Figure 2 As shown, the TSP signaling channel implemented in Java according to an embodiment of this application includes: an MQTT server, an MQ message middleware, and a Worker service, wherein:
[0062] The MQTT server includes multiple MQTT Broker nodes, and the MQTT Broker nodes use AKKA to achieve data synchronization between each MQTT Broker node. The MQTT server communicates with the vehicle terminal device.
[0063] The MQ message middleware communicates with the MQTT server;
[0064] The Worker service is used to listen for MQTT events and uplink and downlink messages, decode uplink messages from the vehicle terminal device and send them to the server, encode downlink messages from the server and send them to the MQTT server through the MQ message middleware, so that the MQTT server can forward them to the vehicle terminal device.
[0065] The TSP signaling channel implemented in Java according to the embodiments of this application is a high-throughput, low-latency TSP signaling channel implemented in Java. This signaling channel uses AKKA to implement data synchronization between MQTT Broker nodes, supports dynamic expansion and contraction of nodes, supports several versions of device registration and connection, provides support for MQTT protocol QoS0, QoS1, and QoS2 message levels, provides heartbeat keep-alive capability to save unnecessary resource overhead, provides an MQTT event synchronization mechanism to enable users to process business logic based on MQTT events, provides device shadow capability, and provides mutual disconnection capability when devices are connected.
[0066] Specific limitations regarding the Java-based TSP signaling channel can be found in the above description of the communication method between the vehicle-mounted terminal device and the server, and will not be repeated here. The various modules of the Java-based TSP signaling channel can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in or independent of the processor in the computer device, or stored in the computer device's memory as software, so that the processor can call and execute the corresponding operations of each module.
[0067] In one embodiment, a computer device is provided. Figure 5 This is a structural block diagram of the computer device provided in the embodiments of this application, with reference to... Figure 5 The computer device includes a memory and a processor. The memory stores a computer program, and the processor executes the computer program to implement the aforementioned communication method embodiment between the vehicle-mounted terminal device and the server. For example, it executes: the Worker service listens for MQTT events and uplink and downlink messages;
[0068] After receiving an uplink message from the vehicle terminal device, the uplink message is decoded and sent to the server.
[0069] Upon receiving a downlink message from the server, the downlink message is encoded and sent to the MQTT server via the MQ message middleware, so that the MQTT server can send it to the vehicle terminal device.
[0070] This application also provides a computer-readable storage medium storing a computer program. When the processor executes the computer program, it implements the aforementioned communication method embodiment between the vehicle-mounted terminal device and the server. For example, it executes: the Worker service listens for MQTT events and uplink / downlink messages;
[0071] After receiving an uplink message from the vehicle terminal device, the uplink message is decoded and sent to the server.
[0072] Upon receiving a downlink message from the server, the downlink message is encoded and sent to the MQTT server via the MQ message middleware, so that the MQTT server can send it to the vehicle terminal device.
[0073] This application provides a computer program product including instructions that, when executed, cause the method described in this application embodiment to be performed. For example, it can execute... Figure 1 The various steps of the communication method between the vehicle-mounted terminal device and the server shown include, for example, the Worker service listening for MQTT events and uplink and downlink messages;
[0074] After receiving an uplink message from the vehicle terminal device, the uplink message is decoded and sent to the server.
[0075] Upon receiving a downlink message from the server, the downlink message is encoded and sent to the MQTT server via the MQ message middleware, so that the MQTT server can send it to the vehicle terminal device.
[0076] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium, and when executed, it can include the processes of the embodiments of the methods described above. Any references to memory, storage, databases, or other media used in the embodiments provided in this application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, or optical storage, etc. Volatile memory can include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM), etc.
[0077] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.
[0078] The above embodiments merely illustrate several implementation methods of this application, and while the descriptions are relatively specific and detailed, they should not be construed as limiting the scope of the patent application. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this patent application should be determined by the appended claims.
Claims
1. A communication method between a vehicle-mounted terminal device and a server, characterized in that, The vehicle-mounted terminal device and the server communicate via a TSP signaling channel implemented in Java. The TSP signaling channel includes an MQTT server, an MQ message middleware, and a Worker service. The communication method includes: The Worker service listens for MQTT events and uplink / downlink messages; After receiving an uplink message from the vehicle terminal device, the uplink message is decoded and sent to the server. Upon receiving a downlink message from the server, the downlink message is encoded and sent to the MQTT server via the MQ message middleware, so that the MQTT server can send it to the vehicle terminal device.
2. The communication method between the vehicle-mounted terminal equipment and the server according to claim 1, characterized in that, in: The MQTT server includes multiple MQTT Broker nodes, and the MQTT Broker nodes use AKKA to achieve data synchronization between each MQTT Broker node. The MQTT server communicates with the vehicle terminal device. The MQ message middleware communicates with the MQTT server; The Worker service is used to listen for MQTT events and uplink and downlink messages, decode uplink messages from the vehicle terminal device and send them to the server, encode downlink messages from the server and send them to the MQTT server through the MQ message middleware, so that the MQTT server can forward them to the vehicle terminal device.
3. The communication method between the vehicle-mounted terminal equipment and the server according to claim 1 or 2, characterized in that, Also includes: The vehicle-mounted terminal device establishes a connection with the MQTT server and sends data or heartbeats to keep the device alive. After receiving the message sent by the vehicle terminal, the MQTT server synchronizes the message to each MQTT Broker node. If the message is a connection establishment message, the server searches for a vehicle terminal device with the same ID on each MQTT Broker node. If a connection is found, the connection is closed, and the new connection is retained. If the message is a unicast message, the MQTT server will forward the message directly to the MQ message middleware; The Worker service listens for uplink messages from the vehicle terminal device, decodes them, and sends them to the server so that the server can respond.
4. The communication method between the vehicle-mounted terminal equipment and the server according to claim 3, characterized in that, Also includes: After establishing a connection with the MQTT server, the vehicle-mounted terminal device reports data; The MQTT server verifies the TOPIC publishing permission of the vehicle terminal device. If the verification is successful, it sends a success ACK to the vehicle terminal device; otherwise, it sends a failure ACK and error code to the vehicle terminal device. After successful verification, the MQTT server sends the data to the Worker service for decoding and filtering, and then forwards it to the server.
5. The communication method between the vehicle-mounted terminal equipment and the server according to claim 4, characterized in that, When the MQTT server sends data to the Worker service for decoding and filtering, and then forwards it to the server, it also includes: sending a response message to the vehicle terminal device.
6. The communication method between the vehicle-mounted terminal equipment and the server according to claim 3, characterized in that, Also includes: After receiving a user's operation, the server performs permission verification. If the verification is successful, the message is forwarded to the Worker service. The Worker service encodes the message and then forwards it to the MQTT server; After receiving the message, the MQTT server caches it and searches for the corresponding vehicle terminal device connection in each MQTT Broker node. If the connection is found, a message is sent to the vehicle terminal device. The vehicle-mounted terminal device responds and sends a reply to the MQTT server; After receiving the response, the MQTT server clears its cache and returns the execution result of the vehicle terminal device to the server.
7. A TSP signaling channel implemented in Java, characterized in that, The TSP signaling channel includes: an MQTT server, an MQ message middleware, and a Worker service, wherein: The MQTT server includes multiple MQTT Broker nodes, and the MQTT Broker nodes use AKKA to achieve data synchronization between each MQTT Broker node. The MQTT server communicates with the vehicle terminal device. The MQ message middleware communicates with the MQTT server; The Worker service is used to listen for MQTT events and uplink and downlink messages, decode uplink messages from the vehicle terminal device and send them to the server, encode downlink messages from the server and send them to the MQTT server through the MQ message middleware, so that the MQTT server can forward them to the vehicle terminal device.
8. A computer device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the program, it implements the communication method between the vehicle terminal device and the server as described in any one of claims 1-6.
9. A computationally readable storage medium, comprising a memory and a computer program stored on the memory and executable on a processor, characterized in that, When the program is executed by the processor, it implements the communication method between the vehicle terminal device and the server according to any one of claims 1-6.
10. A computer program product, comprising a memory and a computer program stored in the memory and executable on a processor, characterized in that, When the program is executed by the processor, it implements the communication method between the vehicle terminal device and the server according to any one of claims 1-6.