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 a portable information terminal using an application program installed in the portable information terminal.

Prior Art Documents

Patent Documents

[0003] [[ID=2?3]]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] Due to 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 necessary 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] A vehicle that solves the above problem is a vehicle that can use a digital key registered on the user's mobile device, and is configured to send log information of events that occurred in the vehicle when the digital key was registered on the mobile device to the digital key management server.

[0007] An information management device that solves the above problems is an information management device that manages information regarding the progress of registering a vehicle's digital key to a user's mobile information terminal, and comprises a processor and data storage, wherein the processor is configured to acquire log information of events that occurred in the vehicle when the digital key is registered and record it in the data storage, and to acquire log information of processes performed on the mobile information terminal when the digital key is registered and record it in the data storage.

[0008] An information management method that solves the above problem is an information management method for managing information regarding the progress of registering a vehicle's digital key to a user's mobile information terminal, wherein the information is stored in data storage, the storage of the information in the data storage is performed by a processor, and the processor's processing related to the storage of the information in the data storage includes the step of obtaining and recording log information of events that occurred in the vehicle when the digital key was registered. [Effects of the Invention]

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

[0010] [Figure 1] This diagram schematically shows the configuration of one embodiment of a vehicle and information management device. [Figure 2] This is a sequence diagram of the digital key registration process. [Figure 3] This is a sequence diagram of the digital key deletion process. [Modes for carrying out the invention]

[0011] Hereinafter, one embodiment of a vehicle, an information management device, and an information management method will be described in detail with reference to Figures 1 to 3. <Vehicle and Information Management System Configuration> First, the configuration of the vehicle 10 and the information management device of this embodiment will be described. The vehicle 10 of this embodiment can utilize a digital key. The digital key is a system that uses a mobile information terminal 20 such as a smartphone owned by the user to lock, unlock, and start the vehicle, instead of a physical key. The information management device is a device that manages information related to the digital key and is operated by the provider of the digital key service. The digital key used by the vehicle 10 of this embodiment conforms to 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) that performs processing related to the digital key. 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. Furthermore, the digital key ECU 11 is equipped with an HSM (Hardware Security Module) 14 that generates and stores encryption keys, and performs encryption and digital signatures using the encryption keys. Furthermore, vehicle 10 is equipped with a TCU (Telematics Control Unit) 15 for communicating with a management server 30 using mobile communication. Furthermore, vehicle 10 is equipped with communication modules 16 to 18 that support BLE (Bluetooth Low Energy) communication, UWB (Ultra-Wide Band) communication, and NFC (Near Field Communication), respectively. Vehicle 10 communicates with the user's mobile information terminal 20 via BLE communication, UWB communication, and NFC.

[0013] The personal information terminal 20 is equipped with communication modules 21-23 for BLE communication, UWB communication, and NFC for communication with the vehicle 10. The personal information terminal 20 is also equipped with a communication module 24 for cellular communication for communication with the management server 30 using mobile communication. Furthermore, the personal information terminal 20 is equipped with a memory module 25, a processor 26, and a secure element 27. The processor 26 reads and executes programs stored in the memory module 25. The secure element 27 is a semiconductor device equipped with damper-resistant memory and cryptographic logic circuitry.

[0014] The memory module 25 of the personal digital assistant (PDTA) 20 pre-stores the native app P1 and the digital key framework P2. The native app P1 is an application program that provides a user interface (UI) for creating, ending, deleting, enabling, and disabling digital keys. The digital key framework P2 is a program that uses the API (Application Programming Interface) provided by the OS to provide functions such as owner pairing, digital key sharing, and management. Owner pairing is the process of downloading digital key information to the PDTA 20, linking the vehicle 10 with the PDTA 20, and registering the digital key with the vehicle 10. The native app P1 and the digital key framework P2 are created by the provider of the PDTA 20's operating system (OS) and are pre-installed on the PDTA 20.

[0015] The provider of the digital key service offers a vehicle OEM app P3, which is an application program that provides similar functionality to the native app P1. The vehicle OEM app P3 is optionally installed on the personal digital assistant (PDTA) 20. The digital key can be registered to the PDTA 20 using either the native app P1 or the vehicle OEM app P3.

