Communication method and communication device

Abstract

The invention provides a communication method, a communication device, a computer storage medium and a computer program product. In the technical scheme provided by the invention, when the MAC addresses in the plurality of VSI messages are conflicted, the receiving end of the VSI message only responds to part of the VSI messages and sends the operation response message carrying the conflicted MAC address; therefore, the equipment capable of correctly decrypting the operation response message can decrypt the ciphertext information in the received operation request message by using the own secret key for a few times, so that the resource waste of the equipment can be avoided.

Description

[0001] This application is a divisional application. The application number of the original application is 202110745084.1, and the original application date is June 30, 2021. The entire contents of the original application are incorporated into this application by reference. Technical Field

[0002] The present application relates to the field of communications, and more particularly, to a communication method, a communication device, a computer storage medium, and a computer program product. Background Art

[0003] The wireless communication technology of the Internet of Vehicles enables information exchange between different subsystems of the intelligent transportation system, thus bringing convenience to different applications such as road safety, traffic efficiency, information services, etc. The Internet of Vehicles is mainly designed for broadcast communication, but it can also be used for unicast communication.

[0004] One application scenario of the vehicle network is the near-field payment service. In the method of implementing the near-field payment service through the vehicle network, the on-board unit (OBU) and the road side unit (RSU) perform data exchange to realize the vehicle payment function.

[0005] The interaction process between OBU and RSU may include the following steps: RSU broadcasts a roadside service table (RST) message; OBU determines whether to initiate a response to RSU based on the content in the received RST message; if OBU determines to initiate a response, OBU generates a medium access control (MAC) address and a symmetric key, and uses the symmetric key to encrypt the content that needs to be kept confidential, such as the contract serial number, vehicle information, and stop-by information, and sends the generated MAC address, symmetric key, and encrypted content to RSU through a vehicle service indication (VSI) message; RSU uses the symmetric key in the VSI message to decrypt the encrypted content to obtain the vehicle's charging information; RSU uses the symmetric key to encrypt the transaction record, stop-by information, and other content, and sends the encrypted content to OBU through a request message (action-request), and the above request message also includes the MAC address generated by OBU; OBU determines whether to process the request message based on the MAC address in the received request message. If OBU decides to process the request message, it uses the symmetric key to decrypt it and implements the subsequent process to realize the transaction.

[0006] After research, it was found that the above interaction process will have the following problems: in the same period, multiple OBUs will send VSI messages to the same RSU, and the MAC addresses generated by these multiple OBUs may be the same, that is, an address conflict occurs. In this case, because the MAC addresses in multiple VSI messages are the same, the MAC addresses in multiple request messages responded by the RSU are also the same, so each of the multiple OBUs using the MAC address can successfully decode the MAC address when receiving these multiple request messages, and use its own symmetric key to decrypt these multiple request message information. Among them, the number of OBUs using the same MAC address is the number of times each OBU in these multiple OBUs needs to use its own symmetric key to decrypt, resulting in a waste of OBU resources.

[0007] Therefore, how to solve the address conflict problem of multiple OBUs to avoid waste of OBU resources is called a technical problem that needs to be solved urgently. Summary of the invention

[0008] The present application proposes a communication method, a communication device, a communication system, a computer storage medium and a computer program product that can avoid a device from wasting decryption resources.

[0009] In a first aspect, the present application provides a communication method, which includes: a first device receives a first vehicle service indication VSI message, the first VSI message carries a first media access control MAC address of a second device, a first key of the second device, and a first ciphertext information obtained by encrypting the first information of the second device using the first key; the first device receives the second VSI message, the second VSI message carries a second MAC address of a third device, a second key of the third device, and a second ciphertext information obtained by encrypting the second information of the third device using the second key, and the first MAC address and the second MAC address are the same; the first device sends a first operation request message based on the first VSI message and the second VSI message, the first operation request message carries the first MAC address and the third ciphertext information obtained by encrypting the third information using the first key.

[0010] It is understandable that the first device may also receive VSI messages sent by one or more other devices, and the MAC addresses carried in the VSI messages sent by the one or more devices are the same as the first MAC address.

[0011] If the first device sends multiple operation request messages carrying the same MAC address to multiple VSI messages carrying the same MAC address, each of the multiple sending devices (such as the second device and the third device) corresponding to the multiple VSI messages will successfully verify the multiple operation request messages based on the same MAC address, and further, it is necessary to use its own key to decode the ciphertext information in the multiple operation request messages (most of them will fail to decode), which will generate a large information processing burden. In the communication method described in the first aspect, because the first device only sends one operation request message (such as the first operation request message) carrying the same MAC address to multiple VSI messages carrying the same MAC address, each of the multiple sending devices (such as the second device and the third device) corresponding to the multiple VSI messages only successfully verifies one operation request message based on the same MAC address, and further, it only needs to use its own key to decrypt the ciphertext information in the above-mentioned only one operation request message, thereby avoiding the waste of information processing resources.

[0012] Optionally, in the communication method, the third information may be the same as or different from the first information. For example, the first information may include one or more of the following information: the contract serial number of the second device, information about the vehicle to which the second device belongs, and information about the second device passing through a station, and the third information may include transaction records, etc.

[0013] Similarly, the third ciphertext information may be the same as or different from the first ciphertext information. For example, when the first information is the same as the third information, the first ciphertext information may be the same as the third ciphertext information. For another example, when the first information is different from the third information, the first ciphertext information may be different from the third ciphertext information.

[0014] In this communication method, the first information may include any information that the second device wishes to send to the first device in a confidential manner, the second information may include any information that the third device system wishes to send to the first device in a confidential manner, and the third information may be any information that the first device wishes to send to the second device in a confidential manner.

[0015] In combination with the first aspect, in a first possible implementation method, the first device sends a first operation request message based on the first VSI message and the second VSI message, including: the first device does not send an operation request message in response to the second VSI message; the first device sends the first operation request message based on the first VSI message.

[0016] In this implementation, optionally, the method also includes: the first device receives a third VSI message from the third device, the third VSI message carries a third MAC address of the third device, a third key of the third device, and ciphertext information obtained by encrypting the second information using the third key, and the third MAC address is different from the second MAC address.

[0017] That is to say, after the first device receives the first VSI message sent by the second device and the second VSI message sent by the third device, if the first MAC address of the second device carried in the first VSI message is the same as the second MAC address of the third device carried in the second VSI message, the first device only sends a first operation request message carrying the first MAC address and the ciphertext information encrypted using the first key of the second device, and does not send an operation request message carrying the same address and the ciphertext information encrypted using the second key of the third device.

[0018] In this implementation, in order to ensure that the third device can normally complete the business transaction, the third device can resend the third VSI message carrying the third MAC address different from the second MAC address and the ciphertext information obtained by encrypting the second information using the third key. Among them, because the third MAC address is different from the second MAC address, it can avoid conflicts with other devices whose MAC address is the second MAC address, thereby facilitating the first device to normally send the operation request message to the third device based on the third VSI message.

[0019] In this implementation, the third MAC address being different from the second MAC address may also be understood as the third MAC address being different from the first MAC address.

[0020] In this implementation, optionally, the third key may be the same as or different from the second key. If the third key is the same as the second key, the complexity of the third device may be reduced.

[0021] In combination with the first aspect, in a second possible implementation, the method also includes: the first device sends a second operation request message based on the first VSI message and the second VSI message, the second operation request message carries a third MAC address and fourth ciphertext information obtained by encrypting fourth information using the second key, and the third MAC address is different from the second MAC address.

[0022] That is to say, after the first device receives the first VSI message sent by the second device and the second VSI message sent by the third device, if the first MAC address of the second device carried in the first VSI message is the same as the second MAC address carried in the second VSI message, the first device sends a first operation request message carrying the first MAC address and ciphertext information encrypted using the first key of the second device, and sends a second operation request message carrying a third MAC address different from the second MAC address and ciphertext information encrypted using the second key of the third device.

[0023] This can not only reduce the number of times the second device and the third device need to use their own keys to decrypt the ciphertext information, thereby avoiding waste of resources, but also help ensure that the second device and the third device can respectively receive their corresponding operation request messages, thereby completing the business.

[0024] In this implementation, the fourth information may include any information that the first device wishes to send to the third device in a confidential manner.

[0025] Optionally, in this implementation, the fourth information may be the same as or different from the second information. For example, the second information may include one or more of the following information: the contract serial number of the third device, the information of the vehicle to which the third device belongs, and the transit information of the third device, and the fourth information may include transaction records, etc.

[0026] Similarly, the fourth ciphertext information may be the same as or different from the second ciphertext information. For example, when the second information is the same as the fourth information, the fourth ciphertext information may be the same as the second ciphertext information. For another example, when the second information is different from the fourth information, the second ciphertext information may be different from the fourth ciphertext information.

[0027] In combination with the second possible implementation manner, in a third possible implementation manner, the third MAC address is a reserved MAC address.

[0028] In combination with the second possible implementation manner, in a fourth possible implementation manner, the third MAC address is a MAC address determined based on a preset rule and the second MAC address.

[0029] For example, the preset rule may include: adding a preset value to the second MAC address. That is, the third MAC address can be obtained by adding the preset value to the second MAC address. An example of the preset value is 1.

[0030] In combination with the first aspect or any one of the above possible implementations, in a fifth possible implementation, the time when the first device receives the first VSI message is earlier than the time when the first device receives the second VSI message; or the number of VSI messages received by the first device from the second device within a first preset time period is greater than the number of VSI messages received by the first device from the third device within the first preset time period; or the priority of the second device is higher than the priority of the third device; or the priority of the service corresponding to the first VSI message is greater than the priority of the service corresponding to the second VSI message; or the priority of the user of the second device is greater than the priority of the user of the third device.

