A data exchange system and method across a vehicle networking system

Abstract

The application provides a data exchange system and method of a cross-vehicle networking system, and the method steps comprise: a forwarding client performing protocol conversion on an instruction message sent by a vehicle networking platform; a forwarding server parsing the obtained message instruction to extract instruction parameters, a sender identification number and an original instruction sequence number to generate an instruction unique identification, and storing the instruction unique identification in a distributed cache server; a vehicle networking gateway converts the instruction parameters into an instruction data packet to generate a real serial number, publishes the instruction unique identification and the real serial number to a distributed message bus, and sends the instruction data packet to a vehicle terminal; the forwarding server obtains the instruction unique identification and the real serial number from the distributed message bus, obtains the original instruction sequence number and the sender identification number in the distributed cache server, locates the forwarding client, and sends a first data packet to establish a mapping relationship; and subsequent instruction response messages are returned according to the mapping relationship of the sequence numbers and the serial numbers, so as to realize an instruction transparent transmission function when a vehicle is monitored by multiple platforms.

Description

Technical Field

[0001] This invention relates to vehicle-to-everything (V2X) data communication technology, and more particularly to a data exchange system and method for cross-vehicle V2X systems. Background Technology

[0002] In recent years, with the development of IoT and Internet technologies, the commercial use of vehicle-to-everything (V2X) has become increasingly mature. my country's Ministry of Transport has specifically formulated the JT / T 808 and JT / T1078 protocols to promote orderly development. When dealing with the communication between the BeiDou-compatible vehicle terminal of the road transport vehicle satellite positioning system and the supervision / monitoring platform, many V2X manufacturers usually choose to use the JT / T 808 and JT / T1078 communication protocols formulated by the Ministry of Transport.

[0003] However, the JT / T808 and JT / T1078 communication modes are one-question-one-response methods, meaning that when a data message is received from the other party, a response is required for that message (except for the response message). This requires that each message must have a relatively unique sequence number. At the same time, in order to prevent packet loss, the sequence numbers of messages must be consecutive.

[0004] Therefore, when multiple vehicle location monitoring platforms are monitoring the same batch of vehicles, a third-party vehicle networking platform faces a problem when sending instructions to the vehicle terminal: the platform initiating the instruction generates an instruction sequence number, but the platform connected to the actual vehicle terminal cannot use the instruction sequence number generated by the initiator due to the requirement of continuous packet sequence numbers. Instead, it must generate a sequence number based on the actual situation (e.g., ...). Figure 1 As shown in the figure, the instruction sequence number generated by the instruction initiator and the instruction sequence number received by the vehicle terminal are inconsistent, so the instruction cannot complete the business loop.

[0005] Therefore, in the past, data forwarding services typically only forwarded data reported by the vehicle terminal and could not transmit instructions. Summary of the Invention

[0006] Therefore, the main objective of this invention is to provide a vehicle network data cluster forwarding system and method to solve the problem in the background art where data forwarding services cannot transmit instructions when monitoring vehicles on multiple platforms.

[0007] To achieve the above objectives, according to a first aspect of the present invention, a data exchange system for cross-vehicle networking systems is provided, comprising:

[0008] The vehicle-to-everything (V2X) platform sends command messages to the forwarding client and receives command response messages.

[0009] The forwarding client receives the transparent transmission instruction message, performs forwarding protocol conversion, and then sends it to the forwarding server.

[0010] The forwarding server parses the transparent transmission command message, obtains the command parameters, sender identifier, and original command sequence number; generates a unique command identifier that maps to the original command sequence number and sender identifier, and stores it in a distributed cache server; and initiates a command request with the unique command identifier to the vehicle network gateway.

[0011] The vehicle-to-everything (V2X) gateway receives command parameters, converts them into command data packets according to the Ministry of Industry and Information Technology (MIIT) standard, generates a real serial number, and publishes the unique identifier of the command and the real serial number to the distributed message bus; it then sends command data packets to the vehicle terminal.

[0012] The forwarding server obtains the unique instruction identifier and real serial number from the distributed message bus. After finding the corresponding original instruction sequence number and sender identifier in the distributed cache server based on the unique instruction identifier, it finds the corresponding forwarding client based on the sender identifier and sends the first data packet containing the original instruction sequence number and real serial number.

