Vehicle-road cloud collaborative data exchange system

Abstract

The invention discloses a vehicle-road cloud collaborative data exchange system, which comprises a data acquisition and exchange unit, a traffic element identification analysis unit, an equipment intelligent operation management unit and an information security unit, and is characterized in that each unit is connected with a road side unit, a cloud control platform and a vehicle end through network communication, and data are interactively transmitted among the units; the data acquisition and exchange unit senses and monitors data changes of the road side unit, the cloud control platform and the vehicle side; the traffic element identification analysis unit identifies and analyzes each piece of traffic element information; the equipment intelligent operation management unit monitors and manages the operation state of each piece of equipment; the information security unit is based on a time sensitive network (TSN) and a software defined network (SDN) to ensure the security of data in the data exchange process during network communication of other units. The method has remarkable advantages in the aspects of improving the performance of the intelligent traffic system, guaranteeing the system safety, improving the resource utilization rate and the like.

Description

Technical Field

[0001] The present invention relates to the field of vehicle-road-cloud collaborative systems, and specifically to a vehicle-road-cloud collaborative data exchange system. Background Art

[0002] With the rapid development of intelligent transportation systems, vehicle-road-cloud collaboration technology, as its core component, is gradually becoming a key means to improve the safety and efficiency of transportation systems. Most of the existing vehicle-road-cloud collaboration data exchange models rely on traditional data communication protocols and methods. These solutions face many challenges in practical applications. Specifically, the existing technical solutions have the following main shortcomings: 1. Data delay and packet loss problems: In a complex and ever-changing traffic environment, the existing data exchange model often cannot guarantee the real-time and reliability of information, resulting in frequent data delays and packet loss, which affects the accuracy of system decisions.

[0003] 2. Poor compatibility and scalability: The data formats and communication protocols of different manufacturers and systems are different, which leads to compatibility issues in the data exchange process and makes it difficult to adapt to the needs of the rapid development of future intelligent transportation systems.

[0004] 3. Insufficient security: During the process of data transmission and exchange, it is vulnerable to the risk of network attacks and data tampering, threatening the safe and stable operation of the entire transportation system.

[0005] 4. Low resource utilization: Existing solutions often waste resources during data exchange, such as bandwidth resources and computing resources are not fully utilized, resulting in limited overall system performance. Summary of the invention

[0006] The present invention provides a vehicle-road-cloud collaborative data exchange system to solve the problems of data delay, compatibility, security and resource utilization in the prior art and improve the overall performance of the intelligent transportation system.

[0007] In order to achieve the above object, the technical solution adopted by the present invention is: A vehicle-road-cloud collaborative data exchange system includes a data acquisition and exchange unit, a traffic element identification and resolution unit, an equipment intelligent operation and management unit, and an information security unit. Each unit is connected to a roadside unit, a cloud control platform, and a vehicle end through network communication, and each unit transmits data to and from the other. The data acquisition and exchange unit senses and monitors data changes of the roadside unit, the cloud control platform, and the vehicle end, and collects data to be exchanged in real time. The traffic element identification and resolution unit identifies and resolves information of each traffic element, and by identifying and resolving traffic elements, realizes data classification, integration, and effective management. The equipment intelligent operation and management unit monitors and manages the operating status of each device, including on-board devices and devices that interact between the roadside and the vehicle. The information security unit is based on a time-sensitive network (TSN) and a software-defined network (SDN) to ensure the security of data during data exchange when other units communicate over the network.

[0008] Furthermore, the message format transmitted between the units supports two structured formats: JSON and XML.

[0009] Furthermore, the message message format transmitted between the units consists of a message header, message data, and a message tail. The sending unit and the receiving unit regard the message header as a data sequence, or regard the message header and the message data as a data sequence, calculate the length of the data sequence through the CRC algorithm, and detect whether an error or tampering occurs in the message message during transmission based on the length of the data sequence.

[0010] Compared with the prior art, the present invention has the following advantages: 1. High real-time and reliability: Based on the time synchronization and low latency characteristics of TSN technology, it ensures the real-time and reliability of data transmission and reduces data delay and packet loss.

[0011] 2. Strong compatibility and scalability: The use of a unified data format and communication protocol solves the compatibility issues between different manufacturers and systems, and has good scalability to adapt to the needs of future intelligent transportation system development.

[0012] 3. High security: A variety of security measures are used to ensure the security and integrity of data transmission, reducing the risk of network attacks and data tampering.

[0013] 4. High resource utilization: Through the flexible configuration and monitoring capabilities of SDN, the network resources can be optimized and efficiently utilized, reducing the overall operating costs of the system.

