Method and apparatus for applying for digital certificate

Abstract

Provided in the embodiments of the present disclosure are a method and apparatus for applying for a digital certificate. The method for applying for a digital certificate comprises: receiving a digital-certificate application request from a vehicle end; acquiring corresponding certificate application information on the basis of the digital-certificate application request, and integrating the certificate application information; applying for a corresponding digital certificate from a TSP background on the basis of the integrated certificate application information; and receiving the digital certificate generated by the TSP background, and synchronizing the digital certificate to an OTA process of the vehicle end. In the embodiments of the present disclosure, a digital certificate is applied for from a TSP background by means of a gateway, such that the security and reliability during the application for the digital certificate are improved, and there is no need to use an additional application system, and thus it is convenient to apply for the digital certificate, and the application efficiency is high. In addition, the digital certificate application process is implemented at the gateway, such that the data processing pressure of a vehicle end can be reduced, the communication pressure of the vehicle end can be reduced, and the subsequent performances of vehicle-end components and parts in terms of testing, diagnosis, etc., can be improved.

Description

Digital certificate application method and device

[0001] Cross-reference

[0002] This disclosure claims priority to the Chinese patent application filed with the China Patent Office on September 22, 2023, with application number 202311234787.3 and invention name “Digital Certificate Application Method and Device,” the entire contents of which are incorporated by reference into this disclosure. Technical Field

[0003] The present disclosure relates to the field of communications, and in particular to a method and device for applying for a digital certificate. Background Art

[0004] Currently, in the field of vehicle communications, digital certificate technology is required to verify the identities of various entities (such as connected vehicles, cloud servers, etc.) that exchange information and conduct business activities online. The digital certificate obtained through application is used to encrypt and decrypt data, thereby ensuring data security. In the Internet of Vehicles environment, secure data communication is mainly achieved by applying for digital certificates. The existing application method for digital certificates for the Internet of Vehicles requires the development of additional systems, servers, or equipment, which is complex to operate and has poor security and reliability during the application process.

[0005] Summary of the Invention

[0006] In view of this, the embodiments of the present disclosure provide a method for applying for a digital certificate to solve the technical problems existing in the prior art, such as the complicated operation of applying for a digital certificate and the poor security and reliability during the application process.

[0007] In order to solve the above technical problems, the embodiments of the present disclosure adopt the following technical solutions:

[0008] In a first aspect, a method for applying for a digital certificate is provided, the method comprising:

[0009] Receive digital certificate application request from the vehicle side;

[0010] Obtaining corresponding certificate application information according to the digital certificate application request, and integrating the certificate application information;

[0011] Apply for the corresponding digital certificate from the TSP backend according to the integrated certificate application information;

[0012] Receive the digital certificate generated by the TSP background and synchronize the digital certificate to the OTA process on the vehicle side.

[0013] According to an achievable method in an embodiment of the present disclosure, applying for a corresponding digital certificate from the TSP backend based on the integrated certificate application information includes:

[0014] Establishing a communication connection with the TSP backend;

[0015] The integrated certificate application information is sent to the TSP backend using the https protocol.

[0016] In some embodiments, after receiving the digital certificate generated by the TSP backend, the method further includes:

[0017] Verifying the digital certificate;

[0018] In response to a successful digital certificate verification, it is determined that the digital certificate application is successful, and the digital certificate is synchronized to the OTA process of the vehicle side; in response to a failure in the digital certificate verification, the reason for the failure of the digital certificate application is obtained, and the digital certificate is deleted.

[0019] According to an achievable method in an embodiment of the present disclosure, verifying the digital certificate includes:

[0020] Verify whether the public key and private key of the digital certificate match;

[0021] Verify whether the certificate name of the digital certificate matches the basic information of the vehicle corresponding to the vehicle end;

[0022] Verify whether the digital certificate is issued by a preset certificate authority;

[0023] Verify whether the digital certificate is within its validity period.

[0024] According to an achievable manner in an embodiment of the present disclosure, after the digital certificate is successfully applied for, the method further includes:

[0025] Setting a first condition variable corresponding to the digital certificate application;

[0026] In response to whether the first condition variable meets a preset requirement; reapplying for the digital certificate.

[0027] According to an achievable manner in an embodiment of the present disclosure, after the digital certificate verification fails, the method further includes:

[0028] Waiting for the digital certificate application according to a preset timer;

[0029] In response to the second condition variable corresponding to the digital certificate application meeting a preset requirement, reapplying for the digital certificate.

[0030] According to an achievable method in an embodiment of the present disclosure, synchronizing the digital certificate to the OTA process on the vehicle side includes:

[0031] Synchronizing the digital certificate to the OTA process via socket communication;

[0032] Set the application status of the digital certificate.

[0033] According to an achievable manner in an embodiment of the present disclosure, the method further includes:

[0034] When the vehicle is offline, the digital certificate is sent to the EOL device on the vehicle side, so that the EOL device obtains the application status of the digital certificate;

[0035] In response to the gateway applying for the digital certificate, the EOL device verifies the digital certificate.

[0036] According to an achievable method in an embodiment of the present disclosure, the method further includes: in response to the gateway failing to apply for the digital certificate, the EOL device obtains the reason for the failure of the digital certificate application, and sends a digital certificate application request to the gateway when the third condition variable corresponding to the digital certificate application meets a preset requirement.

[0037] According to an achievable manner in an embodiment of the present disclosure, after receiving a digital certificate application request from the vehicle side, the method further includes:

[0038] In response to the digital certificate existing, the digital certificate is verified.

[0039] According to an achievable manner in an embodiment of the present disclosure, the method further includes: in response to the digital certificate not existing, applying for a corresponding digital certificate from the TSP backend.

[0040] In a second aspect, an embodiment of the present disclosure further provides a digital certificate application device, comprising:

[0041] A receiving component, used to receive digital certificate application requests from the vehicle side;

[0042] An acquisition component, configured to acquire corresponding certificate application information according to the digital certificate application request and integrate the certificate application information;

[0043] The application component is used to apply for the corresponding digital certificate from the TSP backend of the vehicle communication service provider based on the integrated certificate application information;

[0044] A processing component is used to receive the digital certificate generated by the TSP background and synchronize the digital certificate to the remote update OTA process on the vehicle side.

[0045] In a third aspect, a computer program product is provided, comprising a computer program, which, when executed by a processor, implements the steps of the method described in any one of the first to second aspects.

[0046] In a fourth aspect, a computer program product is provided, comprising a non-volatile computer-readable storage medium, wherein the non-volatile computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of the method described in any one of the first to second aspects are implemented.

[0047] In a fifth aspect, a computer program is provided, which, when executed by a processor, implements the steps of the method described in any one of the first to second aspects above.