[0013] The forwarding client receives the first data packet, parses it, stores it, and establishes a mapping relationship between the real serial number and the original instruction sequence number;

[0014] The vehicle-to-everything (V2X) gateway receives instruction response messages containing real serial numbers reported by the vehicle terminals and publishes them to the distributed message bus.

[0015] The forwarding server obtains instruction response messages from the distributed message bus, performs forwarding protocol conversion, and then distributes the instruction response messages to each forwarding client.

[0016] The client forwards the message, parses the instruction response message, and obtains the real serial number. When the corresponding original instruction number is found, the instruction response message is converted to the Ministry of Transport's standard protocol and then sent to the corresponding vehicle network platform.

[0017] In a possible preferred embodiment, the forwarding server serializes the instruction parameters into a JSON string and sends an instruction request with a unique instruction identifier to the vehicle network gateway by calling the vehicle network gateway cluster API interface.

[0018] In a possible preferred embodiment, the vehicle network gateway invokes the TCP network component to send instruction data packets to the vehicle terminal / send instruction response messages to the vehicle network platform.

[0019] In a possible preferred embodiment, the forwarding server invokes the UDP communication component to send a first data packet containing the original instruction sequence number and the real serial number to the forwarding client, or distributes the instruction response message to each forwarding client.

[0020] In a possible preferred embodiment, the step of the forwarding client receiving the transparent instruction message and performing forwarding protocol conversion includes: creating a forwarding protocol packet object including: a start flag, a header, a body, and a checksum; setting various parameters of the forwarding protocol packet header including: message length, message type, message sequence number, sender identifier, and packet information; setting the instruction message as the body of the forwarding protocol packet; verifying the data and obtaining the checksum to set as the checksum of the forwarding protocol; and finally encoding and packaging the data according to the forwarding protocol.

[0021] In a possible preferred embodiment, the step of the forwarding server parsing the transparent transmission instruction message includes: parsing the packet header according to the forwarding protocol, parsing the packet body according to the message type in the packet header, obtaining the transparent transmission instruction message of the Ministry Standard Protocol, parsing its Ministry Standard packet header according to the Ministry Standard Protocol, obtaining the message type in its packet header and parsing its packet body accordingly, and obtaining the instruction parameters accordingly.

[0022] To achieve the above objectives, according to a second aspect of the present invention, a data exchange method for cross-vehicle network systems is also provided, comprising the steps of:

[0023] During the command transmission phase:

[0024] Step S100: The forwarding client receives the transparent transmission instruction message sent by the vehicle networking platform, performs forwarding protocol conversion, and then sends it to the forwarding server;

[0025] Step S200: The forwarding server parses the transparent transmission command message, obtains the command parameters, sender identifier, and original command sequence number; generates a unique command identifier that maps to the original command sequence number and sender identifier, and stores it in the distributed cache server; and initiates a command request with the unique command identifier to the vehicle network gateway.

[0026] Step S300: The vehicle networking gateway receives the instruction parameters, converts them into instruction data packets of the Ministry of Industry and Information Technology (MIIT) standard protocol, generates a real serial number, and publishes the unique identifier of the instruction and the real serial number to the distributed message bus; then it sends the instruction data packets to the vehicle terminal.

[0027] In step S400, the forwarding server obtains the instruction unique identifier and real serial number from the distributed message bus. After finding the corresponding original instruction sequence number and sender identifier in the distributed cache server based on the instruction unique identifier, it finds the corresponding forwarding client based on the sender identifier and sends the first data packet containing the original instruction sequence number and real serial number.

[0028] Step S500: The forwarding client receives the first data packet, parses it, stores it, and establishes a mapping relationship between the real serial number and the original instruction sequence number.

[0029] In a possible preferred embodiment, the data exchange method across vehicle-to-everything (V2X) systems further includes a command response phase, the steps of which include:

[0030] In step S600, the vehicle-to-everything (V2X) gateway receives the instruction response message containing the real serial number reported by the vehicle terminal and publishes it to the distributed message bus.