[0014] To sum up, the vehicle-road-cloud collaborative data exchange model of the present invention has significant advantages in improving the performance of intelligent transportation systems, ensuring system security, and improving resource utilization, and is expected to provide important support for the development of the intelligent transportation field. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] Figure 1 It is a schematic diagram of the system structure of an embodiment of the present invention.

[0016] Figure 2 It is a message format diagram in an embodiment of the present invention.

[0017] Figure 3 It is a flow chart of vehicle-road-cloud collaborative data exchange using the system of an embodiment of the present invention. DETAILED DESCRIPTION

[0018] The present invention is further described below in conjunction with the accompanying drawings and embodiments.

[0019] like Figure 1 As shown, this embodiment discloses a vehicle-road-cloud collaborative data exchange system, which is composed of the following four core units: data acquisition and exchange unit, traffic element identification and resolution unit, equipment intelligent operation and management unit, and information security unit. Each unit is closely connected to the roadside unit, cloud control platform and vehicle end through network communication, and each unit transmits data interactively to achieve efficient and accurate data exchange.

[0020] The data collection and exchange unit is responsible for sensing and monitoring data changes in the roadside unit, cloud control platform and vehicle end, and collecting data that needs to be exchanged in real time, ensuring the real-time and accuracy of the data, and providing a basis for subsequent data processing and analysis.

[0021] The traffic element identification and parsing unit is the core unit in the data exchange model, which is used to identify and parse the information of various traffic elements, including people (drivers, pedestrians, passengers and other traffic participants), vehicles (vehicles such as motor vehicles and non-motor vehicles), roads (roads, including highways, urban roads, entrance and exit roads and related facilities) and environment (static and dynamic traffic environment composed of off-road landscapes, management facilities, meteorological conditions and traffic phenomena). By identifying and parsing traffic elements, data classification, integration and effective management are achieved, providing strong support for subsequent data applications; The equipment intelligent operation management unit is responsible for monitoring and managing the operating status of each device, including on-board equipment (i.e., sensor equipment) and roadside equipment that interacts with the vehicle. It ensures the normal operation of the equipment, promptly detects and resolves equipment failures, and improves the stability and reliability of the system. The information security unit is used to ensure the security of data during data exchange. Based on the time-sensitive network TSN (Time-Sensitive Networking) and software-defined network SDN (Software-Defined Networking), the network communication of each unit prevents data loss and tampering. Through encryption, identity authentication and other technical means, the integrity and confidentiality of the data are ensured to maintain the information security of the system.

[0022] In this embodiment, the message format transmitted between the units of the vehicle-road-cloud collaborative data exchange model clearly defines the rules for sending and receiving message messages, and supports two structured formats, JSON and XML, to ensure that different units can accurately parse and process messages. Figure 2 As shown in the figure, the message format transmitted between each unit consists of a message header (‌Header), message data (‌Data), and a message tail (‌Tail). ‌ The message header contains the following contents: 1). Version: occupies 4 digits and is used to identify the version of the model; 2). Type: occupies 4 bits, indicating the message type, such as data message, control message, etc. 3).Header Length: occupies 8 bits, indicating the length of the message header, the unit can be bytes; 4) Service Type: occupies 8 bits and is used to indicate the service quality requirements of the message, such as throughput, delay, reliability, etc. 5). Total Length: 16 bits, indicating the length of the entire message, including the header and data. 6). Identification: 16 bits, used to identify the session or connection between the sender and the receiver; 7). Flags: occupies 8 bits and is used to control the fragmentation and reassembly of messages; 8). Fragment Offset: 13 bits, used to indicate the position of the current fragment in the original message when the message is fragmented; 9). Time to Live (TTL): occupies 8 bits, indicating the maximum number of hops a message can have in the network, used to prevent the message from looping infinitely in the network; 10). Protocol: occupies 8 bits, indicating the protocol type used by the upper layer of the message, such as TCP, UDP, etc. 11). Header Checksum: occupies 16 bits and is used to verify the integrity of the message header. The checksum formula is as follows: Header Checksum = NOT(Sum(Version, Type, Header_Length, Service_Type,Total_Length, Identification, Flags, Fragment Offset, TTL, Protocol)) + 1.

[0023] Among them, Sum represents the operation of adding up the values ​​of all fields, NOT represents the bitwise inversion of the accumulated sum, and + 1 represents adding 1 to the inverted result. ‌‌Since the number of bits of each field is different, before accumulation, ensure that the value of each field is extracted according to its number of bits, and convert it to the appropriate integer type for accumulation. ‌In addition, since the checksum is required to be 16 bits, if the result of the accumulated sum exceeds 16 bits, it needs to be truncated or modulo operated to ensure that the checksum is a 16-bit number.