[0016] The management server 30 is a server device operated by the provider of the digital key service. The management server 30 comprises a processor 32 and data storage 31. The management server 30 provides various functions related to the digital key service by having the processor 32 execute programs stored in the data storage 31. Examples of functions provided by the management server 30 include vehicle 10 and user information management, 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 of digital key registration / deletion processes. The data storage 31 also stores a vehicle database that records vehicle 10 information, a user database that records user information, and a key trace database that records the usage history of digital keys. In this embodiment, the management server 30 corresponds to an information management device.

[0017] <Digital key registration process> Next, the digital key registration process will be explained with reference to Figure 2. Digital key registration is performed using either the native application P1 or the vehicle OEM application P3 installed on the mobile information terminal 20. Here, the case using the native application P1 will be explained. Figure 2 shows the processing procedures for the vehicle 10, the mobile information terminal 20, and the management server 30 when registering a digital key using the native application P1. The processing for the vehicle 10 shown in Figure 2 and Figure 3 described later is executed by the processor 12 of the digital key ECU 11. The processing for the management server 30 shown in Figure 2 and Figure 3 described later is executed by the processor 32 of the 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 digital key ID and password are generated by the management server 30 in response to a digital key registration application from the mobile information terminal 20 by the user and issued 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 the public temporary key PK1 and the secret temporary key SK1 (S16). Similarly, the vehicle 10 also generates a key pair of the public temporary key PK2 and the secret temporary key SK2 after the pairing is completed (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 public key PK3 and private key SK3, and the vehicle 10 generates a key pair of public key PK4 and private key SK4, respectively (S30, 32). Then, the mobile information terminal 20 and the vehicle 10 perform a key exchange of the public keys PK3 and PK4 (S34). The mobile information terminal 20 and the vehicle 10 use the public keys PK3 and PK4 exchanged here as data for mutual authentication. At the time of 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 and SIG2 attached to the public keys PK3 and 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 and 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 and 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 and 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 and PK4 used as data for mutual authentication is completed. When the vehicle 10 confirms the completion of the verification of the electronic signatures SIG1 and 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] Subsequently, the personal information terminal 20 generates a shared secret key SK using the public key PK4 received from the vehicle 10 and its own private key SK3 (S46). Vehicle 10 also generates a shared secret key SK using the public key PK3 received from the personal information terminal 20 and its own private key SK4 (S48). The personal information terminal 20 and vehicle 10 confirm the completion of the generation of the shared secret key SK in each other by notifying each other of the completion of the generation of the shared secret key SK (S50). The personal information terminal 20 stores the shared secret key SK in the secure element 27. Vehicle 10 also stores the shared secret key SK in the HSM 14. The shared secret key SK stored in the personal information terminal 20 and vehicle 10 in this way are used for mutual authentication between vehicle 10 and personal information terminal 20 when using the digital key.

[0026] When the portable information terminal 20 confirms that the generation of the common secret key SK is complete for both itself and the vehicle 10, it sends log information indicating the completion of digital key registration to the management server 30 (S52). The management server 30 records the received log information in the log management database 33 (S54). The management server 30 also 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). The management server 30 then notifies the portable information terminal 20 that it has confirmed the completion of digital key registration (S58).

[0027] Meanwhile, once the portable information terminal 20 and the vehicle 10 confirm that the generation of their respective shared secret key SK is complete, they temporarily disconnect their pairing (S60). Then, the portable information terminal 20 and the vehicle 10 perform mutual authentication using the shared secret key SK and resume pairing (S62). Subsequently, the portable information terminal 20 and the vehicle 10 activate the digital key after both the resumption of pairing and notification of registration completion from the management server 30 have been received (S64). Activating the digital key makes it possible to lock, unlock, and start the vehicle 10 using the portable information terminal 20.

[0028] <Deletion process for digital keys> Next, the digital key deletion process will be explained with reference to Figure 3. Similar to registration, digital key deletion is performed using either the native application P1 or the vehicle OEM application P3 installed on the mobile device 20. Here, we will explain the process using the native application P1. Figure 3 shows the processing steps for the vehicle 10, mobile device 20, and management server 30 when deleting a digital key using the native application P1.

