WO2024113077A1 - 通信方法、装置以及运载工具 - Google Patents

通信方法、装置以及运载工具 Download PDF

Info

Publication number
WO2024113077A1
WO2024113077A1 PCT/CN2022/134607 CN2022134607W WO2024113077A1 WO 2024113077 A1 WO2024113077 A1 WO 2024113077A1 CN 2022134607 W CN2022134607 W CN 2022134607W WO 2024113077 A1 WO2024113077 A1 WO 2024113077A1
Authority
WO
WIPO (PCT)
Prior art keywords
certificate
vehicle
identifier
device certificate
service
Prior art date
Application number
PCT/CN2022/134607
Other languages
English (en)
French (fr)
Inventor
郭志鹏
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to PCT/CN2022/134607 priority Critical patent/WO2024113077A1/zh
Publication of WO2024113077A1 publication Critical patent/WO2024113077A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials

Definitions

  • Embodiments of the present application relate to the field of communications, and more specifically, to a communication method, device, and vehicle.
  • the device certificates stored in the vehicle components will inevitably expire, be revoked, etc., and there may even be a situation where the certificates are temporarily not allowed to be used due to business freezes. This requires the vehicle to have the ability to apply for certificates online and confirm the certificate status.
  • some solutions do not support the certificate status confirmation process, and although other solutions support the confirmation of certificate status, the entire certificate application and confirmation process is complex and has poor reliability, resulting in high retry costs.
  • the embodiments of the present application provide a communication method, device, and vehicle, which can reduce the information interaction between the vehicle and the network device during the certificate application and confirmation process, and reduce the complexity of the certificate application and confirmation process.
  • a communication method comprising: 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 comprising: 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 service; 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 to process the first service.
  • the first service may be a service currently being performed by the vehicle, and the first service 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 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.
  • the second device certificate may be an ineffective device certificate
  • the second device certificate being used to process the first service may be understood as the vehicle may use the second device certificate to process the first service.
  • the vehicle includes components including: an on-board gateway, a mobile data center, an intelligent cockpit data center, an on-board communication box, a sensor, an electronic control unit, and one or more of the vehicle dynamic control.
  • components including: an on-board gateway, a mobile data center, an intelligent cockpit data center, an on-board communication box, a sensor, an electronic control unit, and one or more of the vehicle dynamic control.
  • a device certificate can be understood as a certificate used by any of the above components when performing business.
  • the first network device may be a certificate service module.
  • the first network device can determine the second device certificate according to the device identifier and the application scenario identifier. In this way, during the process of the first network device issuing the second device certificate, there is no need to interact 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 the certificate application.
  • the method further includes: using the first device certificate or the second device certificate to process the first service.
  • the vehicle after receiving the second device certificate, the vehicle can use the first device certificate to process the first service, or use the second device certificate to process the first service. In this way, the vehicle can use the device certificate to process services in a more flexible manner.
  • the method also 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.
  • the second device certificate confirmation process can be quickly initiated, so that the vehicle can process the first business according to the verification result of the second device certificate.
  • the second request message includes: the second device certificate, the device identifier, and the application scenario identifier.
  • the use of the first device certificate or the second device certificate to process the first service includes: switching the first device certificate to the second device certificate to process the first service.
  • the vehicle when the vehicle confirms that the verification result of the certificate is successful and the vehicle is using the first device certificate, the vehicle can switch the first device certificate to the second device certificate to process the first service. In this way, the vehicle can use the confirmed new device certificate to process the service in a timely manner, thereby ensuring the security of the first service processing.
  • 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.
  • the vehicle when the vehicle confirms that the verification result of the certificate is successful and the vehicle has 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 processing efficiency of the first business.
  • using the first device certificate or the second device certificate to process the first service includes: using the first device certificate to process the first service.
  • the vehicle 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.
  • the method further includes: prompting a user that the second device certificate cannot be used.
  • the vehicle may prompt the user that the second device certificate cannot be used through a display screen or voice or other methods.
  • the vehicle in the process of repeating the certificate confirmation, if the certificate verification result of the second device certificate last time is successful, that is, the vehicle has used the second device certificate to process the first service.
  • the vehicle initiates the certificate confirmation process again, and the verification result of the second device certificate this time is a failure, the vehicle can prompt the user that the first service cannot be performed.
  • the method 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.
  • the carrier may prompt the user that the first service cannot be performed.
  • the matching principle of the private key and the certificate public key is: the certificate public key is actually an encrypted string, and anyone can see its content, while the content of the private key can only be known by the owner (vehicle).
  • the ciphertext encrypted by the public key can be decrypted using the paired private key, while the public key cannot decrypt the private key.
  • the private key stored locally by the vehicle can decrypt the public key of the certificate, it means that the private key matches the public key.
  • the vehicle before initiating the certificate confirmation process, 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 performed; if the private key stored in the vehicle and the public key of the second device certificate do not match, it can be determined that the second device certificate is unavailable without connecting to the Internet, and corresponding remedial measures can be taken in advance.
  • a third request message is sent 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 service, 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, the third response message is used to indicate the result of the authority verification of the vehicle.
  • the second network device may be a service module, which may verify whether the vehicle has the authority to process the first service.
  • the vehicle can carry the device identifier and/or the application scenario identifier in the third request message, so that the second network device can initiate the verification process of the second device certificate to the first network device.
  • 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 according to the verification result of the service authority.
  • the use of the first device certificate or the second device certificate to process the first service includes: switching the first device certificate to the second device certificate to process the first service.
  • the vehicle when the vehicle confirms that it has the authority to perform the first service and the vehicle is using the first device certificate, the vehicle can switch the first device certificate to the second device certificate to process the first service. In this way, the vehicle can use the confirmed new device certificate to process the service in a timely manner, 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.
  • 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.
  • the vehicle when the vehicle confirms that it has the authority to perform the first service and the vehicle has been using 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 processing efficiency of the first service, but also eliminates the signaling interaction process between the vehicle and the first network device.
  • using the first device certificate or the second device certificate to process the first service includes: using the first device certificate to process the first service.
  • the vehicle when the vehicle is confirmed to not have the authority to conduct 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.
  • a communication method comprising: receiving 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 comprising 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; determining a second device certificate based on the device identifier and the application scenario identifier; and sending a first response message to the vehicle, the first response message comprising the second device certificate, and the second device certificate being used to process the first service.
  • the first network device can receive the device identification and application scenario identification sent by the vehicle, and determine the second device certificate according to 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 interact with the vehicle again, and the vehicle does not need to modify specific parameters synchronously, which can reduce the complexity of the certificate application process and improve the efficiency of the certificate application.
  • the method also 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; and 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.
  • 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 service based on the verification result of the second device certificate.
  • the second request message includes: the second device certificate, the device identifier, and the application scenario identifier.
  • 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.
  • verifying 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.
  • the device identifier when 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, it can be confirmed that the device identifier and the application scenario identifier are valid, and the verification result of the second device certificate is successful.
  • 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, it can be confirmed that the verification result of the second device certificate is failed.
  • 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.
  • 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.
  • 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 further verifies the validity of the device identification and the application scenario identification.
  • the method further includes: maintaining the status of the first device certificate as a valid status.
  • the first network device may not switch the validity state of the first device certificate to a revoked state. In this way, the first device certificate and the second device certificate that have been valid can exist on the vehicle side at the same time, and the first device certificate and the second device certificate can back up each other. If one certificate is damaged, the other certificate can be used to process the service.
  • the application scenario identifier includes at least one of the following: a character string, a readable name, and a digital ID.
  • the 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;
  • the readable name can be understood as a word that can be understood by the user, and
  • the digital ID can be understood as a digital identifier.
  • a communication 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 service, 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 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 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 a verification result of the second device certificate associated with the device identifier and the application scenario identifier;
  • the second network device may be a service module, which may verify whether the vehicle has the authority to process the first service.
  • the third request message may not carry the application scenario identifier but only 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.
  • the third request message may not carry the application scenario identifier and the 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.
  • the second device certificate is a device certificate requested by the vehicle to be issued by the first network device.
  • the second device certificate may also be any device certificate, for example, the first device certificate mentioned above.
  • the second network device can obtain the device identification and application scenario identification from the permission verification request message sent by the vehicle, and initiate the verification process of the second device certificate to the first network device according to the device identification and application scenario identification.
  • 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 according to the verification result of the service authority.
  • the third response message when the verification result of the second device certificate is successful, is used to indicate that the vehicle has the authority to perform the first service.
  • the third response message may be used to indicate that the vehicle does not have the authority to perform the first service.
  • a communication method comprising: 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 comprising 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.
  • the second request message includes: the second device certificate, the device identifier, and the application scenario identifier.
  • the method 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.
  • the use of the first device certificate or the second device certificate to process the first service includes: switching the first device certificate to the second device certificate to process the first service.
  • 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.
  • using the first device certificate or the second device certificate to process the first service includes: using the first device certificate to process the first service.
  • the method further includes: prompting the user that the second device certificate cannot be used.
  • the method 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.
  • a communication 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.
  • the method 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.
  • 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.
  • 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.
  • 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.
  • a communication method comprising: receiving a second request message sent by a first device, the second request message being used to request the first network device to verify the second device certificate, the first device comprising a vehicle or a second network device; determining a verification result of the second device certificate based on a device identifier and an application scenario identifier; and sending a second response message to the first device, the second response message being used to indicate a verification result of the second device certificate.
  • the device identifier and the application scenario identifier have been pre-stored in the first network device.
  • the first network device can determine the verification result of the second device certificate based on the stored device identifier and application scenario identifier.
  • the second request message includes: the second device certificate, the device identifier, and the application scenario identifier.
  • 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.
  • 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.
  • the method further includes: maintaining the status of the first device certificate in a valid state.
  • 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.
  • the application scenario identifier includes at least one of the following: a character string, a readable name, and a digital ID.
  • a communication 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 service, 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 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 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 a verification result of the second device certificate associated with the device identifier and the application scenario identifier
  • the third response message is used to indicate that the vehicle has the authority to perform the first service.
  • a communication device comprising: 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 a usage scenario of the first device certificate, the first device certificate is a certificate used by the vehicle to perform a first service; 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 service.
  • the device also includes: a processing unit; the processing unit is used to use the first device certificate or the second device certificate to process the first business.
  • the transceiver unit is also 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 a verification result of the second device certificate associated with the device identifier and the application scenario identifier.
  • the second request message includes: the second device certificate, the device identifier, and the application scenario identifier.
  • the processing unit 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 is specifically used to switch the first device certificate to the second device certificate to process the first service.
  • the processing unit 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.
  • the processing unit when the verification result of the second device certificate is verification failure, the processing unit is specifically used to use the first device certificate to process the first service.
  • the processing unit when the verification result of the second device certificate is verification failure, the processing unit is further used to prompt the user that the second device certificate cannot be used.
  • 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 also 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.
  • the transceiver unit is also used to: send 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; and receive 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.
  • the processing unit 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.
  • the processing unit 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.
  • the processing unit when the authority verification result is that the vehicle does not have the authority to perform the first service, the processing unit is specifically used to use the first device certificate to process the first service.
  • a communication device comprising: 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, the first device certificate is a certificate used by the vehicle to perform 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.
  • the transceiver unit is further 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 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, and the second response message is used to indicate the verification result of the second device certificate.
  • the second request message includes: the second device certificate, the device identifier, and the application scenario identifier.
  • 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.
  • 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.
  • the processing unit is further used to maintain the status of the first device certificate in a valid state.
  • 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.
  • the application scenario identifier includes at least one of the following: a character string, a readable name, and a digital ID.
  • a communication device 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 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 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 service; 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
  • the third response message is used to indicate that the vehicle has the authority to perform the first service.
  • a communication device 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 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, and the first device certificate is a certificate used by the vehicle to perform a first business.
  • the second request message includes: the second device certificate, the device identifier, and the application scenario identifier.
  • 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.
  • the processing unit 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 is specifically used to switch the first device certificate to the second device certificate to process the first service.
  • the processing unit 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.
  • the processing unit when the verification result of the second device certificate is verification failure, is specifically configured to use the first device certificate to process the first service.
  • the processing unit is further used to prompt the user that the second device certificate cannot be used.
  • 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.
  • a communication device comprising a transceiver unit, the transceiver unit being used to: send 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 is used to process the first service, 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 being the certificate used by the vehicle when performing the first service; and receive 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.
  • 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.
  • the processing unit 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.
  • the processing unit 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.
  • the processing unit when the authority verification result is that the vehicle does not have the authority to perform the first service, the processing unit is specifically used to use the first device certificate to process the first service.
  • a communication device 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, 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 according to 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.
  • the second request message includes: the second device certificate, the device identifier and the application scenario identifier.
  • 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.
  • 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.
  • the processing unit is further used to maintain the status of the first device certificate in a valid state.
  • 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.
  • the application scenario identifier includes at least one of the following: a character string, a readable name, and a digital ID.
  • a communication device 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 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, 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 service; 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
  • the third response message is used to indicate that the vehicle has the authority to perform the first service.
  • a communication device 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 in the first to seventh aspects above.
  • a computer-readable medium stores a program code, and when the computer program code runs on a computer, the computer executes a method of any one of the implementation modes of the first to seventh aspects above.
  • a computer program product is provided, wherein the computer product includes a computer program, and when the computer program is executed, the computer executes a method implemented in any one of the first to seventh aspects.
  • a chip comprising: a circuit, the circuit being used to execute a method of any one of the implementation modes in the first to seventh aspects above.
  • a vehicle 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 modes of the first aspect, the fourth aspect or the fifth aspect mentioned above.
  • the vehicle is a vehicle.
  • a server 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 modes of the second aspect, the third aspect, the sixth aspect, and the seventh aspect.
  • FIG1 is a functional schematic diagram of a vehicle provided in an embodiment of the present application.
  • FIG2 is a system architecture applicable to the communication method provided in an embodiment of the present application.
  • FIG3 is a schematic flow chart of a communication method provided in an embodiment of the present application.
  • FIG4 is a schematic flow chart of another communication method provided in an embodiment of the present application.
  • FIG5 is a schematic flow chart of another communication method provided in an embodiment of the present application.
  • FIG6 is a schematic flow chart of another communication method provided in an embodiment of the present application.
  • FIG7 is a schematic flow chart of another communication method provided in an embodiment of the present application.
  • FIG8 is a schematic flow chart of another communication method provided in an embodiment of the present application.
  • FIG9 is a schematic flow chart of another communication method provided in an embodiment of the present application.
  • FIG10 is a communication device provided in an embodiment of the present application.
  • FIG. 11 is another communication device provided in an embodiment of the present application.
  • Fig. 1 is a functional schematic diagram of a vehicle 100 provided in an embodiment of the present application. It should be understood that Fig. 1 and the related description are only examples and do not limit the vehicle in the embodiment of the present application.
  • the vehicle 100 may include a variety of subsystems, such as a sensing system 120 and a computing platform 130.
  • the vehicle 100 may include more or fewer subsystems, and each subsystem may include one or more components.
  • each subsystem and component of the vehicle 100 may be interconnected by wire or wirelessly.
  • the perception system 120 may include several sensors for sensing information about the environment around the vehicle 100.
  • 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 device.
  • IMU inertial measurement unit
  • the computing platform 130 may include processors 131 to 13n (n is a positive integer).
  • the processor is a circuit with signal processing capability.
  • the processor may be a circuit with instruction reading and execution capability, 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).
  • CPU central processing unit
  • GPU graphics processing unit
  • DSP digital signal processor
  • the processor may implement certain functions through the logical relationship of a hardware circuit, and the logical relationship of the hardware circuit is fixed or reconfigurable, such as a hardware circuit implemented by a processor such as an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), such as an FPGA.
  • ASIC application-specific integrated circuit
  • PLD programmable logic device
  • the process of the processor loading a configuration document 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.
  • the processor may also be a hardware circuit designed for artificial intelligence, which may 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.
  • the computing platform 130 may also include a memory, the memory is used to store instructions, and some or all of the processors 131 to 13n may call instructions in the memory to implement corresponding functions.
  • Computing platform 130 may control functions of vehicle 100 based on input received from various subsystems (eg, perception system 120). In some embodiments, computing platform 130 may be used to provide control over many aspects of vehicle 100 and its subsystems.
  • FIG. 1 should not be understood as a limitation on the embodiments of the present application.
  • the vehicle 100 in the present application may include: road vehicles, water vehicles, air vehicles, industrial equipment, agricultural equipment, or entertainment equipment, etc.
  • the vehicle 100 may be a vehicle, which is a vehicle in a broad sense, and may be a 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 embodiment of the present application does not specifically limit the type of vehicle.
  • the vehicle 100 may be a vehicle such as an airplane or a ship.
  • vehicle-side identity authentication and authorization are required to ensure the authenticity of the identity of the communication subject and the legitimacy of the business permissions. For example, it is necessary to authenticate whether the vehicle has the permissions for vehicle-side logs, data upload to the cloud, vehicle to everything (V2X) communication, and secure data transmission in the vehicle.
  • V2X vehicle to everything
  • the device certificates stored in the vehicle components will inevitably expire, be revoked, etc., and there may even be a situation where the certificates are temporarily not allowed to be used due to business freezes.
  • some solutions do not support certificate status confirmation, and the vehicle can only discover certificate anomalies during business processing, which increases the difficulty of handling business anomalies.
  • Another part of the solutions supports the certificate status confirmation process, multiple information interactions are required during the entire certificate application and confirmation process, and any interruption in any step will cause the process to be interrupted, and the certificate application or confirmation process can only be restarted.
  • the entire certificate application or confirmation process is complex, unreliable, and has a high retry cost.
  • the vehicle needs to interact with the certificate service module multiple times, and the vehicle needs to modify specific parameters (for example, server address, etc.) according to the instructions of the certificate service module.
  • specific parameters for example, server address, etc.
  • 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.
  • FIG2 is a system architecture applicable to the communication method provided in an embodiment of the present application.
  • the system architecture involves an interactive system between vehicle-side components/vehicles and external digital certificate service modules.
  • 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), smart cockpit data center (CDC), telematics box (T-box), sensor, electronic control unit (ECU), vehicle dynamic control (VDC), etc.
  • the digital certificate service module and the vehicle can exchange information through the wireless communication channel.
  • 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.
  • a vehicle sends 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 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 a certificate used by the vehicle to perform the first business.
  • the first service may be a service currently being performed by the vehicle, and the first service may include: sensor data upload, software upgrade, or map download, etc.
  • the first service may have a corresponding relationship with the application scenario identifier.
  • the application scenario identifier may be used to identify that the usage scenario of the first device certificate is a software upgrade scenario.
  • the components of the vehicle may include: one or more of: an onboard gateway, a mobile data center, an intelligent cockpit data center, an onboard communication box, a sensor, an electronic control unit, and a vehicle dynamic control.
  • an onboard gateway a mobile data center
  • an intelligent cockpit data center a mobile data center
  • an onboard communication box a sensor
  • an electronic control unit a vehicle dynamic control.
  • a device certificate may be understood as a certificate used by any of the above components to conduct business.
  • the first network device may be a certificate service module.
  • the 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;
  • the readable name can be understood as a word that can be understood by the user, and
  • the digital ID can be understood as a digital identifier.
  • the first network device determines a second device certificate according to the device identifier and the application scenario identifier.
  • the vehicle receives a first response message sent by the first network device.
  • 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.
  • the second device certificate may be an ineffective device certificate, and the use of the second device certificate to process the first business can be understood as the vehicle can use the second device certificate to process the first business.
  • the first network device can determine the second device certificate according to the device identifier and the application scenario identifier. In this way, during the process of the first network device issuing the second device certificate, there is no need to interact 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 the certificate application.
  • the method further includes: the vehicle uses the first device certificate or the second device certificate to process the first service.
  • the vehicle after receiving the second device certificate, the vehicle can use the first device certificate to process the first service, or use the second device certificate to process the first service. In this way, the vehicle can use the device certificate to process services in a more flexible manner.
  • the vehicle After applying for the second device certificate, the vehicle can directly initiate a certificate confirmation process to the first network device.
  • the method also includes: the vehicle sends 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 vehicle receives a second response message sent by the first network device, the second response message includes a verification result of the second device certificate associated with the device identifier and the application scenario identifier.
  • the second request message may include: a second device certificate, a device identifier and an application scenario identifier.
  • the second device certificate confirmation process can be quickly initiated, so that the vehicle can process the first business according to the verification result of the second device certificate.
  • 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.
  • the first network device may 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.
  • 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 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.
  • 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.
  • the second request message may further include: a message signature.
  • the method further includes: the first network device uses the second device certificate to verify the validity of the message signature.
  • 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 further verifies the validity of the device identification and the application scenario identification.
  • the first network device after confirming that the second device certificate is successfully verified, maintains the status of the first device certificate as a valid status.
  • the first network device may not switch the validity state of the first device certificate to a revoked state. In this way, the first device certificate and the second device certificate that have been valid can exist on the vehicle side at the same time, and the first device certificate and the second device certificate can back up each other. If one certificate is damaged, the other certificate can be used to process the service.
  • the method 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.
  • the carrier may prompt the user that the first service cannot be performed.
  • the matching principle of the private key and the certificate public key is: the certificate public key is actually an encrypted string, and anyone can see its content, while the content of the private key can only be known by the owner (vehicle).
  • the ciphertext encrypted by the public key can be decrypted using the paired private key, while the public key cannot decrypt the private key.
  • the private key stored locally by the vehicle can decrypt the public key of the certificate, it means that the private key matches the public key.
  • the vehicle before initiating the certificate confirmation process, 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 performed; if the private key stored in the vehicle and the public key of the second device certificate do not match, it can be determined that the second device certificate is unavailable without connecting to the Internet, and corresponding remedial measures can be taken in advance.
  • the vehicle After receiving the verification result of the second certificate, the vehicle can perform different processing in combination with the current certificate usage of the vehicle.
  • 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.
  • the vehicle when the vehicle confirms that the verification result of the certificate is successful and the vehicle is using the first device certificate, the vehicle can switch the first device certificate to the second device certificate to process the first service. In this way, the vehicle can use the confirmed new device certificate to process the service in a timely manner, thereby ensuring the security of the first service processing.
  • 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.
  • the vehicle when the vehicle confirms that the verification result of the certificate is successful and the vehicle has 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 processing efficiency of the first business.
  • 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.
  • the carrier may also prompt the user that the second device certificate cannot be used.
  • the vehicle may prompt the user that the second device certificate cannot be used through a display screen or voice or other methods.
  • the vehicle in the process of repeating the certificate confirmation, if the certificate verification result of the second device certificate last time is successful, that is, the vehicle has used the second device certificate to process the first service.
  • the vehicle initiates the certificate confirmation process again, and the verification result of the second device certificate this time is a failure, the vehicle can prompt the user that the first service cannot be performed.
  • the vehicle 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.
  • 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.
  • 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, 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, the third response message is used to indicate the result of the vehicle's authority verification.
  • the second network device may be a service module, which may verify whether the vehicle has the authority to process the first service.
  • the vehicle can carry the device identifier and/or the application scenario identifier in the third request message, so that the second network device can initiate the verification process of the second device certificate to the first network device.
  • 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 according to the verification result of the service authority.
  • the vehicle After receiving the authority verification result, the vehicle can perform different processing based on the current certificate usage of the vehicle.
  • 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.
  • the vehicle when the vehicle confirms that it has the authority to perform the first service and the vehicle is using the first device certificate, the vehicle can switch the first device certificate to the second device certificate to process the first service. In this way, the vehicle can use the confirmed new device certificate to process the service in a timely manner, 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.
  • 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.
  • the vehicle when the vehicle confirms that it has the authority to perform the first service and the vehicle has been using 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 processing efficiency of the first service, but also eliminates the signaling interaction process between the vehicle and the first network device.
  • 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.
  • the vehicle when the vehicle is confirmed to not have the authority to conduct 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.
  • 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.
  • a vehicle sends a second request message to a 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 may include: a second device certificate, a device identifier and an application scenario identifier.
  • the first network device may be a certificate service module.
  • the method before step S401, further includes: the carrier determines whether the locally stored private key matches the public key of the second device certificate; and sends a second request message to the first network device if the locally stored private key matches the public key of the second device certificate.
  • the carrier may prompt the user that the first service cannot be performed.
  • the first network device verifies the second device certificate according to the device identifier and the application scenario identifier.
  • the first network device may 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.
  • 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 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.
  • the second request message may further include: a message signature, and before step S402, the first network device verifies the validity of the message signature using the second device certificate based on the device identifier and the application scenario identifier. In this way, if the message signature is valid, the first network device further verifies the validity of the device identifier and the application scenario identifier.
  • the vehicle receives a second response message sent by the first network device.
  • the second response message includes a verification result of the second device certificate associated with the device identifier and the application scenario identifier.
  • 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.
  • the method before step S401, further includes: the vehicle uses 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.
  • 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.
  • the vehicle when the vehicle confirms that the verification result of the certificate is successful and the vehicle is using the first device certificate, the vehicle can switch the first device certificate to the second device certificate to process the first service. In this way, the vehicle can use the confirmed new device certificate to process the service in a timely manner, thereby ensuring the security of the first service processing.
  • the method further includes: when the verification result of the second device certificate is successful verification, 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.
  • the vehicle when the vehicle confirms that the verification result of the certificate is successful and the vehicle has 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 processing efficiency of the first business.
  • 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.
  • the carrier may also prompt the user that the second device certificate cannot be used.
  • the vehicle may prompt the user that the second device certificate cannot be used through a display screen or voice or other methods.
  • the vehicle in the process of repeating the certificate confirmation, if the certificate verification result of the second device certificate last time is successful, that is, the vehicle has used the second device certificate to process the first service.
  • the vehicle initiates the certificate confirmation process again, and the verification result of the second device certificate this time is a failure, the vehicle can prompt the user that the first service cannot be performed.
  • FIG5 is a schematic flow chart of a communication method provided in an embodiment of the present application.
  • Method 500 may be applied to the system architecture of FIG2 .
  • Method 500 may also be applied to the business authority verification process in method 300 .
  • Method 500 may include the following steps.
  • 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 service.
  • the third request message includes at least one of the following contents: 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 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 when performing the first service.
  • the third request message may not carry the application scenario identifier but only 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.
  • the third request message may not carry the application scenario identifier and the 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.
  • the second network device sends a second request message to the first network device.
  • the second request message is used by the first network device to verify the second device certificate.
  • the second request message may include: a second device certificate, a device identifier, and an application scenario identifier.
  • the first network device verifies the second device certificate according to the device identifier and the application scenario identifier.
  • the first network device may 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.
  • 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.
  • the second request message may further include: a message signature, and before step S503, the first network device verifies the validity of the message signature using the second device certificate based on the device identifier and the application scenario identifier. In this way, if the message signature is valid, the first network device further verifies the validity of the device identifier and the application scenario identifier.
  • S504 The second network device receives a second response message sent by the first network device.
  • the second response message includes a verification result of the second device certificate associated with the device identifier and the application scenario identifier.
  • S505 The vehicle receives a third response message sent by the second network device.
  • the third response message is used to indicate the result of the authority verification of the vehicle.
  • the third response message may indicate that the vehicle has the authority to perform the first service.
  • the third response message may indicate that the vehicle does not have the authority to perform the first service.
  • the second network device can obtain the device identification and application scenario identification from the permission verification request message sent by the vehicle, and initiate the verification process of the second device certificate to the first network device according to the device identification and application scenario identification.
  • 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 according to the verification result of the service authority.
  • the vehicle After receiving the third response message, the vehicle can perform different processing according to the authority verification result and the current usage of the device certificate of the vehicle.
  • 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.
  • the vehicle when the vehicle confirms that it has the authority to perform the first service and the vehicle is using the first device certificate, the vehicle can switch the first device certificate to the second device certificate to process the first service. In this way, the vehicle can use the confirmed new device certificate to process the service in a timely manner, 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.
  • 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.
  • the vehicle when the vehicle confirms that it has the authority to perform the first service and the vehicle has been using 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 processing efficiency of the first service, but also eliminates the signaling interaction process between the vehicle and the first network device.
  • 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.
  • the vehicle when the vehicle is confirmed to not have the authority to conduct 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.
  • FIG6 is a schematic flow chart 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.
  • 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 subsequent steps. Among them, other required conditions may include: vehicle operating status and/or user confirmation. For example, when the vehicle is parked, the vehicle prompts the user that a certificate application is required. After the user confirms on the vehicle display, the vehicle-side component can initiate the certificate application process.
  • the vehicle-end component may perform the certificate check periodically.
  • the vehicle-end component may perform the certificate check every time the vehicle is started or at a specific time every day.
  • vehicle-side components may 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 vehicle dynamic control.
  • the vehicle-side component generates a certificate application document.
  • 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.
  • the vehicle-side component sends a certificate application request message to the certificate service module.
  • the vehicle-side component can send a certificate application request message to the certificate service module, and 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 certificate application message can be the first request message in method 300.
  • the device identifier is used to identify the vehicle-side components; the application scenario identifier can be assigned by the business 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 of 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 through the private key of the device certificate.
  • 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-side and the certificate service module, which is convenient for 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, which is convenient for traffic forwarding), etc.
  • the certificate service module authenticates the vehicle's identity.
  • the certificate service module may authenticate the identity of the vehicle end according to the certificate application request message, which may include at least one of the following methods:
  • the certificate service module uses the Certificate Authority (CA) certificate to verify the legitimacy of the device certificate, check whether the device certificate has expired, and check whether the device certificate is in a valid state.
  • CA Certificate Authority
  • the certificate service module uses the device certificate to verify whether the signature of the certificate application request message is valid.
  • 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.
  • the certificate service module may be the first network device in method 300 .
  • the certificate service module issues a new device certificate according to the device identifier and the application scenario identifier.
  • 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.
  • 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.
  • the certificate service module sends a certificate request response message to the vehicle-side component.
  • the certificate application response message may include: a new device certificate, and at least one of the following contents: a cloud certificate, a message signature, an application scenario identifier, and other additional parameters.
  • the certificate application response message may be the second response message in method 300.
  • 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 through 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.
  • the vehicle-side component verifies the device certificate and stores it.
  • the vehicle-side component can verify the cloud certificate and message signature in the message, and after the cloud certificate and message signature are verified, the vehicle-side component verifies the device certificate and stores it securely.
  • the verification process of the device certificate may include: signature field verification, validity period verification, etc.
  • the vehicle-side component may still use the old device certificate to process services, and switch the old device certificate to the new device certificate after appropriate conditions are met.
  • the above service may be the first service in method 300.
  • 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.
  • the device certificate may include multiple states, that is, in addition to the certificate itself being in an expired or revoked state, it also includes: pending, effective, and frozen states. Among them, only when the certificate is in an effective state, the vehicle-side component is allowed to perform business processing, and in other states, the vehicle-side component is prohibited from performing business processing.
  • a certificate when a certificate is first issued, it is in a pending state. After the certificate service module confirms the successful issuance of the 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 actively switch the effective state of the certificate to a revoked state. In some business scenarios, for example, 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 is restored.
  • the certificate application request message sent by the vehicle-side component to the certificate service module includes the device identification and the application scenario identification.
  • the certificate service module can select the corresponding CA to issue a new certificate based on the device identification and the application scenario identification.
  • the vehicle-side component does not need to interact with the certificate service module again. In this way, the efficiency of device certificate application can be improved and the complexity of the entire certificate application process can be reduced.
  • 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.
  • Method 700 is a schematic flow chart 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.
  • the vehicle-side component checks whether it meets the certificate confirmation conditions.
  • the vehicle-side component can check whether it currently meets the certificate confirmation condition. When the condition is met, the vehicle-side component initiates the certificate confirmation process and performs subsequent steps.
  • the certificate confirmation condition may include: vehicle operation status and/or user confirmation, etc. For example, when the vehicle is parked, the vehicle-side component may initiate the certificate confirmation process.
  • the vehicle-end component may check whether it satisfies the certificate confirmation condition periodically. For example, the vehicle-end component may check each time the vehicle is started or at a specific time every day.
  • the vehicle-side component sends a certificate confirmation request message to the certificate service module.
  • the certificate confirmation request message may include the following contents: 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.
  • 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 wishes to confirm (i.e., 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.
  • Additional parameters can be 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-side 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), etc.
  • business serial number used to uniquely identify the interaction between the vehicle-side 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
  • the certificate service module checks the device certificate status.
  • 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:
  • the certificate service module uses the CA certificate to verify the legitimacy of the device certificate, check whether the device certificate has expired, and check the current status of the device certificate (not valid, valid, frozen, revoked, etc.)
  • the certificate service module uses the device certificate to verify whether the signature of the certificate confirmation request message is valid.
  • 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.
  • the above process of checking the status of the device certificate is a process of verifying the second device certificate in method 300.
  • the result of the check passing may be the result of the second device certificate verification in method 300.
  • this step is performed only when the certificate status check passes and the certificate status is invalid.
  • the device certificate status can be refreshed from an invalid state to an effective state, and at the same time, the certificate service module can switch the effective certificate corresponding to the device identifier and the application scenario identifier to a revoked state.
  • the certificate service module sends a certificate confirmation response message to the vehicle-side component.
  • the certificate confirmation response message includes the certificate confirmation result, and at least one of the following contents: a cloud certificate, a message signature, an application scenario identifier, a certificate confirmation result, and other additional parameters.
  • the certificate confirmation response message may be the second response message in method 300.
  • the certificate confirmation result may include success or failure, that is, when the device certificate is checked, the certificate confirmation result is success.
  • 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 a digital signature that combines the application scenario identifier, the certificate confirmation result, and other additional parameters through the private key of the cloud certificate.
  • the application scenario identifier can be consistent with the application scenario identifier in the certificate confirmation request.
  • 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, which is convenient for 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, which is convenient for traffic forwarding), remarks (such as the specific status of the certificate, the certificate is about to expire, etc., to improve usability), etc.
  • business serial number used to uniquely identify the interaction between the vehicle and the certificate service module, which is convenient for 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, which is convenient for traffic forwarding
  • remarks such as the specific status of the certificate, the certificate is about to expire, etc., to improve usability
  • the vehicle-side component can verify the cloud certificate and the message signature. After the cloud certificate and the message signature are verified, step S707 is performed.
  • the vehicle-side component processes the local device certificate according to the certificate status.
  • the vehicle-side component can process the locally stored device certificate according to the certificate confirmation result, which can include the following three situations:
  • the vehicle-side component switches 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.
  • 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 new certificates for business processing.
  • the above process may not be performed, that is, after certificate confirmation, the vehicle-side component allows the use of new and old certificates for business processing, and also allows the vehicle-side component to use any certificate for application, that is, new and old certificates can be used equally.
  • the certificate confirmation result is a failure and the vehicle-side marking service cannot be performed. In this case, the user or manufacturer can be prompted to restore the service and certificate.
  • the vehicle-side component before the vehicle-side component performs certificate confirmation, it can check whether the local private key and the public key of the device certificate match. If they match, the vehicle-side component can process the locally stored device certificate according to the certificate confirmation result. Otherwise, the vehicle-side tagging service cannot be performed. At this time, the vehicle-side component can prompt the user or manufacturer to restore the service and certificate.
  • the vehicle-side component in the certificate confirmation process, can send the device identification and application scenario identification to the certificate service module, and the certificate service module can complete the confirmation of the device certificate according to the device identification and application scenario identification, so that the complexity of the entire certificate confirmation process can be reduced.
  • the old device certificate will be revoked, so that the risk of abuse of the old device certificate can be reduced and the security of the use of the device certificate can be improved.
  • FIG8 is a schematic flow chart 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.
  • 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 subsequent steps. Among them, other required conditions may include: vehicle operating status and/or user confirmation. For example, when the vehicle is parked, the vehicle prompts the user that a certificate application is required. After the user confirms on the vehicle display, the vehicle-side component can initiate the certificate application process.
  • the vehicle-end component may perform the certificate check periodically.
  • the vehicle-end component may perform the certificate check every time the vehicle is started or at a specific time every day.
  • the vehicle-side component generates a certificate application document.
  • 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.
  • the vehicle-side component sends a certificate application request message to the certificate service module.
  • the vehicle-side component can send a certificate application request message to the certificate service module, and the certificate application request message may include a device identifier, an application scenario identifier, or at least one of the following contents: device certificate, message signature, certificate application file and other additional parameters.
  • the above-mentioned certificate application request message may be the first request message in method 300.
  • 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 a device certificate used by the current business of 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 through the private key of the device certificate.
  • 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-side and the certificate service module, which is convenient for 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, which is convenient for traffic forwarding), etc.
  • the certificate service module authenticates the vehicle's identity.
  • the certificate service module can authenticate the identity of the vehicle end according to the certificate application request message, including:
  • 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.
  • the certificate service module uses the device certificate to verify whether the signature of the certificate application request message is valid.
  • 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.
  • the certificate service module issues a new device certificate according to the device identifier and the application scenario identifier.
  • the certificate service module can select the corresponding certificate issuance 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.
  • the above new device certificate can be the second device certificate in method 300.
  • 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.
  • the certificate service module sends a certificate request response message to the vehicle-side component.
  • the certificate application response message includes a new device certificate and at least one of the following contents: a cloud certificate, a message signature, an application scenario identifier, and other additional parameters.
  • the above-mentioned certificate application response message may be the first response message in method 300.
  • 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 through 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.
  • the vehicle-side component verifies the device certificate and stores it.
  • the vehicle-side component can verify the cloud certificate and message signature in the message, and after the cloud certificate and message signature are verified, the vehicle-side component verifies the device certificate and stores it securely.
  • the verification process of the device certificate may include: signature field verification, validity period verification, etc.
  • the vehicle-side component performs subsequent business processing.
  • the vehicle-side component can either use the old device certificate for business processing and switch the device certificate after meeting appropriate conditions, or directly use the new device certificate in the subsequent business processing process.
  • the appropriate conditions may include: certificate confirmation completion, vehicle is in parking state, user confirmation, etc.
  • the vehicle-side component in the application process of the device certificate, after completing the application for the new device certificate, can directly use the new device certificate that has not yet taken effect to process the business, which can improve the efficiency of using the device certificate.
  • Figure 9 is a schematic flow chart 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.
  • the vehicle-side component uses a device certificate that has not been explicitly confirmed to perform business processing.
  • 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.
  • the certificate service module checks the device certificate status.
  • the certificate service module can obtain the device identification of the vehicle side and the application scenario identification corresponding to the business module, and check the certificate status according to the vehicle side device identification and application scenario identification.
  • the device identification and application scenario identification can be obtained from the business module, that is, the vehicle-side component can carry the device identification and application scenario identification 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.
  • Checking the status of a certificate may include at least one of the following:
  • 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.).
  • the certificate service module verifies the message signature, that is, uses the device certificate to verify whether the message signature is valid.
  • 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.
  • the certificate service module may prompt the vehicle-side component that the certificate is invalid.
  • this step is performed only when the certificate status check passes and the certificate status is ineffective.
  • the certificate status will be refreshed from ineffective to effective, and the certificate service module can switch the effective certificate corresponding to the device identifier and application scenario identifier to a revoked state.
  • the certificate service module may return the checking result of the new device certificate to the business module.
  • the checking result may be the certificate verification result in method 300 .
  • the vehicle-side component processes the local device certificate according to the business processing result.
  • the business module can combine the inspection result of the new device certificate by the certificate module to determine whether the vehicle-side component has the authority to process 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 according to the authority verification result, which can specifically include the following three situations:
  • the vehicle-side component keeps the certificate unchanged and continues to use the certificate for business processing.
  • the vehicle-side component will switch the certificate to a certificate 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.
  • the vehicle side can prompt the user or manufacturer to restore the service and certificate.
  • the vehicle-side component can directly use the new device certificate that has not yet taken effect to process business, and the vehicle-side component can determine the use strategy of the new and old certificates based on the verification result of the business authority. In this way, the vehicle-side component can save the information interaction process with the certificate service module and improve the business processing efficiency.
  • the embodiments of the present application also provide an apparatus for implementing any of the above methods, wherein the apparatus includes a unit for implementing each step performed by a vehicle, a first network device or a second network device in any of the above methods.
  • FIG10 is a schematic diagram of a communication device 1000 provided in an embodiment of the present application, and 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, and 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.
  • the device 1000 is used to execute the actions performed by the vehicle in the above method embodiment.
  • 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.
  • a 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
  • 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.
  • 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.
  • the second request message includes: a second device certificate, a device identifier, and an application scenario identifier.
  • the processing unit 1030 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.
  • the processing unit 1030 is specifically configured to continue to use the second device certificate to process the first service.
  • the processing unit 1030 is specifically configured to use the first device certificate to process the first service.
  • the processing unit 1030 is further configured to prompt the user that the second device certificate cannot be used.
  • 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.
  • the transceiver unit 1010 is also 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; receive a third response message sent by the second network device, the third response message is used to indicate the result of the authority verification of the vehicle.
  • the processing unit 1030 is specifically used to switch the first device certificate to the second device certificate to process the first business.
  • the processing unit 1030 when the authority verification result shows 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 processing unit 1030 is specifically used to continue to use the second device certificate to process the first service.
  • the processing unit 1030 is specifically configured to use the first device certificate to process the first service.
  • 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 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 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 a certificate used when the vehicle performs the first business.
  • the second request message includes: a second device certificate, a device identifier, and an application scenario identifier.
  • 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.
  • the processing unit 1030 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.
  • the processing unit 1030 is specifically configured to continue to use the second device certificate to process the first service.
  • the processing unit 1030 is specifically configured to use the first device certificate to process the first service.
  • the processing unit 1030 is further configured to prompt the user that the second device certificate cannot be used.
  • 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.
  • the device 1000 may include: a transceiver unit 1010, which 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 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 a certificate used when the vehicle performs the first service; receive a third response message sent by the second network device, the third response message is used to indicate the result of the authority verification of the vehicle.
  • a transceiver unit 1010 which 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 service, the third request message includes
  • 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.
  • the processing unit 1030 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.
  • the processing unit 1030 is specifically configured to continue to use the second device certificate to process the first service.
  • the processing unit 1030 is specifically configured to use the first device certificate to process the first service.
  • the apparatus 1000 is used to execute the actions performed by the first network device in the above method embodiment.
  • 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 when the vehicle performs 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.
  • 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
  • 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, and 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.
  • the second request message includes: a second device certificate, a device identifier, and an application scenario identifier.
  • 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 a successful verification.
  • 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.
  • the processing unit 1030 is further configured to keep the status of the first device certificate in a valid state.
  • 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.
  • the application scenario identifier includes at least one of the following: a character string, a readable name, and a digital ID.
  • 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.
  • the second request message includes: a second device certificate, a device identifier, and an application scenario identifier.
  • 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 a successful verification.
  • 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.
  • the processing unit 1030 is further configured to keep the status of the first device certificate in a valid state.
  • 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.
  • the application scenario identifier includes at least one of the following: a character string, a readable name, and a digital ID.
  • the apparatus 1000 is used to execute the actions performed by the second network device in the above method embodiment.
  • 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 a vehicle, the third request message is used to request a second network device to verify whether the vehicle has the authority to perform a 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, the application scenario identifier is used to identify the usage scenario of the first device certificate, and the first device certificate is a certificate used by the vehicle when performing the first service; 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 a
  • the third response message is used to indicate that the vehicle has the authority to perform the first service.
  • the processing unit 1030 may be the processor 131 shown in FIG. 1 .
  • FIG. 11 is a schematic diagram of another communication device 1100 provided in an embodiment of the present application.
  • the communication device 1100 includes: a memory 1110, a processor 1120, and a communication interface 1130.
  • the memory 1110, the processor 1120, and the communication interface 1130 are connected through 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 enable the communication device to execute the communication method in the above embodiments.
  • the memory 1110 can be coupled to the processor 1120 through an interface, or can be integrated with the processor 1120.
  • the communication interface 1130 uses a transceiver such as, but not limited to, a transceiver.
  • the communication interface 1130 may also include an input/output interface.
  • the processor 1120 stores one or more computer programs, and the one or more computer programs include instructions.
  • the communication device 1100 executes the communication method in each of the above embodiments.
  • each step of the above method can be completed by an integrated logic circuit of hardware in the processor 1120 or an instruction in the form of software.
  • the method disclosed in conjunction with the embodiment of the present application can be directly embodied as a hardware processor for execution, or a combination of hardware and software modules in the processor for execution.
  • 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 conjunction with its hardware. To avoid repetition, it will not be described in detail here.
  • 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
  • the processor 1120 in FIG. 11 may implement the processing unit 1030 in FIG. 10 .
  • the device 1000 or the device 1100 may be a computing platform, and the computing platform may be a vehicle-mounted computing platform or a cloud computing platform.
  • the device 1000 or the device 1100 may be located in the vehicle 100 in FIG. 1 .
  • the device 1000 or the device 1100 may be the computing platform 130 in the vehicle in FIG. 1 .
  • An embodiment of the present application also provides a computer-readable medium, which stores a program code.
  • the computer program code runs on a computer, the computer executes any one of the methods in Figures 3 to 9 above.
  • An embodiment of the present application also provides a chip, including: a circuit, wherein the circuit is used to execute any one of the methods in FIG. 3 to FIG. 9 above.
  • An embodiment of the present application further provides a computer program product, which includes a computer program.
  • the computer program When the computer program is executed, the computer executes any one of the methods in FIG. 3 to FIG. 9 .
  • the disclosed systems, devices and methods can be implemented in other ways.
  • the device embodiments described above are only schematic.
  • the division of the units is only a logical function division. There may be other division methods in actual implementation, 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.
  • the units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
  • 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.
  • 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.
  • the technical solution of the present application can be essentially or partly embodied in the form of a software product that contributes to the prior art.
  • the computer software product is stored in a storage medium and includes several instructions for a computer device (which can be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in each embodiment of the present application.
  • the aforementioned storage media include: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), disk or optical disk, and other media that can store program codes.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

