Vehicle network communication method and device

Abstract

This application discloses a vehicle-to-vehicle communication method and device for improving vehicle-to-vehicle communication performance. On the terminal side, the vehicle-to-vehicle communication method provided by this application includes: obtaining roadside unit device group information for a road section where the vehicle is not traveling based on the vehicle's current location information; wherein the roadside unit device group information includes at least one piece of roadside unit device information, and the roadside unit device information includes: an identifier of the map area to which the roadside unit belongs, an identifier of the intersection to which the roadside unit belongs within the map area, a device media access control address of the roadside unit, and the content of the roadside unit's certificate; and utilizing at least one piece of roadside unit device information in the roadside unit device group information to transmit messages between the vehicle and the roadside unit while the vehicle is traveling.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to a vehicle network communication method and device. Background Art

[0002] Vehicle-to-everything (V2X) wireless communication, also known as the Internet of Vehicles (IoV), is a next-generation information and communication network that connects vehicles to everything. IoV communication enables comprehensive information exchange between vehicles (V2V), vehicles and roads (V2I), vehicles and pedestrians (V2P), and vehicles and networks (V2N). Summary of the Invention

[0003] The embodiments of the present application provide a vehicle network communication method and device to improve vehicle network communication performance.

[0004] On the terminal side (e.g., an onboard unit), an embodiment of the present application provides a vehicle network communication method including:

[0005] Based on the vehicle's current location information, obtaining roadside unit device group information for a road section where the vehicle is not traveling; wherein the roadside unit device group information includes at least one piece of roadside unit device information, the roadside unit device information including: an identifier of a map area to which the roadside unit belongs, an identifier of an intersection to which the roadside unit belongs within the map area, a device media access control address of the roadside unit, and content of a certificate of the roadside unit;

[0006] At least one piece of roadside unit equipment information in the roadside unit equipment group information is used to transmit messages between the vehicle and the roadside unit during driving.

[0007] This method enables vehicles to obtain RSU device group information for untraveled sections of road in advance and utilize at least one RSU device in this RSU device group information to transmit messages between the vehicle and the RSU while driving. This ensures that secure V2I communications are not affected during high-speed driving and enables certificate-free communication for non-map messages, reducing message length and avoiding delays caused by frequent certificate verification.

[0008] In some embodiments, based on the current position information of the vehicle, obtaining the roadside unit equipment group information of the road section where the vehicle is not traveling includes:

[0009] Based on the current location information of the vehicle, sending a request message for obtaining the roadside unit device group information to the network side node;

[0010] Receiving the roadside unit device group information sent by the network side node in response to the roadside unit device group information acquisition request message;

[0011] Among them, the network side node is the Internet of Vehicles cloud platform or the target roadside unit.

[0012] In some embodiments, when the network-side node is a target roadside unit, the roadside unit device group information acquisition request message is generated in the following manner:

[0013] Creating a symmetric key, and using the symmetric key to encrypt the request content of the roadside unit device group information acquisition request message to generate a content part;

[0014] Encrypting the symmetric key using the public key of the target roadside unit's certificate to generate a key portion;

[0015] The roadside unit device group information acquisition request message is constructed using the content part and the key part.

[0016] In some embodiments, the public key of the target roadside unit's certificate is obtained in the following manner:

[0017] Receive a map message sent by a target roadside unit, wherein the map message includes the certificate content and message signature value of the roadside unit, and the certificate content of the roadside unit includes the certificate public key of the roadside unit;

[0018] Verify the validity of the certificate content in the map message, and when the verification passes, cache the map information in the map message and the certificate content of the roadside unit.

[0019] In some embodiments, the method further comprises:

[0020] Receiving a message without certificate content broadcast by a roadside unit, wherein the message without certificate content is a roadside traffic information message, a roadside safety message, or a signal light phase and timing message;

[0021] Using the message access layer source media access control address of the uncertified content as a key value, searching for a matching media access control address in the locally cached roadside unit device group information;

[0022] If the match fails, the message without certificate content is determined to be abnormal and discarded;

[0023] If the match is successful, the certificate content corresponding to the key value is extracted from the roadside unit equipment group information, and the certificate content is used to perform signature verification on the message without certificate content. If the verification is unsuccessful, the message without certificate content is determined to be abnormal and discarded. If the verification is successful, the message without certificate content is processed.

[0024] In some embodiments, the method further comprises:

[0025] At least one of the following methods is used to delete the roadside unit device information in the roadside unit device group information:

[0026] When the vehicle leaves the current intersection, the roadside unit equipment information corresponding to the previous intersection is deleted;

[0027] When the vehicle starts path navigation planning, the roadside unit equipment information that needs to be deleted is determined based on the navigation path;

[0028] Delete the roadside unit equipment information that has been stored for longer than the preset time.

[0029] On the roadside unit side, an embodiment of the present application provides a vehicle network communication method, including:

[0030] Obtaining roadside unit device group information; wherein the roadside unit device group information includes at least one roadside unit device information, the roadside unit device information including: an identifier of a map area to which the roadside unit belongs, an identifier of an intersection to which the roadside unit belongs within the map area, a device media access control address of the roadside unit, and content of a certificate of the roadside unit;

[0031] Send the roadside unit equipment group information to the vehicle-mounted unit.

[0032] In some embodiments, obtaining the roadside unit device group information includes:

[0033] Send a registration request to the IoV cloud platform, which contains the latitude and longitude coordinates of the local roadside unit, the device MAC address, and the certificate content;

[0034] Receive the roadside unit device group information sent by the Internet of Vehicles cloud platform in response to the registration request.

[0035] In some embodiments, the sending the roadside unit device group information to the onboard unit includes:

[0036] Receive a roadside unit device group information acquisition request message sent by the vehicle-mounted unit;

[0037] The roadside unit device group information acquisition request message is verified, and when the verification passes, the roadside unit device group information is sent to the onboard unit.

[0038] In some embodiments, the method further comprises:

[0039] Send a broadcast message. When the broadcast message is a map message, the map message includes the certificate content and message signature value of the roadside unit, and the certificate content of the roadside unit includes the certificate public key of the roadside unit. When the broadcast message is a message without certificate content other than a map message, the message without certificate content includes a message signature value.

[0040] On the IoV cloud platform side, an IoV communication method provided by an embodiment of the present application includes:

[0041] Generate roadside unit device group information; wherein the roadside unit device group information includes at least one roadside unit device information, the roadside unit device information including: an identifier of a map area to which the roadside unit belongs, an identifier of an intersection to which the roadside unit belongs within the map area to which it belongs, a device media access control address of the roadside unit, and certificate content of the roadside unit;

[0042] Send the roadside unit equipment group information.

[0043] In some embodiments, generating roadside unit device group information includes:

[0044] For any registered roadside unit, the roadside unit device group information corresponding to the roadside unit is generated by using the association relationship between the roadside unit and its adjacent roadside units, as well as the adjacent roadside unit device information.

[0045] In some embodiments, the method further comprises:

[0046] Receive a registration request sent by a roadside unit, the registration request carrying the latitude and longitude coordinates, device MAC address, and certificate content of the roadside unit;

[0047] Verify the validity of the certificate content of the roadside unit. When the verification passes, determine the identifier of the map area to which the roadside unit belongs and the identifier of the intersection to which the roadside unit belongs within the map area based on the latitude and longitude coordinate values ​​of the roadside unit, and generate the equipment information of the roadside unit.

[0048] Another embodiment of the present application provides a vehicle network communication device, which includes a memory and a processor, wherein the memory is used to store program instructions, and the processor is used to call the program instructions stored in the memory and execute any of the above methods according to the obtained program.

[0049] Furthermore, according to an embodiment, a computer program product for a computer is provided, for example, comprising software code portions for executing the steps of the method defined above when the product is executed on the computer. The computer program product may include a computer-readable medium having the software code portions stored thereon. Furthermore, the computer program product may be directly loaded into the internal memory of the computer and / or transmitted via a network through at least one of an upload process, a download process, and a push process.

[0050] Another embodiment of the present application provides a computer-readable storage medium, wherein the computer-readable storage medium stores computer-executable instructions, and the computer-executable instructions are used to enable the computer to execute any of the above methods. BRIEF DESCRIPTION OF THE DRAWINGS

[0051] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the following is a brief introduction to the drawings required for use in the description of the embodiments. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0052] Figure 1 A schematic diagram of the structure of a communication system provided in an embodiment of the present application;