[0048] The digital certificate application method, device, storage medium and gateway provided in the embodiments of the present disclosure receive a digital certificate application request from the vehicle side through the gateway; obtain corresponding certificate application information and integrate it according to the digital certificate application request; apply for the corresponding digital certificate from the TSP background according to the integrated certificate application information; receive the digital certificate generated by the TSP background, and synchronize the digital certificate to the OTA process of the vehicle side. The present disclosure applies for a digital certificate from the TSP background through the gateway, which improves the security and reliability of the digital certificate application, and does not require the use of an additional application system, making the digital certificate application convenient and efficient; in addition, performing the digital certificate application process at the gateway can reduce the data processing pressure on the vehicle side, reduce the communication pressure on the vehicle side, and improve the performance of subsequent testing and diagnosis of vehicle-side components. BRIEF DESCRIPTION OF THE DRAWINGS

[0049] In order to more clearly illustrate the embodiments of the present disclosure or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments. Obviously, the drawings described below are only some embodiments of the present disclosure. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0050] FIG1 is an architecture diagram of an OTA certificate system provided by an embodiment of the present disclosure;

[0051] FIG2 is a flow chart of a method for applying for a digital certificate according to an embodiment of the present disclosure;

[0052] FIG3 is a flowchart of a specific implementation of a digital certificate application method provided by an embodiment of the present disclosure;

[0053] FIG4 is another specific implementation flow chart of the digital certificate application method provided in an embodiment of the present disclosure;

[0054] FIG5 is a schematic diagram of a digital certificate application device provided in an embodiment of the present disclosure. DETAILED DESCRIPTION

[0055] It should be understood that various modifications may be made to the embodiments disclosed herein. Therefore, the above description should not be considered as limiting, but merely as an example of an embodiment. Other modifications within the scope and spirit of the present disclosure will occur to those skilled in the art.

[0056] The accompanying drawings, which are incorporated in and constitute a part of the specification, illustrate embodiments of the present disclosure and, together with the general description of the present disclosure given above and the detailed description of the embodiments given below, serve to explain the principles of the present disclosure.

[0057] These and other characteristics of the present disclosure will become apparent from the following description of a preferred form of embodiment given as a non-limiting example with reference to the accompanying drawings.

[0058] It should also be understood that although the present disclosure has been described with reference to certain specific examples, those skilled in the art will be able to realize many other equivalent forms of the present disclosure that have the characteristics recited in the claims and are therefore within the scope of protection defined thereby.

[0059] The above and other aspects, features and advantages of the present disclosure will become more apparent from the following detailed description when taken in conjunction with the accompanying drawings.

[0060] Specific embodiments of the present disclosure will be described hereinafter with reference to the accompanying drawings; however, it should be understood that the claimed embodiments are merely examples of the present disclosure, which may be implemented in a variety of ways. Well-known and / or repetitive functions and structures are not described in detail to avoid obscuring the present disclosure with unnecessary or redundant detail. Therefore, the specific structural and functional details claimed herein are not intended to be limiting, but rather serve merely as a basis and representative basis for teaching those skilled in the art to variously employ the present disclosure with substantially any suitable detailed structure.

[0061] This specification may use the phrases "in one embodiment," "in another embodiment," "in a further embodiment," or "in other embodiments," each of which may refer to one or more of the same or different embodiments according to the present disclosure.

[0062] It should be understood that the embodiment of the present disclosure provides a digital certificate application method, which is applied to a gateway (CGW), which is a gateway of an OTA certificate system. The architecture of the OTA certificate system is shown in Figure 1. The OTA certificate system includes: a gateway, an on-board diagnostics controller area network (OBD CAN), a switch, a vehicle-mounted Tbox (Telematics Box) and a TSP background.

[0063] Gateways are network connectors and protocol converters that enable network interconnection above the network layer. They are used for interconnecting networks with different high-level protocols and for interconnecting entire automotive networks. Gateways can be used between systems with different communication protocols, data formats, or languages, or even completely different architectures. They repackage received information to suit the recipient's needs.

[0064] The gateway includes two processors: A55 (Cortex-A55) and R5 (Cortex-R5security). The A55 is used to process data in the application domain, and the R5 is used to process data in the security domain. A55 specifically includes DoIP (Diagnosis over Internet Protocol), OTA (Over-The-Air), and CertManager. DoIP is an Ethernet-based diagnostic protocol. In this embodiment, DoIP is an in-vehicle Ethernet diagnostic protocol used to send vehicle diagnostic information to the gateway, which is then forwarded to other terminals. The OTA component is used to remotely update the firmware or software of vehicle-side components, enabling remote upgrade management of vehicle-side components through a mobile communication interface (such as GSM or CDMA). In this embodiment, the OTA component can be set up in the gateway to implement system upgrades, application updates, vulnerability fixes, and feature activation for vehicle components. The CertManager is used to manage digital certificates. The OTA component set up in the gateway can communicate with the OTA cloud device, which stores the upgrade packages required for vehicle component upgrades or the upgrade information corresponding to the upgrade packages. Communication between the OTA component and the OTA cloud device requires the use of digital certificates to ensure information security. The gateway also includes the SDPE, a packet acceleration processing engine that enables rapid forwarding of data packets and signals. The gateway connects to the vehicle (e.g., the vehicle controller) via OBD CAN communication, receiving and sending information from the vehicle.

[0065] The Switch is used in the gateway to control Ethernet data transmission and reception; the in-vehicle Tbox is an in-vehicle telematics device used for remote data communication; the TSP backend refers to the backend system of the "Telematics Service Provider" (Telematics Service Provider), a cloud-based server that handles the vehicle's telematics and data management. The TSP backend connects with onboard devices (such as onboard equipment) to collect vehicle-related data and provide corresponding services such as remote monitoring, vehicle diagnostics, and vehicle tracking. The TSP occupies a core position in the telematics industry chain, connecting automobiles, in-vehicle equipment manufacturers, network operators, and content providers. Telematics services integrate modern computer technologies such as location services, GIS services, and communication services to provide car owners and individuals with powerful navigation, entertainment, information, security, social networking services, and remote maintenance services.

[0066] FIG2 is a flow chart of a digital certificate application method provided by the present disclosure, which specifically includes the following steps:

[0067] Step S101: Receive a digital certificate application request from the vehicle.

[0068] Receive a digital certificate application request from the vehicle. A digital certificate is an electronic certificate issued by a certificate authority (CA) and is used for identity authentication, certificate signing, information encryption and decryption, and verification of the authenticity and integrity of digital information. For example, in this embodiment, the digital certificate can be an OTA digital certificate, which is used to verify the upgrade package on the vehicle side to ensure the authenticity, integrity, and security of the upgrade package during the upgrade process of vehicle-side components. The OTA digital certificate can be a digital certificate for an electronic control unit (ECU), or a digital certificate for an on-board device such as an in-vehicle navigation system or an in-vehicle audio and video device.

