Communication method and device and carrying tool

Abstract

The embodiment of the invention provides a communication method and device and a carrying tool, and the method comprises the steps: transmitting a first request message to a first network device, the first request message is used for requesting the first network device to issue a device certificate, and the first request message comprises a device identifier and an application scene identifier, the equipment identifier is used for identifying a carrying tool and / or a part included in the carrying tool, the application scene identifier is used for identifying a use scene of a first equipment certificate, and the first equipment certificate is a certificate used by the carrying tool when a first service is carried out; and receiving a first response message sent by the first network device, the first response message comprising the second device certificate, the second device certificate being associated with the device identifier and the application scenario identifier, and the second device certificate being used for processing the first service. Through the method, the complexity of the whole certificate application and confirmation process can be reduced.

Description

Communication method, device and vehicle Technical Field

[0001] The embodiments of the present application relate to the field of communications, and more specifically, to a communication method, device, and vehicle. Background Art

[0002] As smart cars are widely used in daily life, the number of internal and external communication services in vehicles is gradually increasing. In many scenarios, vehicle-side identity authentication and authorization are required to ensure the authenticity of the communication subject's identity and the legitimacy of the business permissions.

[0003] Due to the long product lifecycle of vehicles, device certificates stored in in-vehicle components are bound to expire, be revoked, or even temporarily disabled due to a business freeze. This requires vehicles to be able to apply for certificates online and confirm their status. However, among current solutions for online vehicle certificate application, some do not support the certificate status confirmation process. While others do support certificate status confirmation, the entire certificate application and confirmation process is complex and unreliable, resulting in high retry costs.

[0004] Summary of the Invention

[0005] The embodiments of the present application provide a communication method, apparatus, and vehicle that can reduce information interaction between the vehicle and network equipment during the certificate application and confirmation process, thereby reducing the complexity of the certificate application and confirmation process.

[0006] In a first aspect, a communication method is provided, which includes: sending a first request message to a first network device, the first request message being used to request the first network device to issue a device certificate, the first request message including: a device identifier and an application scenario identifier, the device identifier being used to identify a vehicle and / or components included in the vehicle, the application scenario identifier being used to identify a usage scenario of the first device certificate, the first device certificate being a certificate used by the vehicle when performing a first business; receiving a first response message sent by the first network device, the first response message including the second device certificate, the second device certificate being associated with the device identifier and the application scenario identifier, and the second device certificate being used to process the first business.

[0007] The first service may be a service currently being performed by the vehicle, and may include sensor data upload, software upgrade, or map download, etc. The first service may correspond to an application scenario identifier. For example, when the first service is a software upgrade, the application scenario identifier may be used to identify that the usage scenario of the first device certificate is a software upgrade scenario.

[0008] Optionally, the second device certificate may be an ineffective device certificate, and the second device certificate being used to process the first service may be understood as the vehicle being able to use the second device certificate to process the first service.

[0009] Optionally, the vehicle includes one or more components selected from the group consisting of an onboard gateway, a mobile data center, an intelligent cockpit data center, an onboard communication box, sensors, an electronic control unit, and vehicle dynamic control. In this application, the terms "component" and "device" may have the same meaning. For example, a device certificate may be understood as a certificate used by any of the aforementioned components to conduct business.

[0010] Optionally, the first network device may be a certificate service module.

[0011] In this embodiment of the present application, because the first request message sent by the vehicle to the first network device carries the device identifier and application scenario identifier, the first network device can determine the second device certificate based on the device identifier and application scenario identifier. In this way, during the process of the first network device issuing the second device certificate, there is no need to exchange information with the vehicle again, and the vehicle does not need to synchronously modify specific parameters, which can reduce the complexity of the certificate application process and improve the efficiency of certificate application.

[0012] In combination with the first aspect, in some implementations of the first aspect, the method further includes: using the first device certificate or the second device certificate to process the first service.

[0013] In the embodiment of the present application, after receiving the second device certificate, the vehicle can use either the first device certificate to process the first service or the second device certificate to process the first service. This makes the vehicle more flexible in using device certificates to process services.

[0014] In combination with the first aspect, in certain implementations of the first aspect, the method further includes: sending a second request message to the first network device, the second request message being used to request the first network device to verify the second device certificate; and receiving a second response message sent by the first network device, the second response message including a verification result of the second device certificate associated with the device identifier and the application scenario identifier.

[0015] In the embodiment of the present application, after the vehicle applies for the second device certificate, it can quickly initiate the second device certificate confirmation process, so that the vehicle can process the first business according to the verification result of the second device certificate.

[0016] In combination with the first aspect, in some implementations of the first aspect, the second request message includes: the second device certificate, the device identifier, and the application scenario identifier.

[0017] In combination with the first aspect, in certain implementations of the first aspect, when the verification result of the second device certificate is successful and the vehicle uses the first device certificate to process the first business, the use of the first device certificate or the second device certificate to process the first business includes: switching the first device certificate to the second device certificate to process the first business.

[0018] In this embodiment of the present application, if the vehicle confirms that the certificate verification result is successful and the vehicle is using the first device certificate, the vehicle can switch from the first device certificate to the second device certificate to process the first service. In this way, the vehicle can promptly use the confirmed new device certificate to process the service, ensuring the security of the first service processing.

[0019] In combination with the first aspect, in certain implementations of the first aspect, when the verification result of the second device certificate is successful and the vehicle uses the second device certificate to process the first business, the use of the first device certificate or the second device certificate to process the first business includes: continuing to use the second device certificate to process the first business.

[0020] In an embodiment of the present application, when the vehicle confirms that the verification result of the certificate is successful and the vehicle has already used the second device certificate to process the business, the vehicle can continue to use the second device certificate to process the first business without switching the device certificate, thereby improving the efficiency of processing the first business.

[0021] In combination with the first aspect, in certain implementations of the first aspect, when the verification result of the second device certificate is verification failure, using the first device certificate or the second device certificate to process the first business includes: using the first device certificate to process the first business.

[0022] In an embodiment of the present application, when the verification result of the confirmation certificate of the vehicle is a failure, the vehicle can use the first device certificate to process the first business. In this way, the vehicle can avoid using the unconfirmed second device certificate to process the first business, thereby ensuring the security of the first business processing.

[0023] In combination with the first aspect, in some implementations of the first aspect, the method further includes: prompting the user that the second device certificate cannot be used.

[0024] Optionally, the vehicle may prompt the user that the second device certificate cannot be used through a display screen or voice or other methods.

[0025] Optionally, during the repeated certificate confirmation process, if the previous certificate verification result of the second device certificate is successful, that is, the vehicle has already used the second device certificate to process the first service. When the vehicle initiates the certificate confirmation process again and the verification result of the second device certificate this time is failure, the vehicle may prompt the user that the first service cannot be processed.

[0026] In combination with the first aspect, in certain implementations of the first aspect, before sending the second request message to the first network device, the method also includes: determining whether the locally stored private key matches the public key of the second device certificate; sending the second request message to the first network device includes: sending the second request message to the first network device when the locally stored private key matches the public key of the second device certificate.

[0027] Optionally, when it is determined that the private key stored locally does not match the public key of the second device certificate, the carrier may prompt the user that the first service cannot be performed.

[0028] The matching principle between the private key and the certificate's public key is that the certificate's public key is essentially an encrypted string, visible to anyone, while the private key's contents are known only to the owner (the vehicle). Ciphertext encrypted with the public key can be decrypted using the paired private key, but the public key cannot decrypt the private key. In this application, if the vehicle's locally stored private key can decrypt the certificate's public key, then the private key and public key match.

[0029] In an embodiment of the present application, before initiating the certificate confirmation process, the vehicle can locally check the matching of the private key and the certificate public key. If the private key stored in the vehicle and the public key of the second device certificate match, the certificate confirmation process can be carried out; if the private key stored in the vehicle and the public key of the second device certificate do not match, the second device certificate can be determined to be unavailable without the need to connect to the Internet, and corresponding remedial measures can be taken in advance.

[0030] In combination with the first aspect, in certain implementations of the first aspect, a third request message is sent to a second network device, wherein the third request message is used to request the second network device to verify whether the vehicle has the authority to perform the first business, and the third request message includes at least one of the following: the second device certificate, the device identifier, and the application scenario identifier; and a third response message is received from the second network device, wherein the third response message is used to indicate the result of the authority verification of the vehicle.

[0031] Optionally, the second network device may be a service module, which may verify whether the vehicle has the authority to process the first service.

[0032] In this embodiment of the present application, the vehicle can carry a device identifier and / or an application scenario identifier in the third request message, thereby enabling the second network device to initiate a second device certificate verification process with the first network device. This approach eliminates the need for signaling interaction between the vehicle and the first network device, and the vehicle only needs to process the first service based on the service permission verification result.

[0033] In combination with the first aspect, in certain implementations of the first aspect, when the authority verification result is that the vehicle has the authority to perform the first business, and the vehicle uses the first device certificate to process the first business, the use of the first device certificate or the second device certificate to process the first business includes: switching the first device certificate to the second device certificate to process the first business.

[0034] In this embodiment of the present application, if the vehicle confirms that it has permission to perform the first service and is using the first device certificate, the vehicle can switch from the first device certificate to the second device certificate to process the first service. In this way, the vehicle can promptly use the confirmed new device certificate to process the service, which not only ensures the security of the first service processing but also saves the signaling interaction process between the vehicle and the first network device.

[0035] In combination with the first aspect, in certain implementations of the first aspect, when the authority verification result is that the vehicle has the authority to perform the first business, and the vehicle uses the second device certificate to process the first business, the use of the first device certificate or the second device certificate to process the first business includes: continuing to use the second device certificate to process the first business.

[0036] In an embodiment of the present application, when the vehicle confirms that it has the authority to perform the first service and the vehicle has already used the second device certificate to process the service, the vehicle can continue to use the second device certificate to process the first service without switching the device certificate, which not only improves the efficiency of processing the first service, but also eliminates the signaling interaction process between the vehicle and the first network device.

[0037] In combination with the first aspect, in certain implementations of the first aspect, when the authority verification result is that the vehicle does not have the authority to perform the first business, using the first device certificate or the second device certificate to process the first business includes: using the first device certificate to process the first business.

[0038] In an embodiment of the present application, when the vehicle is confirmed to not have the authority to perform the first business, the vehicle can use the first device certificate to process the first business. In this way, the vehicle can avoid using the unconfirmed second device certificate to process the first business, thereby ensuring the security of the first business processing.

[0039] In a second aspect, a communication method is provided, which includes: receiving a first request message sent by a vehicle, the first request message is used to request a first network device to issue a device certificate, the first request message includes a device identifier and an application scenario identifier, the device identifier is used to identify the vehicle and / or components included in the vehicle, the application scenario identifier is used to identify the usage scenario of the first device certificate, and the first device certificate is the certificate used by the vehicle when performing a first business; determining a second device certificate based on the device identifier and the application scenario identifier; sending a first response message to the vehicle, the first response message includes the second device certificate, and the second device certificate is used to process the first business.

[0040] In this embodiment of the present application, the first network device can receive the device identification and application scenario identification sent by the vehicle and determine the second device certificate based on the device identification and application scenario identification. In this way, during the process of the first network device issuing the second device certificate, there is no need to exchange information with the vehicle again, and the vehicle does not need to synchronously modify specific parameters, which can reduce the complexity of the certificate application process and improve the efficiency of certificate application.

[0041] In combination with the second aspect, in some implementations of the second aspect, the method also includes: receiving a second request message sent by the first device, the second request message is used to request the first network device to verify the second device certificate, the first device includes a vehicle or a second network device; determining the verification result of the second device certificate based on the device identifier and the application scenario identifier; sending a second response message to the first device, the second response message is used to indicate the verification result of the second device certificate.

[0042] In an embodiment of the present application, the first network device can verify the second device certificate based on the vehicle device identifier and the application scenario identifier, and return the verification result of the second device certificate to the vehicle, so that the vehicle can process the first business based on the verification result of the second device certificate.

[0043] In combination with the second aspect, in some implementations of the second aspect, the second request message includes: the second device certificate, the device identifier, and the application scenario identifier.

[0044] In combination with the second aspect, in certain implementations of the second aspect, determining the verification result of the second device certificate based on the device identifier and the application scenario identifier includes: verifying the validity of the device identifier and the application scenario identifier; and when the device identifier and the application scenario identifier are valid, determining that the verification result of the second device certificate is successful verification.

[0045] In combination with the second aspect, in certain implementations of the second aspect, the verification of the validity of the device identifier and the application scenario identifier includes: verifying whether the device identifier is consistent with the device identifier preset in the first network device, and whether the application scenario identifier is consistent with the application scenario identifier preset in the first network device.

[0046] For example, if the device identifier is consistent with the device identifier preset in the first network device, and the application scenario identifier is consistent with the application scenario identifier preset in the first network device, the device identifier and the application scenario identifier can be confirmed to be valid, and the verification result of the second device certificate is successful. If the device identifier is inconsistent with the device identifier preset in the first network device, or the application scenario identifier is inconsistent with the application scenario identifier preset in the first network device, the verification result of the second device certificate can be confirmed to be failed.

[0047] In an embodiment of the present application, the first network device can verify the validity of the device identifier and the application scenario identifier by verifying whether the device identifier is consistent with the device identifier preset in the first network device, and whether the application scenario identifier is consistent with the application scenario identifier preset in the first network device, thereby determining the verification result of the second device certificate.

[0048] In combination with the second aspect, in certain implementations of the second aspect, the second request message also includes: a message signature, and before determining the verification result of the second device certificate based on the device identifier and the application scenario identifier, the method also includes: using the second device certificate to verify the validity of the message signature.

[0049] In the embodiment of the present application, the first network device may also use the second device certificate to verify the validity of the signature. If the signature is valid, the first network device may then verify the validity of the device identifier and the application scenario identifier.

[0050] In combination with the second aspect, in some implementations of the second aspect, the method further includes: maintaining the status of the first device certificate in a valid state.

