Message information transmission method and device based on Internet of Vehicles platform, equipment, storage medium and program product

Abstract

The invention discloses a message information transmission method and device based on an Internet of Vehicles platform, equipment, a storage medium and a program product, and relates to the technical field of Internet of Vehicles, and the method comprises the steps: obtaining message request information and message template information; sending a message based on the message request information and the message template information to determine message middleware queue state information; and based on the message middleware queue state information, controlling a vehicle message middleware to transmit and distribute a buffer message in a first-in first-out mode. According to the method, various complex communication scenes are flexibly processed by acquiring the message request information and the message template information, the message sending process is managed and optimized by using the message middleware, the buffer message is distributed by adopting a first-in first-out mode, the sequence and timeliness of message transmission are ensured, and the message transmission efficiency is improved. The target vehicles are efficiently and accurately distributed, the performance and stability of the whole vehicle networking platform are remarkably improved, and smoother and more reliable intelligent traffic experience is provided for users.

Description

Technical Field

[0001] This application relates to the field of vehicle networking technology, and in particular to message transmission methods, devices, equipment, storage media and program products based on vehicle networking platforms. Background Art

[0002] With the rapid development of vehicle-to-everything (V2X) technology, information interaction between vehicles and the cloud, between vehicles, and between vehicles and infrastructure is becoming increasingly frequent and important. Vehicle dynamic information relies on a stable and reliable message transmission mechanism for real-time transmission and processing through effective communication methods to support various intelligent transportation systems and in-vehicle services. However, implementing message propagation functionality in every module would not only waste resources but also hinder troubleshooting. Therefore, establishing an efficient, flexible, and scalable message transmission system to meet the ever-increasing information interaction needs of V2X platforms is essential.

[0003] Currently, since message propagation functions are largely similar—requiring a sender, a receiver, and a message body—a third-party service, namely a message center, can be used to actually send messages. The message sender ensures the message body meets the message center's specifications according to the agreement. The message center then verifies the message and propagates it to the corresponding receiver according to the agreement. The message propagation method is implemented by the message center. For example, vehicle remote control functions can use the MQTT protocol for message propagation. The user initiates a remote control request through a mobile app, and the app's backend service requests the message center's interface. The message center then transmits the control commands to the vehicle via the MQTT protocol. The message propagation path can include uploading from the mobile phone to the cloud and then transmitting it to the vehicle's infotainment system, thereby controlling the vehicle.

[0004] However, protocols like MQTT are primarily suitable for lightweight message transmission and cannot meet all types of information delivery needs, such as email sending or SMS notifications. Furthermore, with the diversification of connected vehicle services, a single message transmission method may lead to resource waste and maintenance difficulties. When problems arise during message transmission, troubleshooting and resolving them becomes more challenging. Therefore, finding a more flexible and efficient way to transmit messages, adaptable to various message transmission needs, has become an urgent problem to be solved.

[0005] The above content is only used to help understand the technical solution of this application and does not represent an admission that the above content is prior art. Summary of the Invention

[0006] The main objective of this application is to provide a method, apparatus, device, storage medium, and program product for message transmission on a vehicle networking platform, aiming to solve the technical problem of how to transmit message information more efficiently and flexibly, and adapt to various message transmission needs.

[0007] To achieve the above objectives, this application proposes a message transmission method based on a vehicle-to-everything (V2X) platform, the method comprising:

[0008] Retrieve message request information and message template information;

[0009] Based on the message request information and message template information, a message is sent to determine the message middleware queue status information;

[0010] Based on the message middleware queue status information, the vehicle message middleware is controlled to distribute buffered messages in a first-in-first-out manner.

[0011] In one embodiment, the step of obtaining message request information and message template information includes:

[0012] Retrieve variable value key-value pair information, message encoding information, recipient information, extended parameter information, sending method information, push selection parameter information, push channel information, enable resend information, target resend count, response information, response timeout information, scheduled push information, message encoding, message title, template content, approval status, and internationalization content;

[0013] The message request information is determined based on the variable value key-value pair information, message encoding information, recipient information, extended parameter information, sending method information, push selection parameter information, push channel information, retransmission enabled information, target retransmission count, response information, response timeout information, and timed push information.

[0014] The message template is determined based on the message encoding, message title, template content, approval status, and internationalized content.

[0015] In one embodiment, the step of determining the message template based on the message encoding, message title, template content, approval status, and internationalized content includes:

[0016] Obtain channel existence status information;

[0017] When the channel status information indicates that a channel exists, the message template is determined based on the message code, message title, template content, approval status, and internationalized content.

[0018] When the channel status information indicates that there is no channel, obtain recommended channel information, generate channel configuration information based on the recommended channel information, and determine the message template based on the channel configuration information, message code, message title, template content, approval status, and internationalization content.

[0019] In one embodiment, the step of determining the message middleware queue status information based on the message request information and message template information includes:

[0020] Get email service information;

[0021] The push message package is determined based on the email service information, message request information, and message template information;

[0022] The push message packet is sent to the message middleware queue to obtain the message middleware queue status information.

[0023] In one embodiment, the step of obtaining email service information includes:

[0024] Obtain the account and password for the email sending service;

[0025] The email service information is determined based on the email sending service account and email sending service password. The email service information includes the email server ID, email server address, email server port, email login account, email login password, and email default encoder.

[0026] In one embodiment, the step of controlling the vehicle message middleware to deliver and distribute buffered messages in a first-in-first-out manner based on the message middleware queue status information includes:

[0027] Monitor the status information of the message middleware queue and distribute messages to the corresponding channels in a first-in-first-out manner to determine the sending status information;

[0028] When the sending status information indicates a sending failure, the message corresponding to the distribution channel is resent to determine the resentment status information.

[0029] When the sending status information is "sent successfully" or the retransmission status information is "retransmission successfully", modify the message status in the database;

[0030] When the sending status information is "sending failed" and the retransmission status information is "retransmission failed", the message status in the database is not modified.

[0031] Furthermore, to achieve the above objectives, this application also proposes a message transmission device based on a vehicle networking platform, the message transmission device based on the vehicle networking platform comprising:

[0032] The acquisition module is used to acquire message request information and message template information;