[0031] That is to say, after the first device receives multiple VSI messages carrying the same MAC address, when it needs to carry the ciphertext information encrypted using the key of which device in the operation request message carrying the same MAC address, or when the first device determines which device to send the operation request message to using the same MAC address, the first device can determine it based on the order in which the first device receives the VSI messages sent by these devices, or based on the number of VSIs sent to the first device by these devices within a first preset time period, or based on the priority of the devices sending these VSI messages, or based on the priority of the services corresponding to the VSI messages sent by these devices, or based on the priority of the users of these devices.

[0032] Among them, the first device sends an operation request message carrying the same MAC address to the sending device of the VSI message that first arrives at the first device among the VSI messages with the same MAC address, or the first device uses the same MAC address to send an operation request message to the device that sends the most VSI messages within a first preset time period, or the first device uses the same MAC address to send an operation request message to a high-priority device, or the first device uses the same MAC address to send an operation request message to a device used by a high-priority user, or the first device uses the same MAC address to send an operation request message to a device requesting a high-priority service.

[0033] In combination with the first aspect or any one of the foregoing possible implementations, in a sixth possible implementation, an interval between a time when the first device receives the first VSI message and a time when the first device receives the second VSI message is less than or equal to a second preset duration.

[0034] That is, the first device executes the first aspect or any of the above possible implementations only when the second device and the third device use the same MAC address for the second preset time period. This can reasonably avoid the third device from repeatedly sending VSI messages, thereby saving computing resources and transmission resources of the third device.

[0035] In the first aspect or any of the above possible implementations, optionally, the key of each device may be carried in a ciphertext manner in the VSI message. For example, the second device and / or the third device may encrypt its own key using the public key of the first device, and then carry the key by carrying the encrypted ciphertext information in the VSI message.

[0036] In the second aspect, the present application provides a communication method, which includes: a second device sends a first vehicle service indication VSI message to a first device, the first VSI message carries a first media access control MAC address of the second device, a first key of the second device, and a first ciphertext information obtained by encrypting the first information of the second device using the first key; the second device receives an operation request message from the first device, the operation request message carries the first MAC address and second ciphertext information, and the second ciphertext information cannot be successfully decrypted by the first key; the second device sends a second VSI message to the first device, the second VSI message carries a second MAC address of the second device, a second key of the second device, and a third ciphertext information obtained by encrypting the first information using the second key, and the second MAC address is different from the first MAC address.

[0037] This communication method enables the first device to send only one operation request message (i.e., the first operation request message) carrying the same MAC address for multiple VSI messages carrying the same MAC address, without having to send an operation request message carrying the same MAC address for each of the multiple VSI messages. Therefore, when each of the multiple sending devices of the multiple VSI messages (including the second device) uses its own current MAC address to verify the MAC address in the received operation request message, only the MAC address in one operation request message will be successfully verified, while the MAC addresses in multiple operation request messages will not be successfully verified. Therefore, each of the multiple devices only needs to use its own key to decrypt the ciphertext information in one operation request message carrying the same MAC address, without having to use its own key to decode the ciphertext information in more operation request messages carrying the same MAC address, thereby ultimately avoiding waste of resources of the multiple devices.

[0038] In addition, in this communication method, because the second device cannot successfully decrypt the ciphertext information in the operation request message using its own first key, a second MAC address different from the first MAC address is used to resend the second VSI message to the first device, so that the first device can send the corresponding operation request message to the second device, thereby ensuring that the business of the second device can continue normally.

[0039] In the communication method, the first information may include any information that the second device wishes to send to the first device in a ciphertext manner.

[0040] In combination with the second aspect, in a first possible implementation method, the interval between the time when the second device sends the second VSI message to the first device and the time when the second device receives the operation request message is greater than or equal to a preset duration, and the second device does not receive an operation request message carrying the first MAC address and ciphertext information that can be successfully decrypted by the first key within the preset duration.

[0041] That is to say, when the second device receives an operation request message carrying its own MAC address, but cannot successfully decrypt the ciphertext information in the operation request message using its own key, the second device will not immediately resend the VSI message, but will send the second VSI message only after waiting for the first preset time length and the second device has not received an operation request message carrying its own MAC address and ciphertext information that can be successfully decrypted by its own key within the first preset time length.

[0042] This implementation method can avoid the second device from repeatedly sending VSI messages, thereby avoiding the waste of resources of the second device and improving the efficiency of the second device in receiving correct operation request messages. This is because the operation request message whose ciphertext information cannot be successfully decrypted may be a harassing operation request message or a tampered operation request message. The reasonable operation request message sent by the first device to the second device is likely to arrive at the second device after the harassing operation message or the tampered operation request message. In this case, the second device only needs to wait for a while longer to receive the required operation request message without resending the VSI message.

[0043] In combination with the second aspect or the first possible implementation manner, in a second possible implementation manner, the second MAC address is a reserved MAC address.

[0044] In combination with the second aspect or the first possible implementation manner, in a third possible implementation manner, the second MAC address is determined based on a preset rule and the second MAC address.

[0045] For example, the preset rule may include: adding a preset value to the first MAC address. That is, the second MAC address can be obtained by adding the preset value to the first MAC address. An example of the preset value is 1.

[0046] In combination with the second aspect or the first possible implementation manner, in a fourth possible implementation manner, the second MAC address may be randomly generated.

[0047] In the second aspect or any of the above possible implementations, optionally, the key of each device may be carried in a ciphertext manner in the VSI message. For example, the second device and / or the first device may encrypt their own keys using the public key of the first device, and then carry the key by carrying the encrypted ciphertext information in the VSI message.

[0048] In a third aspect, the present application provides a communication method, which includes: a second device sends a first vehicle service indication VSI message to a first device, the first VSI message carries a first media access control MAC address of the second device, a first key of the second device, and a first ciphertext information obtained by encrypting the first information of the second device using the first key; the second device receives a first operation request message from the first device, the first operation request message carries the first MAC address and second ciphertext information; the second device receives a second operation request message from the first device, the second operation request message carries a second MAC address and third ciphertext information, and the second MAC address is different from the first MAC address; the second device determines that the second ciphertext information cannot be successfully decrypted by the first key; the second device determines that the second MAC address meets a preset condition; the second device decrypts the third ciphertext information using the first key.

[0049] That is to say, after the second device sends a VSI message carrying its own first MAC address and ciphertext information encrypted using its own first key to the first device, upon receiving a first manipulation request message carrying the first MAC address and ciphertext information that cannot be successfully decrypted by the first key, the second device can use the first key to decrypt the ciphertext information in the second operation request message carrying the second MAC address.

[0050] This communication method enables the first device to send only one operation request message (i.e., the first operation request message) carrying the same MAC address for multiple VSI messages carrying the same MAC address, without having to send an operation request message carrying the same MAC address for each of the multiple VSI messages. Therefore, when each of the multiple sending devices of the multiple VSI messages (including the second device) uses its own current MAC address to verify the MAC address in the received operation request message, only the MAC address in one operation request message will be successfully verified, while the MAC addresses in multiple operation request messages will not be successfully verified. Therefore, each of the multiple devices only needs to use its own key to decrypt the ciphertext information in only one operation request message carrying the same MAC address, without having to use its own key to decode the ciphertext information in more operation request messages carrying the same MAC address, thereby ultimately avoiding waste of resources of the multiple devices.

[0051] In addition, the communication method enables the first device to send an operation request message to the second device using a second MAC address different from the conflicting first MAC address, thereby enabling the second device to continue to execute subsequent processes with less resource overhead.

[0052] In combination with the third aspect, in a first possible implementation manner, the preset condition includes: the second MAC address is a reserved MAC address.

[0053] In combination with the third aspect, in a second possible implementation manner, the preset condition includes: the second MAC address is determined based on a preset rule and the first MAC address.

[0054] For example, the preset rule may include: adding a preset value to the first MAC address. That is, the second MAC address can be obtained by adding the preset value to the first MAC address. An example of the preset value is 1.

[0055] In combination with the third aspect or any one of the above possible implementations, in a third possible implementation, the interval between the time when the second device uses the first key to decrypt the third ciphertext information and the time when the second device receives the first operation request message is greater than or equal to a first preset time length, and the second device does not receive an operation request message carrying the ciphertext information that is the same as the first MAC address and can be successfully decrypted by the first key within the first preset time length.

[0056] This implementation method can avoid wasting resources on the second device. This is because the first operation request message may be a harassing operation request message or a tampered operation request message, and the operation request message sent by the first device to the second device is likely to arrive at the second device after the first operation message. In this case, the second device only needs to wait for a while longer to receive the required operation request message, and does not need to receive the operation request message with the MAC address of the second MAC address, so there is no need to determine the second MAC address, thereby saving resources.

[0057] In combination with the third aspect or any one of the above possible implementations, in a fourth possible implementation, the method also includes: the second device determines that the third ciphertext information cannot be successfully decrypted by the first key; the second device sends a second VSI message to the first device, and the second VSI message carries the third MAC address of the second device, the second key of the second device, and the fourth ciphertext information obtained by encrypting the first information using the second key.

[0058] That is to say, when the second device cannot successfully use the first key to decrypt the first operation request message sent using the first MAC address, and cannot successfully use the first key to decrypt the second operation request message sent using the agreed second MAC address, the second device can use the agreed third MAC address to resend the VSI message to the first device to ensure the reasonable and normal operation of subsequent processes.

[0059] In this implementation, optionally, the first key and the second key may be the same or different. When the first key and the second key are the same, because the second device does not regenerate a new key, the complexity of the second device can be reduced and the computing resources of the third device can be saved.

[0060] In this implementation, optionally, a method for determining the third MAC address may be the same as or different from a method for determining the second MAC address.

[0061] An example in which the manner of determining the third MAC address is different from the manner of determining the second MAC address includes: the third MAC address may be randomly generated.