[0051] In this embodiment of the present application, if the verification result of the second device certificate is successful, the first network device may not switch the validity status of the first device certificate to a revoked state. In this way, the vehicle can have both the first device certificate and the second device certificate in effect. The first device certificate and the second device certificate can back up each other, and if one certificate is damaged, the other can be used to handle business.

[0052] In combination with the second aspect, in some implementations of the second aspect, the application scenario identifier includes at least one of the following: a character string, a readable name, and a digital ID.

[0053] Among them, a string can be understood as a string of characters consisting of numbers, letters, and underscores, which can be a data type representing text in a programming language; a readable name can be understood as a word that can be understood by the user, and a digital ID can be understood as a digital identifier.

[0054] According to a third aspect, a communication method is provided, which includes: receiving a third request message sent by a vehicle, the third request message being used to request the second network device to verify whether the vehicle has the authority to perform a first service, the third request message including at least one of the following: a second device certificate, a device identifier, and an application scenario identifier, the second device certificate being used to process the first service, the device identifier being used to identify the vehicle and / or components included in the vehicle, the application scenario identifier being used to identify the usage scenario of the first device certificate, the first device certificate being the certificate used by the vehicle when performing the first service; sending a second request message to the first network device, the second request message being used to request the first network device to verify the second device certificate, the second request message including the second device certificate, the device identifier, and the application scenario identifier; receiving a second response message sent by the first network device, the second response message including the verification result of the second device certificate associated with the device identifier and the application scenario identifier; and sending a third response message to the vehicle based on the verification result of the second device certificate, the third response message being used to indicate the result of the authority verification of the vehicle.

[0055] Optionally, the second network device may be a service module, which may verify whether the vehicle has the authority to process the first service.

[0056] Optionally, the third request message may not carry the application scenario identifier, but only carry the device identifier, that is, the second network device is only responsible for authenticating the first service authority, and the second network device can determine the application scenario of the first service only based on the device identifier.

[0057] Optionally, the third request message may not carry the application scenario identifier and device identifier, that is, the second network device is only responsible for authenticating the first service authority, and the second network device already knows the identity of the vehicle, and the second network device can directly determine the application scenario of the first service.

[0058] It should be understood that the above-mentioned second device certificate is the device certificate requested by the vehicle to be issued by the first network device. In some possible implementations, the above-mentioned second device certificate can also be any device certificate, for example, the first device certificate mentioned above.

[0059] In this embodiment of the present application, the second network device can obtain the device identifier and application scenario identifier from the permission verification request message sent by the vehicle, and initiate the second device certificate verification process to the first network device based on the device identifier and application scenario identifier. In this way, the signaling interaction process between the vehicle and the first network device can be omitted, and the vehicle only needs to process the first service based on the verification result of the service permission.

[0060] In combination with the third aspect, in certain implementations of the third aspect, when the verification result of the second device certificate is successful, the third response message is used to indicate that the vehicle has the authority to perform the first service.

[0061] Optionally, when the verification result of the second device certificate fails, the third response message may be used to indicate that the vehicle does not have the authority to perform the first service.

[0062] In a fourth aspect, a communication method is provided, which includes: sending a second request message to the first network device, the second request message being used to request the first network device to verify the second device certificate; receiving a second response message sent by the first network device, the second response message including a verification result of the second device certificate associated with the device identifier and the application scenario identifier; wherein the device identifier is used to identify a vehicle and / or components included in the vehicle, the application scenario identifier is used to identify a usage scenario of the first device certificate, and the first device certificate is a certificate used by the vehicle when performing a first business.

[0063] In combination with the fourth aspect, in some implementations of the fourth aspect, the second request message includes: the second device certificate, the device identifier, and the application scenario identifier.

[0064] In combination with the fourth aspect, in some implementations of the fourth aspect, before sending the second request message to the first network device, the method further includes: using the first device certificate or the second device certificate to process the first service.

[0065] In combination with the fourth aspect, in certain implementations of the fourth aspect, when the verification result of the second device certificate is successful, and the vehicle uses the first device certificate to process the first business, the use of the first device certificate or the second device certificate to process the first business includes: switching the first device certificate to the second device certificate to process the first business.

[0066] In combination with the fourth aspect, in certain implementations of the fourth aspect, when the verification result of the second device certificate is successful and the vehicle uses the second device certificate to process the first business, the use of the first device certificate or the second device certificate to process the first business includes: continuing to use the second device certificate to process the first business.

[0067] In combination with the fourth aspect, in certain implementations of the fourth aspect, when the verification result of the second device certificate is verification failure, using the first device certificate or the second device certificate to process the first business includes: using the first device certificate to process the first business.

[0068] In combination with the fourth aspect, in some implementations of the fourth aspect, the method further includes: prompting the user that the second device certificate cannot be used.

[0069] In combination with the fourth aspect, in certain implementations of the fourth aspect, before sending the second request message to the first network device, the method also includes: determining whether the locally stored private key matches the public key of the second device certificate; sending the second request message to the first network device includes: sending the second request message to the first network device when the locally stored private key matches the public key of the second device certificate.

[0070] In a fifth aspect, a communication method is provided, the method comprising: sending a third request message to a second network device, the third request message being used to request the second network device to verify whether the vehicle has the authority to perform the first service, the third request message comprising at least one of the following: the second device certificate, the device identifier and the application scenario identifier; the second device certificate being used to process the first service, the device identifier being used to identify the vehicle and / or components included in the vehicle, the application scenario identifier being used to identify the usage scenario of the first device certificate, the first device certificate being the certificate used by the vehicle when performing the first service; receiving a third response message sent by the second network device, the third response message being used to indicate the result of the authority verification of the vehicle.

[0071] In combination with the fifth aspect, in some implementations of the fifth aspect, before sending the third request message to the second network device, the method further includes: using the first device certificate or the second device certificate to process the first service.

[0072] In combination with the fifth aspect, in certain implementations of the fifth aspect, when the authority verification result is that the vehicle has the authority to perform the first business, and the vehicle uses the first device certificate to process the first business, the use of the first device certificate or the second device certificate to process the first business includes: switching the first device certificate to the second device certificate to process the first business.

[0073] In combination with the fifth aspect, in certain implementations of the fifth aspect, when the authority verification result is that the vehicle has the authority to perform the first business, and the vehicle uses the second device certificate to process the first business, the use of the first device certificate or the second device certificate to process the first business includes: continuing to use the second device certificate to process the first business.

[0074] In combination with the fifth aspect, in certain implementations of the fifth aspect, when the authority verification result is that the vehicle does not have the authority to perform the first business, using the first device certificate or the second device certificate to process the first business includes: using the first device certificate to process the first business.

[0075] In the sixth aspect, a communication method is provided, which includes: receiving a second request message sent by a first device, the second request message is used to request the first network device to verify the second device certificate, the first device includes a vehicle or a second network device; determining the verification result of the second device certificate based on the device identifier and the application scenario identifier; sending a second response message to the first device, the second response message is used to indicate the verification result of the second device certificate.

[0076] It should be understood that in the above method, the device identifier and application scenario identifier have been pre-stored in the first network device. When the first network device receives the second request message, the first network device can determine the verification result of the second device certificate based on the stored device identifier and application scenario identifier.

[0077] In combination with the sixth aspect, in some implementations of the sixth aspect, the second request message includes: the second device certificate, the device identifier, and the application scenario identifier.

[0078] In combination with the sixth aspect, in certain implementations of the sixth aspect, determining the verification result of the second device certificate based on the device identifier and the application scenario identifier includes: verifying the validity of the device identifier and the application scenario identifier; and when the device identifier and the application scenario identifier are valid, determining that the verification result of the second device certificate is successful verification.

[0079] In combination with the sixth aspect, in certain implementations of the sixth aspect, the verification of the validity of the device identifier and the application scenario identifier includes: verifying whether the device identifier is consistent with the device identifier preset in the first network device, and whether the application scenario identifier is consistent with the application scenario identifier preset in the first network device.

[0080] In combination with the sixth aspect, in some implementations of the sixth aspect, the method further includes: maintaining the status of the first device certificate in a valid state.

[0081] In combination with the sixth aspect, in certain implementations of the sixth aspect, the second request message also includes: a message signature, and before determining the verification result of the second device certificate based on the device identifier and the application scenario identifier, the method also includes: using the second device certificate to verify the validity of the message signature.

[0082] In combination with the sixth aspect, in some implementations of the sixth aspect, the application scenario identifier includes at least one of the following: a character string, a readable name, and a digital ID.

[0083] In the seventh aspect, a communication method is provided, the method comprising: receiving a third request message sent by a vehicle, the third request message being used to request the second network device to verify whether the vehicle has the authority to perform a first business, the third request message comprising at least one of the following: a second device certificate, a device identifier and an application scenario identifier, the second device certificate being used to process the first business, the device identifier being used to identify the vehicle and / or components included in the vehicle, the application scenario identifier being used to identify the usage scenario of the first device certificate, the first device certificate being the certificate used by the vehicle when performing the first business; sending a second request message to the first network device, the second request message being used to request the first network device to verify the second device certificate, the second request message comprising the second device certificate, the device identifier and the application scenario identifier; receiving a second response message sent by the first network device, the second response message comprising the verification result of the second device certificate associated with the device identifier and the application scenario identifier; and sending a third response message to the vehicle based on the verification result of the second device certificate, the third response message being used to indicate the result of the authority verification of the vehicle.

[0084] In combination with the seventh aspect, in certain implementations of the seventh aspect, when the verification result of the second certificate is successful, the third response message is used to indicate that the vehicle has the authority to perform the first business.

[0085] In the eighth aspect, a communication device is provided, which includes: a transceiver unit; the transceiver unit is used to: send a first request message to a first network device, the first request message is used to request the first network device to issue a device certificate, the first request message includes: a device identifier and an application scenario identifier, the device identifier is used to identify a vehicle and / or components included in the vehicle, the application scenario identifier is used to identify the usage scenario of the first device certificate, the first device certificate is a certificate used by the vehicle when performing a first business; receive a first response message sent by the first network device, the first response message includes the second device certificate, the second device certificate is associated with the device identifier and the application scenario identifier, and the second device certificate is used to process the first business.

[0086] In combination with the eighth aspect, in some implementations of the eighth aspect, the apparatus further includes: a processing unit; the processing unit is configured to process the first service using the first device certificate or the second device certificate.

[0087] In combination with the eighth aspect, in certain implementations of the eighth aspect, the transceiver unit is further used to: send a second request message to the first network device, the second request message being used to request the first network device to verify the second device certificate; and receive a second response message sent by the first network device, the second response message including a verification result of the second device certificate associated with the device identifier and the application scenario identifier.

[0088] In combination with the eighth aspect, in some implementations of the eighth aspect, the second request message includes: the second device certificate, the device identifier, and the application scenario identifier.

[0089] In combination with the eighth aspect, in certain implementations of the eighth aspect, when the verification result of the second device certificate is successful and the vehicle uses the first device certificate to process the first business, the processing unit is specifically used to switch the first device certificate to the second device certificate to process the first business.

[0090] In combination with the eighth aspect, in certain implementations of the eighth aspect, when the verification result of the second device certificate is successful and the vehicle uses the second device certificate to process the first business, the processing unit is specifically used to continue using the second device certificate to process the first business.

[0091] In combination with the eighth aspect, in certain implementations of the eighth aspect, when the verification result of the second device certificate is verification failure, the processing unit is specifically configured to use the first device certificate to process the first service.

[0092] In combination with the eighth aspect, in certain implementations of the eighth aspect, when the verification result of the second device certificate is verification failure, the processing unit is further configured to prompt the user that the second device certificate cannot be used.

[0093] In combination with the eighth aspect, in certain implementations of the eighth aspect, the processing unit is further used to determine whether the locally stored private key matches the public key of the second device certificate; the transceiver unit is further used to send the second request message to the first network device when the locally stored private key matches the public key of the second device certificate.

[0094] In combination with the eighth aspect, in certain implementations of the eighth aspect, the transceiver unit is further used to: send a third request message to the second network device, the third request message is used to request the second network device to verify whether the vehicle has the authority to perform the first business, the third request message includes at least one of the following: the second device certificate, the device identifier and the application scenario identifier; receive a third response message sent by the second network device, the third response message is used to indicate the authority verification result of the vehicle.

[0095] In combination with the eighth aspect, in certain implementations of the eighth aspect, when the authority verification result is that the vehicle has the authority to perform the first business, and the vehicle uses the first device certificate to process the first business, the processing unit is specifically used to switch the first device certificate to the second device certificate to process the first business.

[0096] In combination with the eighth aspect, in certain implementations of the eighth aspect, when the authority verification result is that the vehicle has the authority to perform the first business, and the vehicle uses the second device certificate to process the first business, the processing unit is specifically used to continue using the second device certificate to process the first business.

[0097] In combination with the eighth aspect, in certain implementations of the eighth aspect, when the authority verification result is that the vehicle does not have the authority to perform the first business, the processing unit is specifically used to use the first device certificate to process the first business.

[0098] In the ninth aspect, a communication device is provided, which includes: a transceiver unit and a processing unit; the transceiver unit is used to receive a first request message sent by a vehicle, the first request message is used to request a first network device to issue a device certificate, the first request message includes a device identifier and an application scenario identifier, the device identifier is used to identify the vehicle and / or components included in the vehicle, the application scenario identifier is used to identify the usage scenario of the first device certificate, and the first device certificate is the certificate used by the vehicle when performing a first business; the processing unit is used to determine a second device certificate based on the device identifier and the application scenario identifier; the transceiver unit is also used to send a first response message to the vehicle, the first response message includes the second device certificate, and the second device certificate is used to process the first business.

[0099] In combination with the ninth aspect, in certain implementations of the ninth aspect, the transceiver unit is further used to receive a second request message sent by the first device, the second request message being used to request the first network device to verify the second device certificate, the first device including a vehicle or a second network device; the processing unit is further used to determine the verification result of the second device certificate based on the device identifier and the application scenario identifier; the transceiver unit is further used to send a second response message to the first device, the second response message being used to indicate the verification result of the second device certificate.