[0033] The processing module is used to send a message based on the message request information and message template information to determine the message middleware queue status information;

[0034] The execution module is used to control the vehicle message middleware to distribute buffered messages in a first-in-first-out manner based on the message middleware queue status information.

[0035] In addition, to achieve the above objectives, this application also proposes a message transmission device based on a vehicle networking platform. The device includes: a memory, a processor, and a computer program stored in the memory and executable on the processor. The computer program is configured to implement the steps of the message transmission method based on the vehicle networking platform as described above.

[0036] In addition, to achieve the above objectives, this application also proposes a storage medium, which is a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, it implements the steps of the message information transmission method based on the vehicle networking platform described above.

[0037] In addition, to achieve the above objectives, this application also provides a computer program product, which includes a computer program that, when executed by a processor, implements the steps of the message information transmission method based on the vehicle networking platform described above.

[0038] One or more technical solutions proposed in this application have at least the following technical effects:

[0039] This application proposes a message transmission method based on a vehicle-to-everything (V2X) platform. The method involves acquiring message request information and message template information; sending messages based on the message request information and message template information to determine the message middleware queue status information; and controlling the vehicle message middleware to distribute buffered messages in a first-in-first-out (FIFO) manner based on the message middleware queue status information. By acquiring message request information and message template information, this application flexibly handles various complex communication scenarios, utilizes message middleware to manage and optimize the message sending process, optimizes message transmission methods, and employs a FIFO approach to distribute buffered messages. This further enhances the system's response speed and data processing capabilities, ensures the sequential and timely delivery of messages, and efficiently and accurately distributes messages to target vehicles. This significantly improves the performance and stability of the entire V2X platform, providing users with a smoother and more reliable intelligent transportation experience. Attached Figure Description

[0040] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.

[0041] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0042] Figure 1This is a flowchart illustrating an embodiment of the message transmission method based on a vehicle networking platform provided in this application.

[0043] Figure 2 This is a schematic diagram of message request parameters for the message information transmission method based on the vehicle networking platform in this application;

[0044] Figure 3 This is a schematic diagram illustrating the template parameters for the message transmission method based on the vehicle networking platform in this application.

[0045] Figure 4 This is a flowchart illustrating Embodiment 2 of the message transmission method based on the vehicle networking platform of this application;

[0046] Figure 5 This is a schematic diagram of the message transmission method based on the vehicle networking platform in this application, specifically an email service information diagram.

[0047] Figure 6 A simplified flowchart illustrating the message transmission method based on a vehicle networking platform provided in this application embodiment;

[0048] Figure 7 This is a schematic diagram of the module structure of the message transmission device based on the vehicle networking platform in an embodiment of this application;

[0049] Figure 8 This is a schematic diagram of the device structure of the hardware operating environment involved in the message information transmission method based on the vehicle networking platform in the embodiments of this application.

[0050] The purpose, features and advantages of this application will be further explained with reference to the accompanying drawings in conjunction with the embodiments. Detailed Implementation

[0051] It should be understood that the specific embodiments described herein are merely used to explain the technical solutions of the present application and are not intended to limit the present application.

[0052] To better understand the technical solution of this application, a detailed description will be provided below in conjunction with the accompanying drawings and specific implementation methods.

[0053] The main solution of this application embodiment is: to obtain message request information and message template information; to send a message based on the message request information and message template information to determine the message middleware queue status information; and to control the vehicle message middleware to distribute the buffered messages in a first-in-first-out manner based on the message middleware queue status information.

[0054] In this embodiment, for ease of description, the following description will focus on identifying message transmission devices based on the vehicle network platform as the executing entity.

[0055] Because existing technologies such as MQTT are mainly suitable for lightweight message transmission, they cannot meet all types of information transmission needs, such as email sending or SMS notifications. Furthermore, with the diversification of vehicle networking services, a single message transmission method may lead to resource waste and maintenance difficulties. When problems occur during message transmission, the difficulty of troubleshooting and resolving them increases.

[0056] This application provides a solution for obtaining message request information and message template information; sending messages based on the message request information and message template information to determine message middleware queue status information; and controlling the vehicle message middleware to distribute buffered messages in a first-in-first-out manner based on the message middleware queue status information.

[0057] As can be seen from the above embodiments, this application can flexibly handle various complex communication scenarios by obtaining message request information and message template information, using message middleware to manage and optimize the message sending process, optimize the message transmission method, and distribute buffered messages in a first-in-first-out manner, thereby further enhancing the system's response speed and data processing capabilities, ensuring the order and timeliness of message transmission, and efficiently and accurately distributing messages to target vehicles. This significantly improves the performance and stability of the entire vehicle network platform, providing users with a smoother and more reliable intelligent transportation experience.

[0058] Based on this, embodiments of this application provide a message transmission method based on a vehicle networking platform, referring to... Figure 1 , Figure 1 This is a flow chart of the first embodiment of the message information transmission method based on the Internet of Vehicles platform of this application.

[0059] In this embodiment, the message transmission method based on the vehicle networking platform includes steps S10 to S30:

[0060] Step S10, obtaining message request information and message template information;

[0061] It should be noted that the message request information reflects the characteristics of dynamic information processing in the vehicle networking platform during message transmission, and the message template information reflects the standardization characteristics of message structure and content in the vehicle networking platform.

[0062] Understandably, message templates define the basic format and content framework of a message, while message request information includes the content to be filled in the framework and the specific data. This improves the flexibility of message generation and allows the same message template to be applied to various different scenarios and needs, ensuring that the personalized and standardized requirements of messages are met. At the same time, it simplifies the message generation and processing process, improves the efficiency and accuracy of message processing, provides powerful scalability for the vehicle networking platform, supports more types of message services and application scenarios, and enhances the functionality and practicality of the entire system.

[0063] Additionally, it should be noted that database table fields are added to the content corresponding to the template number to record template information for each language. These database table fields include a template content table, a content information table, and a message record table. The template content table includes the message template code, corresponding content code, message channel, publication status, creation time, and update time. The message template code is the unique identifier for the template content table, while the corresponding content code records the unique identifier for the content information table. The content information table includes the content code, content title, message content, creator, creation date, updater, and update date. The content code is the unique identifier for the content information table. The message record table includes a push identifier code, template code, message title, message content, sender, receiver, message status, creator, creation time, modifier, and modification time. The push identifier code is the unique identifier for the message record table. The template code corresponds to the template code in the template content table, and the message status includes success, failure, and pending delivery.