[0031] In step S700, the forwarding server obtains the instruction response message from the distributed message bus, performs forwarding protocol conversion, and then distributes the instruction response message to each forwarding client.

[0032] Step S800 forwards the client to parse the instruction response message and obtain the real serial number. When the corresponding original instruction sequence number is found, the instruction response message is converted to the Ministry of Transport's standard protocol and then sent to the corresponding vehicle network platform.

[0033] In a possible preferred embodiment, step S100, in which the forwarding client receives the transparent instruction message and performs forwarding protocol conversion, includes: creating a forwarding protocol packet object including: a start flag, a header, a body, and a checksum; setting various parameters of the forwarding protocol header including: message length, message type, message sequence number, sender identifier, and packet information; setting the instruction message as the body of the forwarding protocol packet; verifying the data and obtaining the checksum to set as the checksum of the forwarding protocol; and finally encoding and packaging the data according to the forwarding protocol.

[0034] In a possible preferred embodiment, step S200, the step of the forwarding server parsing the transparent transmission instruction message includes: parsing the packet header according to the forwarding protocol, parsing the packet body according to the message type in the packet header, obtaining the transparent transmission instruction message of the Ministry Standard Protocol, parsing its Ministry Standard packet header according to the Ministry Standard Protocol, obtaining the message type in its packet header and parsing its packet body accordingly, and obtaining the instruction parameters accordingly.

[0035] The data exchange system and method for cross-vehicle networking systems provided by this invention solves the problem of inconsistency between the original instruction sequence number and the real serial number through the design of a communication scheme for the conversion between instruction sequence numbers. It realizes a closed loop of business in terms of monitoring the same batch of vehicles and sending instructions on a multi-platform, multi-level vehicle monitoring platform, as well as instruction pass-through function during data forwarding service.

[0036] Furthermore, this invention enables two or more vehicle positioning and monitoring systems to simultaneously monitor the same batch of vehicles without requiring the installation of onboard terminals, thus significantly reducing the economic costs for transportation companies. Simultaneously, it allows for simultaneous monitoring of the same batch of vehicles without modifying the embedded program of the onboard terminal, saving transportation companies hardware costs and thus possessing high application value. Attached Figure Description

[0037] The accompanying drawings, which form part of this application, are used to provide a further understanding of the invention. The illustrative embodiments of the invention and their descriptions are used to explain the invention and do not constitute an undue limitation of the invention. In the drawings:

[0038] Figure 1 This is an example of an information transmission architecture in the background art that cannot perform instruction pass-through;

[0039] Figure 2 This is a schematic diagram of the data exchange system architecture of the cross-vehicle network system of the present invention;

[0040] Figure 3 This is a schematic diagram of the data forwarding protocol packet structure in the data exchange system of the cross-vehicle network system of the present invention;

[0041] Figure 4 This is a schematic diagram illustrating the protocol conversion of a data forwarding protocol packet carrying a national standard protocol packet in an example of a cross-vehicle network system data exchange system of the present invention.

[0042] Figure 5 This is a schematic diagram of the instruction transmission stage steps in the data exchange method for cross-vehicle network systems of the present invention;

[0043] Figure 6 This is a schematic diagram of the instruction response stage steps in the data exchange method for cross-vehicle network systems of the present invention. Detailed Implementation

[0044] To enable those skilled in the art to better understand the technical solutions of the present invention, the specific technical solutions of the present invention will be clearly and completely described below in conjunction with embodiments, so as to help those skilled in the art further understand the present invention. Obviously, the embodiments described in this application are merely some embodiments of the present invention, and not all embodiments. It should be noted that, for those skilled in the art, the embodiments and features in the embodiments of this application can be combined with each other without departing from the concept of the present invention and without conflict. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort should fall within the disclosure and protection scope of the present invention.

[0045] Furthermore, the terms "first," "second," "S100," "S200," etc., used in the specification, claims, and drawings of this invention 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 embodiments of the invention described herein can be implemented in orders other than those described herein. At the same time, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion. Unless otherwise expressly specified and limited, the terms "set," "arranged," "installed," "connected," and "linked" should be interpreted broadly, for example, as a fixed connection, a detachable connection, or an integral connection; a mechanical connection or an electrical connection; a direct connection or an indirect connection through an intermediate medium; or a connection within two elements. Those skilled in the art can understand the specific meaning of the above terms in this case according to the specific circumstances and in conjunction with existing technology.