[0062] In combination with the fourth possible implementation, in a fifth possible implementation, the interval between the time when the second device sends the second VSI message and the time when the second device receives the second operation request message is greater than or equal to a second preset duration, and the second device does not receive an operation request message carrying the second MAC address and ciphertext information that can be successfully decrypted by the first key within the second preset duration.

[0063] This implementation can avoid the second device from repeatedly sending VSI messages, thereby avoiding the waste of resources of the second device and improving the efficiency of the second device in receiving the correct operation request message. This is because the second operation request message may be a harassing operation request message or a tampered operation request message, and the correct operation request message sent by the first device to the second device is likely to arrive at the second device after the second operation request message. In this case, the second device only needs to wait for a while longer to receive the required operation request message without resending the VSI message.

[0064] In the third aspect or any of the above possible implementations, optionally, the key of each device may be carried in a ciphertext manner in the VSI message. For example, the second device and / or the first device may encrypt their own keys using the public key of the first device, and then carry the key by carrying the encrypted ciphertext information in the VSI message.

[0065] In a fourth aspect, the present application provides a communication device, which is applied to a first device. The communication device may be, for example, the first device itself, or a hardware module, software module or chip in the first device, and the communication device includes one or more functional modules for implementing the communication method in the first aspect or any possible implementation method thereof.

[0066] As an example, the communication device includes a receiving module and a sending module.

[0067] The receiving module is used to receive a first vehicle service indication VSI message from a second device, where the first VSI message carries a first media access control MAC address of the second device, a first key of the second device, and first ciphertext information obtained by encrypting first information of the second device using the first key.

[0068] The receiving module is also used to receive the second VSI message from the third device, the second VSI message carries the second MAC address of the third device, the second key of the third device and the second ciphertext information obtained by encrypting the second information of the third device using the second key, and the first MAC address is the same as the second MAC address.

[0069] A sending module is used to send a first operation request message based on the first VSI message and the second VSI message, where the first operation request message carries the first MAC address and third ciphertext information obtained by encrypting third information using the first key.

[0070] In combination with the fourth aspect, in a first possible implementation manner, the sending module is specifically used to: not send an operation request message in response to the second VSI message, and send the first operation request message based on the first VSI message.

[0071] In combination with the fourth aspect, in a second possible implementation method, the sending module is also used to send a second operation request message based on the first VSI message and the second VSI message, the second operation request message carries a third MAC address and fourth ciphertext information obtained by encrypting the fourth information using the second key, and the third MAC address is different from the second MAC address.

[0072] In combination with the second possible implementation manner, in a third possible implementation manner, the third MAC address is a reserved MAC address.

[0073] In combination with the second possible implementation manner, in a fourth possible implementation manner, the third MAC address is determined based on a preset rule and the second MAC address.

[0074] In combination with the fourth aspect or any one of the foregoing possible implementations, in a fifth possible implementation, the time at which the first device receives the first VSI message is earlier than the time at which the first device receives the second VSI message; or the number of VSI messages received by the first device from the second device within a first preset time length is greater than the number of VSI messages received by the first device from the third device within the first preset time length; or

[0075] The priority of the second device is higher than the priority of the third device; or the priority of the service corresponding to the first VSI message is higher than the priority of the service corresponding to the second VSI message; or the priority of the user of the second device is higher than the priority of the user of the third device.

[0076] In combination with the fourth aspect or any one of the foregoing possible implementations, in a sixth possible implementation, an interval between a time when the first device receives the first VSI message and a time when the first device receives the second VSI message is less than or equal to a second preset duration.

[0077] In a fifth aspect, the present application provides a communication device, which is applied to a second device. The communication device may be, for example, the second device itself, or a hardware module, software module or chip in the second device, and the communication device includes one or more functional modules for implementing the communication method in the second aspect or any possible implementation method thereof.

[0078] As an example, the communication device includes a sending module and a receiving module.

[0079] The sending module is used to send a first vehicle service indication VSI message to the first device, where the first VSI message carries a first media access control MAC address of the second device, a first key of the second device, and first ciphertext information obtained by encrypting the first information of the second device using the first key,

[0080] The receiving module is used to receive an operation request message from the first device, where the operation request message carries the first MAC address and second ciphertext information, and the second ciphertext information cannot be successfully decrypted by the first key.

[0081] The sending module is also used to send a second VSI message to the first device, where the second VSI message carries a second MAC address of the second device, a second key of the second device, and third ciphertext information obtained by encrypting the first information using the second key, and the second MAC address is different from the first MAC address.

[0082] In combination with the fifth aspect, in a first possible implementation method, the interval between the time when the second device sends the second VSI message to the first device and the time when the second device receives the operation request message is greater than or equal to a preset duration, and the second device does not receive an operation request message carrying the first MAC address and ciphertext information that can be successfully decrypted by the first key within the preset duration.

[0083] In combination with the fifth aspect or the first possible implementation manner, in a second possible implementation manner, the second MAC address is a reserved MAC address.

[0084] In combination with the fifth aspect or the first possible implementation manner, in a second possible implementation manner, the second MAC address is determined based on a preset rule and the first MAC address.

[0085] In a sixth aspect, the present application provides a communication device, which is applied to a second device. The communication device may be, for example, the second device itself, or a hardware module, software module or chip in the second device, and the communication device includes one or more functional modules for implementing the communication method in the third aspect or any possible implementation method thereof.

[0086] As an example, the communication device includes a sending module, a receiving module and a processing module.

[0087] The sending module is used to send a first vehicle service indication VSI message to the first device, where the first VSI message carries the first media access control MAC address of the second device, the first key of the second device, and the first ciphertext information obtained by encrypting the first information of the second device using the first key.

[0088] The receiving module is used to receive a first operation request message from the first device, where the first operation request message carries the first MAC address and second ciphertext information.

[0089] The receiving module is further used to receive a second operation request message from the first device, where the second operation request message carries a second MAC address and third ciphertext information, and the second MAC address is different from the first MAC address.

[0090] The processing module is used to determine that the second ciphertext information cannot be successfully decrypted by the first key, determine that the second MAC address meets a preset condition; and use the first key to decrypt the third ciphertext information.

[0091] In combination with the sixth aspect, in a first possible implementation manner, the preset condition includes: the second MAC address is a reserved MAC address.

[0092] In combination with the sixth aspect, in a second possible implementation manner, the preset condition includes: the second MAC address is determined based on a preset rule and the first MAC address.

[0093] In combination with the sixth aspect or any one of the above possible implementations, in a third possible implementation, the interval between the time when the second device uses the first key to decrypt the third ciphertext information and the time when the second device receives the first operation request message is greater than or equal to a first preset time length, and the second device does not receive an operation request message carrying the first MAC address and ciphertext information that can be successfully decrypted by the first key within the first preset time length.

[0094] In combination with the sixth aspect or any one of the above possible implementation methods, in a fourth possible implementation method, the processing module is further used to: determine that the third ciphertext information cannot be successfully decrypted by the first key.

[0095] Correspondingly, the sending module is further used to send a second VSI message to the first device, where the second VSI message carries the third MAC address of the second device, the second key of the second device, and fourth ciphertext information obtained by encrypting the second information using the second key.

[0096] In combination with the fourth possible implementation, in a fifth possible implementation, the interval between the time when the second device sends the second VSI message and the time when the second device receives the second operation request message is greater than or equal to a second preset duration, and the second device does not receive an operation request message carrying the second MAC address and ciphertext information that can be successfully decrypted by the first key within the second preset duration.

[0097] In each of the above aspects or any possible implementation, as an example, the first device, the second device or the third device may be an RSU, a chip in the RSU, or a roadside device including an RSU, or may be an OBU, a chip in the OBU, or a vehicle including an OBU, or may also be other devices or chips supporting V2X communication.

[0098] In a seventh aspect, the present application provides a communication device, comprising a processor coupled to a memory, the memory being used to store program instructions, and the processor being used to call the program instructions in the memory to implement the communication method in the first aspect or any possible implementation method thereof.

[0099] Optionally, the communication device may further include the memory.

[0100] Optionally, the communication device may further include an interface circuit, and the interface circuit may include a transceiver or an input-output interface.

[0101] In an eighth aspect, the present application provides a communication device, comprising a processor coupled to a memory, the memory being used to store program instructions, and the processor being used to call the program instructions in the memory to implement the communication method in the second aspect or any possible implementation method thereof.

[0102] Optionally, the communication device may further include the memory.

[0103] Optionally, the communication device may further include an interface circuit, and the interface circuit may include a transceiver or an input-output interface.

[0104] In a ninth aspect, the present application provides a communication device, comprising a processor coupled to a memory, the memory being used to store program instructions, and the processor being used to call the program instructions in the memory to implement the communication method in the third aspect or any possible implementation method thereof.

[0105] Optionally, the communication device may further include the memory.

[0106] Optionally, the communication device may further include an interface circuit, and the interface circuit may include a transceiver or an input-output interface.

[0107] In a tenth aspect, the present application provides a computer-readable storage medium, wherein the computer-readable storage medium stores program instructions, which, when executed on a processor, implement the communication method in the first aspect or any possible implementation method thereof.

[0108] In an eleventh aspect, the present application provides a computer-readable storage medium, wherein the computer-readable storage medium stores program instructions, which, when executed on a processor, implement instructions for the communication method in the second aspect or any possible implementation thereof.

[0109] In a twelfth aspect, the present application provides a computer-readable storage medium, wherein the computer-readable storage medium stores program instructions, which, when executed on a processor, implement instructions for the communication method in the third aspect or any possible implementation method thereof.

[0110] In a thirteenth aspect, the present application provides a computer program product comprising instructions, wherein the computer program product comprises program instructions, and when the program instructions are executed on a processor, the communication method in the first aspect or any possible implementation method thereof is implemented.