[0053] Figure 2 A schematic diagram of the deployment of roadside units provided in an embodiment of the present application;

[0054] Figure 3 A schematic diagram of a process for a roadside unit to register with a connected vehicle cloud platform according to an embodiment of the present application;

[0055] Figure 4 A schematic diagram of a flow chart of a message transmission method of a roadside unit provided in an embodiment of the present application;

[0056] Figure 5a A schematic diagram of a process for an on-board unit to obtain roadside unit device group information from a roadside unit provided in an embodiment of the present application;

[0057] Figure 5b A schematic diagram of a process for an on-board unit to obtain roadside unit device group information from an Internet of Vehicles cloud platform provided in an embodiment of the present application;

[0058] Figure 6 A schematic diagram of the communication process of a vehicle-mounted unit provided in an embodiment of the present application during vehicle driving;

[0059] Figure 7 A schematic diagram of a process flow for receiving and processing uncertified messages by an on-board unit provided in an embodiment of the present application;

[0060] Figure 8 A schematic diagram of a flow chart of a vehicle network communication method on the vehicle-mounted unit side provided in an embodiment of the present application;

[0061] Figure 9 A schematic diagram of a flow chart of a vehicle network communication method on a roadside unit side provided in an embodiment of the present application;

[0062] Figure 10 A flowchart of a vehicle networking communication method on a vehicle networking cloud platform side provided in an embodiment of the present application;

[0063] Figure 11 A schematic diagram of the structure of a vehicle networking communication device on the terminal side provided in an embodiment of the present application;

[0064] Figure 12 A schematic diagram of the structure of a vehicle networking communication device on the network side provided in an embodiment of the present application;

[0065] Figure 13 A schematic diagram of the structure of an Internet of Vehicles communication device on the vehicle-mounted unit side provided in an embodiment of the present application;

[0066] Figure 14 A schematic diagram of the structure of a vehicle networking communication device on the roadside unit side provided in an embodiment of the present application;

[0067] Figure 15 A schematic diagram of the structure of an IoV communication device on the IoV cloud platform side provided in an embodiment of the present application. DETAILED DESCRIPTION

[0068] The following will be combined with the drawings in the embodiments of this application to clearly and completely describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are only part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0069] The embodiments of the present application provide a vehicle network communication method and device to improve vehicle network communication performance.

[0070] Among them, the method and the device are based on the same application concept. Since the principles of solving problems by the method and the device are similar, the implementation of the device and the method can refer to each other, and the repeated parts will not be repeated.

[0071] The terms "first", "second", etc. (if any) in the specification and claims of the embodiments of the present application and the above-mentioned drawings are used to distinguish similar objects and are not necessarily used to describe a specific order or sequential order. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments described herein can be implemented in a sequence other than that illustrated or described herein. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device comprising a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0072] The following examples and embodiments are to be understood as illustrative examples only. Although this specification may refer to "one," "an," or "some" examples or embodiments at several places, this does not mean that each such reference relates to the same example or embodiment, nor does it mean that the feature applies only to a single example or embodiment. Individual features of different embodiments may also be combined to provide further embodiments. Furthermore, terms such as "comprises" and "comprising" should be understood as not limiting the described embodiments to consisting only of those features already mentioned; such examples and embodiments may also include features, structures, units, modules, etc. that are not specifically mentioned.

[0073] The following describes in detail the various embodiments of the present application in conjunction with the accompanying drawings. It should be noted that the order in which the embodiments of the present application are presented only represents the order of the embodiments, and does not represent the advantages or disadvantages of the technical solutions provided by the embodiments.

[0074] Roadside units (RSUs) are key devices in V2X scenarios, transmitting messages to vehicles via the PC5 air interface to enable various V2I applications. However, air interface-based communication carries risks such as counterfeit terminals and information tampering. Therefore, in V2I interaction scenarios, messages sent by RSUs are signed with a digital certificate and the certificate content is included. This allows the vehicle to verify the legitimacy of the RSU's certificate content and the message signature.

[0075] However, attaching the certificate content to each communication message will increase the data transmission volume and affect the transmission performance. Therefore, when the roadside unit message sending interval is greater than or equal to 450 milliseconds, the complete certificate content must be attached. During the 450 millisecond interval, only the summary value corresponding to the certificate needs to be attached, thereby reducing the message length.

[0076] However, the method of sending periodic additional certificate content may result in the failure to receive the corresponding roadside unit certificate content when the vehicle switches roadside units at high speed, resulting in failure to determine the validity of the message. In addition, there will be frequent certificate legitimacy checks during the switching process of multiple roadside units, which increases the message processing delay and affects the safety of V2I communication.

[0077] See also Figure 1 , an embodiment of the present application provides a vehicle network communication system, including:

[0078] The On Board Unit (OBU) on the vehicle terminal side is used to:

[0079] 1) Receive Roadside Info Message (RSI), Roadside Safety Message (RSM), Signal Phase and Timing Message (SPAT), and Map messages broadcast by the roadside unit to achieve V2I communication;

[0080] 2) Obtain the local area map information of the vehicle's location and the information of the adjacent roadside unit equipment group from the Internet of Vehicles cloud platform through the Uu air interface;

[0081] 3) Initiate a unicast request to the designated roadside unit through the PC5 air interface to obtain the roadside unit device group information.

[0082] Road Side Unit (RSU) is used to:

[0083] 1) Broadcast V2I communication messages through the PC5 air interface;

[0084] 2) Register with the Internet of Vehicles cloud platform and report the device MAC address, longitude and latitude coordinates, and certificate content;

[0085] 3) Receive the roadside unit equipment group information issued by the Internet of Vehicles cloud platform;

[0086] 4) Receive the roadside unit equipment group information acquisition request sent by the vehicle-mounted unit.

[0087] Internet of Vehicles cloud platform for:

[0088] 1) Responsible for the unified operation and maintenance management of roadside units, and issuing corresponding roadside equipment group information to registered roadside units;

[0089] 2) Receive local area map information and nearby roadside unit equipment group information acquisition request sent by the vehicle-mounted unit.

[0090] The system configuration is as follows:

[0091] 1) The roadside unit obtains the longitude and latitude coordinates of its own device through pre-configuration or based on the Global Navigation Satellite System (GNSS). When the device is started, it initiates registration with the Internet of Vehicles cloud platform and carries the MAC (Media Access Control) address and certificate content of its own device (such as the certificate public key, etc.). Based on the longitude and latitude coordinate values ​​of the roadside unit, the cloud platform binds the map area ID (Region ID) in the map information with the intersection ID (Node ID) within the region. The map area ID is globally unique, and the intersection ID within the region is the identification value of each intersection in the map area and is unique within the region. The map can be divided into various regions in advance. Within each region, the node ID is unique and is used to identify each intersection within the region. Based on the above information, the cloud platform can form the configuration information shown in Table 1 below for each roadside unit:

[0092] Serial number Record content 1 Device latitude and longitude coordinate information 2 Device MAC address 3 Certificate Contents 4 Map area ID 5 Intersection ID within the area

[0093] Table 1: A roadside unit device information generated in the cloud platform

[0094] 2) The cloud platform generates device group information corresponding to each roadside unit based on the preset level value corresponding to the roadside unit and the association relationship between the upstream and downstream roadside units on the road corresponding to the roadside unit. The upstream and downstream roadside units on the road corresponding to the roadside unit are the adjacent roadside units of the roadside unit (the specific method of determining the upstream and downstream roadside units corresponding to a roadside unit depends on the specific implementation and is not limited in this embodiment of the application).

[0095] Regarding the preset level values ​​corresponding to roadside units, smaller level values ​​indicate closer proximity to the roadside unit's device group members. For example, if the target roadside unit's level value is 1, its device group consists of the target roadside unit + its upstream and downstream roadside units. If the target roadside unit's level value is 2, its device group consists of the target roadside unit's device group structure when its level value is 1 + the device group structures of the target roadside unit's device group members when their level values ​​are each 1.

[0096] Regarding the association relationship between the upstream and downstream roadside units on the road corresponding to the roadside unit, for example, it can be determined based on the information shown in Table 1, such as the map area ID corresponding to the roadside unit, the intersection ID within the area, the longitude and latitude coordinates of the equipment, etc. For example, for any target roadside unit, the target roadside unit and its corresponding upstream and downstream roadside units on the road belong to the same map area (that is, the map area ID is the same), or they can also belong to different adjacent map areas. The locations of these roadside units can be adjacent, and the specific division can be determined according to actual needs, which is not limited in the embodiments of the present application. In other words, the association relationship between the upstream and downstream roadside units on the road corresponding to any roadside unit can be determined based on the configuration information corresponding to the roadside unit (such as the data shown in Table 1), or it can be pre-set, for example, based on Figure 2 Roadside unit deployment shown.