本申请实施例提供了一种通信方法、装置以及运载工具，该方法包括：向第一网络设备发送第一请求消息，所述第一请求消息用于请求第一网络设备签发设备证书，所述第一请求消息包括：设备标识和应用场景标识，所述设备标识用于标识运载工具和/或所述运载工具包括的部件，所述应用场景标识用于标识第一设备证书的使用场景，所述第一设备证书为所述运载工具进行第一业务时所使用的证书；接收第一网络设备发送的第一响应消息，所述第一响应消息包括所述第二设备证书，所述第二设备证书与所述设备标识和所述应用场景标识相关联，且所述第二设备证书用于处理所述第一业务。通过上述方法，能够降低整个证书申请和确认流程的复杂度。

Description

通信方法、装置以及运载工具 技术领域
本申请实施例涉及通信领域，并且更具体地，涉及一种通信方法、装置以及运载工具。
背景技术
随着智能车在日常生活中被广泛使用，车辆内部和对外通信的业务逐渐增多，在许多场景下需要进行车端身份认证和鉴权，从而保证通信主体身份的真实性和业务权限的合法性。
由于车辆的产品生命周期较长，车内部件中存储的设备证书必然会出现过期、吊销等情况，甚至可能出现因业务冻结而临时不允许证书使用的情况。这就需要车辆具备在线申请证书以及证书状态确认的能力。然而，当前车辆在线申请证书的方案中，一部分方案不支持证书的状态确认过程，另外一部分方案虽然支持证书状态的确认，但是，整个证书的申请和确认流程复杂、可靠性差，导致重试成本较高。
发明内容
本申请实施例提供一种通信方法、装置以及运载工具，能够在证书申请和确认的流程中，减少运载工具与网络设备之间的信息交互，降低证书申请和确认流程的复杂度。
第一方面，提供了一种通信方法，该方法包括：向第一网络设备发送第一请求消息，所述第一请求消息用于请求第一网络设备签发设备证书，所述第一请求消息包括：设备标识和应用场景标识，所述设备标识用于标识运载工具和/或所述运载工具包括的部件，所述应用场景标识用于标识第一设备证书的使用场景，所述第一设备证书为所述运载工具进行第一业务时所使用的证书；接收第一网络设备发送的第一响应消息，所述第一响应消息包括所述第二设备证书，所述第二设备证书与所述设备标识和所述应用场景标识相关联，且所述第二设备证书用于处理所述第一业务。
其中，第一业务可以是运载工具当前正在进行的业务，第一业务可以包括：传感器数据上传、软件升级或者地图下载等等。第一业务可以与应用场景标识具有对应关系，例如，当第一业务为软件升级时，应用场景标识可以用于标识第一设备证书的使用场景是软件升级场景。
可选地，第二设备证书可以是未生效的设备证书，第二设备证书用于处理第一业务可以理解为运载工具可以使用第二设备证书处理第一业务。
可选地，运载工具包括的部件包括：车载网关、移动数据中心、智能座舱数据中心、车载通信盒子、传感器、电子控制单元、整车动态控制中的一种或多种。在本申请中，部件和设备表示的意思可以相同。例如，设备证书可以理解为上述任一部件进行业务时所使用的证书。
可选地，第一网络设备可以是证书服务模块。
本申请实施例中，由于运载工具向第一网络设备发送的第一请求消息中携带设备标识和应用场景标识，从而使得第一网络设备可以根据该设备标识和应用场景标识确定第二设备证书。通过这样的方式，在第一网络设备签发第二设备证书的过程中，无需与运载工具再次进行信息交互，运载工具也无需同步修改特定的参数，能够降低证书申请的流程复杂度，提高证书申请的效率。
结合第一方面，在第一方面的某些实现方式中，所述方法还包括：使用所述第一设备证书或所述第二设备证书处理所述第一业务。
本申请实施例中，运载工具在接收到第二设备证书后，既可以使用第一设备证书处理第一业务，也可以使用第二设备证书处理第一业务。这样，使得运载工具使用设备证书处理业务的方式更加的灵活。
结合第一方面，在第一方面的某些实现方式中，所述方法还包括：向所述第一网络设备发送第二请求消息，所述第二请求消息用于请求所述第一网络设备对所述第二设备证书进行验证；接收所述第一网络设备发送的第二响应消息，所述第二响应消息包括与所述设备标识和所述应用场景标识相关联的所述第二设备证书的验证结果。
本申请实施例中，运载工具申请了第二设备证书后，能够迅速发起第二设备证书确认流程，从而使得运载工具可以根据第二设备证书的验证结果进行第一业务的处理。
结合第一方面，在第一方面的某些实现方式中，所述第二请求消息包括：所述第二设备证书、所述设备标识和所述应用场景标识。
结合第一方面，在第一方面的某些实现方式中，在所述第二设备证书的验证结果为验证成功，且所述运载工具使用所述第一设备证书处理所述第一业务的情况下，所述使用所述第一设备证书或所述第二设备证书处理所述第一业务，包括：将所述第一设备证书切换为所述第二设备证书，处理所述第一业务。
本申请实施例中，在运载工具在确认证书的验证结果为成功，且运载工具正在使用第一设备证书的情况下，运载工具可以将第一设备证书切换为第二设备证书处理第一业务。通过这样的方式，运载工具能够及时使用经过确认的新设备证书处理业务，保障了第一业务处理的安全性。
结合第一方面，在第一方面的某些实现方式中，在所述第二设备证书的验证结果为验证成功，且所述运载工具使用所述第二设备证书处理所述第一业务的情况下，所述使用所述第一设备证书或所述第二设备证书处理所述第一业务，包括：继续使用所述第二设备证书处理所述第一业务。
本申请实施例中，在运载工具在确认证书的验证结果为成功，且运载工具已经使用第二设备证书处理业务的情况下，运载工具能够继续使用第二设备证书处理第一业务，无需进行设备证书的切换，从而提高第一业务处理效率。
结合第一方面，在第一方面的某些实现方式中，在所述第二设备证书的验证结果为验证失败的情况下，所述使用所述第一设备证书或所述第二设备证书处理所述第一业务，包括：使用所述第一设备证书处理所述第一业务。
本申请实施例中，在运载工具在确认证书的验证结果为失败的情况下，运载工具能够使用第一设备证书处理第一业务，这样，运载工具能够避免使用未经过确认的第二设备证书处理第一业务，从而保障了第一业务处理的安全性。
结合第一方面，在第一方面的某些实现方式中，所述方法还包括：向用户提示所述第二设备证书无法使用。
可选地，运载工具可以通过显示屏或语音等多种方式向用户提示第二设备证书无法使用。
可选地，在重复进行证书确认的流程中，如果上一次第二设备证书的证书验证结果为成功，即运载工具已经使用第二设备证书处理第一业务。当运载工具再次发起证书确认流程，且本次第二设备证书的验证结果为失败，则运载工具可以向用户提示第一业务无法进行。
结合第一方面，在第一方面的某些实现方式中，在所述向第一网络设备发送第二请求消息之前，所述方法还包括：确定本地保存的私钥与所述第二设备证书的公钥是否匹配；所述向第一网络设备发送第二请求消息，包括：在本地保存的私钥与所述第二设备证书的公钥匹配的情况下，向所述第一网络设备发送所述第二请求消息。
可选地，在确定在本地保存的私钥与所述第二设备证书的公钥不匹配的情况下，运载工具可以向用户提示第一业务无法进行。
其中，上述私钥和证书公钥的匹配原理是：证书公钥实际上是一个加密的字符串，任何人都可以看到其内容，而私钥的内容只用拥有者(运载工具)才可以知晓。通过该公钥加密的密文使用经过配对的私钥可以解密，而公钥不能解密私钥。在本申请中，如果运载工具本地保存的私钥能够解密证书的公钥，则说明私钥与公钥匹配。
本申请实施例中，运载工具在发起证书确认流程前，可以在本地检查私钥和证书公钥的匹配性，如果运载工具存储的私钥和第二设备证书的公钥匹配，则可以进行证书确认流程；如果运载工具存储的私钥和第二设备证书的公钥不匹配，则无需联网即可判断第二设备证书不可用，可以提前进行相应的补救措施。
结合第一方面，在第一方面的某些实现方式中，向第二网络设备发送第三请求消息，所述第三请求消息用于请求所述第二网络设备验证所述运载工具是否具有进行所述第一业务的权限，所述第三请求消息包括以下内容至少一项：所述第二设备证书、所述设备标识和所述应用场景标识；接收所述第二网络设备发送的第三响应消息，所述第三响应消息用于指示所述运载工具的权限验证结果。
可选地，第二网络设备可以是业务模块，该业务模块可以验证运载工具是否具备处理第一业务的权限。
本申请实施例中，运载工具可以在第三请求消息中携带设备标识和/或应用场景标识，从而使得第二网络设备能够向第一网络设备发起第二设备证书的验证流程。通过这样的方式，可以省去运载工具和第一网络设备的信令交互过程，运载工具仅需根据业务权限的验证结果进行第一业务的处理。
结合第一方面，在第一方面的某些实现方式中，在所述权限验证结果为所述运载工具具有进行所述第一业务的权限，且所述运载工具使用所述第一设备证书处理所述第一业务的情况下，所述使用所述第一设备证书或所述第二设备证书处理所述第一业务，包括：将所述第一设备证书切换为所述第二设备证书，处理所述第一业务。
本申请实施例中，在运载工具确认具有进行第一业务权限，且运载工具正在使用第一设备证书的情况下，运载工具可以将第一设备证书切换为第二设备证书处理第一业务。通 过这样的方式，运载工具能够及时使用经过确认的新设备证书处理业务，既保障了第一业务处理的安全性，又省去了运载工具和第一网络设备的信令交互过程。
结合第一方面，在第一方面的某些实现方式中，在所述权限验证结果为所述运载工具具有进行所述第一业务的权限，且所述运载工具使用所述第二设备证书处理所述第一业务的情况下，所述使用所述第一设备证书或所述第二设备证书处理所述第一业务，包括：继续使用所述第二设备证书处理所述第一业务。
本申请实施例中，在运载工具确认具有进行第一业务权限，且运载工具已经使用第二设备证书处理业务的情况下，运载工具能够继续使用第二设备证书处理第一业务，无需进行设备证书的切换，不仅提高第一业务处理效率，也省去了运载工具和第一网络设备的信令交互过程。
结合第一方面，在第一方面的某些实现方式中，在所述权限验证结果为所述运载工具不具有进行所述第一业务的权限的情况下，所述使用所述第一设备证书或所述第二设备证书处理第一业务，包括：使用所述第一设备证书处理所述第一业务。
本申请实施例中，在运载工具在确认不具有进行第一业务的权限的情况下，运载工具能够使用第一设备证书处理第一业务，这样，运载工具能够避免使用未经过确认的第二设备证书处理第一业务，从而保障了第一业务处理的安全性。
第二方面，提供了一种通信方法，该方法包括：接收运载工具发送的第一请求消息，所述第一请求消息用于请求第一网络设备签发设备证书，所述第一请求消息包括设备标识和应用场景标识，所述设备标识用于标识所述运载工具和/或所述运载工具包括的部件，所述应用场景标识用于标识第一设备证书的使用场景，所述第一设备证书为所述运载工具进行第一业务时所使用的证书；根据所述设备标识和所述应用场景标识，确定第二设备证书；向所述运载工具发送第一响应消息，所述第一响应消息包括所述第二设备证书，所述第二设备证书用于处理所述第一业务。
本申请实施例中，第一网络设备可以接收运载工具发送的设备标识和应用场景标识，并根据设备标识和应用场景标识确定第二设备证书。通过这样的方式，在第一网络设备签发第二设备证书的过程中，无需与运载工具再次进行信息交互，运载工具也无需同步修改特定的参数，能够降低证书申请的流程复杂度，提高证书申请的效率。
结合第二方面，在第二方面的某些实现方式中，所述方法还包括：接收第一设备发送的第二请求消息，所述第二请求消息用于请求所述第一网络设备对所述第二设备证书进行验证，所述第一设备包括运载工具或第二网络设备；根据所述设备标识和所述应用场景标识，确定所述第二设备证书的验证结果；向所述第一设备发送第二响应消息，所述第二响应消息用于指示所述第二设备证书的验证结果。
本申请实施例中，第一网络设备可以根据运载工具设备标识和应用场景标识对第二设备证书进行验证，并向运载工具返回第二设备证书的验证结果，从而使得运载工具可以根据第二设备证书的验证结果进行第一业务的处理。
结合第二方面，在第二方面的某些实现方式中，所述第二请求消息包括：所述第二设备证书、所述设备标识和所述应用场景标识。
结合第二方面，在第二方面的某些实现方式中，所述根据所述设备标识和所述应用场景标识，确定所述第二设备证书的验证结果，包括：验证所述设备标识和所述应用场景标 识的有效性；在所述设备标识和所述应用场景标识有效的情况下，确定所述第二设备证书的验证结果为验证成功。
结合第二方面，在第二方面的某些实现方式中，所述验证所述设备标识和所述应用场景标识的有效性，包括：验证所述设备标识和所述第一网络设备中预设的设备标识是否一致，以及所述应用场景标识和所述第一网络设备中预设的应用场景标识是否一致。
示例性地，在设备标识和第一网络设备中预设的设备标识一致，且应用场景标识和第一网络设备中预设的应用场景标识一致的情况下，可以确认设备标识和应用场景标识有效，第二设备证书的验证结果为成功。在设备标识和第一网络设备中预设的设备标识不一致，或者应用场景标识和第一网络设备中预设的应用场景标识不一致的情况下，可以确认第二设备证书的验证结果为失败。
本申请实施例中，第一网络设备可以通过验证设备标识与第一网络设备中预设的设备标识是否一致，以及应用场景标识与第一网络设备中预设的应用场景标识是否一致，来验证设备标识和应用场景标识的有效性，从而确定第二设备证书的验证结果。
结合第二方面，在第二方面的某些实现方式中，所述第二请求消息还包括：消息签名，在所述根据所述设备标识和所述应用场景标识，确定所述第二设备证书的验证结果之前，所述方法还包括：使用所述第二设备证书验证所述消息签名的有效性。
本申请实施例中，第一网络设备还可以使用第二设备证书验证签名的有效性，在签名有效的情况下，第一网络设备再进行设备标识和应用场景标识有效性的验证。
结合第二方面，在第二方面的某些实现方式中，所述方法还包括：将所述第一设备证书的状态保持为生效状态。
本申请实施例中，在第二设备证书的验证结果为验证成功的情况下，第一网络设备可以不将第一设备证书的生效状态切换为吊销状态。这样，运载工具侧可以同时存在已生效的第一设备证书和第二设备证书，第一设备证书和第二设备证书可以相互备份，一张证书损坏可以使用另外一张证书处理业务。
结合第二方面，在第二方面的某些实现方式中，所述应用场景标识包括以下内容至少一种：字符串、可读名称和数字ID。
其中，字符串可以理解为由数字、字母、下划线组成的一串字符，其可以是编程语言中表示文本的数据类型；可读名称可以理解为用户可以理解的词语，数字ID可以理解为数字标识。
第三方面，提供了一种通信方法，该方法包括：接收运载工具发送的第三请求消息，所述第三请求消息用于请求所述第二网络设备验证所述运载工具是否具有进行第一业务的权限，所述第三请求消息包括以下内容至少一项：第二设备证书、设备标识和应用场景标识，所述第二设备证书用于处理所述第一业务，所述设备标识用于标识所述运载工具和/或所述运载工具包括的部件，所述应用场景标识用于标识第一设备证书的使用场景，所述第一设备证书为所述运载工具进行第一业务时所使用的证书；向所述第一网络设备发送第二请求消息，所述第二请求消息用于请求所述第一网络设备对所述第二设备证书进行验证，所述第二请求消息包括所述第二设备证书、所述设备标识和所述应用场景标识；接收所述第一网络设备发送的第二响应消息，所述第二响应消息包括与所述设备标识和所述应用场景标识相关联的所述第二设备证书的验证结果；根据所述第二设备证书的验证结果， 向所述运载工具发送第三响应消息，所述第三响应消息用于指示所述运载工具的权限验证结果。
可选地，第二网络设备可以是业务模块，该业务模块可以验证运载工具是否具备处理第一业务的权限。
可选地，第三请求消息中也可以不携带应用场景标识，仅携带设备标识，即第二网络设备只负责第一业务权限的认证，第二网络设备仅仅根据设备标识就能够确定第一业务的应用场景。
可选地，第三请求消息中可以不携带应用场景标识和设备标识，即第二网络设备只负责第一业务权限的认证，且第二网络设备已经知晓运载工具的身份，第二网络设备能够直接确定第一业务的应用场景。
应理解，上述第二设备证书为运载工具请求第一网络设备签发的设备证书，在一些可能的实现方式中，上述第二设备证书也可以为任意的设备证书，例如，上文中的第一设备证书。
本申请实施例中，第二网络设备可以从运载工具发送的权限验证请求消息中获取设备标识和应用场景标识，并根据该设备标识和应用场景标识向第一网络设备发起第二设备证书的验证流程。通过这样的方式，可以省去运载工具和第一网络设备的信令交互过程，运载工具仅需根据业务权限的验证结果进行第一业务的处理。
结合第三方面，在第三方面的某些实现方式中，在所述第二设备证书的验证结果为成功的情况下，所述第三响应消息用于指示所述运载工具具有进行所述第一业务的权限。
可选地，在第二设备证书的验证结果为失败的情况下，第三响应消息可以用于指示运载工具不具有进行第一业务的权限。
第四方面，提供了一种通信方法，该方法包括：向所述第一网络设备发送第二请求消息，所述第二请求消息用于请求所述第一网络设备对所述第二设备证书进行验证；接收所述第一网络设备发送的第二响应消息，所述第二响应消息包括与所述设备标识和所述应用场景标识相关联的所述第二设备证书的验证结果；其中，所述设备标识用于标识运载工具和/或所述运载工具包括的部件，所述应用场景标识用于标识第一设备证书的使用场景，所述第一设备证书为所述运载工具进行第一业务时所使用的证书。
结合第四方面，在第四方面的某些实现方式中，所述第二请求消息包括：所述第二设备证书、所述设备标识和所述应用场景标识。
结合第四方面，在第四方面的某些实现方式中，在所述向所述第一网络设备发送第二请求消息之前，所述方法还包括：使用所述第一设备证书或所述第二设备证书处理所述第一业务。
结合第四方面，在第四方面的某些实现方式中，在所述第二设备证书的验证结果为验证成功，且所述运载工具使用所述第一设备证书处理所述第一业务的情况下，所述使用所述第一设备证书或所述第二设备证书处理所述第一业务，包括：将所述第一设备证书切换为所述第二设备证书，处理所述第一业务。
结合第四方面，在第四方面的某些实现方式中，在所述第二设备证书的验证结果为验证成功，且所述运载工具使用所述第二设备证书处理所述第一业务的情况下，所述使用所述第一设备证书或所述第二设备证书处理所述第一业务，包括：继续使用所述第二设备证 书处理所述第一业务。
结合第四方面，在第四方面的某些实现方式中，在所述第二设备证书的验证结果为验证失败的情况下，所述使用所述第一设备证书或所述第二设备证书处理所述第一业务，包括：使用所述第一设备证书处理所述第一业务。
结合第四方面，在第四方面的某些实现方式中，所述方法还包括：向用户提示所述第二设备证书无法使用。
结合第四方面，在第四方面的某些实现方式中，在所述向第一网络设备发送第二请求消息之前，所述方法还包括：确定本地保存的私钥与所述第二设备证书的公钥是否匹配；所述向第一网络设备发送第二请求消息，包括：在本地保存的私钥与所述第二设备证书的公钥匹配的情况下，向所述第一网络设备发送所述第二请求消息。
第五方面，提供了一种通信方法，所述方法包括：向第二网络设备发送第三请求消息，所述第三请求消息用于请求所述第二网络设备验证所述运载工具是否具有进行所述第一业务的权限，所述第三请求消息包括以下内容至少一项：所述第二设备证书、所述设备标识和所述应用场景标识；所述第二设备证书用于处理所述第一业务，所述设备标识用于标识运载工具和/或所述运载工具包括的部件，所述应用场景标识用于标识第一设备证书的使用场景，所述第一设备证书为所述运载工具进行第一业务时所使用的证书；接收所述第二网络设备发送的第三响应消息，所述第三响应消息用于指示所述运载工具的权限验证结果。
结合第五方面，在第五方面的某些实现方式中，在所述向所述第二网络设备发送第三请求消息之前，所述方法还包括：使用所述第一设备证书或所述第二设备证书处理所述第一业务。
结合第五方面，在第五方面的某些实现方式中，在所述权限验证结果为所述运载工具具有进行所述第一业务的权限，且所述运载工具使用所述第一设备证书处理所述第一业务的情况下，所述使用所述第一设备证书或所述第二设备证书处理所述第一业务，包括：将所述第一设备证书切换为所述第二设备证书，处理所述第一业务。
结合第五方面，在第五方面的某些实现方式中，在所述权限验证结果为所述运载工具具有进行所述第一业务的权限，且所述运载工具使用所述第二设备证书处理所述第一业务的情况下，所述使用所述第一设备证书或所述第二设备证书处理所述第一业务，包括：继续使用所述第二设备证书处理所述第一业务。
结合第五方面，在第五方面的某些实现方式中，在所述权限验证结果为所述运载工具不具有进行所述第一业务的权限的情况下，所述使用所述第一设备证书或所述第二设备证书处理第一业务，包括：使用所述第一设备证书处理所述第一业务。
第六方面，提供了一种通信方法，所述方法包括：接收第一设备发送的第二请求消息，所述第二请求消息用于请求所述第一网络设备对所述第二设备证书进行验证，所述第一设备包括运载工具或第二网络设备；根据设备标识和应用场景标识，确定所述第二设备证书的验证结果；向所述第一设备发送第二响应消息，所述第二响应消息用于指示所述第二设备证书的验证结果。
应理解，在上述方法中，第一网络设备中已经预先存储设备标识和应用场景标识，当第一网络设备接收到第二请求消息后，第一网络设备可以根据存储的设备标识和应用场景 标识确定第二设备证书的验证结果。
结合第六方面，在第六方面的某些实现方式中，所述第二请求消息包括：所述第二设备证书、所述设备标识和所述应用场景标识。
结合第六方面，在第六方面的某些实现方式中，所述根据所述设备标识和所述应用场景标识，确定所述第二设备证书的验证结果，包括：验证所述设备标识和所述应用场景标识的有效性；在所述设备标识和所述应用场景标识有效的情况下，确定所述第二设备证书的验证结果为验证成功。
结合第六方面，在第六方面的某些实现方式中，所述验证所述设备标识和所述应用场景标识的有效性，包括：验证所述设备标识和所述第一网络设备中预设的设备标识是否一致，以及所述应用场景标识和所述第一网络设备中预设的应用场景标识是否一致。
结合第六方面，在第六方面的某些实现方式中，所述方法还包括：将所述第一设备证书的状态保持为生效状态。
结合第六方面，在第六方面的某些实现方式中，所述第二请求消息还包括：消息签名，在所述根据所述设备标识和所述应用场景标识，确定所述第二设备证书的验证结果之前，所述方法还包括：使用所述第二设备证书验证所述消息签名的有效性。
结合第六方面，在第六方面的某些实现方式中，所述应用场景标识包括以下内容至少一种：字符串、可读名称和数字ID。
第七方面，提供了一种通信方法，所述方法包括：接收运载工具发送的第三请求消息，所述第三请求消息用于请求所述第二网络设备验证所述运载工具是否具有进行第一业务的权限，所述第三请求消息包括以下内容至少一项：第二设备证书、设备标识和应用场景标识，所述第二设备证书用于处理所述第一业务，所述设备标识用于标识所述运载工具和/或所述运载工具包括的部件，所述应用场景标识用于标识第一设备证书的使用场景，所述第一设备证书为所述运载工具进行第一业务时所使用的证书；向所述第一网络设备发送第二请求消息，所述第二请求消息用于请求所述第一网络设备对所述第二设备证书进行验证，所述第二请求消息包括所述第二设备证书、所述设备标识和所述应用场景标识；接收所述第一网络设备发送的第二响应消息，所述第二响应消息包括与所述设备标识和所述应用场景标识相关联的所述第二设备证书的验证结果；根据所述第二设备证书的验证结果，向所述运载工具发送第三响应消息，所述第三响应消息用于指示所述运载工具的权限验证结果。
结合第七方面，在第七方面的某些实现方式中，在所述第二证书的验证结果为成功的情况下，所述第三响应消息用于指示所述运载工具具有进行所述第一业务的权限。
第八方面，提供了一种通信装置，所述装置包括：收发单元；所述收发单元，用于：向第一网络设备发送第一请求消息，所述第一请求消息用于请求第一网络设备签发设备证书，所述第一请求消息包括：设备标识和应用场景标识，所述设备标识用于标识运载工具和/或所述运载工具包括的部件，所述应用场景标识用于标识第一设备证书的使用场景，所述第一设备证书为所述运载工具进行第一业务时所使用的证书；接收第一网络设备发送的第一响应消息，所述第一响应消息包括所述第二设备证书，所述第二设备证书与所述设备标识和所述应用场景标识相关联，且所述第二设备证书用于处理所述第一业务。
结合第八方面，在第八方面的某些实现方式中，所述装置还包括：处理单元；所述处 理单元，用于使用所述第一设备证书或所述第二设备证书处理所述第一业务。
结合第八方面，在第八方面的某些实现方式中，所述收发单元，还用于：向所述第一网络设备发送第二请求消息，所述第二请求消息用于请求所述第一网络设备对所述第二设备证书进行验证；接收所述第一网络设备发送的第二响应消息，所述第二响应消息包括与所述设备标识和所述应用场景标识相关联的所述第二设备证书的验证结果。
结合第八方面，在第八方面的某些实现方式中，所述第二请求消息包括：所述第二设备证书、所述设备标识和所述应用场景标识。
结合第八方面，在第八方面的某些实现方式中，在所述第二设备证书的验证结果为验证成功，且所述运载工具使用所述第一设备证书处理所述第一业务的情况下，所述处理单元，具体用于将所述第一设备证书切换为所述第二设备证书，处理所述第一业务。
结合第八方面，在第八方面的某些实现方式中，在所述第二设备证书的验证结果为验证成功，且所述运载工具使用所述第二设备证书处理所述第一业务的情况下，所述处理单元，具体用于继续使用所述第二设备证书处理所述第一业务。
结合第八方面，在第八方面的某些实现方式中，在所述第二设备证书的验证结果为验证失败的情况下，所述处理单元，具体用于使用所述第一设备证书处理所述第一业务。
结合第八方面，在第八方面的某些实现方式中，在所述第二设备证书的验证结果为验证失败的情况下，所述处理单元，还用于向用户提示所述第二设备证书无法使用。
结合第八方面，在第八方面的某些实现方式中，所述处理单元，还用于确定本地保存的私钥与所述第二设备证书的公钥是否匹配；所述收发单元，还用于在本地保存的私钥与所述第二设备证书的公钥匹配的情况下，向所述第一网络设备发送所述第二请求消息。
结合第八方面，在第八方面的某些实现方式中，所述收发单元，还用于：向第二网络设备发送第三请求消息，所述第三请求消息用于请求所述第二网络设备验证所述运载工具是否具有进行所述第一业务的权限，所述第三请求消息包括以下内容至少一项：所述第二设备证书、所述设备标识和所述应用场景标识；接收所述第二网络设备发送的第三响应消息，所述第三响应消息用于指示所述运载工具的权限验证结果。
结合第八方面，在第八方面的某些实现方式中，在所述权限验证结果为所述运载工具具有进行所述第一业务的权限，且所述运载工具使用所述第一设备证书进行所述第一业务处理的情况下，所述处理单元，具体用于将所述第一设备证书切换为所述第二设备证书，处理所述第一业务。
结合第八方面，在第八方面的某些实现方式中，在所述权限验证结果为所述运载工具具有进行所述第一业务的权限，且所述运载工具使用所述第二设备证书进行所述第一业务处理的情况下，所述处理单元，具体用于继续使用所述第二设备证书处理所述第一业务。
结合第八方面，在第八方面的某些实现方式中，在所述权限验证结果为所述运载工具不具有进行所述第一业务的权限的情况下，所述处理单元，具体用于使用所述第一设备证书处理所述第一业务。
第九方面，提供了一种通信装置，所述装置包括：收发单元和处理单元；所述收发单元，用于接收运载工具发送的第一请求消息，所述第一请求消息用于请求第一网络设备签发设备证书，所述第一请求消息包括设备标识和应用场景标识，所述设备标识用于标识运载工具和/或所述运载工具包括的部件，所述应用场景标识用于标识第一设备证书的使用 场景，所述第一设备证书为所述运载工具进行第一业务时所使用的证书；所述处理单元，用于根据所述设备标识和所述应用场景标识，确定第二设备证书；所述收发单元，还用于向所述运载工具发送第一响应消息，所述第一响应消息包括所述第二设备证书，所述第二设备证书用于处理所述第一业务。
结合第九方面，在第九方面的某些实现方式中，所述收发单元，还用于接收第一设备发送的第二请求消息，所述第二请求消息用于请求所述第一网络设备对所述第二设备证书进行验证，所述第一设备包括运载工具或第二网络设备；所述处理单元，还用于根据所述设备标识和所述应用场景标识，确定所述第二设备证书的验证结果；所述收发单元，还用于向所述第一设备发送第二响应消息，所述第二响应消息用于指示所述第二设备证书的验证结果。
结合第九方面，在第九方面的某些实现方式中，所述第二请求消息包括：所述第二设备证书、所述设备标识和所述应用场景标识。
结合第九方面，在第九方面的某些实现方式中，所述处理单元，具体用于：验证所述设备标识和所述应用场景标识的有效性；在所述设备标识和所述应用场景标识有效的情况下，确定所述第二设备证书的验证结果为验证成功。
结合第九方面，在第九方面的某些实现方式中，所述处理单元，具体用于验证所述设备标识和所述第一网络设备中预设的设备标识是否一致，以及所述应用场景标识和所述第一网络设备中预设的应用场景标识是否一致。
结合第九方面，在第九方面的某些实现方式中，所述处理单元，还用于将所述第一设备证书的状态保持为生效状态。
结合第九方面，在第九方面的某些实现方式中，所述第二请求消息还包括：消息签名；所述处理单元，还用于使用所述第二设备证书验证所述消息签名的有效性。
结合第九方面，在第九方面的某些实现方式中，所述应用场景标识包括以下内容至少一种：字符串、可读名称和数字ID。
第十方面，提供了一种通信装置，所述装置包括：收发单元和处理单元；所述收发单元，用于：接收运载工具发送的第三请求消息，所述第三请求消息用于请求所述第二网络设备验证所述运载工具是否具有进行第一业务的权限，所述第三请求消息包括以下内容至少一项：第二设备证书、设备标识和应用场景标识，所述第二设备证书用于处理所述第一业务，所述设备标识用于标识所述运载工具和/或所述运载工具包括的部件，所述应用场景标识用于标识第一设备证书的使用场景，所述第一设备证书为所述运载工具进行第一业务时所使用的证书；向所述第一网络设备发送第二请求消息，所述第二请求消息用于请求所述第一网络设备对所述第二设备证书进行验证，所述第二请求消息包括所述第二设备证书、所述设备标识和所述应用场景标识；接收所述第一网络设备发送的第二响应消息，所述第二响应消息包括与所述设备标识和所述应用场景标识相关联的所述第二设备证书的验证结果；所述处理单元，用于根据所述第二设备证书的验证结果，向所述运载工具发送第三响应消息，所述第三响应消息用于指示所述运载工具的权限验证结果。
结合第十方面，在第十方面的某些实现方式中，在所述第二证书的验证结果为成功的情况下，所述第三响应消息用于指示所述运载工具具有进行所述第一业务的权限。
第十一方面，提供了一种通信装置，所述装置包括收发单元，所述收发单元，用于： 向所述第一网络设备发送第二请求消息，所述第二请求消息用于请求所述第一网络设备对所述第二设备证书进行验证；接收所述第一网络设备发送的第二响应消息，所述第二响应消息包括与所述设备标识和所述应用场景标识相关联的所述第二设备证书的验证结果；其中，所述设备标识用于标识运载工具和/或所述运载工具包括的部件，所述应用场景标识用于标识第一设备证书的使用场景，所述第一设备证书为所述运载工具进行第一业务时所使用的证书。
结合第十一方面，在第十一方面的某些实现方式中，所述第二请求消息包括：所述第二设备证书、所述设备标识和所述应用场景标识。
结合第十一方面，在第十一方面的某些实现方式中，所述装置还包括处理单元，所述处理单元，用于使用所述第一设备证书或所述第二设备证书处理所述第一业务。
结合第十一方面，在第十一方面的某些实现方式中，在所述第二设备证书的验证结果为验证成功，且所述运载工具使用所述第一设备证书处理所述第一业务的情况下，所述处理单元，具体用于将所述第一设备证书切换为所述第二设备证书，处理所述第一业务。
结合第十一方面，在第十一方面的某些实现方式中，在所述第二设备证书的验证结果为验证成功，且所述运载工具使用所述第二设备证书处理所述第一业务的情况下，所述处理单元，具体用于继续使用所述第二设备证书处理所述第一业务。
结合第十一方面，在第十一方面的某些实现方式中，在所述第二设备证书的验证结果为验证失败的情况下，所述处理单元，具体用于使用所述第一设备证书处理所述第一业务。
结合第十一方面，在第十一方面的某些实现方式中，所述处理单元，还用于向用户提示所述第二设备证书无法使用。
结合第十一方面，在第十一方面的某些实现方式中，所述处理单元还用于确定本地保存的私钥与所述第二设备证书的公钥是否匹配；所述收发单元，具体用于在本地保存的私钥与所述第二设备证书的公钥匹配的情况下，向所述第一网络设备发送所述第二请求消息。
第十二方面，提供了一种通信装置，所述装置包括收发单元，所述收发单元，用于：向第二网络设备发送第三请求消息，所述第三请求消息用于请求所述第二网络设备验证所述运载工具是否具有进行所述第一业务的权限，所述第三请求消息包括以下内容至少一项：所述第二设备证书、所述设备标识和所述应用场景标识；所述第二设备证书用于处理所述第一业务，所述设备标识用于标识运载工具和/或所述运载工具包括的部件，所述应用场景标识用于标识第一设备证书的使用场景，所述第一设备证书为所述运载工具进行第一业务时所使用的证书；接收所述第二网络设备发送的第三响应消息，所述第三响应消息用于指示所述运载工具的权限验证结果。
结合第十二方面，在第十二方面的某些实现方式中，所述装置还包括处理单元，所述处理单元，用于使用所述第一设备证书或所述第二设备证书处理所述第一业务。
结合第十二方面，在第十二方面的某些实现方式中，在所述权限验证结果为所述运载工具具有进行所述第一业务的权限，且所述运载工具使用所述第一设备证书处理所述第一业务的情况下，所述处理单元，具体用于将所述第一设备证书切换为所述第二设备证书，处理所述第一业务。
结合第十二方面，在第十二方面的某些实现方式中，在所述权限验证结果为所述运载工具具有进行所述第一业务的权限，且所述运载工具使用所述第二设备证书处理所述第一 业务的情况下，所述处理单元，具体用于继续使用所述第二设备证书处理所述第一业务。
结合第十二方面，在第十二方面的某些实现方式中，在所述权限验证结果为所述运载工具不具有进行所述第一业务的权限的情况下，所述处理单元，具体用于使用所述第一设备证书处理所述第一业务。
第十三方面，提供了一种通信装置，该装置包括：收发单元和处理单元，所述收发单元用于接收第一设备发送的第二请求消息，所述第二请求消息用于请求所述第一网络设备对所述第二设备证书进行验证，所述第一设备包括运载工具或第二网络设备；所述处理单元，用于根据所述设备标识和所述应用场景标识，确定所述第二设备证书的验证结果；所述收发单元，还用于向所述第一设备发送第二响应消息，所述第二响应消息用于指示所述第二设备证书的验证结果。
结合第十三方面，在第十三方面的某些实现方式中，所述第二请求消息包括：所述第二设备证书、所述设备标识和所述应用场景标识。
结合第十三方面，在第十三方面的某些实现方式中，所述处理单元，具体用于：验证所述设备标识和所述应用场景标识的有效性；在所述设备标识和所述应用场景标识有效的情况下，确定所述第二设备证书的验证结果为验证成功。
结合第十三方面，在第十三方面的某些实现方式中，所述处理单元，具体用于验证所述设备标识和所述第一网络设备中预设的设备标识是否一致，以及所述应用场景标识和所述第一网络设备中预设的应用场景标识是否一致。
结合第十三方面，在第十三方面的某些实现方式中，所述处理单元，还用于将所述第一设备证书的状态保持为生效状态。
结合第十三方面，在第十三方面的某些实现方式中，所述第二请求消息还包括：消息签名；所述处理单元，还用于使用所述第二设备证书验证所述消息签名的有效性。
结合第十三方面，在第十三方面的某些实现方式中，所述应用场景标识包括以下内容至少一种：字符串、可读名称和数字ID。
第十四方面，提供了一种通信装置，所述装置包括：收发单元和处理单元；所述收发单元，用于：接收运载工具发送的第三请求消息，所述第三请求消息用于请求所述第二网络设备验证所述运载工具是否具有进行第一业务的权限，所述第三请求消息包括以下内容至少一项：第二设备证书、设备标识和应用场景标识，所述第二设备证书用于处理所述第一业务，所述设备标识用于标识所述运载工具和/或所述运载工具包括的部件，所述应用场景标识用于标识第一设备证书的使用场景，所述第一设备证书为所述运载工具进行第一业务时所使用的证书；向所述第一网络设备发送第二请求消息，所述第二请求消息用于请求所述第一网络设备对所述第二设备证书进行验证，所述第二请求消息包括所述第二设备证书、所述设备标识和所述应用场景标识；接收所述第一网络设备发送的第二响应消息，所述第二响应消息包括与所述设备标识和所述应用场景标识相关联的所述第二设备证书的验证结果；所述处理单元，用于根据所述第二设备证书的验证结果，向所述运载工具发送第三响应消息，所述第三响应消息用于指示所述运载工具的权限验证结果。
结合第十四方面，在第十四方面的某些实现方式中，在所述第二证书的验证结果为成功的情况下，所述第三响应消息用于指示所述运载工具具有进行所述第一业务的权限。
第十五方面，提供一种通信装置，该装置包括：至少一个处理器和存储器，所述至少 一个处理器与所述存储器耦合，用于读取并执行所述存储器中的指令，使得该装置实现上述第一方面至第七方面中任意一种实现方式的方法。
第十六方面，提供一种计算机可读介质，所述计算机可读介质存储有程序代码，当所述计算机程序代码在计算机上运行时，使得计算机执行上述第一方面至第七方面中任意一种实现方式的方法。
第十七方面，提供一种计算机程序产品，所述计算机产品包括计算机程序，当所述计算机程序被运行时，使得计算机执行上述第一方面至第七方面中任意一种实现方式的方法。
第十八方面，提供一种芯片，该芯片包括：电路，该电路用于执行上述第一方面至第七方面中任意一种实现方式的方法。
第十九方面，提供了一种运载工具，包括：至少一个处理器和存储器，所述至少一个处理器与所述存储器耦合，用于读取并执行所述存储器中的指令，使得该装置实现上述第一方面、第四方面或第五方面中任意一种实现方式的方法。
结合第十九方面，在第十九方面的某些实现方式中，所述运载工具为车辆。
第二十方面，提供了一种服务器，包括：至少一个处理器和存储器，所述至少一个处理器与所述存储器耦合，用于读取并执行所述存储器中的指令，使得该装置实现上述第二方面、第三方面、第六方面、第七方面中任意一种实现方式的方法。
附图说明
图1是本申请实施例提供的运载工具的功能性示意图；
图2是本申请实施例提供的通信方法所适用的系统架构；
图3是本申请实施例提供的一种通信方法的示意性流程图；
图4是本申请实施例提供的另一种通信方法的示意性流程图；
图5是本申请实施例提供的另一种通信方法的示意性流程图；
图6是本申请实施例提供的另一种通信方法的示意性流程图；
图7是本申请实施例提供的另一种通信方法的示意性流程图；
图8是本申请实施例提供的另一种通信方法的示意性流程图；
图9是本申请实施例提供的另一种通信方法的示意性流程图；
图10是本申请实施例提供的一种通信装置；
图11是本申请实施例提供的另一种通信装置。
具体实施方式
下面将结合附图，对本申请实施例中的技术方案进行描述。
图1是本申请实施例提供的运载工具100的一个功能性示意图。应理解，图1及相关描述仅为一种举例，并不对本申请实施例中的运载工具进行限定。
运载工具100可包括多种子系统，例如感知系统120和计算平台130。可选地，该运载工具100可包括更多或更少的子系统，并且每个子系统都可包括一个或多个部件。另外，该运载工具100的每个子系统和部件可以通过有线或者无线的方式实现互连。
感知系统120可包括用于感测关于运载工具100周边的环境的信息的若干种传感器。例如，感知系统120可以包括定位系统，该定位系统可以是全球定位系统(global positioning  system，GPS)，也可以是北斗系统或者其他定位系统。感知系统120可以包括惯性测量单元(inertial measurement unit，IMU)等、激光雷达、毫米波雷达、超声波雷达以及摄像装置中的一种或者多种。
运载工具100的部分或所有功能可以由计算平台130控制。计算平台130可包括处理器131至13n(n为正整数)，处理器是一种具有信号的处理能力的电路，在一种实现中，处理器可以是具有指令读取与运行能力的电路，例如中央处理单元(central processing unit，CPU)、微处理器、图形处理器(graphics processing unit，GPU)(可以理解为一种微处理器)、或数字信号处理器(digital signal processor，DSP)等；在另一种实现中，处理器可以通过硬件电路的逻辑关系实现一定功能，该硬件电路的逻辑关系是固定的或可以重构的，例如处理器为专用集成电路(application-specific integrated circuit，ASIC)或可编程逻辑器件(programmable logic device，PLD)实现的硬件电路，例如FPGA。在可重构的硬件电路中，处理器加载配置文档，实现硬件电路配置的过程，可以理解为处理器加载指令，以实现以上部分或全部单元的功能的过程。此外，处理器还可以是针对人工智能设计的硬件电路，其可以理解为一种ASIC，例如神经网络处理单元(neural network processing unit，NPU)、张量处理单元(tensor processing unit，TPU)、深度学习处理单元(deep learning processing unit，DPU)等。此外，计算平台130还可以包括存储器，存储器用于存储指令，处理器131至13n中的部分或全部处理器可以调用存储器中的指令，以实现相应的功能。
计算平台130可基于从各种子系统(例如，感知系统120)接收的输入来控制运载工具100的功能。在一些实施例中，计算平台130可用于对运载工具100及其子系统的许多方面提供控制。
可选地，上述组件只是一个示例，实际应用中，上述各个模块中的组件有可能根据实际需要增添或者删除，图1不应理解为对本申请实施例的限制。
本申请中的运载工具100可以包括：路上交通工具、水上交通工具、空中交通工具、工业设备、农业设备、或娱乐设备等。例如运载工具100可以为车辆，该车辆为广义概念上的车辆，可以是交通工具(如商用车、乘用车、摩托车、飞行车、火车等)，工业车辆(如：叉车、挂车、牵引车等)，工程车辆(如挖掘机、推土车、吊车等)，农用设备(如割草机、收割机等)，游乐设备，玩具车辆等，本申请实施例对车辆的类型不作具体限定。再如，运载工具100可以为飞机、或轮船等交通工具。
以下以运载工具为车辆为例，说明本申请需要解决的技术问题以及所采用的技术方案。
随着智能车在日常生活中被广泛使用，车辆内部和对外通信的业务逐渐增多，在许多场景下需要进行车端身份认证和鉴权，从而保证通信主体身份的真实性和业务权限的合法性。例如，认证车辆是否具备车端日志、数据上传云端，车联网(vehicle to everything，V2X)通信，车内数据安全传输等权限。
由于车辆的产品生命周期较长，车内部件中存储的设备证书必然会出现过期、吊销等情况，甚至可能出现因业务冻结而临时不允许证书使用的情况。这就需要车辆具备在线申请证书以及证书状态确认的能力。然而，当前车辆在线申请证书的方案中，一部分方案不支持证书的状态确认，车辆仅在业务处理过程中才能发现证书异常，这样增大了业务异常处理难度。另外一部分方案虽然支持证书状态的确认过程，但是，整个证书申请和确认过程中需要进行多次信息交互，并且任意步骤中断都会导致这个流程中断，只能重新开始进 行证书的申请或确认流程，整个证书的申请或确认流程复杂、可靠性差，重试成本较高。
例如，在证书申请过程中，车辆需要和证书服务模块进行多次的信息交互，车辆需要根据证书服务模块的指令，修改特定的参数(例如，服务器地址等等)，整个证书的申请流程较为复杂，可靠性差。
本申请实施例提供了一种通信方法、装置以及运载工具，能够降低整个证书申请和确认流程的复杂度。
在介绍本申请实施例提供的通信方法之前，首先介绍通信方法所适用的系统架构。
图2是本申请实施例提供的通信方法所适用的系统架构。
如图2所示，该系统架构涉及车端部件/整车与外部数字证书服务模块之间的交互系统。其中，数字证书服务模块可以在云端平台或服务器上部署。车端部件可以包括：车载网关(vehicle gateway，VGW)、移动数据中心(mobile data centers，MDC)、智能座舱数据中心(cockpit data center，CDC)、车载通信盒子(telematics box,T-box)、传感器(Sensor)、电子控制单元(electronic control unit，ECU)、整车动态控制(vehicle dynamic control，VDC)等。
其中，数字证书服务模块与车辆之间可以通过无线通信通道实现信息交互。
图3是本申请实施例提供的一种通信方法的示意性流程图，方法300可以应用于图2的系统架构中，方法300可以包括如下步骤。
S301，运载工具向第一网络设备发送第一请求消息。
其中，第一请求消息用于请求第一网络设备签发设备证书，该第一请求消息可以包括：设备标识和应用场景标识，该设备标识用于标识运载工具和/或运载工具包括的部件，该应用场景标识用于标识第一设备证书的使用场景，第一设备证书为运载工具进行第一业务时所使用的证书
示例性地，第一业务可以是运载工具当前正在进行的业务，第一业务可以包括：传感器数据上传、软件升级或者地图下载等等。第一业务可以与应用场景标识具有对应关系，例如，当第一业务为软件升级时，应用场景标识可以用于标识第一设备证书的使用场景是软件升级场景。
可选地，运载工具包括的部件可以包括：车载网关、移动数据中心、智能座舱数据中心、车载通信盒子、传感器、电子控制单元、整车动态控制中的一种或多种，在本申请中，部件和设备表示的意思可以相同。例如，设备证书可以理解为上述任一部件进行业务时所使用的证书。
可选地，第一网络设备可以是证书服务模块。
其中，字符串可以理解为由数字、字母、下划线组成的一串字符，其可以是编程语言中表示文本的数据类型；可读名称可以理解为用户可以理解的词语，数字ID可以理解为数字标识。
S302，第一网络设备根据设备标识和应用场景标识确定第二设备证书。
S303，运载工具接收第一网络设备发送的第一响应消息。
其中，第一响应消息可以包括第二设备证书，该第二设备证书与设备标识和应用场景标识相关联，且第二设备证书用于处理第一业务。
可选地，第二设备证书可以是未生效的设备证书，第二设备证书用于处理第一业务可 以理解为运载工具可以使用第二设备证书处理第一业务。
本申请实施例中，由于运载工具向第一网络设备发送的第一请求消息中携带设备标识和应用场景标识，从而使得第一网络设备可以根据该设备标识和应用场景标识确定第二设备证书。通过这样的方式，在第一网络设备签发第二设备证书的过程中，无需与运载工具再次进行信息交互，运载工具也无需同步修改特定的参数，能够降低证书申请的流程复杂度，提高证书申请的效率。
一个实施例中，在步骤S303之后，该方法还包括：运载工具使用第一设备证书或第二设备证书处理第一业务。
本申请实施例中，运载工具在接收到第二设备证书后，既可以使用第一设备证书处理第一业务，也可以使用第二设备证书处理第一业务。这样，使得运载工具使用设备证书处理业务的方式更加的灵活。
运载工具在申请了第二设备证书后，可以直接向第一网络设备发起证书确认流程。
一个实施例中，在步骤S303之后，该方法还包括：运载工具向第一网络设备发送第二请求消息，该第二请求消息用于请求第一网络设备对第二设备证书进行验证；运载工具接收第一网络设备发送的第二响应消息，该第二响应消息包括与设备标识和应用场景标识相关联的第二设备证书的验证结果。
可选地，上述第二请求消息可以包括：第二设备证书、设备标识和应用场景标识。
本申请实施例中，运载工具申请了第二设备证书后，能够迅速发起第二设备证书确认流程，从而使得运载工具可以根据第二设备证书的验证结果进行第一业务的处理。
第一网络设备可以根据设备标识和应用场景标识，确定第二设备证书的验证结果，从而在第二响应消息中，携带该第二设备证书的验证结果。
一个实施例中，第一网络设备可以验证设备标识和应用场景标识的有效性；在设备标识和应用场景标识有效情况下，确定第二设备证书的验证结果为验证成功。
可选地，第一网络设备验证设备标识和应用场景标识的有效性，包括：第一网络设备验证设备标识和第一网络设备中预设的设备标识是否一致，以及应用场景标识和第一网络设备中预设的应用场景标识是否一致。
本申请实施例中，第一网络设备可以通过验证设备标识与第一网络设备中预设的设备标识是否一致，以及应用场景标识与第一网络设备中预设的应用场景标识是否一致，来验证设备标识和应用场景标识的有效性，从而确定第二设备证书的验证结果。
一个实施例中，第二请求消息还可以包括：消息签名，在第一网络设备根据设备标识和应用场景标识，确定第二设备证书的验证结果之前，该方法还包括：第一网络设备使用第二设备证书验证消息签名的有效性。
本申请实施例中，第一网络设备还可以使用第二设备证书验证签名的有效性，在签名有效的情况下，第一网络设备再进行设备标识和应用场景标识有效性的验证。
一个实施例中，第一网络设备在确认了第二设备证书验证成功后，将第一设备证书的状态保持为生效状态。
本申请实施例中，在第二设备证书的验证结果为验证成功的情况下，第一网络设备可以不将第一设备证书的生效状态切换为吊销状态。这样，运载工具侧可以同时存在已生效的第一设备证书和第二设备证书，第一设备证书和第二设备证书可以相互备份，一张证书 损坏可以使用另外一张证书处理业务。
一个实施例中，在运载工具向第一网络设备发送第二请求消息之前，该方法还包括：运载工具确定本地保存的私钥与第二设备证书的公钥是否匹配；在本地保存的私钥与第二设备证书的公钥匹配的情况下，向第一网络设备发送第二请求消息。
可选地，在确定在本地保存的私钥与第二设备证书的公钥不匹配的情况下，运载工具可以向用户提示第一业务无法进行。
其中，上述私钥和证书公钥的匹配原理是：证书公钥实际上是一个加密的字符串，任何人都可以看到其内容，而私钥的内容只用拥有者(运载工具)才可以知晓。通过该公钥加密的密文使用经过配对的私钥可以解密，而公钥不能解密私钥。在本申请中，如果运载工具本地保存的私钥能够解密证书的公钥，则说明私钥与公钥匹配。
本申请实施例中，运载工具在发起证书确认流程前，可以在本地检查私钥和证书公钥的匹配性，如果运载工具存储的私钥和第二设备证书的公钥匹配，则可以进行证书确认流程；如果运载工具存储的私钥和第二设备证书的公钥不匹配，则无需联网即可判断第二设备证书不可用，可以提前进行相应的补救措施。
运载工具在接收到第二证书的验证结果后，能够结合运载工具当前的证书使用情况，进行不同的处理。
一个实施例中，在第二设备证书的验证结果为验证成功，且运载工具使用第一设备证书处理第一业务的情况下，运载工具使用第一设备证书或第二设备证书处理第一业务，包括：运载工具将第一设备证书切换为第二设备证书，处理第一业务。
本申请实施例中，在运载工具在确认证书的验证结果为成功，且运载工具正在使用第一设备证书的情况下，运载工具可以将第一设备证书切换为第二设备证书处理第一业务。通过这样的方式，运载工具能够及时使用经过确认的新设备证书处理业务，保障了第一业务处理的安全性。
一个实施例中，在第二设备证书的验证结果为验证成功，且运载工具使用第二设备证书处理第一业务的情况下，运载工具使用第一设备证书或第二设备证书处理第一业务，包括：运载工具继续使用第二设备证书处理第一业务。
本申请实施例中，在运载工具在确认证书的验证结果为成功，且运载工具已经使用第二设备证书处理业务的情况下，运载工具能够继续使用第二设备证书处理第一业务，无需进行设备证书的切换，从而提高第一业务处理效率。
一个实施例中，在第二设备证书的验证结果为验证失败的情况下，运载工具使用第一设备证书或第二设备证书处理第一业务，包括：运载工具使用第一设备证书处理第一业务。
可选地，在运载工具在确认证书的验证结果为失败的情况下，运载工具还可以向用户提示第二设备证书无法使用。
可选地，运载工具可以通过显示屏或语音等多种方式向用户提示第二设备证书无法使用。
可选地，在重复进行证书确认的流程中，如果上一次第二设备证书的证书验证结果为成功，即运载工具已经使用第二设备证书处理第一业务。当运载工具再次发起证书确认流程，且本次第二设备证书的验证结果为失败，则运载工具可以向用户提示第一业务无法进行。
本申请实施例中，在运载工具在确认证书的验证结果为失败的情况下，运载工具能够使用第一设备证书处理第一业务，这样，运载工具能够避免使用未经过确认的第二设备证书处理第一业务，从而保障了第一业务处理的安全性。
运载工具还可以在权限验证请求消息中，携带第二设备证书、设备标识和应用场景标识至少一种，从而使得第二网络设备可以发起证书确认流程。
一个实施例中，在步骤S303之后，该方法还包括：运载工具向第二网络设备发送第三请求消息，该第三请求消息用于请求第二网络设备验证运载工具是否具有进行第一业务的权限，该第三请求消息包括以下内容至少一项：第二设备证书、设备标识和应用场景标识；运载工具接收第二网络设备发送的第三响应消息，该第三响应消息用于指示运载工具的权限验证结果。
可选地，第二网络设备可以是业务模块，该业务模块可以验证车辆是否具备处理第一业务的权限。
本申请实施例中，运载工具可以在第三请求消息中携带设备标识和/或应用场景标识，从而使得第二网络设备能够向第一网络设备发起第二设备证书的验证流程。通过这样的方式，可以省去运载工具和第一网络设备的信令交互过程，运载工具仅需根据业务权限的验证结果进行第一业务的处理。
运载工具在接收到权限验证结果后，能够结合运载工具当前的证书使用情况，进行不同的处理。
一个实施例中，在权限验证结果为运载工具具有进行第一业务的权限，且运载工具使用第一设备证书处理第一业务的情况下，运载工具使用第一设备证书或第二设备证书处理第一业务，包括：运载工具将第一设备证书切换为第二设备证书，处理第一业务。
本申请实施例中，在运载工具确认具有进行第一业务权限，且运载工具正在使用第一设备证书的情况下，运载工具可以将第一设备证书切换为第二设备证书处理第一业务。通过这样的方式，运载工具能够及时使用经过确认的新设备证书处理业务，既保障了第一业务处理的安全性，又省去了运载工具和第一网络设备的信令交互过程。
一个实施例中，在权限验证结果为运载工具具有进行第一业务的权限，且运载工具使用第二设备证书处理第一业务的情况下，运载工具使用第一设备证书或第二设备证书处理第一业务，包括：运载工具继续使用第二设备证书处理第一业务。
本申请实施例中，在运载工具确认具有进行第一业务权限，且运载工具已经使用第二设备证书处理业务的情况下，运载工具能够继续使用第二设备证书处理第一业务，无需进行设备证书的切换，不仅提高第一业务处理效率，也省去了运载工具和第一网络设备的信令交互过程。
一个实施例中，在权限验证结果为运载工具不具有进行第一业务的权限的情况下，运载工具使用第一设备证书或第二设备证书处理第一业务，包括：运载工具使用第一设备证书处理第一业务。
本申请实施例中，在运载工具在确认不具有进行第一业务的权限的情况下，运载工具能够使用第一设备证书处理第一业务，这样，运载工具能够避免使用未经过确认的第二设备证书处理第一业务，从而保障了第一业务处理的安全性。
图4是本申请实施例提供的一种通信方法的示意性流程图，方法400可以应用于图2 的系统架构中，方法400也可以应用于方法300中证书确认流程中，方法400可以包括如下步骤。
S401，运载工具向第一网络设备发送第二请求消息。
其中，该第二请求消息用于请求第一网络设备对第二设备证书进行验证。
可选地，上述第二请求消息可以包括：第二设备证书、设备标识和应用场景标识。
可选地，上述第一网络设备可以是证书服务模块。
一个实施例中，在步骤S401之前，该方法还包括：运载工具确定本地保存的私钥与第二设备证书的公钥是否匹配；在本地保存的私钥与第二设备证书的公钥匹配的情况下，向第一网络设备发送第二请求消息。
可选地，在确定在本地保存的私钥与第二设备证书的公钥不匹配的情况下，运载工具可以向用户提示第一业务无法进行。
S402，第一网络设备根据设备标识和应用场景标识，验证第二设备证书。
一个实施例中，第一网络设备可以验证设备标识和应用场景标识的有效性；在设备标识和应用场景标识有效情况下，确定第二设备证书的验证结果为验证成功。
可选地，第一网络设备验证设备标识和应用场景标识的有效性，包括：第一网络设备验证设备标识和第一网络设备中预设的设备标识是否一致，以及应用场景标识和第一网络设备中预设的应用场景标识是否一致。
一个实施例中，第二请求消息还可以包括：消息签名，在第一网络设备根据设备标识和应用场景标识，步骤S402之前，该方法还包括：第一网络设备使用第二设备证书验证消息签名的有效性。这样，在消息签名有效的情况下，第一网络设备再进行设备标识和应用场景标识有效性的验证。
S403，运载工具接收第一网络设备发送的第二响应消息。
其中，该第二响应消息包括与设备标识和应用场景标识相关联的第二设备证书的验证结果。
本申请实施例中，运载工具可以单独的发起设备证书确认流程，即设备证书的确认流程不必在设备证书的申请流程后执行，这样能够使得证书确认流程的适用场景更加多样化，满足不同用户的需求。
一个实施例中，在步骤S401之前，该方法还包括：运载工具使用第一设备证书或第二设备证书进行第一业务的处理。其中，第一设备证书可以是第二设备证书申请前运载工具用于处理第一业务的证书。
一个实施例中，在步骤S403之后，该方法还包括：在第二设备证书的验证结果为验证成功，且运载工具使用第一设备证书处理第一业务的情况下，运载工具使用第一设备证书或第二设备证书处理第一业务，包括：运载工具将第一设备证书切换为第二设备证书，处理第一业务。
本申请实施例中，在运载工具在确认证书的验证结果为成功，且运载工具正在使用第一设备证书的情况下，运载工具可以将第一设备证书切换为第二设备证书处理第一业务。通过这样的方式，运载工具能够及时使用经过确认的新设备证书处理业务，保障了第一业务处理的安全性。
一个实施例中，在步骤S403之后，该方法还包括：在第二设备证书的验证结果为验 证成功，且运载工具使用第二设备证书处理第一业务的情况下，运载工具使用第一设备证书或第二设备证书处理第一业务，包括：运载工具继续使用第二设备证书处理第一业务。
本申请实施例中，在运载工具在确认证书的验证结果为成功，且运载工具已经使用第二设备证书处理业务的情况下，运载工具能够继续使用第二设备证书处理第一业务，无需进行设备证书的切换，从而提高第一业务处理效率。
一个实施例中，在步骤S403之后，该方法还包括：在第二设备证书的验证结果为验证失败的情况下，运载工具使用第一设备证书或第二设备证书处理第一业务，包括：运载工具使用第一设备证书处理第一业务。
可选地，在运载工具在确认证书的验证结果为失败的情况下，运载工具还可以向用户提示第二设备证书无法使用。
可选地，运载工具可以通过显示屏或语音等多种方式向用户提示第二设备证书无法使用。
可选地，在重复进行证书确认的流程中，如果上一次第二设备证书的证书验证结果为成功，即运载工具已经使用第二设备证书处理第一业务。当运载工具再次发起证书确认流程，且本次第二设备证书的验证结果为失败，则运载工具可以向用户提示第一业务无法进行。
图5是本申请实施例提供的一种通信方法的示意性流程图，方法500可以应用于图2的系统架构中，方法500也可以应用于方法300中业务权限验证流程中，方法500可以包括如下步骤。
S501，运载工具向第二网络设备发送第三请求消息。
其中，第三请求消息用于请求第二网络设备验证运载工具是否具有进行第一业务的权限。该第三请求消息包括以下内容至少一种：第二设备证书、设备标识和应用场景标识，该第二设备证书用于处理第一业务，设备标识用于标识运载工具和/或运载工具包括的部件，应用场景标识用于标识第一设备证书的使用场景，该第一设备证书为所述运载工具进行第一业务时所使用的证书。
可选地，第三请求消息中也可以不携带应用场景标识，仅携带设备标识，即第二网络设备只负责第一业务权限的认证，第二网络设备仅仅根据设备标识就能够确定第一业务的应用场景。
可选地，第三请求消息中可以不携带应用场景标识和设备标识，即第二网络设备只负责第一业务权限的认证，且第二网络设备已经知晓运载工具的身份，第二网络设备能够直接确定第一业务的应用场景。
S502，第二网络设备向第一网络设备发送第二请求消息。
其中，第二请求消息用于第一网络设备对第二设备证书进行验证。
可选地，第二请求消息可以包括：第二设备证书、设备标识和应用场景标识。
S503，第一网络设备根据设备标识和应用场景标识验证第二设备证书。
一个实施例中，第一网络设备可以验证设备标识和应用场景标识的有效性；在设备标识和应用场景标识有效情况下，确定第二设备证书的验证结果为验证成功。
可选地，第一网络设备验证设备标识和应用场景标识的有效性，包括：第一网络设备验证设备标识和第一网络设备中预设的设备标识是否一致，以及应用场景标识和第一网络 设备中预设的应用场景标识是否一致。
一个实施例中，第二请求消息还可以包括：消息签名，在第一网络设备根据设备标识和应用场景标识，步骤S503之前，该方法还包括：第一网络设备使用第二设备证书验证消息签名的有效性。这样，在消息签名有效的情况下，第一网络设备再进行设备标识和应用场景标识有效性的验证。
S504，第二网络设备接收第一网络设备发送的第二响应消息。
其中，该第二响应消息包括与所述设备标识和所述应用场景标识相关联的所述第二设备证书的验证结果。
S505，运载工具接收第二网络设备发送的第三响应消息。
其中，该第三响应消息用于指示运载工具的权限验证结果。
可选地，当权限验证结果为验证成功的情况下，第三响应消息可以指示运载工具具有进行第一业务的权限。当权限验证结果为失败的情况下，第三响应消息可以指示运载工具不具有进行第一业务的权限。
本申请实施例中，第二网络设备可以从运载工具发送的权限验证请求消息中获取设备标识和应用场景标识，并根据该设备标识和应用场景标识向第一网络设备发起第二设备证书的验证流程。通过这样的方式，可以省去运载工具和第一网络设备的信令交互过程，运载工具仅需根据业务权限的验证结果进行第一业务的处理。
运载工具在接收了第三响应消息后，根据权限验证结果，能够结合运载工具当前的设备证书使用情况，进行不同的处理。
一个实施例中，在权限验证结果为运载工具具有进行所述第一业务的权限，且运载工具使用第一设备证书处理第一业务的情况下，运载工具使用第一设备证书或第二设备证书处理第一业务，包括：运载工具将第一设备证书切换为第二设备证书，处理第一业务。
本申请实施例中，在运载工具确认具有进行第一业务权限，且运载工具正在使用第一设备证书的情况下，运载工具可以将第一设备证书切换为第二设备证书处理第一业务。通过这样的方式，运载工具能够及时使用经过确认的新设备证书处理业务，既保障了第一业务处理的安全性，又省去了运载工具和第一网络设备的信令交互过程。
一个实施例中，在权限验证结果为运载工具具有进行第一业务的权限，且运载工具使用第二设备证书处理第一业务的情况下，运载工具使用第一设备证书或第二设备证书处理第一业务，包括：运载工具继续使用第二设备证书处理第一业务。
本申请实施例中，在运载工具确认具有进行第一业务权限，且运载工具已经使用第二设备证书处理业务的情况下，运载工具能够继续使用第二设备证书处理第一业务，无需进行设备证书的切换，不仅提高第一业务处理效率，也省去了运载工具和第一网络设备的信令交互过程。
一个实施例中，在权限验证结果为运载工具不具有进行第一业务的权限的情况下，运载工具使用第一设备证书或第二设备证书处理第一业务，包括：运载工具使用第一设备证书处理第一业务。
本申请实施例中，在运载工具在确认不具有进行第一业务的权限的情况下，运载工具能够使用第一设备证书处理第一业务，这样，运载工具能够避免使用未经过确认的第二设备证书处理第一业务，从而保障了第一业务处理的安全性。
图6是本申请实施例提供的另一种通信方法的示意性流程图，方法600可以是对方法300步骤S301至S303的详细描述，方法600可以包括以下步骤。
S601，车端部件进行证书检查。
具体地，车端部件可以检查本地设备证书有效期，在设备证书即将过期和/或满足其他要求的条件下，车端部件可以发起证书申请过程，进行后续步骤。其中，其他要求的条件可以包括：车辆运行状态和/或用户确认等。例如，在车辆处于驻车的情况下，车辆向用户提示需要进行证书申请，用户在车载显示屏上进行确认后，车端部件可以发起证书申请流程。
可选地，车端部件进行证书检查可以是周期性的，例如，车端部件可以在每次车辆启动时、或者在每天特定的时间进行证书检查。
应理解，上述车端部件可以位于方法300中的运载工具中，其可以包括：车载网关、移动数据中心、智能座舱数据中心、车载通信盒子、传感器、电子控制单元、整车动态控制中的一种或多种。
S602，车端部件生成证书申请文件。
示例性地，车端部件可以随机生成公私钥对，并根据公钥生成证书申请文件，同时车端部件能够安全存储私钥。
S603，车端部件向证书服务模块发送证书申请请求消息。
具体地，车端部件可以向证书服务模块发送证书申请请求消息，该证书申请请求消息可以包括：设备标识、应用场景标识或者，设备标识、应用场景标识以及以下内容至少一种：设备证书、消息签名、证书申请文件和其他额外参数，上述证书申请消息可以是方法300中的第一请求消息。
其中，设备标识用于标识车端部件；应用场景标识可以由业务分配，用于标识该证书的使用场景，场景标识的具体形式可以是固定字符串、可读名称或数字ID等等。设备证书可以是车端当前业务使用的设备证书，该设备证书可以是方法300中的第一设备证书。消息签名可以是通过设备证书的私钥对设备标识、应用场景标识、证书申请文件、以及其他额外参数进行数字签名。其他额外参数用于增强证书的易用性和安全性，可以包括以下内容至少一种：业务流水号(用于唯一标识本次车端与证书服务模块的交互，便于问题定位和追溯)、时间戳(用于保证消息的新鲜性，放置重放攻击)、服务标识(用于标识本次请求的请求类型，便于流量转发)等。
S604，证书服务模块认证车端身份。
具体地，证书服务模块在接收到证书申请请求消息后，可以根据该证书申请请求消息认证车端的身份，可以包括以下方式中的至少一种：
(1)证书服务模块使用证书管理机构(Certificate Authority，CA)证书验证设备证书的合法性，检查设备证书的有效期是否过期，以及检查设备证书是否处于有效状态。
(2)证书服务模块使用设备证书验证证书申请请求消息的签名是否有效。
(3)证书服务模块进行身份鉴权，即检查设备标识、应用场景标识是否有效，以及是否允许进行证书申请。
其中，证书服务模块可以是方法300中的第一网络设备。
S605，证书服务模块根据设备标识和应用场景标识签发新设备证书。
示例性地，证书服务模块可以根据证书申请请求消息中的设备标识和应用场景标识，选择对应的证书签发地址、接口、标识ID等信息，签发新设备证书，该新设备证书可以是方法300中的第二设备证书。
可选地，证书服务模块可以通过配置文件、数据库等方式配置应用场景标识和证书签发服务信息的对应关系。
S606，证书服务模块向车端部件发送证书申请响应消息。
可选地，该证书申请响应消息可以包括：新设备证书，以及以下内容至少一种：云端证书、消息签名、应用场景标识和其他额外参数，上述证书申请响应消息可以是方法300中的第二响应消息。
其中，云端证书可以用于认证证书服务模块身份。消息签名可以通过云端证书的私钥对应用场景标识、新设备证书、以及其他额外参数合并进行的数字签名。应用场景标识可以与证书申请请求消息中的应用场景标识一致。其他额外参数用于增强证书的易用性和安全性，可以包括以下内容至少一种：业务流水号(用于唯一标识本次车端与证书服务模块的交互，便于问题定位和追溯)、时间戳(用于保证消息的新鲜性，放置重放攻击)、服务标识(用于标识本次请求的请求类型，便于流量转发)等。
S607，车端部件校验设备证书并存储。
具体地，车端部件接收到证书申请响应消息后，可以验证该消息中云端证书和消息签名，在云端证书和消息签名的验证通过后。车端部件校验设备证书并安全存储。
可选地，设备证书的校验过程可以包括：签名字段校验、有效期校验等等。
S608，车端部件后续仍使用旧设备证书处理业务。
具体地，车端部件可以仍然使用旧设备证书进行业务处理，待满足合适条件后将旧设备证书切换为新设备证书，上述业务可以是方法300中的第一业务。
可选地，合适条件可以包括以下内容至少一种：车端证书确认完成、车辆处于驻车状态和用户确认等等。
应理解，在申请实施例中，设备证书可以包括多种状态，即除了证书本身处于过期或吊销状态，还包括：待生效、生效和冻结等状态。其中，只有在证书处于生效状态时，才允许车端部件进行业务处理，其余状态下，均禁止车端部件进行业务处理。
还应理解，证书刚签发时处于待生效状态，证书服务模块对签发的证书确认成功后，将证书切换为生效状态。在证书超过使用期间后，证书服务模块将生效的证书切换为过期状态。在出现某些安全事件时，证书服务模块可以主动将证书的生效状态切换为吊销状态。在一些业务场景下，例如，用户订阅到期、业务停用等场景。证书服务模块可以证书由生效状态切换为冻结状态，待业务恢复后将证书由冻结状态恢复到生效状态。
本申请实施例中，车端部件向证书服务模块发送的证书申请请求消息中包括设备标识和应用场景标识，证书服务模块可以根据设备标识和应用场景标识选择对应的CA签发新证书，在整个过程中，车端部件无需和证书服务模块再次进行信息交互，这样，能够提高设备证书申请的效率，降低整个证书申请流程的复杂度。此外，在新证书申请完成后，车端部件可以仍使用旧证书处理业务，这样，在新证书完成确认流程完成前，不存在无证书可用的场景，能够提高业务的可靠性。
图7是本申请实施例提供的另一种通信方法的示意性流程图，方法700是对方法300 的证书确认流程以及方法400的步骤S401至S403详细描述，方法700可以在方法600后执行，方法700可以包括如下步骤。
S701，车端部件检查自身是否满足证书确认条件。
具体地，车端部件可以检查当前自身是否满足证书确认条件，当满足该条件时，车端部件发起证书确认流程，并进行后续步骤。其中，证书确认条件可以包括：车辆运行状态和/或用户确认等。例如，在车辆处于驻车的情况下，车端部件可以发起证书确认流程。
可选地，车端部件检查自身是否满足证书确认条件可以是周期性的，例如，车端部件可以在每次车辆启动时、或者在每天特定的时间进行检查。
S702，车端部件向证书服务模块发送证书确认请求消息。
可选地，该证书确认请求消息：可以包括内容：设备标识、应用场景标识或者，设备标识、应用场景标识以及以下内容至少一种：设备证书、消息签名和其他额外参数，该证书确认请求消息可以是方法300中的第二请求消息。
其中，设备标识用于标识车端部件；应用场景标识由业务分配，用于标识该证书的使用场景，场景标识的具体形式可以是固定字符串、可读名称或数字ID等等。设备证书可以是车端希望确认的设备证书(即方法300中的第二设备证书或方法600中的新设备证书)。消息签名可以是通过设备证书的私钥对设备标识、应用场景标识、以及其他额外参数进行数字签名。其他额外参数可以用于增强证书的易用性和安全性，可以包括以下内容至少一种：业务流水号(用于唯一标识本次车端与证书服务模块的交互，便于问题定位和追溯)、时间戳(用于保证消息的新鲜性，放置重放攻击)、服务标识(用于标识本次请求的请求类型，便于流量转发)等。
S703，证书服务模块检查设备证书状态。
具体地，证书服务模块在接收到证书确认请求消息后，可以根据该请求消息，检查设备证书的状态，包括以下方式至少一种：
(1)证书服务模块使用CA证书验证设备证书的合法性，检查设备证书的有效期是否过期，以及检查设备证书当前状态(未生效、已生效、冻结、已吊销等等)
(2)证书服务模块使用设备证书验证证书确认请求消息的签名是否有效。
(3)证书服务模块进行身份鉴权，即检查设备标识、应用场景标识是否有效，以及是否允许进行证书确认。
(4)在证书确认请求消息的签名、身份鉴权通过、设备证书校验完成且证书状态为未生效或已生效时，证书状态检查通过，否则不通过。
应理解，上述检查设备证书状态的过程，在方法300中是对第二设备证书验证的过程。检查通过的结果可以是方法300中第二设备证书验证的结果。
S704，证书服务模块刷新证书状态。
具体地，该步骤只有在证书状态检查通过，且证书状态为未生效时才执行。在执行时，设备证书状态可以从未生效状态刷新为已生效状态，同时，证书服务模块可以将设备标识和应用场景标识对应的已生效证书切换为吊销状态。
S705，证书服务模块向车端部件发送证书确认响应消息。
可选地，该证书确认响应消息包括证书确认结果，以及以下内容至少一种：云端证书、消息签名、应用场景标识、证书确认结果、以及其他额外参数，该证书确认响应消息可以 是方法300中的第二响应消息。
其中，证书确认结果可以包括成功或失败，即检查设备证书通过时，证书确认结果为成功。检查设备证书不通过时，证书确认结果为失败。云端证书用于认证证书服务模块身份。消息签名可以通过云端证书的私钥对应用场景标识、证书确认结果、以及其他额外参数合并进行的数字签名。应用场景标识可以与证书确认请求中的应用场景标识一致。其他额外参数用于增强证书的易用性和安全性，可以包括以下内容至少一种：业务流水号(用于唯一标识本次车端与证书服务模块的交互，便于问题定位和追溯)、时间戳(用于保证消息的新鲜性，放置重放攻击)、服务标识(用于标识本次请求的请求类型，便于流量转发)、备注信息(如证书具体状态、证书即将过期等，提高易用性)等。
S706，车端部件验证响应消息。
具体地，车端部件在接收到证书确认响应消息后，可以验证云端证书和消息签名，在云端证书和消息签名验证通过后，进行步骤S707。
S707，车端部件根据证书状态处理本地设备证书。
具体地，车端部件可以根据证书确认结果处理本地存储的设备证书，具体可以包括以下三种情况：
(1)证书确认结果为成功，且本次确认的设备证书已经用于业务(证书处于已生效状态时)，车端部件保持该证书不变，继续使用该证书进行业务处理。
(2)证书确认结果为成功，且本次确认的证书尚未用于业务(证书处于未生效状态时)，车端部件将该证书切换为业务处理使用的证书，旧证书可以在本地保留一段时间或直接删除，后续使用本次确认的证书处理业务。
在此种情况下，未生效证书完成确认后，证书服务模块可以将对应设备标识、应用场景标识的已生效证书状态切换为已吊销状态，后续车端部件进行业务处理时只能使用新证书。
可选地，在另一种实现方式中，可以不进行上述过程，即证书确认后车端部件允许使用新旧证书进行业务处理，同时还允许车端部件使用任意证书进行申请，即新旧证书可以同等地被使用。
(3)证书确认结果为失败，车端标记业务无法进行，在此种情况下，可以提示用户或制造商进行业务恢复和证书恢复。
可选地，在车端部件进行证书确认之前，可以检查本地私钥和设备证书的公钥是否匹配，在匹配的情况下，车端部件能够根据证书确认结果处理本地存储的设备证书。否则，车端标记业务无法进行，此时，车端部件可以提示用户或制造商进行业务恢复和证书恢复。
本申请实施例中，在证书的确认流程中，车端部件能够向证书服务模块发送设备标识和应用场景标识，证书服务模块可以根据设备标识和应用场景标识完成设备证书的确认，这样，能够降低整个证书确认流程的复杂度。并且，在新设备证书确认完成后，旧设备证书将会被吊销，这样，能够降低旧设备证书的滥用风险，提高设备证书的使用安全性。
图8是本申请实施例提供的另一种通信方法的示意性流程图，方法800可以是对方法300步骤S301至S303的详细描述，方法800可以包括以下步骤。
S801，车端部件进行证书检查。
具体地，车端部件可以检查本地设备证书有效期，在设备证书即将过期和/或满足其 他要求的条件下，车端部件可以发起证书申请过程，进行后续步骤。其中，其他要求的条件可以包括：车辆运行状态和/或用户确认等。例如，在车辆处于驻车的情况下，车辆向用户提示需要进行证书申请，用户在车载显示屏上进行确认后，车端部件可以发起证书申请过程。
可选地，车端部件进行证书检查可以是周期性的，例如，车端部件可以在每次车辆启动时、或者在每天特定的时间进行证书检查。
S802，车端部件生成证书申请文件。
示例性地，车端部件可以随机生成公私钥对，并根据公钥生成证书申请文件，同时安全存储私钥。
S803，车端部件向证书服务模块发送证书申请请求消息。
具体地，车端部件可以向证书服务模块发送证书申请请求消息，该证书申请请求消息可以包括设备标识、应用场景标识或者，设备标识、应用场景标识以下内容至少一种：设备证书、消息签名、证书申请文件和其他额外参数，上述证书申请请求消息可以是方法300中的第一请求消息。
其中，设备标识可以用于标识车端部件；应用场景标识由业务分配，用于标识该证书的使用场景，场景标识的具体形式可以是固定字符串、可读名称或数字ID等等。设备证书可以是车端当前业务使用的设备证书，该设备证书可以是方法300中的第一设备证书。消息签名可以是通过设备证书的私钥对设备标识、应用场景标识、证书申请文件、以及其他额外参数进行数字签名。其他额外参数用于增强证书的易用性和安全性，可以包括以下内容至少一种：业务流水号(用于唯一标识本次车端与证书服务模块的交互，便于问题定位和追溯)、时间戳(用于保证消息的新鲜性，放置重放攻击)、服务标识(用于标识本次请求的请求类型，便于流量转发)等。
S804，证书服务模块认证车端身份。
具体地，证书服务模块在接收到证书申请请求消息后，可以根据该证书申请请求消息认证车端的身份，包括：
(1)证书服务模块使用CA证书验证设备证书的合法性，检查设备证书的有效期是否过期，以及检查设备证书是否处于有效状态。
(2)证书服务模块使用设备证书验证证书申请请求消息的签名是否有效。
(3)证书服务模块进行身份鉴权，即检查设备标识、应用场景标识是否有效，以及是否允许进行证书申请。
S805，证书服务模块根据设备标识和应用场景标识签发新设备证书。
示例性地，证书服务模块可以根据证书申请请求消息中的设备标识和应用场景标识，选择对应的证书签发地址、接口、标识ID等信息，签发新设备证书，上述新设备证书可以是方法300中的第二设备证书。
可选地，证书服务模块可以通过配置文件、数据库等方式配置应用场景标识和证书签发服务信息的对应关系。
S806，证书服务模块向车端部件发送证书申请响应消息。
可选地，该证书申请响应消息包括新设备证书以及以下内容至少一种：云端证书、消息签名、应用场景标识和其他额外参数，上述证书申请响应消息可以是方法300中的第一 响应消息。
其中，云端证书用于认证证书服务模块身份。消息签名可以通过云端证书的私钥对应用场景标识、新设备证书、以及其他额外参数合并进行的数字签名。应用场景标识可以与证书申请请求中的应用场景标识一致。其他额外参数用于增强证书的易用性和安全性，可以包括以下内容至少一种：业务流水号(用于唯一标识本次车端与证书服务模块的交互，便于问题定位和追溯)、时间戳(用于保证消息的新鲜性，放置重放攻击)、服务标识(用于标识本次请求的请求类型，便于流量转发)等。
S807，车端部件校验设备证书并存储。
具体地，车端部件接收到证书申请响应消息后，可以验证该消息中云端证书和消息签名，在云端证书和消息签名的验证通过后。车端部件校验设备证书并安全存储。
可选地，设备证书的校验过程可以包括：签名字段校验、有效期校验等等。
S808，车端部件进行后续业务处理。
具体地，车端部件既可以使用旧设备证书进行业务处理，待满足合适的条件后切换设备证书，也可以直接在后续的业务处理过程中直接使用新设备证书。其中，合适的条件可以包括：证书确认完成、车辆处于驻车状态、用户确认等等。
本申请实施例中，在设备证书的申请流程中，在完成新设备证书申请后，车端部件可以直接使用未生效的新设备证书处理业务，这样，能够提高设备证书的使用效率。
图9是本申请实施例提供的另一种通信方法的示意性流程图，方法900是对方法300的业务权限验证流程以及方法500的步骤S501至S505详细描述，方法900可以在方法800后执行，方法800可以包括如下步骤。
S901，车端部件使用未经过显示确认的设备证书进行业务处理。
其中，未经过显示确认的设备证书可以理解为未经过设备证书确认流程确认的设备证书。
S902，证书服务模块检查设备证书状态。
示例性地，在该步骤中，证书服务模块可以获取车端的设备标识以及业务模块对应的应用场景标识，并根据该车端设备标识和应用场景标识检查证书状态。其中，设备标识和应用场景标识可以从业务模块中获取，即车端部件可以在向业务模块发送的权限验证请求消息中携带该设备标识和应用场景标识，并由业务模块发起证书验证流程。上述权限验证请求消息可以是方法300或方法500中的第三请求消息，业务模块可以是方法300或方法500中的第二网络设备。
检查证书的状态可以包括以下方式至少一项：
(1)证书服务模块校验设备证书，即云端服务模块CA证书验证设备证书的合法性，检查设备证书的有效期是过期，检查设备证书当前状态(例如，未生效、已生效、冻结、已吊销等等)。
(2)证书服务模块验证消息签名，即使用设备证书验证消息签名是否有效。
(3)证书服务模块进行身份鉴权，即证书服务模块检查设备标识、应用场景标识是否有效、是否允许进行证书确认过程。
(4)在消息签名、身份鉴权验证通过，设备证书校验完成，且证书状态为未生效或已生效时，证书检查通过，否则证书检查不通过。
可选地，在证书检查不通过的情况下，证书服务模块可以向车端部件提示证书无效。
应理解，上述检查设备证书状态的过程，在方法300中是对第二设备证书验证的过程。
S903，证书服务模块刷新证书状态。
具体地，该步骤只有在证书状态检查通过，且证书状态为未生效时才执行。在执行时，证书状态会从未生效状态刷新为已生效状态，同时，证书服务模块可以将设备标识和应用场景标识对应的已生效证书切换为吊销状态。
证书服务模块在检查了证书的状态后，可以向业务模块返回新设备证书的检查结果，该检查结果可以是方法300中的证书验证结果。
S904，车端部件根据业务处理结果处理本地设备证书。
具体地，业务模块可以结合证书模块对新设备证书的检查结果，来判断车端部件是否具有处理某项业务的权限，并将权限验证结果发送给车端部件，车端部件可以根据该权限验证结果，处理本地存储的设备证书，具体可以包括以下三种情况：
(1)权限验证结果为成功，且本次使用的设备证书已经用于业务(证书处于已生效状态时)，车端部件保持该证书不变，继续使用该证书进行业务处理。
(2)权限验证结果为成功，且本次使用的证书之间未用于业务(证书处于未生效状态时)，车端部件将该证书切换为业务处理使用证书，旧证书可以在本地保留一段时间或直接删除，后续使用本次确认的证书处理业务。
(3)权限验证结果为失败，且证书服务模块返回证书无效，车端可以提示用户或制造商进行业务恢复和证书恢复。
本申请实施例中，车端部件可以直接使用未生效的新设备证书进行业务处理，并且车端部件可以根据业务权限的验证结果，确定新旧证书的使用策略。通过这样的方式，车端部件可以省去与证书服务模块的信息交互过程，提高业务处理效率。
本申请实施例还提供用于实现以上任一种方法的装置，该装置包括用于实现以上任一种方法中运载工具、第一网络设备或第二网络设备所执行的各步骤的单元。
图10是本申请实施例提供的通信装置1000的示意图，该装置1000可以包括收发单元1010、存储单元1020和处理单元1030。收发单元1010用于接收或发送指令和/或数据，收发单元1010还可以称为通信接口或通信单元。存储单元1020，用于实现相应的存储功能，存储相应的指令和/或数据。处理单元1030用于进行数据处理。处理单元1030可以读取存储单元中的指令和/或数据，以使得装置1000实现前述通信方法。
作为一种设计，装置1000用于执行上述方法实施例中，运载工具所执行的动作。
作为一种设计，装置1000可以包括：收发单元1010；该收发单元1010，用于：向第一网络设备发送第一请求消息，该第一请求消息用于请求第一网络设备签发设备证书，第一请求消息包括：设备标识和应用场景标识，该设备标识用于标识运载工具和/或运载工具包括的部件，该应用场景标识用于标识第一设备证书的使用场景，该第一设备证书为运载工具进行第一业务时所使用的证书；接收第一网络设备发送的第一响应消息，该第一响应消息包括第二设备证书，该第二设备证书与设备标识和应用场景标识相关联，且第二设备证书用于处理第一业务。
一种可能的实现方式中，装置还包括：处理单元1030；该处理单元1030，用于使用第一设备证书或第二设备证书处理第一业务。
一种可能的实现方式中，收发单元1010，还用于：向第一网络设备发送第二请求消息，该第二请求消息用于请求第一网络设备对第二设备证书进行验证；接收第一网络设备发送的第二响应消息，该第二响应消息包括与设备标识和应用场景标识相关联的第二设备证书的验证结果。
一种可能的实现方式中，该第二请求消息包括：第二设备证书、设备标识和应用场景标识。
一种可能的实现方式中，在第二设备证书的验证结果为验证成功，且运载工具使用第一设备证书处理第一业务的情况下，处理单元1030，具体用于将第一设备证书切换为第二设备证书，处理第一业务。
一种可能的实现方式中，在第二设备证书的验证结果为验证成功，且运载工具使用第二设备证书处理第一业务的情况下，处理单元1030，具体用于继续使用第二设备证书处理第一业务。
一种可能的实现方式中，在第二设备证书的验证结果为验证失败的情况下，处理单元1030，具体用于使用第一设备证书处理第一业务。
一种可能的实现方式中，在第二设备证书的验证结果为验证失败的情况下，处理单元1030，还用于向用户提示第二设备证书无法使用。
一种可能的实现方式中，处理单元1030，还用于确定本地保存的私钥与第二设备证书的公钥是否匹配；收发单元1010，还用于在本地保存的私钥与第二设备证书的公钥匹配的情况下，向第一网络设备发送第二请求消息。
一种可能的实现方式中，收发单元1010，还用于：向第二网络设备发送第三请求消息，该第三请求消息用于请求第二网络设备验证运载工具是否具有进行第一业务的权限，该第三请求消息包括以下内容至少一种：第二设备证书、设备标识和应用场景标识；接收第二网络设备发送的第三响应消息，第三响应消息用于指示运载工具的权限验证结果。
一种可能的实现方式中，在权限验证结果为运载工具具有进行第一业务的权限，且运载工具使用第一设备证书进行第一业务处理的情况下，处理单元1030，具体用于将第一设备证书切换为第二设备证书，处理第一业务。
一种可能的实现方式中，在权限验证结果为运载工具具有进行第一业务的权限，且运载工具使用第二设备证书进行第一业务处理的情况下，处理单元1030，具体用于继续使用第二设备证书处理第一业务。
一种可能的实现方式中，在权限验证结果为运载工具不具有进行第一业务的权限的情况下，处理单元1030，具体用于使用第一设备证书处理第一业务。
作为一种设计，装置1000可以包括：收发单元1010，收发单元1010，用于：向第一网络设备发送第二请求消息，该第二请求消息用于请求第一网络设备对第二设备证书进行验证；接收第一网络设备发送的第二响应消息，该第二响应消息包括与设备标识和应用场景标识相关联的第二设备证书的验证结果；其中，设备标识用于标识运载工具和/或运载工具包括的部件，应用场景标识用于标识第一设备证书的使用场景，第一设备证书为运载工具进行第一业务时所使用的证书。
一种可能的实现方式中，第二请求消息包括：第二设备证书、设备标识和应用场景标识。
一种可能的实现方式中，装置还包括处理单元1030，该处理单元1030，用于使用第一设备证书或第二设备证书处理第一业务。
一种可能的实现方式中，在第二设备证书的验证结果为验证成功，且运载工具使用第一设备证书处理第一业务的情况下，处理单元1030，具体用于将第一设备证书切换为第二设备证书，处理第一业务。
一种可能的实现方式中，在第二设备证书的验证结果为验证成功，且运载工具使用第二设备证书处理第一业务的情况下，处理单元1030，具体用于继续使用第二设备证书处理第一业务。
一种可能的实现方式中，在第二设备证书的验证结果为验证失败的情况下，处理单元1030，具体用于使用第一设备证书处理第一业务。
一种可能的实现方式中，处理单元1030，还用于向用户提示第二设备证书无法使用。
一种可能的实现方式中，处理单元1030还用于确定本地保存的私钥与第二设备证书的公钥是否匹配；收发单元1010，具体用于在本地保存的私钥与第二设备证书的公钥匹配的情况下，向第一网络设备发送第二请求消息。
作为一种设计，装置1000可以包括：收发单元1010，该收发单元1010，用于：向第二网络设备发送第三请求消息，该第三请求消息用于请求第二网络设备验证运载工具是否具有进行第一业务的权限，第三请求消息包括以下内容至少一项：第二设备证书、设备标识和应用场景标识；该第二设备证书用于处理第一业务，设备标识用于标识运载工具和/或运载工具包括的部件，应用场景标识用于标识第一设备证书的使用场景，该第一设备证书为运载工具进行第一业务时所使用的证书；接收第二网络设备发送的第三响应消息，该第三响应消息用于指示运载工具的权限验证结果。
一种可能的实现方式中，装置1000还包括处理单元1030，该处理单元1030，用于使用第一设备证书或第二设备证书处理第一业务。
一种可能的实现方式中，在权限验证结果为运载工具具有进行第一业务的权限，且运载工具使用第一设备证书处理第一业务的情况下，处理单元1030，具体用于将第一设备证书切换为第二设备证书，处理第一业务。
一种可能的实现方式中，在权限验证结果为运载工具具有进行第一业务的权限，且运载工具使用第二设备证书处理第一业务的情况下，处理单元1030，具体用于继续使用第二设备证书处理第一业务。
一种可能的实现方式中，在权限验证结果为运载工具不具有进行第一业务的权限的情况下，处理单元1030，具体用于使用第一设备证书处理第一业务。
作为一种设计，装置1000用于执行上述方法实施例中，第一网络设备所执行的动作。
作为一种设计，装置1000可以包括：收发单元1010和处理单元1030；收发单元1010，用于接收运载工具发送的第一请求消息，该第一请求消息用于请求第一网络设备签发设备证书，该第一请求消息包括设备标识和应用场景标识，该设备标识用于标识运载工具和/或运载工具包括的部件，该应用场景标识用于标识第一设备证书的使用场景，该第一设备证书为运载工具进行第一业务时所使用的证书；处理单元1030，用于根据设备标识和应用场景标识，确定第二设备证书；收发单元1010，还用于向运载工具发送第一响应消息，该第一响应消息包括第二设备证书，第二设备证书用于处理第一业务。
一种可能的实现方式中，收发单元1010，还用于接收第一设备发送的第二请求消息，该第二请求消息用于请求第一网络设备对第二设备证书进行验证，该第一设备包括运载工具或第二网络设备；处理单元1030，还用于根据设备标识和应用场景标识，确定第二设备证书的验证结果；收发单元1010，还用于向第一设备发送第二响应消息，第二响应消息用于指示第二设备证书的验证结果。
一种可能的实现方式中，第二请求消息包括：第二设备证书、设备标识和应用场景标识。
一种可能的实现方式中，处理单元1030，具体用于：验证设备标识和应用场景标识的有效性；在设备标识和应用场景标识有效情况下，确定第二设备证书的验证结果为验证成功。
一种可能的实现方式中，处理单元1030，具体用于验证设备标识和第一网络设备中预设的设备标识是否一致，以及应用场景标识和第一网络设备中预设的应用场景标识是否一致。
一种可能的实现方式中，处理单元1030，还用于将第一设备证书的状态保持为生效状态。
一种可能的实现方式中，第二请求消息还包括：消息签名；处理单元1030，还用于使用第二设备证书验证消息签名的有效性。
一种可能的实现方式中，应用场景标识包括以下内容至少一种：字符串、可读名称和数字ID。
作为一种设计，装置1000可以包括：收发单元1010和处理单元1030，收发单元1010用于接收第一设备发送的第二请求消息，该第二请求消息用于请求第一网络设备对第二设备证书进行验证，该第一设备包括运载工具或第二网络设备；处理单元1030，用于根据设备标识和应用场景标识，确定第二设备证书的验证结果；收发单元1010，还用于向第一设备发送第二响应消息，该第二响应消息用于指示第二设备证书的验证结果。
一种可能的实现方式中，第二请求消息包括：第二设备证书、设备标识和应用场景标识。
一种可能的实现方式中，处理单元1030，具体用于：验证设备标识和应用场景标识的有效性；在设备标识和应用场景标识有效情况下，确定第二设备证书的验证结果为验证成功。
一种可能的实现方式中，处理单元1030，具体用于验证设备标识和第一网络设备中预设的设备标识是否一致，以及应用场景标识和第一网络设备中预设的应用场景标识是否一致。
一种可能的实现方式中，处理单元1030，还用于将第一设备证书的状态保持为生效状态。
一种可能的实现方式中，第二请求消息还包括：消息签名；处理单元1030，还用于使用第二设备证书验证消息签名的有效性。
一种可能的实现方式中，应用场景标识包括以下内容至少一种：字符串、可读名称和数字ID。
作为一种设计，装置1000用于执行上述方法实施例中，第二网络设备所执行的动作。
作为一种设计，装置1000包括：收发单元1010和处理单元1030；收发单元1010，用于：接收运载工具发送的第三请求消息，该第三请求消息用于请求第二网络设备验证运载工具是否具有进行第一业务的权限，该第三请求消息包括以下内容至少一项：第二设备证书、设备标识和应用场景标识，第二设备证书用于处理第一业务，该设备标识用于标识运载工具和/或运载工具包括的部件，该应用场景标识用于标识第一设备证书的使用场景，该第一设备证书为运载工具进行第一业务时所使用的证书；向第一网络设备发送第二请求消息，该第二请求消息用于请求第一网络设备对第二设备证书进行验证，该第二请求消息包括第二设备证书、设备标识和应用场景标识；接收第一网络设备发送的第二响应消息，该第二响应消息包括与设备标识和应用场景标识相关联的第二设备证书的验证结果；处理单元1030，用于根据第二设备证书的验证结果，向运载工具发送第三响应消息，该第三响应消息用于指示运载工具的权限验证结果。
一种可能的实现方式中，在第二证书的验证结果为成功的情况下，第三响应消息用于指示运载工具具有进行第一业务的权限。
可选地，若该装置1000位于运载工具100中，上述处理单元1030可以是图1所示的处理器131。
图11是本申请实施例提供的另一种通信装置1100的示意图。
该通信装置1100包括：存储器1110、处理器1120以及通信接口1130。其中，存储器1110、处理器1120，通信接口1130通过内部连接通路相连，该存储器1110用于存储指令，该处理器1120用于执行该存储器1110存储的指令，以控制通信接口1130获取信息，或者使所述通信装置执行上述各实施例中的通信方法。可选地，存储器1110既可以和处理器1120通过接口耦合，也可以和处理器1120集成在一起。
需要说明的是，上述通信接口1130使用例如但不限于收发器一类的收发装置。上述通信接口1130还可以包括输入/输出接口(input/output interface)。
处理器1120存储有一个或多个计算机程序，该一个或多个计算机程序包括指令。当该指令被所述处理器1120运行时，使得该通信装置1100执行上述各实施例中通信方法。
在实现过程中，上述方法的各步骤可以通过处理器1120中的硬件的集成逻辑电路或者软件形式的指令完成。结合本申请实施例所公开的方法可以直接体现为硬件处理器执行完成，或者用处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器1110，处理器1120读取存储器1110中的信息，结合其硬件完成上述方法的步骤。为避免重复，这里不再详细描述。
可选地，图11中的通信接口1130可以实现图10中的收发单元1010，图11中的存储器1110可以实现图10中的存储单元1020，图11中的处理器1120可以实现图10中的处理单元1030。
可选地，该装置1000或装置1100可以是计算平台，该计算平台可以是车载计算平台或云端计算平台。
可选地，该装置1000或装置1100可以位于图1中的运载工具100中。
可选地，该装置1000或装置1100可以为图1中运载工具中的计算平台130。
本申请实施例还提供一种计算机可读介质，所述计算机可读介质存储有程序代码，当 所述计算机程序代码在计算机上运行时，使得所述计算机执行上述图3至图9中的任一种方法。
本申请实施例还提供一种芯片，包括：电路，该电路用于执行上述图3至图9中的任一种方法。
本申请实施例还提供一种计算机程序产品，该计算机产品包括计算机程序，当所述计算机程序被运行时，使得计算机执行上述图3至图9中的任一种方法。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(Read-Only Memory，ROM)、随机存取存储器(Random Access Memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (35)

  1. 一种通信方法，其特征在于，所述方法包括：
    向第一网络设备发送第一请求消息，所述第一请求消息用于请求第一网络设备签发设备证书，所述第一请求消息包括：设备标识和应用场景标识，所述设备标识用于标识运载工具和/或所述运载工具包括的部件，所述应用场景标识用于标识第一设备证书的使用场景，所述第一设备证书为所述运载工具进行第一业务时所使用的证书；
    接收第一网络设备发送的第一响应消息，所述第一响应消息包括所述第二设备证书，所述第二设备证书与所述设备标识和所述应用场景标识相关联，且所述第二设备证书用于处理所述第一业务。
  2. 如权利要求1所述的方法，其特征在于，所述方法还包括：
    使用所述第一设备证书或所述第二设备证书处理所述第一业务。
  3. 如权利要求2所述的方法，其特征在于，所述方法还包括：
    向所述第一网络设备发送第二请求消息，所述第二请求消息用于请求所述第一网络设备对所述第二设备证书进行验证；
    接收所述第一网络设备发送的第二响应消息，所述第二响应消息包括与所述设备标识和所述应用场景标识相关联的所述第二设备证书的验证结果。
  4. 如权利要求3所述的方法，其特征在于，所述第二请求消息包括：所述第二设备证书、所述设备标识和所述应用场景标识。
  5. 如权利要求3或4所述的方法，其特征在于，在所述第二设备证书的验证结果为验证成功，且所述运载工具使用所述第一设备证书处理所述第一业务的情况下，所述使用所述第一设备证书或所述第二设备证书处理所述第一业务，包括：
    将所述第一设备证书切换为所述第二设备证书，处理所述第一业务。
  6. 如权利要求3或4所述的方法，其特征在于，在所述第二设备证书的验证结果为验证成功，且所述运载工具使用所述第二设备证书处理所述第一业务的情况下，所述使用所述第一设备证书或所述第二设备证书处理所述第一业务，包括：
    继续使用所述第二设备证书处理所述第一业务。
  7. 如权利要求3或4所述的方法，其特征在于，在所述第二设备证书的验证结果为验证失败的情况下，所述使用所述第一设备证书或所述第二设备证书处理所述第一业务，包括：
    使用所述第一设备证书处理所述第一业务。
  8. 如权利要求7所述的方法，其特征在于，所述方法还包括：
    向用户提示所述第二设备证书无法使用。
  9. 如权利要求3至8任一项所述的方法，其特征在于，在所述向第一网络设备发送第二请求消息之前，所述方法还包括：
    确定本地保存的私钥与所述第二设备证书的公钥是否匹配；
    所述向第一网络设备发送第二请求消息，包括：
    在本地保存的私钥与所述第二设备证书的公钥匹配的情况下，向所述第一网络设备发 送所述第二请求消息。
  10. 如权利要求2所述的方法，其特征在于，所述方法还包括：
    向第二网络设备发送第三请求消息，所述第三请求消息用于请求所述第二网络设备验证所述运载工具是否具有进行所述第一业务的权限，所述第三请求消息包括以下内容至少一项：所述第二设备证书、所述设备标识和所述应用场景标识；
    接收所述第二网络设备发送的第三响应消息，所述第三响应消息用于指示所述运载工具的权限验证结果。
  11. 如权利要求10所述的方法，其特征在于，在所述权限验证结果为所述运载工具具有进行所述第一业务的权限，且所述运载工具使用所述第一设备证书处理所述第一业务的情况下，所述使用所述第一设备证书或所述第二设备证书处理所述第一业务，包括：
    将所述第一设备证书切换为所述第二设备证书，处理所述第一业务。
  12. 如权利要求10所述的方法，其特征在于，在所述权限验证结果为所述运载工具具有进行所述第一业务的权限，且所述运载工具使用所述第二设备证书处理所述第一业务的情况下，所述使用所述第一设备证书或所述第二设备证书处理所述第一业务，包括：
    继续使用所述第二设备证书处理所述第一业务。
  13. 如权利要求10所述的方法，其特征在于，在所述权限验证结果为所述运载工具不具有进行所述第一业务的权限的情况下，所述使用所述第一设备证书或所述第二设备证书处理第一业务，包括：
    使用所述第一设备证书处理所述第一业务。
  14. 一种通信方法，其特征在于，所述方法包括：
    接收运载工具发送的第一请求消息，所述第一请求消息用于请求第一网络设备签发设备证书，所述第一请求消息包括设备标识和应用场景标识，所述设备标识用于标识所述运载工具和/或所述运载工具包括的部件，所述应用场景标识用于标识第一设备证书的使用场景，所述第一设备证书为所述运载工具进行第一业务时所使用的证书；
    根据所述设备标识和所述应用场景标识，确定第二设备证书；
    向所述运载工具发送第一响应消息，所述第一响应消息包括所述第二设备证书，所述第二设备证书用于处理所述第一业务。
  15. 如权利要求14所述的方法，其特征在于，所述方法还包括：
    接收第一设备发送的第二请求消息，所述第二请求消息用于请求所述第一网络设备对所述第二设备证书进行验证，所述第一设备包括所述运载工具或第二网络设备；
    根据所述设备标识和所述应用场景标识，确定所述第二设备证书的验证结果；
    向所述第一设备发送第二响应消息，所述第二响应消息用于指示所述第二设备证书的验证结果。
  16. 如权利要求15所述的方法，其特征在于，所述第二请求消息包括：所述第二设备证书、所述设备标识和所述应用场景标识。
  17. 如权利要求15或16所述的方法，其特征在于，所述根据所述设备标识和所述应用场景标识，确定所述第二设备证书的验证结果，包括：
    验证所述设备标识和所述应用场景标识的有效性；
    在所述设备标识和所述应用场景标识有效的情况下，确定所述第二设备证书的验证结 果为验证成功。
  18. 如权利要求17所述的方法，其特征在于，所述验证所述设备标识和所述应用场景标识的有效性，包括：
    验证所述设备标识和所述第一网络设备中预设的设备标识是否一致，以及所述应用场景标识和所述第一网络设备中预设的应用场景标识是否一致。
  19. 如权利要求17或18所述的方法，其特征在于，所述方法还包括：
    将所述第一设备证书的状态保持为生效状态。
  20. 如权利要求14至19任一项所述的方法，其特征在于，所述第二请求消息还包括：消息签名，在所述根据所述设备标识和所述应用场景标识，确定所述第二设备证书的验证结果之前，所述方法还包括：
    使用所述第二设备证书验证所述消息签名的有效性。
  21. 如权利要求14至20任一项所述的方法，其特征在于，所述应用场景标识包括以下内容至少一种：字符串、可读名称和数字ID。
  22. 一种通信方法，其特征在于，所述方法包括：
    接收运载工具发送的第三请求消息，所述第三请求消息用于请求所述第二网络设备验证所述运载工具是否具有进行第一业务的权限，所述第三请求消息包括以下内容至少一项：第二设备证书、设备标识和应用场景标识，所述第二设备证书用于处理所述第一业务，所述设备标识用于标识所述运载工具和/或所述运载工具包括的部件，所述应用场景标识用于标识第一设备证书的使用场景，所述第一设备证书为所述运载工具进行第一业务时所使用的证书；
    向所述第一网络设备发送第二请求消息，所述第二请求消息用于请求所述第一网络设备对所述第二设备证书进行验证，所述第二请求消息包括所述第二设备证书、所述设备标识和所述应用场景标识；
    接收所述第一网络设备发送的第二响应消息，所述第二响应消息包括与所述设备标识和所述应用场景标识相关联的所述第二设备证书的验证结果；
    根据所述第二设备证书的验证结果，向所述运载工具发送第三响应消息，所述第三响应消息用于指示所述运载工具的权限验证结果。
  23. 如权利要求22所述的方法，其特征在于，在所述第二设备证书的验证结果为成功的情况下，所述第三响应消息用于指示所述运载工具具有进行所述第一业务的权限。
  24. 一种通信装置，其特征在于，所述装置包括：收发单元；
    所述收发单元，用于：
    向第一网络设备发送第一请求消息，所述第一请求消息用于请求第一网络设备签发设备证书，所述第一请求消息包括：设备标识和应用场景标识，所述设备标识用于标识运载工具和/或所述运载工具包括的部件，所述应用场景标识用于标识第一设备证书的使用场景，所述第一设备证书为所述运载工具进行第一业务时所使用的证书；
    接收第一网络设备发送的第一响应消息，所述第一响应消息包括所述第二设备证书，所述第二设备证书与所述设备标识和所述应用场景标识相关联，且所述第二设备证书用于处理所述第一业务。
  25. 一种通信装置，其特征在于，所述装置包括：收发单元和处理单元；
    所述收发单元，用于接收运载工具发送的第一请求消息，所述第一请求消息用于请求第一网络设备签发设备证书，所述第一请求消息包括设备标识和应用场景标识，所述设备标识用于标识所述运载工具和/或所述运载工具包括的部件，所述应用场景标识用于标识第一设备证书的使用场景，所述第一设备证书为所述运载工具进行第一业务时所使用的证书；
    所述处理单元，用于根据所述设备标识和所述应用场景标识，确定第二设备证书；
    所述收发单元，还用于向所述运载工具发送第一响应消息，所述第一响应消息包括所述第二设备证书，所述第二设备证书用于处理所述第一业务。
  26. 一种通信装置，其特征在于，所述装置包括：收发单元和处理单元；
    所述收发单元，用于：
    接收运载工具发送的第三请求消息，所述第三请求消息用于请求所述第二网络设备验证所述运载工具是否具有进行第一业务的权限，所述第三请求消息包括以下内容至少一项：第二设备证书、设备标识和应用场景标识，所述第二设备证书用于处理所述第一业务，所述设备标识用于标识所述运载工具和/或所述运载工具包括的部件，所述应用场景标识用于标识第一设备证书的使用场景，所述第一设备证书为所述运载工具进行第一业务时所使用的证书；
    向所述第一网络设备发送第二请求消息，所述第二请求消息用于请求所述第一网络设备对所述第二设备证书进行验证，所述第二请求消息包括所述第二设备证书、所述设备标识和所述应用场景标识；
    接收所述第一网络设备发送的第二响应消息，所述第二响应消息包括与所述设备标识和所述应用场景标识相关联的所述第二设备证书的验证结果；
    所述处理单元，用于根据所述第二设备证书的验证结果，向所述运载工具发送第三响应消息，所述第三响应消息用于指示所述运载工具的权限验证结果。
  27. 一种通信装置，其特征在于，包括：处理器和存储器，所述处理器与所述存储器耦合，用于读取并执行所述存储器中的指令，以执行如权利要求1至13中任一项所述的方法。
  28. 一种通信装置，其特征在于，包括：处理器和存储器，所述处理器与所述存储器耦合，用于读取并执行所述存储器中的指令，以执行如权利要求14至21中任一项所述的方法。
  29. 一种通信装置，其特征在于，包括：处理器和存储器，所述处理器与所述存储器耦合，用于读取并执行所述存储器中的指令，以执行如权利要求22或23所述的方法。
  30. 一种运载工具，其特征在于，包括：处理器和存储器，所述处理器与所述存储器耦合，用于读取并执行所述存储器中的指令，以执行如权利要求1至13中任一项所述的方法。
  31. 如权利要求30所述的方法，其特征在于，所述运载工具包括车辆。
  32. 一种服务器，其特征在于，包括：处理器和存储器，所述处理器与所述存储器耦合，用于读取并执行所述存储器中的指令，以执行如权利要求14至21中任一项所述的方法。
  33. 一种服务器，其特征在于，包括：处理器和存储器，所述处理器与所述存储器耦 合，用于读取并执行所述存储器中的指令，以执行如权利要求22或23所述的方法。
  34. 一种计算机可读介质，其特征在于，所述计算机可读介质存储有程序代码，当所述计算机程序代码在计算机上运行时，使得所述计算机执行如权利要求1至23中任一项所述的方法。
  35. 一种计算机程序产品，其特征在于，所述计算机产品包括：计算机程序，当所述计算机程序被运行时，使得计算机执行如权利要求1至23中任一项所述的方法。
PCT/CN2022/134607 2022-11-28 2022-11-28 通信方法、装置以及运载工具 WO2024113077A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/134607 WO2024113077A1 (zh) 2022-11-28 2022-11-28 通信方法、装置以及运载工具

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/134607 WO2024113077A1 (zh) 2022-11-28 2022-11-28 通信方法、装置以及运载工具

Publications (1)

Publication Number Publication Date
WO2024113077A1 true WO2024113077A1 (zh) 2024-06-06

Family

ID=91322655

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/134607 WO2024113077A1 (zh) 2022-11-28 2022-11-28 通信方法、装置以及运载工具

Country Status (1)

Country Link
WO (1) WO2024113077A1 (zh)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103974255A (zh) * 2014-05-05 2014-08-06 宇龙计算机通信科技(深圳)有限公司 一种车辆接入系统和方法
KR20170065172A (ko) * 2015-12-03 2017-06-13 현대오토에버 주식회사 차량 애드 혹 네트워크에서의 차량 인증서 생성 방법 및 장치
US20190278903A1 (en) * 2018-03-06 2019-09-12 GM Global Technology Operations LLC Vehicle control module security credential replacement
CN111066284A (zh) * 2017-10-09 2020-04-24 华为技术有限公司 一种业务证书管理方法、终端及服务器
KR20220090465A (ko) * 2020-12-22 2022-06-29 현대자동차주식회사 PnC 관련 서비스 제공자 정보 제공 방법 및 장치

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103974255A (zh) * 2014-05-05 2014-08-06 宇龙计算机通信科技(深圳)有限公司 一种车辆接入系统和方法
KR20170065172A (ko) * 2015-12-03 2017-06-13 현대오토에버 주식회사 차량 애드 혹 네트워크에서의 차량 인증서 생성 방법 및 장치
CN111066284A (zh) * 2017-10-09 2020-04-24 华为技术有限公司 一种业务证书管理方法、终端及服务器
US20190278903A1 (en) * 2018-03-06 2019-09-12 GM Global Technology Operations LLC Vehicle control module security credential replacement
KR20220090465A (ko) * 2020-12-22 2022-06-29 현대자동차주식회사 PnC 관련 서비스 제공자 정보 제공 방법 및 장치

Similar Documents

Publication Publication Date Title
US11782692B2 (en) Transport component acceptance
US20190377336A1 (en) Method and system for distributed ledger technology communications for vehicles
US20190371176A1 (en) Transferring control of vehicles
US20220398149A1 (en) Minimizing transport fuzzing reactions
US20240073037A1 (en) Internal certificate authority for electronic control unit
CN111355701A (zh) 针对连接性的基于策略和令牌的授权框架
US20230095845A1 (en) Transport modifications for impaired occupants
WO2020154159A1 (en) Vehicle integration platform (vip) security
US11438158B2 (en) Provisioning of external functionality to transports
US11870557B2 (en) Process for generating transport keys for data communication based on actions performed by a transport
CN108632356B (zh) 基于车联网的车辆控制方法及系统、车载终端及服务器
WO2024113077A1 (zh) 通信方法、装置以及运载工具
US20220335123A1 (en) Transport component tamper detection
US20240103843A1 (en) Robust over the air reprogramming
US12079616B2 (en) Real-time modifications for vehicles
US20230048368A1 (en) Transport onboard security check
US20230074898A1 (en) Transport limitation for data reads
US20220274593A1 (en) Transport-related object avoidance
US20220357406A1 (en) Electric vehicle battery maintenance
US20220227246A1 (en) Fractional energy retrieval
US12054157B2 (en) Hardware timer data expiration
US12112851B2 (en) Linking personal environment and transport operation
US11503114B2 (en) Provisioning of event-based keys to transports
WO2024000402A1 (zh) 诊断方法和装置
US20230419825A1 (en) Managing communication in a group of vehicles

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22966682

Country of ref document: EP

Kind code of ref document: A1