A vehicle communication method, device, equipment and medium

Abstract

The application provides a vehicle communication method, device, equipment and medium. The method comprises the following steps: receiving a communication connection request sent by a vehicle end; the communication connection request carries a subscription topic and to-be-processed data; sending the communication connection request to a cloud end, so that the cloud end processes the to-be-processed data to obtain target data; and so that the cloud end publishes the target data to the subscription topic to generate a target topic; receiving the target topic sent by the cloud end; and sending the target topic to the vehicle end. The technical scheme of the application does not need to configure a special hardware device as a transmission communication intermediary, can shorten the transmission link, ensure the transmission response speed when a large amount of data is transmitted, and improve the data transmission efficiency.

Description

Technical Field

[0001] This application relates to the field of intelligent driving technology, and in particular to a vehicle communication method, device, equipment and medium. Background Technology

[0002] Currently, with the development of intelligent driving technology, vehicles generate a large amount of data that needs to communicate and interact with the cloud. For example... Figure 1 As shown, in the existing technology, when the data generated by the vehicle needs to communicate and interact with the cloud, a dedicated hardware device needs to be configured as a communication intermediary to realize the data transmission. The hardware devices corresponding to each vehicle are not universal, the data communication process is complicated, the transmission link is long, and the data transmission efficiency is low. Summary of the Invention

[0003] This application provides a vehicle communication method, apparatus, device, and medium to overcome the shortcomings of the prior art. It eliminates the need for dedicated hardware as a transmission communication intermediary, shortens the transmission link, ensures fast transmission response when transmitting large amounts of data, and improves data transmission efficiency.

[0004] To solve the above-mentioned technical problems, this application provides the following technical solution:

[0005] On one hand, embodiments of this application provide a vehicle communication method, including:

[0006] Receive a communication connection request sent by the vehicle terminal; the communication connection request carries the subscription topic and the data to be processed;

[0007] The communication connection request is sent to the cloud so that the cloud can process the data to be processed to obtain the target data; and the cloud can publish the target data to the subscribed topic to generate the target topic.

[0008] Receive the target topic sent by the cloud;

[0009] Send the target topic to the vehicle terminal.

[0010] In one exemplary embodiment, the method further includes:

[0011] Receive a registration request sent by the vehicle terminal; the registration request carries the registration information of the vehicle terminal;

[0012] The registration request is sent to the cloud so that the cloud can query the registration status information corresponding to the registration information.

[0013] Receive the registration status information sent from the cloud;

[0014] If the registration status information indicates that the vehicle has registered in the cloud, then the operation of receiving the communication connection request sent by the vehicle is executed.

[0015] In one exemplary implementation, when the registration status information indicates that the vehicle has not registered in the cloud, the method further includes:

[0016] The registration information is encrypted to obtain encrypted registration information;

[0017] The encrypted registration information is sent to the cloud and the vehicle respectively.

[0018] In one exemplary implementation, sending the encrypted registration information to the cloud and the vehicle terminal respectively includes:

[0019] The encrypted registration information is sent to the cloud, so that the cloud changes the status type of the registration status information from "not registered on the cloud" to "registered on the cloud".

[0020] The encrypted registration information is sent to the vehicle terminal, so that the vehicle terminal updates the information content corresponding to the registration information to the information content corresponding to the encrypted registration information.

[0021] In one exemplary implementation, the communication connection request carries message publishing information, which is determined based on the data transmission rules corresponding to the subscribed topic. The communication connection request sent by the receiving vehicle includes:

[0022] Based on the message release information, the communication connection request sent by the vehicle terminal is received.

[0023] On the other hand, embodiments of this application provide a vehicle communication method, including:

[0024] The system receives a communication connection request from the server; the communication connection request is sent from the vehicle to the server; the communication connection request carries the subscribed topic and the data to be processed.

[0025] The data to be processed is then processed to obtain the target data;

[0026] The target data is published to the subscribed topic to generate the target topic;

[0027] The target topic is sent to the server, so that the server sends the target topic to the vehicle.

[0028] In one exemplary embodiment, the method further includes:

[0029] The system receives a registration request sent by the server; the registration request is sent from the vehicle to the server, and the registration request carries the vehicle's registration information.

[0030] Query the registration status information corresponding to the aforementioned registration information;

[0031] The registration status information is sent to the server so that the server can receive the communication connection request sent by the vehicle when the registration status information indicates that the vehicle has been registered locally in the cloud.

[0032] In one exemplary implementation, when the registration status information indicates that the vehicle has not registered on the local cloud, the method further includes:

[0033] The server receives encrypted registration information; the encrypted registration information is obtained by the server encrypting the registration information.

[0034] In one exemplary implementation, receiving the encrypted registration information sent by the server includes:

[0035] Receive the encrypted registration information sent by the server;

[0036] Change the status type of the registration status information from "not registered on the local cloud" to "registered on the local cloud".

[0037] On the other hand, embodiments of this application provide a vehicle communication device, the device comprising:

[0038] The first connection request receiving module is used to receive a communication connection request sent by the vehicle terminal; the communication connection request carries a subscription topic and data to be processed.

[0039] A connection request sending module is configured to send the communication connection request to the cloud, so that the cloud can process the data to be processed to obtain target data; and to enable the cloud to publish the target data to the subscribed topic to generate a target topic;