[0064] For ease of understanding, we will take the acquisition of message request information and message template information as an example, where the information acquisition device is the information acquisition module and the storage device is the memory.

[0065] The information collection device acquires the following information: variable key-value pairs (keyValue), message encoding (msgCd), recipient information (receiverId), sending method information (manualFlag), push selection parameter information (Plateform), push channel information (channelCd), which includes channels such as Kafka, MQTT, and email; enable retransmission information (enableRepeat); target retransmission count (maxRepeat); response information (enableAck); response timeout information (ackTimeout); timed push information (Timer); message encoding (msgCd); message title (tplTitle); template content (tplContent); and approval status (appr). The `ovalStatus` function retrieves the internationalized content `resDesc`. Based on the variable value key-value pair information, message encoding information, recipient information, extended parameter information, sending method information, push selection parameter information, push channel information, enabled resend information, target resend count, response information, response timeout information, and scheduled push information, the message request information is determined. Based on the message encoding, message title, template content, approval status, and internationalized content, a message template is determined. When creating a message template, it is determined whether there is a corresponding sending channel. If there is no corresponding sending channel, a message channel is created, filling in fields such as server type, server address, and protocol. After the message channel is created, a message template is created based on the message channel. If there is a corresponding sending channel, the message template is created directly based on the message channel. Subsequent processing is performed based on the message request information and message template information.

[0066] In one feasible implementation, step S10 may include steps A11 to A13:

[0067] Step A11: Obtain variable value key-value pair information, message encoding information, recipient information, extended parameter information, sending method information, push selection parameter information, push channel information, enable resend information, target resend count, response information, response timeout information, scheduled push information, message encoding, message title, template content, approval status, and internationalization content;

[0068] It is understood that the variable value key-value pair information reflects the specific values ​​of variable parameters in the message template, enabling the message content to be dynamically generated based on different parameters. The message encoding information reflects the unique identifier of different message templates. The recipient information reflects the characteristics of the message recipient. The extended parameter information reflects the characteristics of additional message transmission parameters. The sending method information reflects the characteristics of the intelligent message sending status. The push selection parameter information reflects the characteristics of optional settings during the message push process, including push timing and frequency. The push channel information reflects the characteristics of the message transmission path, including Kafka channel, MQTT channel, and email channel. The enable retransmission information reflects the characteristics of the retry mechanism when message sending fails. The target retransmission count reflects the characteristics of the maximum number of message retransmissions. The response information reflects the characteristics of the recipient's confirmation response after receiving the message. The response timeout information reflects the characteristics of the maximum waiting time for the recipient's response. The scheduled push information reflects the characteristics of the message being sent according to a predetermined time. The message encoding reflects the unique identifier of the message information. The message title reflects the characteristics of the message information's subject. The template content reflects the characteristics of the message's structure and content. The approval status reflects the characteristics of the successful message transmission status. The internationalization content reflects the characteristics of language and regional settings.

[0069] Step A12: Determine message request information based on the variable value key-value pair information, message encoding information, recipient information, extended parameter information, sending method information, push selection parameter information, push channel information, enable retransmission information, target retransmission count, response information, response timeout information, and timed push information;

[0070] It is understandable that if Figure 2 As shown, Figure 2This is a schematic diagram of the message request parameters for the message information transmission method based on the vehicle networking platform in this application. The variable value key-value pair information (keyValue) is in key-value pair form. Since parameters may need to be assigned in the message title and message body, keyValue contains the parameter and its corresponding value. The message encoding information (msgCd) is the message template encoding. Based on this encoding, the corresponding template information and template title can be retrieved. The receiver information (receiverId) is the message recipient. The extended parameter information (extra) is retrieved; extra is the extended parameter, stored as a key-value pair. When business needs require transmitting some verification... When specifying parameters, you need to add the parameters and their corresponding values ​​to key-value pairs. The sending method information, `manualFlag`, is the sending method field, which is divided into automatic sending and manual sending. Automatic sending is for other programs to call the interface to send messages, while manual sending is for sending messages on the system's default page. The push selection parameter information, `Plateform`, is for platform selection, used when sending push messages to mobile phones. Its main function is to distinguish between iOS and Android phones, allowing push messages to be sent to one system or both. The push channel information, `channelCd`, is the push channel, including Kafka and MQT. For channels such as email, each channel can be represented by a given number, and there is a mapping relationship between this number and the channel. EnableRepeatt indicates whether to enable the automatic resend mechanism. The logic of the resend mechanism is that if the message fails to be sent, it will be resent. The target resend count, maxRepeat, is the maximum number of resends. This parameter is only effective when the automatic resend mechanism is enabled. When the number of message resends reaches the maxRepeat threshold, no further resends will be performed. This maximum number also has a boundary value; when the set maximum resend count exceeds this boundary value, the boundary value is used by default as the maximum resend count. The number of times to send the message is specified. The response information `enableAck` indicates whether a response is required. By default, no response is required. When this feature is enabled, the receiver needs to call a given method to pass parameters to the sender. The message status will only be modified to "not sent successfully" after the message is received. The response timeout information `ackTimeout` is the time threshold for the response. This parameter is only valid when the response is enabled. If the sender does not receive the message sent by the receiver within a certain time, the message that requires a response will be considered to have failed to send by default. The timed push information `Timer` enables the timed sending function. When a value is assigned to this parameter, the message will be sent at the specified time.

[0071] Step A13: Determine the message template based on the message encoding, message title, template content, approval status, and internationalization content.

[0072] It is understandable that if Figure 3 As shown, Figure 3This diagram illustrates the template parameters for the message transmission method based on the vehicle networking platform in this application. The message code `msgCd` is a unique identifier distinguishing message templates, the message title `tplTitle` is the title of the sent message, the template content `tplContent` is the message information to be transmitted, and the approval status `approvalStatus` has two states: published and unpublished. When sending a message according to the template, the message status is verified, and the message transmission process can only continue if the sending status is published. The internationalization content `resDesc` supports multiple languages ​​and regional settings, enabling message transmission to adapt to the needs of users in different countries and regions.