[0069] During this step, the gateway can receive a digital certificate request from the vehicle in real time. This digital certificate request can be sent to the gateway either actively or passively after the communication connection between the vehicle and the gateway is activated. For example, when the gateway connected to the vehicle is powered on and the communication connection between the vehicle and the gateway is activated, the gateway can be confirmed to have received the digital certificate request from the vehicle. For another example, when the communication connection between the vehicle and the gateway is activated, the vehicle sends a digital certificate request to the gateway. This digital certificate can include vehicle information such as the vehicle model and the name of the certificate being requested.

[0070] The vehicle information that this digital certificate can carry includes basic vehicle information such as the Vehicle Identification Number (VIN) and SN (machine code, also called serial number, authentication code, registration application code, etc.). VIN and SN are unique identifiers used to identify and recognize a vehicle. Each vehicle has a unique VIN, which is similar to the vehicle's ID number. The VIN usually consists of a string of numbers and letters, with a length of about 17 characters. It contains specific information about the vehicle, such as manufacturer, model, year of production, manufacturing location, vehicle characteristics, etc. By interpreting the VIN, you can obtain vehicle information about the vehicle.

[0071] After the gateway is powered on, the gateway's CertManager process starts to determine whether the vehicle's VIN code is written into the gateway. If the gateway writes the vehicle's VIN code, it determines that a digital certificate application request has been received from the vehicle side, and a digital certificate application needs to be made for the vehicle. Then, a digital certificate application can be made for the vehicle.

[0072] S102: According to the digital certificate application request, corresponding certificate application information is obtained and the certificate application information is integrated.

[0073] After the gateway receives the digital certificate application request from the vehicle, it can obtain the certificate application information corresponding to the digital certificate application request from the preset secure storage area in the gateway (such as the memory of the above-mentioned R5 processor) and integrate the certificate application information.

[0074] In this step, the certificate application information is the relevant information used to apply for a digital certificate, for example, in this embodiment, it is an OTA component. The gateway's CertManager process integrates the relevant OTA components to generate a P10 application file (P10 data packet). PKCS#10 (P10 for short) is a format for applying for a digital certificate from a certificate application agency. The P10 application file can be another new digital certificate application request that is different from the digital certificate application request from the vehicle side. The P10 application file may include the identity information of the digital certificate requester (such as the unique identifier of the vehicle) and public key and other data. After the gateway integrates the certificate application information to generate the P10 application file, it establishes a secure connection with the TSP backend.

[0075] It is understandable that the digital certificate application request from the vehicle side may only carry simple information such as the vehicle model and the name of the certificate to be applied for. The P10 application file generated after the gateway integrates the certificate application information contains detailed information of the certificate application. The high data processing performance of the gateway can be used to realize fast and convenient application of digital certificates.

[0076] S103: Apply for the corresponding digital certificate from the TSP backend according to the integrated certificate application information.

[0077] In this step, the gateway establishes a secure connection with the TSP backend and sends the generated P10 application file to the TSP backend. After receiving the P10 application file, the TSP backend generates the corresponding digital certificate based on the P10 application file and sends it to the gateway.

[0078] Before the gateway sends the P10 application file to the TSP background, the gateway can use the first encryption key pre-stored in the secure storage area to encrypt the P10 application file. After receiving the P10 application file, the gateway uses the second encryption key that matches the first encryption key to decrypt the P10 application file and processes the decrypted P10 application file to generate the corresponding digital certificate. The same encryption algorithm and matching shared keys are used between the gateway and the TSP background to ensure the consistency of information encryption and decryption during the communication process. The first encryption key and the second encryption key are keys pre-negotiated by the gateway and the TSP background. They can be the same key or different keys (such as public and private keys).

[0079] S104: Receive the digital certificate generated by the TSP backend, and synchronize the digital certificate to the OTA process on the vehicle side.

[0080] After the gateway receives the digital certificate generated by the TSP background, it synchronizes the information of the digital certificate to the OTA process on the vehicle side so that the vehicle side components can be remotely upgraded.

[0081] It is understood that in this embodiment, the vehicle-side OTA process can be the process corresponding to the OTA component in the above-mentioned gateway. After the vehicle sends a digital certificate application request to the gateway, the vehicle-side OTA process is activated, and the process corresponding to the OTA component in the gateway is also activated. The OTA component in the gateway and the OTA cloud device communicate securely using the digital certificate applied for above. The OTA component in the gateway sends the upgrade package sent by the OTA cloud device to the vehicle-side OTA component, realizing remote upgrade of vehicle-side components. In this embodiment, the OTA component is set up in the gateway to facilitate secure communication between the gateway and the OTA cloud device after applying for a digital certificate, reducing the data processing volume on the vehicle side.

[0082] In some other embodiments, the OTA component may not be set in the gateway. After the gateway receives the digital certificate generated by the TSP background, it directly sends it to the OTA component on the vehicle side and synchronizes the digital certificate to the OTA process on the vehicle side.

[0083] After the gateway receives the digital certificate generated by the TSP background, it can also store it in a preset secure storage area for subsequent use. At the same time, it is also convenient to manage the digital certificate through the CertManager process.

[0084] The TSP backend's primary role in the entire OTA process is to utilize PKI to ensure data confidentiality and uniqueness, screening and filtering devices and data to prevent risky intrusion. Therefore, in this embodiment, a highly secure TSP backend can be used to apply for a digital certificate. Simultaneously, the digital certificate application is performed on a highly secure gateway to ensure security and reliability.

[0085] The digital certificate application method provided by the embodiment of the present disclosure receives a digital certificate application request from the vehicle side through a gateway; obtains and integrates corresponding certificate application information according to the digital certificate application request; applies for a corresponding digital certificate from the TSP background according to the integrated certificate application information; receives the digital certificate generated by the TSP background, and synchronizes the digital certificate to the OTA process of the vehicle side, that is, applies for a digital certificate from the TSP background through the gateway, which improves the security and reliability of the digital certificate application, and does not require the use of an additional application system, and the digital certificate application is convenient and efficient; in addition, performing the digital certificate application process at the gateway can reduce the data processing pressure on the vehicle side, reduce the communication pressure on the vehicle side, and improve the performance of subsequent testing and diagnosis of vehicle-side components.

[0086] In some embodiments, in step S103, applying for a corresponding digital certificate from the TSP backend according to the integrated certificate application information includes:

[0087] Step S1031: establishing a communication connection with the TSP backend;

[0088] Step S1032: Send the integrated certificate application information to the TSP backend using the https protocol.

[0089] Before sending a digital certificate application request, the gateway communicates with the TSP backend over the network, and the gateway and the TSP backend perform Transport Layer Security (TLS) identity authentication in advance.

[0090] Specifically, the gateway encapsulates the digital certificate application request containing the encrypted certificate application information through a network protocol, such as, in this embodiment, Hypertext Transfer Protocol Secure (HTTPS), and then submits the encapsulated digital certificate application file (such as the P10 application file described above) to the TSP backend. HTTPS effectively ensures the secure transmission of information between the gateway and the TSP backend.

[0091] In some embodiments, after receiving the digital certificate generated by the TSP backend in step S104, the method further includes:

[0092] Step S201: verifying the digital certificate;

[0093] Step S202: In response to the successful verification of the digital certificate, determine that the digital certificate is successfully applied for, and synchronize the digital certificate to the OTA process on the vehicle side; in response to the failure of the digital certificate verification, obtain the reason for the failure of the digital certificate application, and delete the digital certificate.

[0094] In this embodiment, the digital certificate generated by the TSP background and received by the gateway may include a valid digital certificate or an invalid digital certificate. Therefore, it is necessary to verify the digital certificate. Exemplarily, the digital certificate is verified. If the received digital certificate is a complete digital certificate and the digital certificate is valid, it is determined that the gateway has successfully applied for the digital certificate, and the digital certificate is synchronized to the OTA process on the vehicle side to achieve a safe and reliable upgrade of the vehicle-side components; if the network signal is not good when the digital certificate is received and a partial digital certificate is obtained, the verification fails and it is determined that the digital certificate application has failed. At this time, the reason for the failure of the digital certificate application is recorded, for example, the failure reason is recorded as a poor network condition, and the partial digital certificate is deleted to avoid the subsequent reapplication of the digital certificate due to the existence of the partial digital certificate, thereby improving the reliability of the digital certificate application.

[0095] In some embodiments, in step S201, verifying the digital certificate includes:

[0096] Step S2011: Verify whether the public key and private key of the digital certificate match.

[0097] The basic architecture of digital certificates is public-key PKI, which uses a pair of keys for encryption and decryption. These keys consist of a private key and a public key. The private key, used for signing and decryption, is user-defined and known only to the user. The public key, used for signature verification and encryption, can be shared by multiple users.

[0098] In the embodiment of the present disclosure, the TSP backend generates a digital certificate, so the digital certificate will carry the signature information of the TSP backend, such as a private key signature. If the private key of the TSP backend is used to sign the content of the digital certificate, the signature information of the TSP backend can be obtained, and it is determined that the digital certificate carries the signature information of the TSP backend. The gateway can use the built-in public key of the TSP backend to verify the private key signature information of the TSP backend carried in the digital certificate. If the public and private keys of the digital certificate match, the verification is successful and the digital certificate is determined to be valid; if the public and private keys of the digital certificate do not match, the verification fails and the digital certificate is determined to be invalid.

[0099] In some other embodiments, in step S201, verifying the digital certificate includes:

[0100] Step S2012: Verify whether the certificate name of the digital certificate matches the basic information of the vehicle.

[0101] The basic vehicle information includes the aforementioned VIN and SN. In this embodiment, the CN (Common Name) of the digital certificate generated by the TSP backend can be compared with the vehicle's VIN or SN to determine whether the two match. If they do, the digital certificate is determined to correspond to the vehicle, the verification is successful, and the digital certificate is valid. If they do not match, the digital certificate is determined to be incompatible with the vehicle, the verification fails, and the digital certificate is invalid.

[0102] In some further embodiments, in step S201, verifying the digital certificate includes:

[0103] Step S2013: Verify whether the digital certificate is issued by a preset certificate authority.

[0104] In the embodiment of the present disclosure, the gateway can use a built-in root certificate to verify whether the digital certificate is a certificate issued by a preset certificate issuing authority (such as a vehicle manufacturer), thereby verifying whether the digital certificate is a certificate issued by a legal agency. If it is a certificate issued by the preset certificate issuing authority, the verification is successful, and it is determined that the digital certificate is a certificate issued by a legal agency, and the digital certificate is valid; if it is not a certificate issued by the preset certificate issuing authority, the verification fails, and it is determined that the digital certificate is a certificate issued by an illegal agency. For example, the digital certificate has been tampered with by an illegal third party, and the digital certificate is invalid.

[0105] The gateway has a pre-installed root certificate, which is pre-installed in the factory. This ensures that the subsequent certificate chain verification process can correctly identify the legitimacy of other certificates. This pre-installed root certificate is typically issued by the device manufacturer or a trusted third-party certificate authority and is stored in a secure storage area on the gateway to ensure its security.

[0106] In some further embodiments, in step S201, verifying the digital certificate includes:

[0107] Step S2014: Verify whether the digital certificate is within the validity period.

[0108] In the disclosed embodiment, the gateway may use a built-in root certificate to verify whether the digital certificate is valid. If the certificate is within the validity period, the verification succeeds and the certificate is determined to be valid. If the certificate is not within the validity period, it is determined that the certificate has expired or has not yet reached the usage time, the verification fails and the certificate is determined to be invalid. In a specific implementation, the relevant information in the digital certificate may also be compared to determine whether the certificate is in a revoked state, etc., to verify whether the certificate is valid. For example, the validity period information carried in the digital certificate generated by the TSP background indicates that it is in a revoked state, and the certificate is determined to be invalid and the verification fails. In other embodiments, the integrity of the digital certificate may also be verified to verify whether the digital certificate is valid.

[0109] Through the above embodiments, the validity and security of digital certificates can be fully guaranteed, preventing digital certificates from being forged or tampered with. The above different methods and steps for verifying the digital certificate can be performed simultaneously to improve the accuracy of digital certificate verification, or they can be performed separately, for example, only verifying the validity of the digital certificate to perform targeted verification of the digital certificate.

[0110] In some embodiments, after the digital certificate is successfully applied for, the method further includes:

[0111] Step S301: setting a first condition variable corresponding to the digital certificate application;

[0112] Step S302: In response to the first condition variable meeting a preset requirement, reapply for the digital certificate.

[0113] In the disclosed embodiment, the first conditional variable is a variable used to determine whether the conditions for re-applying for a digital certificate are met. The first conditional variable may specifically be the usage time of the digital certificate, the number of times (frequency) the digital certificate is used, the current network status of the gateway or vehicle, etc. After the first conditional variable is set, during the subsequent use of the digital certificate, it can be determined in real time whether the first conditional variable meets the preset requirements. If so, it is determined that the use of the digital certificate is blocked. In this case, the gateway can re-send the digital certificate application file to the TSP backend to re-apply for the digital certificate.