[0097] Specifically, for example, Figure 2 For RSU7 in the example, when the level value is 1, RSU4, RSU5, RSU9 and RSU10 are its device group members. When the level value is 2, RSU1, RSU2, RSU3, RSU4, RSU5, RSU6, RSU8, RSU9, RSU10, RSU11, RSU12 and RSU13 are its device group members. The cloud platform sends the device group information corresponding to each registered roadside unit. For example, the device group information corresponding to any registered roadside unit is shown in Table 2 below:

[0098] Map area ID Intersection ID within the area Device MAC address Certificate public key 1 4 AA:BB:CC:DD:EE:F1 Binary data 1 5 AA:BB:CC:DD:EE:F2 Binary data 1 7 AA:BB:CC:DD:EE:F3 Binary data 1 9 AA:BB:CC:DD:EE:F4 Binary data 1 10 AA:BB:CC:DD:EE:F5 Binary data

[0099] Table 2: Equipment group information corresponding to registered roadside units

[0100] As can be seen from Table 2, for any registered RSU, the corresponding RSUs have the same map area ID, meaning they belong to the same map area. However, the corresponding intersection IDs within the area are different, meaning they are located at different intersections. The device MAC addresses in Table 2 represent the MAC addresses of the RSUs. Different RSUs have different certificate public keys. The specific binary data is not shown in Table 2.

[0101] The following is an example of the vehicle network communication process provided by the embodiment of the present application with reference to the accompanying drawings.

[0102] For the process of roadside unit registration on the Internet of Vehicles cloud platform, see Figure 3 As shown, for example, including:

[0103] Step 1: The roadside unit obtains the longitude and latitude coordinates of its own equipment through pre-configuration or based on GNSS;

[0104] Step 2: The roadside unit initiates registration with the cloud platform and carries the latitude and longitude coordinates, device MAC address, and certificate content;

[0105] Step 3: The cloud platform verifies the validity of the certificate content of the roadside unit;

[0106] Step 4: If the RSU's certificate is valid, the cloud platform binds the map region ID (Region ID) and the node ID (Node ID) of the location (i.e., the location corresponding to the longitude and latitude coordinates) reported by the RSU to the RSU's reported latitude and longitude, generating the data for the RSU as shown in Table 1. In other words, the RSU device information is generated for any registered RSU.

[0107] Step 5: The cloud platform generates roadside unit device group information corresponding to the roadside unit by using the association relationship between the roadside unit and its adjacent roadside units.

[0108] For example, in some embodiments, the cloud platform generates device group information corresponding to each registered roadside unit based on the preset level value corresponding to the roadside unit and the association relationship between the roadside unit and the upstream and downstream roadside units on the road, as shown in Table 2.

[0109] Step 6: The cloud platform sends the roadside unit device group information generated for the roadside unit to the roadside unit.

[0110] In some embodiments, if the certificate content of any roadside unit is updated, the roadside unit re-initiates registration with the cloud platform, and the cloud platform regenerates the device group information corresponding to the roadside unit and sends it to the roadside unit.

[0111] For the message transmission (including sending and receiving) process of the roadside unit, see Figure 4 , for example:

[0112] Step 1: The roadside unit broadcasts RSI, RSM, SPAT and / or Map messages via the PC5 air interface;

[0113] In some embodiments, the roadside unit can broadcast Map messages according to a preset period, with a sending interval greater than 450 milliseconds, and attach the certificate content and message signature value of the roadside unit. The remaining messages attach the message signature value but not the certificate content.

[0114] In some embodiments, regarding message signature values, the key type in the V2X secure interaction certificate is an asymmetric key (private key + public key). The private key content is cached in the security chip of each roadside unit, and the certificate public key is notified to other devices through the certificate content. When the roadside unit sends a message, it uses the private key of its own security chip to sign the message to be broadcast, generating a message signature value. When other devices receive the message, they use the cached certificate public key of the corresponding device or the public key contained in the certificate content to verify the signature value and determine whether the message is legitimate and can be received and processed.

[0115] Step 2: The roadside unit receives in real time a roadside unit device group information acquisition request message sent by the vehicle's onboard unit;

[0116] Step 3: The RSU determines whether the access layer destination MAC address in the request message is the MAC address of the RSU itself;

[0117] Step 4: If the access layer destination MAC address in the request message is the MAC address of the roadside unit itself, the roadside unit decrypts the key part in the request message using its own certificate private key to obtain a temporary symmetric key;

[0118] Step 5: The roadside unit uses the symmetric key to decrypt the content of the request message to obtain the original request content;

[0119] Step 6: The roadside unit processes the original request content obtained from the request message, and sends the device group information stored in itself (such as shown in Table 2) to the vehicle-mounted unit that initiated the request message.

[0120] Regarding the message transmission (including sending and receiving) process of the vehicle-mounted unit:

[0121] In some embodiments, the roadside unit device group information in the on-board unit may be the roadside unit device group information corresponding to the current location of the vehicle, that is, the vehicle may request to obtain and save the roadside unit device group information based on the current location.

[0122] In some embodiments, the vehicle-mounted unit can send a request message to request the roadside unit device group information and receive the roadside unit device group information fed back in response to the request message; it can also receive the roadside unit device group information actively pushed by the roadside unit or the cloud platform. Figure 5a , the OMU can obtain the RSU device group information from the RSU; see Figure 5b The vehicle-mounted unit can also obtain roadside unit device group information from the cloud platform. The following examples illustrate this.

[0123] See also Figure 5a The process of the onboard unit obtaining the roadside unit device group information from the roadside unit, for example, includes:

[0124] Step 1: The OMU receives the Map message broadcast by the RSU via the PC5 air interface.

[0125] Step 2: The on-board unit determines whether there is map information of the area where the vehicle is currently located. If so, it further determines whether there is roadside unit equipment information of the adjacent intersection at the current location; wherein, the vehicle is the vehicle to which the on-board unit belongs (the same applies below and will not be repeated).

[0126] Among them, regarding determining whether the vehicle has roadside unit equipment information at an adjacent intersection at its current location, for example, the vehicle obtains map information from the roadside unit or cloud platform, and each intersection in the map information is identified by RegionID (map region identifier) ​​and NodeID (intersection identifier within the region). The vehicle obtains the corresponding roadside unit equipment group information from the roadside unit (as shown in Table 2), and can match whether the current vehicle has the corresponding roadside unit equipment information by looking up Table 2 based on RegionID+NodeID.

[0127] For example: See Figure 2 , the vehicle stops at the RSU7 intersection. The roadside unit device group information obtained from RSU7 includes the device information of RSU4, RSU5, RSU9 and RSU10. When the vehicle travels from RSU7 to the intersection where RSU5 is located, the vehicle determines that it is about to enter the NodeID5 intersection based on its own real-time position and the obtained map information. The roadside unit device information corresponding to this intersection is the RSU5 device information. Starting from the NodeID5 intersection, there are four intersections (NodeID2, NodeID3, NodeID7, NodeID8) that can be driven to. These four intersections are the downstream intersections of the NodeID5 intersection, and the intersection where the vehicle is located is the adjacent intersection. Because the vehicle's driving direction is not fixed, it would be untimely to first determine which downstream intersection the vehicle is heading to based on the vehicle's heading angle or turn signal, and then check whether there is any roadside unit equipment information. Therefore, in some embodiments, when the vehicle enters the current intersection, it is immediately determined whether the NodeID value of the downstream intersection has corresponding roadside unit equipment information, and whether it is necessary to obtain roadside unit equipment information from the adjacent roadside unit;

[0128] For example, after the vehicle enters the current intersection NodeID5 and finds that there is no roadside unit equipment information corresponding to NodeID2, NodeID3, and NodeID8, it initiates a roadside unit equipment group information acquisition request to the roadside unit RSU5 corresponding to NodeID5 to obtain the equipment information of RSU2, RSU3, and RSU8 in advance.

[0129] Step 3: When the vehicle does not have map information for the current area, or does not have roadside unit equipment information for the adjacent intersection, the on-board unit verifies the validity of the certificate content attached to the Map message based on its own CA certificate chain;