[0100] In combination with the ninth aspect, in some implementations of the ninth aspect, the second request message includes: the second device certificate, the device identifier, and the application scenario identifier.

[0101] In combination with the ninth aspect, in certain implementations of the ninth aspect, the processing unit is specifically used to: verify the validity of the device identifier and the application scenario identifier; and when the device identifier and the application scenario identifier are valid, determine that the verification result of the second device certificate is successful.

[0102] In combination with the ninth aspect, in certain implementations of the ninth aspect, the processing unit is specifically used to verify whether the device identifier is consistent with the device identifier preset in the first network device, and whether the application scenario identifier is consistent with the application scenario identifier preset in the first network device.

[0103] In combination with the ninth aspect, in certain implementations of the ninth aspect, the processing unit is further configured to maintain the status of the first device certificate in a valid state.

[0104] In combination with the ninth aspect, in certain implementations of the ninth aspect, the second request message further includes: a message signature; and the processing unit is further used to verify the validity of the message signature using the second device certificate.

[0105] In combination with the ninth aspect, in certain implementations of the ninth aspect, the application scenario identifier includes at least one of the following: a character string, a readable name, and a digital ID.

[0106] In a tenth aspect, a communication device is provided, comprising: a transceiver unit and a processing unit; the transceiver unit is used to: receive a third request message sent by a vehicle, the third request message being used to request the second network device to verify whether the vehicle has the authority to perform a first service, the third request message including at least one of the following: a second device certificate, a device identifier, and an application scenario identifier, the second device certificate being used to process the first service, the device identifier being used to identify the vehicle and / or components included in the vehicle, the application scenario identifier being used to identify the usage scenario of the first device certificate, the first device certificate being the certificate used by the vehicle when performing the first service; send a second request message to the first network device, the second request message being used to request the first network device to verify the second device certificate, the second request message including the second device certificate, the device identifier, and the application scenario identifier; receive a second response message sent by the first network device, the second response message including the verification result of the second device certificate associated with the device identifier and the application scenario identifier; the processing unit is used to send a third response message to the vehicle based on the verification result of the second device certificate, the third response message being used to indicate the result of the authority verification of the vehicle.

[0107] In combination with the tenth aspect, in certain implementations of the tenth aspect, when the verification result of the second certificate is successful, the third response message is used to indicate that the vehicle has the authority to perform the first business.

[0108] In the eleventh aspect, a communication device is provided, which includes a transceiver unit, and the transceiver unit is used to: send a second request message to the first network device, the second request message is used to request the first network device to verify the second device certificate; receive a second response message sent by the first network device, the second response message includes the verification result of the second device certificate associated with the device identifier and the application scenario identifier; wherein the device identifier is used to identify the vehicle and / or the components included in the vehicle, and the application scenario identifier is used to identify the usage scenario of the first device certificate, and the first device certificate is the certificate used by the vehicle to perform the first business.

[0109] In combination with the eleventh aspect, in certain implementations of the eleventh aspect, the second request message includes: the second device certificate, the device identifier, and the application scenario identifier.

[0110] In combination with the eleventh aspect, in some implementations of the eleventh aspect, the apparatus further includes a processing unit, and the processing unit is configured to process the first service using the first device certificate or the second device certificate.

[0111] In combination with the eleventh aspect, in certain implementations of the eleventh aspect, when the verification result of the second device certificate is successful and the vehicle uses the first device certificate to process the first business, the processing unit is specifically used to switch the first device certificate to the second device certificate to process the first business.

[0112] In combination with the eleventh aspect, in certain implementations of the eleventh aspect, when the verification result of the second device certificate is successful and the vehicle uses the second device certificate to process the first business, the processing unit is specifically used to continue using the second device certificate to process the first business.

[0113] In combination with the eleventh aspect, in certain implementations of the eleventh aspect, when the verification result of the second device certificate is verification failure, the processing unit is specifically configured to use the first device certificate to process the first service.

[0114] In combination with the eleventh aspect, in some implementations of the eleventh aspect, the processing unit is further configured to prompt the user that the second device certificate cannot be used.

[0115] In combination with the eleventh aspect, in certain implementations of the eleventh aspect, the processing unit is also used to determine whether the locally stored private key matches the public key of the second device certificate; the transceiver unit is specifically used to send the second request message to the first network device when the locally stored private key matches the public key of the second device certificate.

[0116] In the twelfth aspect, a communication device is provided, which includes a transceiver unit, and the transceiver unit is used to: send a third request message to a second network device, the third request message is used to request the second network device to verify whether the vehicle has the authority to perform the first business, the third request message includes at least one of the following: the second device certificate, the device identifier and the application scenario identifier; the second device certificate is used to process the first business, the device identifier is used to identify the vehicle and / or the components included in the vehicle, the application scenario identifier is used to identify the usage scenario of the first device certificate, and the first device certificate is the certificate used by the vehicle when performing the first business; receive a third response message sent by the second network device, the third response message is used to indicate the authority verification result of the vehicle.

[0117] In combination with the twelfth aspect, in some implementations of the twelfth aspect, the apparatus further includes a processing unit, and the processing unit is configured to process the first service using the first device certificate or the second device certificate.

[0118] In combination with the twelfth aspect, in certain implementations of the twelfth aspect, when the authority verification result is that the vehicle has the authority to perform the first business, and the vehicle uses the first device certificate to process the first business, the processing unit is specifically used to switch the first device certificate to the second device certificate to process the first business.

[0119] In combination with the twelfth aspect, in certain implementations of the twelfth aspect, when the authority verification result is that the vehicle has the authority to perform the first business, and the vehicle uses the second device certificate to process the first business, the processing unit is specifically used to continue using the second device certificate to process the first business.

[0120] In combination with the twelfth aspect, in certain implementations of the twelfth aspect, when the authority verification result is that the vehicle does not have the authority to perform the first business, the processing unit is specifically used to use the first device certificate to process the first business.

[0121] In the thirteenth aspect, a communication device is provided, which includes: a transceiver unit and a processing unit, the transceiver unit is used to receive a second request message sent by a first device, the second request message is used to request the first network device to verify the second device certificate, and the first device includes a vehicle or a second network device; the processing unit is used to determine the verification result of the second device certificate based on the device identifier and the application scenario identifier; the transceiver unit is also used to send a second response message to the first device, and the second response message is used to indicate the verification result of the second device certificate.

[0122] In combination with the thirteenth aspect, in some implementations of the thirteenth aspect, the second request message includes: the second device certificate, the device identifier and the application scenario identifier.

[0123] In combination with the thirteenth aspect, in certain implementations of the thirteenth aspect, the processing unit is specifically used to: verify the validity of the device identifier and the application scenario identifier; and when the device identifier and the application scenario identifier are valid, determine that the verification result of the second device certificate is successful verification.

[0124] In combination with the thirteenth aspect, in certain implementations of the thirteenth aspect, the processing unit is specifically used to verify whether the device identifier is consistent with the device identifier preset in the first network device, and whether the application scenario identifier is consistent with the application scenario identifier preset in the first network device.

[0125] In combination with the thirteenth aspect, in some implementations of the thirteenth aspect, the processing unit is further used to maintain the status of the first device certificate in a valid state.

[0126] In combination with the thirteenth aspect, in certain implementations of the thirteenth aspect, the second request message also includes: a message signature; and the processing unit is further used to verify the validity of the message signature using the second device certificate.

[0127] In combination with the thirteenth aspect, in certain implementations of the thirteenth aspect, the application scenario identifier includes at least one of the following: a character string, a readable name, and a digital ID.

[0128] In a fourteenth aspect, a communication device is provided, comprising: a transceiver unit and a processing unit; the transceiver unit is used to: receive a third request message sent by a vehicle, the third request message is used to request the second network device to verify whether the vehicle has the authority to perform a first business, the third request message includes at least one of the following: a second device certificate, a device identifier and an application scenario identifier, the second device certificate is used to process the first business, the device identifier is used to identify the vehicle and / or the components included in the vehicle, the application scenario identifier is used to identify the usage scenario of the first device certificate, and the first device certificate is the certificate used by the vehicle when performing the first business; send a second request message to the first network device, the second request message is used to request the first network device to verify the second device certificate, the second request message includes the second device certificate, the device identifier and the application scenario identifier; receive a second response message sent by the first network device, the second response message includes the verification result of the second device certificate associated with the device identifier and the application scenario identifier; the processing unit is used to send a third response message to the vehicle based on the verification result of the second device certificate, the third response message is used to indicate the authority verification result of the vehicle.

[0129] In combination with the fourteenth aspect, in certain implementations of the fourteenth aspect, when the verification result of the second certificate is successful, the third response message is used to indicate that the vehicle has the authority to perform the first business.

[0130] In the fifteenth aspect, a communication device is provided, which includes: at least one processor and a memory, wherein the at least one processor is coupled to the memory and is used to read and execute instructions in the memory, so that the device implements the method of any one of the implementation methods of the above-mentioned first to seventh aspects.

[0131] In the sixteenth aspect, a computer-readable medium is provided, wherein the computer-readable medium stores a program code, and when the computer program code is run on a computer, the computer executes a method of any one of the implementation methods of the above-mentioned first to seventh aspects.

[0132] In the seventeenth aspect, a computer program product is provided, which includes a computer program. When the computer program is run, the computer executes the method of any one of the implementation methods of the above-mentioned first to seventh aspects.

[0133] In the eighteenth aspect, a chip is provided, which includes: a circuit, which is used to execute the method of any one of the implementation methods of the first to seventh aspects above.

[0134] In the nineteenth aspect, a vehicle is provided, comprising: at least one processor and a memory, wherein the at least one processor is coupled to the memory and is used to read and execute instructions in the memory so that the device implements a method of any one of the implementation methods of the first, fourth or fifth aspects above.

[0135] In combination with the nineteenth aspect, in certain implementations of the nineteenth aspect, the vehicle is a vehicle.

[0136] In the twentieth aspect, a server is provided, comprising: at least one processor and a memory, wherein the at least one processor is coupled to the memory and is used to read and execute instructions in the memory, so that the device implements a method of any one of the implementation methods of the second aspect, the third aspect, the sixth aspect, and the seventh aspect above. BRIEF DESCRIPTION OF THE DRAWINGS

[0137] FIG1 is a functional schematic diagram of a vehicle provided in an embodiment of the present application;

[0138] FIG2 is a system architecture applicable to the communication method provided in an embodiment of the present application;

[0139] FIG3 is a schematic flow chart of a communication method provided in an embodiment of the present application;

[0140] FIG4 is a schematic flow chart of another communication method provided in an embodiment of the present application;

[0141] FIG5 is a schematic flow chart of another communication method provided in an embodiment of the present application;

[0142] FIG6 is a schematic flow chart of another communication method provided in an embodiment of the present application;

[0143] FIG7 is a schematic flow chart of another communication method provided in an embodiment of the present application;

[0144] FIG8 is a schematic flow chart of another communication method provided in an embodiment of the present application;

[0145] FIG9 is a schematic flow chart of another communication method provided in an embodiment of the present application;

[0146] FIG10 is a communication device provided in an embodiment of the present application;

[0147] FIG11 is another communication device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0148] The technical solutions in the embodiments of the present application will be described below with reference to the accompanying drawings.

[0149] Figure 1 is a functional schematic diagram of a vehicle 100 provided in an embodiment of the present application. It should be understood that Figure 1 and the related description are merely examples and do not limit the vehicle in the embodiment of the present application.

[0150] Vehicle 100 may include various subsystems, such as perception system 120 and computing platform 130. Optionally, vehicle 100 may include more or fewer subsystems, and each subsystem may include one or more components. In addition, each subsystem and component of vehicle 100 may be interconnected via wired or wireless means.

[0151] The perception system 120 may include several sensors for sensing information about the environment surrounding the vehicle 100. For example, the perception system 120 may include a positioning system, which may be a global positioning system (GPS), a Beidou system, or other positioning systems. The perception system 120 may include one or more of an inertial measurement unit (IMU), a laser radar, a millimeter-wave radar, an ultrasonic radar, and a camera.

[0152] Some or all functions of the vehicle 100 can be controlled by a computing platform 130. The computing platform 130 may include processors 131 to 13n (n is a positive integer). A processor is a circuit with signal processing capabilities. In one implementation, the processor can be a circuit with instruction reading and execution capabilities, such as a central processing unit (CPU), a microprocessor, a graphics processing unit (GPU) (which can be understood as a microprocessor), or a digital signal processor (DSP). In another implementation, the processor can implement certain functions through the logical relationship of a hardware circuit. The logical relationship of the hardware circuit is fixed or reconfigurable. For example, the processor is a hardware circuit implemented by an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), such as an FPGA. In a reconfigurable hardware circuit, the process of the processor loading a configuration file to implement the hardware circuit configuration can be understood as the process of the processor loading instructions to implement the functions of some or all of the above units. In addition, the processor may also be a hardware circuit designed for artificial intelligence, which can be understood as an ASIC, such as a neural network processing unit (NPU), a tensor processing unit (TPU), a deep learning processing unit (DPU), etc. In addition, the computing platform 130 may also include a memory for storing instructions, and some or all of the processors 131 to 13n may call the instructions in the memory to implement corresponding functions.

[0153] Computing platform 130 may control functions of vehicle 100 based on input received from various subsystems, such as perception system 120. In some embodiments, computing platform 130 may be used to provide control over many aspects of vehicle 100 and its subsystems.

[0154] Optionally, the above components are only an example. In actual applications, the components in the above modules may be added or deleted according to actual needs. Figure 1 should not be understood as a limitation to the embodiments of the present application.