[0073] In one feasible implementation, step A10 may include steps B11 to B13:

[0074] Step B11: Obtain channel existence status information;

[0075] It should be noted that the channel existence status information reflects the characteristics of the corresponding transmission channel that is expected to exist.

[0076] Understandably, the currently supported push channels include Kafka, MQTT, email, in-app messages, and push notifications. MQTT and Kafka push channels are mostly used for Tbox, IVI, and cloud interaction. Push channels for transmitting user information include email, in-app messages, and push notifications. Using email requires configuring SMTP username, password, host, and port number. In-app messages and push notifications do not require configuring host information; users need to download the app and register. After registration, a unique identifier string is generated as the user ID. When sending information later, the request parameters are processed to determine whether the user will ultimately receive an in-app message or a push notification.

[0077] Step B12: When the channel existence status information is "channel exists", determine the message template based on the message code, message title, template content, approval status and internationalization content;

[0078] Understandably, the system checks the channel existence status information. If the channel existence status information indicates that a channel exists, then the existing channel is used to create a message template to ensure that users can use it directly and facilitate message transmission.

[0079] Step B13: When the channel existence status information is "no channel", obtain recommended channel information, generate channel configuration information based on the recommended channel information, and determine the message template based on the channel configuration information, message code, message title, template content, approval status and internationalization content.

[0080] It can be understood that when checking the channel existence status information, when the channel existence status information is that the channel does not exist, the operation and maintenance personnel can select different message channels according to different needs, and create a message template according to the configured message channel. When creating the template, it is necessary to fill in the template number, sending channel, message title and message content. The template number will verify the uniqueness and be passed in as one of the required request parameters when sending the message. Fill in the message title and message body. The message title and message body are the main message content received by the user. The sending channel is a required parameter for creating the template. After creating the message template, the template needs to be published so that the message can be sent according to the template.

[0081] Step S20: Based on the message request information and message template information, send a message to determine the message middleware queue status information;

[0082] It should be noted that the message middleware queue status information reflects the characteristics of message processing and scheduling by the vehicle networking platform during message transmission.

[0083] It is understandable that in order to reduce the pressure on the service during the peak period of message sending, the message middleware is used as a buffering method in the process of sending messages. That is, the message is sent to the message centerware, the message middleware queue status information is determined, and then the message middleware distributes the buffered messages and transmits the messages to each message recipient. This method not only reduces the service load pressure, but also improves the stability of the database.

[0084] Additionally, it should be noted that message middleware, as the core component of message passing, is responsible for queuing and distributing messages after processing message requests and template information, optimizing the message processing flow, and thus improving the overall message passing efficiency.

[0085] For ease of understanding, we will take determining the status information of the message middleware queue as an example. The information acquisition device is the information acquisition module, the storage device is the memory, and the processing device is the processing module.

[0086] The information collection device obtains message request information and message template information and stores them in the memory, verifies whether the message template exists according to the message coding information msgCd in the message request information, and reports an error directly if it does not exist, verifies whether the message template is published, and reports an error if it is not published, verifies whether the message channel is valid, and reports an error if it is an invalid message channel, verifies whether the template content corresponding to the template code exists, and reports an error if it does not exist, sends a message based on the message request information and message template information to determine the message middleware queue status information, fills in the message content, title, scheduled task, interval task and other content information in the message request information, sends a message based on the message template information to determine the message middleware queue status information, and performs subsequent processing based on the message middleware queue status information.

[0087] Step S30: Based on the message middleware queue status information, control the vehicle message middleware to distribute buffered messages in a first-in-first-out manner.

[0088] Understandably, First-In-First-Out (FIFO) is a common queue management mechanism that ensures messages are processed in the order they are received, thereby guaranteeing the fairness and determinism of message transmission, avoiding message out-of-order or loss issues, reducing message waiting time during transmission, improving the overall system response speed, and providing users with a smoother and more reliable service experience.

[0089] For ease of understanding, the acquisition of message middleware queue status information is taken as an example for explanation, wherein the information collection device is the information collection module, the storage device is the memory, and the execution device is the execution module.

[0090] The information acquisition module obtains the message middleware queue status information, listens to the message middleware queue status information, packages and pushes messages in a first-in-first-out manner, and generates a push ID. Based on the push ID, the message is sent to the Kafka topic. The module listens to the Kafka topic, and upon receiving a message, retrieves the corresponding information from Kafka to distribute the message to the corresponding channel. It obtains the sending status information. When the sending status information indicates a sending failure, it resends and distributes the message to the corresponding channel to determine the resend status information. When the sending status information indicates a sending success or the resend status information indicates a resend success, it modifies the message status in the database. When both the sending status information and the resend status information indicate a resend failure, it does not modify the message status in the database.

[0091] In a feasible implementation, step S30 may include steps C11 to C14:

[0092] Step C11: Monitor the status information of the message middleware queue and distribute the corresponding channel messages in a first-in-first-out manner to determine the sending status information;

[0093] It should be noted that the sending status information reflects the characteristics of the status information of the message during the transmission process.

[0094] Understandably, if the sending status information is "successful," it means that the message has been successfully transmitted from the message middleware to the target recipient, and the recipient has confirmed receipt of the message. If the sending status information is "failed," it means that the message encountered a problem during the sending process, such as a network error, the target address being unreachable, or an incorrect message format, which caused the message to fail to be delivered.

[0095] Step C12: When the sending status information is "sending failed", resend the corresponding distribution channel message to determine the resend status information;

[0096] It should be noted that the retransmission status information reflects the characteristic of attempting to send the message again when the sending status information indicates a sending failure.

[0097] Understandably, if a message fails to be sent, the system can retry according to a preset strategy. The retry status information can record the number of times the message has been sent and whether the maximum number of retry attempts has been reached. If the message does not receive a response from the recipient within a certain period of time, the system will mark it as timed out. This allows for effective monitoring and management of the entire message delivery process, ensuring that the message can be delivered to the target vehicle or user efficiently and accurately.

[0098] Step C13: When the sending status information is "sent successfully" or the retransmission status information is "retransmission successfully", modify the message status in the database;