[0040] A target topic receiving module is used to receive the target topic sent by the cloud.

[0041] The first target topic sending module is used to send the target topic to the vehicle terminal.

[0042] On the other hand, embodiments of this application provide a vehicle communication device, the device comprising:

[0043] The second connection request receiving module is used to receive a communication connection request sent by the server; the communication connection request is sent from the vehicle to the server; the communication connection request carries the subscribed topic and the data to be processed.

[0044] The data processing module is used to process the data to be processed to obtain the target data;

[0045] The target topic generation module is used to publish the target data to the subscribed topic and generate the target topic;

[0046] The second target topic sending module is used to send the target topic to the server, so that the server sends the target topic to the vehicle terminal.

[0047] On the other hand, embodiments of this application provide an electronic device, including a processor and a memory, wherein the memory stores at least one instruction or at least one program, and the at least one instruction or the at least one program is loaded and executed by the processor to implement the vehicle communication method described above.

[0048] On the other hand, embodiments of this application provide a computer-readable storage medium storing at least one instruction or at least one program, wherein the at least one instruction or the at least one program is loaded and executed by a processor to implement the vehicle communication method described above.

[0049] By adopting the above technical solution, this application has the following beneficial effects:

[0050] This application provides a vehicle communication method, apparatus, device, and medium. The method involves a server receiving a communication connection request from a vehicle. The communication connection request carries a subscribed topic and data to be processed. The server then sends the communication connection request to the cloud, enabling the cloud to process the data to obtain target data. The cloud then publishes the target data to the subscribed topic, generating a target topic. The server then receives the target topic from the cloud and sends it back to the vehicle. This method enables communication between the vehicle and the cloud without requiring hardware as a communication intermediary, shortening the transmission link, ensuring fast response times when transmitting large amounts of data, and improving data transmission efficiency. Attached Figure Description

[0051] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0052] Figure 1 This is a schematic diagram illustrating the implementation environment of a vehicle communication method in the prior art.

[0053] Figure 2 A schematic diagram illustrating the implementation environment of a vehicle communication method provided in this application embodiment;

[0054] Figure 3 A flowchart illustrating a vehicle communication method provided in this application embodiment. Figure 1 ;

[0055] Figure 4 A flowchart illustrating a vehicle communication method provided in this application embodiment. Figure 2 ;

[0056] Figure 5 A flowchart illustrating a vehicle communication method provided in this application embodiment. Figure 3 ;

[0057] Figure 6 A flowchart illustrating a vehicle communication method provided in this application embodiment. Figure 4 ;

[0058] Figure 7 A flowchart illustrating a vehicle communication method provided in this application embodiment. Figure 5 ;

[0059] Figure 8 A structural frame of a vehicle communication device provided in this application embodiment Figure 1 ;

[0060] Figure 9 A structural frame of a vehicle communication device provided in this application embodiment Figure 2 ;

[0061] Figure 10 A structural frame of a vehicle communication device provided in this application embodiment Figure 3 ;

[0062] Figure 11 This is a hardware structure block diagram of an electronic device that operates a vehicle communication method, as provided in an embodiment of this application. Detailed Implementation

[0063] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of them. All other embodiments obtained by those skilled in the art based on the embodiments of this application without creative effort are within the scope of protection of this application.

[0064] The term "an embodiment" or "embodiment" as used herein refers to a specific feature, structure, or characteristic that may be included in at least one implementation of this application. In the description of the embodiments of this application, it should be understood that the terms "upper," "lower," "top," "bottom," etc., indicating orientation or positional relationships based on the orientation or positional relationships shown in the accompanying drawings, are only for the convenience of describing this application and simplifying the description, and do not indicate or imply that the referred device or element must have a specific orientation, or be constructed and operated in a specific orientation, and therefore should not be construed as a limitation of this application. Furthermore, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of indicated technical features. Thus, a feature defined with "first" and "second" may explicitly or implicitly include one or more of that feature. Moreover, the terms "first," "second," etc., are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms “comprising” and “having”, and any variations thereof, are intended to cover non-exclusive inclusion, such that a process, method, system, product, or server that includes a series of steps or units is not necessarily limited to those steps or units that are explicitly listed, but may include other steps or units that are not explicitly listed or that are inherent to such processes, methods, products, or devices.

[0065] Please see Figure 2 The diagram shown is a schematic representation of an implementation environment for a vehicle communication method provided in this application. Figure 2 As shown, this implementation environment can include at least a vehicle-side terminal, a server, and a cloud platform. The vehicle-side terminal, the server, and the cloud platform can be connected via wireless communication or intranet / local area network communication; this application does not impose any limitations on this connection. For example, the vehicle-side terminal can send communication connection requests and registration requests to the server via wireless communication. The server can send a target topic and encrypted registration information to the vehicle-side terminal via wireless communication. The server can also send the communication connection request and the encrypted registration information to the cloud platform via wireless communication, and the cloud platform can send the target topic to the server via wireless communication.

[0066] Specifically, the server is a Message Queuing Telemetry Transport Protocol (MQTTBroker) proxy server. The MQTTBroker enables communication between the vehicle and the cloud, eliminating the need for dedicated hardware on the vehicle as a communication intermediary. This shortens the transmission link, ensures faster transmission response when transmitting large amounts of data, and improves data transmission efficiency.