[0155] The vehicle 100 in this application may include: road vehicles, water vehicles, air vehicles, industrial equipment, agricultural equipment, or entertainment equipment, etc. For example, the vehicle 100 can be a vehicle, which is a vehicle in the broad sense, and can be a transportation vehicle (such as a commercial vehicle, a passenger car, a motorcycle, a flying car, a train, etc.), an industrial vehicle (such as a forklift, a trailer, a tractor, etc.), an engineering vehicle (such as an excavator, a bulldozer, a crane, etc.), agricultural equipment (such as a lawn mower, a harvester, etc.), amusement equipment, a toy vehicle, etc. The embodiments of this application do not specifically limit the type of vehicle. For another example, the vehicle 100 can be a vehicle such as an airplane or a ship.

[0156] The following uses a vehicle as an example to illustrate the technical problems that need to be solved in this application and the technical solutions adopted.

[0157] As smart cars become more commonplace in daily life, the number of internal and external communications within vehicles is increasing. In many scenarios, vehicle-side identity authentication and authorization are required to ensure the authenticity of the communication subject and the legitimacy of service permissions. For example, verifying whether a vehicle has permissions to log data, upload data to the cloud, perform vehicle-to-everything (V2X) communications, and securely transmit in-vehicle data is crucial.

[0158] Due to the long product lifecycle of vehicles, device certificates stored in vehicle components are bound to expire, be revoked, or even temporarily disabled due to a business freeze. This requires vehicles to have the ability to apply for certificates online and confirm certificate status. However, among current solutions for online vehicle certificate application, some do not support certificate status confirmation. Vehicles can only discover certificate anomalies during business processing, which increases the difficulty of handling business anomalies. Although other solutions support the certificate status confirmation process, the entire certificate application and confirmation process requires multiple information exchanges, and any interruption in any step will cause the process to be interrupted, forcing the certificate application or confirmation process to be restarted. The entire certificate application or confirmation process is complex, unreliable, and has high retry costs.

[0159] For example, during the certificate application process, the vehicle needs to interact with the certificate service module multiple times. The vehicle needs to modify specific parameters (for example, server address, etc.) according to the instructions of the certificate service module. The entire certificate application process is relatively complicated and has poor reliability.

[0160] The embodiments of the present application provide a communication method, device, and vehicle that can reduce the complexity of the entire certificate application and confirmation process.

[0161] Before introducing the communication method provided in the embodiments of the present application, the system architecture to which the communication method is applicable is first introduced.

[0162] FIG2 is a system architecture applicable to the communication method provided in an embodiment of the present application.

[0163] As shown in Figure 2, the system architecture involves an interactive system between vehicle-side components / the entire vehicle and an external digital certificate service module. The digital certificate service module can be deployed on a cloud platform or server. Vehicle-side components may include: vehicle gateway (VGW), mobile data centers (MDC), cockpit data center (CDC), telematics box (T-box), sensors, electronic control unit (ECU), vehicle dynamic control (VDC), etc.

[0164] Among them, information exchange can be achieved between the digital certificate service module and the vehicle through the wireless communication channel.

[0165] FIG3 is a schematic flow chart of a communication method provided in an embodiment of the present application. Method 300 may be applied to the system architecture of FIG2 . Method 300 may include the following steps.

[0166] S301: A vehicle sends a first request message to a first network device.

[0167] Among them, the first request message is used to request the first network device to issue a device certificate. The first request message may include: a device identifier and an application scenario identifier. The device identifier is used to identify the vehicle and / or the components included in the vehicle. The application scenario identifier is used to identify the usage scenario of the first device certificate. The first device certificate is the certificate used by the vehicle to perform the first business.

[0168] For example, the first service may be a service currently being performed by the vehicle, and may include sensor data upload, software upgrade, or map download, etc. The first service may have a corresponding relationship with the application scenario identifier. For example, when the first service is a software upgrade, the application scenario identifier may be used to identify that the usage scenario of the first device certificate is a software upgrade scenario.

[0169] Optionally, the components of a vehicle may include one or more of: an onboard gateway, a mobile data center, an intelligent cockpit data center, an onboard communication box, sensors, an electronic control unit, and vehicle dynamic control. In this application, the terms "component" and "device" may have the same meaning. For example, a device certificate may be understood as a certificate used by any of the above components to conduct business.

[0170] Optionally, the first network device may be a certificate service module.

[0171] Among them, a string can be understood as a string of characters consisting of numbers, letters, and underscores, which can be a data type representing text in a programming language; a readable name can be understood as a word that can be understood by the user, and a digital ID can be understood as a digital identifier.

[0172] S302: The first network device determines a second device certificate according to the device identifier and the application scenario identifier.

[0173] S303: The vehicle receives a first response message sent by the first network device.

[0174] The first response message may include a second device certificate, where the second device certificate is associated with the device identifier and the application scenario identifier, and the second device certificate is used to process the first service.

[0175] Optionally, the second device certificate may be an ineffective device certificate, and the second device certificate being used to process the first service may be understood as the vehicle being able to use the second device certificate to process the first service.

[0176] In this embodiment of the present application, because the first request message sent by the vehicle to the first network device carries the device identifier and application scenario identifier, the first network device can determine the second device certificate based on the device identifier and application scenario identifier. In this way, during the process of the first network device issuing the second device certificate, there is no need to exchange information with the vehicle again, and the vehicle does not need to synchronously modify specific parameters, which can reduce the complexity of the certificate application process and improve the efficiency of certificate application.

[0177] In one embodiment, after step S303, the method further includes: the vehicle using the first device certificate or the second device certificate to process the first service.

[0178] In the embodiment of the present application, after receiving the second device certificate, the vehicle can use either the first device certificate to process the first service or the second device certificate to process the first service. This makes the vehicle more flexible in using device certificates to process services.

[0179] After applying for the second device certificate, the vehicle can directly initiate a certificate confirmation process to the first network device.

[0180] In one embodiment, after step S303, the method further includes: the carrier sends a second request message to the first network device, wherein the second request message is used to request the first network device to verify the second device certificate; the carrier receives a second response message sent by the first network device, wherein the second response message includes a verification result of the second device certificate associated with the device identifier and the application scenario identifier.

[0181] Optionally, the second request message may include: a second device certificate, a device identifier, and an application scenario identifier.

[0182] In the embodiment of the present application, after the vehicle applies for the second device certificate, it can quickly initiate the second device certificate confirmation process, so that the vehicle can process the first business according to the verification result of the second device certificate.

[0183] The first network device may determine the verification result of the second device certificate according to the device identifier and the application scenario identifier, and thus carry the verification result of the second device certificate in the second response message.

[0184] In one embodiment, the first network device may verify the validity of the device identifier and the application scenario identifier; and if the device identifier and the application scenario identifier are valid, determine that the verification result of the second device certificate is successful.

[0185] Optionally, the first network device verifies the validity of the device identifier and the application scenario identifier, including: the first network device verifies whether the device identifier is consistent with the device identifier preset in the first network device, and whether the application scenario identifier is consistent with the application scenario identifier preset in the first network device.

[0186] In an embodiment of the present application, the first network device can verify the validity of the device identifier and the application scenario identifier by verifying whether the device identifier is consistent with the device identifier preset in the first network device, and whether the application scenario identifier is consistent with the application scenario identifier preset in the first network device, thereby determining the verification result of the second device certificate.

[0187] In one embodiment, the second request message may further include: a message signature. Before the first network device determines the verification result of the second device certificate based on the device identifier and the application scenario identifier, the method further includes: the first network device uses the second device certificate to verify the validity of the message signature.

[0188] In the embodiment of the present application, the first network device may also use the second device certificate to verify the validity of the signature. If the signature is valid, the first network device may then verify the validity of the device identifier and the application scenario identifier.

[0189] In one embodiment, after confirming that the second device certificate is successfully verified, the first network device maintains the status of the first device certificate as valid.

[0190] In this embodiment of the present application, if the verification result of the second device certificate is successful, the first network device may not switch the validity status of the first device certificate to a revoked state. In this way, the vehicle can have both the first device certificate and the second device certificate in effect. The first device certificate and the second device certificate can back up each other, and if one certificate is damaged, the other can be used to handle business.

[0191] In one embodiment, before the vehicle sends the second request message to the first network device, the method also includes: the vehicle determines whether the locally stored private key matches the public key of the second device certificate; and if the locally stored private key matches the public key of the second device certificate, sends the second request message to the first network device.

[0192] Optionally, when it is determined that the private key stored locally does not match the public key of the second device certificate, the carrier may prompt the user that the first service cannot be performed.

[0193] The matching principle between the private key and the certificate's public key is that the certificate's public key is essentially an encrypted string, visible to anyone, while the private key's contents are known only to the owner (the vehicle). Ciphertext encrypted with the public key can be decrypted using the paired private key, but the public key cannot decrypt the private key. In this application, if the vehicle's locally stored private key can decrypt the certificate's public key, then the private key and public key match.

[0194] In an embodiment of the present application, before initiating the certificate confirmation process, the vehicle can locally check the matching of the private key and the certificate public key. If the private key stored in the vehicle and the public key of the second device certificate match, the certificate confirmation process can be carried out; if the private key stored in the vehicle and the public key of the second device certificate do not match, the second device certificate can be determined to be unavailable without the need to connect to the Internet, and corresponding remedial measures can be taken in advance.

[0195] After receiving the verification result of the second certificate, the vehicle can perform different processing based on the current certificate usage of the vehicle.

[0196] In one embodiment, when the verification result of the second device certificate is successful and the vehicle uses the first device certificate to process the first business, the vehicle uses the first device certificate or the second device certificate to process the first business, including: the vehicle switches the first device certificate to the second device certificate to process the first business.

[0197] In this embodiment of the present application, if the vehicle confirms that the certificate verification result is successful and the vehicle is using the first device certificate, the vehicle can switch from the first device certificate to the second device certificate to process the first service. In this way, the vehicle can promptly use the confirmed new device certificate to process the service, ensuring the security of the first service processing.

[0198] In one embodiment, when the verification result of the second device certificate is successful and the vehicle uses the second device certificate to process the first business, the vehicle uses the first device certificate or the second device certificate to process the first business, including: the vehicle continues to use the second device certificate to process the first business.

[0199] In an embodiment of the present application, when the vehicle confirms that the verification result of the certificate is successful and the vehicle has already used the second device certificate to process the business, the vehicle can continue to use the second device certificate to process the first business without switching the device certificate, thereby improving the efficiency of processing the first business.

[0200] In one embodiment, when the verification result of the second device certificate is verification failure, the vehicle uses the first device certificate or the second device certificate to process the first service, including: the vehicle uses the first device certificate to process the first service.

[0201] Optionally, when the carrier confirms that the verification result of the certificate is a failure, the carrier may also prompt the user that the second device certificate cannot be used.

[0202] Optionally, the vehicle may prompt the user that the second device certificate cannot be used through a display screen or voice or other methods.

[0203] Optionally, during the repeated certificate confirmation process, if the previous certificate verification result of the second device certificate is successful, that is, the vehicle has already used the second device certificate to process the first service. When the vehicle initiates the certificate confirmation process again and the verification result of the second device certificate this time is failure, the vehicle may prompt the user that the first service cannot be processed.

[0204] In an embodiment of the present application, when the verification result of the confirmation certificate of the vehicle is a failure, the vehicle can use the first device certificate to process the first business. In this way, the vehicle can avoid using the unconfirmed second device certificate to process the first business, thereby ensuring the security of the first business processing.

[0205] The vehicle may also carry at least one of a second device certificate, a device identifier, and an application scenario identifier in the authority verification request message, so that the second network device can initiate a certificate confirmation process.

[0206] In one embodiment, after step S303, the method further includes: the vehicle sends a third request message to the second network device, the third request message is used to request the second network device to verify whether the vehicle has the authority to perform the first business, and the third request message includes at least one of the following: a second device certificate, a device identifier, and an application scenario identifier; the vehicle receives a third response message sent by the second network device, and the third response message is used to indicate the authority verification result of the vehicle.

[0207] Optionally, the second network device may be a service module, which may verify whether the vehicle has the authority to process the first service.

[0208] In this embodiment of the present application, the vehicle can carry a device identifier and / or an application scenario identifier in the third request message, thereby enabling the second network device to initiate a second device certificate verification process with the first network device. This approach eliminates the need for signaling interaction between the vehicle and the first network device, and the vehicle only needs to process the first service based on the service permission verification result.

[0209] After receiving the result of the authority verification, the vehicle can perform different processing based on the current certificate usage of the vehicle.

[0210] In one embodiment, when the result of the authority verification is that the vehicle has the authority to conduct the first business and the vehicle uses the first device certificate to process the first business, the vehicle uses the first device certificate or the second device certificate to process the first business, including: the vehicle switches the first device certificate to the second device certificate to process the first business.

[0211] In this embodiment of the present application, if the vehicle confirms that it has permission to perform the first service and is using the first device certificate, the vehicle can switch from the first device certificate to the second device certificate to process the first service. In this way, the vehicle can promptly use the confirmed new device certificate to process the service, which not only ensures the security of the first service processing but also saves the signaling interaction process between the vehicle and the first network device.

[0212] In one embodiment, when the authority verification result is that the vehicle has the authority to perform the first business and the vehicle uses the second device certificate to process the first business, the vehicle uses the first device certificate or the second device certificate to process the first business, including: the vehicle continues to use the second device certificate to process the first business.

[0213] In an embodiment of the present application, when the vehicle confirms that it has the authority to perform the first service and the vehicle has already used the second device certificate to process the service, the vehicle can continue to use the second device certificate to process the first service without switching the device certificate, which not only improves the efficiency of processing the first service, but also eliminates the signaling interaction process between the vehicle and the first network device.

[0214] In one embodiment, when the authority verification result is that the vehicle does not have the authority to perform the first service, the vehicle uses the first device certificate or the second device certificate to process the first service, including: the vehicle uses the first device certificate to process the first service.

[0215] In an embodiment of the present application, when the vehicle is confirmed to not have the authority to perform the first business, the vehicle can use the first device certificate to process the first business. In this way, the vehicle can avoid using the unconfirmed second device certificate to process the first business, thereby ensuring the security of the first business processing.

[0216] FIG4 is a schematic flow chart of a communication method provided in an embodiment of the present application. Method 400 may be applied to the system architecture of FIG2 . Method 400 may also be applied to the certificate confirmation process in method 300 . Method 400 may include the following steps.