[0099] Understandably, when a message is successfully sent to the target recipient, or successfully sent after a retransmission attempt, the status of the corresponding message in the database is updated, or other related status information, such as the number of times the message was sent and the time of the last sending attempt, is updated to reflect the latest status of the message.

[0100] Step C14: When the sending status information is "sending failed" and the retransmission status information is "retransmission failed", the message status in the database is not modified.

[0101] Understandably, if a message fails to be sent on its first attempt during message transmission, the system will resend it according to a preset strategy. If the resend attempt also fails, it indicates a persistent problem, such as network failure, unavailability of the message middleware service, or message format not supported by the recipient. In this case, the message status in the database is not modified, which facilitates the identification and diagnosis of the problem and retains log information about message transmission failures. Based on the cause and frequency of failures, different processing procedures can be automatically triggered, such as switching to a backup message channel, adjusting the message format or content, or requesting manual intervention, so as to further analyze and process the failed messages and improve the success rate of message transmission and the overall stability of the system.

[0102] This embodiment proposes a message transmission method based on a vehicle-to-everything (V2X) platform. The method involves acquiring message request information and message template information; sending messages based on the message request information and message template information to determine the message middleware queue status information; and controlling the vehicle message middleware to distribute buffered messages in a first-in-first-out (FIFO) manner based on the message middleware queue status information. This solves the technical problem of how to perform message transmission and distribution more efficiently and flexibly. Compared to existing technologies, this application, by acquiring message request information and message template information, effectively manages and optimizes the message sending process using message middleware, and controls message transmission and distribution through a FIFO mechanism. This avoids resource waste, maintenance difficulties, and complex problem troubleshooting, not only improving the orderliness and timeliness of message transmission but also significantly enhancing the response speed and data processing capabilities of the V2X platform, providing users with a more stable and smooth intelligent transportation experience.

[0103] Based on the first embodiment of this application, in the second embodiment of this application, the same or similar content as the first embodiment can be referred to the above description, and will not be repeated hereafter.

[0104] In this embodiment, refer to Figure 4 , Figure 4 This is a flowchart illustrating Embodiment 2 of the message information transmission method based on the vehicle networking platform of this application. Step S20 specifically includes steps S21 to S23:

[0105] Step S21: Obtain email service information;

[0106] In one feasible implementation, step S21 may include steps D11 to D12:

[0107] It should be noted that the email service information reflects the characteristics of the integrated vehicle networking platform's ability to adapt to different message channels during message transmission.

[0108] It is understandable that the email service information is saved to the database so that this information can be read directly from the database table without having to reconfigure this information every time a message is sent. The mailDefaultEncoding in the email service information is the default email encoding, which is usually UTF-8.

[0109] Additionally, it should be noted that by ensuring the correct configuration of email service information, email sending failures due to configuration errors can be reduced, improving the accuracy of message delivery. Furthermore, selecting different email services according to different needs enhances the system's flexibility and adaptability, and ensures that important notices and key information can be sent to users in a timely and accurate manner, thereby improving user experience and satisfaction.

[0110] For ease of understanding, we will take obtaining email service information as an example. The information collection device is the information collection module, the storage device is the memory, and the processing device is the processing module.

[0111] The information acquisition device obtains the mail server code, mail server address, mail server port, mail login account, mail account login password, and mail default encoder and stores them in the memory. Based on the mail server code, mail server address, mail server port, mail login account, mail account login password, and mail default encoder, it determines the service email information and performs subsequent processing based on the service email information.

[0112] Step D11: Obtain the email sending service account and email sending service password;

[0113] Understandably, requesting server resources requires a server capable of integrating the messaging channel's functionality. This server needs domain name configuration to ensure access during message sending. Enabling SMTP mail forwarding functionality requires providing an SMTP account and password to send emails via SMTP and saving the SMTP service information to a database. Figure 5 As shown, Figure 5 This is a schematic diagram of the email service information of the message information transmission method based on the vehicle network platform of this application. It includes email server code, email server address, email server port, email login account, email login password and email default encoder. The email server code, email server address, email server port, email login account, email login password and email default encoder are saved in the database, so that these information do not need to be reconfigured every time a message is sent.

[0114] Step D12: Determine email service information based on the email sending service account and email sending service password. The email service information includes email server ID, email server address, email server port, email login account, email login password, and email default encoder.

[0115] It should be noted that the email service information reflects the characteristics of using email channels for message transmission.

[0116] It is understood that the email service information may include the mail server's identifier, address, port, login account, login password, and default encoder. Configuring the email service based on the email service information can ensure that emails can be correctly sent to the designated recipients, and enable the email service to be personalized according to different needs.

[0117] Step S22: Determine the push message package based on the email service information, message request information, and message template information;

[0118] It should be noted that the push message package reflects the characteristics of the push messages that are expected to be packaged.

[0119] It is understandable that when creating a push message package, the SMTP server settings in the email service information, combined with the recipient information, message encoding, template content, and other content in the message template in the message request information, will form a complete message package. The message package includes the generated push feature identifier, so that the email service can correctly send the message to the specified recipient.

[0120] Additionally, it should be noted that the server connection parameters for sending emails can be configured based on the SMTP server address, port, login account, and password in the email service information. The recipient's address can be determined based on the recipient information in the message request information. The email title and content can be obtained based on the message template information. If the template contains variables, the corresponding variables in the template can be replaced based on the variable value key-value pair information. The sending method and timing of the email sending can be determined based on the sending method information, such as immediate or scheduled sending. Additional options for the email can be set based on the push selection parameter information, such as whether a receipt is required and email priority. A suitable email sending channel can be selected based on the push channel information to ensure that the email is sent through the correct channel. A resend mechanism for email sending failure can be set based on the enabled resend information and the target resend count. A response mechanism after email sending and timeout handling when no response is received can be set based on the response information and response timeout information. The configured email parameters are then packaged into a push message package, which will be sent to the message middleware queue to ensure the correctness of the email content and the accuracy of email sending. This effectively delivers the message to the target recipient, while improving the efficiency and reliability of message delivery.