[0024] In actual applications, after receiving the message, the receiver recalculates the checksum according to the same order and rules, and compares it with the checksum field in the message. If the two are equal, it is considered that there is no error in the message during transmission; if they are not equal, it is considered that the message may have an error or tampering, and corresponding error handling is required.

[0025] The message data contains the following contents: Data part: variable length, used to transmit data or control information between units.

[0026] The message tail contains the following: Tail Checksum: It occupies 16 bits and is used to verify the integrity of the entire message, including the header and data. It uses a common CRC (cyclic redundancy check) algorithm, as follows: The basic idea of ​​the CRC algorithm is to regard the data as a polynomial, and then divide it by a predefined polynomial (generator polynomial), and the remainder is the checksum. Assume that the CRC checksum of a piece of data D is to be calculated, and the generating polynomial is G, then the CRC checksum C can be calculated by the following formula: C = remainder(D * 2n / G) Among them, ‌n‌ is the order of the generating polynomial G (‌that is, the highest power plus one), ‌*‌ represents polynomial multiplication, ‌ / ‌ represents polynomial division, and ‌remainder‌ represents the remainder operation. ‌ In practical applications, the specific implementation of the CRC algorithm will vary depending on the generator polynomial. Common CRC algorithms include CRC-8, CRC-16, CRC-32, etc., which use 8-bit, 16-bit, and 32-bit generator polynomials respectively. For the checksum calculation of the above message format, the sender regards the message header or the entire message (including the header and data part) as a data sequence, and then calculates the data sequence checksum according to the selected CRC algorithm. After receiving the message, the receiver also calculates the checksum of the received data sequence according to the selected CRC algorithm, and compares it with the checksum field in the message to detect whether the data has been tampered with during transmission.

[0027] like Figure 3 As shown, the data exchange process of the vehicle-road-cloud collaborative data exchange model of this embodiment covers four key links: data collection, processing, distribution, and feedback optimization. The vehicle side and the roadside unit collect vehicle status and road infrastructure information in real time, and upload them to the cloud control platform for processing through the vehicle-road-cloud collaborative data exchange model of this embodiment. The cloud control platform aggregates, cleans, and analyzes the received data to generate real-time environmental information, predicted environmental information, and auxiliary decision-making information, which is then distributed to the vehicle side and roadside unit through the vehicle-road-cloud collaborative data exchange model of this embodiment to guide vehicle driving and road management. The vehicle side and the roadside unit perform operations based on the received information, and feed back the execution results to the cloud control platform through the vehicle-road-cloud collaborative data exchange model of this embodiment to achieve continuous optimization of the system. The preferred embodiments of the present invention are described in detail above in conjunction with the accompanying drawings. The embodiments described in the present invention are merely descriptions of the preferred embodiments of the present invention, and do not limit the concept and scope of the present invention. The various specific technical features described in the above specific embodiments can be combined in any suitable manner without contradiction, and such combinations should also be regarded as the contents disclosed in the present disclosure as long as they do not violate the concept of the present invention. In order to avoid unnecessary repetition, the present invention will not further describe various possible combinations.

[0028] The present invention is not limited to the specific details of the above-mentioned embodiments. Within the technical concept of the present invention and without departing from the design concept of the present invention, various modifications and improvements made to the technical solution of the present invention by technical personnel in this field should fall within the protection scope of the present invention. The technical contents for which protection is sought in the present invention have been fully recorded in the claims.

Claims

1. A vehicle-road-cloud collaborative data exchange system, characterized in that: It includes a data collection and exchange unit, a traffic element identification and resolution unit, an equipment intelligent operation and management unit, and an information security unit. Each unit is connected to the roadside unit, the cloud control platform and the vehicle end through network communication, and the units exchange data with each other. The data collection and exchange unit senses and monitors the data changes of the roadside unit, the cloud control platform and the vehicle end, and collects the data that needs to be exchanged in real time. The traffic element identification and resolution unit identifies and resolves the information of each traffic element, and realizes the classification, integration and effective management of data by identifying and resolving traffic elements. The equipment intelligent operation and management unit monitors and manages the operating status of each device, including on-board equipment and equipment that interacts between the roadside and the vehicle. The information security unit is based on the time-sensitive network TSN and the software-defined network SDN to ensure the security of data during data exchange during network communication between other units.

2. The vehicle-road-cloud collaborative data exchange system according to claim 1, characterized in that: The message format transmitted between units supports two structured formats: JSON and XML.

3. The vehicle-road-cloud collaborative data exchange system according to claim 1, characterized in that: The message format transmitted between the units consists of a message header, message data, and a message tail. The sending unit and the receiving unit regard the message header as a data sequence, or regard the message header and the message data as a data sequence, calculate the length of the data sequence through the CRC algorithm, and detect whether an error or tampering occurs in the message during transmission based on the length of the data sequence.

Images