[0067] It should be noted that, Figure 2 This is just one example.

[0068] Please see Figure 3 The diagram shown is a flowchart of a vehicle communication method provided in an embodiment of this application. Figure 1 This method can be used for Figure 2 In the implementation environment described in the embodiments or flowcharts, this specification provides the operational steps of the methods described in the embodiments or flowcharts, but based on conventional or non-inventive labor, more or fewer operational steps may be included. The order of steps listed in the embodiments is merely one possible execution order among many and does not represent the only execution order. In actual system or server product execution, the methods shown in the embodiments or drawings can be executed sequentially or in parallel (e.g., in a parallel processor or multi-threaded processing environment). Specifically, as shown in the embodiments or drawings... Figure 3 As shown, the method may include:

[0069] Step S1001: The vehicle sends a communication connection request to the server; the communication connection request carries the subscribed topic and the data to be processed;

[0070] Specifically, the Message Queuing Telemetry Transport Protocol (MQTT) communication service is started, the vehicle terminal and the server establish a communication connection, and the vehicle terminal, as a subscriber, sends a communication connection request to the server; the communication connection request carries the subscription topic and the data to be processed; the server is an MQTTBroker; the subscription topic is configured with vehicle terminal subscription information corresponding to the subscription topic; the data to be processed is the data that the vehicle terminal needs to process, and the data to be processed is related to the subscription topic.

[0071] Optionally, the subscription topics can be customized according to different needs or sources, such as: $SYS / + / clients / #. Topics are distinguished by " / " and support wildcards such as "+" and "#", specifically including:

[0072] 1) Topics that begin with $ are special topics, for example, $SYS / indicates a reserved system topic;

[0073] 2) "+": indicates a wildcard match for a level, for example, a / + matches a / b, a / c;

[0074] 3) "#": indicates wildcard matching of multiple levels, for example, a / # matches a / b, a / b / c.

[0075] Step S1002: The server receives the communication connection request sent by the vehicle terminal;

[0076] Specifically, the communication connection request also carries message publishing information, which is determined based on the data transmission rules corresponding to the subscribed topic. The server receiving the communication connection request sent by the vehicle includes:

[0077] The server receives the communication connection request sent by the vehicle based on the message publishing information.

[0078] Optionally, the data transmission rules are determined based on the usage scenario of the communication connection request, specifically including:

[0079] 1) "At most once": Message delivery relies entirely on the underlying Transmission Control Protocol / Internet Protocol (TCP / IP) network. Message loss or duplication may occur. This level is suitable for situations where data is not critical, the impact of losing one piece of data is minimal, and a second transmission will occur shortly afterward. This method is primarily used for ordinary push notification subscriptions. If the device is not connected to the internet when a message is pushed, it will not receive the message after being published and will not receive the corresponding push notification once it reconnects to the internet.

[0080] 2) "At least once" ensures that the message arrives, but message duplication may occur.

[0081] 3) "Only Once" ensures that the message arrives only once. This level can be used in vehicle-side scenarios where the requirements for transmitting data are relatively strict.

[0082] Step S1003: The server sends the communication connection request to the cloud;

[0083] Specifically, the server establishes a communication connection with the cloud, and the server sends the communication connection request received from the vehicle to the cloud.

[0084] Step S1004: The cloud receives the communication connection request sent by the server;

[0085] Specifically, based on the communication connection established between the cloud and the server, the cloud receives the communication connection request sent by the server.

[0086] Step S1005: The cloud platform processes the data to be processed to obtain the target data;

[0087] Specifically, the cloud analyzes the data to be processed carried in the communication connection request, determines the data processing strategy corresponding to the data to be processed, and processes the data to be processed based on the data processing strategy to obtain the target data.

[0088] Step S1006: The cloud publishes the target data to the subscribed topic, generating the target topic;

[0089] Specifically, the cloud platform acts as the publisher, publishing the target data to the subscription topic, thereby matching the subscription topic with the target data and generating the target topic; the target topic is configured with the vehicle-side subscription information.

[0090] Step S1007: The cloud sends the target topic to the server;

[0091] Specifically, based on the communication connection established between the cloud and the server, the cloud sends the target topic to the server.

[0092] Step S1008: The server receives the target topic sent by the cloud;

[0093] Specifically, based on the communication connection established between the cloud and the server, the server receives the target topic sent by the cloud.

[0094] Step S1009: The server sends the target topic to the vehicle terminal;

[0095] Specifically, the server determines the vehicle client corresponding to the target topic based on the vehicle client subscription information configured for the target topic, and the server, as the publisher, publishes the target topic to the vehicle client corresponding to the target topic.

[0096] Step S1010: The vehicle receives the target topic.

[0097] Specifically, the vehicle receives the target topic and completes the communication.

[0098] This embodiment describes a vehicle communication method in which the vehicle and the cloud are connected via MQTT communication service. The MQTTBroker satisfies the data transmission and communication needs of the vehicle and the cloud, enabling them to communicate and interact without the need for hardware devices as a communication intermediary. This shortens the transmission link, ensures fast transmission response when transmitting large amounts of data, improves data transmission efficiency, and guarantees the effectiveness and integrity of data transmission between the vehicle and the cloud.

