Vehicle, information management device, and information management method

Abstract

To facilitate diagnosis and analysis of registration processing of a digital key.SOLUTION: A vehicle 10 capable of using a digital key registered in a mobile information terminal 20 of a user, transmits log information of an event that has occurred in the vehicle 10 to a management server 30 of the digital key when the digital key is registered in the mobile information terminal 20.SELECTED DRAWING: Figure 1

Description

Technical Field

[0001] The present invention relates to a vehicle, an information management device, and an information management method.

Background Art

[0002] As described in Patent Document 1, a system called a digital key that uses a portable information terminal such as a smartphone to lock, unlock, start, etc. a vehicle instead of a physical key is in practical use. It is conceivable to register a digital key to the portable information terminal using an application program installed in the portable information terminal.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] For some reason, the registration process of the digital key may not be completed normally. In order to identify the cause in such a case, it may be desired to manage the log of the registration process in the management server of the digital key service. For this purpose, it is necessary to design an application program (hereinafter referred to as a registration app) of a portable information terminal for registering a digital key so that the log necessary for cause identification is recorded.

[0005] It is conceivable that a person other than the provider of the digital key service, for example, the provider of the OS (basic software) of the portable information terminal, develops a registration app for the digital key. The specifications of such a registration app do not necessarily meet the requirements of the provider of the digital key service. Therefore, depending on the specifications of the registration app, the log of the registration process necessary for cause identification etc. may not be uploaded from the portable information terminal to the management server.

Means for Solving the Problem

[0006] The vehicle for solving the above problem is a vehicle that can use a digital key registered in a user's portable information terminal, and is configured to transmit log information of an event that occurred in the vehicle when registering the digital key in the portable information terminal to a management server of the digital key.

[0007] The information management device for solving the above problem is an information management device that manages information related to the progress of registering a digital key of a vehicle in a user's portable information terminal, and includes a processor and a data storage. The processor is configured to acquire log information of an event that occurred in the vehicle when registering the digital key from the vehicle and record it in the data storage, and acquire log information of a process performed in the portable information terminal when registering the digital key from the portable information terminal and record it in the data storage.

[0008] The information management method for solving the above problem is an information management method that manages information related to the progress of registering a digital key of a vehicle in a user's portable information terminal. The information is stored in a data storage, and the storage of the information in the data storage is performed by a processor. The processing of the processor related to the storage of the information in the data storage includes a step of acquiring and recording log information of an event that occurred in the vehicle when registering the digital key from the vehicle.

Advantages of the Invention

[0009] The above vehicle, information management device, and information management method have the effect of facilitating the diagnosis and analysis of the digital key registration process.

Brief Description of the Drawings

[0010]

Figure 1

Figure 2

Figure 3

Embodiments for Carrying Out the Invention

[0011] Hereinafter, an embodiment of a vehicle, an information management device, and an information management method will be described in detail with reference to FIGS. 1 to 3. <Configuration of Vehicle and Information Management Device> First, the configurations of the vehicle 10 and the information management device according to this embodiment will be described. The vehicle 10 according to this embodiment can use a digital key. The digital key is a system that performs locking, unlocking, starting, etc. using a portable information terminal 20 such as a smartphone owned by the user instead of a physical key. The information management device is a device that manages information related to the digital key and is operated by a provider of the digital key service. The digital key used by the vehicle 10 according to this embodiment complies with the CCC (Car Connectivity Consortium) standard.

[0012] Vehicle 10 is equipped with a digital key ECU 11. The digital key ECU 11 is an electronic control unit (ECU: Electronic Control Unit) that performs processing related to digital keys. The digital key ECU 11 includes a storage module 13 in which a program is stored, and a processor 12 that reads and executes the program from the storage module 13. Further, the digital key ECU 11 includes an HSM (Hardware Security Module) 14 that generates and stores encryption keys, performs encryption using the encryption keys, and assigns electronic signatures, etc. Further, the vehicle 10 is equipped with a TCU (Telematics Control Unit) 15 for communicating with the management server 30 using mobile communication. Further, the vehicle 10 is equipped with communication modules 16 to 18 corresponding to BLE (Bluetooth Low Energy) communication, UWB (Ultra-Wide Band) communication, and NFC (Near Field Communication), respectively. The vehicle 10 communicates with the user's portable information terminal 20 via BLE communication, UWB communication, and NFC.