[0114] Exemplarily, the first conditional variable is the number of times a digital certificate is used. When the number of times a digital certificate is used exceeds a preset threshold, it is determined that the conditional variable meets the preset requirements, the digital certificate has been used multiple times, and some information may be obtained by a third party. To ensure communication security, it is necessary to re-apply for the digital certificate from the TSP backend; or, when the number of times a digital certificate is used exceeds a preset threshold, it is determined that some information in the digital certificate may need to be updated to ensure that the digital certificate is the latest and valid certificate. At this time, the gateway can re-apply for the digital certificate from the TSP backend.

[0115] In another embodiment, the first condition variable is the current network status of the gateway. If the current network status is good and the communication status between the gateway and the TSP is good, it is determined that the first condition variable meets the preset requirements, and the digital certificate can be re-applied to ensure the real-time use of the digital certificate.

[0116] In some embodiments, after the digital certificate verification fails, the method further includes:

[0117] S401: waking up the application for the digital certificate according to a preset timer;

[0118] S402: In response to the second condition variable corresponding to the digital certificate application meeting a preset requirement, reapply for the digital certificate.

[0119] In the embodiment of the present disclosure, after the digital certificate verification fails, it is determined that the digital certificate application has failed. After determining to delete the incomplete digital certificate, a timer can be started to count. When the timing meets the preset time condition (for example, the timing is full 60s), it is determined that the operation of the gateway has reached the preset timing time. At this time, it may be necessary to reapply for the digital certificate. At this time, the digital certificate application process in the gateway can be awakened. After the digital certificate application process is awakened, it is determined whether the second condition variable corresponding to the digital certificate application meets the preset requirements. For example, it is determined whether the network condition of the gateway is good. If it is good, it can be determined that the communication between the gateway and the TSP background is smooth, and the second condition variable meets the preset requirements. The digital certificate can be re-applied to the TSP background.

[0120] The second conditional variable can be the first conditional variable set after the previous digital certificate application was successful, that is, the second conditional variable is the same as the first conditional variable. The second conditional variable can also be a conditional variable specifically set for the situation where the digital certificate application fails. For example, if the reason for the failure of the digital certificate application is that the network condition of the gateway is poor and the communication is not smooth, then the second conditional variable can be set to the network condition of the gateway; if the reason for the failure of the digital certificate application is that the digital certificate has expired, then the second conditional variable can be set to whether the digital certificate in the TSP background is updated. If the digital certificate in the TSP background is updated, it is determined that the digital certificate can be applied for and is within the validity period. At this time, you can re-apply for the digital certificate from the TSP background.

[0121] In an embodiment of the present disclosure, synchronizing the digital certificate to the OTA process on the vehicle side includes:

[0122] Step S1041: Synchronize the digital certificate to the OTA process via socket communication;

[0123] Step S1042: Setting the application status of the digital certificate.

[0124] Socket communication refers to network communication implemented by applications using the socket interface, used to transmit data between different computers. Socket is a standard API (application programming interface) for transmitting data between different computers, supporting various network protocols such as TCP and UDP. Socket communication is cross-platform and not restricted to a specific operating system. It is also flexible and can use different network protocols (such as TCP and UDP) to meet different needs.

[0125] In the disclosed embodiment, the gateway uses socket communication to send the digital certificate to the OTA process on the vehicle side, making network communication more convenient and flexible. At the same time, the gateway can set the application status of the digital certificate, so that after the vehicle is offline, the EOL (End of Line) device can read the application status of the digital certificate and perform offline diagnosis of the vehicle. The application status of the digital certificate includes a successful application status or a failed application status. The EOL device (such as a diagnostic instrument) can diagnose SDPE through the OBD CAN, and then establish communication with the A55 processor through the SDPE to obtain the current status of the certificate.

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

[0127] Step S501: When the vehicle is offline, the digital certificate is sent to the EOL device on the vehicle side, so that the EOL device obtains the application status of the digital certificate;

[0128] Step S502: In response to the gateway having applied for the digital certificate online, the EOL device verifies the digital certificate; in response to the gateway not applying for the digital certificate, the EOL device obtains the reason for the failure of the digital certificate application, and sends a digital certificate application request to the gateway when the third condition variable corresponding to the digital certificate application meets the preset requirements.

[0129] In the disclosed embodiment, the whole vehicle coming off the assembly line refers to the last process on the vehicle production line, also known as "the whole vehicle coming off the assembly line". In the vehicle production process, after multiple processes and assembly lines, all parts of the vehicle are completed, and the final finished vehicle is about to leave the production line and be put into the stage of sale or delivery. When the whole vehicle comes off the assembly line, the digital certificate is sent to the EOL device on the vehicle side to facilitate the EOL device's diagnosis of the vehicle. If the EOL device reads the application status of the digital certificate as a successful application, the digital certificate is verified. Specifically, the verification can be performed by determining whether the digital certificate is issued by a legitimate certificate issuing authority, whether it is within the validity period, and whether the public and private keys of the digital certificate match.

[0130] If the EOL device reads the digital certificate application status as failed, the EOL device is unable to read the digital certificate and obtains the reason for the digital certificate application failure. For example, if the reason for the digital certificate application failure is poor network quality, and the third condition variable corresponding to the digital certificate application is the current network status of the gateway, and the current network status is good and meets preset requirements, a digital certificate application request is sent to the gateway to re-apply for the digital certificate.

[0131] The third condition variable can be the same as the first and / or second condition variables, or can be an independent condition variable set for the EOL device. For example, in this embodiment, to ensure the reliability of the digital certificate application, the second condition variable can be the current network status between the gateway and the TSP backend, and the third condition variable can be the current network status between the gateway and the TSP backend and the current network status between the gateway and the EOL device.

[0132] In some embodiments, after step S101, receiving a digital certificate application request from the vehicle, the method further includes:

[0133] Step S601: In response to the existence of the digital certificate, verify the digital certificate;

[0134] Step S602: In response to the digital certificate not existing, apply for a corresponding digital certificate from the TSP backend.

[0135] In this embodiment, after receiving a digital certificate request from the vehicle, that is, after the gateway's CertManager process determines the vehicle's VIN code written into the gateway, it determines whether the gateway has a digital certificate corresponding to the vehicle. If so, the digital certificate is verified to determine its legality and validity. If so, it is directly synchronized to the vehicle's OTA process, eliminating the need for the gateway to repeatedly apply for a digital certificate, thereby improving the efficiency of the entire digital certificate application process. If not, step S102 is executed to apply for the corresponding digital certificate from the TSP backend.

