Intelligent traffic Internet of Vehicles V2X communication method based on metadata driving

Abstract

The invention discloses an intelligent traffic Internet of Vehicles V2X communication method based on metadata driving, and the method comprises the steps: encrypting and decrypting real-time shared data, updating a secret image file, and transmitting the secret image file. The encryption and decryption of the real-time shared data, the updating of the secret mapping file and the transmission of the secret mapping file are all processed by a protection module MDPM (Metadata Drive Procedure Module) based on metadata driving, which is provided by the invention, and the encryption and decryption of the real-time shared data, the updating of the secret mapping file and the transmission of the secret mapping file are all carried out; according to the V2X communication method for the smart traffic Internet of Vehicles, the problems of data leakage, data counterfeiting, timeliness and accuracy of data transmission and the like can be effectively solved; according to the invention, safe, fast, fine-grained and low-latency data communication services can be provided.

Description

Technical Field

[0001] This invention relates to the field of intelligent transportation, specifically a metadata-driven intelligent transportation vehicle-to-everything (V2X) communication method. Background Technology

[0002] In the field of intelligent transportation, the Internet of Vehicles (IoV) is a unique wireless self-organizing network. Its goal is to facilitate information exchange and collaboration through communication between vehicles and intelligent infrastructure, and between vehicles themselves, ensuring the reliability of IoV communication. Existing IoV security methods are mainly divided into overall defense strategies and specific defense technologies targeting specific vulnerabilities. However, with the increase in data transmission and communication, potential security issues are gradually emerging, including privacy leaks, data forgery, and malicious attacks. Some IoV security solutions employ blockchain technology, but the complexity, computational and storage overhead of blockchain can lead to performance degradation and increased latency. Traditional big data analytics can be used for risk prediction, but this may be limited by the timeliness and accuracy of the data, especially in the rapidly changing IoV environment. Furthermore, some IoV authentication protocols may require fully trusted third parties, while traditional data management methods allow network service providers, high-privilege administrators, or curious third parties to snoop on or even modify this sensitive data, potentially introducing single points of failure and security dependencies. IoV technology and standards (both existing and anticipated future developments) are still in their early stages, and the development of standards based on device attributes and permissions still faces many challenges. Summary of the Invention

[0003] To address the aforementioned issues, this application proposes a metadata-driven intelligent transportation vehicle-to-everything (V2X) communication method.

[0004] To achieve the above objectives, the technical solution of the present invention is as follows:

[0005] 1. A metadata-driven intelligent transportation vehicle-to-everything (V2X) communication method, characterized in that the intelligent transportation vehicle-to-everything (V2X) communication method includes the following steps:

[0006] A metadata-driven intelligent transportation vehicle-to-everything (V2X) communication method, the communication method comprising the following steps:

[0007] (1) Set access permissions for communication data. This process is completed in the MetadataDriven Protection Module (MDPM).

[0008] (2) Data encryption methods are divided according to data size. This process is completed in MDPM.

[0009] (3) Different encryption algorithms are used to encrypt data of different sizes. This process is completed in MDPM.

[0010] (4) Generate metadata based on the information in the data and encrypt it. This process is completed in MDPM.

[0011] (5) Store the metadata in a Cryptographic Mapping Index (CMI) file.

[0012] (6) Update CMI in MDPM. This process is completed in MDPM.

[0013] (7) The CMI file is sent to the requesting vehicle, intelligent infrastructure (roadside unit) and regional vehicle network service center (RVNS). The requesting vehicle obtains and decrypts the data according to the CMI file and accessibility attributes. The RVNS integrates the data being uploaded and the data already uploaded according to the CMI file.

[0014] Prior to this, in the metadata-driven intelligent transportation vehicle-to-everything (V2X) communication method, it is first necessary to set attributes, access permissions, and storage methods for encrypted data. Specifically, MDPM specifies the access attributes of the data according to the data owner's needs; MDPM divides the encryption and storage methods of the data according to the data type and scale.

[0015] Preferred, the data encryption process specifically involves: inputting the data to be encrypted into MDPM for encryption processing; specifically, MDPM uses the Advanced Encryption Standard (AES) encryption algorithm for large-scale data and generates an access key.