[0099] Please see Figure 4 The diagram shown is a flowchart of a vehicle communication method provided in an embodiment of this application. Figure 2 Before step S1001, the method may further include:

[0100] Step S2001: The vehicle sends a registration request to the server; the registration request carries the vehicle's registration information;

[0101] Specifically, the server establishes a bidirectional communication connection with the vehicle and the cloud based on MQTT, and the vehicle sends the registration request to the server; the registration request carries the vehicle's registration information; the registration information includes the vehicle's corresponding registration identity information and registration password information.

[0102] Step S2002: The server receives the registration request sent by the vehicle terminal;

[0103] Specifically, based on the communication connection established between the server and the vehicle, the server receives the registration request sent by the vehicle.

[0104] Step S2003: The server sends the registration request to the cloud;

[0105] Specifically, based on the communication connection established between the server and the cloud, the server sends the registration request to the cloud.

[0106] Step S2004: The cloud receives the registration request sent by the server;

[0107] Specifically, based on the communication connection established between the server and the cloud, the cloud receives the registration request sent by the server.

[0108] Step S2005: The cloud queries the registration status information corresponding to the registration information;

[0109] Specifically, the cloud queries the registration status information corresponding to the registration information, and the registration status information is stored in the cloud to represent the registration status of the vehicle.

[0110] Step S2006: The cloud sends the registration status information to the server;

[0111] Specifically, based on the communication connection established between the server and the cloud, the cloud sends the registration status information to the server.

[0112] Step S2007: The server receives the registration status information sent by the cloud;

[0113] Specifically, based on the communication connection established between the server and the cloud, the server receives the registration status information sent by the cloud.

[0114] Step S2008: If the registration status information indicates that the vehicle has been registered in the cloud, the server executes the operation of receiving the communication connection request sent by the vehicle.

[0115] Specifically, when the registration status information received by the server indicates that the vehicle has registered in the cloud, the server executes the operation of receiving the communication connection request sent by the vehicle based on the communication connection established between the server and the vehicle.

[0116] In an optional embodiment, if the registration status information indicates that the vehicle has not registered in the cloud, the method further includes:

[0117] Step S20081: The server encrypts the registration information to obtain encrypted registration information;

[0118] Step S20082: The server sends the encrypted registration information to the cloud and the vehicle terminal respectively;

[0119] Step S20083: The cloud and the vehicle receive the encrypted registration information sent by the server;

[0120] Step S20084: The cloud changes the status type of the registration status information from "not registered on the cloud" to "registered on the cloud"; the vehicle updates the information content corresponding to the registration information to the information content corresponding to the encrypted registration information.

[0121] Specifically, when the registration status information received by the server indicates that the vehicle has not registered with the cloud, step S20081 causes the server to encrypt the registration password information in the registration information to obtain encrypted registration information. The encryption method includes, but is not limited to, symmetric encryption, hash function, hash salting, and asymmetric encryption. Step S20082 causes the server to send the encrypted registration information to the cloud and the vehicle respectively, based on the communication connections established between the server and the cloud and the vehicle. Step S20083 causes the cloud and the vehicle to receive the encrypted registration information sent by the server, based on the communication connections established between the server and the cloud and the vehicle. Step S20084 causes the cloud to change the status type of the registration status information from "not registered with the cloud" to "registered with the cloud". The vehicle updates the information content corresponding to the registration information to the information content corresponding to the encrypted registration information, thereby realizing information updates between the cloud and the vehicle.

[0122] The following explanation focuses on the vehicle itself as the executing entity for this vehicle communication method:

[0123] Please see Figure 5 The diagram shown is a flowchart of a vehicle communication method provided in an embodiment of this application. Figure 3 The method includes:

[0124] Step S301: Send a communication connection request to the server; the communication connection request carries a subscription topic and data to be processed; so that the server sends the communication connection request to the cloud; so that the cloud processes the data to be processed to obtain target data; so that the cloud publishes the target data to the subscription topic to generate a target topic; and so that the server receives the target topic sent by the cloud.

[0125] Step S302: Receive the target topic sent by the server.

[0126] In an optional embodiment, before performing step S301 above, the method further includes:

[0127] Step S401: Send a registration request to the server; the registration request carries the vehicle's registration information; so that the server sends the registration request to the cloud; so that the cloud queries the registration status information corresponding to the registration information; so that the server receives the registration status information sent by the cloud;

[0128] Step S402: If the registration status information indicates that the vehicle has been registered in the cloud, perform the operation of sending a communication connection request to the server.

[0129] In an optional embodiment, if the registration status information indicates that the vehicle has not registered in the cloud, the method further includes:

[0130] The system receives encrypted registration information sent by the server; the encrypted registration information is obtained by the server encrypting the registration information.

[0131] Update the information content corresponding to the registration information to the information content corresponding to the encrypted registration information.

[0132] The following describes this vehicle communication method with the server as the executing entity:

[0133] Please see Figure 6 The diagram shown is a flowchart of a vehicle communication method provided in an embodiment of this application. Figure 4 The method includes:

[0134] Step S501: Receive a communication connection request sent by the vehicle terminal; the communication connection request carries the subscription topic and the data to be processed;

[0135] Step S502: Send the communication connection request to the cloud so that the cloud can process the data to be processed to obtain the target data; and so that the cloud can publish the target data to the subscribed topic to generate the target topic;

[0136] Step S503: Receive the target topic sent by the cloud;

[0137] Step S504: Send the target topic to the vehicle terminal.

[0138] In an optional embodiment, before performing step S501 above, the method further includes:

[0139] Step S601: Receive the registration request sent by the vehicle terminal; the registration request carries the registration information of the vehicle terminal;

[0140] Step S602: Send the registration request to the cloud so that the cloud can query the registration status information corresponding to the registration information;

[0141] Step S603: Receive the registration status information sent by the cloud;

[0142] Step S604: If the registration status information indicates that the vehicle has been registered in the cloud, perform the operation of receiving the communication connection request sent by the vehicle.

[0143] In an optional embodiment, if the registration status information indicates that the vehicle has not registered in the cloud, the method further includes:

[0144] The registration information is encrypted to obtain encrypted registration information;

[0145] The encrypted registration information is sent to the cloud and the vehicle respectively.

[0146] In an optional embodiment, sending the encrypted registration information to the cloud and the vehicle terminal respectively includes:

[0147] The encrypted registration information is sent to the cloud, so that the cloud changes the status type of the registration status information from "not registered on the cloud" to "registered on the cloud".

[0148] The encrypted registration information is sent to the vehicle terminal, so that the vehicle terminal updates the information content corresponding to the registration information to the information content corresponding to the encrypted registration information.

[0149] In an optional embodiment, the communication connection request carries message publishing information, which is determined based on the data transmission rules corresponding to the subscribed topic. The communication connection request sent by the receiving vehicle includes:

[0150] The communication connection request carries message publishing information, which is determined based on the data transmission rules corresponding to the subscribed topic. The communication connection request sent by the receiving vehicle includes:

[0151] Based on the message release information, the communication connection request sent by the vehicle terminal is received.

[0152] The following explanation focuses on the cloud as the primary execution platform for this vehicle communication method:

[0153] Please see Figure 7 The diagram shown is a flowchart of a vehicle communication method provided in an embodiment of this application. Figure 5 The method includes:

[0154] Step S701: Receive a communication connection request sent by the server; the communication connection request is sent from the vehicle to the server; the communication connection request carries the subscribed topic and the data to be processed;

[0155] Step S702: Process the data to be processed to obtain the target data;

[0156] Step S703: Publish the target data to the subscribed topic to generate the target topic;

[0157] Step S704: Send the target topic to the server, so that the server sends the target topic to the vehicle terminal.

[0158] In an optional embodiment, before performing step S701 above, the method further includes:

[0159] Step S801: Receive a registration request sent by the server; the registration request is sent from the vehicle to the server, and the registration request carries the registration information of the vehicle.

[0160] Step S802: Query the registration status information corresponding to the registration information;

[0161] Step S803: Send the registration status information to the server, so that the server can receive the communication connection request sent by the vehicle when the registration status information indicates that the vehicle has been registered locally in the cloud.

[0162] In an optional embodiment, if the registration status information indicates that the vehicle has not registered on the local cloud, the method further includes:

[0163] The server receives encrypted registration information; the encrypted registration information is obtained by the server encrypting the registration information.

[0164] Change the status type of the registration status information from "not registered on the local cloud" to "registered on the local cloud".

[0165] As can be seen from the above technical solutions of the embodiments of this application, in the embodiments of this application, the vehicle end and the cloud end are connected through MQTT communication service, and the data transmission communication needs of the vehicle end and the cloud end are met through MQTTBroker. This enables the vehicle end and the cloud end to achieve communication interaction without configuring hardware devices as a transmission communication intermediary, shortens the transmission link, ensures the transmission response speed when transmitting a large amount of data, improves data transmission efficiency, and ensures the effectiveness and integrity of the communication data transmission between the vehicle end and the cloud end.

[0166] Corresponding to the vehicle communication method provided in the above embodiments, this application also provides a vehicle communication device. Since the vehicle communication device provided in this application corresponds to the vehicle communication method provided in the above embodiments, the implementation methods of the aforementioned vehicle communication method are also applicable to the vehicle communication device provided in this embodiment, and will not be described in detail in this embodiment.

[0167] Please see Figure 8 The diagram shows the structural frame of a vehicle communication device provided in an embodiment of this application. Figure 1 The device includes:

[0168] A vehicle-side communication request sending module is used to send a communication connection request to a server; the communication connection request carries a subscription topic and data to be processed; so that the server sends the communication connection request to the cloud; so that the cloud processes the data to be processed to obtain target data; so that the cloud publishes the target data to the subscription topic to generate a target topic; and so that the server receives the target topic sent by the cloud.

[0169] The vehicle-side target topic receiving module is used to receive the target topic sent by the server.

[0170] In an optional embodiment, before executing the vehicle-side communication request sending module described above, the apparatus further includes:

[0171] A vehicle-side registration request sending module is used to send a registration request to the server; the registration request carries the vehicle-side registration information; so that the server sends the registration request to the cloud; so that the cloud queries the registration status information corresponding to the registration information; so that the server receives the registration status information sent by the cloud.