[0136] When verifying the digital certificate, it can be verified by determining whether the public and private keys of the digital certificate match, whether the certificate name of the digital certificate matches the basic information of the vehicle, whether the digital certificate is issued by a legal organization, and whether the digital certificate is within the validity period.

[0137] The following describes the digital certificate application method in detail using a specific application scenario as an example.

[0138] Scenario 1: FIG3 is a flow chart of a digital certificate application method provided in an embodiment of the present disclosure. As shown in FIG3 , the specific steps of the digital certificate application method include:

[0139] Step S701: Start;

[0140] Step S702: The gateway is powered on, the CertManager process is started, and it is determined whether a VIN exists; if no VIN exists, the process proceeds to step S702; if a VIN exists, the process proceeds to step S703;

[0141] Step S703: If the digital certificate exists, proceed to step S705; if the digital certificate does not exist, proceed to step S704;

[0142] Step S704: Apply for a digital certificate;

[0143] Step S705: Determine whether the public and private keys match; if the public and private keys do not match, execute step S715; if the public and private keys match, execute step S706;

[0144] Step S706: Determine whether the VIN matches; if the VIN does not match, execute step S715; if the VIN matches, execute step S707;

[0145] Step S707: Determine whether the SN matches; if the SN does not match, execute step S715; if the SN matches, execute step S708;

[0146] Step S708: Determine whether the digital certificate is within the validity period; if the digital certificate is not within the validity period, execute step S715; if the digital certificate is within the validity period, execute step S709;

[0147] Step S709: Determine whether the digital certificate is issued by a legal institution (i.e., determine whether the digital certificate is issued by a preset certificate authority); if not, execute step S715; if issued by a legal institution, execute step S710;

[0148] Step S710: Save the digital certificate;

[0149] Step S711: Socket communication synchronizes the OTA process on the vehicle side;

[0150] Step S712: Setting the digital certificate application status to success;

[0151] Step S713: setting condition variables;

[0152] Step S714: Determine whether the condition variable is satisfied; if the condition variable is satisfied, execute step 702; if the condition variable is not satisfied, execute step S719;

[0153] Step S715: Set the digital certificate application status to failure and obtain the failure reason;

[0154] Step S716: Delete the digital certificate;

[0155] Step S717: Start the timer and count for 60 seconds;

[0156] Step S718: waking up the certificate application process, i.e. reapplying for a digital certificate;

[0157] Step S719: End.

[0158] The steps in Scenario 1 above describe in detail the process by which the gateway applies for a digital certificate from the TSP backend. This process includes the specific digital certificate application process, the verification process after the digital certificate application, the storage of the digital certificate, and the processing after successful and failed digital certificate applications. This effectively ensures the reliability of digital certificate applications and the validity and security of the applied digital certificates. In this embodiment, the first condition variable set after a successful digital certificate application and the second condition variable used after a failed digital certificate application are the same condition variable.

[0159] Scenario 2: FIG4 is another specific implementation flow chart of the digital certificate application method provided in an embodiment of the present disclosure. As shown in FIG4 , the specific steps of the digital certificate application method include:

[0160] Step S801: Start;

[0161] Step S802: When the vehicle is offline, the EOL device is used to read the digital certificate status in the gateway to determine whether the digital certificate exists; if the digital certificate exists, proceed to step S803; if the digital certificate does not exist, proceed to step S806;

[0162] Step S803: Determine whether the digital certificate is issued by a legal institution (i.e., determine whether the digital certificate is issued by a preset certificate authority); if not, execute step S806; if issued by a legal institution, execute step S804;

[0163] Step S804: Determine whether the digital certificate is within the validity period; if the digital certificate is not within the validity period, execute step S806; if the digital certificate is within the validity period, execute step S805;

[0164] Step S805: Determine whether the public and private keys match; if the public and private keys do not match, execute step S806; if the public and private keys match, execute step S808;

[0165] Step S806: Obtain the reason for the certificate application failure;

[0166] Step S807: waking up the certificate application process, i.e. reapplying for a digital certificate;

[0167] Step S808: End.

[0168] This embodiment communicates with the vehicle's diagnostic process through a socket to complete the response to the OBD diagnosis. It can not only apply for a digital certificate, but also support EOL device diagnosis, thereby providing the digital certificate application status to the EOL device. In addition, the EOL device can also trigger the application of a digital certificate and delete the certificate, thereby improving the rationality of the digital certificate application.

[0169] It should be understood that the above examples are only for illustration and should not constitute specific limitations.

[0170] FIG5 is a schematic diagram of a digital certificate application apparatus provided in a second embodiment of the present disclosure. As shown in FIG5 , the digital certificate application apparatus provided in the second embodiment of the present disclosure corresponds to the digital certificate application method of the first embodiment described above, and includes a receiving component 10, an acquiring component 20, an application component 30, and a processing component 40 coupled to each other, wherein:

[0171] Receiving component 10, for receiving a digital certificate application request from the vehicle end;

[0172] An acquisition component 20 is configured to acquire corresponding certificate application information according to the digital certificate application request and integrate the certificate application information;

[0173] The application component 30 is used to apply for the corresponding digital certificate from the vehicle communication service provider TSP backend according to the integrated certificate application information;

[0174] The processing component 40 is used to receive the digital certificate generated by the TSP background and synchronize the digital certificate to the remote update OTA process on the vehicle side.

[0175] Furthermore, the application component 30 is also used to:

[0176] Establishing a communication connection with the TSP backend;

[0177] The integrated certificate application information is sent to the TSP backend using the https protocol.

[0178] Furthermore, the digital certificate application device further includes:

[0179] A verification component, configured to verify the digital certificate;

[0180] The processing component 40 is also used to: if the digital certificate verification is successful, determine that the digital certificate application is successful, and synchronize the digital certificate to the OTA process on the vehicle side; if the digital certificate verification fails, obtain the reason for the failure of the digital certificate application and delete the digital certificate.

[0181] Furthermore, the verification component block is specifically used to:

[0182] Verify that the public and private keys of the digital certificate match; and / or

[0183] Verify that the certificate name of the digital certificate matches the basic information of the vehicle; and / or

[0184] Verify whether the digital certificate is issued by a preset certificate authority; and / or

[0185] Verify whether the digital certificate is within its validity period.

[0186] Furthermore, the digital certificate application device further includes:

[0187] A setting component, configured to set a first condition variable corresponding to the digital certificate application after the digital certificate application is successfully applied for;

[0188] The processing component 40 is further configured to: determine whether the first condition variable meets a preset requirement;

[0189] If satisfied, re-apply for the digital certificate.