[0046] The standard protocol specification described in this invention references the following specifications:

[0047] JT / T808: This refers to the "Communication Protocol and Data Format for Satellite Positioning System Terminals of Road Transport Vehicles" promulgated by the Ministry of Transport of the People's Republic of China.

[0048] JT / T1078: This refers to the "Video Communication Protocol for Satellite Positioning System of Road Transport Vehicles" promulgated by the Ministry of Transport of the People's Republic of China.

[0049] like Figures 2 to 4 As shown, the present invention exemplifies a data exchange system for cross-vehicle networking systems, comprising:

[0050] During the command transmission phase:

[0051] The vehicle networking platform, as defined in this invention, is an external third-party commercial vehicle positioning and monitoring system that, during the command transmission phase, sends command messages to the forwarding client (and receives command response messages in the subsequent command response phase).

[0052] The forwarding client receives the transparent transmission command message, performs forwarding protocol conversion, and then sends it to the forwarding server. For example... Figures 3 to 4 As shown, the steps of this forwarding protocol conversion include: creating a forwarding protocol packet object, including: start flag, packet header, packet body, and checksum; setting various parameters of the forwarding protocol packet header, including: message length, message type, message sequence number, sender identifier, and packet information; setting the instruction message as the packet body of the forwarding protocol packet; verifying the data and obtaining the checksum to set as the checksum of the forwarding protocol; and finally encoding and packaging the data according to the forwarding protocol.

[0053] The forwarding server parses the transparent transmission command message converted by the forwarding protocol to obtain the command parameters, sender identifier, and original command sequence number. The steps for parsing the transparent transmission command message include: parsing the packet header according to the forwarding protocol; parsing the packet body according to the message type in the packet header to obtain the transparent transmission command message of the national standard protocol; parsing the national standard protocol's packet header according to the national standard protocol to obtain the message type in the packet header; and then parsing the packet body accordingly to obtain the command parameters.

[0054] Then, a unique instruction identifier is generated that maps to the original instruction sequence number and sender identifier, and stored in a distributed cache server.

[0055] Next, the forwarding server sets various instruction parameters according to the parameter requirements of the vehicle network gateway cluster API, then serializes the instruction parameters into a JSON string, and sends an instruction request with a unique instruction identifier to the vehicle network gateway by calling the vehicle network gateway cluster API interface.

[0056] In this invention, a vehicle networking gateway is defined as a commercial vehicle positioning and monitoring system accessed by an in-vehicle terminal. During the command transmission phase, the gateway receives command parameters, converts them into command data packets of the Ministry of Transport's standard protocol, generates a real serial number, publishes the unique identifier of the command and the real serial number to the distributed message bus, and simultaneously calls the TCP network component to send command data packets to the in-vehicle terminal for execution.

[0057] The forwarding server obtains the unique instruction identifier and real serial number from the distributed message bus. It then uses this identifier to find the corresponding original instruction sequence number and sender identifier in the distributed cache server. Based on the sender identifier, it finds the corresponding forwarding client and calls the UDP communication component to send the first data packet containing the original instruction sequence number and real serial number to the forwarding client.

[0058] The forwarding client receives the first data packet, parses it, stores it, and establishes a mapping relationship between the real serial number and the original instruction sequence number.

[0059] During the instruction response phase:

[0060] The vehicle-to-everything (V2X) gateway receives instruction response messages containing real serial numbers reported by the vehicle-mounted terminals and sends them to the distributed message bus.

[0061] The forwarding server retrieves instruction response messages from the distributed message bus, performs forwarding protocol conversion, and then calls the UDP communication component to distribute the instruction response messages to each forwarding client.

[0062] The client forwards the message, parses the instruction response message, and obtains the real serial number. When the corresponding original instruction number is found, the instruction response message is converted to the standard protocol and then sent to the vehicle network platform by calling the TCP network communication component.