[0121] For ease of understanding, we will take the acquisition of push message packets as an example, where the information acquisition device is the information acquisition module, the storage device is the memory, and the processing device is the processing module.

[0122] The information collection device acquires email service information, message request information, and message template information and stores them in the memory. It verifies the existence of the message template based on the message encoding information (msgCd) in the message request information; if it does not exist, it reports an error. It then verifies whether the message template has been published; if not, it reports an error. Next, it verifies the validity of the message channel; if it is an invalid channel, it reports an error. Finally, it verifies the existence of the template content corresponding to the template encoding; if it does not exist, it reports an error. Based on the message request information and message template information, it sends a message, determines the message middleware queue status information, fills in the message content, title, scheduled task, interval task, and other content information from the message request information, packages it, and determines the push message package. Subsequent processing is then performed based on the push message package.

[0123] Step S23: Send the push message packet to the message middleware queue to obtain the message middleware queue status information.

[0124] It should be noted that the message middleware is responsible for message storage, queuing, and distribution, and is used to handle high-throughput message transmission.

[0125] Understandably, Kafka can be used as a message middleware. Kafka is a distributed stream processing platform that efficiently processes real-time data streams. When messages are sent to the system, Kafka can store these messages in a queue as a buffer until they are distributed. It also supports asynchronous message delivery, meaning that message producers can send messages without waiting for them to be processed by consumers, and ensures that messages are not lost due to system failures.

[0126] Additionally, it's important to note that message distribution is achieved by listening to Kafka topics, configuring Kafka consumers, and configuring consumer groups for these consumers. These consumer groups enable message load balancing and failover. Each consumer needs to subscribe to one or more topics, which serve as message delivery channels. Consumers establish connections by identifying the addresses of at least one server in the Kafka cluster and can configure SSL, TLS, or other security protocols to protect data transmission. Consumers can periodically send requests to the Kafka server to retrieve new messages. When the Kafka server has new messages, it sends them to the consumers. Upon receiving the messages, the consumers parse the message content and process them according to actual business needs, such as updating the database or triggering other service operations.

[0127] For ease of understanding, we will take the acquisition of message middleware queue status information as an example, where the information acquisition device is the information acquisition module, the storage device is the memory, and the processing device is the processing module.

[0128] The information acquisition module obtains push message packets, sends the push message packets to the message middleware queue to obtain message middleware queue status information, listens to the message middleware queue status information, packages and pushes messages in a first-in-first-out manner, and generates push IDs. Based on the push IDs, the messages are sent to the Kafka topic. The module listens to the Kafka topic, and upon receiving a message, retrieves the corresponding information from Kafka to distribute the message to the corresponding channel. It obtains the sending status information. When the sending status information indicates a sending failure, it resends and distributes the message to the corresponding channel to determine the resend status information. When the sending status information indicates a sending success or the resend status information indicates a resend success, it modifies the message status in the database. When both the sending status information and the resend status information indicate a sending failure, it does not modify the message status in the database.

[0129] This embodiment proposes a message transmission method based on a vehicle-to-everything (V2X) platform. The method involves acquiring email service information; determining a push message package based on the email service information, message request information, and message template information; and sending the push message package to a message middleware queue to obtain the message middleware queue status information. This solves the technical problem of how to personalize and integrate a message middleware queue for message transmission and distribution. Compared to existing technologies, this application improves the personalization and accuracy of email sending by acquiring email service information, combining message request and template information to construct a push message package, and then sending it to the message middleware queue. Furthermore, the efficient management and distribution mechanism of the message middleware enhances the system's performance and stability when handling high-throughput message transmission, providing users with a more reliable and efficient email communication service experience.

[0130] For example, to help understand the implementation flow of the message transmission method based on the vehicle network platform obtained by combining this embodiment with the above embodiment one, please refer to... Figure 6 , Figure 6 A simplified flowchart of a message transmission method based on a vehicle-to-everything (V2X) platform is provided, specifically:

[0131] Referring to Example 1, message request information and message template information are obtained; based on the message request information and message template information, a message is sent to determine the message middleware queue status information; based on the message middleware queue status information, the vehicle message middleware is controlled to distribute buffered messages in a first-in-first-out manner. When creating a message template, it is determined whether there is a corresponding sending channel. If there is no corresponding sending channel, a message channel is created, filling in fields such as server type, server address, and protocol. After the message channel is created, a message template is created based on the message channel. If there is a corresponding sending channel, a message template is created directly based on the message channel, filling in the message content title, scheduled task, and interval task, and sending the message based on the message template content. Referring to Example 2, email service information is obtained; based on the email service information, message request information, and message template information, a push message package is determined; the push message package is sent to the message middleware queue to obtain the message middleware queue status information. The message middleware queue status information is monitored, and messages are distributed to the corresponding channels in a first-in-first-out manner to determine the sending status information. When the sending status information indicates a sending failure, the corresponding channel message is resent and distributed to determine the retransmission status information. When the sending status information indicates a sending success or the retransmission status information indicates a retransmission success, the message status in the database is modified. When both the sending status information and the retransmission status information indicate a retransmission failure, the message status in the database is not modified.

[0132] It should be noted that the above examples are only for understanding this application and do not constitute a limitation on the message transmission method based on the vehicle networking platform of this application. Any simple modifications based on this technical concept are within the protection scope of this application.

[0133] This application also provides a message transmission device based on a vehicle networking platform; please refer to [reference needed]. Figure 7 The message transmission device based on the vehicle networking platform includes:

[0134] Module 10 is used to obtain message request information and message template information;

[0135] Processing module 20 is used to send a message based on the message request information and message template information to determine the message middleware queue status information;

[0136] The execution module 30 is used to control the vehicle message middleware to distribute buffered messages in a first-in-first-out manner based on the message middleware queue status information.

[0137] The acquisition module 10 is also used to acquire variable value key-value pair information, message encoding information, recipient information, extended parameter information, sending method information, push selection parameter information, push channel information, retransmission enabled information, target retransmission count, response information, response timeout information, timed push information, message encoding, message title, template content, approval status, and internationalization content.

[0138] The message request information is determined based on the variable value key-value pair information, message encoding information, recipient information, extended parameter information, sending method information, push selection parameter information, push channel information, retransmission enabled information, target retransmission count, response information, response timeout information, and timed push information.