[0013] The portable information terminal 20 is equipped with communication modules 21 to 23 for BLE communication, UWB communication, and NFC for communicating with the vehicle 10. Further, the portable information terminal 20 is equipped with a cellular communication module 24 for communicating with the management server 30 using mobile communication. Further, the portable information terminal 20 includes a storage module 25, a processor 26, and a secure element 27. The processor 26 reads and executes the program stored in the storage module 25. The secure element 27 is a semiconductor device including a memory having shock resistance and an encryption logic circuit.

[0014] The memory module 25 of the mobile information terminal 20 pre-stores a native app P1 and a digital key framework P2. The native app P1 is an application program that provides UIs for creating, ending, deleting, enabling, disabling, etc. of digital keys. The digital key framework P2 is a program that uses the APIs (Application Programming Interfaces) prepared in the OS to provide functions such as owner pairing, sharing, and management of digital keys. Owner pairing is a process of downloading digital key information to the mobile information terminal 20, associating the vehicle 10 with the mobile information terminal 20, and registering the digital key in the vehicle 10. The native app P1 and the digital key framework P2 are created by the provider of the basic software (OS) of the mobile information terminal 20 and are pre-installed in the mobile information terminal 20.

[0015] The provider of the digital key service provides a vehicle OEM app P3, which is an application program that provides the same functions as the native app P1. The vehicle OEM app P3 is optionally installed on the mobile information terminal 20 by the user. Registration of the digital key in the mobile information terminal 20 can be performed using either the native app P1 or the vehicle OEM app P3.

[0016] The management server 30 is a server device operated by a provider of digital key services. The management server 30 includes a processor 32 and a data storage 31. Then, the management server 30 provides various functions related to digital key services by the processor 32 executing a program stored in the data storage 31. Examples of functions provided by the management server 30 include information management of the vehicle 10 and the user, integrated management of data required for digital keys, creation and transmission of data for owner pairing, and key tracking. The data storage 31 stores a log management database 33 that records log information on digital key registration / deletion processing. The data storage 31 also stores, among other things, a vehicle database that records information on the vehicle 10, a user database that records user information, and a key trace database that records the usage history of digital keys. In the case of this embodiment, the management server 30 corresponds to an information management device.

[0017] <Digital key registration process> Next, with reference to FIG. 2, the digital key registration process will be described. Digital key registration is performed using either the native app P1 or the vehicle OEM app P3 installed on the mobile information terminal 20. Here, the case of using the native app P1 will be described. FIG. 2 shows the processing procedures of the vehicle 10, the mobile information terminal 20, and the management server 30 when registering a digital key using the native app P1. The processing of the vehicle 10 shown in FIG. 2 and FIG. 3 described later is executed by the processor 12 of the digital key ECU 11. Also, the processing of the management server 30 shown in FIG. 2 and FIG. 3 described later is executed by the processor 32 of the same management server 30.

[0018] At the time of registration processing, first, pairing between the mobile information terminal 20 and the vehicle 10 using any one of LE communication, UWB communication, and NFC is performed (S10). The pairing here is performed using the digital key ID and password registered in advance in the vehicle 10 and the mobile information terminal 20. The management server 30 generates the digital key ID and password in response to a digital key registration application from the mobile information terminal 20 by the user, and issues them to the vehicle 10 and the mobile information terminal 20.

[0019] When the pairing is completed, the vehicle 10 transmits log information indicating the completion of the pairing to the management server 30 (S12). The management server 30 records the received log information in the log management database 33 (S14).

[0020] After the pairing is completed, the mobile information terminal 20 generates a key pair of a public temporary key PK1 and a secret temporary key SK1 (S16). Similarly, after the pairing is completed, the vehicle 10 also generates a key pair of a public temporary key PK2 and a secret temporary key SK2 (S18). Then, the mobile information terminal 20 and the vehicle 10 perform key exchange of the public temporary keys PK1 and PK2 (S20). When the vehicle 10 completes the key exchange, it transmits log information indicating the completion of the temporary key exchange to the management server 30 (S22). The management server 30 records the received log information in the log management database 33 (S24).