[0063] By using the above-mentioned system communication architecture, a business loop for instructions can be realized, thereby enabling instruction pass-through functionality.

[0064] On the other hand, corresponding to the above system embodiments, such as Figures 5 to 6 As shown, a second aspect of the present invention also provides a data exchange method across vehicle networking systems, the steps of which include:

[0065] like Figure 5 As shown, during the command transmission phase:

[0066] Step S100: The forwarding client receives the transparent transmission instruction message sent by the vehicle networking platform, performs forwarding protocol conversion, and then sends it to the forwarding server.

[0067] The specific execution steps of the forwarding client include:

[0068] Step S101: Receive the instruction message of the Ministry of Transport Standard Protocol sent by the downstream vehicle networking platform;

[0069] Step S102: Create a... Figure 3 The forwarding protocol packet object shown includes a start flag, header, body, and checksum;

[0070] Step S103: Set the parameters of the forwarding protocol header;

[0071] Step S104: As Figure 4 As shown, the instruction message received in step S101 is set as the forwarding protocol packet body;

[0072] Step S105: Verify the data, obtain the verification code, and set it as the verification code for the forwarding protocol;

[0073] Step S106: Encode and package the data according to the forwarding protocol;

[0074] Step S107: Use the UDP network component to send the data to the forwarding server.

[0075] Step S200: The forwarding server parses the transparent transmission command message, obtains the command parameters, sender identifier, and original command sequence number; generates a unique command identifier that maps to the original command sequence number and sender identifier, and stores it in the distributed cache server; and initiates a command request with the unique command identifier to the vehicle network gateway.

[0076] The specific execution steps of the forwarding server include:

[0077] Step S201: Receive and forward the instruction message forwarded by the client;

[0078] Step S202: Parse the packet header according to the forwarding protocol;

[0079] Step S203: Parse the forwarding protocol packet body according to the message type in the packet header;

[0080] Step S204: Parse the header of the Ministry Standard Protocol instruction message according to the Ministry Standard Protocol;

[0081] Step S205: Based on the message type in the header of the standard protocol packet, parse the body of the standard protocol packet to obtain the various instruction parameters;

[0082] Step S206: Synchronously generate a globally unique ID;

[0083] Step S207: Set various instruction parameters according to the parameter requirements of the upstream vehicle network gateway cluster API, and use the globally unique ID generated in step S206 as the unique identifier of the instruction;

[0084] Step S208: Serialize all instruction parameters into a JSON string;

[0085] Step S209: Call the upstream vehicle network gateway cluster API interface to send an instruction request with a unique instruction identifier to the upstream vehicle network gateway;

[0086] Step S210: Obtain the sender identifier from the forwarding protocol packet header obtained in step S202, obtain the instruction unique identifier (i.e., globally unique ID) from step S206, and use the instruction unique identifier as the KEY to store the sender identifier and the original instruction sequence number in the distributed cache server (Redis) to form a key-value relationship.

[0087] Step S300: The vehicle network gateway receives the instruction parameters, converts them into instruction data packets of the Ministry of Transport's standard protocol, generates a real serial number, and publishes the unique identifier of the instruction and the real serial number to the distributed message bus; and sends the instruction data packets to the vehicle terminal.

[0088] The specific execution steps of the vehicle-to-everything (V2X) gateway include:

[0089] Step S301: The vehicle network gateway receives the instruction parameters and creates the Ministry of Transport standard protocol data packet;

[0090] Step S302: The vehicle network gateway generates a real serial number, sets the real serial number in the header of the standard protocol packet, and sets various parameters of the packet header;

[0091] Step S303: Set the departmental standard package body according to the departmental standard protocol for the various instruction parameters obtained from step S301;

[0092] Step S304: Verify the data and encode it according to the departmental standard protocol;

[0093] Step S305: The vehicle network gateway calls the TCP network component to send instruction data packets of the Ministry of Industry and Information Technology (MIIT) standard protocol to the vehicle terminal;

[0094] Step S306: The unique instruction identifier obtained from the instruction parameters in step S301, and the actual serial number generated in step S302, are published together to the distributed message bus (e.g., Kafka, RabbitMQ, etc.).