[0130] Among them, regarding the CA certificate chain, the Public Key Infrastructure (PKI) issues application certificates for roadside units and pseudonym certificates for on-board units, and provides the PKI system's own certificate chain (including RCA, ICA, ACA, PCA), namely the CA certificate chain. The role of the CA certificate chain is to be used between different devices (vehicles and vehicles, vehicles and roads) to verify the validity of the certificate content of other devices based on the obtained CA certificate chain.

[0131] In some embodiments, the vehicle obtains the current position information in real time during driving, and determines whether there is roadside unit equipment information of the downstream intersection of the adjacent intersection based on the current position information. If not, a roadside unit equipment group information acquisition request message is sent to the adjacent roadside unit, for example Figure 2 The vehicle is about to drive to the RSU5 position. The vehicle can turn left, turn right, make a U-turn and go straight at the RSU5 position. When there is no roadside unit device information in the downstream node ID of any driving direction, the device MAC address of RSU5 is obtained according to the ID value of the adjacent intersection node in the map information, and a roadside unit device group information acquisition request message is constructed. A temporary symmetric key is created, and the request content is encrypted with the symmetric key to generate the message content part. The temporary symmetric key is then encrypted with the public key of RSU5's certificate to generate the key part of the request message, which is then unicasted to RSU5 to obtain the device information of RSU2, RSU3 and RSU8.

[0132] Step 4: If the certificate content attached to the Map message passes verification, the onboard unit caches the map information and certificate public key content in the Map message;

[0133] Step 5: The OMU constructs a request message for obtaining the RSU device group information (referred to as the request message) based on the access layer source MAC address of the Map message.

[0134] Step 6: The onboard unit creates a temporary symmetric key and uses the symmetric key to encrypt the request content to generate the content part of the request message;

[0135] Step 7: The OMU encrypts the temporary symmetric key with the public key of the target RSU's certificate to generate the key portion of the request message, and sends the request message via PC5 air interface unicast.

[0136] The target roadside unit is the roadside unit that broadcasts the Map message through the PC5 air interface in step 1.

[0137] Step 8: The OMU receives the target RSU device group information fed back by the target RSU in response to the request message.

[0138] Step 9: The onboard unit performs acquisition and / or deletion processing on the roadside unit device group information while the vehicle is traveling (explained in detail later).

[0139] See also Figure 5b The process of the onboard unit obtaining the roadside unit device group information from the cloud platform includes, for example:

[0140] Step 1: The onboard unit obtains the vehicle's own speed in real time; wherein, the vehicle is the vehicle to which the onboard unit belongs (the same applies below and will not be explained again).

[0141] Step 2: When the vehicle speed is greater than 0 (i.e., the vehicle is in motion), the onboard unit determines whether there is map information for the area where the vehicle is currently located. If so, it further determines whether there is roadside unit equipment information for the adjacent intersection at the current location;

[0142] Step 3. When the vehicle does not have map information for the current area, or the vehicle does not have roadside unit equipment information for the adjacent intersection at its current location, a request message (referred to as a request message) for obtaining map information and adjacent roadside unit equipment group information is initiated to the Internet of Vehicles cloud platform through the Uu air interface, and the request message carries the vehicle's current location information.

[0143] Step 4: The on-board unit receives the target roadside unit device group information fed back by the cloud platform in response to the request message.

[0144] Step 5: The onboard unit performs acquisition and / or deletion processing on the roadside unit device group information while the vehicle is traveling.

[0145] Regarding the onboard unit involved in the above process, while the vehicle is driving, the vehicle performs the acquisition and / or deletion of the roadside unit device group information. The acquisition can be to obtain the latest roadside unit device group information using a similar process as described above; the deletion is to save the onboard unit cache space. When the preset conditions are met, one or more roadside unit device information in the vehicle's currently cached roadside unit device group information can be deleted. For example:

[0146] In some embodiments, when a vehicle leaves a current intersection, the onboard unit deletes the roadside unit device information corresponding to the previous intersection ID to save onboard unit cache space;

[0147] In some embodiments, when a vehicle starts route navigation planning, the onboard unit determines the roadside unit device information that needs to be deleted based on the navigation route. For example, when a vehicle starts route navigation planning, it determines whether the corresponding intersection will be passed repeatedly, and thus determines whether the roadside unit device information corresponding to the intersection node ID needs to be deleted, thereby reducing the frequent acquisition of roadside unit device group information. For example, if the vehicle's driving route is RSU9→RSU7→RSU5→RSU7→RSU9, then the intersection node corresponding to RSU9 will be passed repeatedly, so the device information of this roadside unit can be retained and not deleted.

[0148] In some embodiments, the roadside unit device information stored in the vehicle's on-board unit is automatically deleted when the set maximum aging time is reached, that is, the roadside unit device information that has been stored for more than a preset time is deleted.

[0149] See below Figure 6 , gives a more specific example of the communication process of the vehicle-mounted unit during vehicle driving. For example, it includes the following steps:

[0150] S601. The onboard unit obtains the current position information of the vehicle (the vehicle to which the roadside unit belongs) in real time while the vehicle is traveling.

[0151] S602: The onboard unit determines whether the roadside unit equipment information corresponding to the intersection downstream of the current location exists. If yes, execute step S608; otherwise, execute step S603;

[0152] S603: The onboard unit uses the ID value of the adjacent intersection in the map information to match the roadside unit device group information cached by itself;

[0153] S604: The OMU constructs a request for obtaining the roadside unit device group information based on the device MAC address in the obtained roadside unit device group information.

[0154] S605. The onboard unit creates a temporary symmetric key and encrypts the request content to generate the message content.

[0155] S606. The onboard unit encrypts the temporary symmetric key using the certificate public key to generate a message key portion, combines the message content portion and the message key portion into a request message, and sends the request message via PC5 air interface unicast.

[0156] S607: The onboard unit obtains the roadside unit equipment group information corresponding to the adjacent intersection;

[0157] S608. The onboard unit performs reception processing for messages with no certificate content (e.g., messages other than map messages);

[0158] S609, the vehicle leaves the current intersection;

[0159] S610: The vehicle-mounted unit determines whether the vehicle has started path navigation planning; if so, execute step S611; otherwise, execute step S612;

[0160] S611, the onboard unit determines whether the vehicle will pass through the previous intersection again; if yes, execute step S613; otherwise, execute step S612;

[0161] S612: The onboard unit deletes the roadside unit equipment information corresponding to the previous intersection ID;

[0162] S613: The onboard unit determines to retain the roadside unit device group information of the previous intersection and not to delete it;

[0163] S614: If any roadside unit device information in the roadside unit device group information stored in the on-board unit reaches a preset maximum aging time, the roadside unit device information is automatically deleted.

[0164] For details on the onboard unit's process for receiving and processing messages without certificate content, see Figure 7 , for example:

[0165] Step 1: The vehicle's onboard unit receives in real time the RSI, RSM, and / or SPAT messages broadcast by the roadside unit, i.e., messages without certificate content;

[0166] Step 2: The OMU uses the access layer source MAC address of the message without certificate content (i.e., the device MAC address of the roadside unit that broadcasts the message without certificate content) as the key value to match the roadside unit device group information cached in the vehicle and determine whether the match is successful;

[0167] Step 3. If there is no match (i.e., there is no device MAC address with the same Key value in the roadside unit device group information cached in the vehicle), the message without certificate content is deemed abnormal and discarded; if the match is successful (i.e., there is a device MAC address with the same Key value in the roadside unit device group information cached in the vehicle), it means that the device information of the roadside unit that broadcasts the message without certificate content is stored locally, and then the certificate public key corresponding to the device information of the roadside unit is extracted, and the signature of the message without certificate content is verified; if the verification is unsuccessful, the message without certificate content is deemed to be a forged message and discarded; if the verification is successful, the message without certificate content is parsed.

[0168] In summary, see Figure 8 On the terminal side (e.g., an onboard unit), an embodiment of the present application provides a vehicle network communication method including:

[0169] S101. Based on the current location information of the vehicle, obtain roadside unit device group information for a road section where the vehicle is not traveling; wherein the roadside unit device group information includes at least one piece of roadside unit device information, and the roadside unit device information includes: an identifier of a map area to which the roadside unit belongs, an identifier of an intersection to which the roadside unit belongs within the map area, a device media access control address of the roadside unit, and content of a certificate of the roadside unit;

[0170] S102: Utilize at least one piece of roadside unit equipment information in the roadside unit equipment group information to transmit messages between the vehicle and the roadside unit during driving.