[0111] In a fourteenth aspect, the present application provides a computer program product comprising instructions, wherein the computer program product comprises program instructions, and when the program instructions are executed on a processor, the communication method in the second aspect or any possible implementation method thereof is implemented.

[0112] In a fifteenth aspect, the present application provides a computer program product comprising instructions, wherein the computer program product comprises program instructions, and when the program instructions are executed on a processor, the communication method in the third aspect or any possible implementation method thereof is implemented.

[0113] In a sixteenth aspect, the present application provides a vehicle, comprising the communication device of the fifth aspect, the sixth aspect, the eighth aspect or the ninth aspect or any one of the implementations thereof. BRIEF DESCRIPTION OF THE DRAWINGS

[0114] Figure 1 An exemplary architecture diagram of a communication system applicable to embodiments of the present application;

[0115] Figure 2 Schematic diagram of the main stages of near-field payment based on LTE-V2X;

[0116] Figure 3 An exemplary flow chart of an existing communication method;

[0117] Figure 4 This is an exemplary flow chart of a communication method according to the first embodiment of the present application;

[0118] Figure 5 This is an exemplary flow chart of a communication method according to a second embodiment of the present application;

[0119] Figure 6 This is an exemplary flow chart of a communication method according to a third embodiment of the present application;

[0120] Figure 7 This is an exemplary flow chart of a communication method according to a fourth embodiment of the present application;

[0121] Figure 8 This is an exemplary structural diagram of a communication device according to a first embodiment of the present application;

[0122] Fig. 9 This is an exemplary structural diagram of a communication device according to the second embodiment of the present application. DETAILED DESCRIPTION

[0123] The technical solutions in the embodiments of the present application will be described below in conjunction with the drawings in the embodiments of the present application.

[0124] In order to facilitate the clear description of the technical solutions of the embodiments of the present application, in the embodiments of the present application, the words "first" and "second" are used to distinguish the same items or similar items with substantially the same functions and effects. For example, the first information and the second information are only used to distinguish different information, and their order is not limited. Those skilled in the art can understand that the words "first" and "second" do not limit the quantity and execution order, and the words "first" and "second" do not necessarily limit them to be different.

[0125] In the embodiments of the present application, "multiple" refers to two or more. "And / or" describes the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone, where A and B can be singular or plural. The character " / " generally indicates that the previous and next associated objects are in an "or" relationship. "At least one of the following" or similar expressions refers to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can represent: a, b, c; a and b; a and c; b and c; or a and b and c. Among them, a, b, c can be single or multiple.

[0126] To facilitate understanding of the communication method provided in the embodiment of the present application, the application scenario of the communication method provided in the embodiment of the present application is described below. It is understandable that the application scenario described in the embodiment of the present application is to more clearly illustrate the technical solution of the embodiment of the present application, and does not constitute a limitation on the technical solution provided in the embodiment of the present application.

[0127] Figure 1 Schematic diagram of several exemplary application scenarios applicable to the communication method of the embodiment of the present application. It can be understood that, Figure 1 The application scenarios shown are only examples, and the communication method of the embodiments of the present application is applicable to any vehicle-to-everything (V2X) communication system.

[0128] like Figure 1 As shown in (a), the application scenario includes RSU and N OBUs, which are respectively denoted as OBU1, OBU2 to OBU N, where N is a positive integer.

[0129] RSU is generally installed on the roadside and uses dedicated short range communication (DSRC) technology to communicate with OBU.

[0130] OBU is usually installed on vehicles. When the vehicle passes through RSU, OBU and RSU communicate via microwaves to facilitate vehicle identification and / or electronic fee deduction without stopping the vehicle, or to achieve card-free or even non-stop vehicle passage.

[0131] For example, in a toll collection scenario on a highway, the RSU may be a toll station deployed on the roadside, and the OBU may be a device deployed on a vehicle. When the vehicle passes the RSU on the way, the communication method of the embodiment of the present application is executed to realize the function of collecting the vehicle's transportation fee without stopping the vehicle.

[0132] For another example, in a parking lot charging scenario, the RSU may be a charging station deployed in the parking lot, and the OBU may be deployed on the vehicle. When the vehicle is parked in the parking lot, the communication method of the embodiment of the present application is executed to realize the function of collecting the parking fee of the vehicle without stopping.

[0133] For example, in a city, the RSU can be a toll station deployed on the side of a designated road, and the OBU can be deployed on a vehicle. When the vehicle passes through these designated roads, the communication method of the embodiment of the present application is executed, and the traffic congestion fee for the vehicle passing through the designated road can be collected without stopping.

[0134] like Figure 1As shown in (b), the application scenario includes M OBUs, which are respectively denoted as OBU 1, OBU 2 to OBUM, and M is an integer greater than 1.

[0135] The OBU 1 can communicate with other OBUs by using DSRC technology. The OBU 1 can be installed on a vehicle, and the vehicle can be moved to any location where a charging or identification OBU needs to be deployed to serve as a charging station.

[0136] Other OBUs passing through OBU 1 communicate with OBU 1 via microwaves, so that the vehicles where these OBUs are located can realize vehicle identity recognition and / or electronic fee deduction functions without stopping, or can realize vehicle passage without card collection or even stopping.

[0137] For example, in a toll collection scenario on a highway, OBU 1 can be deployed on a vehicle to act as a mobile toll collection station. When other vehicles with OBU deployed pass through OBU 1, the communication method of the embodiment of the present application is executed to realize the function of collecting the traffic fee of the other vehicles without stopping.

[0138] For example, in a parking lot charging scenario, OBU 1 can be deployed on a vehicle to act as a mobile charging station. When other vehicles with OBUs deployed pass through OBU 1, the communication method of the embodiment of the present application is executed to realize the function of collecting parking fees from the vehicle without stopping.

[0139] For another example, in a city, OBU 1 can be deployed on a vehicle to serve as a mobile toll station. When other vehicles with OBU deployed pass through OBU 1, the communication method of the embodiment of the present application can be executed to collect traffic congestion fees for vehicles passing through the designated road without stopping.

[0140] Figure 1 (a) and Figure 1 In (b), the RSU or OBU serving as a toll station may be collectively referred to as a toll collection device, and the OBU interacting with the toll station may be referred to as a payment device.

[0141] The following takes the charging device as RSU and the payment device as OBU as an example to introduce the process of implementing payment services between the charging device and the payment device.

[0142] Figure 2 Figure 1 is a schematic diagram of the main stages of near-field payment based on the long term evolution (LTE)-V2X system. Figure 2As shown, the payment service between RSU and OBU can generally include four stages, which are as follows: Stage 1, unicast communication link establishment and charging information acquisition stage; Stage 2, pass credential acquisition stage; Stage 3, user prompt stage; Stage 4, link release stage.

[0143] During the unicast communication link establishment and charging information acquisition phase, the RSU and OBU can establish a unicast connection, determine the charging service type, exchange transaction information and exchange site information, etc.

[0144] During the pass credential acquisition phase, the RSU and OBU can exchange charging transaction credentials.

[0145] During the user prompt stage, the RSU can send the transaction result to the OBU, and the OBU can output a prompt message for exiting the toll site.

[0146] In the link release phase, the RSU and OBU can disconnect the link and release resources.

[0147] It can be understood that in the embodiment of the present application, the process of implementing the payment service between the RSU and the OBU may include fewer, more or replaceable stages.

[0148] like Figure 3 As shown, the unicast communication link establishment and charging information acquisition phase may include steps S301 to S307.

[0149] S301, RSU broadcasts a RST message.

[0150] As an example, the RSU may include announcement information of the near-field payment service, and the announcement information may include one or more of payment node information, charging type, charging information, and the like.

[0151] As an example, the payment node information may be used to indicate relevant information when the RSU serves as a charging station. For example, the payment node information may be used to indicate information such as a communication method and / or a payment method supported by the RSU.

[0152] As an example, the charging type may include one or more of the following charging types: highway charging, parking charging, or traffic congestion charging.

[0153] As an example, the charging information may be used to indicate the charging standard. For example, for a charging type such as a highway charging, the charging standard includes how much is charged for how many kilometers; for another charging type such as a parking charging, the charging standard includes how much is charged for how many hours.

[0154] Optionally, the RST message may also include an application identifier (AID) for implementing a near field payment service.

[0155] Optionally, the RST message may be signed using the private key of the RSU's certificate.

[0156] Optionally, in addition to sending the RST message, the RSU may also send a certificate of the RSU, which includes a public key.

[0157] S302, the OBU that receives the RST message generates a VSI message, the VSI message carries the MAC address of the OBU, the key of the OBU, and ciphertext information obtained by encrypting the information to be encrypted using the key of the OBU.

[0158] As an example, after receiving the RST message, the OBU may determine whether to initiate a response message of the RST message to the RSU according to the content of the RST message, for example, according to information such as the AID.

[0159] The OBU generating the VSI message may include: the OBU generating a MAC address and a key, using the key to encrypt the OBU information to be encrypted to obtain ciphertext information, and generating a VSI message carrying the MAC address and the ciphertext information.

[0160] The information to be encrypted of the OBU may include any information that the OBU wishes to transmit to the charging device in a ciphertext manner. For example, the information to be encrypted of the OBU may include one or more of the following information: the contract serial number of the OBU, the information of the vehicle to which the OBU belongs, and the passing station information.

[0161] The information of the vehicle to which the OBU belongs may include information on the type of the vehicle, such as whether the vehicle is a car with less than 7 seats or a truck.

[0162] In a toll collection scenario such as a highway, as an example, the stop-over information of the vehicle to which the OBU belongs may include the entrance of the vehicle into the highway and / or the exit of the highway company.