[0095] Step S400: The forwarding server obtains the instruction unique identifier and real serial number from the distributed message bus. After finding the corresponding original instruction sequence number and sender identifier in the distributed cache server based on the instruction unique identifier, it finds the corresponding forwarding client based on the sender identifier and sends the first data packet containing the original instruction sequence number and real serial number.

[0096] The specific execution steps of the forwarding server include:

[0097] Step S401: After obtaining the instruction unique identifier and real serial number from the distributed message bus, the forwarding server finds the corresponding sender identifier and original instruction sequence number from the distributed cache server based on the instruction unique identifier.

[0098] Step S402: The forwarding server finds the corresponding forwarding client based on the sender identifier;

[0099] Step S403: The forwarding server packages the original instruction sequence number and the real serial number obtained in step S401 into a forwarding protocol packet body.

[0100] Step S404: The forwarding server calls the UDP communication component to send the first data packet containing the original instruction sequence number and the real serial number to the forwarding client.

[0101] Step S500: The forwarding client receives the first data packet, parses it, stores it, and establishes a mapping relationship between the real serial number and the original instruction sequence number.

[0102] The specific execution steps of the forwarding client include:

[0103] Step S501: The forwarding client receives the forwarded data and parses the data packets according to the forwarding protocol;

[0104] Step S502: The forwarding client uses the real serial number as the KEY and the original instruction sequence number as the VALUE to cache the data in memory using key-value pairs.

[0105] To achieve a closed-loop business process for instructions, the data exchange method across the vehicle-to-everything (V2X) system includes, for example... Figure 6 As shown, it also includes a command response phase, the steps of which include:

[0106] Step S600: The vehicle network gateway receives the instruction response message containing the real serial number reported by the vehicle terminal and publishes it to the distributed message bus.

[0107] Step S700: The forwarding server obtains the instruction response message from the distributed message bus, performs forwarding protocol conversion, and then distributes the instruction response message to each forwarding client.

[0108] The specific execution steps of the forwarding server include:

[0109] Step S701: Obtain instruction response message from the distributed message bus;

[0110] Step S702: Create a forwarding protocol packet object;

[0111] Step S703: Set the forwarding protocol header parameters;

[0112] Step S704: Set the instruction response message obtained in step S701 as the forwarding protocol packet body;

[0113] Step S705: Pack the data according to the forwarding protocol;

[0114] Step S706: Invoke the UDP communication component to distribute the instruction response message to each forwarding client.

[0115] Step S800: Forward the client parsing instruction response message to obtain the real serial number. When the corresponding original instruction sequence number is found, the instruction response message is converted to the Ministry of Transport's standard protocol and then sent to the corresponding vehicle network platform.

[0116] The specific execution steps of the forwarding client include:

[0117] Step S801: Receive the instruction response message sent by the forwarding server;

[0118] Step S802: Parse the packet header according to the forwarding protocol;

[0119] Step S803: Parse and forward the protocol packet body according to the packet header message type;

[0120] Step S804: Parse the forwarding protocol packet body obtained in step S803 according to the Ministry Standard Protocol header and packet body to obtain the Ministry Standard Protocol header and Ministry Standard packet body;

[0121] Step S805: Read the actual serial number from the header of the standard protocol packet;

[0122] Step S806: Use the real serial number as the KEY to retrieve the original instruction sequence number from the key-value pair in the cache;

[0123] Step S807: Create a Ministry Standard Protocol Packet object;

[0124] Step S808: Set the parameters of the Ministry Standard Protocol packet header according to the Ministry Standard packet header generated in step S804, and set the serial number to the original instruction sequence number;

[0125] Step S809: Set the packet body obtained in step S804 as the packet body of the Ministry Standard Protocol packet;

[0126] Step S810: Verify the data, obtain the verification code, and set the verification code to the verification code of the Ministry Standard Protocol packet;

[0127] Step S811: Encode and package the data according to the departmental standard protocol;

[0128] Step S812: Call the TCP network communication component to send data packets to the downstream vehicle networking platform.