[0171] In some embodiments, based on the current position information of the vehicle, obtaining the roadside unit equipment group information of the road section where the vehicle is not traveling includes:

[0172] Based on the current location information of the vehicle, send the roadside unit device group information acquisition request message to the network side node (which may refer to the request message sent to the target roadside unit or the request message sent to the cloud platform);

[0173] Receiving the roadside unit device group information sent by the network side node in response to the roadside unit device group information acquisition request message;

[0174] The network side node is the Internet of Vehicles cloud platform (e.g. Figure 5b process shown) or target roadside unit (e.g. Figure 5a process shown).

[0175] In some embodiments, when the network-side node is a target roadside unit, the roadside unit device group information acquisition request message is generated in the following manner:

[0176] Creating a symmetric key, and using the symmetric key to encrypt the request content of the roadside unit device group information acquisition request message to generate a content part;

[0177] Encrypting the symmetric key using the public key of the target roadside unit's certificate to generate a key portion;

[0178] The roadside unit device group information acquisition request message is constructed using the content part and the key part.

[0179] In some embodiments, the public key of the target roadside unit's certificate is obtained in the following manner:

[0180] Receive a map message sent by a target roadside unit, the map message including the roadside unit's certificate content and message signature value. The roadside unit's certificate content includes the roadside unit's certificate public key. For example, when the vehicle does not have map information for the current area, or the vehicle does not have roadside unit equipment information for the intersection near its current location, receive a Map message broadcast by the roadside unit via the PC5 air interface.

[0181] Verify the validity of the certificate content in the map message, and when the verification passes, cache the map information in the map message and the certificate content of the roadside unit.

[0182] In some embodiments, the method further comprises:

[0183] Receiving a message without certificate content broadcast by a roadside unit, wherein the message without certificate content is a roadside traffic information message, a roadside safety message, or a signal light phase and timing message;

[0184] Using the message access layer source media access control address of the uncertified content as a key value, searching for a matching media access control address in the locally cached roadside unit device group information;

[0185] If the match fails, the message without certificate content is determined to be abnormal and discarded;

[0186] If the match is successful, the certificate content corresponding to the key value is extracted from the roadside unit equipment group information, and the certificate content is used to perform signature verification on the message without certificate content. If the verification is unsuccessful, the message without certificate content is determined to be abnormal and discarded. If the verification is successful, the message without certificate content is processed.

[0187] In some embodiments, the method further comprises:

[0188] At least one of the following methods is used to delete the roadside unit device information in the roadside unit device group information:

[0189] When the vehicle leaves the current intersection, the roadside unit equipment information corresponding to the previous intersection is deleted;

[0190] When the vehicle starts path navigation planning, the roadside unit equipment information that needs to be deleted is determined based on the navigation path;

[0191] Delete the roadside unit equipment information that has been stored for longer than the preset time.

[0192] On the roadside unit side, see Figure 9 , an embodiment of the present application provides a vehicle network communication method, including:

[0193] S201. Obtain roadside unit device group information; wherein the roadside unit device group information includes at least one roadside unit device information, the roadside unit device information including: an identifier of a map area to which the roadside unit belongs, an identifier of an intersection to which the roadside unit belongs within the map area, a device media access control address of the roadside unit, and content of a certificate of the roadside unit;

[0194] S202: Send the roadside unit device group information to the vehicle-mounted unit.

[0195] In some embodiments, obtaining the roadside unit device group information includes:

[0196] Send a registration request to the IoV cloud platform, which contains the latitude and longitude coordinates of the local roadside unit, the device MAC address, and the certificate content;

[0197] Receive the roadside unit device group information sent by the Internet of Vehicles cloud platform in response to the registration request.

[0198] In some embodiments, the sending the roadside unit device group information to the onboard unit includes:

[0199] Receive a roadside unit device group information acquisition request message sent by the vehicle-mounted unit;

[0200] The roadside unit device group information acquisition request message is verified (including verification of the MAC address and message content), and when the verification passes, the roadside unit device group information is sent to the onboard unit.

[0201] In some embodiments, the method further comprises:

[0202] Send a broadcast message. When the broadcast message is a map message, the map message includes the certificate content and message signature value of the roadside unit, and the certificate content of the roadside unit includes the certificate public key of the roadside unit. When the broadcast message is a message without certificate content other than a map message (such as RSI, RSM, SPAT message), the message without certificate content includes a message signature value, but does not need to include certificate content.

[0203] On the IoV cloud platform side, see Figure 10 , an embodiment of the present application provides a vehicle network communication method, including:

[0204] S301. Generate roadside unit device group information (which may be generated for each roadside unit or for multiple roadside units); wherein the roadside unit device group information includes at least one roadside unit device information, and the roadside unit device information includes: an identifier of a map area to which the roadside unit belongs, an identifier of an intersection to which the roadside unit belongs within the map area, a device media access control address of the roadside unit, and content of a roadside unit certificate;

[0205] S302: Send the roadside unit device group information (either to the roadside unit or directly to the vehicle-mounted unit).

[0206] In some embodiments, generating roadside unit device group information includes:

[0207] For any registered roadside unit, the roadside unit device group information corresponding to the roadside unit is generated by using the association relationship between the roadside unit and its adjacent roadside units, as well as the adjacent roadside unit device information.

[0208] In some embodiments, the method further comprises:

[0209] Receive a registration request sent by a roadside unit, the registration request carrying the latitude and longitude coordinates, device MAC address, and certificate content of the roadside unit;

[0210] Verify the validity of the certificate content of the roadside unit. When the verification passes, determine the identifier of the map area to which the roadside unit belongs and the identifier of the intersection to which the roadside unit belongs within the map area based on the latitude and longitude coordinate values ​​of the roadside unit, and generate the equipment information of the roadside unit.

[0211] In summary, the technical solutions provided in the embodiments of the present application have the following beneficial effects:

[0212] Based on the real-time location and the cached device information of each intersection in the map information, the vehicle obtains the roadside unit equipment information of the untraveled section in advance, thereby ensuring that V2I safety communication is not affected during the high-speed driving of the vehicle across nodes and regions. Specifically, the roadside unit equipment group is bound based on the area and intersection ID in the map information, so that the vehicle can determine whether there is a roadside unit equipment information cache based on the area and intersection ID in the map information, and obtain the roadside unit equipment information of the untraveled section in advance. Therefore, the on-board unit can directly verify the validity of the broadcast messages of the roadside units at multiple intersections based on the equipment group information, ensuring that V2I safety communication is not affected during the high-speed driving of the vehicle across nodes and regions;

[0213] Each roadside unit is bound to the roadside units corresponding to its upstream and downstream intersections to form device group information. During driving, the vehicle can obtain the roadside unit device group information at any map node in real time. The device group information can be used to directly verify the validity of broadcast messages at multiple intersections, thus achieving certificate-free communication for non-map messages.

[0214] Based on the cloud platform hierarchical value division, the map node range included in the equipment group information of each roadside unit can be dynamically changed, thereby dynamically adjusting the cache size and acquisition frequency of the vehicle-side equipment group information. That is, based on the cloud platform hierarchical value division, each roadside unit is bound to its corresponding equipment group member. The roadside unit equipment information on each map node can be obtained in real time during vehicle driving. The device MAC address matching and certificate public key verification in the device information can ensure that the roadside communication messages received by the vehicle's on-board unit are authentic and valid. In addition, the roadside unit can broadcast and send RSM, RSI and SPAT messages with a higher sending frequency without additional certificates, thereby reducing the message length and avoiding the delay problem caused by frequent certificate verification.

[0215] Roadside unit equipment information can be automatically deleted according to the configured maximum aging time, or the roadside unit equipment information that has passed the intersection node can be quickly deleted according to the vehicle's driving path, thereby saving the cache space of the vehicle's on-board unit.

[0216] The following is an introduction to the equipment or device provided in the embodiments of the present application, in which the explanations or examples of technical features that are the same as or corresponding to those described in the above method are not repeated hereafter.

[0217] On the vehicle terminal side, such as OBU, see Figure 11 , an embodiment of the present application provides a vehicle networking communication device including:

[0218] The processor 600 is configured to read the program in the memory 620 and execute the following process:

[0219] Based on the vehicle's current location information, obtaining roadside unit device group information for a road section where the vehicle is not traveling; wherein the roadside unit device group information includes at least one piece of roadside unit device information, the roadside unit device information including: an identifier of a map area to which the roadside unit belongs, an identifier of an intersection to which the roadside unit belongs within the map area, a device media access control address of the roadside unit, and content of a certificate of the roadside unit;