[0163] In a charging scenario such as a parking lot, as an example, the transit information of the vehicle to which the OBU belongs may include the time when the vehicle enters the parking lot and / or the time when the vehicle exits the parking lot.

[0164] Optionally, the information to be encrypted of the OBU may be carried in an application layer message. In this case, the OBU encrypting the information to be encrypted using a key may be understood as the OBU encrypting the application layer message using a key.

[0165] Optionally, in order to improve the transmission security of the OBU's key, the OBU can encrypt its own key. For example, when the RST message includes the RSU's certificate, the OBU can encrypt its own key using the public key in the RSU's certificate. In this implementation, the VSI message carrying the OBU's key may include: the VSI message carrying the OBU's encrypted key.

[0166] S303, the OBU sends a VSI message, and the RSU receives the VSI message accordingly.

[0167] S304, the RSU uses the OBU key in the VSI message to decrypt the ciphertext information in the VSI message to obtain plaintext information.

[0168] Optionally, the OBU key in the VSI message can carry ciphertext information encrypted using the public key of the RSU's certificate. In this case, the RSU can first decrypt the key ciphertext using the key of its own certificate to obtain the OBU key, and then use the OBU key to decrypt the ciphertext information in the VSI message.

[0169] S305, the RSU sends an operation request message to the OBU, the operation request message carries the MAC address of the OBU, the key of the OBU, and ciphertext information obtained by encrypting the information to be encrypted of the RSU using the key of the OBU.

[0170] The information to be encrypted of the RSU may include any information that the RSU wishes to transmit to the OBU in a ciphertext manner. For example, the information to be encrypted of the RSU may include one or more information such as transaction records and station passing information.

[0171] Optionally, the information to be encrypted of the RSU may be carried in an application layer message. In this case, the encryption of the information to be encrypted by the RSU may be understood as the encryption of the application layer message by the RSU.

[0172] Optionally, the RSU can also use its own private key to sign the MAC address and ciphertext information of the OBU to obtain signature information. In this case, the operation request message also carries the signature information.

[0173] S306, the OBU receiving the operation request message determines whether to send an operation response message in response to the operation request message. If the OBU determines that an operation response message should be sent in response to the operation request message, S307 is executed, otherwise the operation request message is ignored.

[0174] As an example, the OBU determines whether to send an operation response message in response to the operation request message, including: the OBU verifies the MAC address in the operation request message; when the MAC address verification is successful, the OBU uses its own key to decrypt the ciphertext information; if the decryption is successful, the OBU can send an operation response message in response to the operation request message. Wherein, when the MAC address verification fails and the decryption fails, the OBU can ignore the operation request message.

[0175] The OBU verifies the MAC address in the operation request message including: the OBU determines whether the MAC address carried in the operation request message is the same as its own MAC address. If they are the same, it can be determined that the MAC address verification is successful, otherwise it can be determined that the MAC address verification fails.

[0176] When the OBU uses its own key to decrypt the ciphertext information, if the decrypted information is garbled or data that the OBU cannot recognize, it can be determined that the decryption has failed; if the decrypted information is information that the OBU can recognize, it can be determined that the decryption is successful.

[0177] Optionally, if the operation request message carries signature information, the OBU can use the public key of the RSU to verify the signature of the operation request message before performing MAC address verification. If the signature verification succeeds, the MAC address carried in the operation request message will continue to be verified; if the signature verification fails, the operation request message will be discarded.

[0178] S307, the OBU sends an operation response message.

[0179] As an example, the operation response message carries the MAC address of the OBU and the ciphertext information obtained by encrypting the information to be encrypted using the key of the OBU. The information to be encrypted here may include information such as transaction vouchers or payment accounts.

[0180] It is understandable that the steps between the RSU and the OBU may include fewer, more or other replaceable steps.

[0181] When the RSU and OBU are used Figure 3When interacting with the RSU according to the process shown in the figure, the following phenomenon will occur: in the same period, multiple OBUs will send VSI messages to the RSU, and the MAC addresses of these multiple OBUs are the same, that is, the MAC addresses of these multiple OBUs conflict. This will cause the following problem: each of the multiple OBUs using the same MAC address can successfully verify the MAC address in multiple operation request messages, and thus use its own key to decrypt the ciphertext information in these multiple operation request messages, but in fact each OBU can only successfully decrypt the ciphertext information in one of the operation request messages to obtain the corresponding information. This interaction method will waste the resources of the OBU using its own key to decrypt the ciphertext information.

[0182] In view of the above problems, the present application proposes a new communication method. The following still takes the payment device as OBU and the charging device as RSU as an example to introduce the communication method proposed in the present application. Figure 4 shown.

[0183] S401, RSU broadcasts a RST message.

[0184] This step may refer to S301 and will not be described in detail here.

[0185] S402, the OBU that receives the RST message generates a VSI message, the VSI message carries the MAC address of the OBU, the key of the OBU, and ciphertext information obtained by encrypting the information to be encrypted using the key of the OBU.

[0186] This step may refer to S302 and will not be described in detail here.

[0187] S403, the OBU sends a VSI message, and the RSU receives the VSI message accordingly.

[0188] S404, the RSU uses the key in the VSI message to decrypt the ciphertext information in the VSI message. This step can refer to S304 and will not be described in detail here.

[0189] S405, the RSU determines whether the MAC address in the VSI message conflicts with the MAC address in other VSI messages, and determines whether to send a corresponding operation request message in response to the VSI message according to the determination result.

[0190] In an example in which the RSU determines whether the MAC address in the VSI message conflicts with the MAC address in other VSI messages, the RSU determines whether the MAC address in the VSI message is the same as the MAC address in other VSI messages. If so, it determines whether the MAC address in the VSI message conflicts with the MAC address in other VSI messages. Otherwise, it determines whether the MAC address in the VSI message does not conflict with the MAC address in other VSI messages.

[0191] Sending a corresponding operation request message in response to the VSI message includes: sending operation information carrying the MAC address in the VSI message and ciphertext information obtained by encrypting the to-be-encrypted information of the RSU using the key in the VSI message.

[0192] As an example, after receiving the VSI message, the RSU obtains the MAC address in the VSI message, and determines whether a VSI message carrying the MAC address has been received within a preset time period before receiving the VSI message. If the RSU has received a VSI message carrying the MAC address within a preset time period before receiving the VSI message, the RSU determines not to respond to the VSI message, that is, not to send an operation request message corresponding to the VSI message. If the RSU has not received a VSI message carrying the MAC address within a preset time period before receiving the VSI message, the RSU determines to respond to the VSI message, that is, to send an operation request message corresponding to the VSI message.

[0193] As another example, the RSU receives multiple VSI messages within a preset time period, and selects an appropriate VSI message from the multiple VSI messages received within the preset time period to respond. The following introduces several implementations of the RSU selecting an appropriate VSI message from the multiple VSI messages.

[0194] In a first implementation, the RSU may determine which VSI message is a suitable VSI message based on the order of the reception times of the multiple VSI messages. For example, the RSU may select a VSI message with an earlier reception time as a suitable VSI message.

[0195] In a second implementation, the RSU may select a suitable VSI message based on the number of VSI messages sent by the multiple OBUs corresponding to the multiple VSI messages within the same preset duration. For example, the RSU may select a VSI message of an OBU that sends more VSI messages within the same preset duration as a suitable VSI message.

[0196] In a third implementation, the RSU may select a suitable VSI message based on the priority of the OBU. For example, the RSU may select a VSI message sent by an OBU with a higher priority as a suitable VSI message.

[0197] In a fourth implementation, the RSU may select a suitable VSI message based on the service priority. For example, the RSU may select a VSI message with a high service priority as a suitable VSI message.

[0198] In a fifth implementation, the RSU may select a suitable VSI message based on the user priority. For example, the RSU may select a VSI message sent by an OBU with a high user priority as a suitable VSI message.

[0199] S406, the RSU sends an operation request message, which carries the MAC address in the corresponding VSI message and ciphertext information obtained by encrypting the RSU's information to be encrypted using the key in the corresponding VSI message. Correspondingly, the OBU receives the operation request message.

[0200] This step may refer to S305 and will not be described in detail here.

[0201] S407, when the MAC address in the operation request message is successfully verified and the ciphertext information in the operation request message cannot be successfully decrypted by the key of the OBU, the OBU executes S408.

[0202] As an example, when the MAC address in the OBU operation request message is successfully verified and the ciphertext information in the operation request message cannot be successfully decrypted by the key of the OBU, the OBU can wait for a preset duration, and only execute S408 if no operation request message in which the MAC address can be successfully verified and the ciphertext information can be successfully decrypted by the key of the OBU is received within the preset duration. Because the currently received operation request message may be one in which the MAC address has been tampered with, and the operation request message corresponding to the OBU may then arrive at the OBU. Such an implementation can improve the reliability of the OBU successfully receiving the corresponding operation request message and avoid waste of resources.

[0203] Optionally, when the MAC address in the operation request message is successfully verified and the ciphertext information in the operation request message is successfully decrypted by the key of the OBU, the OBU executes S409.

[0204] Optionally, when the MAC address verification in the operation request message fails, the OBU executes S408.

[0205] As an example, when the MAC address in the OBU operation request message fails to be verified, the OBU can wait for a preset duration, and only execute S408 if no operation request message whose MAC address can be successfully verified and whose ciphertext information can be successfully decrypted by the key of the OBU is received within the preset duration. Because the currently received operation request message may have a MAC address that has been tampered with, and the operation request message corresponding to the OBU may then arrive at the OBU. Such an implementation can improve the reliability of the OBU successfully receiving the corresponding operation request message and avoid waste of resources.

[0206] Optionally, when the OBU fails to verify the signature information of the operation request message using the certificate public key of the RSU, the OBU executes S408.