[0021] Subsequently, the mobile information terminal 20 generates an electronic signature SIG1 using the public temporary key PK2 received from the vehicle 10 (S26). Similarly, the vehicle 10 generates an electronic signature SIG2 using the public temporary key PK1 received from the mobile information terminal 20. For example, the mobile information terminal 20 calculates the hash values of the public temporary keys PK1 and PK2, and generates the encrypted hash value with the public temporary key PK2 received from the vehicle 10 as the electronic signature SIG1. Also, the vehicle 10 calculates the hash values of the public temporary keys PK1 and PK2, and generates the encrypted hash value with the public temporary key PK1 received from the mobile information terminal 20 as the electronic signature SIG2.

[0022] Furthermore, the mobile information terminal 20 generates a key pair of a public key PK3 and a secret key SK3, and the vehicle 10 generates a key pair of a public key PK4 and a secret key SK4, respectively (S30, 32). Then, the mobile information terminal 20 and the vehicle 10 perform a key exchange of the public keys PK3, PK4 (S34). The mobile information terminal 20 and the vehicle 10 use the public keys PK3, PK4 exchanged here as data for mutual authentication. When performing the key exchange here, the mobile information terminal 20 attaches an electronic signature SIG1 to the public key PK3 and transmits it to the vehicle 10. Also, the vehicle 10 attaches an electronic signature SIG2 to the public key PK4 and transmits it to the mobile information terminal 20.

[0023] After that, the mobile information terminal 20 and the vehicle 10 respectively perform verification of the electronic signatures SIG1, SIG2 attached to the public keys PK3, PK4 (S36, S38). For example, the mobile information terminal 20 decrypts the electronic signature SIG2 received from the vehicle 10 using its own secret temporary key SK1. Then, the mobile information terminal 20 verifies the electronic signature SIG2 based on whether the value obtained by decrypting the electronic signature SIG2 matches the hash value of the public temporary keys PK1, PK2 calculated by itself. Also, the vehicle 10 decrypts the electronic signature SIG1 received from the vehicle 10 using its own secret temporary key SK2. Then, the vehicle 10 verifies the electronic signature SIG1 based on whether the value obtained by decrypting the electronic signature SIG1 matches the hash value of the public temporary keys PK1, PK2 calculated by itself.

[0024] The mobile information terminal 20 and the vehicle 10 confirm the completion of the verification of the electronic signatures SIG1, SIG2 on both sides by notifying each other of the completion of the verification (S40). By this confirmation, the exchange of the public keys PK3, PK4 used as data for mutual authentication is completed. When the vehicle 10 confirms the completion of the verification of the electronic signatures SIG1, SIG2 on both itself and the mobile information terminal 20, it transmits log information indicating the completion of the exchange of mutual authentication data to the management server 30 (S42). The management server 30 records the received log information in the log management database 33 (S44).

[0025] Thereafter, the mobile information terminal 20 generates a common secret key SK using the public key PK4 received from the vehicle 10 and its own secret key SK3 (S46). Also, the vehicle 10 generates a common secret key SK using the public key PK3 received from the mobile information terminal 20 and its own secret key SK4 (S48). The mobile information terminal 20 and the vehicle 10 confirm the completion of the generation of the common secret key SK on both sides by notifying each other of the completion of the generation of the common secret key SK (S50). Note that the mobile information terminal 20 stores the common secret key SK in the secure element 27. Also, the vehicle 10 stores the common secret key SK in the HSM 14. Thus, the common secret key SK stored in the mobile information terminal 20 and the vehicle 10 is used for mutual authentication between the vehicle 10 and the mobile information terminal 20 when using the digital key.

[0026] When the mobile information terminal 20 confirms the completion of the generation of the common secret key SK on both itself and the vehicle 10, it transmits log information indicating the completion of the registration of the digital key to the management server 30 (S52). The management server 30 records the received log information in the log management database 33 (S54). Also, the management server 30 registers the information of the digital key in the key trace database in order to start recording the usage history of the registered digital key (S56). Then, the management server 30 notifies the mobile information terminal 20 that the registration of the digital key has been completed (S58).