[0220] At least one piece of roadside unit equipment information in the roadside unit equipment group information is used to transmit messages between the vehicle and the roadside unit during driving.

[0221] In some embodiments, based on the current position information of the vehicle, obtaining the roadside unit equipment group information of the road section where the vehicle is not traveling includes:

[0222] Based on the current location information of the vehicle, sending a request message for obtaining the roadside unit device group information to the network side node;

[0223] Receiving the roadside unit device group information sent by the network side node in response to the roadside unit device group information acquisition request message;

[0224] Among them, the network side node is the Internet of Vehicles cloud platform or the target roadside unit.

[0225] In some embodiments, when the network-side node is a target roadside unit, the roadside unit device group information acquisition request message is generated in the following manner:

[0226] Creating a symmetric key, and using the symmetric key to encrypt the request content of the roadside unit device group information acquisition request message to generate a content part;

[0227] Encrypting the symmetric key using the public key of the target roadside unit's certificate to generate a key portion;

[0228] The roadside unit device group information acquisition request message is constructed using the content part and the key part.

[0229] In some embodiments, the public key of the target roadside unit's certificate is obtained in the following manner:

[0230] Receive a map message sent by a target roadside unit, wherein the map message includes the certificate content and message signature value of the roadside unit, and the certificate content of the roadside unit includes the certificate public key of the roadside unit;

[0231] Verify the validity of the certificate content in the map message, and when the verification passes, cache the map information in the map message and the certificate content of the roadside unit.

[0232] In some embodiments, the processor 600 is further configured to read a program in the memory 620 and execute the following process:

[0233] Receiving a message without certificate content broadcast by a roadside unit, wherein the message without certificate content is a roadside traffic information message, a roadside safety message, or a signal light phase and timing message;

[0234] Using the message access layer source media access control address of the uncertified content as a key value, searching for a matching media access control address in the locally cached roadside unit device group information;

[0235] If the match fails, the message without certificate content is determined to be abnormal and discarded;

[0236] If the match is successful, the certificate content corresponding to the key value is extracted from the roadside unit equipment group information, and the certificate content is used to perform signature verification on the message without certificate content. If the verification is unsuccessful, the message without certificate content is determined to be abnormal and discarded. If the verification is successful, the message without certificate content is processed.

[0237] In some embodiments, the processor 600 is further configured to read a program in the memory 620 and execute the following process:

[0238] At least one of the following methods is used to delete the roadside unit device information in the roadside unit device group information:

[0239] When the vehicle leaves the current intersection, the roadside unit equipment information corresponding to the previous intersection is deleted;

[0240] When the vehicle starts path navigation planning, the roadside unit equipment information that needs to be deleted is determined based on the navigation path;

[0241] Delete the roadside unit equipment information that has been stored for longer than the preset time.

[0242] In some embodiments, the Internet of Vehicles communication device further includes a transceiver 610 for receiving and sending data under the control of the processor 600 .

[0243] Among them, Figure 11 In the embodiment of the present invention, the bus architecture can include any number of interconnected buses and bridges, specifically linking various circuits such as one or more processors represented by processor 600 and memory represented by memory 620. The bus architecture can also link various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and therefore not further described herein. The bus interface provides an interface. The transceiver 610 can be multiple components, namely, a transmitter and a receiver, providing a unit for communicating with various other devices over a transmission medium.

[0244] In some embodiments, a user interface 630 is also included. The user interface 630 can be an interface that can connect to required external or internal devices. The connected devices include but are not limited to a keypad, a display, a speaker, a microphone, a joystick, etc.

[0245] The processor 600 is responsible for managing the bus architecture and general processing, and the memory 620 can store data used by the processor 600 when performing operations.

[0246] In some embodiments, the processor 600 may be a CPU (central processing unit), an ASIC (Application Specific Integrated Circuit), an FPGA (Field-Programmable Gate Array), or a CPLD (Complex Programmable Logic Device).

[0247] On the network side, see Figure 12 , an embodiment of the present application provides a vehicle networking communication device including: a processor 500, a transceiver 510, and a memory 520;

[0248] When the Internet of Vehicles communication device on the network side is an RSU:

[0249] The processor 500 is configured to read the program in the memory 520 and execute the following process:

[0250] Obtaining roadside unit device group information; wherein the roadside unit device group information includes at least one roadside unit device information, the roadside unit device information including: an identifier of a map area to which the roadside unit belongs, an identifier of an intersection to which the roadside unit belongs within the map area, a device media access control address of the roadside unit, and content of a certificate of the roadside unit;

[0251] Send the roadside unit equipment group information to the vehicle-mounted unit.

[0252] In some embodiments, obtaining the roadside unit device group information includes:

[0253] Send a registration request to the IoV cloud platform, which contains the latitude and longitude coordinates of the local roadside unit, the device MAC address, and the certificate content;

[0254] Receive the roadside unit device group information sent by the Internet of Vehicles cloud platform in response to the registration request.

[0255] In some embodiments, the sending the roadside unit device group information to the onboard unit includes:

[0256] Receive a roadside unit device group information acquisition request message sent by the vehicle-mounted unit;

[0257] The roadside unit device group information acquisition request message is verified, and when the verification passes, the roadside unit device group information is sent to the onboard unit.

[0258] In some embodiments, the processor 500 is further configured to read a program in the memory 520 and execute the following process:

[0259] Send a broadcast message. When the broadcast message is a map message, the map message includes the certificate content and message signature value of the roadside unit, and the certificate content of the roadside unit includes the certificate public key of the roadside unit. When the broadcast message is a message without certificate content other than a map message, the message without certificate content includes a message signature value.

[0260] When the IoV communication device on the network side is an IoV cloud platform:

[0261] The processor 500 is configured to read the program in the memory 520 and execute the following process:

[0262] Generate roadside unit device group information; wherein the roadside unit device group information includes at least one roadside unit device information, the roadside unit device information including: an identifier of a map area to which the roadside unit belongs, an identifier of an intersection to which the roadside unit belongs within the map area to which it belongs, a device media access control address of the roadside unit, and certificate content of the roadside unit;

[0263] Send the roadside unit equipment group information.

[0264] In some embodiments, generating roadside unit device group information includes:

[0265] For any registered roadside unit, the roadside unit device group information corresponding to the roadside unit is generated by using the association relationship between the roadside unit and its adjacent roadside units, as well as the adjacent roadside unit device information.

[0266] In some embodiments, the processor 500 is further configured to read a program in the memory 520 and execute the following process:

[0267] Receive a registration request sent by a roadside unit, the registration request carrying the latitude and longitude coordinates, device MAC address, and certificate content of the roadside unit;

[0268] Verify the validity of the certificate content of the roadside unit. When the verification passes, determine the identifier of the map area to which the roadside unit belongs and the identifier of the intersection to which the roadside unit belongs within the map area based on the latitude and longitude coordinate values ​​of the roadside unit, and generate the equipment information of the roadside unit.

[0269] The transceiver 510 is configured to receive and send data under the control of the processor 500 .

[0270] Among them, Figure 12In the embodiment, the bus architecture may include any number of interconnected buses and bridges, specifically linking together various circuits of one or more processors represented by processor 500 and memory represented by memory 520. The bus architecture may also link together various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are all well known in the art and therefore will not be described further herein. The bus interface provides an interface. The transceiver 510 may be a plurality of components, i.e., a transmitter and a receiver, providing a unit for communicating with various other devices on a transmission medium. The processor 500 is responsible for managing the bus architecture and general processing, and the memory 520 may store data used by the processor 500 when performing operations.

[0271] The processor 500 may be a central processing unit (CPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), or a complex programmable logic device (CPLD).

[0272] See also Figure 13 On the vehicle-mounted unit side, an Internet of Vehicles communication device provided by an embodiment of the present application includes:

[0273] A roadside unit device group information acquisition unit 11 is configured to acquire roadside unit device group information for a road section on which the vehicle is not traveling based on the vehicle's current location information; wherein the roadside unit device group information includes at least one piece of roadside unit device information, the roadside unit device information including: an identifier of a map area to which the roadside unit belongs, an identifier of an intersection to which the roadside unit belongs within the map area to which it belongs, a device media access control address of the roadside unit, and content of a roadside unit certificate;

[0274] The message transmission processing unit 12 is configured to utilize at least one piece of roadside unit equipment information in the roadside unit equipment group information to perform message transmission between the vehicle and the roadside unit during driving.