[0207] As an example, when the signature information verification of the OBU operation request message fails, the OBU can wait for a preset time length, and only execute S408 if no operation request message whose MAC address can be successfully verified and whose ciphertext information can be successfully decrypted by the key of the OBU is received within the preset time length. Because the currently received operation request message may have a MAC address that has been tampered with, and the operation request message corresponding to the OBU may then arrive at the OBU. Such an implementation method can improve the reliability of the OBU successfully receiving the corresponding operation request message and avoid waste of resources.

[0208] S408, the OBU resends the VSI message, and the MAC address carried in the resent VSI message is different from the MAC address in the previously sent VSI message.

[0209] This step can be performed as in S402 , except that the new MAC address carried in the VSI message in S408 is different from the original MAC address carried in the VSI message in S402 .

[0210] The new MAC address may be a reserved MAC address, or may be a MAC address determined by the OBU based on the original MAC address and a preset rule.

[0211] As an example, the OBU may add a preset value to the original MAC address to obtain a new MAC address. For example, the preset value may be 1.

[0212] Optionally, the key used for encryption by OBU in this step may be the same as or different from the key used for encryption in S402. In the case of being the same, the complexity of OBU can be reduced. In the case of being different, security can be improved.

[0213] S409, the OBU sends an operation response message according to the operation request message. This step can refer to S307 and will not be described in detail here.

[0214] The following example takes the conflict between the MAC address of the first OBU and the MAC address of the second OBU as an example. Figure 5 Further details Figure 4 The communication method shown.

[0215] S501, RSU broadcasts a RST message. The OBUs that receive the RST message include a first OBU and a second OBU.

[0216] S502a, the first OBU generates a first VSI message, where the first VSI message carries a first MAC address and first ciphertext information obtained by encrypting first information using a first key.

[0217] This step may refer to S302 and will not be described in detail here.

[0218] S503a, the first OBU sends a first VSI message. Correspondingly, the RSU receives the first VSI message.

[0219] S504a: The RSU decrypts the first ciphertext information using the first key in the first VSI message.

[0220] This step may refer to S304 and will not be described in detail here.

[0221] S502b: The second OBU generates a second VSI message, where the second VSI message carries the second MAC address and second ciphertext information obtained by encrypting the second information using the second key.

[0222] This step may refer to S302 and will not be described in detail here.

[0223] S503b, the second OBU sends a second VSI message. Correspondingly, the RSU receives the first VSI message.

[0224] S504b: The RSU decrypts the second ciphertext information using the second key in the second VSI message.

[0225] This step may refer to S304 and will not be described in detail here.

[0226] It can be understood that the fact that S502b, S503b and S504b are located after S502a, S503a and S504a is only an example, and the present application does not limit the sequence of S502b, S503b and S504b and S502a, S503a and S504a.

[0227] S505, the RSU determines to respond to the first VSI message, and determines not to respond to the second VSI message. The RSU determines to respond to the first VSI message can be understood as sending a first operation request message corresponding to the first VSI message, and not responding to the second VSI message can be understood as not sending a second operation request message corresponding to the second VSI message. This step can refer to S405.

[0228] As an example, after receiving the first VSI message and the second VSI message within a first preset time period, the RSU determines whether the MAC addresses in the first VSI message and the second VSI message are the same. An example of the first preset time period is tens of milliseconds.

[0229] The RSU receives the first VSI message and the second VSI message within the first preset time period, which can be understood as: the time interval between the time when the RSU receives the first VSI message and the time when the RSU receives the second VSI message is less than or equal to the first preset time period

[0230] In this embodiment, the time when the RSU receives the first VSI message is earlier than the time when the RSU receives the second VSI message; or the number of VSI messages received by the RSU from the first OBU within the first preset time is greater than the number of VSI messages received by the RSU from the second OBU within the first preset time; or the priority of the first OBU is higher than the priority of the second OBU; or the priority of the service corresponding to the first VSI message is greater than the priority of the service corresponding to the second VSI message; or the priority of the user of the first OBU is greater than the priority of the user of the second OBU. Therefore, the RSU decides to respond to the first VSI message and not to respond to the second VSI message, that is, the RSU determines to send the first operation request message and determines not to send the second operation request message, the first operation request message carries the first MAC address and the ciphertext information encrypted using the first key of the first OBU, and the second operation request message carries the second MAC address and the ciphertext information encrypted using the second key of the second OBU.

[0231] S506, the RSU broadcasts a first operation request message, the first operation request message carrying the first MAC address and third ciphertext information obtained by encrypting third information using the first key. The first OBU and the second OBU receive the first operation request message.

[0232] S507a: The first OBU sends a first operation response message based on the first operation request message.

[0233] Specifically, the first OBU determines whether the MAC address carried in the first operation request message is the same as its own first MAC address. Because the MAC address carried in the first operation request message is the same as its own first MAC address, the first OBU continues to use its own first key to decrypt the third ciphertext information in the first operation request message.

[0234] Because the third ciphertext information in the first operation request message is the ciphertext information encrypted by the RSU using the first key, the first OBU can decrypt it successfully, thereby sending the first operation response message.

[0235] For the content related to the first OBU sending the first operation response message, please refer to S307, which will not be described in detail here.

[0236] S507b, the second OBU sends a second VSI message based on the first operation request message, the second VSI message carries a third MAC address and fourth ciphertext information obtained by encrypting the second information using a third key, and the third MAC address is different from the second MAC address.

[0237] Specifically, the second OBU determines whether the MAC address carried in the first operation request message is the same as its second MAC address. Because the MAC address carried in the first operation request message is the same as its second MAC address, the first OBU continues to use its first key to decrypt the third ciphertext information in the first operation request message.

[0238] Because the third ciphertext information in the first operation request message is encrypted by the RSU using the first key, the second OBU fails to decrypt, and thus sends the second VSI message.

[0239] The third MAC address may be a reserved MAC address, or may be a MAC address determined by the OBU based on the second MAC address and a preset rule.

[0240] As an example, the OBU may add a preset value to the second MAC address to obtain a third MAC address. For example, the preset value may be 1.

[0241] Optionally, when the MAC address in the first operation request message is successfully verified and the third ciphertext information in the first operation request message cannot be successfully decrypted by the second key, the second OBU can wait for a preset time length, and only send the second VSI if no operation request message in which the MAC address can be successfully verified and the ciphertext information can be successfully decrypted by the second key is received within the preset time length. Such an implementation can improve the reliability of the second OBU successfully receiving the second operation request message and avoid waste of resources.

[0242] Figure 6FIG. 1 is an exemplary flow chart of a communication method according to another embodiment of the present application. Figure 6 As shown, the method includes S601 to S609.

[0243] S601, RSU broadcasts a RST message.

[0244] This step may refer to S301 and will not be described in detail here.

[0245] S602, the OBU that receives the RST message generates a VSI message, the VSI message carries the MAC address of the OBU, the key of the OBU, and ciphertext information obtained by encrypting the information to be encrypted using the key of the OBU.

[0246] This step may refer to S302 and will not be described in detail here.

[0247] S603, the OBU sends a VSI message, and the RSU receives the VSI message accordingly.

[0248] S604, the RSU uses the key in the VSI message to decrypt the ciphertext information in the VSI message. This step can refer to S304 and will not be described in detail here.

[0249] S605, the RSU determines whether the MAC address in the VSI message conflicts with the MAC address in other VSI messages, and determines whether to send the first operation request message or the second operation request message in response to the VSI message according to the determination result. If it is determined to send the first operation request message in response to the VSI message, execute S606a; if it is determined to send the second operation request message in response to the VSI message, execute S606b.

[0250] The first operation request message carries the MAC address in the VSI message and key information encrypted using the key in the VSI message. The second operation request message carries the new MAC address and ciphertext information encrypted using the key in the VSI message.

[0251] In this embodiment, the first operation request message may be referred to as the operation request message corresponding to the VSI message. The implementation of the RSU determining whether to send the corresponding operation request message in response to the VSI message may refer to the relevant content in S405, which will not be repeated here.

[0252] S606a, the RSU sends a first operation request message, the first operation request message carries the MAC address in the corresponding VSI message and ciphertext information obtained by encrypting the RSU's information to be encrypted using the key in the corresponding VSI message. Correspondingly, the OBU receives the first operation request message.

[0253] This step may refer to S305 and will not be described in detail here.

[0254] S606b, the RSU sends a second operation request message, the second operation request message carries a new MAC address and ciphertext information encrypted using the key in the VSI message. The new MAC address here refers to a MAC address different from the MAC address in the VSI message.

[0255] Optionally, the new MAC address may be a reserved MAC address, or may be a MAC address determined by the RSU based on the original MAC address and a preset rule.

[0256] As an example, the RSU may add a preset value to the original MAC address to obtain a new MAC address. For example, the preset value may be 1.

[0257] S607, when the MAC address in the operation request message is successfully verified and the ciphertext information in the operation request message cannot be successfully decrypted by the key of the OBU, the OBU executes S608. This step can refer to the relevant content in S407, which will not be repeated here.

[0258] For example, if the OBU is an OBU other than the OBU corresponding to the first operation request message, the OBU executes S608.

[0259] As an example, when the MAC address in the operation request message is successfully verified and the ciphertext information in the operation request message cannot be successfully decrypted by the key of the OBU, the OBU can wait for a preset time length, and only execute S608 if no operation request message whose MAC address can be successfully verified and the ciphertext information can be successfully decrypted by the key of the OBU is received within the preset time length. Because the currently received operation request message may have a MAC address tampered with, and the operation request message corresponding to the OBU may arrive at the OBU later.

[0260] Optionally, when the MAC address in the operation request message is successfully verified and the ciphertext information in the operation request message is successfully decrypted by the key of the OBU, the OBU executes S609.

[0261] For example, if the OBU is the OBU corresponding to the first operation request message, the OBU executes S609.