[0016] For small-scale data (physical firmware control commands, roadside unit signal commands, basic vehicle information, environmental sensor data, etc.), due to their small size, encryption, and fast storage speed, they are defined as metadata in this invention. The encryption method is the same as the metadata encryption method. Metadata is generated based on the key, data name, attributes, access permissions, data owner, modification time, and other information generated after data encryption. This process is completed in MDPM.

[0017] Preferred, the encrypted data storage method is as follows: after data encryption, the data is stored as follows: the encrypted large-scale data is uploaded to RVNS storage; the metadata is encrypted in the local MDPM, and the encrypted data name, attribute access permissions, and access address are stored in the CMI ciphertext block. The storage area of ​​the ciphertext block in the local CMI and the encrypted attributes are recorded in the header index element.

[0018] Preferred, the update of the CMI file in MDPM specifically involves the following steps: MDPM updates the CMI file according to the attributes and access permissions of the encrypted data: MDPM determines whether a data index element exists in the CMI based on the attributes and access permissions. If it exists, new information is added to the corresponding ciphertext block. If it does not exist, the data index element is updated, and a new ciphertext block is created to store the information.

[0019] Prior to this, the transmission of the CMI file between the vehicle, the intelligent infrastructure (roadside unit), and the RVNS specifically involves the RVNS integrating encrypted metadata blocks based on the attributes in the CMI to facilitate rapid extraction by the vehicle and the intelligent infrastructure (roadside unit). The RVNS then requests the MDPM in the vehicle and the intelligent infrastructure (roadside unit) to determine the location of the encrypted metadata block in the CMI data index element based on its held attributes and extract it. If the encrypted block contains access addresses for large-scale data and corresponding AES keys, data download can continue through these access addresses and AES keys. Communication between intelligent vehicles and between intelligent vehicles and roadside units employs an inadvertent transmission protocol; the RVNS can perform wireless broadcasting (the specific broadcasting protocol is not claimed), enabling intelligent vehicles and roadside units in need to communicate point-to-point with the RVNS to obtain the CMI.

[0020] The beneficial effects of this invention are as follows:

[0021] This invention effectively solves problems such as data leakage, data forgery, and the timeliness and accuracy of data transmission. By using MDPM to encrypt data, it prevents RVNS and unauthorized third parties from inferring data content based on data names, thus improving transmission efficiency. The use of CMI files further enhances transmission efficiency. This invention effectively addresses issues such as data leakage, data forgery, and the timeliness and accuracy of data transmission; it provides secure, fast, fine-grained, and low-latency data communication services. Attached Figure Description

[0022] Figure 1 This is a flowchart illustrating the MDPM process in an intelligent transportation system as described in this invention.

[0023] Figure 2 This is a format design diagram of the CMI described in this invention;

[0024] Figure 3 A flowchart for CMI update processing;

[0025] Figure 4 This is a flowchart of the CMI transfer process. Detailed Implementation

[0026] To make the objectives, technical solutions, and advantages of the present invention clearer, the embodiments of the present invention will be described in further detail below with reference to the accompanying drawings.

[0027] This application is based on the proposed MDPM and features a carefully designed CMI for encrypted files, which efficiently and securely manages related metadata. Figure 1 This application demonstrates the process framework of MDPM in intelligent transportation systems.

[0028] In this invention, the CMI is generated and maintained by MDPM, and its content includes index data elements and attribute-based metadata ciphertext blocks. The attribute-based ciphertext blocks are divided into real-time data ciphertext blocks based on the environment awareness layer and sensitive control instruction blocks based on the control execution layer. Figure 2 The CMI uses different colors to distinguish index data elements, metadata ciphertext blocks, and instruction blocks. Each metadata ciphertext block corresponds to an access attribute. The Location field in the header index data element is implemented using special programming; its content indicates the storage location of the metadata ciphertext block within the CMI. The MDPM can locate the corresponding storage location of the ciphertext block based on the Location and perform decryption. This process is completed locally within the CMI, without requiring additional communication with the MDPM in servers or other intelligent units, making the process fast and efficient. The processing follows these steps: First, the MDPM locates the metadata ciphertext block matching its own access attribute based on the index data elements in the CMI, accurately extracts the ciphertext from the corresponding block, and then performs decryption. When a ciphertext block contains a sub-CMI link, the MDPM will locate the CMI corresponding to the sub-ciphertext block and perform iterative processing. During communication, to prevent devices or other smart infrastructure from accessing encrypted data beyond their authorized limits, we set access permission thresholds based on AND and OR in CPABE, allowing higher-privilege users to access lower-privilege data, but preventing lower-privilege users from accessing higher-privilege data. For example, special permissions can be set for MDPMs of police cars, ambulances, military vehicles, etc., or special permissions can be obtained based on RVNS.