[0275] In some embodiments, based on the current position information of the vehicle, obtaining the roadside unit equipment group information of the road section where the vehicle is not traveling includes:

[0276] Based on the current location information of the vehicle, sending a request message for obtaining the roadside unit device group information to the network side node;

[0277] Receiving the roadside unit device group information sent by the network side node in response to the roadside unit device group information acquisition request message;

[0278] Among them, the network side node is the Internet of Vehicles cloud platform or the target roadside unit.

[0279] In some embodiments, when the network-side node is a target roadside unit, the roadside unit device group information acquisition request message is generated in the following manner:

[0280] Creating a symmetric key, and using the symmetric key to encrypt the request content of the roadside unit device group information acquisition request message to generate a content part;

[0281] Encrypting the symmetric key using the public key of the target roadside unit's certificate to generate a key portion;

[0282] The roadside unit device group information acquisition request message is constructed using the content part and the key part.

[0283] In some embodiments, the public key of the target roadside unit's certificate is obtained in the following manner:

[0284] Receive a map message sent by a target roadside unit, wherein the map message includes the certificate content and message signature value of the roadside unit, and the certificate content of the roadside unit includes the certificate public key of the roadside unit;

[0285] Verify the validity of the certificate content in the map message, and when the verification passes, cache the map information in the map message and the certificate content of the roadside unit.

[0286] In some embodiments, the message transmission processing unit 12 is further configured to:

[0287] Receiving a message without certificate content broadcast by a roadside unit, wherein the message without certificate content is a roadside traffic information message, a roadside safety message, or a signal light phase and timing message;

[0288] Using the message access layer source media access control address of the uncertified content as a key value, searching for a matching media access control address in the locally cached roadside unit device group information;

[0289] If the match fails, the message without certificate content is determined to be abnormal and discarded;

[0290] If the match is successful, the certificate content corresponding to the key value is extracted from the roadside unit equipment group information, and the certificate content is used to perform signature verification on the message without certificate content. If the verification is unsuccessful, the message without certificate content is determined to be abnormal and discarded. If the verification is successful, the message without certificate content is processed.

[0291] In some embodiments, the message transmission processing unit 12 is further configured to:

[0292] At least one of the following methods is used to delete the roadside unit device information in the roadside unit device group information:

[0293] When the vehicle leaves the current intersection, the roadside unit equipment information corresponding to the previous intersection is deleted;

[0294] When the vehicle starts path navigation planning, the roadside unit equipment information that needs to be deleted is determined based on the navigation path;

[0295] Delete the roadside unit equipment information that has been stored for longer than the preset time.

[0296] See also Figure 14 On the drive test unit side, an Internet of Vehicles communication device provided by an embodiment of the present application includes:

[0297] A roadside unit device group information acquisition unit 21 is configured to acquire roadside unit device group information; wherein the roadside unit device group information includes at least one piece of roadside unit device information, the roadside unit device information including: an identifier of a map area to which the roadside unit belongs, an identifier of an intersection to which the roadside unit belongs within the map area, a device media access control address of the roadside unit, and content of a roadside unit certificate;

[0298] The roadside unit device group information sending unit 22 is used to send the roadside unit device group information to the vehicle-mounted unit.

[0299] In some embodiments, obtaining the roadside unit device group information includes:

[0300] Send a registration request to the IoV cloud platform, which contains the latitude and longitude coordinates of the local roadside unit, the device MAC address, and the certificate content;

[0301] Receive the roadside unit device group information sent by the Internet of Vehicles cloud platform in response to the registration request.

[0302] In some embodiments, the sending the roadside unit device group information to the onboard unit includes:

[0303] Receive a roadside unit device group information acquisition request message sent by the vehicle-mounted unit;

[0304] The roadside unit device group information acquisition request message is verified, and when the verification passes, the roadside unit device group information is sent to the onboard unit.

[0305] In some embodiments, the roadside unit device group information sending unit 22 is further configured to:

[0306] Send a broadcast message. When the broadcast message is a map message, the map message includes the certificate content and message signature value of the roadside unit, and the certificate content of the roadside unit includes the certificate public key of the roadside unit. When the broadcast message is a message without certificate content other than a map message, the message without certificate content includes a message signature value.

[0307] See also Figure 15 On the IoV cloud platform side, an IoV communication device provided by an embodiment of the present application includes:

[0308] A roadside unit device group information generating unit 31 is configured to generate roadside unit device group information; wherein the roadside unit device group information includes at least one piece of roadside unit device information, the roadside unit device information including: an identifier of a map area to which the roadside unit belongs, an identifier of an intersection to which the roadside unit belongs within the map area, a device media access control address of the roadside unit, and content of a certificate of the roadside unit;

[0309] The roadside unit device group information sending unit 32 is used to send the roadside unit device group information.

[0310] In some embodiments, generating roadside unit device group information includes:

[0311] For any registered roadside unit, the roadside unit device group information corresponding to the roadside unit is generated by using the association relationship between the roadside unit and its adjacent roadside units, as well as the adjacent roadside unit device information.

[0312] In some embodiments, the roadside unit device group information generating unit 31 is further configured to:

[0313] Receive a registration request sent by a roadside unit, the registration request carrying the latitude and longitude coordinates, device MAC address, and certificate content of the roadside unit;

[0314] Verify the validity of the certificate content of the roadside unit. When the verification passes, determine the identifier of the map area to which the roadside unit belongs and the identifier of the intersection to which the roadside unit belongs within the map area based on the latitude and longitude coordinate values ​​of the roadside unit, and generate the equipment information of the roadside unit.

[0315] It should be noted that the division of units in the embodiments of the present application is schematic and is merely a logical functional division. In actual implementation, other division methods may be used. Furthermore, the functional units in the various embodiments of the present application may be integrated into a single processing unit, or each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or software functional units.

[0316] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) or a processor to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0317] An embodiment of the present application provides a computing device, which may specifically be a desktop computer, a portable computer, a smart phone, a tablet computer, a personal digital assistant (PDA), etc. The computing device may include a central processing unit (CPU), a memory, input / output devices, etc. The input devices may include a keyboard, a mouse, a touch screen, etc., and the output devices may include a display device such as a liquid crystal display (LCD) or a cathode ray tube (CRT).

[0318] The memory may include a read-only memory (ROM) and a random access memory (RAM), and provides program instructions and data stored in the memory to the processor. In an embodiment of the present application, the memory may be used to store the program of any of the methods provided in the embodiments of the present application.

[0319] The processor calls the program instructions stored in the memory, and the processor is used to execute any of the methods provided in the embodiments of the present application according to the obtained program instructions.

[0320] The present application embodiment also provides a computer program product or computer program, which includes computer instructions, which are stored in a computer-readable storage medium. The processor of the computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions so that the computer device performs any of the methods described in the above embodiments. The program product can adopt any combination of one or more readable media. The readable medium can be a readable signal medium or a readable storage medium. The readable storage medium can be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples of readable storage media (non-exhaustive list) include: an electrical connection with one or more wires, a portable 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 of the above.

[0321] The present invention provides a computer-readable storage medium for storing computer program instructions used by the apparatus provided in the above embodiments of the present invention, which includes a program for executing any of the methods provided in the above embodiments of the present invention. The computer-readable storage medium may be a non-transitory computer-readable medium.

[0322] The computer-readable storage medium can be any available medium or data storage device that can be accessed by a computer, including but not limited to magnetic storage (such as floppy disks, hard disks, magnetic tapes, magneto-optical disks (MO), etc.), optical storage (such as CDs, DVDs, BDs, HVDs, etc.), and semiconductor storage (such as ROMs, EPROMs, EEPROMs, non-volatile memories (NANDFLASH), solid-state drives (SSDs)), etc.

[0323] It should be understood that:

[0324] The access technology through which entities in the communication network transmit traffic can be any suitable current or future technology, such as WLAN (Wireless Local Access Network), WiMAX (Worldwide Interoperability for Microwave Access), LTE, LTE-A, 5G, Bluetooth, infrared, etc.; in addition, the embodiments can also apply wired technology, for example, IP-based access technology, such as a wired network or a fixed line.

[0325] Embodiments suitable for being implemented as software code or a portion thereof and run using a processor or processing functionality are independent of the software code and may be specified using any known or future developed programming language, such as a high-level programming language such as objective-C, C, C++, C#, Java, Python, Javascript, other scripting languages, etc., or a low-level programming language such as machine language or assembler.