[0139] The message template is determined based on the message encoding, message title, template content, approval status, and internationalized content.

[0140] The acquisition module 10 is also used to acquire channel existence status information;

[0141] When the channel status information indicates that a channel exists, the message template is determined based on the message code, message title, template content, approval status, and internationalized content.

[0142] When the channel status information indicates that there is no channel, obtain recommended channel information, generate channel configuration information based on the recommended channel information, and determine the message template based on the channel configuration information, message code, message title, template content, approval status, and internationalization content.

[0143] The processing module 20 is also used to obtain email service information;

[0144] The push message package is determined based on the email service information, message request information, and message template information;

[0145] The push message packet is sent to the message middleware queue to obtain the message middleware queue status information.

[0146] The processing module 20 is also used to obtain the email sending service account and email sending service password.

[0147] The email service information is determined based on the email sending service account and email sending service password. The email service information includes the email server ID, email server address, email server port, email login account, email login password, and email default encoder.

[0148] The execution module 30 is also used to monitor the status information of the message middleware queue and distribute the corresponding channel message in a first-in-first-out manner to determine the sending status information;

[0149] When the sending status information indicates a sending failure, the message corresponding to the distribution channel is resent to determine the resentment status information.

[0150] When the sending status information is "sent successfully" or the retransmission status information is "retransmission successfully", modify the message status in the database;

[0151] When the sending status information is "sending failed" and the retransmission status information is "retransmission failed", the message status in the database is not modified.

[0152] The message transmission device based on a vehicle-to-everything (V2X) platform provided in this application, employing the message transmission method based on a V2X platform described in the above embodiments, can solve the technical problem of how to transmit messages more efficiently and flexibly, and adapt to various message transmission needs. Compared with the prior art, the beneficial effects of the message transmission device based on a V2X platform provided in this application are the same as those of the message transmission method based on a V2X platform provided in the above embodiments, and other technical features in the message transmission device based on a V2X platform are the same as those disclosed in the methods of the above embodiments, and will not be repeated here.

[0153] This application provides a message transmission device based on a vehicle networking platform. The message transmission device based on a vehicle networking platform includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to execute the message transmission method based on the vehicle networking platform in the above embodiment 1.

[0154] Reference below Figure 8 This document illustrates a structural schematic diagram of a message transmission device based on a vehicle-to-everything (V2X) platform suitable for implementing embodiments of this application. The message transmission device based on a V2X platform in these embodiments may include, but is not limited to, mobile terminals such as mobile phones, laptops, digital radio receivers, PDAs (Personal Digital Assistants), PADs (Portable Application Description), PMPs (Portable Media Players), and in-vehicle terminals (e.g., in-vehicle navigation terminals), as well as fixed terminals such as digital TVs and desktop computers. Figure 8 The message transmission device based on the vehicle networking platform shown is merely an example and should not impose any limitations on the functionality and scope of use of the embodiments of this application.

[0155] like Figure 8As shown, the message transmission device based on the vehicle-to-everything (V2X) platform may include a processing unit 1001 (e.g., a central processing unit, a graphics processing unit, etc.), which can perform various appropriate actions and processes according to programs stored in read-only memory (ROM) 1002 or programs loaded from storage device 1003 into random access memory (RAM) 1004. The RAM 1004 also stores various programs and data required for the operation of the message transmission device based on the V2X platform. The processing unit 1001, ROM 1002, and RAM 1004 are interconnected via a bus 1005. An input / output (I / O) interface 1006 is also connected to the bus. Typically, the following systems can be connected to I / O interface 1006: input devices 1007 including, for example, touchscreens, touchpads, keyboards, mice, image sensors, microphones, accelerometers, gyroscopes, etc.; output devices 1008 including, for example, liquid crystal displays (LCDs), speakers, vibrators, etc.; storage devices 1003 including, for example, magnetic tapes, hard disks, etc.; and communication devices 1009. Communication device 1009 allows the vehicle-to-everything (V2X) platform-based messaging device to exchange data with other devices wirelessly or via wired communication. Although the figure shows a V2X platform-based messaging device with various systems, it should be understood that it is not required to implement or possess all of the systems shown. More or fewer systems may be implemented alternatively.

[0156] In particular, according to the embodiments disclosed in the present application, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, the embodiments disclosed in the present application include a computer program product comprising a computer program carried on a computer-readable medium, the computer program comprising program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network via a communication device, or installed from a storage device 1003, or installed from a ROM 1002. When the computer program is executed by the processing device 1001, the above-mentioned functions defined in the method of the embodiment disclosed in the present application are executed.

[0157] The message transmission device based on a vehicle-to-everything (V2X) platform provided in this application, employing the message transmission method based on a V2X platform described in the above embodiments, can solve the technical problem of how to transmit messages more efficiently and flexibly, and adapt to various message transmission needs. Compared with the prior art, the beneficial effects of the message transmission device based on a V2X platform provided in this application are the same as those of the message transmission method based on a V2X platform provided in the above embodiments, and other technical features of this message transmission device based on a V2X platform are the same as those disclosed in the previous embodiment method, and will not be repeated here.

[0158] It should be understood that the various parts disclosed in this application can be implemented using hardware, software, firmware, or a combination thereof. In the description of the above embodiments, specific features, structures, materials, or characteristics can be combined in any one or more embodiments or examples in a suitable manner.

[0159] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.

[0160] This application provides a computer-readable storage medium having computer-readable program instructions (i.e., a computer program) stored thereon, the computer-readable program instructions being used to execute the message information transmission method based on the vehicle networking platform in the above embodiments.

[0161] The computer-readable storage medium provided in this application may be, for example, a USB flash drive, but is not limited to electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, systems or devices, or any combination thereof. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof. In this embodiment, the computer-readable storage medium may be any tangible medium that contains or stores a program that can be used by or in conjunction with an instruction execution system, system or device. The program code contained on the computer-readable storage medium may be transmitted using any appropriate medium, including but not limited to: wires, optical cables, RF (Radio Frequency), etc., or any suitable combination thereof.

[0162] The aforementioned computer-readable storage medium may be included in a message transmission device based on a vehicle-to-everything (V2X) platform; or it may exist independently and not be installed in a message transmission device based on a V2X platform.