[0172] If the registration status information indicates that the vehicle has been registered in the cloud, the vehicle communication request sending module described above is executed.

[0173] In an optional embodiment, if the registration status information indicates that the vehicle has not registered with the cloud, the device further includes:

[0174] The vehicle-side encrypted information receiving module is used to receive encrypted registration information sent by the server; the encrypted registration information is obtained by the server encrypting the registration information.

[0175] The vehicle-side registration information update module is used to update the information content corresponding to the registration information to the information content corresponding to the encrypted registration information.

[0176] Please see Figure 9 The diagram shows the structural frame of a vehicle communication device provided in an embodiment of this application. Figure 2 The device includes:

[0177] The first connection request receiving module is used to receive a communication connection request sent by the vehicle terminal; the communication connection request carries a subscription topic and data to be processed.

[0178] A connection request sending module is configured to send the communication connection request to the cloud, so that the cloud can process the data to be processed to obtain target data; and to enable the cloud to publish the target data to the subscribed topic to generate a target topic;

[0179] A target topic receiving module is used to receive the target topic sent by the cloud.

[0180] The first target topic sending module is used to send the target topic to the vehicle terminal.

[0181] In an optional embodiment, before executing the first connection request receiving module described above, the apparatus further includes:

[0182] The first registration request receiving module is used to receive the registration request sent by the vehicle terminal; the registration request carries the registration information of the vehicle terminal;

[0183] The registration request sending module is used to send the registration request to the cloud so that the cloud can query the registration status information corresponding to the registration information;

[0184] The registration status information receiving module is used to receive the registration status information sent by the cloud.

[0185] If the registration status information indicates that the vehicle has been registered in the cloud, the first connection request receiving module described above will be executed.

[0186] In an optional embodiment, if the registration status information indicates that the vehicle has not registered with the cloud, the device further includes:

[0187] The information encryption processing module is used to encrypt the registration information to obtain encrypted registration information;

[0188] An encrypted information sending module is used to send the encrypted registration information to the cloud and the vehicle respectively.

[0189] Please see Figure 10 The diagram shows the structural frame of a vehicle communication device provided in an embodiment of this application. Figure 3 The device includes:

[0190] The second connection request receiving module is used to receive a communication connection request sent by the server; the communication connection request is sent from the vehicle to the server; the communication connection request carries the subscribed topic and the data to be processed.

[0191] The data processing module is used to process the data to be processed to obtain the target data;

[0192] The target topic generation module is used to publish the target data to the subscribed topic and generate the target topic;

[0193] The second target topic sending module is used to send the target topic to the server, so that the server sends the target topic to the vehicle terminal.

[0194] In an optional embodiment, before executing the second connection request receiving module described above, the apparatus further includes:

[0195] The second registration request receiving module is used to receive the registration request sent by the server; the registration request is sent from the vehicle terminal to the server, and the registration request carries the registration information of the vehicle terminal;

[0196] The registration status information query module is used to query the registration status information corresponding to the registration information;

[0197] The registration status information sending module is used to send the registration status information to the server, so that the server can receive the communication connection request sent by the vehicle when the registration status information indicates that the vehicle has been registered locally in the cloud.

[0198] In an optional embodiment, if the registration status information indicates that the vehicle has not registered on the local cloud, the device further includes:

[0199] An encrypted information receiving module is used to receive encrypted registration information sent by the server; the encrypted registration information is obtained by the server encrypting the registration information.

[0200] The status type change module is used to change the status type of the registration status information from "not registered on the local cloud" to "registered on the local cloud".

[0201] It should be noted that the apparatus provided in the above embodiments is only illustrated by the division of the above functional modules when implementing its functions. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above. In addition, the apparatus and method embodiments provided in the above embodiments belong to the same concept, and the specific implementation process can be found in the method embodiments, which will not be repeated here.

[0202] The vehicle communication device of this application embodiment enables the vehicle and the cloud to connect via MQTT communication service. The MQTTBroker satisfies the data transmission communication needs of the vehicle and the cloud, allowing them to communicate without requiring hardware as a communication intermediary. This shortens the transmission link, ensures faster transmission response when transmitting large amounts of data, improves data transmission efficiency, and guarantees the effectiveness and integrity of data transmission between the vehicle and the cloud.

[0203] This application also provides a vehicle communication system, which includes: a vehicle terminal, a server, and a cloud;

[0204] The vehicle terminal is configured to: send a communication connection request to the server when the registration status information indicates that the vehicle terminal has registered in the cloud, the communication connection request carrying a subscription topic and data to be processed; receive a target topic sent by the server; send a registration request to the server, the registration request carrying the vehicle terminal's registration information; and receive encrypted registration information sent by the server, and then update the information content corresponding to the registration information with the information content corresponding to the encrypted registration information.

[0205] The server is configured to: receive a communication connection request from the vehicle terminal when the registration status information indicates that the vehicle terminal has registered with the cloud; the communication connection request carries the subscription topic and the data to be processed; send the communication connection request to the cloud; receive the target topic sent by the cloud; send the target topic to the vehicle terminal; receive a registration request from the vehicle terminal, the registration request carrying the registration information of the vehicle terminal; send the registration request to the cloud; receive the registration status information sent by the cloud; and encrypt the registration information when the registration status information indicates that the vehicle terminal has not registered with the cloud, obtain encrypted registration information, and then send the encrypted registration information to the cloud and the vehicle terminal respectively.