[0326] The implementation of the embodiments is hardware independent and may be implemented using any known or future developed hardware technology or any mixture thereof, such as a microprocessor or CPU (Central Processing Unit), MOS (Metal Oxide Semiconductor), CMOS (Complementary MOS), BiMOS (Bipolar MOS), BiCMOS (Bipolar CMOS), ECL (Emitter Coupled Logic) and / or TTL (Transistor-Transistor Logic).

[0327] Embodiments may be implemented as separate devices, apparatuses, units, components or functions, or in a distributed manner, for example, one or more processors or processing functions may be used or shared in a process, or one or more processing segments or processing portions may be used and shared in a process, where one physical processor or more than one physical processor may be used to implement one or more processing portions dedicated to a particular process as described.

[0328] The apparatus may be implemented by a semiconductor chip, a chipset, or a (hardware) module including such a chip or chipset.

[0329] The embodiments may also be implemented as any combination of hardware and software, such as ASIC (Application Specific IC (Integrated Circuit)) components, FPGA (Field Programmable Gate Array) or CPLD (Complex Programmable Logic Device) components or DSP (Digital Signal Processor) components.

[0330] The embodiments may also be implemented as a computer program product including a computer usable medium having computer readable program code embodied therein, the computer readable program code being adapted to perform the processes as described in the embodiments, wherein the computer usable medium may be a non-transitory medium.

[0331] Those skilled in the art will appreciate that the embodiments of the present application can be provided as methods, systems, or computer program products. Therefore, the present application can adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application can adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to magnetic disk storage and optical storage, etc.) that contain computer-usable program code.

[0332] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the steps in the process. Figure 1 a process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0333] These computer program instructions may also be stored in a computer readable memory that can direct a computer or other programmable data processing device to work in a specific manner, so that the instructions stored in the computer readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 a process or multiple processes and / or boxes Figure 1 The function specified in one or more boxes.

[0334] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operational steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing the instructions executed on the computer or other programmable device for implementing the process. Figure 1 a process or multiple processes and / or boxes Figure 1 A step that specifies a function in one or more boxes.

[0335] Obviously, those skilled in the art may make various changes and modifications to this application without departing from the spirit and scope of this application. Thus, if these modifications and variations of this application fall within the scope of the claims of this application and their equivalents, this application is intended to include these modifications and variations.

Claims

1. A vehicle network communication method, characterized in that: Applied to an on-board unit, the method includes: Based on the vehicle's current location information, obtaining roadside unit device group information for a road section where the vehicle is not traveling; wherein the roadside unit device group information includes at least one piece of roadside unit device information, the roadside unit device information including: an identifier of a map area to which the roadside unit belongs, an identifier of an intersection to which the roadside unit belongs within the map area, a device media access control address of the roadside unit, and content of a certificate of the roadside unit; At least one piece of roadside unit equipment information in the roadside unit equipment group information is used to transmit messages between the vehicle and the roadside unit during driving.

2. The method according to claim 1, characterized in that Based on the current position information of the vehicle, obtaining the roadside unit equipment group information of the road section where the vehicle is not traveling, including: Based on the current location information of the vehicle, sending a request message for obtaining the roadside unit device group information to the network side node; Receiving the roadside unit device group information sent by the network side node in response to the roadside unit device group information acquisition request message; Among them, the network side node is the Internet of Vehicles cloud platform or the target roadside unit.

3. The method according to claim 2, characterized in that When the network-side node is a target roadside unit, the roadside unit device group information acquisition request message is generated in the following manner: Creating a symmetric key, and using the symmetric key to encrypt the request content of the roadside unit device group information acquisition request message to generate a content part; Encrypting the symmetric key using the public key of the target roadside unit's certificate to generate a key portion; The roadside unit device group information acquisition request message is constructed using the content part and the key part.

4. The method according to claim 3, characterized in that The public key of the target roadside unit's certificate is obtained in the following manner: Receive a map message sent by a target roadside unit, wherein the map message includes the certificate content and message signature value of the roadside unit, and the certificate content of the roadside unit includes the certificate public key of the roadside unit; Verify the validity of the certificate content in the map message, and when the verification passes, cache the map information in the map message and the certificate content of the roadside unit.

5. The method according to claim 1, wherein The method further comprises: Receiving a message without certificate content broadcast by a roadside unit, wherein the message without certificate content is a roadside traffic information message, a roadside safety message, or a signal light phase and timing message; Using the message access layer source media access control address of the uncertified content as a key value, searching for a matching media access control address in the locally cached roadside unit device group information; If the match fails, the message without certificate content is determined to be abnormal and discarded; If the match is successful, the certificate content corresponding to the key value is extracted from the roadside unit equipment group information, and the certificate content is used to perform signature verification on the message without certificate content. If the verification is unsuccessful, the message without certificate content is determined to be abnormal and discarded. If the verification is successful, the message without certificate content is processed.

6. The method according to claim 1, characterized in that The method further comprises: At least one of the following methods is used to delete the roadside unit device information in the roadside unit device group information: When the vehicle leaves the current intersection, the roadside unit equipment information corresponding to the previous intersection is deleted; When the vehicle starts path navigation planning, the roadside unit equipment information that needs to be deleted is determined based on the navigation path; Delete the roadside unit equipment information that has been stored for longer than the preset time.

7. A vehicle network communication method, characterized in that: Applied to a roadside unit, the method includes: Obtaining roadside unit device group information for a road section where the vehicle is not traveling; wherein the roadside unit device group information includes at least one roadside unit device information, the roadside unit device information including: an identifier of a map area to which the roadside unit belongs, an identifier of an intersection to which the roadside unit belongs within the map area, a device media access control address of the roadside unit, and content of a certificate of the roadside unit; Send the roadside unit equipment group information to the vehicle-mounted unit.

8. The method according to claim 7, characterized in that The obtaining of roadside unit equipment group information includes: Send a registration request to the IoV cloud platform, which contains the latitude and longitude coordinates of the local roadside unit, the device MAC address, and the certificate content; Receive the roadside unit device group information sent by the Internet of Vehicles cloud platform in response to the registration request.

9. The method according to claim 7, characterized in that The sending of the roadside unit device group information to the onboard unit includes: Receive a roadside unit device group information acquisition request message sent by the vehicle-mounted unit; The roadside unit device group information acquisition request message is verified, and when the verification passes, the roadside unit device group information is sent to the onboard unit.

10. The method according to claim 7, characterized in that The method further comprises: Send a broadcast message. When the broadcast message is a map message, the map message includes the certificate content and message signature value of the roadside unit, and the certificate content of the roadside unit includes the certificate public key of the roadside unit. When the broadcast message is a message without certificate content other than a map message, the message without certificate content includes a message signature value.

11. A vehicle network communication method, characterized in that: Applied to the Internet of Vehicles cloud platform, the method includes: Generate roadside unit device group information for a road section where the vehicle is not traveling; wherein the roadside unit device group information includes at least one roadside unit device information, the roadside unit device information including: an identifier of a map area to which the roadside unit belongs, an identifier of an intersection to which the roadside unit belongs within the map area, a device media access control address of the roadside unit, and content of a certificate of the roadside unit; Send the roadside unit equipment group information.

12. The method according to claim 11, characterized in that The generating of the roadside unit equipment group information includes: For any registered roadside unit, the roadside unit device group information corresponding to the roadside unit is generated by using the association relationship between the roadside unit and its adjacent roadside units, as well as the adjacent roadside unit device information.

13. The method according to claim 11, characterized in that The method further comprises: Receive a registration request sent by a roadside unit, the registration request carrying the latitude and longitude coordinates, device MAC address, and certificate content of the roadside unit; Verify the validity of the certificate content of the roadside unit. When the verification passes, determine the identifier of the map area to which the roadside unit belongs and the identifier of the intersection to which the roadside unit belongs within the map area based on the latitude and longitude coordinate values ​​of the roadside unit, and generate the equipment information of the roadside unit.

14. A vehicle networking communication device, characterized in that: include: a memory for storing program instructions; A processor, configured to call the program instructions stored in the memory and execute the method according to any one of claims 1 to 13 according to the obtained program.

15. A computer program product for a computer, characterized in that The invention comprises software code parts for executing the method according to any one of claims 1 to 13 when the product is run on the computer.

16. A computer-readable storage medium, characterized in that The computer-readable storage medium stores computer-executable instructions, and the computer-executable instructions are used to enable the computer to execute the method according to any one of claims 1 to 13.

Images