[0262] Optionally, when the MAC address in the operation request message fails to be verified, the OBU executes S610. The content can refer to the relevant content in S407, which will not be repeated here.

[0263] Optionally, when the OBU fails to verify the signature information of the operation request message using the certificate public key of the RSU, the OBU executes S610. The content can refer to the relevant content in S407, which will not be repeated here.

[0264] S608, the OBU uses the new MAC address to verify the MAC address in the received operation request message, and if the MAC address verification is successful, uses the key to decrypt the ciphertext information in the operation request message.

[0265] As an example, the OBU may use the reserved MAC address to verify the MAC address in the received operation request message.

[0266] As another example, the OBU may determine a new MAC address based on a preset rule and the MAC address used by the OBU in S602, and use the new MAC address to verify the MAC address in the received operation request message.

[0267] The OBU may add a preset value to the MAC address used in S602 to obtain a new MAC address. An example of the preset value is 1.

[0268] In this step, if the OBU successfully decrypts the ciphertext information in the operation request message using its own key, the OBU can execute S609; if the OBU fails to decrypt the ciphertext information in the operation request message using its own key, the OBU can execute S610.

[0269] For example, when the OBU is the OBU that sends the VSI message corresponding to the second operation request message, the OBU successfully decrypts the ciphertext information in the second operation request message using its own key, and thus S609 can be executed.

[0270] As an example, when the MAC address in the OBU operation request message is successfully verified and the ciphertext information in the operation request message cannot be successfully decrypted by the key of the OBU, the OBU can wait for a preset time length, and only execute S610 if no operation request message whose MAC address can be successfully verified and the ciphertext information can be successfully decrypted by the key of the OBU is received within the preset time length. Because the currently received operation request message may have a MAC address tampered with, and the operation request message corresponding to the OBU may arrive at the OBU later.

[0271] In this step, optionally, when the MAC address verification in the operation request message fails, the OBU executes S610.

[0272] As an example, when the MAC address in the OBU operation request message fails to be verified, the OBU can wait for a preset duration, and only execute S610 if no operation request message whose MAC address can be successfully verified and whose ciphertext information can be successfully decrypted by the key of the OBU is received within the preset duration. Because the currently received operation request message may have a MAC address that has been tampered with, and the operation request message corresponding to the OBU may then arrive at the OBU. Such an implementation can improve the reliability of the OBU successfully receiving the corresponding operation request message and avoid waste of resources.

[0273] It can be understood that in this embodiment, the OBU can store all operation request messages received within a preset time length. As long as the OBU successfully decodes the MAC address of any operation request message using its original MAC address, but cannot successfully decode the ciphertext information in the operation message using its own key, the OBU can use the new MAC address to perform MAC address verification on other stored operation request messages or newly received operation request messages.

[0274] S609, the OBU sends an operation response message according to the operation request message. This step can refer to S307 and will not be described in detail here.

[0275] S610, the OBU resends the VSI message, and the MAC address carried in the resent VSI message is different from the MAC address in the previously sent VSI message. This step can be operated in S408, which will not be described in detail here.

[0276] Understandably, Figure 6 The communication method shown may include more, fewer or replaceable steps. For example, the communication method of this embodiment may not include S610.

[0277] The following example takes the conflict between the MAC address of the first OBU and the MAC address of the second OBU as an example. Figure 7 Further details Figure 6 The communication method shown.

[0278] S701, RSU broadcasts a RST message. The OBUs that receive the RST message include a first OBU and a second OBU.

[0279] S702a, the first OBU generates a first VSI message, where the first VSI message carries a first MAC address and first ciphertext information obtained by encrypting first information using a first key.

[0280] This step may refer to S302 and will not be described in detail here.

[0281] S703a, the first OBU sends a first VSI message. Correspondingly, the RSU receives the first VSI message.

[0282] S704a: The RSU decrypts the first ciphertext information in the first VSI message using the first key in the first VSI message.

[0283] This step may refer to S304 and will not be described in detail here.

[0284] S702b: The second OBU generates a second VSI message, where the second VSI message carries the second MAC address and second ciphertext information obtained by encrypting the second information using the second key.

[0285] This step may refer to S302 and will not be described in detail here.

[0286] S703b, the second OBU sends a second VSI message. Correspondingly, the RSU receives the first VSI message.

[0287] S704b: The RSU uses the second key in the second VSI message to decrypt the ciphertext information in the second VSI message.

[0288] This step may refer to S304 and will not be described in detail here.

[0289] It can be understood that here, S702b, S703b and S704b are arranged after S702a, S703a and S704a for only an example, and the present application does not limit the sequence of S702b, S703b and S704b and S702a, S703a and S704a.

[0290] S705, the RSU determines to send a first operation request message in response to the first VSI message, and determines to send a second operation request message in response to the second VSI message, the first operation request message carries the first MAC address and the third ciphertext information obtained by encrypting the third information using the first key, and the second operation information carries the third MAC address and the fourth ciphertext information obtained by encrypting the fourth information using the second key.

[0291] As an example, after receiving the first VSI message and the second VSI message within a first preset time period, the RSU determines whether the MAC addresses in the first VSI message and the second VSI message are the same. An example of the first preset time period is tens of milliseconds.

[0292] The RSU receives the first VSI message and the second VSI message within the first preset time period, which can be understood as: the time interval between the time when the RSU receives the first VSI message and the time when the RSU receives the second VSI message is less than or equal to the first preset time period

[0293] In this embodiment, the time when the RSU receives the first VSI message is earlier than the time when the RSU receives the second VSI message; or the number of VSI messages received by the RSU from the first OBU within the first preset time is greater than the number of VSI messages received by the RSU from the second OBU within the first preset time; or the priority of the first OBU is higher than the priority of the second OBU; or the priority of the service corresponding to the first VSI message is greater than the priority of the service corresponding to the second VSI message; or the priority of the user of the first OBU is greater than the priority of the user of the second OBU. Therefore, the RSU decides to respond to the first VSI message and not to respond to the second VSI message, that is, the RSU determines to send the first operation request message and determines not to send the second operation request message, the first operation request message carries the first MAC address and the ciphertext information encrypted using the first key of the first OBU, and the second operation request message carries the second MAC address and the ciphertext information encrypted using the second key of the second OBU.

[0294] S706a: The RSU broadcasts a first operation request message.

[0295] S706b, the RSU broadcasts a second operation request message.

[0296] This embodiment does not limit the sequence of S706a and S706b.

[0297] S707a: The first OBU sends a first operation response message based on the first operation request message.

[0298] For the relevant content of the first OBU sending the first operation response message based on the first operation request message, reference may be made to the relevant content of the OBU sending the operation response message based on the operation request message in S307, which will not be repeated here.

[0299] Optionally, after receiving the second operation request message, the first OBU ignores the second operation request message because MAC address verification fails.

[0300] S707b, the second OBU successfully verifies the MAC address in the first operation request message using the second MAC address, but fails to decrypt the third ciphertext information in the first operation request message using the second key, and then uses the third MAC address to verify the MAC address of the second operation request message; and successfully verifies the MAC address of the second operation request message using the third MAC address, and sends a second operation response message based on the second operation request message.

[0301] For the relevant content of the second OBU sending the second operation response message based on the second operation request message, reference may be made to the relevant content of the OBU sending the operation response message based on the operation request message in S307, which will not be repeated here.

[0302] Optionally, because the MAC address verification of the first operation request message fails, the second OBU ignores the second operation request message.

[0303] This embodiment does not limit the sequence of S707a and S707b.

[0304] Figure 8 This is a schematic diagram of the structure of the communication device of the first embodiment of the present application. Figure 8 As shown, the communication device 1800 includes a receiving module 801 , a sending module 802 and a processing module 803 .

[0305] The communication device 800 can be used to perform Figures 4 to 7 A communication method implemented by an RSU or any OBU in the communication method shown in any figure.

[0306] As a first example, the communication device 800 can be used to implement Figure 4 The communication method implemented by the RSU in the illustrated embodiment, wherein the receiving module 801 can be used to execute the operations executed by the RSU in S404 and S409, the sending module 802 can be used to execute the steps executed by the RSU in S401 and S406, and the processing module 803 can be used to execute S404 and S405.

[0307] As a second example, the communication device 800 can be used to implement Figure 4 The communication method implemented by the OBU in the illustrated embodiment, wherein the receiving module 801 can be used to execute the steps executed by the OBU in S401 and S406, the sending module 802 can be used to execute the operations executed by the OBU in S403 and S409, and the processing module 803 can be used to execute S407 and S408.

[0308] As a third example, the communication device 800 can be used to implement Figure 6 The communication method implemented by the RSU in the illustrated embodiment, wherein the receiving module 801 can be used to execute the operations executed by the RSU in S603 and S609, the sending module 802 can be used to execute the steps executed by the RSU in S601, S606a and S606b, and the processing module 803 can be used to execute S604 and S605.

[0309] As a fourth example, the communication device 800 can be used to implement Figure 6 The communication method implemented by the OBU in the illustrated embodiment. The receiving module 801 can be used to execute the steps in S601, S606a and S606b executed by the OBU, the sending module 802 can be used to execute the operations in S603 and S609 executed by the OBU, and the processing module 803 can be used to execute S607, S608 and S610.

[0310] Fig. 9 FIG. 1 is a schematic diagram of the structure of a communication device according to another embodiment of the present application. Fig. 9 As shown, the communication device 900 includes a processor 901 and an interface circuit 902. The processor 901 and the interface circuit 902 are coupled to each other. It can be understood that the interface circuit 902 can be a transceiver or an input-output interface.

[0311] Optionally, the communication device 900 may further include a memory 903 for storing instructions executed by the processor 901 or storing input data required for the processor 901 to run instructions or storing data generated after the processor 901 runs instructions.