[0029] In the deletion process, the mobile information terminal 20 and the vehicle 10 are first paired using either LE communication, UWB communication, or NFC (S100). This pairing is performed using the common secret key SK generated during registration. Once pairing is complete, the mobile information terminal 20 notifies the vehicle 10 and the management server 30 that the deletion of the digital key has begun (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 personal information terminal 20 deletes the common secret key SK stored in its secure element 27 (S106). Then, the personal information terminal 20 notifies the vehicle 10 that the deletion of the common secret key SK is complete (S108). In response to the notification, the vehicle 10 sends log information to the management server 30 indicating that the deletion of the common secret key SK by the personal information terminal 20 is complete (S110). The management server 30 records the received log information in the log management database 33 (S112).

[0031] Next, vehicle 10 deletes the shared secret key SK stored in its HSM14 (S114). Then, vehicle 10 sends log information to the management server 30 indicating that the deletion of its shared secret key SK is complete (S116). The management server 30 records the received log information in the log management database 33 (S118). The key trace database of the management server 30 stores information related to the deleted digital key. Some of this information becomes unnecessary when the use of the digital key is discontinued. The management server 30 deletes the information that is no longer needed (S120).

[0032] In addition, the log information sent to the management server 30 in steps S12, S22, S42, and S52 in Figure 2, and in steps S102, S110, and S116 in Figure 3, includes a digital key ID and a timestamp. Then, in steps S14, S24, S44, and S54 in Figure 2, and in steps S104, S112, and S118 in Figure 3, the management server 30 records the log information, along with the timestamp, in the log management database 33, linked to 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 the mobile information terminal 20 sends log information to the management server 30 at the same time that the vehicle 10 sends log information to the management server 30.

[0034] <Effects and Effects of the Embodiment> The operation and effects of this embodiment will now be described. In this embodiment, the vehicle 10 can utilize a digital key registered on the user's mobile device 20. In this vehicle 10, the registration and deletion of the digital key are performed using the native application P1 or the vehicle OEM application P3 installed on the mobile device 20.

[0035] During the registration and deletion of digital keys, the process may be interrupted for some reason. In such cases, if log information of the registration and deletion process is recorded on the management server 30, it will be easier to identify the cause. The vehicle OEM application P3 is created by the provider of the digital key service. Therefore, the provider of the digital key service can design the vehicle OEM application P3 so that the management server 30 can collect sufficient log information.

[0036] In contrast, the native application P1 is created by the provider of the OS for the personal digital assistant (PDTA) 20. Therefore, when the registration and deletion of a digital key is performed using the native application P1, there is a possibility that sufficient log information may not be sent from the PDTA 20 to the management server 30. For example, in this embodiment, during the registration process using the native application P1, log information is sent from the PDTA 20 to the management server 30 only when the registration is completed (Figure 2: S52). Also, during the deletion process using the native application P1, log information is sent from the PDTA 20 to the management server 30 only when the deletion process begins (Figure 3: S102).

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

[0038] The management server 30 comprises 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 digital keys and records it in the data storage 31. The processor 32 of the management server 30 also acquires log information of processes performed on the mobile information terminal 20 when registering or deleting digital keys and records it in the data storage 31. Therefore, the log management database 33 aggregates log information of events that occurred in the vehicle 10 when registering or deleting digital keys and log information of processes performed on the mobile information terminal 20. As a result, log information of registration and deletion processes can be recorded in the log management database 33 of the management server 30 regardless of the specifications of the application used for registering and deleting digital keys.

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

[0040] (2) During the digital key registration process, a key exchange takes place between the vehicle 10 and the portable information terminal 20. In this embodiment, the vehicle 10 sends information to the management server 30 as log information indicating that the key exchange with the portable information terminal 20 has been completed. If the registration process is interrupted, the stage at which the registration process had progressed can be determined by checking whether or not log information indicating the completion of the key exchange has been recorded in the log management database 33.

[0041] (3) In this embodiment, the vehicle 10 transmits log information of events that occurred in the vehicle 10 when the digital key is deleted to the management server 30. Therefore, regardless of the specifications of the application on the mobile information terminal 20 used to delete the digital key, log information of the deletion process can be recorded on the management server 30. Thus, the vehicle 10 in this embodiment has the effect of making it easier to diagnose and analyze the digital key deletion process.

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

[0043] (5) The information management method of this embodiment is a method for managing information regarding the progress of registering and deleting the digital key of the vehicle 10 to the user's mobile 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. The processing of the processor 32 regarding the storage of information in the data storage 31 includes a step of acquiring and recording log information of events that occurred in the vehicle 10 when the digital key was registered or deleted from the vehicle 10. With this information management method, log information of the registration and deletion process can be recorded in the management server 30 regardless of the specifications of the application on the mobile information terminal 20 used for registering and deleting the digital key. Therefore, the information management method of this embodiment has the effect of facilitating the diagnosis and analysis of the digital key registration and deletion process.

[0044] (6) In the information management method of this embodiment, the processing of the processor 32 related to storing information in the data storage 31 includes a step of acquiring and recording log information of the processing performed on the portable information terminal 20 when registering or deleting a digital key from the portable information terminal 20. In this information management method, log information of the registration and deletion process is acquired from both the vehicle 10 and the portable information terminal 20. This makes it easier to diagnose and analyze the digital key registration and deletion process than when log information is acquired only from the vehicle 10.

[0045] <Other Embodiments> This embodiment can be implemented with the following modifications. This embodiment and the following modifications can be combined with each other to the extent that they do not contradict each other technically.

[0046] The registration and deletion of digital keys may be performed using a different procedure than that shown in Figures 2 and 3. When registering or deleting a digital key, the transmission of log information from the vehicle 10 to the management server 30 and from the mobile information terminal 20 to the management server 30 may be performed at different times than those shown in Figures 2 and 3. Alternatively, when registering or deleting a digital key, the mobile information terminal 20 may not transmit log information to the management server 30. In this case, the management server 30 will acquire log information only from the vehicle 10 and record it in the log management database 33.

[0047] - Of the digital key registration and deletion processes, log information may be sent from the vehicle 10 to the management server 30 only during the registration process. The hardware configuration of the vehicle 10, the mobile information terminal 20, and the management server 30 may differ from that shown in Figure 1.

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

[0049] [Note 2] The vehicle described in Note 1, which transmits information indicating that the key exchange with the portable information terminal has been completed to the management server as log information. [Note 3] The vehicle described in Note 1 or Note 2 that sends log information of events that occurred in the vehicle when the digital key was deleted to the management server. [Explanation of Symbols]

[0050] 10 vehicles 11 Digital Key ECU 12 processors 13 Memory Modules 14 HSM 15 TCU 16. Communication module for BLE communication 17. Communication module for UWB communication 18. Communication module for NFC 20 Mobile Information Terminals 21. Communication module for BLE communication 22 Communication modules for UWB communication 23 Communication module for NFC 24. Communication module for cellular communication. 25 memory modules 26 processors 27 Secure Elements 30 Management Server 31 Data Storage 32 processors 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 on the user's mobile device, When registering the digital key to the aforementioned mobile information terminal, log information of events that occurred in the vehicle is transmitted to the digital key management server. vehicle.

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

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

4. An information management device that manages information regarding the progress of registering a vehicle's digital key to a user's mobile device, It has a processor and data storage, The aforementioned processor, The process involves obtaining log information of events that occurred in the vehicle during the registration of the digital key and recording it in the data storage. Log information of the process performed on the mobile device during the registration of the digital key is obtained from the mobile device and recorded in the data storage. An information management device that performs this function.

5. An information management method for managing information regarding the progress of registering a vehicle's digital key to a user's mobile device, The aforementioned information is stored in data storage. The storage of the information in the data storage is performed by the processor. The processor's processing for storing the information in the data storage includes the step of obtaining and recording log information of events that occurred in the vehicle when the digital key was registered. Information management method.

6. The information management method according to claim 5, wherein the processor's processing for storing the information in the data storage includes the step of acquiring and recording log information of the processing performed on the mobile information terminal when registering the digital key from the mobile information terminal.

Images