Information Management System
The information management system addresses the challenge of managing driver-specific data in shared vehicles by securely identifying and collecting driver information for personalized telematics insurance, ensuring privacy and secure data transmission.
Patent Information
- Application Number
- JP2021022213
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2021-02-16
- Publication Date
- 2024-12-25
- Estimated Expiration
- 2041-02-16
AI Technical Summary
Conventional data collection systems struggle with managing driver-specific information when multiple drivers use a single vehicle, such as in car-sharing scenarios.
An information management system that includes a driver identification unit to acquire personal identification information, an information acquisition unit to collect driver information, and individual information storage units to associate personal identification information with driver information, enabling secure and individualized management of driver data.
The system allows for the collection and management of driver-specific information, ensuring secure identification and privacy of each driver, even when multiple drivers use the same vehicle, facilitating personalized telematics insurance calculations and secure data transmission.
Smart Images

Figure 0007606358000002 
Figure 0007606358000003 
Figure 0007606358000004
Abstract
Description
[Technical field]
[0001] The present disclosure relates to an information management system that manages information related to a driver of a vehicle. [Background technology]
[0002] Conventionally, a data collection system has been known that includes an on-board device mounted on a vehicle and a server that communicates with the on-board device via a network, and collects probe data from the vehicle (Patent Document 1, Abstract, Claim 1, etc.). In this conventional data collection system, the server includes a data collection condition determination unit, a data collection condition distribution unit, and a probe reception processing unit. The on-board device also includes a data acquisition unit, a collection data narrowing down processing unit, and a probe data transmission unit.
[0003] The data collection condition determination unit of the server determines data collection conditions including a frequency of collection of probe data in the vehicle. The data collection condition distribution unit of the server distributes the data collection conditions determined by the data collection condition determination unit to the vehicle. The probe reception processing unit of the server receives the probe data transmitted from the vehicle and stores it in a storage device.
[0004] The data acquisition unit of the in-vehicle device acquires data related to the surrounding environment or state of the vehicle. The collected data selection processing unit of the in-vehicle device extracts probe data for each collection frequency from the data acquired by the data acquisition unit based on the data collection conditions distributed from the server. The probe data transmission unit of the in-vehicle device transmits the probe data extracted for each collection frequency by the collected data selection processing unit to the server. [Prior art documents] [Patent documents]
[0005] [Patent Document 1] JP 2018-055191 A Summary of the Invention [Problem to be solved by the invention]
[0006] According to the conventional data collection system, data acquired by the vehicle can be collected at an appropriate data collection frequency in a server (Patent Document 1, paragraph 0008, etc.). However, this conventional data collection system has a problem in handling information related to each driver when multiple drivers drive one vehicle, such as in car sharing.
[0007] The present disclosure provides an information management system capable of resolving issues regarding the handling of information related to each driver when multiple drivers drive a single vehicle. [Means for solving the problem]
[0008] One aspect of the present disclosure is an information management system that manages driver information regarding a vehicle driver, and is characterized by having a driver identification unit that acquires personal identification information of the driver, an information acquisition unit that acquires the driver information including driving information of the vehicle, and an individual information storage unit that stores individual information associating the personal identification information with the driver information. Effect of the Invention
[0009] According to the above aspect of the present disclosure, it is possible to provide an information management system that can solve problems related to the handling of information related to each driver when multiple drivers drive a single vehicle. [Brief description of the drawings]
[0010] [Figure 1] 1 is a block diagram showing a first embodiment of an information management system according to the present disclosure. [Diagram 2] 1 is a block diagram of a vehicle equipped with an information management system according to a first embodiment. [Diagram 3] 3 is a block diagram showing an example of an electronic key that wirelessly communicates with the key input unit of FIG. 2; [Figure 4] 3 is a block diagram showing an example of a PDA that performs wireless communication with the key input unit of FIG. 2. [Diagram 5] FIG. 3 is a flow diagram showing an example of processing by the information management system of FIG. 2. [Figure 6] FIG. 11 is a block diagram of a vehicle equipped with an information management system according to a second embodiment. [Figure 7] FIG. 7 is a flow diagram showing an example of a process performed by the information management system of FIG. 6. [Figure 8] FIG. 7 is a flow diagram showing an example of a process performed by the information management system of FIG. 6. [Figure 9] FIG. 7 is a flow diagram showing an example of a process performed by the information management system of FIG. 6. [Figure 10] FIG. 11 is a block diagram of a driver identification unit of an information management system according to a third embodiment. [Figure 11] FIG. 11 is a flow chart showing an example of processing by an information management system according to a third embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0011] Hereinafter, an embodiment of an information management system according to the present disclosure will be described with reference to the drawings.
[0012] (Embodiment 1) Fig. 1 is a block diagram showing a first embodiment of an information management system according to the present disclosure. Fig. 2 is a block diagram of a vehicle V equipped with an information management system 1 according to the first embodiment. The information management system 1 of the present embodiment is a system that manages driver information related to a driver of the vehicle V, and is, for example, a vehicle system equipped in the vehicle V. The vehicle V is, for example, a gasoline engine vehicle, a diesel engine vehicle, a hybrid vehicle, an electric vehicle, or a hydrogen vehicle.
[0013] As shown in Fig. 1, a vehicle V is connected to a server S in a data center DC and a plurality of computers PC constituting a distributed network DN, for example, via a wireless communication line RCL, a wireless base station WBS, and a wired communication line WCL. The plurality of computers PC constituting the distributed network DN perform data communication in a P2P (peer-to-peer) network manner.
[0014] 2, the information management system 1 includes, for example, a key authentication unit 11 including a driver identification unit 111, an information acquisition unit 12, and an information management unit 13. The information management system 1 may also include, for example, a key input unit 14, a communication unit 15, a plurality of electronic control units (ECUs) 16, 17, and an in-vehicle network 18 mounted on the vehicle V. The information management system 1 may also include devices and networks external to the vehicle V, such as a server S of a data center DC shown in FIG. 1 and a computer PC constituting a distributed network DN.
[0015] The communication unit 15 includes, for example, a wireless communication device capable of communicating with a wireless base station WBS or a communication device outside the vehicle V via a wireless communication line RCL. The ECUs 16 and 17 are, for example, electronic control devices for controlling the power train of the vehicle V and various actuators constituting an advanced driver assistance system (ADAS) or an autonomous driving system (ADS). The in-vehicle network 18 is, for example, configured by a controller area network (CAN) or Ethernet (registered trademark). Other general components of the vehicle V are not illustrated or described.
[0016] The key input unit 14 performs wireless communication with, for example, an electronic key constituting a keyless entry system of the vehicle V, or a smart key or a mobile information terminal constituting a smart entry system of the vehicle V. As a result, the key input unit 14 acquires encrypted information including a vehicle identification number VIN from the electronic key, smart key, or mobile information terminal. The encrypted information acquired by the key input unit 14 also includes, for example, personal identification information PI. The personal identification information PI includes, for example, a personal identification number PIN. The key input unit 14 outputs the encrypted information acquired from the electronic key, smart key, or mobile information terminal to, for example, the key authentication unit 11.
[0017] Fig. 3 is a block diagram showing an example of an electronic key 2 that performs wireless communication with the key input unit 14 of Fig. 2. The information management system 1 may include, for example, the electronic key 2. The electronic key 2 includes, for example, an antenna 21, a microcontroller 22, and an operation button 23. The antenna 21 performs wireless communication with, for example, the key input unit 14.
[0018] The microcontroller 22 includes, for example, a non-volatile memory 221 and an input / output unit 222. For example, an encrypted vehicle identification number VIN and encrypted personal identification information PI are stored in the memory 221. When the operation button 23 is pressed, for example, the input / output unit 222 reads out the encrypted vehicle identification number VIN and personal identification information PI from the memory 221 and transmits them to the key input unit 14 via the antenna 21.
[0019] Furthermore, when the input / output unit 222 receives a request signal from the key input unit 14 via the antenna 21, it reads out the encrypted vehicle identification number VIN and personal identification information PI from the memory 221. Furthermore, the input / output unit 222 transmits the encrypted vehicle identification number VIN and personal identification information PI together with a response code to the key input unit 14 via the antenna 21.
[0020] 4 is a block diagram showing an example of a mobile information terminal 3 that performs wireless communication with the key input unit 14 of FIG. 2. Hereinafter, the mobile information terminal 3 is abbreviated as "PDA 3." The information management system 1 may include, for example, a PDA 3. The PDA 3 is, for example, a smartphone or a tablet computer. The PDA 3 includes, for example, a communication unit 31, a microcontroller 32, and an input unit 33.
[0021] The communication unit 31 of the PDA 3 performs wireless communication with the key input unit 14 mounted on the vehicle V by short-range wireless communication such as Bluetooth (registered trademark). The protocol for short-range wireless communication is not limited to Bluetooth (registered trademark). The communication unit 31 also performs communication with a server S installed in a data center DC outside the vehicle V, for example, via a wireless communication line RCL, a wireless base station WBS, and a communication network CN.
[0022] 4, the server S of the data center DC includes, for example, key management software S1 and a user database S2. In the user database S2, for example, personal identification information PI and a vehicle identification number VIN are registered in association with the user ID of the driver of the vehicle V.
[0023] The microcontroller 32 of the PDA 3 includes, for example, a key management application 321 and a memory 322. The key management application 321 is, for example, a program stored in the memory of the microcontroller 32, and is executed by a central processing unit (CPU) of the microcontroller 32. The key management application 321 transmits, for example, a user ID input by the driver of the vehicle V via the input unit 33 to the server S of the data center DC via the communication unit 31.
[0024] The key management software S1 of the server S in the data center DC is stored in the storage device of the server S and executed by the CPU of the server S. The key management software S1 receives the user ID of the driver of the vehicle V transmitted from the PDA3 via the wireless base station WBS and the communication network CN. The key management software S1 then reads out the vehicle identification number VIN and personal identification information PI corresponding to the received user ID from the user database S2 and encrypts them. Furthermore, the key management software S1 transmits the encrypted vehicle identification number VIN and personal identification information PI to the PDA3 via the communication network CN and the wireless base station WBS.
[0025] The key management application 321 of the PDA 3 receives the encrypted vehicle identification number VIN and personal identification information PI via the communication unit 31, and stores them in the memory 322. Furthermore, the key management application 321 transmits the encrypted vehicle identification number VIN and personal identification information PI to the key input unit 14 via the communication unit 31 of the PDA 3.
[0026] The key management application 321 of the PDA 3 may be installed in the server S of the data center DC. In this case, the microcontroller 32 of the PDA 3 receives, for example, an executable file for transmitting the encrypted vehicle identification number VIN and personal identification information PI from the server S of the data center DC, and stores it in the memory 322. This makes it possible to omit the key management application 321 of the PDA 3.
[0027] Returning to the description of each part of the information management system 1 shown in Fig. 2, the key authentication unit 11 is, for example, a microcontroller or ECU equipped with a CPU, a memory, a timer, and an input / output unit. The key authentication unit 11 receives information output from the key input unit 14 as input and authenticates and identifies the vehicle V and the driver. The key authentication unit 11 includes, for example, a driver identification unit 111, a VIN storage unit 112, a VIN comparison unit 113, and an interface unit 114. Each part of the key authentication unit 11 may represent a function of the key authentication unit 11 that is realized by, for example, executing a program stored in a memory by the CPU.
[0028] The driver identification unit 111 decrypts encrypted information, which is, for example, the output of the key input unit 14, and converts it into plain text. The driver identification unit 111 further extracts personal identification information PI including a personal identification number PIN from the plain text information, and separates the vehicle identification number VIN. The driver identification unit 111 outputs the vehicle identification number VIN separated from the plain text information to the VIN comparison unit 113. The driver identification unit 111 also outputs the personal identification information PI including the personal identification number PIN extracted from the plain text information to the information acquisition unit 12 and the information management unit 13 via the interface unit 114 and the in-vehicle network 18.
[0029] The VIN storage unit 112 is, for example, configured by a memory, and stores a vehicle identification number VIN unique to the vehicle V. The VIN comparison unit 113, for example, compares the vehicle identification number VIN input from the driver identification unit 111 with the vehicle identification number VIN stored in the VIN storage unit 112. If these vehicle identification numbers VIN match, the VIN comparison unit 113 transmits the collation result to an ECU for driving the vehicle (not shown) via the interface unit 114 and the in-vehicle network 18. This makes it possible to drive a power source such as an engine or a motor of the vehicle V and run the vehicle V.
[0030] As described above, the key authentication unit 11 decrypts and plaintexts, for example, the information including the encrypted vehicle identification number VIN and personal identification information PI output from the key input unit 14, using the driver identification unit 111. In this way, the key authentication unit 11 obtains the vehicle identification number VIN of the vehicle V and the personal identification information PI of the driver of the vehicle V, and authenticates and identifies the vehicle V and the driver of the vehicle V.
[0031] The information acquisition unit 12 is, for example, a microcontroller or ECU equipped with a CPU, a memory, a timer, and an input / output unit. The information acquisition unit 12 acquires driver information DI including driving information TI of the vehicle V. The information acquisition unit 12 includes, for example, an interface unit 121, a PI storage unit 122, a condition setting unit 123, a DI collection unit 124, and an individual information storage unit 125. Hereinafter, the individual information storage unit 125 may be abbreviated as a "PD storage unit 125." Each of these units of the information acquisition unit 12 may represent a function of the information acquisition unit 12 that is realized by, for example, executing a program stored in a memory by the CPU.
[0032] The interface unit 121 transmits and receives data between the key authentication unit 11, the information management unit 13, and the communication unit 15, for example, via the in-vehicle network 18. The PI storage unit 122 temporarily stores the personal identification information PI input from the key authentication unit 11 via the interface unit 114, the in-vehicle network 18, and the interface unit 121. The condition setting unit 123 sets conditions such as the type, frequency, and format of the driver information DI collected by the DI collection unit 124.
[0033] The DI collection unit 124 collects driver information DI via the interface unit 121 and the in-vehicle network 18 in accordance with the conditions set by the condition setting unit 123. Here, the driver information DI includes at least driving information TI of the vehicle V. More specifically, the DI collection unit 124 collects, for example, detection results output from an in-vehicle camera, an in-vehicle sensor, and a receiver of a global positioning satellite system (not shown), via the interface unit 121. Furthermore, the DI collection unit 124 calculates the driving information TI using, for example, the collected detection results of the in-vehicle camera, etc.
[0034] The PD memory unit 125 stores individual information PD that associates the driver information DI collected by the DI collection unit 124 with the personal identification information PI of the driver of the vehicle V stored in the PI memory unit 122, for example, as shown in Table 1 below. The driving information TI of the vehicle V includes, for example, the driving tendency DT of the driver of the vehicle V. The driver's driving tendency DT includes, for example, the number of times each item as shown in Table 1 occurs on each recording date. Note that the items of the driver's driving tendency DT shown in Table 1 are merely examples and are not particularly limited.
[0035] [Table 1]
[0036] The individual information PD including the driving tendency DT of the driver of the vehicle V as shown in Table 1 can be applied to, for example, calculation of insurance premiums in telematics insurance. In this case, the server S installed in the data center DC outside the vehicle V shown in Fig. 1 can include, for example, insurance premium calculation software S3 and an insurance premium calculation database S4. The calculation of insurance premiums by the server S of the data center DC will be described later.
[0037] In addition, the driving information TI of the vehicle V may include information such as the position, driving route, speed, acceleration, and angular velocity of the vehicle V, in addition to the driving tendency DT of the driver. Furthermore, the driver information DI may include, in addition to the driving information TI of the vehicle V, settings of the vehicle V for each driver, such as the seat position and angle, the mirror position and angle, lighting, and air conditioning, and preferences regarding in-vehicle infotainment.
[0038] As described above, the information acquisition unit 12 acquires the driver information DI including the driving information TI of the vehicle V, for example, by the DI collection unit 124. Furthermore, the information acquisition unit 12 outputs, for example, the individual information PD stored in the PD storage unit 125 to the information management unit 13 via the interface unit 121 and the in-vehicle network 18 as necessary.
[0039] The information management unit 13 is, for example, a microcontroller or ECU equipped with a CPU, a memory, a timer, and an input / output unit. The information management unit 13 manages the individual information PD that associates the personal identification information PI with the driver information DI as described above. The information management unit 13 includes, for example, an interface unit 131, an individual information storage unit 132, a private key storage unit 133, an address calculation unit 134, an electronic signature unit 135, and a public key generation unit 136.
[0040] Each of these parts of the information management unit 13 may represent a function of the information management unit 13 that is realized by, for example, executing a program stored in a memory by a CPU. In addition, hereinafter, the individual information storage unit 132 may be abbreviated as "PD storage unit 132."
[0041] The interface unit 131 transmits and receives data between the information acquisition unit 12 and the communication unit 15, for example, via the in-vehicle network 18. The PD storage unit 132 is, for example, configured by a memory, and acquires and stores the individual information PD stored in the PD storage unit 125 of the information acquisition unit 12, via the interface unit 131 and the in-vehicle network 18. If the information acquisition unit 12 does not have the PD storage unit 125, the PD storage unit 132 of the information management unit 13 may associate the personal identification information PI and the driver information DI acquired individually from the information acquisition unit 12, and store them as individual information PD as shown in Table 1 above.
[0042] The private key storage unit 133 is configured by a non-volatile memory such as a ROM, and stores a plurality of pieces of personal identification information PI and a plurality of private keys SK in one-to-one correspondence. That is, the private key storage unit 133 stores one private key SK in one address in association with one piece of personal identification information PI. In this embodiment, the individual information PD is created by the personal identification information PI acquired by the key input unit 14 and the driver information DI acquired by the information acquisition unit 12, but the individual information PD may be created by associating the personal identification information PI and the driver information DI stored in the private key storage unit 133 with each other.
[0043] The private key SK can be written to the private key storage unit 133, for example, as follows: A seed that is the basis of the private key SK is written to a non-volatile memory at the production factory of the information management system 1, private key encryption calculation software is installed in the information management unit 13, the seed is input to create the private key SK, the private key SK is written to the non-volatile memory, and the corresponding seed is deleted. The private key encryption calculation software may be downloaded before the seed is written at the production factory, and deleted after the private key SK is created.
[0044] The address calculation unit 134 receives, for example, the personal identification information PI contained in the individual information PD stored in the PD memory unit 132, and outputs the address of the private key memory unit 133 in which the private key SK corresponding to the personal identification information PI is stored.
[0045] For example, electronic signature unit 135 acquires private key SK by referring to the address of private key storage unit 133 output from address calculation unit 134, and acquires individual information PD from PD storage unit 132. Here, the individual information PD is, for example, information in which personal identification information PI is added to the beginning of driver information DI. Electronic signature unit 135 calculates a hash value of the individual information PD acquired from PD storage unit 132, for example, by using a hash function. Furthermore, electronic signature unit 135 encrypts the calculated hash value using private key SK acquired from private key storage unit 133. This allows electronic signature unit 135 to create an electronic signature by RSA encryption.
[0046] The public key generation unit 136 acquires the private key SK by, for example, referring to the address of the private key storage unit 133 output from the address calculation unit 134, and generates a public key PK using the acquired private key SK. Note that each public key PK corresponding to the private key SK unique to each driver stored in the private key storage unit 133 may be transmitted in advance via the interface unit 131, the in-vehicle network 18, and the communication unit 15 to a destination of the individual information PD of each driver.
[0047] The information management unit 13 transmits the individual information PD to which the electronic signature is attached by the electronic signature unit 135 to the outside of the vehicle V via the interface unit 131, the in-vehicle network 18, and the communication unit 15. The individual information PD to which the electronic signature is attached and which is transmitted from the vehicle V is transmitted to the wireless base station WBS via the wireless communication line RCL, for example, as shown in FIG. 1. The individual information PD to which the electronic signature is attached and which is received by the wireless base station WBS is transmitted to the server S of the data center DC and the computer PC constituting the distributed network DN, for example, via the wired communication line WCL. The server S and the computer PC authenticate the individual information PD to which the electronic signature is attached, which is received from the information management unit 13 of the information management system 1, for example, by the public key PK generated by the same information management unit 13.
[0048] Furthermore, the computer PC or its user may, for example, register the authenticated individual information PD in the blockchain. In this case, in the information management unit 13 of the information management system 1, the digital signature unit 135 encrypts the hash value of the previous block of individual information PD with the private key SK when transmitting a new block of individual information PD, and creates a digital signature for the new block of individual information PD. This allows the computer PC or its user to authenticate the digitally signed individual information PD with the public key PK and register it in the blockchain.
[0049] Furthermore, the information management unit 13 transmits, without creating an electronic signature, information that does not require an electronic signature, among the driver information DI acquired by the information acquisition unit 12, to the outside of the vehicle V via the interface unit 131, the in-vehicle network 18, and the communication unit 15. Furthermore, the electronic signature unit 135 may encrypt information including the individual information PD to be transmitted to the outside of the vehicle V, using the private key SK.
[0050] The operation of the information management system 1 of this embodiment will be described below. As shown in Fig. 1, the information management system 1 of this embodiment is connected to, for example, a distributed network DN or a data center DC, and a vehicle V and the data center DC transmit and receive data and programs in both directions.
[0051] Examples of data and program transmission from the data center DC to the vehicle V include FOTA (Firmware Over-The-Air) for updating ECU programs, updating map data for a car navigation system, and distribution of music data. Also, an example of data transmission from the vehicle V to the data center DC is transmission of diagnostic information for parts of the vehicle V. In this case, the data center DC can manage the parts of the vehicle V, for example, by transmitting the diagnostic information for the parts received from the vehicle V to a car dealer, and the car dealer can replace the parts.
[0052] The insurance industry is also working to utilize the driving information TI of vehicle V. Telematics insurance, which reflects the driving information TI of vehicle V in the insurance premium, is moving from a stage where the premium is calculated based on the mileage of vehicle V to a stage where the premium is calculated based on the driver's driving tendency DT, such as the driver's sudden braking or sudden acceleration. In telematics insurance, for example, when multiple drivers share a vehicle V, such as when multiple residents of a large apartment complex share the vehicle V, it is reasonable to set insurance premiums for each driver.
[0053] When multiple drivers use one vehicle V, in order to apply telematic insurance to each driver, it is necessary to collect driving information TI of the vehicle V for each driver and manage the collected driving information TI in a state in which the driver can be identified. In addition, it is required that the driving information TI including the driver's driving tendency DT is transmitted from the vehicle V to an external data center DC in a state in which the driver can be identified. Furthermore, when the driving information TI for each driver is managed by a distributed ledger such as a blockchain, it is required to support registration in the blockchain.
[0054] To address the above-mentioned issues, the information management system 1 of this embodiment executes the following process. Fig. 5 is a flow diagram showing an example of the flow of process P1 by the information management system 1. When a driver attempts to turn on the start switch of the vehicle V, the key input unit 14 mounted on the vehicle V communicates with the electronic key 2 or PDA 3 carried by the driver. As a result, the key input unit 14 receives the encrypted vehicle identification number VIN and the encrypted personal identification information PI from the electronic key 2 or PDA 3.
[0055] 5, and executes key information input process P11. In this process P11, the driver identification unit 111 acquires the encrypted vehicle identification number VIN and the encrypted personal identification information PI of the driver from the key input unit 14. Furthermore, as described above, the driver identification unit 111 decrypts the vehicle identification number VIN and the personal identification information PI into plain text, and separates the vehicle identification number VIN and the personal identification information PI to acquire the vehicle identification number VIN and the personal identification information PI, respectively.
[0056] Furthermore, the VIN comparison unit 113 compares the vehicle identification number VIN acquired from the key input unit 14 with the vehicle identification number VIN stored in the VIN storage unit 112, and if they do not match, the vehicle V is not started. In this case, the information management system 1 ends the process shown in FIG. 5. Here, it is assumed that the vehicle identification number VIN acquired from the key input unit 14 matches the vehicle identification number VIN stored in the VIN storage unit 112. Next, the information management system 1 executes, for example, a transmission process P12 of the personal identification information PI. In this process P12, the key authentication unit 11 transmits the personal identification information PI via, for example, the in-vehicle network 18.
[0057] Next, the information management system 1 executes, for example, an acquisition process P13 of the driver information DI. In this process P13, the information acquisition unit 12 receives the personal identification information PI via the in-vehicle network 18, for example, and stores it in the PI storage unit 122. Furthermore, the information acquisition unit 12 collects the driver information DI by the DI collection unit 124 according to the conditions set by the condition setting unit 123. Then, the information acquisition unit 12 stores, in the PD storage unit 125, individual information PD that associates the personal identification information PI with the driver information DI.
[0058] Next, the information management system 1 executes, for example, a transmission process P14 of the individual information PD. In this process P14, the information acquisition unit 12 transmits the individual information PD via, for example, the in-vehicle network 18.
[0059] Next, the information management system 1 executes, for example, a preparation process P15 of a private key SK. In this process P15, the information management unit 13 receives the individual information PD via the in-vehicle network 18 by, for example, the interface unit 131, and stores it in the PD storage unit 132. Furthermore, the information management unit 13 calculates, for example, by the address calculation unit 134, the address of the private key storage unit 133 in which the private key SK corresponding to the personal identification information PI included in the individual information PD is stored, and outputs the address to the electronic signature unit 135.
[0060] Next, the information management system 1 executes, for example, an electronic signature process P16. In this process P16, the information management unit 13, for example, refers to the address of the private key storage unit 133 input from the address calculation unit 134, and acquires a private key SK corresponding to the personal identification information PI of the current driver of the vehicle V, by means of the electronic signature unit 135. Furthermore, in this process P16, the electronic signature unit 135 acquires the individual information PD from the PD storage unit 132. Then, the electronic signature unit 135 applies an electronic signature to the individual information PD using the acquired private key SK. Note that, when encrypting the individual information PD, the electronic signature may be applied after encrypting the individual information PD.
[0061] Next, the information management system 1 executes, for example, an external transmission process P17. In this process P17, the information management unit 13 transmits the individual information PD with the electronic signature to the outside of the vehicle V, for example, via the interface unit 131, the in-vehicle network 18, and the communication unit 15. With the above, the process P1 of the information management system 1 shown in FIG. 5 is completed.
[0062] The electronically signed individual information PD transmitted from the vehicle V is received by the server S of the data center DC or the computer PC of the distributed network DN, for example, via the wireless communication line RCL, the wireless base station WBS, and the wired communication line WCL shown in Fig. 1. The server S of the data center DC authenticates the received electronically signed individual information PD, for example, by using the public key PK corresponding to the personal identification information PI included in the individual information PD, using insurance premium calculation software S3.
[0063] After authenticating the individual information PD, the insurance premium calculation software S3 of the server S registers the individual information PD in the insurance premium calculation database S4. Here, the individual information PD is information in which the personal identification information PI and the driver information DI of each driver of the vehicle V are associated with each other, as shown in Table 1 above. Also, as described above, the driver information DI includes driving information TI of the vehicle V driven by each driver, and the driving information TI includes the driving tendency DT of each driver.
[0064] Therefore, the insurance premium calculation software S3 can properly calculate the risk for each driver based on the individual information PD for each driver registered in the insurance premium calculation database S4, and can calculate an appropriate insurance premium for each driver. This makes it possible to apply telematics insurance to each driver, even when a single vehicle V is driven by an unspecified number of drivers, such as in car sharing.
[0065] In addition, the computer PC constituting the distributed network DN authenticates the received digitally signed individual information PD using, for example, the public key PK corresponding to the personal identification information PI included in the individual information PD, and registers it in the blockchain. This makes it possible to prevent tampering with the individual information PD, and to build a highly reliable database using a distributed ledger.
[0066] As described above, the information management system 1 of this embodiment is a system that manages driver information DI related to the driver of the vehicle V. The information management system 1 includes a driver identification unit 111 that acquires personal identification information PI of the driver of the vehicle V, an information acquisition unit 12 that acquires driver information DI including driving information TI of the vehicle V, and individual information storage units 125, 132 that store individual information PD that associates the personal identification information PI with the driver information DI.
[0067] With this configuration, the information management system 1 of this embodiment is capable of collecting driver information DI including driving information TI in a state in which each driver can be identified based on personal identification information PI, even when multiple drivers share a single vehicle V.
[0068] The information management system 1 of this embodiment further includes a communication unit 15 capable of communicating with the outside of the vehicle V, a private key storage unit 133 in which a private key SK unique to each piece of personal identification information PI is stored, and an electronic signature unit 135 that applies an electronic signature to the individual information PD using the private key SK unique to the personal identification information PI associated with the individual information PD. The communication unit 15 also transmits the individual information PD with the electronic signature attached to the outside of the vehicle V.
[0069] With such a configuration, the information management system 1 of this embodiment can prevent impersonation by others and ensure that the individual information PD belongs to each individual driver, even when multiple drivers share one vehicle V. Furthermore, when transmitting and receiving the individual information PD between the vehicle V, the data center DC, the distributed network DN, and the like, it is possible to prevent tampering with the individual information PD, and to transmit and receive the individual information PD in a secure environment.
[0070] Furthermore, in the information management system 1 of this embodiment, the driver identification unit 111 acquires personal identification information PI transmitted from the electronic key 2 of the vehicle V or the mobile information terminal 3 owned by the driver. With this configuration, even when multiple drivers use one vehicle V, it becomes possible to easily identify the driver.
[0071] Moreover, the information management system 1 of this embodiment further includes a public key generation unit 136 that generates a public key PK corresponding to a secret key SK unique to each individual personal identification information PI. Furthermore, the communication unit 15 transmits the public key PK to the outside. With this configuration, the information management system 1 can transmit the public key PK to a plurality of computers PC constituting the distributed network DN, for example, and further transmit the individual information PD for which a digital signature is created by the secret key SK. Therefore, it becomes possible to register the individual information PD in a blockchain, which is a distributed ledger based on a public key cryptography system.
[0072] As described above, according to the information management system 1 of this embodiment, when multiple drivers drive one vehicle V, the driver information DI including the driving information TI of each driver can be collected and output independently. Furthermore, according to the information management system 1 of this embodiment, security regarding the identification of each driver can be ensured. That is, according to this embodiment, when multiple drivers drive one vehicle V, it is possible to provide an information management system 1 that can solve the problem regarding the handling of information related to each driver.
[0073] (Embodiment 2) Next, a second embodiment of an information management system according to the present disclosure will be described with reference to Figs. 1, 3, and 4, and with reference to Figs. 6 to 9. Fig. 6 is a block diagram of a vehicle V equipped with an information management system 1 according to the second embodiment. The information management system 1 differs from the information management system 1 of the first embodiment described above mainly in that it includes a hardware security module 137 including a private key storage unit 133 and a digital signature unit 135. Hereinafter, the hardware security module may be abbreviated as "HSM."
[0074] The information management system 1 or vehicle V of this embodiment is different from the information management system 1 or vehicle V of the first embodiment in that the key authentication unit 11, the information acquisition unit 12, the communication unit 15, and the ECUs 16 and 17 each include authentication units 115, 126, 152, 162, and 172 configured by an HSM. The information management system 1 or vehicle V of this embodiment also includes, for example, a battery power supply unit 19. Other configurations of the information management system 1 and vehicle V of this embodiment are similar to those of the information management system 1 and vehicle V of the first embodiment, and therefore similar parts are denoted by the same reference numerals and description thereof will be omitted.
[0075] The HSM 137 of the information management unit 13 includes a private key storage unit 133, an address calculation unit 134, a digital signature unit 135, and a public key generation unit 136, similar to those in the above-described embodiment 1. The HSM 137 is, for example, a one-chip configuration in which all encryption processing is performed by a single chip, an integrated configuration that is difficult to disassemble, and is hardware equipped with a true random number generation function, and safely stores electronic keys such as a private key SK, a public key PK, and a common key CK.
[0076] As described above, the information management system 1 of this embodiment includes a hardware security module 137 including the private key storage unit 133 and the digital signature unit 135. With this configuration, when multiple drivers use one vehicle V, the private keys SK specific to each driver can be securely stored in the private key storage unit 133 included in the HSM 137, and leakage of the private keys SK can be more reliably prevented. Therefore, according to the information management system 1 of this embodiment, not only can the same effects as those of the above-described first embodiment be achieved, but also security in identifying the driver can be ensured.
[0077] HSM 137 further includes authentication unit 138. Authentication unit 138 stores a common key CK used for message authentication, for example. That is, HSM 137 can perform message authentication by authentication unit 138 in addition to digital signature by private key storage unit 133, address calculation unit 134, digital signature unit 135, and public key generation unit 136 described above. HSM 137 can select, for example, whether to digitally sign data or to perform message authentication of data, according to an instruction input together with the data.
[0078] Moreover, the key authentication unit 11, the information acquisition unit 12, the communication unit 15, and the authentication units 115, 126, 152, 162, and 172 of the ECUs 16 and 17 are configured by hardware security modules similar to the HSM 137 of the information management unit 13. Moreover, these authentication units 115, 126, 152, 162, and 172 have a configuration similar to that of the authentication unit 138 of the HSM 137. However, unlike the HSM 137, these authentication units 115, 126, 152, 162, and 172 do not have the private key storage unit 133, the address calculation unit 134, the electronic signature unit 135, and the public key generation unit 136.
[0079] Each of the authentication units 115, 126, 138, 152, 162, and 172 calculates a MAC value using a hash function based on the data to be transmitted to the in-vehicle network 18 and the common key CK. Each of the authentication units 115, 126, 138, 152, 162, and 172 also receives data and a MAC value from the in-vehicle network 18, calculates a MAC value based on the received data and the common key CK, and compares the calculated MAC value with the received MAC value. If the calculated MAC value matches the received MAC value, authentication is successful. This prevents tampering with data transmitted and received via the in-vehicle network 18, and enables secure communication between the key authentication unit 11, the information acquisition unit 12, the information management unit 13, the communication unit 15, and the ECUs 16 and 17.
[0080] The battery power supply unit 19 is, for example, configured by a microcontroller or an ECU, and controls the supply and stopping of power from the battery installed in the vehicle V to the information acquisition unit 12 and the information management unit 13 when the start switch of the vehicle V is turned off.
[0081] The information management system 1 of this embodiment differs from the information management system 1 of the above-described first embodiment in that when the start switch of the vehicle V is turned on or off, the information management system 1 erases the individual information PD stored in the individual information storage units 125, 132. Hereinafter, the processing by the information management system 1 of this embodiment will be described.
[0082] Fig. 7 is a flow diagram showing an example of process P2 by the information management system 1 of this embodiment. When the information management system 1 starts process P2 shown in Fig. 7, it executes processes P21, P22, and P23 similar to the input process P11 of key information, the transmission process P12 of personal identification information PI, and the acquisition process P13 of driver information DI of embodiment 1 shown in Fig. 5. Next, the information management system 1 executes process P24, for example, by the battery power supply unit 19 to determine whether or not the start switch of the vehicle V is off.
[0083] In this process P24, for example, if it is determined that the start switch is not off (NO), the information management system 1 executes a process P25 for determining whether or not a predetermined time ts has elapsed since the start switch of the vehicle V was turned on or since the previous external transmission process P29 ended. In this process P25, if it is determined that the predetermined time ts has not elapsed (NO), the information management system 1 executes the process P23 for acquiring the driver information DI again.
[0084] On the other hand, if it is determined in this process P25 that the predetermined time ts has elapsed (YES), the information management system 1 executes processes P26, P27, P28, and P29 similar to the individual information PD transmission process P14, the private key SK preparation process P15, the electronic signature process P16, and the external transmission process P17 in the first embodiment shown in Fig. 5. As a result, the individual information PD is periodically transmitted to the outside of the vehicle V until the start switch of the vehicle V is turned off.
[0085] On the other hand, if it is determined in the above-mentioned process P24 that the start switch of the vehicle V is off (YES), the information management system 1 executes process P2A in which, for example, the battery power supply unit 19 supplies power from the battery of the vehicle V to the information acquisition unit 12 and the information management unit 13.
[0086] 7. Furthermore, the information management system 1 executes, for example, a process P2B in which the information acquisition unit 12 and the information management unit 13 erase the individual information PD stored in the PD storage units 125, 132. Thereafter, the information management system 1 executes, for example, a process P2C in which the battery power supply unit 19 stops the supply of power from the vehicle battery to the information acquisition unit 12 and the information management unit 13, and ends the process P2 shown in FIG.
[0087] 7, when the start switch of the vehicle V is turned off, the information management system 1 erases the individual information PD stored in the individual information storage units 125, 132. In this way, when multiple drivers use one vehicle V, the individual information PD of each driver can be prevented from being known to the other drivers, and the privacy of each driver can be protected.
[0088] Fig. 8 is a flow diagram showing an example of another process P3 by the information management system 1 of this embodiment. When the information management system 1 starts the process P3 shown in Fig. 8, it executes processes P31, P32, and P33 similar to the input process P11 of key information, the transmission process P12 of personal identification information PI, and the acquisition process P13 of driver information DI of the first embodiment shown in Fig. 5. Next, the information management system 1 executes a process P34, for example, by the battery power supply unit 19 to determine whether or not the start switch of the vehicle V is off.
[0089] In this process P34, for example, if it is determined that the start switch is not off (NO), the information management system 1 executes the driver information DI acquisition process P33 again. On the other hand, in this process P34, for example, if it is determined that the start switch is off (YES), the information management system 1 executes a process P35 in which the battery power supply unit 19 supplies power from the battery of the vehicle V to the information acquisition unit 12 and the information management unit 13.
[0090] Next, the information management system 1 executes processes P36, P37, P38, and P39 similar to the individual information PD transmission process P14, the private key SK preparation process P15, the electronic signature process P16, and the external transmission process P17 of the first embodiment shown in Fig. 5. As a result, the individual information PD is transmitted to the outside of the vehicle V when the start switch of the vehicle V is turned off.
[0091] Thereafter, the information management system 1 executes, for example, a process P3A in which the information acquisition unit 12 and the information management unit 13 erase the individual information PD stored in the PD storage units 125, 132. Thereafter, the information management system 1 executes, for example, a process P3B in which the battery power supply unit 19 stops the supply of power from the battery of the vehicle V to the information acquisition unit 12 and the information management unit 13, and ends the process P3 shown in FIG.
[0092] 8, the information management system 1 erases the individual information PD stored in the individual information storage units 125, 132 when the start switch of the vehicle V is turned off, but before erasing the individual information PD, transmits the individual information PD to the outside of the vehicle V via the communication unit 15. This not only makes it possible to protect the privacy of each driver when multiple drivers use one vehicle V, but also makes it possible to transmit the individual information PD of the driver up until the start switch of the vehicle V is turned off to the outside of the vehicle V.
[0093] Fig. 9 is a flow diagram showing an example of another process P4 by the information management system 1 of this embodiment. When the information management system 1 starts the process P4 shown in Fig. 9, it executes processes P41 and P42 similar to the input process P11 of key information and the transmission process P12 of personal identification information PI of the first embodiment shown in Fig. 5. Next, the information management system 1 executes a process P43 in which the information management unit 13 determines whether or not unoutputted individual information PD that has not been transmitted to the outside of the vehicle V is stored in the PD storage unit 125 or the PD storage unit 132.
[0094] In this process P43, for example, if it is determined that the individual information PD is not stored in the PD storage unit 125 or the PD storage unit 132 and there is no unoutput data (NO), the information management system 1 executes a process P44 similar to the driver information DI acquisition process P13 shown in Fig. 5. Next, the information management system 1 executes a process P45, for example, by the battery power supply unit 19 to determine whether or not the start switch of the vehicle V is off.
[0095] In this process P45, for example, if it is determined that the start switch is not off (NO), the information management system 1 executes the driver information DI acquisition process P44 again. On the other hand, in this process P45, if it is determined that the start switch is off (YES), the information management system 1 executes a process P46 in which the battery power supply unit 19 supplies power from the battery of the vehicle V to the information acquisition unit 12 and the information management unit 13.
[0096] Next, the information management system 1 executes a process P47 in which, for example, the information acquisition unit 12 or the information management unit 13 stores and saves the individual information PD in the non-volatile storage area of the PD storage unit 125 or the PD storage unit 132. Thereafter, the information management system 1 executes a process P48 in which, for example, the battery power supply unit 19 stops the supply of power from the battery of the vehicle V to the information acquisition unit 12 and the information management unit 13, and ends the process P4 shown in FIG.
[0097] Thereafter, for example, when the start switch of the vehicle V is turned on again, the information management system 1 again executes the input process P41 of the key information and the transmission process P42 of the personal identification information PI. Here, the previous individual information PD is stored in the non-volatile storage area of the PD storage unit 125 or the PD storage unit 132 in a state where it has not been output to the outside of the vehicle V. Therefore, the information management system 1 determines in the above-mentioned process P43 that there is data that has not been output (YES).
[0098] Then, the information management system 1 executes processes P49, P4A, P4B, and P4C similar to the individual information PD transmission process P14, the private key SK preparation process P15, the electronic signature process P16, and the external transmission process P17 of the first embodiment shown in Fig. 5. As a result, when the start switch of the vehicle V is turned on, the previous individual information PD that has not been output to the outside of the vehicle V is transmitted to the outside of the vehicle V.
[0099] Thereafter, the information management system 1 executes a process P4D in which the information acquisition unit 12 and the information management unit 13 erase the individual information PD stored in the PD storage units 125, 132. Next, the information management system 1 executes a new process P44 for acquiring driver information DI.
[0100] 9, when the start switch of the vehicle V is turned off, the information management system 1 stores the individual information PD in the non-volatile storage area of the individual information storage units 125, 132. When the start switch of the vehicle V is turned on, the information management system 1 transmits the individual information PD stored in the non-volatile storage area of the individual information storage units 125, 132 to the outside of the vehicle V via the communication unit 15 and then erases it.
[0101] With this configuration, when multiple drivers use one vehicle V, the individual information PD of the driver up until the last time the start switch of the vehicle V was turned off can be transmitted to the outside of the vehicle V the next time the start switch of the vehicle V is turned on. Furthermore, the individual information PD of each driver can be prevented from being known to other drivers, thereby protecting the privacy of each driver.
[0102] As described above, according to the information management system 1 of this embodiment, when multiple drivers use one vehicle V, the private key SK can be securely stored to ensure security in identifying the drivers. Furthermore, according to the information management system 1 of this embodiment, when multiple drivers use one vehicle V, the privacy of each driver can be protected. Therefore, according to this embodiment, when multiple drivers drive one vehicle V, it is possible to provide an information management system 1 that can solve problems related to the handling of information related to each driver.
[0103] (Embodiment 3) Next, a third embodiment of the information management system according to the present disclosure will be described with reference to Figs. 1, 3, 4, and 6, and with reference to Figs. 10 and 11. Fig. 10 is a block diagram of a driver identification unit (biometric authentication unit) 1A connected to the in-vehicle network 18 of the vehicle V shown in Fig. 6. The information management system 1 of this embodiment differs from the information management system 1 of the second embodiment described above mainly in that the driver identification unit 1A shown in Fig. 10 is provided instead of the driver identification unit 111 of the key authentication unit 11 shown in Fig. 6. The other configurations of the information management system 1 of this embodiment are similar to those of the information management system 1 of the second embodiment described above, and therefore the same reference numerals are used for similar parts and their description will be omitted.
[0104] As shown in FIG. 10, the driver identification unit 1A includes, for example, an interface unit 1A1, an authentication unit 1A2, an authentication information acquisition unit 1A3, an authentication information storage unit 1A4, a registration unit 1A5, and a matching unit 1A6.
[0105] The interface unit 1A1 is connected to, for example, an in-vehicle network 18, and transmits information to the in-vehicle network 18 and receives information from the in-vehicle network 18. The authentication unit 1A2 has a configuration similar to the authentication units 115, 126, and 138 provided in the key authentication unit 11, the information acquisition unit 12, the information management unit 13, etc., and performs message authentication of information transmitted and received via the interface unit 1A1.
[0106] The authentication information acquisition unit 1A3 is a sensor that acquires biometric information BI of the driver of the vehicle V. The biometric information BI includes, for example, fingerprint information, finger vein information, palm vein information, face image information, iris image information, and the like. In this embodiment, the authentication information acquisition unit 1A3 is, for example, an imaging unit such as a camera that captures a face image of the driver. Note that the authentication information acquisition unit 1A3 may be another sensor such as a fingerprint sensor.
[0107] The authentication information storage unit 1A4 is, for example, configured with a non-volatile memory, and stores the driver's personal identification information PI and biometric information BI such as data based on a face image in association with each other. The registration unit 1A5 stores and registers the biometric information BI acquired by the authentication information acquisition unit 1A3 in the authentication information storage unit 1A4 in association with the personal identification information PI. Note that each piece of biometric information BI is associated with personal identification information PI that is unique at least within the vehicle V.
[0108] The matching unit 1A6 matches the biometric information BI acquired by the authentication information acquisition unit 1A3 with the biometric information BI stored in the authentication information storage unit 1A4. When the biometric information BI acquired by the authentication information acquisition unit 1A3 matches the biometric information BI stored in the authentication information storage unit 1A4, the matching unit 1A6 acquires personal identification information PI associated with the biometric information BI from the authentication information storage unit 1A4.
[0109] The collation unit 1A6 transmits the personal identification information PI acquired from the authentication information storage unit 1A4, for example, to the information acquisition unit 12 or the private key storage unit 133. In this embodiment, the electronic key 2 shown in Fig. 3 and the PDA 3 shown in Fig. 4 transmit, for example, only the vehicle identification number VIN to the key authentication unit 11. In this embodiment, the key authentication unit 11 shown in Fig. 6 does not have a driver identification unit 111 because it is only necessary to authenticate the vehicle identification number VIN.
[0110] The following describes the operation of the information management system 1 of this embodiment. Fig. 11 is a flow diagram showing an example of the flow of process P5 of the information management system 1 of this embodiment.
[0111] When a driver attempts to turn on the start switch of the vehicle V, the key input unit 14 mounted on the vehicle V communicates with the electronic key 2 or PDA 3 carried by the driver. As a result, the key input unit 14 receives the encrypted vehicle identification number VIN from the electronic key 2 or PDA 3. Then, the information management system 1 starts, for example, process P5 shown in Fig. 11 and executes key information input process P51.
[0112] In this process P51, the VIN comparison unit 113 acquires the encrypted vehicle identification number VIN from the key input unit 14, and decrypts the acquired vehicle identification number VIN into plain text. Furthermore, the VIN comparison unit 113 compares the vehicle identification number VIN acquired from the key input unit 14 with the vehicle identification number VIN stored in the VIN storage unit 112, and does not start the vehicle V if they do not match. In this case, the information management system 1 ends the process shown in FIG.
[0113] Here, it is assumed that the vehicle identification number VIN acquired from the key input unit 14 matches the vehicle identification number VIN stored in the VIN storage unit 112. Next, the information management system 1 executes, for example, a biometric information acquisition process P52. In this process P52, the driver identifying unit 1A acquires the driver's biometric information BI, for example, by the authentication information acquisition unit 1A3. More specifically, for example, an imaging unit serving as the authentication information acquisition unit 1A3 captures the driver's face to acquire a facial image.
[0114] Next, the information management system 1 executes a matching process P53. In this process P53, the driver identification unit 1A, for example, uses the matching unit 1A6 to match the biometric information BI acquired by the authentication information acquisition unit 1A3 with the biometric information BI stored in the authentication information storage unit 1A4. If they do not match, the information management system 1, for example, uses the registration unit 1A5 to associate the biometric information BI acquired by the authentication information acquisition unit 1A3 with the unique personal identification information PI and stores and registers it in the authentication information storage unit 1A4.
[0115] On the other hand, when the biometric information BI acquired by the authentication information acquisition unit 1A3 matches the biometric information BI stored in the authentication information storage unit 1A4, the collation unit 1A6 acquires the personal identification information PI associated with the biometric information BI from the authentication information storage unit 1A4. Next, the information management system 1 executes a transmission process P54 of the personal identification information PI.
[0116] In this process P54, the information management system 1 transmits, for example, the personal identification information PI acquired by the collation unit 1A6 to the information acquisition unit 12 and the information management unit 13 via the interface unit 1A1 and the in-vehicle network 18. Thereafter, the information management system 1 executes processes P55, P56, P57, P58, and P59 similar to the driver information DI acquisition process P13, individual information PD transmission process P14, private key SK preparation process P15, electronic signature process P16, and external transmission process P17 of the first embodiment shown in Fig. 5. As a result, the individual information PD of the vehicle V is transmitted to the outside of the vehicle V.
[0117] As described above, in the information management system 1 of this embodiment, the driver identification unit 1A includes an authentication information acquisition unit 1A3 that acquires the driver's biometric information BI, an authentication information storage unit 1A4 that stores the biometric information BI and the personal identification information PI in association with each other, and a matching unit 1A6 that matches the biometric information BI acquired by the authentication information acquisition unit 1A3 with the biometric information BI stored in the authentication information storage unit 1A4. When the biometric information BI acquired by the authentication information acquisition unit 1A3 matches the biometric information BI stored in the authentication information storage unit 1A4, the matching unit 1A6 acquires the personal identification information PI associated with the matching biometric information BI from the authentication information storage unit 1A4.
[0118] With this configuration, the information management system 1 of this embodiment can achieve the same effects as the information management system 1 of the second embodiment, without acquiring the personal identification information PI from the electronic key 2 or the PDA 3.
[0119] The above describes in detail an embodiment of the information management system according to the present disclosure using the drawings, but the specific configuration is not limited to this embodiment, and even if there are design changes, etc., within the scope that does not deviate from the gist of the present disclosure, they are included in the present disclosure.
[0120] For example, in the above embodiment, the driver identification unit, the information acquisition unit, and the information management unit of the information management system are configured by individual ECUs or microcontrollers. However, the information management system can also be configured by, for example, one microcontroller. The information management system may also be configured as a part of a vehicle control device mounted on a vehicle. [Explanation of symbols]
[0121] 1 Information Management System 111 Driver Identification Unit 12 Information acquisition department 125 PD storage unit (individual information storage unit) 132 PD storage unit (individual information storage unit) 133 Private key storage 135 Electronic Signature Department 136 Public Key Generation Unit 137 HSM (Hardware Security Module) 15 Communications Department 1A Driver Identification Unit 1A3 Authentication information acquisition unit 1A4 Authentication information storage unit 1A6 Collation section 2 Electronic key 3. PDA (Personal Digital Assistant) BI Biometric information DI Driver Information PD Individual Information PI Personally Identifiable Information PK Public Key SK private key TI Driving Information V Vehicle
Claims
1. An information management system for managing driver information relating to a driver of a vehicle, A driver identification unit that acquires personal identification information of the driver; an information acquisition unit that acquires the driver information including driving information of the vehicle; an individual information storage unit that stores individual information that associates the personal identification information with the driver information; Equipped with A communication unit capable of communicating with an outside of the vehicle; a private key storage unit storing a private key unique to each of the personal identification information; and an electronic signature unit that performs an electronic signature on the individual information by using the private key that is unique to the personal identification information associated with the individual information, The information management system is characterized in that the communication unit transmits the individual information to which the electronic signature is attached to an outside of the vehicle.
2. 2. The information management system according to claim 1, further comprising a hardware security module including the private key storage unit and the digital signature unit.
3. 2. The information management system according to claim 1, wherein the individual information stored in the individual information storage unit is erased when a start switch of the vehicle is turned off.
4. 4. The information management system according to claim 3, wherein the individual information is transmitted to the outside of the vehicle via the communication unit before being erased.
5. When a start switch of the vehicle is turned off, the individual information is stored in a non-volatile storage area of the individual information storage unit; The information management system described in claim 1, characterized in that when the vehicle's start switch is turned on, the individual information stored in the non-volatile memory area of the individual information storage unit is transmitted to the outside of the vehicle via the communication unit and then erased.
6. a public key generating unit that generates a public key corresponding to the private key unique to each of the personal identification information; 2. The information management system according to claim 1, wherein the communication unit transmits the public key to an external device.
Citation Information
Patent Citations
Electronic signature generating device and electronic signature device
JP2005303615A
Operation information recording system and operation information recording method
JP2009169486A
Operation management system, operation recording apparatus, and management program
JP2014235609A
Data collection system
JP2018055191A
Vehicle information transmitting device, vehicle information receiving device, vehicle information communication method, and computer program
JP2020017805A