[0206] The cloud platform is configured to: receive a communication connection request sent by the server, the communication connection request carrying the subscription topic and the data to be processed; process the data to be processed to obtain target data, and then publish the target data to the subscription topic to generate the target topic; send the target topic to the server; receive a registration request sent by the server, the registration request carrying the registration information of the vehicle; query the registration status information corresponding to the registration information, and then send the registration status information to the server; and receive the encrypted registration information sent by the server, and then change the status type of the registration status information from "not registered on the local cloud" to "registered on the local cloud".

[0207] This application also provides an electronic device, including a processor and a memory, wherein the memory stores at least one instruction or at least one program, and the processor loads and executes the at least one instruction or at least one program to implement the vehicle communication method provided in the above method embodiments.

[0208] Memory can be used to store software programs and modules. The processor executes these stored software programs and modules to perform various functional applications and achieve advanced autonomous driving. Memory can primarily include a program storage area and a data storage area. The program storage area can store the operating system, application programs required for functions, etc.; the data storage area can store data created based on device usage, etc. Furthermore, memory can include high-speed random access memory and non-volatile memory, such as at least one disk storage device, flash memory device, or other volatile solid-state storage device. Accordingly, memory can also include a memory controller to provide the processor with access to the memory.

[0209] The method embodiments provided in this application can be executed in a computer terminal, server or similar computing device, that is, the above-mentioned electronic device may include a computer terminal, server or similar computing device. Figure 11 This is a hardware structure block diagram of an electronic device that runs a vehicle communication method according to an embodiment of this application, such as... Figure 11 As shown, the internal structure of this electronic device may include, but is not limited to, a processor, a network interface, and a memory. The processor, network interface, and memory within the electronic device can be connected via a bus or other means, as illustrated in the embodiments of this specification. Figure 11 Taking the example of a connection between China and Israel via a bus.

[0210] The processor (or CPU, Central Processing Unit) is the computing and control core of the electronic device. The network interface may optionally include a standard wired interface or a wireless interface (such as Wi-Fi, mobile communication interface, etc.). The memory is the storage device in the electronic device used to store programs and data. It is understood that the memory here can be a high-speed RAM storage device, or a non-volatile storage device, such as at least one disk storage device; optionally, it can also be at least one storage device located remotely from the aforementioned processor. The memory provides storage space, which stores the operating system of the electronic device, including but not limited to: Windows (an operating system), Linux (an operating system), Android (a mobile operating system), iOS (a mobile operating system), etc., which are not limited in this application; and the storage space also stores one or more instructions suitable for being loaded and executed by the processor, which can be one or more computer programs (including program code). In the embodiments of this specification, the processor loads and executes one or more instructions stored in the memory to implement the vehicle communication method provided in the above method embodiments.

[0211] This application also provides a computer-readable storage medium storing at least one instruction or at least one program, wherein the at least one instruction or at least one program is loaded and executed by a processor to implement the vehicle communication method provided in the method embodiment.

[0212] Optionally, in this embodiment, the storage medium may include, but is not limited to, various media capable of storing program code, such as USB flash drives, read-only memory (ROM), random access memory (RAM), portable hard drives, magnetic disks, or optical disks.

[0213] It should be noted that the order of the embodiments described above is merely for descriptive purposes and does not represent the superiority or inferiority of the embodiments. Furthermore, the above description focuses on specific embodiments of this specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps described in the claims can be performed in a different order than those shown in the embodiments and still achieve the desired results. Additionally, the processes depicted in the drawings do not necessarily require a specific or sequential order to achieve the desired results. In some embodiments, multi-sample image classification and parallel processing are also possible or may be advantageous.

[0214] The various embodiments in this specification are described in a progressive manner. Similar or identical parts between embodiments can be referred to mutually. Each embodiment focuses on describing the differences from other embodiments. In particular, the apparatus embodiments are basically similar to the method embodiments, so the description is relatively simple; relevant parts can be referred to the descriptions of the method embodiments.

[0215] Those skilled in the art will understand that all or part of the steps of the above embodiments can be implemented by hardware or by a program instructing related hardware. The program can be stored in a computer-readable storage medium, such as a read-only memory, a disk, or an optical disk.

[0216] The above are merely preferred embodiments of this application and are not intended to limit this application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the protection scope of this application.

Claims

1. A vehicle communication method, characterized in that, include: Receive the registration request sent by the vehicle terminal; The registration request carries the vehicle's registration information; The registration request is sent to the cloud so that the cloud can query the registration status information corresponding to the registration information. The system receives the registration status information sent by the cloud; if the registration status information indicates that the vehicle has registered with the cloud, the system receives a communication connection request sent by the vehicle; the communication connection request carries a subscription topic and data to be processed; the subscription topic is configured with vehicle subscription information; the vehicle is a subscriber. The communication connection request is sent to the cloud so that the cloud can process the data to be processed to obtain the target data; and the cloud, as a publisher, publishes the target data to the subscription topic to generate the target topic; the target topic is configured with vehicle-side subscription information; Receive the target topic sent by the cloud; Based on the vehicle-side subscription information configured for the target topic, determine the vehicle-side device corresponding to the target topic, and send the target topic to the vehicle-side device.