[0027] On the other hand, when the mobile information terminal 20 and the vehicle 10 confirm the completion of the generation of the common secret key SK on both sides, they temporarily disconnect their pairing (S60). Then, the mobile information terminal 20 and the vehicle 10 perform mutual authentication using the common secret key SK and resume the pairing (S62). Thereafter, the mobile information terminal 20 and the vehicle 10 activate the digital key when both the resumption of the pairing and the notification of the completion of the registration confirmation from the management server 30 have been performed (S64). The activation of the digital key is to make it possible to lock, unlock, and start the vehicle 10 using the mobile information terminal 20.

[0028] <Digital Key Deletion Process> Next, with reference to FIG. 3, the deletion process of the digital key will be described. The deletion of the digital key is performed using either the native app P1 or the vehicle OEM app P3 installed in the mobile information terminal 20, similar to the registration process. Here, the case of using the native app P1 will be described. FIG. 3 shows the processing procedures of the vehicle 10, the mobile information terminal 20, and the management server 30 when deleting the digital key using the native app P1.

[0029] At the time of the deletion process, first, pairing between the mobile information terminal 20 and the vehicle 10 is performed using either LE communication, UWB communication, or NFC (S100). The pairing here is performed using the common secret key SK generated at the time of registration. When the pairing is completed, the mobile information terminal 20 notifies the vehicle 10 and the management server 30 of the start of digital key deletion (S102). In response to the notification, the management server 30 records log information indicating the start of deletion in the log management database 33 (S104).

[0030] Next, the mobile information terminal 20 deletes the common secret key SK stored in its secure element 27 (S106). Then, the mobile information terminal 20 notifies the vehicle 10 of the completion of the deletion of the common secret key SK (S108). In response to the notification, the vehicle 10 transmits log information indicating that the deletion of the common secret key SK of the mobile information terminal 20 has been completed to the management server 30 (S110). The management server 30 records the received log information in the log management database 33 (S112).

[0031] Next, the vehicle 10 deletes the common secret key SK stored in its HSM 14 (S114). Then, the vehicle 10 transmits log information indicating that the deletion of its own common secret key SK has been completed to the management server 30 (S116). The management server 30 records the received log information in the log management database 33 (S118). Information related to the deleted digital key is stored in the key trace database etc. of the management server 30. Some of such information becomes unnecessary in response to the suspension of use of the digital key. The management server 30 deletes the unnecessary information (S120).

[0032] In addition, the log information transmitted to the management server 30 in S12, S22, S42, S52 of FIG. 2 and S102, S110, S116 of FIG. 3 is attached with a digital key ID and a timestamp. Then, in S14, S24, S44, S54 of FIG. 2 and S104, S112, S118 of FIG. 3, the management server 30 records the log information in the log management database 33 together with the timestamp in a form associated with the digital key ID.

[0033] Incidentally, the specifications of the vehicle OEM app P3 may be the same as or different from those of the native app P1. For example, the specifications of the vehicle OEM app P3 may be such that when the vehicle 10 transmits log information to the management server 30, the log information is transmitted from the portable information terminal 20 to the management server 30.

[0034] <Actions and effects of the embodiment> The actions and effects of this embodiment will be described. The vehicle 10 of this embodiment can use the digital key registered in the user's portable information terminal 20. Also, in the case of this vehicle 10, registration and deletion of the digital key are performed using the native app P1 or the vehicle OEM app P3 installed in the portable information terminal 20.

[0035] During the process of registering and deleting the digital key, it is conceivable that the process may be interrupted for some reason. Even in such a case, if the log information of the registration and deletion process is recorded in the management server 30, it will be easy to identify the cause. The vehicle OEM app P3 is created by the provider of the digital key service. Therefore, the provider of the digital key service can design the vehicle OEM app P3 so that the management server 30 can collect sufficient log information.

[0036] In contrast, the native app P1 is created by the provider of the OS of the mobile information terminal 20. Therefore, when digital key registration / deletion processing is performed using the native app P1, there is a possibility that sufficient log information may not be transmitted from the mobile information terminal 20 to the management server 30. For example, in the case of this embodiment, in the registration process using the native app P1, log information is transmitted from the mobile information terminal 20 to the management server 30 only at the time of registration completion (Fig. 2: S52). Also, in the deletion process using the native app P1, log information is transmitted from the mobile information terminal 20 to the management server 30 only at the start of deletion (Fig. 3: S102).