[0217] S401: The vehicle sends a second request message to the first network device.

[0218] The second request message is used to request the first network device to verify the second device certificate.

[0219] Optionally, the second request message may include: a second device certificate, a device identifier, and an application scenario identifier.

[0220] Optionally, the first network device may be a certificate service module.

[0221] In one embodiment, before step S401, the method further includes: the carrier determines whether the locally stored private key matches the public key of the second device certificate; and if the locally stored private key matches the public key of the second device certificate, sends a second request message to the first network device.

[0222] Optionally, when it is determined that the private key stored locally does not match the public key of the second device certificate, the carrier may prompt the user that the first service cannot be performed.

[0223] S402: The first network device verifies the second device certificate according to the device identifier and the application scenario identifier.

[0224] In one embodiment, the first network device may verify the validity of the device identifier and the application scenario identifier; and if the device identifier and the application scenario identifier are valid, determine that the verification result of the second device certificate is successful.

[0225] Optionally, the first network device verifies the validity of the device identifier and the application scenario identifier, including: the first network device verifies whether the device identifier is consistent with the device identifier preset in the first network device, and whether the application scenario identifier is consistent with the application scenario identifier preset in the first network device.

[0226] In one embodiment, the second request message may further include a message signature. Before step S402, the first network device, based on the device identifier and the application scenario identifier, may further include: verifying the validity of the message signature using the second device certificate. If the message signature is valid, the first network device then verifies the validity of the device identifier and the application scenario identifier.

[0227] S403: The vehicle receives a second response message sent by the first network device.

[0228] The second response message includes a verification result of the second device certificate associated with the device identifier and the application scenario identifier.

[0229] In an embodiment of the present application, the vehicle can independently initiate the device certificate confirmation process, that is, the device certificate confirmation process does not have to be executed after the device certificate application process. This can make the applicable scenarios of the certificate confirmation process more diversified and meet the needs of different users.

[0230] In one embodiment, before step S401, the method further includes: the vehicle using the first device certificate or the second device certificate to process the first service. The first device certificate may be a certificate used by the vehicle to process the first service before the second device certificate is applied.

[0231] In one embodiment, after step S403, the method further includes: when the verification result of the second device certificate is successful, and the vehicle uses the first device certificate to process the first business, the vehicle uses the first device certificate or the second device certificate to process the first business, including: the vehicle switches the first device certificate to the second device certificate to process the first business.

[0232] In this embodiment of the present application, if the vehicle confirms that the certificate verification result is successful and the vehicle is using the first device certificate, the vehicle can switch from the first device certificate to the second device certificate to process the first service. In this way, the vehicle can promptly use the confirmed new device certificate to process the service, ensuring the security of the first service processing.

[0233] In one embodiment, after step S403, the method further includes: when the verification result of the second device certificate is successful, and the vehicle uses the second device certificate to process the first business, the vehicle uses the first device certificate or the second device certificate to process the first business, including: the vehicle continues to use the second device certificate to process the first business.

[0234] In an embodiment of the present application, when the vehicle confirms that the verification result of the certificate is successful and the vehicle has already used the second device certificate to process the business, the vehicle can continue to use the second device certificate to process the first business without switching the device certificate, thereby improving the efficiency of processing the first business.

[0235] In one embodiment, after step S403, the method further includes: when the verification result of the second device certificate is verification failure, the vehicle uses the first device certificate or the second device certificate to process the first business, including: the vehicle uses the first device certificate to process the first business.

[0236] Optionally, when the carrier confirms that the verification result of the certificate is a failure, the carrier may also prompt the user that the second device certificate cannot be used.

[0237] Optionally, the vehicle may prompt the user that the second device certificate cannot be used through a display screen or voice or other methods.

[0238] Optionally, during the repeated certificate confirmation process, if the previous certificate verification result of the second device certificate is successful, that is, the vehicle has already used the second device certificate to process the first service. When the vehicle initiates the certificate confirmation process again and the verification result of the second device certificate this time is failure, the vehicle may prompt the user that the first service cannot be processed.

[0239] Figure 5 is a schematic flowchart of a communication method provided in an embodiment of the present application. Method 500 can be applied to the system architecture of Figure 2. Method 500 can also be applied to the business authority verification process in method 300. Method 500 can include the following steps.

[0240] S501: The vehicle sends a third request message to the second network device.

[0241] The third request message is used to request the second network device to verify whether the vehicle has permission to perform the first service. The third request message includes at least one of the following: a second device certificate, a device identifier, and an application scenario identifier. The second device certificate is used to process the first service; the device identifier is used to identify the vehicle and / or components included in the vehicle; and the application scenario identifier is used to identify the usage scenario of the first device certificate. The first device certificate is the certificate used by the vehicle to perform the first service.

[0242] Optionally, the third request message may not carry the application scenario identifier, but only carry the device identifier, that is, the second network device is only responsible for authenticating the first service authority, and the second network device can determine the application scenario of the first service only based on the device identifier.

[0243] Optionally, the third request message may not carry the application scenario identifier and device identifier, that is, the second network device is only responsible for authenticating the first service authority, and the second network device already knows the identity of the vehicle, and the second network device can directly determine the application scenario of the first service.

[0244] S502: The second network device sends a second request message to the first network device.

[0245] The second request message is used by the first network device to verify the second device certificate.

[0246] Optionally, the second request message may include: a second device certificate, a device identifier, and an application scenario identifier.

[0247] S503: The first network device verifies the second device certificate according to the device identifier and the application scenario identifier.

[0248] In one embodiment, the first network device may verify the validity of the device identifier and the application scenario identifier; and if the device identifier and the application scenario identifier are valid, determine that the verification result of the second device certificate is successful.

[0249] Optionally, the first network device verifies the validity of the device identifier and the application scenario identifier, including: the first network device verifies whether the device identifier is consistent with the device identifier preset in the first network device, and whether the application scenario identifier is consistent with the application scenario identifier preset in the first network device.

[0250] In one embodiment, the second request message may further include a message signature. Before step S503, the first network device, based on the device identifier and the application scenario identifier, may further include: verifying the validity of the message signature using the second device certificate. If the message signature is valid, the first network device then verifies the validity of the device identifier and the application scenario identifier.

[0251] S504: The second network device receives a second response message sent by the first network device.

[0252] The second response message includes a verification result of the second device certificate associated with the device identifier and the application scenario identifier.

[0253] S505: The vehicle receives a third response message sent by the second network device.

[0254] The third response message is used to indicate the result of the authority verification of the vehicle.

[0255] Optionally, when the authority verification result is successful, the third response message may indicate that the vehicle has the authority to perform the first service. When the authority verification result is failed, the third response message may indicate that the vehicle does not have the authority to perform the first service.

[0256] In this embodiment of the present application, the second network device can obtain the device identifier and application scenario identifier from the permission verification request message sent by the vehicle, and initiate the second device certificate verification process to the first network device based on the device identifier and application scenario identifier. In this way, the signaling interaction process between the vehicle and the first network device can be omitted, and the vehicle only needs to process the first service based on the verification result of the service permission.

[0257] After receiving the third response message, the vehicle can perform different processing according to the result of the authority verification and the current usage of the device certificate of the vehicle.

[0258] In one embodiment, when the authority verification result is that the vehicle has the authority to perform the first business, and the vehicle uses the first device certificate to process the first business, the vehicle uses the first device certificate or the second device certificate to process the first business, including: the vehicle switches the first device certificate to the second device certificate to process the first business.

[0259] In this embodiment of the present application, if the vehicle confirms that it has permission to perform the first service and is using the first device certificate, the vehicle can switch from the first device certificate to the second device certificate to process the first service. In this way, the vehicle can promptly use the confirmed new device certificate to process the service, which not only ensures the security of the first service processing but also saves the signaling interaction process between the vehicle and the first network device.

[0260] In one embodiment, when the authority verification result is that the vehicle has the authority to perform the first business and the vehicle uses the second device certificate to process the first business, the vehicle uses the first device certificate or the second device certificate to process the first business, including: the vehicle continues to use the second device certificate to process the first business.

[0261] In an embodiment of the present application, when the vehicle confirms that it has the authority to perform the first service and the vehicle has already used the second device certificate to process the service, the vehicle can continue to use the second device certificate to process the first service without switching the device certificate, which not only improves the efficiency of processing the first service, but also eliminates the signaling interaction process between the vehicle and the first network device.

[0262] In one embodiment, when the authority verification result is that the vehicle does not have the authority to perform the first service, the vehicle uses the first device certificate or the second device certificate to process the first service, including: the vehicle uses the first device certificate to process the first service.

[0263] In an embodiment of the present application, when the vehicle is confirmed to not have the authority to perform the first business, the vehicle can use the first device certificate to process the first business. In this way, the vehicle can avoid using the unconfirmed second device certificate to process the first business, thereby ensuring the security of the first business processing.

[0264] FIG6 is a schematic flowchart of another communication method provided in an embodiment of the present application. Method 600 may be a detailed description of steps S301 to S303 of method 300. Method 600 may include the following steps.

[0265] S601, vehicle-side components undergo certificate inspection.

[0266] Specifically, the vehicle-side component can check the validity period of the local device certificate. If the device certificate is about to expire and / or meets other requirements, the vehicle-side component can initiate the certificate application process and proceed to the next steps. Other requirements may include: vehicle operating status and / or user confirmation. For example, if the vehicle is parked and the user is prompted to apply for a certificate, the vehicle-side component can initiate the certificate application process after the user confirms it on the vehicle display.

[0267] Optionally, the vehicle-end component may perform the certificate check periodically. For example, the vehicle-end component may perform the certificate check each time the vehicle is started, or at a specific time every day.

[0268] It should be understood that the above-mentioned vehicle-side components can be located in the vehicle in method 300, which may include: an on-board gateway, a mobile data center, an intelligent cockpit data center, an on-board communication box, sensors, an electronic control unit, and one or more of the vehicle dynamic control.

[0269] S602, the vehicle-side component generates a certificate application document.

[0270] Exemplarily, the vehicle-side component can randomly generate a public-private key pair and generate a certificate application document based on the public key, while the vehicle-side component can securely store the private key.

[0271] S603: The vehicle-side component sends a certificate application request message to the certificate service module.

[0272] Specifically, the vehicle-side component can send a certificate application request message to the certificate service module. The certificate application request message may include: device identification, application scenario identification, or device identification, application scenario identification and at least one of the following: device certificate, message signature, certificate application file and other additional parameters. The above-mentioned certificate application message may be the first request message in method 300.

[0273] Among them, the device identifier is used to identify the vehicle-side components; the application scenario identifier can be assigned by the business and is used to identify the usage scenario of the certificate. The specific form of the scenario identifier can be a fixed string, a readable name or a digital ID, etc. The device certificate can be the device certificate used by the current business on the vehicle side, and the device certificate can be the first device certificate in method 300. The message signature can be a digital signature of the device identifier, application scenario identifier, certificate application document, and other additional parameters using the private key of the device certificate. Other additional parameters are used to enhance the usability and security of the certificate, and can include at least one of the following: a business serial number (used to uniquely identify the interaction between the vehicle side and the certificate service module, to facilitate problem location and tracing), a timestamp (used to ensure the freshness of the message and prevent replay attacks), a service identifier (used to identify the request type of this request, to facilitate traffic forwarding), etc.

[0274] S604, the certificate service module authenticates the vehicle's identity.

[0275] Specifically, after receiving the certificate application request message, the certificate service module can authenticate the identity of the vehicle end according to the certificate application request message, which may include at least one of the following methods:

[0276] (1) The certificate service module uses the Certificate Authority (CA) certificate to verify the legitimacy of the device certificate, check whether the validity period of the device certificate has expired, and check whether the device certificate is in a valid state.

[0277] (2) The certificate service module uses the device certificate to verify whether the signature of the certificate application request message is valid.

[0278] (3) The certificate service module performs identity authentication, that is, checks whether the device identification and application scenario identification are valid, and whether the certificate application is allowed.

[0279] The certificate service module may be the first network device in method 300 .

[0280] S605: The certificate service module issues a new device certificate according to the device identifier and the application scenario identifier.

[0281] Exemplarily, the certificate service module may select the corresponding certificate issuing address, interface, identification ID and other information according to the device identifier and application scenario identifier in the certificate application request message, and issue a new device certificate, which may be the second device certificate in method 300.

[0282] Optionally, the certificate service module may configure the correspondence between the application scenario identifier and the certificate issuance service information through a configuration file, a database, or the like.

[0283] S606: The certificate service module sends a certificate request response message to the vehicle-side component.

[0284] Optionally, the certificate request response message may include: a new device certificate, and at least one of the following: a cloud certificate, a message signature, an application scenario identifier, and other additional parameters. The above certificate request response message may be the second response message in method 300.

[0285] Among them, the cloud certificate can be used to authenticate the identity of the certificate service module. The message signature can be digitally signed by combining the application scenario identifier, new device certificate, and other additional parameters with the private key of the cloud certificate. The application scenario identifier can be consistent with the application scenario identifier in the certificate application request message. Other additional parameters are used to enhance the usability and security of the certificate, and may include at least one of the following: business serial number (used to uniquely identify the interaction between the vehicle and the certificate service module, facilitating problem location and tracing), timestamp (used to ensure the freshness of the message and prevent replay attacks), service identifier (used to identify the request type of this request, facilitating traffic forwarding), etc.

[0286] S607: The vehicle-side component verifies the device certificate and stores it.

[0287] Specifically, after receiving the certificate request response message, the vehicle-side component can verify the cloud certificate and message signature in the message. After the cloud certificate and message signature are verified, the vehicle-side component verifies the device certificate and stores it securely.

[0288] Optionally, the verification process of the device certificate may include: signature field verification, validity period verification, etc.

[0289] S608: The vehicle-side component will continue to use the old device certificate to process business.

