Certificate verification device, certificate verification method, and certificate verification program
The certificate verification device addresses the issue of expired certificate verification in mobile environments by using stored logs and alternative date and time sources to determine certificate expiration, ensuring reliable verification without direct communication.
Patent Information
- Application Number
- JP2023079407
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2023-05-12
- Publication Date
- 2024-11-22
AI Technical Summary
Existing certificate verification systems in vehicles fail to determine the expiration of public key certificates when date and time information cannot be received due to communication breakdowns or abnormal conditions, which is common in mobile environments.
A certificate verification device that utilizes a receiving unit to acquire date and time information from a date and time distribution device, stores this information, generates and stores logs, and uses these logs to verify certificate expiration even when direct date and time information is unavailable, employing alternative date and time information when necessary.
Ensures the verification of certificate expiration even in conditions where direct date and time information is unavailable, reducing network traffic and improving verification accuracy by using stored logs and alternative sources.
Smart Images

Figure 2024163630000001_ABST
Abstract
Description
[Technical field]
[0001] The present invention relates to a certificate verification device that is primarily installed in an in-vehicle electronic control system, receives certificates such as X.509 from an authentication request device, and verifies the expiration date of the certificate, as well as a method realized by the certificate verification device and a program that can be executed by the certificate verification device. [Background technology]
[0002] Automobiles are equipped with various electronic control devices that are connected via an in-vehicle network. With the recent development of autonomous driving technology, the functions required of automobiles are becoming more complex, and the number of electronic control devices installed in automobiles is increasing.
[0003] An electronic control unit transmits and receives programs and data between other electronic control units in an electronic control system and devices outside the electronic control system by verifying signatures and decrypting encryption using a public key. In this case, a public key certificate can be used to prove that the public key really belongs to its owner.
[0004] Since public key certificates have an expiration date, it is necessary to verify whether the certificate has expired. For example, in Patent Document 1, in order to verify whether the certificate has expired, it is verified whether the certificate is within the validity period based on date and time information acquired by a GPS receiver. [Prior art documents] [Patent documents]
[0005] [Patent Document 1] JP 2015-119243 A Summary of the Invention [Problem to be solved by the invention]
[0006] Here, the present inventors have found the following problem as a result of detailed investigation. If the date and time information cannot be received due to some abnormal condition such as a communication interruption, it becomes impossible to verify whether the public key certificate has expired. For example, in the case of a device mounted on a mobile object, the communication environment changes as the device moves, so it is not always possible to receive date and time information.
[0007] Therefore, an object of the present invention is to provide a certificate verification device or the like that can verify that a public key certificate has expired even when date and time information cannot be received due to some abnormal state. [Means for solving the problem]
[0008] A certificate verification device according to an aspect of the present disclosure is a certificate verification device that verifies the expiration date of a certificate, comprising: a receiving unit (101) that receives the certificate from an authentication request device (30) and first date and time information, which is date and time information, from a date and time distribution device; a date and time information storage unit (102) that stores the first date and time information; a log storage unit (104) for storing a log generated or received by the certificate verification device; a certificate verification unit (105) that verifies whether the validity period of the certificate has expired by using the first date and time information, If the receiving unit cannot receive the first date and time information, the certificate validation unit verifies that the certificate has expired using second date and time information linked to the log stored in the log storage unit.
[0009] In addition, the claims and the numbers in parentheses attached to the constituent elements of the invention described in this section indicate the correspondence between the present invention and the embodiments described below, and are not intended to limit the present invention. Effect of the Invention
[0010] According to the above configuration, the certificate verification device, etc. of the present invention verifies that a certificate has expired using date and time information linked to the log stored in the log storage unit, so that it is possible to verify that a certificate has expired even if the date and time information cannot be received. [Brief description of the drawings]
[0011] [Figure 1] FIG. 1 is a diagram illustrating the layout of a certificate verification device and its peripheral devices. [Diagram 2] FIG. 1 is a diagram illustrating an example of the configuration of an electronic control system and its relationship with a certificate verification device, etc. [Diagram 3] FIG. 1 is a block diagram illustrating a configuration of a certificate validation device according to a first embodiment. [Figure 4] FIG. 1 is a diagram for explaining the determination operation of the certificate validation unit of the certificate validation device of the first embodiment. [Diagram 5] FIG. 1 is a flow diagram for explaining the operation of the certificate validation device according to the first embodiment. [Figure 6] FIG. 1 is a flow diagram for explaining the operation of a certificate verification unit of the certificate verification device according to the first embodiment. [Figure 7] FIG. 11 is a block diagram illustrating the configuration of a certificate validation device according to a second embodiment. [Figure 8] FIG. 11 is a flow diagram for explaining the operation of the certificate verification unit of the certificate verification device according to the second embodiment. [Figure 9] FIG. 11 is a block diagram illustrating the configuration of a certificate validation device according to a third embodiment. [Figure 10] FIG. 11 is a flow diagram for explaining the operation of the certificate verification unit of the certificate verification device according to the third embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0012] Hereinafter, an embodiment of the present invention will be described with reference to the drawings.
[0013] The present invention means the invention described in the claims or in the Summary of the Invention section, and is not limited to the following embodiments. Furthermore, at least the words in quotation marks mean the words described in the claims or in the Summary of the Invention section, and are not limited to the following embodiments.
[0014] The configurations and methods described in the dependent claims are optional configurations and methods in the invention described in the independent claims. The configurations and methods of the embodiments corresponding to the configurations and methods described in the dependent claims, and the configurations and methods described only in the embodiments without being described in the claims, are optional configurations and methods in the present invention. The configurations and methods described in the embodiments when the description of the claims is broader than the description of the embodiments are also optional configurations and methods in the present invention in the sense that they are examples of the configurations and methods of the present invention. In either case, by being described in the independent claims, they become essential configurations and methods of the present invention.
[0015] The effects described in the embodiments are effects obtained when the configurations of the embodiments are provided as examples of the present invention, and are not necessarily effects that the present invention possesses.
[0016] When there are multiple embodiments (including modified examples; the same applies hereinafter in this paragraph), the configurations disclosed in each embodiment are not limited to each embodiment, but can be combined across the embodiments. For example, a configuration disclosed in one embodiment may be combined with another embodiment. Also, the configurations disclosed in each of the multiple embodiments may be collected and combined.
[0017] The problem described in the section on problems that the invention is intended to solve is not a publicly known problem, but was discovered independently by the inventor, and this, together with the configuration and method of the present invention, is a fact that affirms the inventive step of the invention.
[0018] 1. Configuration underlying each embodiment (1) Placement of certificate validation devices and their peripheral devices FIG. 1 is a diagram for explaining the arrangement of the "certificate verification device" in each embodiment. For example, the certificate verification device 11, the certificate verification device 12, or the certificate verification device 13 (hereinafter, abbreviated as the certificate verification device 11, etc.) is "mounted" on a vehicle, which is a "mobile body", as a device constituting an electronic control system S as shown in FIG. 1(a), or as a device separate from the electronic control system S. Alternatively, the certificate verification device 11, etc. may not necessarily be "mounted" on a "mobile body" as shown in FIG. 1(b). An example of the form of the certificate verification device 11, etc. in FIG. 1(a) is an electronic control unit (ECU: Electric Control Unit), but is not limited thereto. Also, an example of the form of the certificate verification device 11, etc. in FIG. 1(b) is a personal computer (PC) or a smartphone, but is not limited thereto. Where: "Mobile object" refers to an object that can move and can move at any speed. It also includes cases where the mobile object is stationary. For example, it includes, but is not limited to, automobiles, motorcycles, bicycles, pedestrians, ships, aircraft, and objects mounted on these. "Mounted" includes not only the case where the device is directly fixed to the moving body, but also the case where the device is not fixed to the moving body but moves with the moving body, such as the case where the device is carried by a person riding on the moving body, or the case where the device is mounted on cargo placed on the moving body.
[0019] In the case of Fig. 1(a), the certificate verification device 11 etc. receives a public key certificate (hereinafter, abbreviated as a certificate) from the external device 30 mainly via a communication network using wireless communication. If the vehicle is parked or in a repair shop, the file may be received via a communication network using wired communication. In the case of Fig. 1(b), the certificate verification device 11 etc. receives a certificate from the external device 30 via wireless communication or wired communication.
[0020] Examples of wireless communication include wireless communication methods such as IEEE802.11 (Wi-Fi (registered trademark)), IEEE802.16 (WiMAX (registered trademark)), W-CDMA (Wideband Code Division Multiple Access), HSPA (High Speed Packet Access), LTE (Long Term Evolution), LTE-A (Long Term Evolution Advanced), 4G, and 5G. Alternatively, DSRC (Dedicated Short Range Communication) can be used. Examples of wired communication include IEEE802.3 (Ethernet), CAN (Control Area Network), CAN FD (CAN with Flexible Data rate), and fixed telephone lines.
[0021] Furthermore, the certificate verification device 11 receives date and time information indicating the time at which the positioning signal was transmitted from the GNSS satellite. The date and time information may be obtained by other methods, such as receiving standard time information from an NTP (Network Time Protocol) server.
[0022] (2) Configuration of electronic control system S and its relationship with the certificate verification device Fig. 2 is a diagram showing an example of the configuration of an electronic control system S. The electronic control system S is made up of a plurality of electronic control units 20 (hereinafter referred to as ECUs (Electronic Control Units)) and an in-vehicle network (NW1 to NW3) that connects them. Fig. 2 shows nine ECUs (ECU20a to ECU20i) as an example, but the electronic control system S is naturally made up of any number of ECUs. In the following explanation, the ECU20 or each ECU20 will be used to comprehensively explain one or more electronic control units as a whole, and the ECU20a, ECU20b, ECU20c, ... will be used to specifically explain each individual electronic control unit.
[0023] 2, the ECUs 20 are connected to each other via an in-vehicle communication network such as a Controller Area Network (CAN) or a Local Interconnect Network (LIN). Alternatively, the ECUs 20 may be connected to each other using any communication method, whether wired or wireless, such as Ethernet (registered trademark), Wi-Fi (registered trademark), or Bluetooth (registered trademark).
[0024] The electronic control system S shown in FIG. 2 includes an integrated ECU 20a, an external communication ECU 20b, zone ECUs (20c, 20d), individual ECUs (20e to 20h), and a GPS reception ECU 20i.
[0025] The integrated ECU 20a is an ECU that has a function of controlling the entire electronic control system S and also has a gateway function of mediating communication between the ECUs 20. The integrated ECU 20a is also called a gateway ECU (G-ECU) or a mobility computer (MC). The integrated ECU 20a may also be a relay device or a gateway device.
[0026] The external communication ECU 20b is an ECU having a communication unit that communicates with an external device provided outside the vehicle, for example, the external device 30 in each embodiment. The communication method used by the external communication ECU 20b is the wireless communication method or the wired communication method described in the description of Fig. 1. In each embodiment, the external communication ECU 20b receives a certificate from the external device 30. In order to realize a plurality of communication methods, a plurality of external communication ECUs 20b may be provided. Also, instead of providing the external communication ECU 20b, the integrated ECU 20a may include the function of the external communication ECU 20b.
[0027] The zone ECUs (20c, 20d) are ECUs with a gateway function appropriately arranged according to the location and function of the individual ECUs described below. For example, the zone ECU 20c is an ECU having a gateway function that mediates communication between the individual ECUs 20e and 20f arranged at the front of the vehicle and other ECUs 20, and the zone ECU 20d is an ECU having a gateway function that mediates communication between the individual ECUs 20g and 20h arranged at the rear of the vehicle and other ECUs 20. The zone ECUs (20c, 20d) are sometimes called domain computers (DC). The individual ECUs 20e and 20f are connected to the zone ECU 20c via a network 2 (NW2), and the individual ECUs 20g and 20h are connected to the zone ECU 20d via a network 3 (NW3).
[0028] The individual ECUs (20e to 20h) can be configured with ECUs having any desired functions. For example, they can be drive system electronic control devices that control the engine, steering, brakes, etc., vehicle body electronic control devices that control meters, power windows, etc., information system electronic control devices such as navigation devices, or safety control system electronic control devices that perform control to prevent collisions with obstacles or pedestrians. Also, the ECUs may not be parallel to each other, but may be classified as master and slave.
[0029] The GPS reception ECU 20i receives date and time information indicating the time when the positioning signal was transmitted from the GNSS satellite. The received date and time information may be used as is, but may be corrected based on the time required for the GPS reception ECU 20i to travel from the GNSS satellite to the GPS reception ECU 20i in order to obtain a more accurate time. The GPS reception ECU 20i outputs the date and time information to the integrated ECU 20a. The GPS reception ECU 20i may be included in the external communication ECU 20b.
[0030] Each ECU 20 may be a physically independent electronic control device, or a virtualized electronic control device realized using virtualization technology. When each ECU 20 is realized by different hardware, it is sufficient that they are connected via a wired or wireless communication method, and when multiple virtualized electronic control devices are realized on the same hardware, it is sufficient that the virtualized electronic control devices are virtually connected to each other.
[0031] The certificate verification device 11 in each embodiment described below may be any device that verifies the integrity of a public key by using a certificate received by the external communication ECU 20b and uses the public key, and may be any of the ECUs 20. In Fig. 2, the individual ECU 20e is the certificate verification device 11 in each embodiment. The external device 30 corresponds to an authentication request device, and the GPS reception ECU 20i corresponds to a date and time distribution device.
[0032] The authentication request device may be a device inside the electronic control system S. For example, the integrated ECU 20a may be the authentication request device. The date and time distribution device may be a device inside the electronic control system S other than the GPS reception ECU 20i. For example, the integrated ECU 20a may be the date and time distribution device. Alternatively, the date and time distribution device may be a device outside the electronic control system S. For example, a GNSS satellite may be the date and time distribution device.
[0033] The certificate validation device 11 will be described below as an example of the first embodiment, the certificate validation device 12 as an example of the second embodiment, and the certificate validation device 13 as an example of the third embodiment.
[0034] 2. Embodiment 1 (1) Configuration of the certificate validation device 11 An example of the configuration of the certificate validation device 11 of this embodiment will be described with reference to Fig. 3. The certificate validation device 11 includes a receiving unit 101, a date and time information storage unit 102, a log generating unit 103, a log storage unit 104, and a certificate validation unit 105. In this embodiment, the certificate validation device 11 is assumed to be provided in the individual ECU 20e of Fig. 2.
[0035] The certificate validation device 11 can be configured with a general-purpose CPU (Central Processing Unit), volatile memory such as RAM, non-volatile memory such as ROM, flash memory, or hard disk, various interfaces, and an internal bus connecting these. Then, by executing software on this hardware, it can be configured to perform the functions of each functional block shown in FIG. 3.
[0036] The certificate validation device 11 is a device that verifies the "expiration date" of a "certificate." The same applies to the certificate validation device 12 of the second embodiment and the certificate validation device 13 of the third embodiment. Where: A "certificate" is anything that proves the owner of a public key. The "expiration date" is sufficient as long as it is a time criterion indicating that the certificate is valid, and may be a condition that the expiration date is fulfilled in addition to a deadline or period.
[0037] The receiving unit 101 receives a certificate from the authentication request device. In this embodiment, since the authentication request device is the external device 30, the receiving unit 101 receives the certificate transmitted from the external device 30 via the external communication ECU 20b, the integrated ECU 20a, and the zone ECU 20c. The received certificate is, for example, a public key with a signature of a certificate authority attached thereto, but is not limited to this.
[0038] The receiving unit 101 also receives first date and time information, which is information on "date and time", from the date and time distribution device. In this embodiment, since the date and time distribution device is the GPS reception ECU 20i, the receiving unit 101 receives the first date and time information generated by the GPS reception ECU 20i based on the date and time information received from the GNSS satellite via the integrated ECU 20a and the zone ECU 20c. In this embodiment, the first date and time information is made up of information on the day, hour, minute, and second, but is not limited to this. The timing of receiving the first date and time information may be every certain period, for example, every second, or may be by sending a request to the date and time distribution device. Note that the date and time distribution device may always receive date and time information from the GNSS satellite when radio waves from the GNSS satellite are received, or may periodically receive date and time information from the GNSS satellite. Here, the "date and time" may be a calendar day, a calendar time, or a calendar day and time, and the time may be hours, hours and minutes, hours, minutes and seconds, or a unit of time shorter than seconds. Other information that indirectly indicates the date and time may also be used.
[0039] The date and time information storage unit 102 stores the first date and time information received by the receiving unit 101. The date and time information storage unit 102 may use a non-volatile or volatile recording medium. The date and time information storage unit 102 may always store only the latest first date and time information, but may also store information for a certain period of time in the past. The date and time information storage unit 102 may store third date and time information in addition to the first date and time information. The third date and time information will be described in the third embodiment.
[0040] The log generating unit 103 generates various logs to be generated by the certificate verification device 11 itself, that is, in this embodiment, the individual ECU 20e that realizes the certificate verification device 11. For example, there are SEv (Security Event) and QSEv (Qualified Security Event), a driving log, and the like, which are generated by a security sensor mounted on the individual ECU 20e. Furthermore, the timing for generating a log in log generating unit 103 may be periodically or when some trigger occurs. Hereinafter, the log generated by log generating unit 103 will be referred to as the local device generated log.
[0041] Log storage unit 104 stores the local device generated log generated by log generation unit 103. Like date and time information storage unit 102, log storage unit 104 may use a non-volatile or volatile recording medium. The device-generated log stored in log storage unit 104 is linked to second date and time information indicating the date and time when the log was generated. For example, when log generation unit 103 generates the device-generated log, log generation unit 103 reads out the first date and time information stored in date and time information storage unit 102, and includes it in the device-generated log as the second date and time information. Alternatively, when log generation unit 103 generates the device-generated log, a request for distribution of the first date and time information may be made to the date and time distribution device, and the first date and time information received by receiving unit 101 may be included in the device-generated log as the second date and time information. In these cases, the second date and time information indicates the date and time when the device-generated log was generated. Note that it is sufficient that the second date and time information is linked to the device-generated log, and the second date and time information does not necessarily have to be the content of the device-generated log.
[0042] The log storage unit 104 may store logs generated by other devices in addition to the log generated by the own device. That is, in this embodiment, the receiving unit 101 receives logs generated by ECUs 20 other than the individual ECU 20e and stores them in the log storage unit 104. Hereinafter, a log generated by another device will be referred to as a “other-device generated log.” Examples of the other-device generated log are similar to the examples of the own-device generated log. The other-device generated log stored in log storage unit 104 is, for example, linked to second date and time information by the other device and transmitted. The method of linking the other-device generated log with the second date and time information in the other device is the same as the example described for the self-device generated log. However, when the other-device generated log is received, the other-device generated log may be linked to the first date and time information stored in date and time information storage unit 102 as the second date and time information, or the first date and time information received as a result of a distribution request to the date and time distribution device may be linked as the second date and time information. In this case, the second date and time information indicates the date and time when the other-device generated log was received.
[0043] The certificate validation unit 105 verifies the integrity of the certificate, whether the certificate has been revoked, and whether the certificate has expired. The validation of the integrity of the certificate is performed by using the public key of the certification authority stored in a key management unit (not shown) to validate whether the information included in the certificate, such as the public key and validity period, has been tampered with. The validation of whether the certificate has been revoked is performed by verifying the certificate against a certificate revocation list (CRL) stored in a key management unit (not shown). The validation of whether the certificate has expired is performed by verifying whether the certificate has expired at the current date and time.
[0044] In this embodiment, the first date and time information is used to verify whether or not the certificate has expired. For example, in FIG. 4(a), if the validity period of the certificate is the period from T1 to T2, and the current date and time, i.e., the first date and time information, is Tp1, it is determined that the certificate has expired because Tp1 is not included in the period from T1 to T2 (i.e., outside the validity period). On the other hand, if the first date and time information is Tp2, it is determined that Tp2 is included in the period from T1 to T2 (i.e., within the validity period), and it is determined that the certificate has not expired (i.e., before the expiration date). Hereinafter, this verification will be referred to as verification of whether or not the certificate has expired.
[0045] On the other hand, if the receiving unit 101 "cannot receive" the first date and time information from the date and time distribution device, the current time is unknown to the certificate verification device 11, and therefore it is not possible to verify whether the certificate has expired. Any method can be used to determine how the receiving unit 101 cannot receive the first date and time information from the date and time distribution device. For example, in the case where the first date and time information is distributed periodically from the date and time distribution device at a fixed cycle, this corresponds to the case where the first date and time information cannot be received even after a time exceeding the fixed cycle has elapsed. In addition, in the case where the first date and time information is acquired by sending a request to the date and time distribution device, this corresponds to the case where the first date and time information cannot be received after a predetermined time from the sending of the request. Here, "if it cannot be received" means that it is sufficient that the receiving unit of the certificate validation device cannot receive the signal, regardless of the reason for the inability to receive the signal. For example, this includes cases where the cause lies in the receiving unit of the certificate validation device, the cause lies in the date and time distribution device, the cause lies in the device that provides date and time information to the date and time distribution device, or the cause lies in the communication between these devices.
[0046] Therefore, in this embodiment, when the receiving unit 101 "cannot receive" the first date and time information from the date and time distribution device, the certificate verification unit 105 verifies that the certificate has expired using the second date and time information linked to the log stored in the log storage unit 104. Specifically, the certificate verification unit 105 reads the second date and time information from the log including the second date and time information indicating the latest date and time among the self-device generated log and the other-device generated log stored in the log storage unit 104, and verifies that the certificate has expired. For example, in FIG. 4(b), if the validity period of the certificate is the period from T1 to T2, if the latest time added to the log, i.e., the second date and time information, is Tr1, Tr1 is not included in the period from T1 to T2 (i.e., outside the validity period), and it is determined that the certificate has expired. On the other hand, if the second date and time information is Tr2, Tr2 is included in the period from T1 to T2, but it is not guaranteed that Tr2 indicates the current date and time, and therefore it cannot be determined that the certificate has not expired. In other words, it cannot be determined whether the certificate has expired or not. In this manner, in this embodiment, by using the second date and time information, it may be possible to determine that the certificate has expired. Hereinafter, this verification will be referred to as "verification of expiration."
[0047] It is desirable that the other device is time-synchronized with the date and time distribution device. For example, the certificate verification unit 105 selects another device that is time-synchronized with the date and time distribution device. Whether or not the time is synchronized with the date and time distribution device can be confirmed by using, for example, the IEEE802.1AS protocol. Alternatively, the other device can confirm whether or not the time is synchronized with the date and time distribution device to the ECU 20 that manages information on whether or not the time is synchronized with the date and time distribution device. According to this configuration, even when logs generated by other devices are used, time synchronization with the date and time distribution device is guaranteed for all logs, so that the latest second date and time information can be extracted. The above also applies to time synchronization between the device itself and the date and time distribution device.
[0048] In this embodiment, all logs stored in the log storage unit 104 are targeted, and no distinction is made between logs generated by the own device and logs generated by other devices. However, the certificate verification unit 105 may use only the second date and time information of the logs generated by the own device. According to this configuration, it is not necessary to check whether the time of the other device is synchronized with that of the date and time distribution device, and it is possible to more quickly verify whether the certificate has expired.
[0049] (2) Operation of the certificate validation device 11 The operation of certificate validation device 11 will be described with reference to Figures 5 and 6. Note that the operation shown in Figures 5 and 6 not only shows the certificate validation method executed by certificate validation device 11, but also shows the processing procedure of a certificate validation program executable by certificate validation device 11. The processing shown here is not limited to the order shown in Figures 5 and 6. In other words, the order may be changed as long as there are no constraints, such as a relationship in which a certain step utilizes the result of the previous step. The same applies to Figures 8 and 10 described below.
[0050] FIG. 5 is a diagram for explaining the overall operation of certificate verification device 11. As shown in FIG. The receiving section 101 of the certificate verification device 11 receives the certificate from the authentication request device (S101). The receiving unit 101 receives the first date and time information from the date and time distribution device, and stores it in the date and time information storage unit 102 (S102). Log generating unit 103 generates a local device generated log and stores it in log storage unit 104 (S103). Furthermore, receiving unit 101 receives a different device generated log from another device and stores it in log storage unit 104 (S103). The certificate verification unit 105 verifies the integrity of the certificate (S104). The certificate validation unit 105 verifies whether the certificate has been revoked (S105). The certificate validation unit 105 validates whether the certificate has expired (S106). Details of S106 will be described with reference to FIG. If all the verifications from S104 to S106 are successful (S107: Yes), the certificate verification unit 105 outputs information indicating that the verification was successful as the certificate verification result (for example, information indicating that the certificate is valid) (S108). On the other hand, if all the verifications from S104 to S106 are not successful (S107: No), that is, if at least one of the verifications from S104 to S106 is not successful, the certificate verification unit 105 outputs information indicating that the verification was unsuccessful as the certificate verification result (for example, information indicating that the certificate is invalid) (S109).
[0051] FIG. 6 is a diagram for explaining details of the operation (S106) of the certificate validation unit 105 in the certificate validation device 11 to validate whether or not the validity period has expired. The certificate validation unit 105 verifies whether the first date and time information is receivable (S110). If the first date and time information is receivable (S110: Yes), the certificate validation unit 105 reads the first date and time information from the date and time information storage unit 102 (S111). If the first date and time information is within the validity period of the certificate (S112: Yes), the certificate validation unit 105 determines that the validity period verification has been successful (S113). If the first date and time information is not within the validity period of the certificate (S112: No), the certificate validation unit 105 determines that the validity period verification has failed (S114). On the other hand, if the first date and time information cannot be received (S110: No), the certificate validation unit 105 reads the latest second date and time information from the log storage unit 104 (S115). If the second date and time information is within the validity period of the certificate (S116: Yes), the certificate validation unit 105 determines that the expiration date verification is not possible (S117). If the second date and time information is not within the validity period of the certificate (S116: No), the certificate validation unit 105 determines that the expiration date verification has failed (S114).
[0052] (3) Summary As described above, according to this embodiment, even if the receiving unit 101 cannot receive the first date and time information, it is possible to verify the expiration of the certificate using the second date and time information linked to the self-device generated log or the other device generated log, and in particular, if it is determined that the certificate has expired, it is possible to quickly execute the processing required in the case of expiration. Furthermore, by using not only the own device generated log but also the other device generated log, even if there is a problem with the own device acquiring the second date and time information or adding the second date and time information to the own device generated log, it is possible to reflect more up-to-date second date and time information. Furthermore, since the certificate verification device 11 verifies the expiration of the certificate based on the log already stored in the log storage unit 104, there is no need to inquire of other devices about date and time information, and an increase in traffic on the in-vehicle network can be suppressed.
[0053] 3. Embodiment 2 (1) Configuration of the certificate validation device 12 In the first embodiment, if the receiving unit 101 cannot receive the first date and time information, the expiration is verified using the second date and time information linked to the log. In the present embodiment, the expiration is verified using the first date and time information stored in the date and time information storage unit 102 in addition to the second date and time information linked to the log.
[0054] An example of the configuration of certificate validation device 12 of this embodiment will be described with reference to Fig. 7. The configuration of certificate validation device 12 of this embodiment is the same as the configuration of certificate validation device 11 of embodiment 1 shown in Fig. 3, except for some of the operations of certificate validation unit 205. The same components as in Fig. 3 are given the same numbers as in Fig. 3, and the description of embodiment 1 will be quoted. Only the parts that differ from embodiment 1 will be described below.
[0055] When the receiving unit 101 "cannot receive" the first date and time information from the date and time distribution device, the certificate validating unit 205 verifies that the certificate has expired using the latest date and time information among the first date and time information received in the past and stored in the date and time information storage unit 102, and the second date and time information linked to the log stored in the log storage unit 104. In other words, even if the first date and time information cannot be received, the certificate validating unit 205 verifies that the certificate has expired using the latest date and time information among the first date and time information and the second date and time information, taking advantage of the fact that the first date and time information received in the past is stored in the date and time information storage unit 102.
[0056] In the second embodiment, the explanations in the first embodiment regarding the time synchronization between the other device generated log and the date and time distribution device, and the explanations regarding the own device generated log and the other device generated log also apply, so these explanations are also cited in this embodiment.
[0057] (2) Operation of the certificate validation device 12 The operation of the certificate verification device 12 will be described with reference to FIGS. FIG. 5 is also common to the operation of the certificate validation device 12 of this embodiment, so FIG. 5 and the explanation of FIG. 5 will be quoted in this embodiment. In addition, in Fig. 8, the same step numbers are used for the parts common to Fig. 6, and the explanation of Fig. 6 is quoted in this embodiment. Below, the parts different from Fig. 6 will be explained.
[0058] If the certificate verification unit 205 is unable to receive the first date and time information (S110: No), the certificate verification unit 205 reads out the latest first date and time information received in the past and stored in the date and time information storage unit 102, and the latest second date and time information stored in the log storage unit 104 (S215). The certificate validation unit 205 verifies the expiration of the certificate using the most recent date and time information of the first date and time information and the second date and time information read in S215 (S216). That is, if the latest date and time information is within the validity period of the certificate (S216: Yes), the certificate validation unit 205 determines that the expiration date verification is not possible (S117). If the second date and time information is not within the validity period of the certificate (S216: No), the certificate validation unit 205 determines that the expiration date verification has failed (S114).
[0059] (3) Summary As described above, according to this embodiment, even if the receiving unit 101 cannot receive the first date and time information, the latest date and time information among the first date and time information and the second date and time information received in the past is used to verify the expiration of the certificate. Therefore, verification can be performed using date and time information closer to the current time, thereby improving the accuracy of the verification of the expiration of the certificate. Since the certificate expiration is verified based on the date and time information already held by the certificate verification device 11, there is no need to inquire of other devices about the date and time information, and an increase in traffic on the in-vehicle network can be suppressed.
[0060] 4. Embodiment 3 (1) Configuration of the certificate validation device 13 In this embodiment, third date and time information is received from the date and time delivery alternative device, and is used to verify whether or not the validity period has expired.
[0061] An example of the configuration of the certificate validation device 13 of this embodiment will be described with reference to Fig. 9. The configuration of the certificate validation device 13 of this embodiment has a configuration related to a date and time delivery alternative device, in addition to the configuration of the certificate validation device 11 of the first embodiment shown in Fig. 3 and the configuration of the certificate validation device 12 of the second embodiment shown in Fig. 7. The same configuration as in Fig. 3 is given the same numbers as in Fig. 3, and the description of the first embodiment will be quoted. Only the parts that differ from the first embodiment will be described below.
[0062] The receiving unit 301 receives a certificate from the authentication request device and first date and time information from the date and time distribution device, and also receives third date and time information from the date and time distribution alternative device. The date and time distribution alternative device is connected to the date and time distribution device and receives the first date and time information from the date and time distribution device. Then, in response to a request from the certificate verification device 13, for example, the date and time distribution alternative device transmits the stored first date and time information to the certificate verification device 13 as the third date and time information. The date and time distribution alternative device may be any device that receives and stores the first date and time information from the date and time distribution device, and in Fig. 2, for example, the integrated ECU 20a corresponds to the date and time distribution alternative device. Alternatively, the zone ECU 20c or the zone ECU 20d may be used.
[0063] It is preferable that the date and time distribution alternative device is a device that is time-synchronized with the date and time distribution device. For example, the certificate verification unit 305 selects a date and time distribution alternative device that is time-synchronized with the date and time distribution device. Whether or not time synchronization with the date and time distribution device is achieved may be determined, for example, by sending an inquiry from the certificate verification device 13 as to whether or not time synchronization is achieved, and receiving a response as to whether or not time synchronization is achieved from the date and time distribution alternative device. Alternatively, an inquiry may be sent to the ECU 20 that manages information as to whether or not time synchronization with the date and time distribution device is achieved, and a response may be received from the ECU 20.
[0064] The date and time information storage unit 302 stores the third date and time information received by the receiving unit 301 in addition to the first date and time information.
[0065] If the certificate validation unit 305 cannot determine whether the certificate has expired, it reads the third date and time information from the date and time information storage unit 302 and verifies whether the certificate has expired using the third date and time information. That is, in the first and second embodiments, if it is not possible to verify whether the certificate has expired, the certificate validation unit 305 verifies whether the certificate has expired using the third date and time information.
[0066] (2) Operation of the certificate validation device 13 The operation of the certificate verification device 13 will be described with reference to FIGS. FIG. 5 is also common to the operation of the certificate validation device 13 of this embodiment, so FIG. 5 and the explanation of FIG. 5 will be quoted in this embodiment. 10, the same step numbers are used for the parts common to Fig. 6, and the explanation for Fig. 6 is quoted for this embodiment. Below, the parts different from Fig. 6 will be explained.
[0067] If the second date and time information is within the validity period of the certificate (S116: Yes), the certificate verification unit 305 transmits a request for date and time information to the date and time delivery alternative device (S317). The receiving unit 301 receives the third date and time information from the date and time delivery alternative device (S318). If the third date and time information is within the validity period of the certificate (S319: Yes), the certificate validation unit 305 determines that the validity verification has been successful (S113). If the third date and time information is not within the validity period of the certificate (S319: No), the certificate validation unit 305 determines that the validity verification has failed (S114). If the third date and time information cannot be received in S318, it may be determined that the validity period cannot be verified.
[0068] (3) Summary As described above, according to this embodiment, even if it is not possible to verify whether a certificate has expired using the first date and time information or the second date and time information received in the past, it is possible to verify whether the certificate has expired using the third date and time information. In addition, since the date and time information of another device, called a date and time information distribution alternative device, is used, even if there is a problem with the acquisition of the first date and time information in the own device, the third date and time information, which is accurate date and time information received from a date and time information distribution device that is operating normally, can be used to verify whether the expiration date has expired.
[0069] 5.Other inventions In the third embodiment, if it is not possible to verify whether the certificate has expired using the first date and time information or the second date and time information, the third date and time information is used to verify whether the certificate has expired. However, if the receiving unit 301 cannot receive the first date and time information, the certificate validating unit 305 may use the third date and time information to verify whether the certificate has expired. That is, embodiment 3 also discloses the following invention.
[0070] A certificate verification device that verifies the validity period of a certificate, comprising: a receiving unit (301) that receives the certificate from the authentication request device and first date and time information, which is date and time information, from a date and time distribution device; a date and time information storage unit (302) that stores the first date and time information; a log storage unit (104) for storing a log generated or received by the certificate verification device; a certificate verification unit (305) that verifies whether the validity period of the certificate has expired by using the first date and time information, If the receiving unit cannot receive the first date and time information, the certificate validating unit verifies whether or not the certificate has expired by using third date and time information received from a date and time distribution alternative device connected to the date and time distribution device. Certificate verification device (13).
[0071] 6. Summary The features of the certificate validation device and the like in each embodiment of the present invention have been described above.
[0072] The terms used in each embodiment are merely examples and may be replaced with synonymous terms or terms having the same functions.
[0073] The block diagrams used to explain the embodiments classify and organize the configuration of the device by function. The blocks showing the respective functions are realized by any combination of hardware or software. In addition, since the block diagrams show the functions, they can also be understood as disclosures of a method invention and a program invention that realizes the method.
[0074] The order of the functional blocks that can be understood as the processes, flows, and methods described in each embodiment may be changed as long as there are no constraints such as a relationship in which one step utilizes the results of another step that precedes it.
[0075] The terms first, second, through Nth (N is an integer) used in each embodiment and in the claims are used to distinguish two or more configurations or methods of the same type, and do not limit the order or superiority or inferiority.
[0076] Examples of the form of the device of the present invention are as follows. Examples of the component include a semiconductor element, an electronic circuit, a module, and a microcomputer. Examples of semi-finished products include electronic control units (ECUs (Electric Control Units)) and system boards. Finished product forms include mobile phones, smartphones, tablets, personal computers (PCs), workstations, and servers. Other examples include devices with communication functions, such as video cameras, still cameras, and car navigation systems.
[0077] Additionally, necessary functions such as an antenna and a communication interface may be added to the device.
[0078] In addition, the present invention can be realized not only by dedicated hardware having the configuration and functions described in each embodiment, but also as a combination of a program for realizing the present invention recorded on a recording medium such as a memory or a hard disk, and general-purpose hardware having a dedicated or general-purpose CPU and memory capable of executing the program.
[0079] A program stored in a non-transient physical recording medium (for example, an external storage device (hard disk, USB memory, CD / BD, etc.) or an internal storage device (RAM, ROM, etc.)) of dedicated or general-purpose hardware can be provided to the dedicated or general-purpose hardware via a recording medium, or via a communication line from a server without using a recording medium. This makes it possible to always provide the latest functions through program upgrades. [Industrial Applicability]
[0080] Although the present disclosure has been described mainly as a certificate verification device for an on-board electronic control device mounted on an automobile, the present disclosure can be applied to any moving object, such as a motorcycle, a ship, a train, an airplane, etc. Furthermore, the present disclosure can be applied not only to moving objects, but also to any product that includes a microcomputer. [Explanation of symbols]
[0081] 11, 12, 13 Certificate verification device, 101 Receiving unit, 102 Date and time information storage unit, 103 Log generation unit, 104 Log storage unit, 105 Certificate verification unit, 20 ECU, 30 External device
Claims
1. A certificate verification device that verifies the validity period of a certificate, comprising: a receiving unit (101) for receiving the certificate from an authentication request device (30) and first date and time information, which is date and time information, from a date and time distribution device; a date and time information storage unit (102) for storing the first date and time information; a log storage unit (104) for storing a log generated or received by the certificate verification device; a certificate validation unit (105) that validates whether the validity period of the certificate has expired by using the first date and time information; If the receiving unit cannot receive the first date and time information, the certificate validating unit verifies that the certificate has expired by using second date and time information linked to the log stored in the log storage unit. Certificate verification devices (11, 12, 13).
2. the certificate verification unit uses the latest date and time information among the second date and time information associated with the self-device generated log generated by the certificate verification device and the other-device generated log generated by another device other than the certificate verification device. The certificate verification device (11) according to claim 1.
3. the certificate verification unit selects the other device that is time-synchronized with the date and time distribution device, and uses the latest date and time information among the second date and time information linked to the own device generated log and the other device generated log. The certificate verification device (11) according to claim 2.
4. the certificate verification unit uses the second date and time information associated with a self-generated log generated by the certificate verification device; The certificate verification device (11) according to claim 1.
5. When the receiving unit cannot receive the first date and time information, the certificate validating unit verifies that the certificate has expired by using the most recent date and time information among the first date and time information and the second date and time information that have been received in the past and are stored in the date and time information storage unit. The certificate verification device (12) according to claim 1.
6. the receiving unit receives third date and time information from a date and time distribution alternative device connected to the date and time distribution device, If the certificate validation unit cannot determine whether the certificate has expired, the certificate validation unit validates whether the certificate has expired using the third date and time information. The certificate verification device (13) according to claim 1 or 5.
7. the certificate verification unit selects the date and time distribution alternative device which is time-synchronized with the date and time distribution device, and verifies whether or not the certificate has expired using the third date and time information received from the date and time distribution device which is time-synchronized with the date and time distribution device. The certificate verification device (13) according to claim 6.
8. The certificate validation device is mounted on a mobile object.
2. The certificate verification device (11, 12, 13) according to claim 1.
9. A certificate verification method executed by a certificate verification device (11) that verifies the validity period of a certificate, comprising the steps of: The certificate is received from the authentication request device, and first date and time information, which is date and time information, is received from the date and time distribution device (S101, S102); The first date and time information is stored (S102); The log generated or received by the certificate verification device is stored (S103). Using the first date and time information, verify whether the validity period of the certificate has expired (S106, S112); If the first date and time information cannot be received, it is verified that the certificate has expired using the second date and time information linked to the stored log (S115, S116). The certificate validation method.
10. A certificate validation program executable by a certificate validation device (11) for validating the validity period of a certificate, The certificate is received from the authentication request device, and first date and time information, which is date and time information, is received from the date and time distribution device (S101, S102); The first date and time information is stored (S102); The log generated or received by the certificate verification device is stored (S103). Using the first date and time information, verify whether the validity period of the certificate has expired (S106, S112); If the first date and time information cannot be received, it is verified that the certificate has expired using the second date and time information linked to the stored log (S115, S116). Certificate validation programs.
Citation Information
Patent Citations
Relay processing device, relay processing method, and program
JP2012044694A
On-vehicle device
JP2015119243A
Unauthorized connection detecting device, unauthorized connection detecting system, and unauthorized connection detecting method
US20140129829A1
Communications device, partner communications device, and communications program
WO2016147568A1
Packed food sterilizer and sterilization
JP1999009243A