[0190] Furthermore, the processing component 40 is further configured to:

[0191] After the digital certificate verification fails, waking up the application for the digital certificate according to a preset timer;

[0192] Determining whether a second condition variable corresponding to the digital certificate application meets a preset requirement;

[0193] If satisfied, re-apply for the digital certificate.

[0194] Furthermore, the processing component 40 is further configured to:

[0195] Synchronize the digital certificate to the OTA process via socket communication;

[0196] Set the application status of the digital certificate.

[0197] Furthermore, the digital application device further includes a diagnostic component for:

[0198] When the vehicle is offline, the digital certificate is sent to the EOL device on the vehicle side, so that the EOL device obtains the application status of the digital certificate and determines whether the gateway has applied for the digital certificate online;

[0199] If the application is successful, the EOL device verifies the digital certificate; if the application is not successful, the EOL device obtains the reason for the failure of the digital certificate application, and sends a digital certificate application request to the gateway when the third condition variable corresponding to the digital certificate application meets the preset requirements.

[0200] Furthermore, the device further includes a second judgment component, configured to:

[0201] Determining whether the digital certificate exists;

[0202] If the digital certificate exists, verify the digital certificate; if the digital certificate does not exist, apply for the corresponding digital certificate from the TSP background.

[0203] It should be noted that the digital certificate application device provided in the embodiment of the present disclosure corresponds to the digital certificate application method in the above-mentioned embodiment. Based on the above-mentioned digital certificate application method, those skilled in the art can understand the specific implementation methods of the digital certificate application device in the embodiment of the present disclosure and its various variations. Any optional items in the embodiment of the digital certificate application method are also applicable to the digital certificate application device and will not be repeated here.

[0204] The embodiments of the present disclosure further provide a computer program, wherein when the computer program is executed in a computer, the computer is caused to execute the steps of the above-mentioned task processing method or automatic question-answering method.

[0205] Optionally, the above-mentioned computer program implements the program code of the following steps when executed by the processor: receiving a digital certificate application request from the vehicle side; obtaining corresponding certificate application information based on the digital certificate application request, and integrating the certificate application information; applying for the corresponding digital certificate from the vehicle communication service provider TSP background based on the integrated certificate application information; receiving the digital certificate generated by the TSP background, and synchronizing the digital certificate to the remote update OTA process of the vehicle side.

[0206] Furthermore, when the computer program is executed by a processor, other methods provided in the first embodiment of the present disclosure are implemented.

[0207] The present disclosure also provides a storage medium, which is a computer-readable medium and stores a computer program. When the computer program is executed by a processor, the method provided in the first embodiment of the present disclosure is implemented, including the following steps S101 to S104:

[0208] Step S101: receiving a digital certificate application request from the vehicle;

[0209] Step S102: according to the digital certificate application request, obtain corresponding certificate application information and integrate the certificate application information;

[0210] Step S103: Apply for the corresponding digital certificate from the TSP backend according to the integrated certificate application information;

[0211] Step S104: Receive the digital certificate generated by the TSP background, and synchronize the digital certificate to the OTA process on the vehicle side.

[0212] The present disclosure also provides a gateway, which includes at least a memory and a processor. The memory stores a computer program. The processor implements the method provided in the first embodiment of the present disclosure when executing the computer program in the memory. The computer program, when executed by the processor, implements the method provided in the embodiment of the present disclosure, including the following steps S101 to S104:

[0213] Step S101: receiving a digital certificate application request from the vehicle;

[0214] Step S102: according to the digital certificate application request, obtain corresponding certificate application information and integrate the certificate application information;

[0215] Step S103: Apply for the corresponding digital certificate from the TSP backend according to the integrated certificate application information;

[0216] Step S104: Receive the digital certificate generated by the TSP backend, and synchronize the digital certificate to the OTA process on the vehicle side. Furthermore, the processor also executes the computer program in the above embodiment.

[0217] The above-mentioned storage medium may be included in the above-mentioned gateway; or it may exist independently without being assembled into the gateway.

[0218] The above-mentioned storage medium carries one or more programs. When the above-mentioned one or more programs are executed by the gateway, the gateway enables the gateway to: receive a digital certificate application request from the vehicle side; obtain the corresponding certificate application information and integrate it according to the digital certificate application request; apply for the corresponding digital certificate from the TSP background according to the integrated certificate application information; receive the digital certificate generated by the TSP background, and synchronize the digital certificate to the OTA process of the vehicle side.

[0219] The present disclosure also provides a computer program product, which includes a non-volatile computer-readable storage medium storing a computer program.

[0220] The above is a schematic diagram of a computer program according to this embodiment. It should be noted that the technical solution of this computer program is based on the same concept as the technical solutions of the task processing method and the automatic question-answering method described above. For details not described in detail in the technical solution of the computer program, please refer to the description of the technical solutions of the task processing method or the automatic question-answering method described above.

[0221] The foregoing description describes specific embodiments of the present disclosure. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims can be performed in an order different from that described in the embodiments and still achieve the desired results. Furthermore, the processes depicted in the accompanying drawings do not necessarily require the specific order shown or the sequential order to achieve the desired results. In certain embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0222] The computer instructions include computer program code, which may be in source code form, object code form, executable file, or some intermediate form. The computer-readable medium may include any entity or device capable of carrying the computer program code, a recording medium, a USB flash drive, a mobile hard drive, a magnetic disk, an optical disk, a computer memory, a read-only memory (ROM), a random access memory (RAM), an electrical carrier signal, a telecommunications signal, and a software distribution medium.

[0223] It should be noted that for the aforementioned method embodiments, for the sake of simplicity of description, they are all expressed as a series of action combinations, but those skilled in the art should be aware that the embodiments of this disclosure are not limited by the order of the actions described, because according to the embodiments of this disclosure, certain steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also be aware that the embodiments described in this disclosure in the specification are all preferred embodiments, and the actions and components involved are not necessarily required by the embodiments of this disclosure.