[0037] In the vehicle 10 of this embodiment, when registering a digital key to the mobile information terminal 20, log information of events that occurred in the vehicle 10 is transmitted to the management server 30 of the digital key (Fig. 2: S12, S22, S42, S52, S58). The log information transmitted by the vehicle 10 to the management server 30 includes information indicating that key exchange between the mobile information terminal 20 and the vehicle 10 has been completed (S22, S42). Furthermore, even when deleting the digital key, the vehicle 10 transmits log information of events that occurred in the vehicle 10 to the management server 30.

[0038] The management server 30 includes a processor 32 and a data storage 31 that stores a log management database 33. The processor 32 of the management server 30 acquires log information of events that occurred in the vehicle 10 when registering or deleting a digital key from the vehicle 10 and records it in the data storage 31. Further, the processor 32 of the management server 30 also acquires log information of the processes performed on the portable information terminal 20 when registering or deleting a digital key from the portable information terminal 20 and records it in the data storage 31. Therefore, the log management database 33 aggregates the log information of the events that occurred in the vehicle 10 and the log information of the processes performed on the portable information terminal 20 when registering or deleting a digital key. Therefore, regardless of the specifications of the application used for registering or deleting a digital key, the log information of the registration or deletion process can be recorded in the log management database 33 of the management server 30.

[0039] According to the above-described embodiment, the following effects can be achieved. (1) The vehicle 10 of the present embodiment transmits log information of events that occurred in the vehicle 10 when registering a digital key to the portable information terminal 20 to the management server 30 for digital key management. Therefore, regardless of the specifications of the application of the portable information terminal 20 used for registering the digital key, the log information of the registration process can be recorded in the management server 30. Therefore, the vehicle 10 of the present embodiment has the effect of facilitating the diagnosis and analysis of the digital key registration process.

[0040] (2) In the digital key registration process, key exchange is performed between the vehicle 10 and the portable information terminal 20. The vehicle 10 of the present embodiment transmits information indicating that the key exchange with the portable information terminal 20 has been completed to the management server 30 as log information. When the registration process is interrupted, it is possible to confirm up to which stage the registration process has progressed by checking whether the log information of the key exchange completion is recorded in the log management database 33.

[0041] (3) When deleting the digital key, the vehicle 10 of this embodiment transmits the log information of the events that occurred in the vehicle 10 to the management server 30. Therefore, regardless of the specifications of the application of the portable information terminal 20 used for deleting the digital key, the log information of the deletion process can be recorded in the management server 30. Accordingly, the vehicle 10 of this embodiment has the effect of facilitating the diagnosis and analysis of the digital key deletion process.

[0042] (4) The processor 32 of the management server 30 of this embodiment acquires the log information of the events that occurred in the vehicle 10 when registering / deleting the digital key from the vehicle 10 and records it in the data storage 31. Also, the processor 32 acquires the log information of the processes performed on the portable information terminal 20 when registering / deleting the digital key from the portable information terminal 20 and records it in the data storage 31. Therefore, regardless of the specifications of the application of the portable information terminal 20 used for registering / deleting the digital key, the log information of the registration / deletion process can be recorded in the data storage 31 of the management server 30. Accordingly, the management server 30 of this embodiment has the effect of facilitating the diagnosis and analysis of the digital key registration / deletion process.

[0043] (5) The information management method of this embodiment is a method for managing information regarding the progress of registering / deleting the digital key of the vehicle 10 to the user's portable information terminal 20. In this method, the above information is stored in the data storage 31 of the management server 30, and the storage is performed by the processor 32 of the management server 30. And the processing of the processor 32 regarding the storage of information in the data storage 31 includes the step of acquiring and recording the log information of the events that occurred in the vehicle 10 when registering / deleting the digital key from the vehicle 10. In such an information management method, regardless of the specifications of the application of the portable information terminal 20 used for registering / deleting the digital key, the log information of the registration / deletion process can be recorded in the management server 30. Accordingly, the information management method of this embodiment has the effect of facilitating the diagnosis and analysis of the digital key registration / deletion process.