[0163] The aforementioned computer-readable storage medium carries one or more programs. When the aforementioned one or more programs are executed by a message transmission device based on a vehicle-to-everything (V2X) platform, the message transmission device based on the V2X platform causes the following: to acquire message request information and message template information; to send messages based on the message request information and message template information to determine message middleware queue status information; and to control the vehicle message middleware to distribute buffered messages in a first-in-first-out (FIFO) manner based on the message middleware queue status information.

[0164] Computer program code for performing the operations of the present application may be written in one or more programming languages, or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, C++, and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a stand-alone software package, partially on the user's computer and partially on a remote computer, or entirely on the remote computer or server. In cases involving a remote computer, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., through the Internet using an Internet service provider).

[0165] The flow charts and block diagrams in the accompanying drawings illustrate the possible architecture, functions and operations of the systems, methods and computer program products according to various embodiments of the present application. In this regard, each box in the flow chart or block diagram can represent a module, program segment or a part of code, and the module, program segment or a part of code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order than that marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram and / or flow chart, and the combination of the boxes in the block diagram and / or flow chart can be implemented by a dedicated hardware-based system that performs the specified function or operation, or can be implemented by a combination of dedicated hardware and computer instructions.

[0166] The modules described in the embodiments of the present application may be implemented in software or hardware, wherein the name of a module does not necessarily limit the unit itself.

[0167] The readable storage medium provided in this application is a computer-readable storage medium that stores computer-readable program instructions (i.e., computer programs) for executing the aforementioned message transmission method based on a vehicle-to-everything (V2X) platform. This solves the technical problem of how to transmit messages more efficiently and flexibly, and how to adapt to various message transmission needs. Compared with the prior art, the beneficial effects of the computer-readable storage medium provided in this application are the same as those of the message transmission method based on a V2X platform provided in the above embodiments, and will not be repeated here.

[0168] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the steps of the message information transmission method based on the vehicle networking platform described above.

[0169] The computer program product provided in this application can solve the technical problem of how to transmit message information more efficiently and flexibly, and how to adapt to various message transmission needs. Compared with the prior art, the beneficial effects of the computer program product provided in this application are the same as those of the message transmission method based on the vehicle network platform provided in the above embodiments, and will not be repeated here.

[0170] The above description is only part of the embodiments of the present application and does not limit the patent scope of the present application. All equivalent structural transformations made by using the contents of the present application specification and drawings under the technical concept of the present application, or direct / indirect application in other related technical fields are included in the patent protection scope of the present application.

Claims

1. A message information transmission method based on an Internet of Vehicles platform, characterized in that: The method includes: Get message request information and message template information; Sending a message based on the message request information and the message template information to determine the message middleware queue status information; Based on the message middleware queue status information, the vehicle message middleware is controlled to distribute the buffered messages in a first-in-first-out manner.

2. The method according to claim 1, characterized in that The step of obtaining message request information and message template information includes: Get variable value key-value pair information, message encoding information, recipient information, extended parameter information, sending method information, push selection parameter information, push channel information, enable resend information, target resend times, response information, response timeout information, scheduled push information, message encoding, message title, template content, approval status and internationalization content; Determine message request information based on the variable value key-value pair information, message encoding information, recipient information, extended parameter information, sending method information, push selection parameter information, push channel information, enable resend information, target resend times, response information, response timeout information and scheduled push information; A message template is determined based on the message code, message title, template content, approval status and internationalized content.

3. The method according to claim 2, characterized in that The step of determining the message template based on the message code, message title, template content, approval status and international content includes: Get channel existence status information; When the channel existence status information indicates that the channel exists, determining a message template based on the message code, message title, template content, approval status and international content; When the channel existence status information indicates that the channel does not exist, the recommended channel information is obtained, channel configuration information is generated based on the recommended channel information, and a message template is determined based on the channel configuration information, message encoding, message title, template content, approval status and internationalized content.

4. The method according to claim 1, characterized in that The step of sending a message based on the message request information and the message template information to determine the message middleware queue status information comprises: Get mail service information; Determine a push message package based on the mail service information, the message request information and the message template information; The push message packet is sent to the message middleware queue to obtain the message middleware queue status information.

5. The method according to claim 4, characterized in that The step of obtaining mail service information includes: Obtain the account and password of the mail sending service; The mail service information is determined based on the mail sending service account and the mail sending service password, wherein the mail service information includes a mail server code, a mail server address, a mail server port, a mail login account, a mail account login password and a mail default encoder.

6. The method according to claim 1, characterized in that The step of controlling the vehicle message middleware to distribute the buffered messages in a first-in-first-out manner based on the message middleware queue status information comprises: Monitor the message middleware queue status information and distribute the corresponding channel messages in a first-in-first-out manner to determine the sending status information; When the sending status information indicates that the sending fails, resending the distribution corresponding channel message to determine the resending status information; When the sending status information indicates that the sending is successful or the resending status information indicates that the resending is successful, modifying the message status in the database; When the sending status information indicates sending failure and the resending status information indicates resending failure, the message status in the database is not modified.

7. A message information transmission device based on the Internet of Vehicles platform, characterized in that: The device comprises: An acquisition module is used to obtain message request information and message template information; A processing module, used for sending a message based on the message request information and the message template information to determine the message middleware queue status information; The execution module is used to control the vehicle message middleware to distribute the buffered messages in a first-in-first-out manner based on the message middleware queue status information.

8. A message information transmission device based on the Internet of Vehicles platform, characterized in that: The device comprises: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the computer program is configured to implement the steps of the message information transmission method based on the Internet of Vehicles platform as described in any one of claims 1 to 6.

9. A storage medium, characterized in that: The storage medium is a computer-readable storage medium, and a computer program is stored on the storage medium. When the computer program is executed by a processor, the steps of the message information transmission method based on the Internet of Vehicles platform as described in any one of claims 1 to 6 are implemented.

10. A computer program product, characterized in that The computer program product includes a computer program, and when the computer program is executed by a processor, the steps of the message information transmission method based on the Internet of Vehicles platform as described in any one of claims 1 to 6 are implemented.

Images