[0129] In summary, the data exchange system and method for cross-vehicle networking systems provided by this invention solves the problem of inconsistency between the original instruction sequence number and the actual serial number through the design of a communication scheme for converting instruction sequence numbers. It realizes a closed-loop business function and instruction pass-through function for monitoring the same batch of vehicles and sending instructions on a multi-platform, multi-level vehicle monitoring platform.

[0130] The preferred embodiments of the present invention disclosed above are merely illustrative of the invention. These preferred embodiments do not exhaustively describe all details, nor do they limit the invention to the specific implementations described. Clearly, many modifications and variations can be made based on the content of this specification. This specification selects and specifically describes these embodiments to better explain the principles and practical applications of the invention, thereby enabling those skilled in the art to better understand and utilize the invention. The present invention is limited only by the claims and their full scope and equivalents. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the invention should be included within the protection scope of the invention.

[0131] Those skilled in the art will understand that, besides implementing the system, apparatus, and their modules provided by this invention in purely computer-readable program code, the same program can be implemented in the form of logic gates, switches, application-specific integrated circuits, programmable logic controllers, and embedded microcontrollers by logically programming the method steps. Therefore, the system, apparatus, and their modules provided by this invention can be considered a hardware component, and the modules included therein for implementing various programs can also be considered structures within the hardware component; alternatively, modules for implementing various functions can be considered both software programs implementing the method and structures within the hardware component.

[0132] Furthermore, all or part of the steps in the methods of the above embodiments can be implemented by a program instructing related hardware. This program is stored in a storage medium and includes several instructions to cause a microcontroller, chip, or processor to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as a USB flash drive, a portable hard drive, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0133] Furthermore, various different implementations of the present invention can be combined arbitrarily, as long as they do not violate the spirit of the present invention, they should also be regarded as the content disclosed in the present invention.

Claims

1. A data exchange system for cross-vehicle networking systems, characterized in that... include: The vehicle-to-everything (V2X) platform sends command messages to the forwarding client and receives command response messages. The forwarding client receives the transparent transmission instruction message, performs forwarding protocol conversion, and then sends it to the forwarding server. The forwarding server parses the transparent transmission command message, obtains the command parameters, sender identifier, and original command sequence number; generates a unique command identifier that maps to the original command sequence number and sender identifier, and stores it in the distributed cache server. Send a command request with a unique identifier to the vehicle network gateway; The vehicle-to-everything (V2X) gateway receives command parameters, converts them into command data packets of the Ministry of Industry and Information Technology (MIIT) standard protocol, generates a real serial number, and then publishes the unique identifier of the command and the real serial number to the distributed message bus. Send instruction data packets to the vehicle-mounted terminal; The forwarding server obtains the unique instruction identifier and real serial number from the distributed message bus. After finding the corresponding original instruction sequence number and sender identifier in the distributed cache server based on the unique instruction identifier, it finds the corresponding forwarding client based on the sender identifier and sends the first data packet containing the original instruction sequence number and real serial number. The forwarding client receives the first data packet, parses it, stores it, and establishes a mapping relationship between the real serial number and the original instruction sequence number; The vehicle-to-everything (V2X) gateway receives instruction response messages containing real serial numbers reported by the vehicle terminals and publishes them to the distributed message bus. The forwarding server obtains instruction response messages from the distributed message bus, performs forwarding protocol conversion, and then distributes the instruction response messages to each forwarding client. The client forwards the message, parses the instruction response message, and obtains the real serial number. When the corresponding original instruction number is found, the instruction response message is converted to the Ministry of Transport's standard protocol and then sent to the corresponding vehicle network platform.

2. The data exchange system for cross-vehicle networking systems according to claim 1, characterized in that, The forwarding server serializes the instruction parameters into a JSON string and sends an instruction request with a unique instruction identifier to the vehicle network gateway by calling the vehicle network gateway cluster API interface.

3. The data exchange system for cross-vehicle networking systems according to claim 1, characterized in that, The vehicle network gateway invokes the TCP network component to send instruction data packets to the vehicle terminal / to send instruction response messages to the vehicle network platform.

4. The data exchange system for cross-vehicle networking systems according to claim 1, characterized in that, The forwarding server invokes the UDP communication component to send a first data packet containing the original instruction sequence number and the real serial number to the forwarding client, and distributes the instruction response message to each forwarding client.