[0290] Specifically, the vehicle-side component may still use the old device certificate to perform business processing, and switch the old device certificate to the new device certificate after appropriate conditions are met. The above business may be the first business in method 300.

[0291] Optionally, the suitable conditions may include at least one of the following: completion of vehicle-side certificate confirmation, the vehicle being in parking state, and user confirmation, etc.

[0292] It should be understood that in the application embodiments, a device certificate may have multiple states, including, in addition to the certificate itself being expired or revoked, pending, valid, and frozen. The vehicle-side component is only allowed to process services when the certificate is valid; in all other states, the vehicle-side component is prohibited from processing services.

[0293] It should also be understood that when a certificate is first issued, it is in a pending state. After the certificate service module successfully confirms the issued certificate, it switches the certificate to an effective state. After the certificate expires, the certificate service module switches the effective certificate to an expired state. When certain security incidents occur, the certificate service module can proactively switch the effective state of the certificate to a revoked state. In some business scenarios, such as user subscription expiration, business deactivation, etc., the certificate service module can switch the certificate from an effective state to a frozen state, and restore the certificate from a frozen state to an effective state after the business resumes.

[0294] In the embodiment of the present application, the certificate application request message sent by the vehicle-side component to the certificate service module includes a device identifier and an application scenario identifier. The certificate service module can select the corresponding CA to issue a new certificate based on the device identifier and the application scenario identifier. During the entire process, the vehicle-side component does not need to exchange information with the certificate service module again. This can improve the efficiency of device certificate application and reduce the complexity of the entire certificate application process. In addition, after the new certificate application is completed, the vehicle-side component can still use the old certificate to process the business. In this way, there is no scenario where no certificate is available before the new certificate confirmation process is completed, which can improve the reliability of the business.

[0295] FIG7 is a schematic flowchart of another communication method provided in an embodiment of the present application. Method 700 describes in detail the certificate confirmation process of method 300 and steps S401 to S403 of method 400. Method 700 may be executed after method 600. Method 700 may include the following steps.

[0296] S701, the vehicle-side component checks whether it meets the certificate confirmation conditions.

[0297] Specifically, the vehicle-side component can check whether it currently meets the certificate verification conditions. If so, it initiates the certificate verification process and proceeds to subsequent steps. Certificate verification conditions may include vehicle operating status and / or user confirmation. For example, if the vehicle is parked, the vehicle-side component may initiate the certificate verification process.

[0298] Optionally, the vehicle-end component may check whether it satisfies the certificate confirmation condition periodically. For example, the vehicle-end component may perform the check each time the vehicle is started or at a specific time every day.

[0299] S702: The vehicle-side component sends a certificate confirmation request message to the certificate service module.

[0300] Optionally, the certificate confirmation request message may include the following content: device identification, application scenario identification, or device identification, application scenario identification and at least one of the following contents: device certificate, message signature and other additional parameters. The certificate confirmation request message may be the second request message in method 300.

[0301] Among them, the device identifier is used to identify the vehicle-side components; the application scenario identifier is assigned by the business and is used to identify the usage scenario of the certificate. The specific form of the scenario identifier can be a fixed string, a readable name or a digital ID, etc. The device certificate can be the device certificate that the vehicle side wants to confirm (that is, the second device certificate in method 300 or the new device certificate in method 600). The message signature can be a digital signature of the device identifier, application scenario identifier, and other additional parameters using the private key of the device certificate. Other additional parameters can be used to enhance the usability and security of the certificate, and can include at least one of the following: a business serial number (used to uniquely identify the interaction between the vehicle side and the certificate service module, to facilitate problem location and tracing), a timestamp (used to ensure the freshness of the message and prevent replay attacks), a service identifier (used to identify the request type of this request, to facilitate traffic forwarding), etc.

[0302] S703: The certificate service module checks the device certificate status.

[0303] Specifically, after receiving the certificate confirmation request message, the certificate service module may check the status of the device certificate according to the request message, including at least one of the following methods:

[0304] (1) The certificate service module uses the CA certificate to verify the legitimacy of the device certificate, check whether the validity period of the device certificate has expired, and check the current status of the device certificate (not valid, valid, frozen, revoked, etc.)

[0305] (2) The certificate service module uses the device certificate to verify whether the signature of the certificate confirmation request message is valid.

[0306] (3) The certificate service module performs identity authentication, that is, checks whether the device identification and application scenario identification are valid, and whether certificate confirmation is allowed.

[0307] (4) When the signature of the certificate confirmation request message, identity authentication, device certificate verification are completed and the certificate status is not valid or valid, the certificate status check passes; otherwise, it fails.

[0308] It should be understood that the process of checking the status of the device certificate is a process of verifying the second device certificate in method 300. The result of checking the status of the device certificate may be the result of verifying the second device certificate in method 300.

[0309] S704: The certificate service module refreshes the certificate status.

[0310] Specifically, this step is only executed if the certificate status check passes and the certificate status is invalid. During execution, the device certificate status can be refreshed from invalid to valid. At the same time, the certificate service module can switch the valid certificate corresponding to the device identifier and application scenario identifier to a revoked state.

[0311] S705: The certificate service module sends a certificate confirmation response message to the vehicle-side component.

[0312] Optionally, the certificate confirmation response message includes the certificate confirmation result and at least one of the following contents: cloud certificate, message signature, application scenario identifier, certificate confirmation result, and other additional parameters. The certificate confirmation response message may be the second response message in method 300.

[0313] Among them, the certificate confirmation result may include success or failure, that is, when the device certificate check passes, the certificate confirmation result is success. When the device certificate check fails, the certificate confirmation result is failure. The cloud certificate is used to authenticate the identity of the certificate service module. The message signature can be digitally signed by the private key of the cloud certificate on the application scenario identifier, the certificate confirmation result, and other additional parameters. The application scenario identifier can be consistent with the application scenario identifier in the certificate confirmation request. Other additional parameters are used to enhance the usability and security of the certificate, and may include at least one of the following: business serial number (used to uniquely identify the interaction between the vehicle and the certificate service module, to facilitate problem location and tracing), timestamp (used to ensure the freshness of the message and prevent replay attacks), service identifier (used to identify the request type of this request, to facilitate traffic forwarding), remarks information (such as the specific status of the certificate, the certificate is about to expire, etc., to improve usability), etc.

[0314] S706, vehicle-side component verification response message.

[0315] Specifically, after receiving the certificate confirmation response message, the vehicle-side component can verify the cloud certificate and message signature. After the cloud certificate and message signature are verified, step S707 is performed.

[0316] S707: The vehicle-side component processes the local device certificate according to the certificate status.

[0317] Specifically, the vehicle-side component can process the locally stored device certificate based on the certificate confirmation result, which can include the following three situations:

[0318] (1) If the certificate confirmation result is successful and the device certificate confirmed this time has been used for business (when the certificate is in the effective state), the vehicle-side component will keep the certificate unchanged and continue to use the certificate for business processing.

[0319] (2) If the certificate confirmation result is successful and the certificate confirmed this time has not been used for business (when the certificate is in an ineffective state), the vehicle-side component will switch the certificate to the certificate used for business processing. The old certificate can be retained locally for a period of time or deleted directly, and the certificate confirmed this time will be used to process business subsequently.

[0320] In this case, after the ineffective certificate is confirmed, the certificate service module can switch the status of the effective certificate corresponding to the device identifier and application scenario identifier to a revoked status, and subsequent vehicle-side components can only use the new certificate for business processing.

[0321] Optionally, in another implementation, the above process may not be performed, that is, after certificate confirmation, the vehicle-end component allows the use of new and old certificates for business processing, and also allows the vehicle-end component to use any certificate for application, that is, the new and old certificates can be used equally.

[0322] (3) If the certificate confirmation result is a failure, the vehicle-side marking service cannot be performed. In this case, the user or manufacturer can be prompted to restore the service and certificate.

[0323] Optionally, before the vehicle-side component performs certificate validation, it can check whether the local private key matches the public key of the device certificate. If so, the vehicle-side component can process the locally stored device certificate based on the certificate validation result. Otherwise, the vehicle-side tagging service cannot be performed. In this case, the vehicle-side component can prompt the user or manufacturer to restore the service and certificate.

[0324] In this embodiment of the present application, during the certificate confirmation process, the vehicle-side component can send the device identification and application scenario identification to the certificate service module. The certificate service module can then complete the device certificate confirmation based on the device identification and application scenario identification, thus reducing the complexity of the entire certificate confirmation process. Furthermore, after the new device certificate is confirmed, the old device certificate will be revoked, thus reducing the risk of abuse of the old device certificate and improving the security of device certificate use.

[0325] FIG8 is a schematic flowchart of another communication method provided in an embodiment of the present application. Method 800 may be a detailed description of steps S301 to S303 of method 300. Method 800 may include the following steps.

[0326] S801, vehicle-side components undergo certificate inspection.

[0327] Specifically, the vehicle-side component can check the validity period of the local device certificate. If the device certificate is about to expire and / or meets other requirements, the vehicle-side component can initiate the certificate application process and proceed to the next steps. Other requirements may include: vehicle operating status and / or user confirmation. For example, if the vehicle is parked and the user is prompted to apply for a certificate, the vehicle-side component can initiate the certificate application process after the user confirms it on the vehicle display.

[0328] Optionally, the vehicle-end component may perform the certificate check periodically. For example, the vehicle-end component may perform the certificate check each time the vehicle is started, or at a specific time every day.

[0329] S802, the vehicle-side component generates a certificate application document.

[0330] Exemplarily, the vehicle-side component can randomly generate a public-private key pair, generate a certificate application document based on the public key, and securely store the private key.

[0331] S803: The vehicle-side component sends a certificate application request message to the certificate service module.

[0332] Specifically, the vehicle-side component can send a certificate application request message to the certificate service module. The certificate application request message may include a device identifier, an application scenario identifier, or at least one of the following: a device certificate, a message signature, a certificate application file, and other additional parameters. The above-mentioned certificate application request message may be the first request message in method 300.

[0333] Among them, the device identifier can be used to identify the vehicle-side components; the application scenario identifier is assigned by the business and is used to identify the usage scenario of the certificate. The specific form of the scenario identifier can be a fixed string, a readable name or a digital ID, etc. The device certificate can be the device certificate used by the current business on the vehicle side, and the device certificate can be the first device certificate in method 300. The message signature can be a digital signature of the device identifier, application scenario identifier, certificate application document, and other additional parameters using the private key of the device certificate. Other additional parameters are used to enhance the usability and security of the certificate, and can include at least one of the following: a business serial number (used to uniquely identify the interaction between the vehicle side and the certificate service module, to facilitate problem location and tracing), a timestamp (used to ensure the freshness of the message and prevent replay attacks), a service identifier (used to identify the request type of this request, to facilitate traffic forwarding), etc.

[0334] S804, the certificate service module authenticates the vehicle's identity.

[0335] Specifically, after receiving the certificate application request message, the certificate service module can authenticate the identity of the vehicle end according to the certificate application request message, including:

[0336] (1) The certificate service module uses the CA certificate to verify the legitimacy of the device certificate, check whether the validity period of the device certificate has expired, and check whether the device certificate is in a valid state.

[0337] (2) The certificate service module uses the device certificate to verify whether the signature of the certificate application request message is valid.

[0338] (3) The certificate service module performs identity authentication, that is, checks whether the device identification and application scenario identification are valid, and whether the certificate application is allowed.

[0339] S805: The certificate service module issues a new device certificate according to the device identifier and the application scenario identifier.

[0340] Exemplarily, the certificate service module can select the corresponding certificate issuance address, interface, identification ID and other information based on the device identifier and application scenario identifier in the certificate application request message, and issue a new device certificate. The above new device certificate can be the second device certificate in method 300.

[0341] Optionally, the certificate service module may configure the correspondence between the application scenario identifier and the certificate issuance service information through a configuration file, a database, or the like.

[0342] S806: The certificate service module sends a certificate request response message to the vehicle-side component.

[0343] Optionally, the certificate request response message includes the new device certificate and at least one of the following: a cloud certificate, a message signature, an application scenario identifier, and other additional parameters. The certificate request response message may be the first response message in method 300 .

[0344] Among them, the cloud certificate is used to authenticate the identity of the certificate service module. The message signature can be digitally signed by combining the application scenario identifier, new device certificate, and other additional parameters with the private key of the cloud certificate. The application scenario identifier can be consistent with the application scenario identifier in the certificate application request. Other additional parameters are used to enhance the usability and security of the certificate, and may include at least one of the following: business serial number (used to uniquely identify the interaction between the vehicle and the certificate service module, facilitating problem location and tracing), timestamp (used to ensure the freshness of the message and prevent replay attacks), service identifier (used to identify the request type of this request, facilitating traffic forwarding), etc.

[0345] S807, the vehicle-side component verifies the device certificate and stores it.

[0346] Specifically, after receiving the certificate request response message, the vehicle-side component can verify the cloud certificate and message signature in the message. After the cloud certificate and message signature are verified, the vehicle-side component verifies the device certificate and stores it securely.

[0347] Optionally, the verification process of the device certificate may include: signature field verification, validity period verification, etc.

[0348] S808: The vehicle-side components perform subsequent business processing.

[0349] Specifically, the vehicle-side component can either use the old device certificate for business processing and switch to the new device certificate when appropriate conditions are met, or directly use the new device certificate for subsequent business processing. Appropriate conditions may include: certificate verification completed, the vehicle is in the parked state, user confirmation, etc.

[0350] In an embodiment of the present application, in the device certificate application process, after completing the application for a new device certificate, the vehicle-side component can directly use the new device certificate that has not yet taken effect to process business, thereby improving the efficiency of using the device certificate.

[0351] Figure 9 is a schematic flowchart of another communication method provided in an embodiment of the present application. Method 900 is a detailed description of the business authority verification process of method 300 and steps S501 to S505 of method 500. Method 900 can be executed after method 800. Method 800 can include the following steps.

[0352] S901: The vehicle-side component uses a device certificate that has not been displayed and confirmed to perform business processing.