[0044] (6) In the information management method of this embodiment, the processing of the processor 32 regarding the storage of information in the data storage 31 includes the step of acquiring and recording the log information of the processing performed by the portable information terminal 20 when registering and deleting the digital key from the portable information terminal 20. In such an information management method, the log information of the registration / deletion processing is acquired from both the vehicle 10 and the portable information terminal 20. The diagnosis and analysis of the registration / deletion processing of the digital key can be performed more easily than when acquiring the log information only from the vehicle 10.

[0045] <Other Embodiments> This embodiment can be implemented with the following modifications. This embodiment and the following modification examples can be implemented in combination with each other within a technically non - conflicting range.

[0046] · The registration / deletion processing of the digital key may be performed according to procedures different from those in FIGS. 2 and 3. · When registering and deleting the digital key, the transmission of log information from the vehicle 10 to the management server 30 and the transmission of log information from the portable information terminal 20 to the management server 30 may be performed at times different from those in FIGS. 2 and 3. Also, when registering and deleting the digital key, the portable information terminal 20 may not transmit log information to the management server 30. In that case, the management server 30 acquires log information only from the vehicle 10 among the portable information terminal 20 and the vehicle 10 and records it in the log management database 33.

[0047] · Among the registration processing and deletion processing of the digital key, the transmission of log information from the vehicle 10 to the management server 30 may be performed only in the registration processing. · The hardware configurations of the vehicle 10, the portable information terminal 20, and the management server 30 may be different from those in FIG. 1.

[0048] <Supplementary Notes> [Appendix 1] A vehicle that can use a digital key registered on a user's mobile information terminal, and transmits log information of events that occurred in the vehicle to the digital key management server when registering the digital key on the mobile information terminal.

[0049] [Appendix 2] The vehicle according to Appendix 1, which transmits information indicating that the key exchange with the mobile information terminal has been completed to the management server as the log information. [Appendix 3] The vehicle according to Appendix 1 or Appendix 2, which transmits log information of events that occurred in the vehicle to the management server when deleting the digital key.

Explanation of Reference Numerals

[0050] 10 Vehicle 11 Digital Key ECU 12 Processor 13 Memory Module 14 HSM 15 TCU 16 Communication Module for BLE Communication 17 Communication Module for UWB Communication 18 Communication Module for NFC 20 Mobile Information Terminal 21 Communication Module for BLE Communication 22 Communication Module for UWB Communication 23 Communication Module for NFC 24 Communication Module for Cellular Communication 25 Memory Module 26 Processor 27 Secure Element 30 Management Server 31 Data Storage 32 Processor 33 Log Management Database P1 Native App P2 Digital Key Framework P3 Vehicle OEM App

Claims

1. A vehicle that can use a digital key registered in a user's portable information terminal, wherein when registering the digital key in the portable information terminal, log information of an event that occurred in the vehicle is transmitted to a management server of the digital key. Vehicle.

2. The vehicle according to claim 1, wherein information indicating that key exchange with the portable information terminal has been completed is transmitted to the management server as the log information.

3. The vehicle according to claim 1, wherein when deleting the digital key, log information of an event that occurred in the vehicle is transmitted to the management server.

4. An information management device that manages information regarding the progress of registration of a vehicle digital key in a user's portable information terminal, comprising a processor and a data storage, wherein the processor obtains log information of an event that occurred in the vehicle when registering the digital key from the vehicle and records it in the data storage, and obtains log information of a process performed on the portable information terminal when registering the digital key from the portable information terminal and records it in the data storage. Information management device.

5. An information management method for managing information regarding the progress of registration of a vehicle digital key in a user's portable information terminal, wherein the information is stored in a data storage, the storage of the information in the data storage is performed by a processor, and the processing of the processor related to the storage of the information in the data storage includes a step of obtaining and recording log information of an event that occurred in the vehicle when registering the digital key from the vehicle. Information management method.

6. The information management method according to claim 5, wherein the processing of the processor related to the storage of the information in the data storage includes a step of obtaining and recording log information of a process performed on the portable information terminal when registering the digital key from the portable information terminal.

Images