[0312] The communication device 900 can be used to implement Figures 4 to 7 A communication method implemented by any device in the embodiments shown in any figure.

[0313] The communication device 900 may be a communication device or a chip used in a communication device. For example, the communication device 900 may be an RSU or a chip used in an RSU. For another example, the communication device 900 may be an OBU or a chip used in an OBU.

[0314] It is understood that the processor in the embodiments of the present application may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, transistor logic devices, hardware components or any combination thereof. The general-purpose processor may be a microprocessor or any conventional processor.

[0315] The method steps in the embodiments of the present application can be implemented by hardware, or by a processor executing software instructions. The software instructions can be composed of corresponding software modules, and the software modules can be stored in a random access memory, a flash memory, a read-only memory, a programmable read-only memory, an erasable programmable read-only memory, an electrically erasable programmable read-only memory, a register, a hard disk, a mobile hard disk, a CD-ROM, or any other form of storage medium well known in the art. An exemplary storage medium is coupled to the processor so that the processor can read information from the storage medium and can write information to the storage medium. Of course, the storage medium can also be a component of the processor. The processor and the storage medium can be located in an ASIC. In addition, the ASIC can be located in a network device or a terminal device. Of course, the processor and the storage medium can also be present in a network device or a terminal device as discrete components.

[0316] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented by software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer programs or instructions. When the computer program or instruction is loaded and executed on a computer, the process or function described in the embodiment of the present application is executed in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, a network device, a user device or other programmable device. The computer program or instruction may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer program or instruction may be transmitted from one website site, computer, server or data center to another website site, computer, server or data center by wired or wireless means. The computer-readable storage medium may be any available medium that a computer can access or a data storage device such as a server, data center, etc. that integrates one or more available media. The available medium may be a magnetic medium, for example, a floppy disk, a hard disk, a tape; it may also be an optical medium, for example, a digital video disc; it may also be a semiconductor medium, for example, a solid-state hard disk.

[0317] In the various embodiments of the present application, unless otherwise specified or provided for in any logical conflict, the terms and / or descriptions between the different embodiments are consistent and may be referenced to each other, and the technical features in the different embodiments may be combined to form new embodiments according to their inherent logical relationships.

[0318] In this application, "at least one" means one or more, and "more than one" means two or more. "And / or" describes the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone, where A and B can be singular or plural. In the text description of this application, the character " / " generally indicates that the previous and next associated objects are in an "or" relationship; in the formula of this application, the character " / " indicates that the previous and next associated objects are in a "division" relationship.

[0319] It is understood that the various numbers involved in the embodiments of the present application are only for the convenience of description and are not used to limit the scope of the embodiments of the present application. The size of the sequence number of the above-mentioned processes does not mean the order of execution, and the execution order of each process should be determined by its function and internal logic.

Claims

1. A communication method, characterized in that: include: Receive a first vehicle service indication VSI message, where the first VSI message carries a first media access control MAC address of a second device and first ciphertext information obtained by encrypting first information of the second device using a first key; receiving a second VSI message, where the second VSI message carries a second MAC address of a third device and second ciphertext information obtained by encrypting second information of the third device using a second key, and the first MAC address is the same as the second MAC address; A first operation request message is sent based on the first VSI message and the second VSI message, where the first operation request message carries the first MAC address and third ciphertext information obtained by encrypting third information using the first key.

2. The method according to claim 1, characterized in that Sending a first operation request message based on the first VSI message and the second VSI message includes: not sending an operation request message in response to the second VSI message; The first operation request message is sent in response to the first VSI message.

3. The method according to claim 1, characterized in that The method further comprises: A second operation request message is sent based on the first VSI message and the second VSI message, where the second operation request message carries a third MAC address and fourth ciphertext information obtained by encrypting fourth information using the second key, and the third MAC address is different from the second MAC address.

4. The method according to claim 3, characterized in that The third MAC address is a reserved MAC address.

5. The method according to claim 3, characterized in that: The third MAC address is determined based on a preset rule and the second MAC address.

6. The method according to any one of claims 1 to 5, characterized in that The time of receiving the first VSI message is earlier than the time of receiving the second VSI message by the first device; or The number of VSI messages received from the second device within a first preset time period is greater than the number of VSI messages received from the third device within the first preset time period; or The priority of the second device is higher than the priority of the third device; or The priority of the service corresponding to the first VSI message is greater than the priority of the service corresponding to the second VSI message; or The priority of the user of the second device is greater than the priority of the user of the third device.

7. The method according to any one of claims 1 to 5, characterized in that An interval between a time when the first device receives the first VSI message and a time when the first device receives the second VSI message is less than or equal to a second preset duration.

8. A communication method, characterized in that: include: Sending a first vehicle service indication VSI message to the first device, where the first VSI message carries a first media access control MAC address and first ciphertext information encrypted using a first key and first information; receiving an operation request message from the first device, the operation request message carrying a first MAC address and second ciphertext information, where the second ciphertext information cannot be successfully decrypted by the first key; A second VSI message is sent to the first device, where the second VSI message carries a second MAC address and third ciphertext information obtained by encrypting the first information using a second key, where the second MAC address is different from the first MAC address.

9. The method according to claim 8, characterized in that The interval between the time of sending the second VSI message to the first device and the time of receiving the operation request message is greater than or equal to a preset duration, and no operation request message carrying the first MAC address and ciphertext information that can be successfully decrypted by the first key is received within the preset duration.

10. The method according to claim 8 or 9, characterized in that: The second MAC address is a reserved MAC address.

11. The method according to claim 8 or 9, characterized in that: The second MAC address is determined based on a preset rule and the first MAC address.

12. A communication method, characterized in that: include: Sending a first vehicle service indication VSI message to the first device, where the first VSI message carries a first media access control MAC address and first ciphertext information obtained by encrypting the first information using a first key; receiving a first operation request message from the first device, where the first operation request message carries a first MAC address and second ciphertext information; receiving a second operation request message from the first device, where the second operation request message carries a second MAC address and third ciphertext information, where the second MAC address is different from the first MAC address; Determining that the second ciphertext information cannot be successfully decrypted by the first key; Determining that the second MAC address meets a preset condition; The third ciphertext information is decrypted using the first key.

13. The method according to claim 12, characterized in that The preset condition includes: the second MAC address is a reserved MAC address.

14. The method according to claim 12, characterized in that The preset condition includes: the second MAC address is determined based on a preset rule and the first MAC address.

15. The method according to any one of claims 12 to 14, characterized in that The interval between the time of decrypting the third ciphertext information using the first key and the time of receiving the first operation request message is greater than or equal to a first preset time length, and no operation request message carrying the first MAC address and ciphertext information that can be successfully decrypted by the first key is received within the first preset time length.

16. The method according to any one of claims 12 to 14, characterized in that The method further comprises: Determining that the third ciphertext information cannot be successfully decrypted by the first key; A second VSI message is sent to the first device, where the second VSI message carries a third MAC address and fourth ciphertext information obtained by encrypting the first information using a second key.

17. The method according to claim 16, characterized in that The interval between the time of sending the second VSI message and the time of receiving the second operation request message is greater than or equal to a second preset duration, and no operation request message carrying the second MAC address and ciphertext information that can be successfully decrypted by the first key is received within the second preset duration.

18. A communication device, characterized in that: The communication device comprises: A receiving module, configured to receive a first vehicle service indication VSI message, where the first VSI message carries a first media access control MAC address of a second device and first ciphertext information obtained by encrypting first information of the second device using a first key; The receiving module is further used to receive a second VSI message, where the second VSI message carries a second MAC address of a third device and second ciphertext information obtained by encrypting second information of the third device using a second key, and the first MAC address is the same as the second MAC address; A sending module is used to send a first operation request message based on the first VSI message and the second VSI message, where the first operation request message carries the first MAC address and point ciphertext information obtained by encrypting third information using the first key.

19. A communication device, characterized in that: The communication device comprises: A sending module, configured to send a first vehicle service indication VSI message to the first device, the first VSI message carrying a first media access control MAC address of a second device to which the communication apparatus belongs, and first ciphertext information obtained by encrypting first information of the second device using a first key; A receiving module, configured to receive an operation request message from the first device, where the operation request message carries a first MAC address and second ciphertext information, and the second ciphertext information cannot be successfully decrypted by the first key; The sending module is further used to send a second VSI message to the first device, where the second VSI message carries a second MAC address of the second device and third ciphertext information obtained by encrypting the first information using a second key, and the second MAC address is different from the first MAC address.

20. A communication device, characterized in that: The communication device comprises: A sending module, configured to send a first vehicle service indication VSI message to the first device, the first VSI message carrying a first media access control MAC address of a second device to which the communication apparatus belongs and first ciphertext information obtained by encrypting first information of the second device using a first key; A receiving module, configured to receive a first operation request message from the first device, where the first operation request message carries the first MAC address and second ciphertext information; The receiving module is further configured to receive a second operation request message from the first device, where the second operation request message carries a second MAC address and third ciphertext information, and the second MAC address is different from the first MAC address; A processing module, configured to determine that the second ciphertext information cannot be successfully decrypted by the first key; The processing module is also used to determine that the second MAC address meets a preset condition; The processing module is further configured to decrypt the third ciphertext information using the first key.

21. A communication device, characterized in that: include: Memory and processor; The memory is used to store program instructions; The processor is used to call the program instructions in the memory to implement the communication method according to any one of claims 1 to 17.

22. A vehicle, characterized in that: The vehicle comprises a communication device as claimed in claim 18, 19 or 20.

23. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores program instructions, and when the program instructions are executed on a processor, the communication method according to any one of claims 1 to 17 is implemented.

24. A computer program product, characterized in that The computer program product comprises program instructions, and when the program instructions are executed on a processor, the communication method according to any one of claims 1 to 17 is implemented.

Images