[0353] The device certificate that has not been displayed and confirmed can be understood as a device certificate that has not been confirmed by the device certificate confirmation process.

[0354] S902: The certificate service module checks the device certificate status.

[0355] Exemplarily, in this step, the certificate service module can obtain the vehicle-side device identifier and the application scenario identifier corresponding to the business module, and check the certificate status based on the vehicle-side device identifier and application scenario identifier. The device identifier and application scenario identifier can be obtained from the business module, that is, the vehicle-side component can carry the device identifier and application scenario identifier in the permission verification request message sent to the business module, and the business module initiates the certificate verification process. The above-mentioned permission verification request message can be the third request message in method 300 or method 500, and the business module can be the second network device in method 300 or method 500.

[0356] Checking the status of a certificate can include at least one of the following methods:

[0357] (1) The certificate service module verifies the device certificate, that is, the cloud service module CA certificate verifies the legitimacy of the device certificate, checks whether the validity period of the device certificate is expired, and checks the current status of the device certificate (for example, ineffective, effective, frozen, revoked, etc.).

[0358] (2) The certificate service module verifies the message signature, that is, uses the device certificate to verify whether the message signature is valid.

[0359] (3) The certificate service module performs identity authentication, that is, the certificate service module checks whether the device identification and application scenario identification are valid and whether the certificate confirmation process is allowed.

[0360] (4) When the message signature and identity authentication are passed, the device certificate verification is completed, and the certificate status is not valid or valid, the certificate check passes; otherwise, the certificate check fails.

[0361] Optionally, if the certificate check fails, the certificate service module may prompt the vehicle-side component that the certificate is invalid.

[0362] It should be understood that the above process of checking the status of the device certificate is a process of verifying the second device certificate in method 300 .

[0363] S903: The certificate service module refreshes the certificate status.

[0364] Specifically, this step is only executed if the certificate status check passes and the certificate status is invalid. When executed, the certificate status will be refreshed from invalid to valid. At the same time, the certificate service module can switch the valid certificate corresponding to the device identifier and application scenario identifier to revoked status.

[0365] After checking the status of the certificate, the certificate service module may return a check result of the new device certificate to the business module. The check result may be the certificate verification result in method 300 .

[0366] S904: The vehicle-side component processes the local device certificate according to the business processing result.

[0367] Specifically, the business module can combine the certificate module's check result on the new device certificate to determine whether the vehicle-side component has the authority to handle a certain business, and send the authority verification result to the vehicle-side component. The vehicle-side component can process the locally stored device certificate based on the authority verification result. Specifically, it can include the following three situations:

[0368] (1) If the result of the permission verification is successful and the device certificate used this time has been used for business (when the certificate is in the effective state), the vehicle-side component will keep the certificate unchanged and continue to use the certificate for business processing.

[0369] (2) If the result of the authority verification is successful and the certificate used this time has not been used for business (when the certificate is in an ineffective state), the vehicle-side component will switch the certificate to the certificate used for business processing. The old certificate can be retained locally for a period of time or deleted directly, and the certificate confirmed this time will be used to process business in the future.

[0370] (3) If the permission verification result fails and the certificate service module returns that the certificate is invalid, the vehicle side can prompt the user or manufacturer to restore the service and certificate.

[0371] In this embodiment of the present application, the vehicle-side component can directly use the new device certificate that has not yet been validated for business processing, and the vehicle-side component can determine the use policy of the new and old certificates based on the verification results of the business permissions. In this way, the vehicle-side component can save the information exchange process with the certificate service module and improve business processing efficiency.

[0372] An embodiment of the present application also provides an apparatus for implementing any of the above methods, which includes a unit for implementing each step performed by the vehicle, the first network device or the second network device in any of the above methods.

[0373] Figure 10 is a schematic diagram of a communication device 1000 provided in an embodiment of the present application. The device 1000 may include a transceiver unit 1010, a storage unit 1020, and a processing unit 1030. The transceiver unit 1010 is used to receive or send instructions and / or data. The transceiver unit 1010 may also be referred to as a communication interface or a communication unit. The storage unit 1020 is used to implement a corresponding storage function and store corresponding instructions and / or data. The processing unit 1030 is used to perform data processing. The processing unit 1030 can read the instructions and / or data in the storage unit so that the device 1000 implements the aforementioned communication method.

[0374] As a design, the device 1000 is used to execute the actions performed by the vehicle in the above method embodiment.

[0375] As a design, the device 1000 may include: a transceiver unit 1010; the transceiver unit 1010 is used to: send a first request message to a first network device, the first request message is used to request the first network device to issue a device certificate, the first request message includes: a device identifier and an application scenario identifier, the device identifier is used to identify a vehicle and / or components included in the vehicle, the application scenario identifier is used to identify a usage scenario of the first device certificate, the first device certificate is a certificate used when the vehicle performs a first business; receive a first response message sent by the first network device, the first response message includes a second device certificate, the second device certificate is associated with the device identifier and the application scenario identifier, and the second device certificate is used to process the first business.

[0376] In a possible implementation, the apparatus further includes: a processing unit 1030; the processing unit 1030 is configured to process the first service using the first device certificate or the second device certificate.

[0377] In one possible implementation, the transceiver unit 1010 is also used to: send a second request message to the first network device, where the second request message is used to request the first network device to verify the second device certificate; and receive a second response message sent by the first network device, where the second response message includes a verification result of the second device certificate associated with the device identifier and the application scenario identifier.

[0378] In a possible implementation, the second request message includes: a second device certificate, a device identifier, and an application scenario identifier.

[0379] In one possible implementation, when the verification result of the second device certificate is successful and the vehicle uses the first device certificate to process the first service, the processing unit 1030 is specifically configured to switch the first device certificate to the second device certificate to process the first service.

[0380] In a possible implementation, when the verification result of the second device certificate is successful and the vehicle uses the second device certificate to process the first service, the processing unit 1030 is specifically configured to continue using the second device certificate to process the first service.

[0381] In a possible implementation, when the verification result of the second device certificate is verification failure, the processing unit 1030 is specifically configured to use the first device certificate to process the first service.

[0382] In a possible implementation, when the verification result of the second device certificate is verification failure, the processing unit 1030 is further configured to prompt the user that the second device certificate cannot be used.

[0383] In one possible implementation, the processing unit 1030 is also used to determine whether the locally stored private key matches the public key of the second device certificate; the transceiver unit 1010 is also used to send a second request message to the first network device when the locally stored private key matches the public key of the second device certificate.

[0384] In one possible implementation, the transceiver unit 1010 is also used to: send a third request message to the second network device, where the third request message is used to request the second network device to verify whether the vehicle has the authority to perform the first business, and the third request message includes at least one of the following: a second device certificate, a device identifier, and an application scenario identifier; and receive a third response message sent by the second network device, where the third response message is used to indicate the result of the authority verification of the vehicle.

[0385] In one possible implementation, when the authority verification result shows that the vehicle has the authority to perform the first business and the vehicle uses the first device certificate to process the first business, the processing unit 1030 is specifically used to switch the first device certificate to the second device certificate to process the first business.

[0386] In one possible implementation, when the authority verification result shows that the vehicle has the authority to perform the first business and the vehicle uses the second device certificate to process the first business, the processing unit 1030 is specifically used to continue using the second device certificate to process the first business.

[0387] In a possible implementation, when the authority verification result is that the vehicle does not have the authority to perform the first service, the processing unit 1030 is specifically configured to use the first device certificate to process the first service.

[0388] As a design, the device 1000 may include: a transceiver unit 1010, the transceiver unit 1010 is used to: send a second request message to the first network device, the second request message is used to request the first network device to verify the second device certificate; receive a second response message sent by the first network device, the second response message includes the verification result of the second device certificate associated with the device identifier and the application scenario identifier; wherein the device identifier is used to identify the vehicle and / or the components included in the vehicle, and the application scenario identifier is used to identify the usage scenario of the first device certificate, and the first device certificate is the certificate used when the vehicle performs the first business.

[0389] In a possible implementation, the second request message includes: a second device certificate, a device identifier, and an application scenario identifier.

[0390] In a possible implementation, the apparatus further includes a processing unit 1030, where the processing unit 1030 is configured to process the first service using the first device certificate or the second device certificate.

[0391] In one possible implementation, when the verification result of the second device certificate is successful and the vehicle uses the first device certificate to process the first service, the processing unit 1030 is specifically configured to switch the first device certificate to the second device certificate to process the first service.

[0392] In a possible implementation, when the verification result of the second device certificate is successful and the vehicle uses the second device certificate to process the first service, the processing unit 1030 is specifically configured to continue using the second device certificate to process the first service.

[0393] In a possible implementation, when the verification result of the second device certificate is verification failure, the processing unit 1030 is specifically configured to use the first device certificate to process the first service.

[0394] In a possible implementation, the processing unit 1030 is further configured to prompt the user that the second device certificate cannot be used.

[0395] In one possible implementation, the processing unit 1030 is also used to determine whether the locally stored private key matches the public key of the second device certificate; the transceiver unit 1010 is specifically used to send a second request message to the first network device when the locally stored private key matches the public key of the second device certificate.

[0396] As a design, the device 1000 may include: a transceiver unit 1010, which is used to: send a third request message to the second network device, the third request message is used to request the second network device to verify whether the vehicle has the authority to perform the first business, the third request message includes at least one of the following: a second device certificate, a device identifier and an application scenario identifier; the second device certificate is used to process the first business, the device identifier is used to identify the vehicle and / or components included in the vehicle, and the application scenario identifier is used to identify the usage scenario of the first device certificate, and the first device certificate is the certificate used by the vehicle when performing the first business; receive a third response message sent by the second network device, and the third response message is used to indicate the authority verification result of the vehicle.

[0397] In a possible implementation, the apparatus 1000 further includes a processing unit 1030 , where the processing unit 1030 is configured to process the first service using the first device certificate or the second device certificate.

[0398] In one possible implementation, when the authority verification result shows that the vehicle has the authority to perform the first business and the vehicle uses the first device certificate to process the first business, the processing unit 1030 is specifically used to switch the first device certificate to the second device certificate to process the first business.

[0399] In one possible implementation, when the authority verification result shows that the vehicle has the authority to perform the first business and the vehicle uses the second device certificate to process the first business, the processing unit 1030 is specifically configured to continue using the second device certificate to process the first business.

[0400] In a possible implementation, when the authority verification result is that the vehicle does not have the authority to perform the first service, the processing unit 1030 is specifically configured to use the first device certificate to process the first service.

[0401] As a design, the apparatus 1000 is used to execute the actions performed by the first network device in the above method embodiment.

[0402] As a design, the device 1000 may include: a transceiver unit 1010 and a processing unit 1030; the transceiver unit 1010 is used to receive a first request message sent by a vehicle, the first request message is used to request a first network device to issue a device certificate, the first request message includes a device identifier and an application scenario identifier, the device identifier is used to identify the vehicle and / or components included in the vehicle, the application scenario identifier is used to identify the usage scenario of the first device certificate, the first device certificate is a certificate used by the vehicle to perform a first business; the processing unit 1030 is used to determine a second device certificate based on the device identifier and the application scenario identifier; the transceiver unit 1010 is also used to send a first response message to the vehicle, the first response message includes a second device certificate, and the second device certificate is used to process the first business.

[0403] In one possible implementation, the transceiver unit 1010 is also used to receive a second request message sent by the first device, where the second request message is used to request the first network device to verify the second device certificate, where the first device includes a vehicle or a second network device; the processing unit 1030 is also used to determine the verification result of the second device certificate based on the device identifier and the application scenario identifier; the transceiver unit 1010 is also used to send a second response message to the first device, where the second response message is used to indicate the verification result of the second device certificate.

[0404] In a possible implementation, the second request message includes: a second device certificate, a device identifier, and an application scenario identifier.

[0405] In a possible implementation, the processing unit 1030 is specifically configured to: verify the validity of the device identifier and the application scenario identifier; and if the device identifier and the application scenario identifier are valid, determine that the verification result of the second device certificate is successful.

[0406] In a possible implementation, the processing unit 1030 is specifically configured to verify whether the device identifier is consistent with a device identifier preset in the first network device, and whether the application scenario identifier is consistent with an application scenario identifier preset in the first network device.

[0407] In a possible implementation, the processing unit 1030 is further configured to maintain the status of the first device certificate in a valid state.

[0408] In a possible implementation, the second request message further includes: a message signature; and the processing unit 1030 is further configured to verify the validity of the message signature using the second device certificate.

[0409] In a possible implementation, the application scenario identifier includes at least one of the following: a character string, a readable name, and a digital ID.

[0410] As a design, the device 1000 may include: a transceiver unit 1010 and a processing unit 1030, the transceiver unit 1010 is used to receive a second request message sent by a first device, the second request message is used to request the first network device to verify the second device certificate, the first device includes a carrier or a second network device; the processing unit 1030 is used to determine the verification result of the second device certificate based on the device identifier and the application scenario identifier; the transceiver unit 1010 is also used to send a second response message to the first device, the second response message is used to indicate the verification result of the second device certificate.

[0411] In a possible implementation, the second request message includes: a second device certificate, a device identifier, and an application scenario identifier.

[0412] In a possible implementation, the processing unit 1030 is specifically configured to: verify the validity of the device identifier and the application scenario identifier; and if the device identifier and the application scenario identifier are valid, determine that the verification result of the second device certificate is successful.

[0413] In a possible implementation, the processing unit 1030 is specifically configured to verify whether the device identifier is consistent with a device identifier preset in the first network device, and whether the application scenario identifier is consistent with an application scenario identifier preset in the first network device.

[0414] In a possible implementation, the processing unit 1030 is further configured to maintain the status of the first device certificate in a valid state.

[0415] In a possible implementation, the second request message further includes: a message signature; and the processing unit 1030 is further configured to verify the validity of the message signature using the second device certificate.

[0416] In a possible implementation, the application scenario identifier includes at least one of the following: a character string, a readable name, and a digital ID.

[0417] As a design, the apparatus 1000 is used to execute the actions performed by the second network device in the above method embodiment.