[0029] Metadata in CMI includes real-time data (such as traffic information, current status of intelligent vehicles and facilities), access attributes, and data access addresses on the regional network server, data encryption keys, data names, attributes, access permissions, data owners, modification times, etc. To ensure data security and prevent the Regional Network Service Center (RVNS) and unauthorized third parties from inferring data content through data names, we replace data names with random bytes before uploading them to RVNS or when sharing them with MDPMs on other devices. Figure 3 The detailed format of CMI is shown.

[0030] In this embodiment, the MDPM updates the CMI file according to the permission attributes as follows. CMIs can be divided into local CMIs and CMIs on the RVNS. Local CMIs are used for information exchange between the local MDPM and the MDPMs of other units, such as decision-making and planning in autonomous driving. RVNS CMIs can be used for large-scale, real-time data sharing. The MDPM processes CMI data updates as follows: 1) If the access attribute of the updated data already exists in the index data element (PlaintextBlock) of the current CMI, a new information line is added to the data location of the corresponding ciphertext block, including the original data name, a randomly generated data name (access address stored on the local MDPM), the data's access attribute, time information, etc. 2) If the access attribute is not found in the current CMI, the MDPM needs to update the data index element in the CMI and create a new block for the attribute. When an attribute block contains sub-CMI links, iterative processing can be performed based on the access attribute. Figure 3 The CMI update process is demonstrated.

[0031] In this embodiment, the process of sharing real-time data between intelligent vehicles (intelligent facilities) via an wireless network after access permissions are set for the access address is as follows. During data transmission, data transmission between devices such as V2V, V2I, V2O, IVI, and IVO (collectively referred to as V2X) is based on the CMI proposed in this paper. Since CMI only manages metadata, it is small in size and has a fast transmission speed, making it suitable for vehicle networks with high real-time requirements. Index data elements are stored in plaintext. To enhance security, in CMI-based communication, MDPM uses an Oblivious Transfer (OT) protocol, such as... Figure 4 As shown. During OT protocol data transmission, the sender does not know the exact data received by the receiver, and the receiver can only obtain the corresponding data based on attributes.

[0032] MDPM is an attribute-based secure communication model that combines security, speed, fine-grained processing, and low-latency data communication. The MDPM described in this application is a meticulously designed secure communication model. Compared to traditional data management methods, MDPM eliminates the need for a database, reducing the privileges of network service providers and database administrators and enhancing security. Furthermore, the CMI in MDPM is designed as a sophisticated metadata management index, storing only data addresses, not the data itself. The CMI contains different blocks, and the metadata within these blocks can only be accessed by authorized entities. This reduces computational and data volume while preventing curious or malicious third-party snooping and mitigating security risks associated with high privileges held by service providers (and database administrators, etc.). Moreover, the design of the CMI in MDPM aligns with distributed data management methods, enabling its widespread application and deployment. MDPM can be flexibly adjusted according to different security scenarios, thus possessing strong scalability.

[0033] All functionalities of the MDPM proposed in this application have been implemented. The experimental platform for the MDPM is based on a Raspberry Pi 4 Model B (CPU: 4 Cores ARM Cortex-A72, 1.5GHz, 1.2GHz, Memory: 4GB), and the operating system is Ubuntu Server for Raspberry Pi (22.04.3LTS). The regional center server's processor is an AMD Ryzen 7 5800H (3.2GHz, Memory: 16GB). All programs, including the regional center server, the intelligent vehicle, and the intelligent infrastructure MDPM, were written in PHP and C. The CP-ABE toolkit was also used to implement the MDPM's security protection functions. In the experiments, the RVNS, the intelligent vehicle, and the intelligent infrastructure MDPM were all on the same wireless LAN, resulting in stable and low-latency communication. The experiments demonstrate that the proposed MDPM is fast and effective, suitable for intelligent transportation application scenarios.