5. The data exchange system for cross-vehicle networking systems according to claim 1, characterized in that, The steps for the forwarding client to receive and perform forwarding protocol conversion on the transparent transmission command message include: creating a forwarding protocol packet object, including a start flag, packet header, packet body, and checksum; setting various parameters of the forwarding protocol packet header, including message length, message type, message sequence number, sender identifier, and packet information; setting the command message as the packet body of the forwarding protocol packet; verifying the data and obtaining the checksum to set as the checksum of the forwarding protocol; and finally encoding and packaging the data according to the forwarding protocol.

6. The data exchange system for cross-vehicle networking systems according to claim 1, characterized in that, The steps of the forwarding server in parsing the transparent transmission instruction message include: parsing the packet header according to the forwarding protocol, parsing the packet body according to the message type in the packet header, obtaining the transparent transmission instruction message of the Ministry Standard Protocol, parsing its Ministry Standard packet header according to the Ministry Standard Protocol, obtaining the message type in its packet header and parsing its packet body accordingly, and obtaining the instruction parameters accordingly.

7. A data exchange method across vehicle networking systems, characterized by the following steps include: During the command transmission phase: Step S100: The forwarding client receives the transparent transmission instruction message sent by the vehicle networking platform, performs forwarding protocol conversion, and then sends it to the forwarding server; Step S200: The forwarding server parses the transparent transmission command message, obtains the command parameters, sender identifier, and original command sequence number; generates a unique command identifier that maps to the original command sequence number and sender identifier, and stores it in the distributed cache server; and initiates a command request with the unique command identifier to the vehicle network gateway. In step S300, the vehicle networking gateway receives the instruction parameters, converts them into instruction data packets of the Ministry of Industry and Information Technology (MIIT) standard protocol, generates a real serial number, and then publishes the unique identifier of the instruction and the real serial number to the distributed message bus. Send instruction data packets to the vehicle-mounted terminal; In step S400, the forwarding server obtains the instruction unique identifier and real serial number from the distributed message bus. After finding the corresponding original instruction sequence number and sender identifier in the distributed cache server based on the instruction unique identifier, it finds the corresponding forwarding client based on the sender identifier and sends the first data packet containing the original instruction sequence number and real serial number. Step S500: The forwarding client receives the first data packet, parses it, stores it, and establishes a mapping relationship between the real serial number and the original instruction sequence number.

8. The data exchange method across vehicle networking systems according to claim 7, characterized in that, It also includes a command response phase, the steps of which include: In step S600, the vehicle-to-everything (V2X) gateway receives the instruction response message containing the real serial number reported by the vehicle terminal and publishes it to the distributed message bus. In step S700, the forwarding server obtains the instruction response message from the distributed message bus, performs forwarding protocol conversion, and then distributes the instruction response message to each forwarding client. Step S800 forwards the client to parse the instruction response message and obtain the real serial number. When the corresponding original instruction sequence number is found, the instruction response message is converted to the Ministry of Industry and Information Technology's standard protocol and then sent to the corresponding vehicle network platform.

9. The data exchange method across vehicle networking systems according to claim 7, characterized in that, In step S100, the forwarding client receives the transparent transmission instruction message and performs forwarding protocol conversion, including: creating a forwarding protocol packet object including: start flag, packet header, packet body, and checksum; setting various parameters of the forwarding protocol packet header including: message length, message type, message sequence number, sender identifier, and packet information; setting the instruction message as the packet body of the forwarding protocol packet; verifying the data and obtaining the checksum to set as the checksum of the forwarding protocol; and finally encoding and packaging the data according to the forwarding protocol.

10. The data exchange method across vehicle networking systems according to claim 7, characterized in that, In step S200, the step of the forwarding server parsing the transparent transmission instruction message includes: parsing the packet header according to the forwarding protocol, parsing the packet body according to the message type in the packet header, obtaining the transparent transmission instruction message of the Ministry Standard Protocol, parsing its Ministry Standard packet header according to the Ministry Standard Protocol, obtaining the message type in its packet header and parsing its packet body accordingly, and obtaining the instruction parameters accordingly.

Images