[0224] In the above embodiments, the description of each embodiment has its own focus. For parts that are not described in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0225] The preferred embodiments of the present disclosure disclosed above are only used to help illustrate the disclosure of this specification. The optional embodiments do not describe all the details in detail, nor do they limit the invention to the specific implementation methods described. Obviously, many modifications and changes can be made based on the content of the embodiments of the present disclosure. The present disclosure selects and specifically describes these embodiments in order to better explain the principles and practical applications of the embodiments of the present disclosure, so that those skilled in the art can well understand and use the present disclosure. The present disclosure is limited only by the claims and their full scope and equivalents. Specifically, the computer program code for performing the operations of the present disclosure can be written in one or more programming languages ​​or a combination thereof, including but not limited to object-oriented programming languages ​​such as Java, Smalltalk, C++, and conventional procedural programming languages ​​such as C or similar programming languages. The program code can be executed entirely on the passenger computer, partially on the passenger computer, as a separate software package, partially on the passenger computer and partially on a remote computer, or entirely on a remote computer or server. Where a remote computer is involved, the remote computer may be connected to the passenger computer via any type of network, including a local area network (LAN) or wide area network (WAN), or may be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0226] It should be noted that the storage medium described above in the present disclosure may be a computer-readable signal medium or a computer-readable storage medium, or any combination thereof. A computer-readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or component, or any combination thereof. More specific examples of computer-readable storage media may include, but are not limited to, an electrical connection having one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof. In the present disclosure, a computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, device, or component. In the present disclosure, a computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, which carries computer-readable program code. This propagated data signal may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. A computer-readable signal medium may also be any storage medium other than a computer-readable storage medium that can transmit, propagate, or convey a program for use by or in conjunction with an instruction execution system, apparatus, or device. The program code contained on the storage medium may be conveyed using any suitable medium, including but not limited to wires, optical cables, RF (radio frequency), or any suitable combination thereof.

[0227] The above description is merely a preferred embodiment of the present disclosure and an illustration of the technical principles employed. Those skilled in the art should understand that the scope of disclosure involved in the present disclosure is not limited to the technical solutions formed by the specific combination of the above-mentioned technical features, but also includes other technical solutions formed by any combination of the above-mentioned technical features or their equivalents without departing from the above-mentioned disclosed concepts. For example, a technical solution formed by replacing the above-mentioned features with (but not limited to) technical features with similar functions disclosed in this disclosure.

[0228] In addition, although each operation is described in a specific order, this should not be understood as requiring these operations to be performed in the specific order shown or in a sequential order. Under certain circumstances, multitasking and parallel processing may be advantageous. Similarly, although some specific implementation details have been included in the above discussion, these should not be interpreted as limiting the scope of the present disclosure. Some features described in the context of a separate embodiment can also be implemented in a single embodiment in combination. On the contrary, the various features described in the context of a single embodiment can also be implemented in multiple embodiments individually or in any suitable sub-combination mode. Industrial Applicability

[0229] The solution provided by the embodiment of the present disclosure can be applied to the digital certificate application process, receiving a digital certificate application request from the vehicle side through the gateway; obtaining corresponding certificate application information according to the digital certificate application request, and integrating the certificate application information; applying for the corresponding digital certificate from the TSP background according to the integrated certificate application information; receiving the digital certificate generated by the TSP background, and synchronizing the digital certificate to the OTA process of the vehicle side, thereby solving the technical problems existing in the prior art such as the complicated application operation of the digital certificate and the poor security and reliability in the application process.

Claims

1. A digital certificate application method, applied to a gateway, comprising: Receive digital certificate application request from the vehicle end; According to the digital certificate application request, obtain corresponding certificate application information, and integrate the certificate application information; Apply for the corresponding digital certificate from the TSP backend of the vehicle communication service provider based on the integrated certificate application information; Receive the digital certificate generated by the TSP background, and synchronize the digital certificate to the remote update OTA process on the vehicle side.

2. The digital certificate application method according to claim 1, wherein: Apply for the corresponding digital certificate from the TSP backend based on the integrated certificate application information, including: Establishing a communication connection with the TSP backend; The integrated certificate application information is sent to the TSP backend using the hypertext transfer protocol (https).

3. The digital certificate application method according to claim 1, wherein: After receiving the digital certificate generated by the TSP background, the method further includes: Verifying the digital certificate; If the digital certificate verification succeeds, it is determined that the digital certificate application is successful, and the digital certificate is synchronized to the OTA process of the vehicle end; If the digital certificate verification fails, the reason for the failure of the digital certificate application is obtained, and the digital certificate is deleted.

4. The digital certificate application method according to claim 3, wherein: Verifying the digital certificate includes at least one of the following: Verify whether the public key and private key of the digital certificate match; Verify whether the certificate name of the digital certificate matches the basic information of the vehicle corresponding to the vehicle end; Verifying whether the digital certificate is issued by a preset certificate authority; Verify whether the digital certificate is within the validity period.

5. The digital certificate application method according to claim 3, wherein: After the digital certificate is successfully applied for, the method further includes: Setting a first condition variable corresponding to the digital certificate application; In response to the first condition variable satisfying a preset requirement, reapplying for the digital certificate.

6. The digital certificate application method according to claim 3, wherein: After the digital certificate verification fails, the method further includes: Waking up the application for the digital certificate according to a preset timing; In response to the second condition variable corresponding to the digital certificate application meeting a preset requirement, reapplying for the digital certificate.

7. The digital certificate application method according to claim 1, wherein: The OTA process of synchronizing the digital certificate to the vehicle side includes: Synchronizing the digital certificate to the OTA process via socket communication; Set the application status of the digital certificate.

8. The digital certificate application method according to claim 7, further comprising: When the vehicle is offline, the digital certificate is sent to the end of life (EOL) device of the vehicle, so that the EOL device obtains the application status of the digital certificate; In response to the gateway having applied for the digital certificate online, the EOL device verifies the digital certificate.

9. The digital certificate application method according to claim 8, further comprising: In response to the gateway failing to apply for the digital certificate, the EOL device obtains the reason for the failure of the digital certificate application, and sends a digital certificate application request to the gateway when a third condition variable corresponding to the digital certificate application meets a preset requirement.

10. The digital certificate application method according to claim 1, wherein: After receiving the digital certificate application request from the vehicle end, the method further includes: In response to the digital certificate existing, the digital certificate is verified.

11. The digital certificate application method according to claim 10, further comprising: In response to the digital certificate not existing, applying for a corresponding digital certificate from the TSP backend.

12. A digital certificate application device, characterized in that: include: A receiving component, used to receive a digital certificate application request from the vehicle end; An acquisition component, used to acquire corresponding certificate application information according to the digital certificate application request, and integrate the certificate application information; The application component is used to apply for the corresponding digital certificate from the TSP backend of the vehicle communication service provider according to the integrated certificate application information; A processing component is used to receive the digital certificate generated by the TSP background and synchronize the digital certificate to the remote update OTA process of the vehicle side.

13. A computer program product, wherein: The invention comprises a computer program which, when executed by a processor, implements the method according to any one of claims 1 to 11.

14. A computer program product, wherein: The invention comprises a non-volatile computer-readable storage medium storing a computer program, wherein the computer program implements the method according to any one of claims 1 to 11 when executed by a processor.

15. A computer program, wherein: When the computer program is executed by a processor, the method according to any one of claims 1 to 11 is implemented.

Images