[0034] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the embodiments of this application, and are not intended to limit them; although the embodiments of this application have been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the foregoing embodiments, or make equivalent substitutions for some or all of the technical features; and these modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of this application.

Claims

1. A metadata-driven intelligent transportation vehicle-to-everything (V2X) communication method, characterized in that, The intelligent transportation vehicle-to-everything (V2X) communication method includes the following steps: A metadata-driven intelligent transportation vehicle-to-everything (V2X) communication method, the communication method comprising the following steps: (1) Set access permissions for communication data. This process is completed in the MetadataDriven Protection Module (MDPM). (2) Data encryption methods are divided according to data size. This process is completed in MDPM. (3) Different encryption algorithms are used to encrypt data of different sizes. This process is completed in MDPM. (4) Generate metadata based on the information in the data and encrypt it. This process is completed in MDPM. (5) Store the metadata in a Cryptographic Mapping Index (CMI) file. (6) Update CMI in MDPM. This process is completed in MDPM. (7) The CMI file is sent to the requesting vehicle, intelligent infrastructure (roadside unit) and regional vehicle network service center (RVNS). The requesting vehicle obtains and decrypts the data according to the CMI file and accessibility attributes. The RVNS integrates the data being uploaded and the data already uploaded according to the CMI file.

2. The metadata-driven intelligent transportation vehicle-to-everything (V2X) communication method according to claim 1, characterized in that: Setting attributes, access permissions, and storage methods for data that needs to be encrypted includes the following steps: MDPM specifies the access attributes of the data according to the data owner's needs; MDPM categorizes the encryption and storage methods of the data based on its data type and size.

3. The metadata-driven intelligent transportation vehicle-to-everything (V2X) communication method according to claim 1, characterized in that: The process of encrypting data by passing it into MDPM involves the following steps: MDPM uses the Advanced Encryption Standard (AES) encryption algorithm for large-scale data and generates an access key.

4. The metadata-driven intelligent transportation vehicle-to-everything (V2X) communication method according to claim 1, characterized in that: The generation of metadata includes the following steps: For small-scale data (physical firmware control instructions, roadside unit signal instructions, basic vehicle information, environmental sensor data, etc.), due to their small size, encryption, and fast storage speed, they are defined as metadata in this invention; metadata is generated based on information such as the key, data name, attributes, access permissions, data owner, and modification time generated after data encryption. This process is completed in MDPM.

5. The metadata-driven intelligent transportation vehicle-to-everything (V2X) communication method according to claim 1, characterized in that: The data storage method that requires encryption includes the following steps: After the data is encrypted, the data is stored as follows: The encrypted large-scale data is uploaded to RVNS storage; the metadata is encrypted in the local MDPM, and the encrypted data name, attribute access permissions, and access address are stored in the CMI ciphertext block. The storage area of ​​the ciphertext block in the local CMI and the encrypted attributes are recorded in the header index element.

6. The metadata-driven intelligent transportation vehicle-to-everything (V2X) communication method according to claim 1, characterized in that: The steps of MDPM updating the CMI file based on the attributes and access permissions of encrypted data are as follows: MDPM determines whether a data index element exists in the CMI based on the attributes and access permissions. If it exists, new information is added to the corresponding ciphertext block. If it does not exist, the data index element is updated, and a new ciphertext block is created to store the information.

7. A metadata-driven intelligent transportation vehicle-to-everything (V2X) communication method according to claim 1, characterized in that: The transmission of CMI between vehicles, intelligent infrastructure (roadside units), and RVNS includes the following steps: RVNS integrates encrypted data blocks based on the attributes in the CMI to facilitate rapid retrieval by vehicles and intelligent infrastructure (roadside units). It then requests the MDPM in the vehicle or intelligent infrastructure (roadside unit) to determine the location of the ciphertext block in the CMI data index element based on its held attributes and retrieve it. If the ciphertext block contains access addresses for large-scale data and corresponding AES keys, data download can continue through those access addresses and AES keys. Communication between intelligent vehicles and between intelligent vehicles and roadside units uses an inadvertent transmission protocol; RVNS can perform wireless broadcasting (specific broadcast protocols are not claimed), enabling intelligent vehicles and roadside units in need to communicate point-to-point with RVNS to obtain the CMI.

Images