[0418] As a design, the device 1000 includes: a transceiver unit 1010 and a processing unit 1030; the transceiver unit 1010 is used to: receive a third request message sent by the vehicle, the third request message is used to request the second network device to verify whether the vehicle has the authority to perform the first business, the third request message includes at least one of the following: a second device certificate, a device identifier and an application scenario identifier, the second device certificate is used to process the first business, the device identifier is used to identify the vehicle and / or the components included in the vehicle, the application scenario identifier is used to identify the usage scenario of the first device certificate, and the first device certificate is The certificate used by the vehicle when performing the first business; sending a second request message to the first network device, the second request message is used to request the first network device to verify the second device certificate, the second request message includes the second device certificate, the device identifier and the application scenario identifier; receiving a second response message sent by the first network device, the second response message includes the verification result of the second device certificate associated with the device identifier and the application scenario identifier; the processing unit 1030 is used to send a third response message to the vehicle according to the verification result of the second device certificate, and the third response message is used to indicate the authority verification result of the vehicle.

[0419] In a possible implementation, when the verification result of the second certificate is successful, the third response message is used to indicate that the vehicle has the authority to perform the first service.

[0420] Optionally, if the device 1000 is located in the vehicle 100 , the processing unit 1030 may be the processor 131 shown in FIG. 1 .

[0421] FIG11 is a schematic diagram of another communication device 1100 provided in an embodiment of the present application.

[0422] The communication device 1100 includes a memory 1110, a processor 1120, and a communication interface 1130. The memory 1110, processor 1120, and communication interface 1130 are connected via an internal connection path. The memory 1110 is used to store instructions, and the processor 1120 is used to execute the instructions stored in the memory 1110 to control the communication interface 1130 to obtain information or to cause the communication device to execute the communication methods described in the above embodiments. Optionally, the memory 1110 can be coupled to the processor 1120 via an interface or integrated with the processor 1120.

[0423] It should be noted that the communication interface 1130 may be a transceiver device such as, but not limited to, a transceiver. The communication interface 1130 may also include an input / output interface.

[0424] The processor 1120 stores one or more computer programs, which include instructions. When the instructions are executed by the processor 1120, the communication device 1100 executes the communication methods in the above embodiments.

[0425] During implementation, each step of the above method can be completed by an integrated logic circuit of the hardware in the processor 1120 or by instructions in the form of software. The method disclosed in conjunction with the embodiments of the present application can be directly embodied as being executed by a hardware processor, or can be executed by a combination of hardware and software modules in the processor. The software module can be located in a mature storage medium in the art, such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory or an electrically erasable programmable memory, a register, etc. The storage medium is located in the memory 1110, and the processor 1120 reads the information in the memory 1110 and completes the steps of the above method in combination with its hardware. To avoid repetition, it will not be described in detail here.

[0426] Optionally, the communication interface 1130 in FIG. 11 may implement the transceiver unit 1010 in FIG. 10 , the memory 1110 in FIG. 11 may implement the storage unit 1020 in FIG. 10 , and the processor 1120 in FIG. 11 may implement the processing unit 1030 in FIG. 10 .

[0427] Optionally, the device 1000 or the device 1100 may be a computing platform, which may be an in-vehicle computing platform or a cloud computing platform.

[0428] Alternatively, the apparatus 1000 or the apparatus 1100 may be located in the vehicle 100 in FIG. 1 .

[0429] Optionally, the device 1000 or the device 1100 may be the computing platform 130 in the vehicle in FIG. 1 .

[0430] An embodiment of the present application further provides a computer-readable medium storing a program code. When the computer program code is executed on a computer, the computer executes any one of the methods in FIG. 3 to FIG. 9 .

[0431] An embodiment of the present application further provides a chip, comprising: a circuit, wherein the circuit is used to execute any one of the methods in FIG. 3 to FIG. 9 above.

[0432] An embodiment of the present application further provides a computer program product, which includes a computer program. When the computer program is executed, the computer executes any one of the methods in Figures 3 to 9 above.

[0433] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0434] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0435] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0436] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.

[0437] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

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

[0439] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.

Claims

1. A communication method, characterized in that: The method comprises: Sending a first request message to a first network device, where the first request message is used to request the first network device to issue a device certificate, the first request message including: a device identifier and an application scenario identifier, where the device identifier is used to identify a vehicle and / or components included in the vehicle, and the application scenario identifier is used to identify a usage scenario of the first device certificate, where the first device certificate is a certificate used by the vehicle to perform a first service; A first response message sent by a first network device is received, where the first response message includes the second device certificate, the second device certificate is associated with the device identifier and the application scenario identifier, and the second device certificate is used to process the first service.

2. The method according to claim 1, wherein The method further comprises: The first service is processed using the first device certificate or the second device certificate.

3. The method according to claim 2, wherein The method further comprises: Sending a second request message to the first network device, where the second request message is used to request the first network device to verify the second device certificate; A second response message sent by the first network device is received, where the second response message includes a verification result of the second device certificate associated with the device identifier and the application scenario identifier.

4. The method according to claim 3, wherein The second request message includes: the second device certificate, the device identifier, and the application scenario identifier.

5. The method according to claim 3 or 4, wherein: If the verification result of the second device certificate is successful, and the vehicle uses the first device certificate to process the first service, the using the first device certificate or the second device certificate to process the first service includes: The first device certificate is switched to the second device certificate, and the first service is processed.

6. The method according to claim 3 or 4, wherein: If the verification result of the second device certificate is successful, and the vehicle uses the second device certificate to process the first service, the using the first device certificate or the second device certificate to process the first service includes: Continue to use the second device certificate to process the first service.

7. The method according to claim 3 or 4, wherein: When the verification result of the second device certificate is verification failure, the using the first device certificate or the second device certificate to process the first service includes: The first service is processed using the first device certificate.

8. The method according to claim 7, wherein The method further comprises: The user is prompted that the second device certificate cannot be used.

9. The method according to any one of claims 3 to 8, wherein: Before sending the second request message to the first network device, the method further includes: Determining whether the locally stored private key matches the public key of the second device certificate; The sending the second request message to the first network device includes: In a case where the locally stored private key matches the public key of the second device certificate, the second request message is sent to the first network device.

10. The method according to claim 2, wherein The method further comprises: Sending a third request message to the second network device, the third request message being used to request the second network device to verify whether the vehicle has the authority to perform the first service, the third request message including at least one of the following: the second device certificate, the device identifier, and the application scenario identifier; A third response message sent by the second network device is received, where the third response message is used to indicate a result of the authority verification of the vehicle.

11. The method according to claim 10, wherein If the authority verification result is that the vehicle has the authority to perform the first service, and the vehicle uses the first device certificate to process the first service, the using the first device certificate or the second device certificate to process the first service includes: The first device certificate is switched to the second device certificate, and the first service is processed.

12. The method according to claim 10, wherein If the authority verification result is that the vehicle has the authority to perform the first service, and the vehicle uses the second device certificate to process the first service, the using the first device certificate or the second device certificate to process the first service includes: Continue to use the second device certificate to process the first service.

13. The method according to claim 10, wherein If the authority verification result is that the vehicle does not have the authority to perform the first service, the using the first device certificate or the second device certificate to process the first service includes: The first service is processed using the first device certificate.

14. A communication method, characterized in that: The method comprises: Receiving a first request message sent by a vehicle, where the first request message is used to request a first network device to issue a device certificate, the first request message including a device identifier and an application scenario identifier, the device identifier being used to identify the vehicle and / or components included in the vehicle, and the application scenario identifier being used to identify a usage scenario of the first device certificate, where the first device certificate is a certificate used by the vehicle to perform a first service; Determining a second device certificate according to the device identifier and the application scenario identifier; A first response message is sent to the vehicle, where the first response message includes the second device certificate, and the second device certificate is used to process the first service.

15. The method according to claim 14, wherein The method further comprises: receiving a second request message sent by a first device, wherein the second request message is used to request the first network device to verify the second device certificate, where the first device includes the vehicle or the second network device; Determining a verification result of the second device certificate according to the device identifier and the application scenario identifier; A second response message is sent to the first device, where the second response message is used to indicate a verification result of the second device certificate.

16. The method according to claim 15, wherein The second request message includes: the second device certificate, the device identifier, and the application scenario identifier.

17. The method according to claim 15 or 16, wherein: The determining, according to the device identifier and the application scenario identifier, a verification result of the second device certificate includes: Verifying the validity of the device identifier and the application scenario identifier; If the device identifier and the application scenario identifier are valid, it is determined that the verification result of the second device certificate is successful.

18. The method according to claim 17, wherein The verifying the validity of the device identifier and the application scenario identifier includes: Verify whether the device identifier is consistent with a device identifier preset in the first network device, and whether the application scenario identifier is consistent with an application scenario identifier preset in the first network device.

19. The method according to claim 17 or 18, wherein: The method further comprises: The status of the first device certificate is maintained as a valid state.

20. The method according to any one of claims 14 to 19, characterized in that The second request message further includes a message signature. Before determining the verification result of the second device certificate based on the device identifier and the application scenario identifier, the method further includes: The validity of the message signature is verified using the second device certificate.

21. The method according to any one of claims 14 to 20, characterized in that The application scenario identifier includes at least one of the following: a character string, a readable name, and a digital ID.

22. A communication method, characterized in that: The method comprises: Receive a third request message sent by a vehicle, where the third request message is used to request the second network device to verify whether the vehicle has the authority to perform the first service, and the third request message includes at least one of the following: a second device certificate, a device identifier, and an application scenario identifier, where the second device certificate is used to process the first service, the device identifier is used to identify the vehicle and / or components included in the vehicle, and the application scenario identifier is used to identify a usage scenario of the first device certificate, where the first device certificate is a certificate used by the vehicle to perform the first service; Sending a second request message to the first network device, where the second request message is used to request the first network device to verify the second device certificate, and the second request message includes the second device certificate, the device identifier, and the application scenario identifier; receiving a second response message sent by the first network device, where the second response message includes a verification result of the second device certificate associated with the device identifier and the application scenario identifier; According to the verification result of the second device certificate, a third response message is sent to the vehicle, where the third response message is used to indicate the authority verification result of the vehicle.

23. The method according to claim 22, wherein When the verification result of the second device certificate is successful, the third response message is used to indicate that the vehicle has the authority to perform the first service.

24. A communication device, characterized in that: The device comprises: a transceiver unit; The transceiver unit is used to: Sending a first request message to a first network device, where the first request message is used to request the first network device to issue a device certificate, the first request message including: a device identifier and an application scenario identifier, where the device identifier is used to identify a vehicle and / or components included in the vehicle, and the application scenario identifier is used to identify a usage scenario of the first device certificate, where the first device certificate is a certificate used by the vehicle to perform a first service; A first response message sent by a first network device is received, where the first response message includes the second device certificate, the second device certificate is associated with the device identifier and the application scenario identifier, and the second device certificate is used to process the first service.

25. A communication device, characterized in that: The device comprises: a transceiver unit and a processing unit; The transceiver unit is configured to receive a first request message sent by a vehicle, the first request message being used to request a first network device to issue a device certificate, the first request message including a device identifier and an application scenario identifier, the device identifier being used to identify the vehicle and / or components included in the vehicle, the application scenario identifier being used to identify a usage scenario of the first device certificate, the first device certificate being a certificate used by the vehicle when performing a first service; The processing unit is configured to determine a second device certificate based on the device identifier and the application scenario identifier; The transceiver unit is further configured to send a first response message to the vehicle, where the first response message includes the second device certificate, and the second device certificate is used to process the first service.

26. A communication device, characterized in that: The device comprises: a transceiver unit and a processing unit; The transceiver unit is used to: Receive a third request message sent by a vehicle, where the third request message is used to request the second network device to verify whether the vehicle has the authority to perform the first service, and the third request message includes at least one of the following: a second device certificate, a device identifier, and an application scenario identifier, where the second device certificate is used to process the first service, the device identifier is used to identify the vehicle and / or components included in the vehicle, and the application scenario identifier is used to identify a usage scenario of the first device certificate, where the first device certificate is a certificate used by the vehicle to perform the first service; Sending a second request message to the first network device, where the second request message is used to request the first network device to verify the second device certificate, and the second request message includes the second device certificate, the device identifier, and the application scenario identifier; receiving a second response message sent by the first network device, where the second response message includes a verification result of the second device certificate associated with the device identifier and the application scenario identifier; The processing unit is configured to send a third response message to the vehicle according to the verification result of the second device certificate, where the third response message is used to indicate the authority verification result of the vehicle.

27. A communication device, characterized in that: include: A processor and a memory, wherein the processor is coupled to the memory and is configured to read and execute instructions in the memory to perform the method according to any one of claims 1 to 13.

28. A communication device, characterized in that: include: A processor and a memory, wherein the processor is coupled to the memory and is configured to read and execute instructions in the memory to perform the method according to any one of claims 14 to 21.

29. A communication device, characterized in that: include: A processor and a memory, wherein the processor is coupled to the memory and is configured to read and execute instructions in the memory to perform the method according to claim 22 or 23.

30. A vehicle, characterized in that: include: A processor and a memory, wherein the processor is coupled to the memory and is configured to read and execute instructions in the memory to perform the method according to any one of claims 1 to 13.

31. The method of claim 30, wherein: The vehicle includes a vehicle.

32. A server, characterized in that: include: A processor and a memory, wherein the processor is coupled to the memory and is configured to read and execute instructions in the memory to perform the method according to any one of claims 14 to 21.

33. A server, characterized in that: include: A processor and a memory, wherein the processor is coupled to the memory and is configured to read and execute instructions in the memory to perform the method according to claim 22 or 23.

34. A computer-readable medium, characterized in that The computer-readable medium stores a program code, and when the computer program code is run on a computer, the computer is caused to perform the method according to any one of claims 1 to 23.

35. A computer program product, characterized in that The computer product comprises a computer program, which enables a computer to perform the method according to any one of claims 1 to 23 when the computer program is executed.

Images