2. The vehicle communication method according to claim 1, characterized in that, If the registration status information indicates that the vehicle has not registered with the cloud, the method further includes: The registration information is encrypted to obtain encrypted registration information; The encrypted registration information is sent to the cloud and the vehicle respectively.

3. The vehicle communication method according to claim 2, characterized in that, The step of sending the encrypted registration information to the cloud and the vehicle terminal respectively includes: The encrypted registration information is sent to the cloud, so that the cloud changes the status type of the registration status information from "not registered on the cloud" to "registered on the cloud". The encrypted registration information is sent to the vehicle terminal, so that the vehicle terminal updates the information content corresponding to the registration information to the information content corresponding to the encrypted registration information.

4. The vehicle communication method according to claim 1, characterized in that, The communication connection request carries message publishing information, which is determined based on the data transmission rules corresponding to the subscribed topic. The communication connection request sent by the receiving vehicle includes: Based on the message release information, the communication connection request sent by the vehicle terminal is received.

5. A vehicle communication method, characterized in that, include: Receive a registration request sent by the server; the registration request is sent from the vehicle to the server, and the registration request carries the registration information of the vehicle. Query the registration status information corresponding to the aforementioned registration information; The registration status information is sent to the server so that the server can receive the communication connection request sent by the vehicle when the registration status information indicates that the vehicle has been registered locally in the cloud. Receive a communication connection request sent by the server; the communication connection request is sent from the vehicle to the server; The communication connection request carries a subscription topic and data to be processed; the subscription topic is configured with vehicle-side subscription information. The vehicle-side device is a subscriber; The data to be processed is processed to obtain the target data; As the publisher, the target data is published to the subscribed topic, thereby generating the target topic; The target topic is configured with vehicle-side subscription information; The target topic is sent to the server, so that the server determines the vehicle corresponding to the target topic based on the vehicle subscription information configured for the target topic, and sends the target topic to the vehicle.

6. The vehicle communication method according to claim 5, characterized in that, If the registration status information indicates that the vehicle has not registered on the local cloud, the method further includes: The server receives encrypted registration information; the encrypted registration information is obtained by the server encrypting the registration information.

7. The vehicle communication method according to claim 6, characterized in that, The receipt of the encrypted registration information sent by the server includes: Receive the encrypted registration information sent by the server; Change the status type of the registration status information from "not registered on the local cloud" to "registered on the local cloud".

8. A vehicle communication device, characterized in that, The device includes: The vehicle-side registration request sending module is used to receive a registration request sent by the vehicle-side; the registration request carries the registration information of the vehicle-side; send the registration request to the cloud so that the cloud can query the registration status information corresponding to the registration information; and receive the registration status information sent by the cloud. The first connection request receiving module is configured to receive a communication connection request sent by the vehicle terminal when the registration status information indicates that the vehicle terminal has registered in the cloud; the communication connection request carries a subscription topic and data to be processed; the subscription topic is configured with vehicle terminal subscription information; the vehicle terminal is a subscriber; A connection request sending module is used to send the communication connection request to the cloud, so that the cloud can process the data to be processed to obtain target data; and to enable the cloud to publish the target data to the subscription topic as a publisher, thereby generating a target topic; the target topic is configured with vehicle-side subscription information; A target topic receiving module is used to receive the target topic sent by the cloud. The first target topic sending module is used to determine the vehicle terminal corresponding to the target topic based on the vehicle terminal subscription information configured for the target topic, and send the target topic to the vehicle terminal.

9. A vehicle communication device, characterized in that, The device includes: The second registration request receiving module is used to receive a registration request sent by the server; the registration request is sent from the vehicle to the server, and the registration request carries the registration information of the vehicle. The registration status information query module is used to query the registration status information corresponding to the registration information; The registration status information sending module is used to send the registration status information to the server, so that the server can receive the communication connection request sent by the vehicle when the registration status information indicates that the vehicle has been registered in the local cloud. The second connection request receiving module is used to receive a communication connection request sent by the server; the communication connection request is sent from the vehicle to the server; the communication connection request carries a subscription topic and data to be processed; the subscription topic is configured with vehicle subscription information; the vehicle is the subscriber; The data processing module is used to process the data to be processed to obtain the target data; The target topic generation module is used as a publisher to publish the target data to the subscribed topic and generate a target topic; the target topic is configured with vehicle-side subscription information; The second target topic sending module is used to send the target topic to the server, so that the server determines the vehicle corresponding to the target topic according to the vehicle subscription information configured for the target topic, and sends the target topic to the vehicle.

10. An electronic device, characterized in that, It includes a processor and a memory, wherein the memory stores at least one instruction or at least one program, the at least one instruction or the at least one program being loaded and executed by the processor to implement the vehicle communication method as described in any one of claims 1 to 7.

11. A computer-readable storage medium storing at least one instruction or at least one program, said at least one instruction or said at least one program being loaded and executed by a processor to implement the vehicle communication method as described in any one of claims 1 to 7.

Images