System, management server, vehicle management apparatus, management method, and program

Abstract

A management system (10) comprises an inquiry unit (70CD) and an execution unit (70RA). When a third digital key is newly registered by a second device to which a second digital key has been registered on the basis of a request from a first device to which a first digital key has been registered, the inquiry unit (70CD) is configured to query the first device whether or not to accept registration of the third digital key. The execution unit (70RA) is configured to execute registration processing of the third digital key when acceptance information has been received, and not to execute the registration processing when the acceptance information is not received.

Description

System, management server, vehicle management device, management method, and program

[0001] The present disclosure relates to a system, a management server, a vehicle management device, a management method, and a program.

[0002] Patent Document 1 describes a digital key management system. The management system includes a vehicle, an owner device, a shared device, and a management server. The owner device registers an owner key. An owner key is a digital key that can only exist once per vehicle. The shared device registers a shared key based on a registration request from the owner device. A single vehicle can have multiple shared keys.

[0003] The management server manages multiple digital keys. When a vehicle uses a digital key, it authenticates the digital key and allows it to unlock the vehicle and perform other controls.

[0004] JP 2024-001720 A

[0005] In a management system such as that described in Patent Document 1, it is desirable to be able to register multiple digital keys to multiple devices as freely as possible under appropriate restrictions.

[0006] In a first aspect of the present disclosure, a system is a system for managing a plurality of digital keys that can be used for a vehicle, the plurality of digital keys including a first digital key registered in a first device, a second digital key registered in a second device based on a request from the first device, and a third digital key, and is equipped with an inquiry unit configured to, when the second device newly registers the third digital key, inquire of the first device as to whether or not to agree to the registration of the third digital key, and an execution unit configured to execute a registration process for the third digital key if consent information indicating consent to the registration of the third digital key is received, and not execute the registration process if the consent information is not received.

[0007] In a second aspect of the present disclosure, a management server manages a plurality of digital keys available for a vehicle, the plurality of digital keys including a first digital key registered in a first device, a second digital key registered in a second device based on a request from the first device, and a third digital key, and is equipped with an inquiry unit configured to inquire of the first device whether or not to accept the registration of the third digital key when the second device newly registers the third digital key, and an execution unit configured to execute a registration process for the third digital key if acceptance information indicating acceptance of the registration of the third digital key is received, and not execute the registration process if the acceptance information is not received.

[0008] In a third aspect of the present disclosure, a vehicle management device is a vehicle management device that manages multiple digital keys that can be used for a vehicle, wherein the multiple digital keys include a first digital key registered in a first device, a second digital key registered in a second device based on a request from the first device, and a third digital key, and is equipped with an inquiry unit configured to, when the second device newly registers the third digital key, inquire of the first device as to whether or not to agree to the registration of the third digital key, and an execution unit configured to execute a registration process for the third digital key if acceptance information indicating acceptance of the registration of the third digital key is received, and not execute the registration process if the acceptance information is not received.

[0009] In a fourth aspect of the present disclosure, a management method is performed by a system configured to manage a plurality of digital keys available for a vehicle, wherein the plurality of digital keys include a first digital key registered in a first device, a second digital key registered in a second device based on a request from the first device, and a third digital key, and the management method includes, when the second device newly registers the third digital key, inquiring of the first device as to whether or not to accept the registration of the third digital key, performing registration processing of the third digital key if acceptance information indicating acceptance of the registration of the third digital key is received, and not performing the registration processing if the acceptance information is not received.

[0010] In a fifth aspect of the present disclosure, the program is a program to be executed by a computer configured to manage multiple digital keys available for a vehicle, the multiple digital keys including a first digital key registered in a first device, a second digital key registered in a second device based on a request from the first device, and a third digital key, and is configured to cause the computer to, when the second device newly registers the third digital key, inquire of the first device as to whether or not to agree to the registration of the third digital key, and to execute registration processing for the third digital key if the second device receives agreement information indicating agreement to the registration of the third digital key, and not to execute the registration processing if the computer does not receive the agreement information.

[0011] FIG. 1 is a schematic diagram showing a management system of a first embodiment. FIG. 2 is a schematic diagram showing owner key information of an owner device of FIG. 1. FIG. 3 is a schematic diagram showing share key information of a share device of FIG. 1. FIG. 4 is a schematic diagram showing data in the database of FIG. 1. FIG. 5 is an explanatory diagram showing a series of processes performed by the management system of FIG. 1 when an owner key is registered. FIG. 6 is an explanatory diagram showing a series of processes performed by the management system of FIG. 1 when a friend key is registered. FIG. 7 is an explanatory diagram showing a series of processes performed by the management system of FIG. 1 when a non-friend key is registered. FIG. 8 is an explanatory diagram showing a series of processes performed by the management system of FIG. 1 when a non-friend key is deleted in response to a request from a friend device. FIG. 9 is an explanatory diagram showing a series of processes performed by the management system of FIG. 1 when a non-friend key is deleted in response to a request from a non-friend device. FIG. 10 is a schematic diagram showing an inquiry unit and an execution unit in the management system of FIG. 1. FIG. 11 is a flowchart showing a series of processes performed by the inquiry unit and the execution unit of FIG. 10. FIG. 12 is a schematic diagram showing a vehicle of a second embodiment. FIG. 13 is a schematic diagram showing an inquiry unit and an execution unit in a management system of a second embodiment. FIG. 14 is a flowchart showing a series of processes performed by the inquiry unit and the execution unit of FIG. 13. FIG. 15 is a schematic diagram showing a non-friend device of a third embodiment. FIG. 16 is a schematic diagram showing an inquiry unit and an execution unit in a management system of the third embodiment. FIG. 17 is a flowchart showing a series of processes performed by the inquiry unit and the execution unit of FIG. 16. FIG. 18 is a schematic diagram showing a friend device of a fourth embodiment. FIG. 19 is a schematic diagram showing an inquiry unit and an execution unit in a management system of the fourth embodiment. FIG. 20 is a flowchart showing a series of processes performed by the inquiry unit and the execution unit of FIG. 19.

[0012] First Embodiment A management system 10 according to a first embodiment will be described below with reference to the drawings. <Overview of the Management System> As shown in FIG. 1 , the management system 10 manages a plurality of digital keys that can be used for a vehicle 20. In this embodiment, the management system 10 is a system. Regarding digital keys, there is a standard established by the Car Connectivity Consortium (CCC). Matters relating to the digital keys in this embodiment comply with the CCC. The management system 10 includes a vehicle 20, a plurality of devices 30, a device server 60, and a management server 70.

[0013] The vehicle 20 includes a communication module 21, an HMI 22, a BLE module 23, a UWB module 24, an NFC module 25, and a vehicle management device 26. HMI stands for Human Machine Interface. BLE stands for Bluetooth Low Energy. UWB stands for Ultra Wide Band. NFC stands for Near Field Communication.

[0014] The communication module 21 communicates with the management server 70 via a wireless communication network. The HMI 22 includes an input device that accepts operations by the user of the vehicle 20 and a presentation device that presents information to the user using images, audio, etc. The presentation device is, for example, a monitor and a speaker.

[0015] The BLE module 23 performs short-range wireless communication with the device 30 via BLE communication. The UWB module 24 communicates with the device 30 via UWB communication. The UWB module 24 measures the distance between the device 30 and the vehicle 20. The NFC module 25 performs short-range wireless communication with the device 30 via NFC communication.

[0016] The vehicle management device 26 is mounted on the vehicle 20. The vehicle management device 26 manages the digital key of the vehicle 20. The vehicle management device 26 is, for example, a digital key ECU. The vehicle management device 26 has an execution device 27, which is a processing circuit, and a storage device 28. The storage device 28 stores a vehicle program PV and authentication information AT. The execution device 27 executes the vehicle program PV, causing the execution device 27 to store and delete the authentication information AT. The authentication information AT is information for authenticating the digital key so that the vehicle 20 can be controlled using the digital key when the digital key is used. The authentication information AT is provided for each digital key to be authenticated. The execution device 27 is a CPU. The execution device 27 executes the vehicle program PV to perform processes related to the storage and deletion of the authentication information AT.

[0017] When the vehicle management device 26 authenticates the digital key, the vehicle management device 26 allows the digital key to be used to control the vehicle 20. For example, when the vehicle management device 26 authenticates the digital key, the vehicle management device 26 allows the vehicle 20 to be unlocked. For example, when the vehicle management device 26 authenticates the digital key, the vehicle management device 26 allows the vehicle 20 to be started.

[0018] The device 30 is a mobile information terminal such as a smartphone, and includes a communication module 31, an HMI 32, a BLE module 33, a UWB module 34, an NFC module 35, an execution unit 36 ​​which is a processing circuit, and a storage unit 37.

[0019] The communication module 31 communicates with the device server 60 via a wireless communication line. The HMI 32 includes an input device that accepts operations by the user of the device 30, and a presentation device that presents information to the user using images, audio, etc. The presentation device is, for example, a monitor and a speaker.

[0020] The BLE module 33 performs short-range wireless communication with the vehicle 20 using BLE communication. The UWB module 34 communicates with the vehicle 20 using UWB communication. The NFC module 35 performs short-range wireless communication with the vehicle 20 using NFC communication.

[0021] The storage device 37 stores a device program PD and key information DK. The device program PD is executed by the execution device 36, causing the execution device 36 to store and delete the key information DK. The key information DK is information indicating a digital key.

[0022] The device program PD includes, for example, a device application and a digital key framework. The device application is an application for storing and deleting key information DK. The digital key framework is a program that provides functions for pairing devices 30 and sharing digital keys using APIs provided by the OS. The execution unit 36 ​​executes the device program PD to perform processes related to storing and deleting key information DK.

[0023] The multiple devices 30 include an owner device 40 and multiple shared devices 50. The owner device 40 stores owner key information DKO indicating an owner key KO as key information DK. Only one owner key KO can be registered to one vehicle 20. Therefore, only one owner key KO exists for one vehicle 20.

[0024] 2, the owner key information DKO includes owner key structure information STO. The owner key structure information STO includes vehicle identification information ST1, in-device key identification information ST2, digital key identification information ST3, and slot identification information ST4. The owner key structure information STO also includes certificate information ST5, device public key information ST6, vehicle public key information ST7, and permission public key information ST8.

[0025] The vehicle identification information ST1 is information for identifying the vehicle 20 for which the digital key is to be set. For example, it is the ID of the vehicle 20. The in-device key identification information ST2 is used for managing the digital key within the device 30. The in-device key identification information ST2 is information that can identify the digital key within the application of the device 30.

[0026] The digital key identification information ST3 is used for managing the digital key in the management server 70. The slot identification information ST4 is information that can identify the digital key locally on the device 30.

[0027] Certificate information ST5 indicates a certificate that certifies the digital key. Device public key information ST6 indicates a device public key PKD that is the public key of the device 30. The device public key PKD in the owner key information DKO indicates the public key of the owner device 40. Vehicle public key information ST7 indicates a vehicle public key PKV that is the public key of the vehicle 20. Authorization public key information ST8 indicates an already authorized vehicle public key PKV.

[0028] 1, the share device 50 stores share key information DKS indicating a share key KS as key information DK. A share key KS is a digital key that can be registered in multiple numbers for one vehicle 20 in order to enable the use of the digital key. In other words, multiple share keys KS can exist for one vehicle 20.

[0029] The multiple share devices 50 include a friend device 51 and a non-friend device 52. The friend device 51 stores, as the share key information DKS, friend key information DKF indicating the friend key KF. The non-friend device 52 stores, as the share key information DKS, non-friend key information DKN indicating the non-friend key KN. In other words, the types of share keys KS include a friend key KF and a non-friend key KN. The friend key KF is a share key KS registered based on a direct registration request D21 from the owner device 40, as described below. The non-friend key KN is a share key KS registered based on a registration request D31 from the friend device 51, as described below. In other words, the non-friend key KN is a share key KS registered based on an indirect registration request from a share device 50, which is a device 30 different from the owner device 40.

[0030] When a digital key is registered, the digital key is enabled for use, i.e., when the digital key is registered, the vehicle 20 stores the authentication information AT and the device 30 stores the key information DK.

[0031] As shown in Fig. 3, the shared key information DKS includes shared key structure information STS and an authentication package ATP. The shared key structure information STS includes vehicle identification information ST1, in-device key identification information ST2, digital key identification information ST3, and slot identification information ST4. The shared key structure information STS also includes certificate information ST5, vehicle public key information ST7, and permission public key information ST8. In other words, the shared key structure information STS is the owner key structure information STO minus the device public key information ST6.

[0032] The authentication package ATP includes signature information ATP1, password information ATP2, validity start time information ATP3, expiration date information ATP4, name information ATP5, and device public key information ATP6.

[0033] The signature information ATP1 indicates that the sharing device 50 is a legitimate target for sharing a digital key. For example, in the case of the friend device 51, the signature information ATP1 indicates a signature by the owner device 40. The signature information ATP1 in the case of the friend device 51 indicates that the owner device 40 has signed the device public key PKD of the friend device 51 indicated by the device public key information ATP6. For example, in the case of the non-friend device 52, the signature information ATP1 indicates a signature by the friend device 51. The signature information ATP1 in the case of the non-friend device 52 indicates that the friend device 51 has signed the device public key PKD of the non-friend device 52 indicated by the device public key information ATP6.

[0034] The password information ATP2 indicates the pairing password PAS used to establish a secure channel when pairing the vehicle 20 and the owner device 40. The validity start time information ATP3 indicates the earliest date and time at which the shared key KS can be used. The expiration date information ATP4 indicates the latest date and time at which the shared key KS can be used. The name information ATP5 indicates a name that identifies the shared key KS. The name information ATP5 is set to an identifiable name for each shared device 50, for example, by operation from the owner device 40.

[0035] As shown in FIG. 1 , the device server 60 relays communication between the devices 30 and the management server 70. Only one device server 60 is illustrated in FIG. 1 . However, a device server 60 may be provided for each type of device 30. That is, the device server 60 with which a first type of device 30 communicates may be different from the device server 60 with which a second type of device 30 communicates. For example, the type refers to the model of the device 30, and a device server 60 is provided for each model of the device 30. For example, the type refers to the communication line used by the device 30, and a device server 60 is provided for each communication line used by the device 30.

[0036] Each device server 60 relays communication between the corresponding device 30 and the management server 70. Different types of devices 30 can communicate with the management server 70 via the corresponding device server 60.

[0037] <Management Server> The management server 70 is configured to manage digital keys. The management server 70 is capable of communicating with the vehicle 20 and multiple devices 30. The management server 70 includes an execution device 71, which is a processing circuit, a storage device 72, and a communication module 73. The communication module 73 communicates with the device server 60 via a wireless communication line. The communication module 73 is also capable of wireless communication with the communication module 21 of the vehicle 20.

[0038] The storage device 72 stores a server program PS, a consent program PCA, and a database DB. The server program PS, when executed by the execution device 71, causes the execution device 71 to register and delete digital keys in the database DB. Details of the consent program PCA will be described later.

[0039] The database DB contains information associating, for each of a plurality of digital keys, the corresponding vehicle 20 with the registered device 30. The data DA contained in the database DB is separated for each vehicle 20. When a digital key is registered, the management server 70 stores, in the data DA, information indicating the device 30 that stores the key information DK indicating the digital key.

[0040] As shown in Figure 4, the data DA for one vehicle 20 includes information about the type of digital key registered to the vehicle 20, the registered devices 30, and the relationships between the registered devices 30. Digital keys are divided into multiple hierarchies based on their type. From top to bottom, the hierarchy is divided into owner keys KO, friend keys KF, and non-friend keys KN. The higher the hierarchy, the greater the authority set for the digital key.

[0041] The authority may be, for example, the number of share keys KS that can be requested to be registered, the range of control of the vehicle 20 that can be achieved by authenticating the digital key, etc. The higher the hierarchical level of the digital key, the greater the number of share keys KS that can be requested to be registered. More specifically, for example, the number of friend keys KF that the owner device 40 can request to be registered is greater than the number of non-friend keys KN that the friend device 51 can request to be registered.

[0042] For example, the higher the hierarchical level of a digital key, the wider the controllable range of the vehicle 20. The controllable range of the vehicle 20 indicates, for example, the possible controls among control of starting the engine of the vehicle 20, control of turning on the power of the vehicle 20, and control of unlocking and locking the doors of the vehicle 20. For example, if the controllable range of the vehicle 20 includes the above-mentioned three controls, the controllable range of the vehicle 20 is wider than if the controllable range of the vehicle 20 is only control of unlocking and locking the doors of the vehicle 20. More specifically, the controllable range of the vehicle 20 that can be controlled by the friend key KF is the above-mentioned three controls, while the controllable range of the vehicle 20 that can be controlled by the non-friend key KN is only control of unlocking and locking the doors of the vehicle 20.

[0043] A state will be described in which digital keys are registered to seven devices 30 for one vehicle 20. The seven devices 30 are a first device 30A to a seventh device 30G. The digital keys registered in the first device 30A to the seventh device 30G are a first digital key to a seventh digital key, respectively. This information is included in the data DA.

[0044] The device 30 in which the owner key KO is registered as a digital key is the first device 30A. That is, the first device 30A is the owner device 40. That is, the first digital key is the owner key KO.

[0045] The devices 30 in which the shared key KS is registered as a digital key are the second device 30B, the third device 30C, the fourth device 30D, the fifth device 30E, the sixth device 30F, and the seventh device 30G. That is, the second device 30B, the third device 30C, the fourth device 30D, the fifth device 30E, the sixth device 30F, and the seventh device 30G are shared devices 50. That is, the second digital key to the seventh digital key are all shared keys KS.

[0046] More specifically, the devices 30 in which the friend key KF is registered as the share key KS are the second device 30B and the fifth device 30E. That is, the second device 30B and the fifth device 30E are friend devices 51. The devices 30 in which the non-friend key KN is registered as the share key KS are the third device 30C, the fourth device 30D, the sixth device 30F, and the seventh device 30G. That is, the third device 30C, the fourth device 30D, the sixth device 30F, and the seventh device 30G are non-friend devices 52.

[0047] The relationship between the registered devices 30 contained in the data DA will be described. The relationship between the second device 30B and the first device 30A is such that the friend key KF is registered in the second device 30B based on a registration request from the first device 30A. In other words, the second digital key is registered based on the first digital key.

[0048] The relationship between the fifth device 30E and the first device 30A is such that the friend key KF is registered in the fifth device 30E based on a registration request from the first device 30A. In other words, the fifth digital key is registered based on the first digital key.

[0049] The relationship between the third device 30C and the second device 30B is such that the non-friend key KN is registered in the third device 30C based on a registration request from the second device 30B. In other words, the third digital key is registered based on the second digital key.

[0050] The relationship between the fourth device 30D and the second device 30B is such that the non-friend key KN is registered in the fourth device 30D based on a registration request from the second device 30B. In other words, the fourth digital key is registered based on the second digital key.

[0051] The relationship between the sixth device 30F and the fifth device 30E is such that the non-friend key KN is registered in the sixth device 30F based on a registration request from the fifth device 30E. In other words, the sixth digital key is registered based on the fifth digital key.

[0052] In the data DA, the relationship between the seventh device 30G and the fifth device 30E is such that the non-friend key KN is registered in the seventh device 30G due to a registration request from the fifth device 30E. In other words, the seventh digital key is registered based on the fifth digital key.

[0053] In this way, the data DA includes information about the device 30 to which the digital key is registered. In the data DA, the registered device 30 is associated with information indicating the device 30 that made the request that caused the registration of the device 30. The data DA also includes information indicating which digital key each digital key is registered under.

[0054] <Digital Key Registration> Next, a series of registration processes for registering digital keys in the management system 10 will be described. Digital key registration includes registration of the owner key KO, registration of the friend key KF, and registration of the non-friend key KN. Below, a series of processes from when each digital key is not registered to when the digital key is registered will be described. In the following explanation, the processes executed by the execution device 27 will be described as processes executed by the vehicle 20. The processes executed by the execution device 36 will be described as processes executed by the device 30. The processes executed by the execution device 71 will be described as processes executed by the management server 70.

[0055] 5, the management system 10 performs a series of processes to register the owner key KO. The following describes an example of registering the owner key KO for the first device 30A that does not store key information DK indicating the owner key KO.

[0056] By registering the owner key KO, the management system 10 causes the first device 30A to store key information DK indicating the owner key KO. By registering the owner key KO, the management system 10 causes the vehicle 20 to store authentication information AT for authenticating the owner key KO. As a result, the first device 30A is set as the owner device 40. When registering the owner key KO, necessary applications are pre-installed in the first device 30A.

[0057] When the management server 70 receives a registration request D11 for the owner key KO from the first device 30A or the like, the management server 70 first performs processing in step S11. In step S11, the management server 70 generates a pairing password PAS. Then, the management server 70 transmits information indicating the pairing password PAS to the vehicle 20 and the first device 30A.

[0058] Then, vehicle 20 receives pairing password PAS. After receiving pairing password PAS, vehicle 20 is set to pairing mode via HMI 22. Vehicle 20 waits in a state in which it can receive a password from first device 30A. Then, vehicle 20 proceeds to step S12.

[0059] In step S12, the vehicle 20 performs pairing with the first device 30A. Once pairing is performed, the vehicle 20 establishes a secure channel for data communication with the first device 30A. The pairing is performed using a pairing password PAS transmitted from the management server 70 to the vehicle 20 and the first device 30A. Once pairing is complete, the vehicle 20 proceeds to step S13.

[0060] In step S13, the vehicle 20 generates a vehicle public key PKV, which is the public key of the vehicle 20, and a vehicle private key SKV, which is the private key of the vehicle 20. Then, the vehicle 20 transmits generation data DC for generating the owner key KO to the first device 30A via the secure channel. The generation data DC includes vehicle identification information ST1 and vehicle public key information indicating the vehicle public key PKV. The first device 30A then receives the generation data DC. The first device 30A then proceeds to step S14.

[0061] In step S14, the first device 30A generates owner key information DKO indicating the owner key KO. Then, the first device 30A proceeds to step S15. In step S15, the first device 30A stores the owner key information DKO. As a result, the first device 30A becomes the owner device 40. Then, the first device 30A transmits, to the vehicle 20, certificate information ST5 related to the owner key KO and device public key information ST6 indicating the device public key PKD.

[0062] Thereafter, when vehicle 20 receives certificate information ST5 and device public key information ST6, vehicle 20 performs the process of step S16. In step S16, vehicle 20 verifies certificate information ST5. Then, when the verification of certificate information ST5 is completed, vehicle 20 proceeds to the process of step S17.

[0063] In step S17, vehicle 20 stores device public key information ST6 indicating device public key PKD as authentication information AT, and then transmits a completion notification M11 to first device 30A indicating that storage of authentication information AT has been completed.

[0064] Thereafter, when the first device 30A receives the completion notification M11, the first device 30A performs the process of step S18. In step S18, the first device 30A generates a key track request D12 for the owner key KO. The key track request D12 is a signal requesting the management server 70 to update the database DB. The first device 30A then transmits the key track request D12 for the owner key KO to the management server 70 via the device server 60.

[0065] Thereafter, when the management server 70 receives the key track request D12, it performs processing in step S19. In step S19, the management server 70 performs registration management of the owner key KO. Specifically, the management server 70 stores, as data DA of the vehicle 20 in the database DB, that the device 30 in which the owner key KO is registered is the first device 30A. This causes the management system 10 to complete the series of processes for registering the owner key KO.

[0066] 6, the management system 10 performs a series of registration processes to register a friend key KF. The following describes an example of registering a friend key KF through the series of processes for a second device 30B that does not store friend key information DKF.

[0067] When an operation to request registration of a friend key KF is executed in the owner device 40, the owner device 40 first performs the process of step S21. In step S21, the owner device 40 transmits a friend key KF registration request D21 to a relay server (not shown). Then, the owner device 40 proceeds to step S22.

[0068] In step S22, the owner device 40 obtains invitation information IV1 for sharing the digital key from the relay server. The invitation information IV1 is, for example, a URL link. The URL link stores share information SH1 required for sharing the digital key. The owner device 40 then transmits the invitation information IV1 to the second device 30B.

[0069] After that, when the second device 30B receives the invitation information IV1, it performs the process of step S23. In step S23, the second device 30B acquires the share information SH1 based on the invitation information IV1. Specifically, the second device 30B downloads the share information SH1 from the link source of the URL link.

[0070] The share information SH1 includes, for example, share key structure information STS, password information ATP2, validity start time information ATP3, expiration date information ATP4, and name information ATP5. The validity start time information ATP3, expiration date information ATP4, and name information ATP5 are set by the owner device 40. The second device 30B then proceeds to step S24.

[0071] In step S24, the second device 30B uses the share information SH1 to generate signature-less friend key information DKFN. The signature-less friend key information DKFN is friend key information DKF that does not include signature information ATP1. The second device 30B then transmits to the owner device 40 a completion notification M21 indicating that the generated signature-less friend key information DKFN has been uploaded to the URL link, and a signature request D22 requesting a signature.

[0072] The owner device 40 then receives a completion notification M21 and a signature request D22 from the second device 30B. Upon receiving the completion notification M21, the owner device 40 acquires the unsigned friend key information DKFN. Upon receiving the signature request D22, the owner device 40 performs the process of step S25 in response to an operation of the owner device 40.

[0073] In step S25, the owner device 40 generates signature information ATP1. Specifically, the owner device 40 causes the HMI 32 to present the acquired signature-free friend key information DKFN and accepts an operation by the user of the owner device 40 indicating consent to the registration of the friend key KF. When this operation is performed, the owner device 40 generates signature information ATP1 based on the operation. The owner device 40 then proceeds to step S26.

[0074] In step S26, the owner device 40 adds the signature information ATP1 to the unsigned friend key information DKFN. This causes the owner device 40 to generate friend key information DKF. The owner device 40 then uploads the generated friend key information DKF to the URL link, which is the invitation information IV1. The owner device 40 then transmits a completion notification M22 to the second device 30B, indicating that the completed friend key information DKF has been uploaded to the URL link.

[0075] The second device 30B then receives the completion notification M22. The second device 30B then performs the process of step S27. In step S27, the second device 30B downloads and stores the friend key information DKF. As a result, the second device 30B is set as a friend device 51. The second device 30B then proceeds to step S28.

[0076] In step S28, the second device 30B generates a key track request D23 for the friend key KF. Then, the second device 30B transmits the friend key information DKF and the key track request D23 for the friend key KF to the management server 70.

[0077] Thereafter, when the management server 70 receives a key track request D23 for the friend key KF, the management server 70 performs the process of step S29. In step S29, the management server 70 performs registration management of the friend key KF.

[0078] Specifically, the management server 70 confirms that the friend key KF that is the target of the key track request D23 is not on the reject list. The reject list is a list that shows the share keys KS that include the friend key KF and the non-friend key KN for which a deletion request has already been received. If the friend key KF is on the reject list, the management server 70 sends a notification to the second device 30B that the key track request D23 cannot be fulfilled.

[0079] On the other hand, if the friend key KF that received the key track request D23 is not on the rejection list, the management server 70 registers the friend key KF that received the key track request D23 in the database DB. Specifically, the management server 70 stores, as data DA of the vehicle 20 in the database DB, that the device 30 registered as the friend device 51 is the second device 30B. The management server 70 stores the relationship between the second device 30B and the owner device 40 by referring to the acquired friend key information DKF.

[0080] Thereafter, the management server 70 transmits the authentication package ATP included in the friend key information DKF and a storage request D24 requesting storage of the authentication package ATP to the vehicle 20. That is, the management server 70 transmits device public key information ST6 indicating the device public key PKD of the friend device 51 to the vehicle 20. The management server 70 notifies the vehicle 20 that the device public key PKD has been signed by the owner device 40.

[0081] Thereafter, when the vehicle 20 receives the storage request D24 and the authentication package ATP from the management server 70, the vehicle 20 performs the process of step S30. In step S30, the vehicle 20 stores the received authentication package ATP as authentication information AT for authenticating the friend key KF.

[0082] After completing the registration management, the management server 70 transmits a key track completion notification M23 to the second device 30B. Thereafter, upon receiving the key track completion notification M23, the second device 30B performs the processing of step S31. In the processing of step S31, the second device 30B presents information indicating the completion of the registration of the friend key KF to the HMI 32. For example, the second device 30B presents an image indicating the completion of the registration of the friend key KF to the HMI 32. For example, the second device 30B displays an image indicating the completion of the registration of the friend key KF on the HMI 32. This causes the management system 10 to complete the series of processes for registering the friend key KF.

[0083] 7, the management system 10 performs a series of registration processes to register a non-friend key KN. Below, an example will be described in which the series of processes is used to register a non-friend key KN for a third device 30C that does not store non-friend key information DKN.

[0084] When an operation to request registration of a non-friend key KN is executed on the friend device 51, the friend device 51 first performs the process of step S41. In step S41, the friend device 51 transmits a registration request D31 of the non-friend key KN to a relay server (not shown). Then, the friend device 51 proceeds to the process of step S42.

[0085] In step S42, the friend device 51 obtains invitation information IV2 for sharing the digital key from the relay server. The invitation information IV2 is, for example, a URL link. The URL link stores share information SH2 required for sharing the digital key. The friend device 51 then transmits the invitation information IV2 to the third device 30C.

[0086] After that, when the third device 30C receives the invitation information IV2, it performs the process of step S43. In step S43, the third device 30C acquires the share information SH2 based on the invitation information IV2. Specifically, the second device 30B downloads the share information SH2 from the URL link.

[0087] The share information SH2 includes, for example, share key structure information STS, password information ATP2, validity start time information ATP3, expiration date information ATP4, and name information ATP5. The validity start time information ATP3, expiration date information ATP4, and name information ATP5 are set by the friend device 51. The third device 30C then proceeds to step S44.

[0088] In step S44, the third device 30C uses the share information SH2 to generate unsigned non-friend key information DKNN. The unsigned non-friend key information DKNN is non-friend key information DKN that does not have the signature information ATP1. The third device 30C then transmits a completion notification M31 indicating that the generated unsigned non-friend key information DKNN has been uploaded to the URL link, and a signature request D32 requesting a signature.

[0089] The friend device 51 then receives a completion notification M31 and a signature request D32 from the third device 30C. Upon receiving the completion notification M31, the friend device 51 acquires the unsigned non-friend key information DKNN. Upon receiving the signature request D32, the friend device 51 performs the process of step S45 in response to an operation of the friend device 51.

[0090] In step S45, the friend device 51 generates signature information ATP1. Specifically, the friend device 51 causes the HMI 32 to present the acquired signature-less non-friend key information DKNN, and accepts an operation by the user of the friend device 51 indicating consent to the generation of the non-friend key KN. When the operation is performed, the friend device 51 generates signature information ATP1 based on the operation. The friend device 51 then proceeds to step S46.

[0091] In step S46, the friend device 51 adds the signature information ATP1 to the unsigned non-friend key information DKNN. This causes the friend device 51 to generate non-friend key information DKN. The friend device 51 then uploads the generated non-friend key information DKN to the URL link, which is the invitation information IV2. The friend device 51 then transmits a completion notification M32 to the third device 30C, indicating that the completed non-friend key information DKN has been uploaded to the URL link.

[0092] The third device 30C then receives the completion notification M32. The third device 30C then performs the process of step S47. In step S47, the third device 30C downloads and stores the non-friend key information DKN. As a result, the third device 30C is set as a non-friend device 52. The third device 30C then proceeds to step S47.

[0093] In step S48, the third device 30C generates a key track request D33 for the non-friend key KN. Then, the third device 30C transmits the non-friend key information DKN and the key track request D33 for the non-friend key KN to the management server 70.

[0094] Thereafter, when the management server 70 receives a key track request D33 for the non-friend key KN, the management server 70 performs the process of step S49. In step S49, the management server 70 performs registration management of the non-friend key KN.

[0095] Specifically, the management server 70 confirms that the non-friend key KN that is the target of the key track request D33 is not on the rejection list. If the non-friend key KN is on the rejection list, the management server 70 sends a notification to the third device 30C that the key track request D33 cannot be fulfilled.

[0096] On the other hand, if the non-friend key KN is not on the rejection list, the management server 70 registers the non-friend key KN that is the target of the key track request D33 in the database DB. Specifically, the management server 70 stores, as data DA of the vehicle 20 in the database DB, that the third device 30C is the device 30 registered as a non-friend device 52. The management server 70 stores the relationship between the third device 30C and the friend device 51 by referring to the acquired non-friend key information DKN. Specifically, the management server 70 stores that the third device 30C is the device 30 having the non-friend key KN registered in response to the registration request D31 from the second device 30B.

[0097] Thereafter, the management server 70 transmits the authentication package ATP included in the non-friend key information DKN and a storage request D34 requesting storage of the authentication package ATP to the vehicle 20. That is, the management server 70 transmits device public key information ST6 indicating the device public key PKD of the non-friend device 52 to the vehicle 20. The management server 70 notifies the vehicle 20 that the device public key PKD is signed by the friend device 51.

[0098] Thereafter, when the vehicle 20 receives the authentication package ATP and the storage request D34, the vehicle 20 performs the process of step S50. In step S50, the vehicle 20 stores the received authentication package ATP. The authentication package ATP is authentication information AT for authenticating the non-friend key KN.

[0099] After completing the registration management, the management server 70 transmits a key track completion notification M33 to the second device 30B. After that, upon receiving the key track completion notification M33, the second device 30B performs the processing of step S51. In the processing of step S51, the third device 30C presents information indicating the completion of registration of the non-friend key KN to the HMI 32. For example, the third device 30C displays an image indicating the completion of registration of the non-friend key KN on the HMI 32. This causes the management system 10 to complete the series of processes for registering the non-friend key KN.

[0100] <Deleting a Non-Friend Key> Next, a series of processes for deleting a non-friend key KN in the management system 10 will be described. Below, a series of flows from a state in which a non-friend key KN is registered to a state in which the non-friend key KN is not registered will be described. In the following explanation, the process executed by the execution unit 27 will be described as a process executed by the vehicle 20. The process executed by the execution unit 36 ​​will be described as a process executed by the device 30. The process executed by the execution unit 71 will be described as a process executed by the management server 70.

[0101] <Deleting a Non-Friend Key in Response to a Deletion Request from a Friend Device> As shown in FIG. 8, the management system 10 performs a series of processes to delete a non-friend key KN in response to a reservation deletion request D41 from a friend device 51.

[0102] When an operation to request the deletion of the non-friend key KN is executed in the friend device 51, the friend device 51 first performs the process of step S61. In step S61, a reservation deletion request D41 for the non-friend key KN is generated. The reservation deletion request D41 is a request to delete the reservation.

[0103] The reservation deletion request D41 includes a signal requesting deletion of the non-friend key KN, digital key identification information ST3 indicating the non-friend key KN, and information indicating a prescribed condition RC. The prescribed condition RC is a condition required to start deletion after receiving the reservation deletion request D41. The prescribed condition RC is predetermined. For example, the prescribed condition RC is that a predetermined fade-out period has elapsed since receiving the reservation deletion request D41. The friend device 51 then transmits the reservation deletion request D41 for the non-friend key KN to the management server 70.

[0104] Thereafter, when the management server 70 receives the reservation deletion request D41 for the non-friend key KN, it performs processing in step S62. In step S62, the management server 70 generates a deletion in progress notification M41 indicating that the reservation is being deleted in accordance with the reservation deletion request D41. Then, the management server 70 transmits the deletion in progress notification M41 to the friend device 51.

[0105] Thereafter, when the friend device 51 receives the deletion notification M41, the friend device 51 performs the process of step S63. In step S63, the friend device 51 presents to the HMI 32 information indicating that the non-friend key KN that is the target of the reservation deletion request D41 is being deleted.

[0106] After the process of step S62, the management server 70 performs the process of step S64. In step S64, the management server 70 stores the state of the non-friend key KN that is the target of the reservation deletion request D41 as a fade-out state in the database DB. The fade-out state is a state after the reservation deletion request D41 has been received and the execution of deletion is still pending. Then, the management server 70 proceeds to the process of step S65.

[0107] In step S65, the management server 70 confirms that the prescribed condition RC is satisfied. If the management server 70 confirms that the prescribed condition RC is satisfied, the management server 70 proceeds to step S66.

[0108] In step S66, the management server 70 generates a deletion request D42 for deleting the non-friend key information DKN indicating the non-friend key KN that is the target of the reservation deletion request D41. Then, the management server 70 transmits the deletion request D42 to the non-friend device 52.

[0109] Thereafter, when the non-friend device 52 receives the deletion request D42, it performs processing in step S67. In step S67, the non-friend device 52 deletes the non-friend key information DKN in accordance with the deletion request D42. Then, the non-friend device 52 transmits a deletion completion notification M42 to the management server 70, indicating that the deletion in accordance with the deletion request D42 has been completed.

[0110] Thereafter, when the management server 70 receives the completion notification M42, the management server 70 performs the process of step S68. In step S68, the management server 70 stores the history of the deletion of the non-friend key information DKN in the non-friend device 52. Thereafter, the management server 70 proceeds to the process of step S69.

[0111] In step S69, the management server 70 generates a deletion request D43 for the authentication information AT. The deletion request D43 for the authentication information AT indicates a request to delete the authentication information AT for authenticating the non-friend key KN that is the target of the reservation deletion request D41. The management server 70 then transmits the deletion request D43 to the vehicle 20.

[0112] Thereafter, when the vehicle 20 receives the deletion request D43, the vehicle 20 performs the processing of step S70. In step S70, the vehicle 20 deletes the authentication information AT for authenticating the non-friend key KN that is the subject of the reservation deletion request D41 in accordance with the deletion request D43. That is, the vehicle 20 deletes the authentication package ATP of the non-friend key KN. The vehicle 20 then transmits a completion notification M43 to the management server 70 indicating that the deletion of the authentication information AT in accordance with the deletion request D43 has been completed.

[0113] Thereafter, when the management server 70 receives the completion notification M43, the management server 70 performs the process of step S71. In step S71, the management server 70 stores the deletion history of the authentication information AT for authenticating the non-friend key KN to be deleted in the current series of deletion-related processes in the vehicle 20. Thereafter, the management server 70 proceeds to step S72.

[0114] In step S72, the management server 70 updates the database DB. Specifically, the management server 70 deletes the non-friend device 52 having the non-friend key KN to be deleted in this series of processes from the data DA of the vehicle 20 in the database DB. Thereafter, the management server 70 transmits a completion notification M44 to the friend device 51, indicating that the series of deletions of the non-friend key KN in accordance with the reservation deletion request D41 has been completed.

[0115] Thereafter, when the friend device 51 receives the completion notification M44, the friend device 51 performs the process of step S73. In step S73, the friend device 51 presents information indicating that the deletion of the non-friend key KN, which is the target of the reservation deletion request D41, has been completed to the HMI 32. For example, the friend device 51 displays an image indicating the completion of the deletion of the non-friend key KN on the HMI 32. Thereafter, the management system 10 ends the series of processes for the deletion of the current non-friend key KN.

[0116] <Deletion of a non-friend key due to a deletion operation on a non-friend device> As shown in Figure 9, the management system 10 performs a series of processes to delete the non-friend key KN indicated by the non-friend key information DKN stored in the non-friend device 52 due to a deletion operation on the non-friend device 52.

[0117] When a predetermined operation requesting the deletion of the non-friend key KN is executed in the non-friend device 52, the non-friend device 52 first performs the processing of step S81. In step S81, the non-friend device 52 deletes the non-friend key information DKN in accordance with the predetermined operation. Thereafter, the non-friend device 52 transmits a completion notification M51 indicating that the deletion of the non-friend key information DKN has been completed to the management server 70.

[0118] Thereafter, when the management server 70 receives the completion notification M51, the management server 70 performs the process of step S82. In step S82, the management server 70 stores the history of the deletion of the non-friend key information DKN in the non-friend device 52. Thereafter, the management server 70 transmits a completion notification M52 to the friend device 51, indicating that the deletion of the non-friend key information DKN has been completed.

[0119] Thereafter, when the friend device 51 receives the completion notification M52, the friend device 51 performs the process of step S83. In step S83, the friend device 51 presents, to the HMI 32, information indicating that the deletion of the non-friend key information DKN of the non-friend device 52 has been completed. For example, the friend device 51 displays, on the HMI 32, an image indicating that the deletion of the non-friend key KN has been completed.

[0120] After processing in step S82, the management server 70 performs processing in step S84. In step S84, the management server 70 generates a deletion request D51 for deleting the authentication information AT for authenticating the non-friend key information DKN whose deletion has been completed in the completion notification M51. The management server 70 then transmits the deletion request D51 to the vehicle 20.

[0121] Thereafter, when the vehicle 20 receives the deletion request D51, the vehicle 20 performs the processing of step S85. In step S85, the vehicle 20 deletes the authentication information AT for authenticating the non-friend key KN deleted in the processing of step S81 in accordance with the deletion request D51. The vehicle 20 then transmits to the management server 70 a completion notification M53 indicating that the deletion of the authentication information AT in accordance with the deletion request D51 has been completed.

[0122] Thereafter, when the management server 70 receives the completion notification M53, the management server 70 performs the process of step S86. In step S86, the management server 70 stores the history of the deletion of the authentication information AT for authenticating the non-friend key KN deleted in step S81. Thereafter, the management server 70 proceeds to the process of step S87.

[0123] In step S87, the management server 70 updates the database DB. Specifically, the management server 70 deletes the non-friend device 52 having the non-friend key KN to be deleted in this series of processes from the data DA of the vehicle 20 in the database DB. This causes the management system 10 to end the series of processes for deleting the non-friend key KN.

[0124] Next, we will explain a series of processes in the management system 10 regarding whether to execute inquiry and registration processes to notify the owner device 40 that a request for registration of a non-friend key KN has been made.

[0125] 1, in the management server 70, the storage device 72 stores the consent program PCA. The consent program PCA is a program that causes the execution device 71, which is a computer, to function as a query unit 70CD and an execution unit 70RA by executing a series of processes.

[0126] As shown in Figure 10, when the execution device 71 executes the consent program PCA, the execution device 71 functions as an inquiry unit 70CD and an execution unit 70RA. Therefore, in the first embodiment, the management server 70 has the inquiry unit 70CD and the execution unit 70RA. The communication module 73 of the management server 70 functions as a receiving unit 70RE that receives the key track request D33. Therefore, the management server 70 has the receiving unit 70RE. The management server 70 is an external server.

[0127] When the second device 30B newly registers a third digital key, the inquiry unit 70CD inquires of the first device 30A whether or not to accept the registration of the third digital key. The first device 30A is the device 30 in which the first digital key is registered. The second device 30B is the device 30 in which the second digital key is registered based on a request from the first device 30A.

[0128] Specifically, when the inquiry unit 70CD detects that there has been a request to register the non-friend key KN, it transmits to the owner device 40 a consent request CD requesting consent to the registration of the non-friend key KN.

[0129] When the execution unit 70RA receives consent information CI indicating consent to the registration of the third digital key, the execution unit 70RA executes the registration process of the third digital key. On the other hand, when the execution unit 70RA does not receive consent information CI, the execution unit 70RA does not execute the registration process of the third digital key.

[0130] Specifically, if the execution unit 70RA does not receive consent information CI indicating consent from the owner device 40, the execution unit 70RA does not cause the management system 10 to execute the registration process for the non-friend key KN. If the execution unit 70RA receives consent information CI from the owner device 40, the execution unit 70RA causes the management system 10 to execute the registration process for the non-friend key KN.

[0131] The storage device 28 of the vehicle 20 functions as a storage unit 20M that stores the authentication information AT. Therefore, the vehicle 20 has the storage unit 20M as an authentication information storage unit. The storage device 72 of the management server 70 functions as a storage unit 70M that stores the database DB. Therefore, the management server 70 has the storage unit 70M as a database storage unit.

[0132] Specifically, the execution device 71 starts execution of the consent program PCA when it detects that registration of a non-friend key KN has been requested in the management system 10. When the execution device 71 receives the key track request D33, it detects that registration of a non-friend key KN has been requested in the management system 10. That is, the inquiry unit 70CD detects that there has been a request to register a non-friend key KN, which is a third digital key, when the receiving unit 70RE of the management server 70 receives the key track request D33 from the friend device 51, which is the second device 30B.

[0133] As shown in FIG. 11 , when the execution device 71 starts executing the consent program PCA, it first performs processing in step S101. In step S101, the execution device 71 identifies the owner device 40, which is the first device 30A to be the destination. Specifically, the execution device 71 first references the database DB to identify the vehicle 20 that is the target of the non-friend key KN of the key track request D33. Next, the execution device 71 references the data DA of the identified vehicle 20 to identify the device 30 that stores owner key information DKO indicating the owner key KO for the vehicle 20 as the owner device 40. The execution device 71 then proceeds to step S102.

[0134] In step S102, the executing device 71 transmits an acceptance request CD to the owner device 40. The acceptance request CD indicates to the destination owner device 40 that the acceptance of the request to register the non-friend key KN is requested from the owner device 40. The owner device 40 that receives the acceptance request CD displays the acceptance request CD on the HMI 32. When the owner device 40 accepts the acceptance request CD, the owner device 40 transmits acceptance information CI indicating acceptance to the management server 70. On the other hand, if the owner device 40 does not accept the acceptance request CD within a predetermined specified period PP, or if the owner device 40 accepts an operation not to accept, the owner device 40 transmits information indicating not to accept to the management server 70. The specified period PP is, for example, one day. The executing device 71 then proceeds to step S103.

[0135] In step S103, the executing device 71 determines whether or not it has received consent information CI from the owner device 40 within the specified period PP. Specifically, when the executing device 71 receives consent information CI from the owner device 40 within the specified period PP after starting the processing of step S104, the executing device 71 determines that it has received consent information CI. On the other hand, when the executing device 71 does not receive consent information CI or receives information indicating that the executing device 71 does not give consent within the specified period PP after starting the processing of step S104, the executing device 71 determines that it has not received consent information CI.

[0136] When the executing device 71 receives the consent information CI from the owner device 40 during the specified period PP (S103: YES), the executing device 71 proceeds to step S104. In step S104, the executing device 71 determines to have the management system 10 execute the registration process of the non-friend key KN. Thereafter, the executing device 71 proceeds to step S105.

[0137] In step S105, the execution device 71 allows the non-friend key KN to be stored in the database DB. Specifically, the execution device 71 allows the specific device 30X to be stored as the non-friend device 52 of the non-friend key KN in accordance with the key track request D33 for the non-friend key KN. As a result, the execution unit 70RA does not prevent the management server 70 from registering the non-friend key KN in the database DB. When the execution device 71 allows the non-friend key KN to be stored in the database DB, the execution device 71 stores the specific device 30X as the non-friend device 52 through registration management of the non-friend key KN. In other words, the execution unit 70RA associates the third digital key with the third device 30C and stores them in the database DB during the registration process. The execution device 71 then proceeds to step S106.

[0138] In step S106, the execution device 71 allows the transmission of the authentication package ATP and storage request D34 for the non-friend key KN. As a result, the execution unit 70RA does not prevent the management server 70 from transmitting the authentication package ATP and storage request D34 for the non-friend key KN to the vehicle 20. When the execution device 71 allows the transmission of the authentication package ATP and storage request D34 for the non-friend key KN to the vehicle 20, the execution device 71 transmits the authentication package ATP and storage request D34 for the non-friend key KN to the vehicle 20. When the vehicle 20 receives the authentication package ATP and storage request D34 for the non-friend key KN, the vehicle management device 26 stores the authentication package ATP for the non-friend key KN as authentication information AT. The execution device 71 then terminates this series of processes.

[0139] On the other hand, if the executing device 71 does not receive the consent information CI from the owner device 40 within the specified period PP (S103: NO), the executing device 71 proceeds to step S107.

[0140] In step S107, the execution device 71 determines not to allow the non-friend key KN to be registered in the management system 10. After that, the execution device 71 advances the process to step S108.

[0141] In step S108, the execution device 71 denies storage of the non-friend key KN in the database DB. That is, the execution device 71 does not allow storage of the non-friend key KN in the database DB. Specifically, even if a key track request D33 for the non-friend key KN is made, the execution device 71 does not store the specific device 30X as a non-friend device 52 for the non-friend key KN. As a result, the execution unit 70RA does not allow the management server 70 to register the non-friend key KN in the database DB. If the execution device 71 does not allow storage of the non-friend key KN in the database DB, the execution device 71 does not store the specific device 30X as a non-friend device 52 through registration management of the non-friend key KN. Then, the execution device 71 proceeds to step S109.

[0142] In step S109, the execution device 71 does not allow the transmission of the authentication package ATP and storage request D34 for the non-friend key KN. As a result, the execution unit 70RA does not allow the management server 70 to transmit the authentication package ATP and storage request D34 for the non-friend key KN to the vehicle 20. If the execution device 71 does not allow the transmission of the authentication package ATP and storage request D34 for the non-friend key KN to the vehicle 20, the execution device 71 does not transmit the authentication package ATP and storage request D34 for the non-friend key KN to the vehicle 20. Therefore, the vehicle management device 26 does not store the authentication package ATP for the non-friend key KN as authentication information AT. The execution device 71 then terminates this series of processes.

[0143] The management system 10 includes an inquiry unit 70CD and an execution unit 70RA, and thus performs a management method. In the management method, when the second device 30B newly registers a third digital key, the management system 10 inquires of the first device 30A whether or not to consent to the registration of the third digital key. In the management method, the management system 10 executes the registration process for the third digital key if it receives consent information CI, and does not execute the registration process if it does not receive consent information CI.

[0144] <Operation of First Embodiment> In the first embodiment, it is assumed that the management system 10 does not have the inquiry unit 70CD and the execution unit 70RA. In this case, in the series of processes for registering the non-friend key KN shown in Fig. 7, the owner device 40 cannot recognize that there has been a request to register the non-friend key KN. Therefore, there is a risk that a non-friend key KN will be registered against the will of the owner of the owner device 40.

[0145] In this regard, according to the first embodiment, the inquiry unit 70CD transmits an acceptance request CD to the owner device 40. The execution unit 70RA allows the registration of the non-friend key KN when it receives acceptance information CI from the owner device 40. Therefore, the owner device 40 is involved in continuing the process during the series of processes when the non-friend key KN is registered.

[0146] <Effects of the First Embodiment> (1-1) When the inquiry unit 70CD detects a request for registration of the third digital key, it sends an acceptance request CD to the first device 30A to inquire whether to accept the registration of the third digital key. If the execution unit 70RA subsequently does not receive acceptance information CI from the first device 30A, it does not allow the management system 10 to register the non-friend key KN, thereby not executing the registration process for the third digital key. On the other hand, when the execution unit 70RA receives acceptance information CI from the owner device 40, it allows the management system 10 to register the non-friend key KN, thereby executing the registration process for the third digital key. Therefore, the owner device 40 is involved in continuing the process during the series of processes for registering the non-friend key KN. This allows the management system 10 to prevent the non-friend key KN from being registered against the will of the owner of the owner device 40.

[0147] (1-2) When the execution unit 70RA allows the management server 70 to register the non-friend key KN, which is a third digital key, the execution unit 70RA sends a storage request D34 to the vehicle 20. As a result, the vehicle 20 stores the authentication information AT of the non-friend key KN. Therefore, when the third device 30C stores the non-friend key information DKN and the vehicle 20 stores the authentication information AT, the management system 10 can enable the use of the non-friend key KN.

[0148] (1-3) When the execution unit 70RA does not allow the management server 70 to register the non-friend key KN, which is the third digital key, the execution unit 70RA does not send a storage request D34 to the vehicle 20. As a result, the vehicle 20 does not store the authentication information AT of the non-friend key KN, which is the third digital key. Therefore, although the third device 30C stores the non-friend key information DKN, the vehicle 20 does not store the authentication information AT, and the management system 10 does not enable the use of the non-friend key KN, which is the third digital key.

[0149] (1-4) When the execution unit 70RA allows the management server 70 to register the non-friend key KN, the execution unit 70RA stores in the database DB the non-friend key KN, which is the third digital key, in association with the third device 30C in which the third digital key is registered. Therefore, the management server 70 can update the database DB to store information about the non-friend device 52, which is the third device 30C in which the third digital key is registered.

[0150] (1-5) When the execution unit 70RA does not allow the management server 70 to register a non-friend key KN, the execution unit 70RA does not store information indicating the shared device 50 indicating the non-friend key KN whose registration was not allowed in the database DB. Therefore, the management server 70 can set the database DB to a state in which the non-friend device 52 is not stored.

[0151] (1-6) The management server 70 has an inquiry unit 70CD and an execution unit 70RA. Therefore, the inquiry unit 70CD and the execution unit 70RA can easily use information acquired by the management server 70. Therefore, the inquiry unit 70CD and the execution unit 70RA can easily control the processing performed by the management server 70.

[0152] (1-7) When the inquiry unit 70CD receives the key track request D33, it detects that there has been a request to register the non-friend key KN. Therefore, in the series of processes shown in Figure 7, the inquiry unit 70CD can detect that there has been a request to register the non-friend key KN when the non-friend device 52 has stored the non-friend key information DKN but before the vehicle 20 has stored the authentication information AT.

[0153] Second Embodiment The management system 10 according to the second embodiment will be described below with reference to the drawings. The second embodiment differs from the first embodiment in that the vehicle management device 26 of the vehicle 20 includes a query unit 20CD and an execution unit 20RA. The following description will focus on the differences from the first embodiment, and descriptions of the same points will be simplified or omitted.

[0154] 12, the storage device 28 stores the consent program PCA2 in the second embodiment. The consent program PCA2 is a program that causes the vehicle management device 26, which is a computer, in the vehicle 20 to function as a query unit 20CD and an execution unit 20RA.

[0155] 13, when the execution device 27 executes the consent program PCA2, the execution device 27 functions as an inquiry unit 20CD and an execution unit 20RA. Therefore, in the second embodiment, the vehicle 20 has the inquiry unit 20CD and the execution unit 20RA. The communication module 21 of the vehicle 20 functions as a receiving unit 20RE that receives the storage request D34. Therefore, the vehicle 20 has the receiving unit 20RE.

[0156] The execution device 27 starts execution of the consent program PCA2 when it detects that registration of the non-friend key KN has been requested in the management system 10. When the execution device 27 receives the authentication package ATP and storage request D34 for the non-friend key KN, it detects that registration of the non-friend key KN has been requested in the management system 10. In other words, when the receiving unit 20RE receives the authentication package ATP and storage request D34 for the non-friend key KN, the inquiry unit 20CD detects that a request for registration of the non-friend key KN has been made.

[0157] 14, when the execution device 27 starts executing the consent program PCA2, the execution device 27 performs the process of step S111. In step S111, the execution device 27 identifies the owner device 40 to which the consent request CD is to be sent. In the second embodiment, information identifying the owner device 40 is added to the authentication package ATP. The execution device 27 identifies the owner device 40 identified by the information identifying the owner device 40 as the owner device 40 to which the consent request CD is to be sent. The execution device 27 then proceeds to step S112.

[0158] In step S112, the executing device 27 transmits a consent request CD to the owner device 40. For example, the executing device 27 communicates with the owner device 40 via the management server 70 and the device server 60 using the communication module 21. That is, when the receiving unit 20RE receives the storage request D34, the inquiry unit 20CD inquires of the first device 30A whether or not to consent to the registration of the third digital key. Then, the executing device 27 proceeds to step S113.

[0159] In step S113, the execution device 27 determines whether or not consent information CI has been received within the specified period PP from the owner device 40. Step S113 is the same as step S103 in the first embodiment, and therefore a detailed description thereof will be omitted.

[0160] When the executing device 27 receives the consent information CI from the owner device 40 within the specified period PP (S113: YES), the executing device 27 proceeds to step S114. In step S114, the executing device 27 determines to allow registration of the non-friend key KN in the management system 10. Thereafter, the executing device 27 proceeds to step S115.

[0161] In step S115, the execution unit 27 allows the authentication information AT of the non-friend key KN to be stored. That is, the execution unit 20RA allows the non-friend key KN to be registered in the vehicle 20. Specifically, the execution unit 20RA allows the vehicle 20 to store the authentication information AT of the non-friend key KN. As a result, the execution unit 27 stores the authentication information AT of the non-friend key KN in accordance with the storage request D34. Thereafter, the execution unit 27 ends this series of processes.

[0162] On the other hand, if the executing device 27 does not receive consent information CI from the owner device 40 within the specified period PP (S113: NO), the executing device 27 proceeds to step S116. In step S116, the executing device 27 determines not to allow registration of the non-friend key KN in the management system 10. Thereafter, the executing device 27 proceeds to step S117.

[0163] In step S117, the execution unit 27 refuses to store the authentication information AT of the non-friend key KN. That is, the execution unit 20RA does not allow the vehicle 20 to register the non-friend key KN. Specifically, the execution unit 20RA does not allow the vehicle 20 to store the authentication information AT of the non-friend key KN. As a result, even if the execution unit 27 receives the storage request D34, it does not store the authentication information AT of the non-friend key KN. Thereafter, the execution unit 27 ends this series of processes.

[0164] <Operation of Second Embodiment> In the second embodiment, when the execution unit 20RA receives consent information CI from the owner device 40, it allows the vehicle 20 to store authentication information AT. In this case, when the vehicle 20 stores the authentication information AT, the non-friend key KN becomes usable. On the other hand, when the execution unit 20RA does not receive consent information CI from the owner device 40, it does not cause the vehicle 20 to store authentication information AT. In this case, when the vehicle 20 does not store the authentication information AT, the non-friend key KN does not become usable.

[0165] <Effects of Second Embodiment> According to the second embodiment, in addition to the effect (1-1) of the first embodiment, the following effects can be achieved.

[0166] (2-1) In the second embodiment, the vehicle 20 includes an inquiry unit 20CD and an execution unit 20RA. Therefore, the inquiry unit 20CD and the execution unit 20RA can use information acquired by the vehicle 20. The execution unit 20RA can easily control the processing performed by the vehicle 20.

[0167] (2-2) When the inquiry unit 20CD receives the storage request D34, it detects that there has been a request to register the non-friend key KN. Therefore, the inquiry unit 20CD can detect that there has been a request to register the non-friend key KN when the vehicle 20 stores the authentication information AT in the series of processes shown in FIG.

[0168] (2-3) When the execution unit 20RA allows the registration of the non-friend key KN, which is the third digital key, to the vehicle 20, the execution device 27 stores the authentication information AT of the non-friend key KN, which is the third digital key. As a result, the vehicle 20 can be made ready to use the third digital key.

[0169] (2-4) When the execution unit 20RA does not allow the registration of the non-friend key KN, which is the third digital key, to the vehicle 20, the execution device 27 does not store the authentication information AT of the non-friend key KN, which is the third digital key. Therefore, the vehicle 20 can remain in a state where the third digital key cannot be used.

[0170] Third Embodiment The management system 10 according to the third embodiment will be described below with reference to the drawings. The third embodiment differs from the first embodiment in that the non-friend device 52 includes a query unit 30CD and an execution unit 30RA. The following description will focus on the differences from the first embodiment, and the same descriptions will be simplified or omitted for the same aspects.

[0171] As shown in Figure 15, the storage device 37 of the non-friend device 52 stores the consent program PCA3 in the third embodiment. The consent program PCA3 is a program that causes the execution device 36 of the non-friend device 52, which is a computer, to function as the inquiry unit 30CD and execution unit 30RA in the non-friend device 52. Hereinafter, the execution device 36 of the non-friend device 52 will be referred to as the execution device 36N. The storage device 37 of the non-friend device 52 will be referred to as the storage device 37N.

[0172] 16, when the execution device 36N executes the consent program PCA3, the execution device 36N functions as an inquiry unit 30CD and an execution unit 30RA. Therefore, in the third embodiment, the non-friend device 52 has the inquiry unit 30CD and the execution unit 30RA.

[0173] The execution unit 36N starts execution of the consent program PCA3 when it detects that registration of a non-friend key KN has been requested in the management system 10. The execution unit 36N detects that a request for registration of a non-friend key KN has been made when it acquires the non-friend key information DKN. That is, the inquiry unit 30CD detects that a request for registration of a non-friend key KN has been made by acquiring the non-friend key information DKN.

[0174] 17, when the execution device 36N starts executing the consent program PCA2, the execution device 36N first performs the processing of step S121. In step S121, the execution device 36N identifies the owner device 40 to which the consent request CD is to be sent. In the third embodiment, information identifying the owner device 40 is added to the shared key information DKS. The execution device 36N identifies the owner device 40 identified by the information identifying the owner device 40 as the owner device 40 to which the consent request CD is to be sent. The execution device 36N then proceeds to step S122.

[0175] In step S122, the executing device 36N transmits a consent request CD to the owner device 40. Then, the executing device 36N proceeds to step S123. In step S123, the executing device 36N determines whether consent information CI has been received from the owner device 40 within the specified period PP. Step S123 is the same as step S103 in the first embodiment, and therefore a detailed description thereof will be omitted.

[0176] When the executing device 36N receives the consent information CI from the owner device 40 during the specified period PP (S123: YES), the executing device 36N proceeds to step S124. In step S124, the executing device 36N determines that the management system 10 is permitted to register the non-friend key KN. Then, the executing device 36N proceeds to step S125.

[0177] In step S125, the execution unit 36N allows the storage of the non-friend key information DKN. That is, the execution unit 36N does not prevent the non-friend device 52 from registering the non-friend key KN. Specifically, the execution unit 36N allows the storage of the non-friend key information DKN in accordance with the completion notification M32 of the non-friend key KN. As a result, the execution unit 30RA stores the non-friend key information DKN in the non-friend device 52. After allowing the storage of the non-friend key information DKN, the execution unit 36N stores the non-friend key information DKN by processing in step S47. Thereafter, the execution unit 36N proceeds to step S126.

[0178] In step S126, the execution device 36N allows the transmission of the key track request D33. As a result, the execution unit 70RA does not prevent the non-friend device 52 from transmitting the key track request D33 to the management server 70. When the execution device 36N allows the transmission of the key track request D33, the execution device 36N transmits the key track request D33 to the management server 70. Thereafter, the execution device 36N proceeds with the current series of processes.

[0179] On the other hand, if the executing device 36N does not receive consent information CI from the owner device 40 within the specified period PP (S123: NO), the executing device 36N proceeds to step S127. In step S127, the executing device 36N determines not to allow registration of the non-friend key KN in the management system 10. Thereafter, the executing device 36N proceeds to step S128.

[0180] In step S128, the execution unit 36N rejects the storage of the non-friend key information DKN. That is, the execution unit 36N does not allow the non-friend device 52 to register the non-friend key KN. Specifically, even if the execution unit 36N receives the completion notification M32 for the non-friend key KN, the execution unit 36N does not allow the non-friend key information DKN to be stored. As a result, the execution unit 30RA does not allow the non-friend device 52 to store the non-friend key information DKN. If the execution unit 36N does not allow the storage of the non-friend key information DKN, the execution unit 36N does not perform the processing of step S47 and therefore does not store the non-friend key information DKN. The execution unit 36N then proceeds to step S129.

[0181] In step S129, the execution device 36N does not allow the transmission of the key track request D33. As a result, the execution unit 30RA does not allow the non-friend device 52 to send the key track request D33 to the management server 70. If the execution device 36N does not allow the transmission of the key track request D33, the execution device 36N does not send the key track request D33 to the management server 70. Therefore, the management server 70 does not store information indicating the device 30 as the non-friend device 52 of the non-friend key KN according to the key track request D33.

[0182] <Operation of Third Embodiment> In the third embodiment, when the execution unit 30RA receives consent information CI from the owner device 40, it allows the non-friend device 52 to store the non-friend key information DKN. In this case, when the non-friend device 52 stores the non-friend key information DKN, the non-friend device 52 becomes able to use the non-friend key KN. On the other hand, when the execution unit 30RA does not receive consent information CI from the owner device 40, it does not allow the non-friend device 52 to store the non-friend key information DKN. In this case, when the non-friend device 52 does not store the non-friend key information DKN, the non-friend key KN does not become able to be used.

[0183] <Effects of the Third Embodiment> According to the third embodiment, in addition to the effect (1-1) of the first embodiment, the following effects can be achieved.

[0184] (3-1) In the third embodiment, the non-friend device 52 has an inquiry unit 30CD and an execution unit 30RA. Therefore, the inquiry unit 30CD and the execution unit 30RA can use information acquired by the non-friend device 52. Therefore, the execution unit 30RA can easily control the processing performed by the non-friend device 52.

[0185] (3-2) When the inquiry unit 30CD acquires the non-friend key information DKN, it detects that there has been a request to register the non-friend key KN. Therefore, the inquiry unit 30CD can detect that there has been a request to register the non-friend key KN when the non-friend device 52 stores the non-friend key information DKN in the series of processes shown in FIG.

[0186] (3-3) When the execution unit 30RA allows the non-friend key KN to be registered in the non-friend device 52, the execution unit 36N stores the non-friend key information DKN. Therefore, the non-friend device 52 can be made to be able to use the non-friend key KN.

[0187] (3-4) When the execution unit 30RA does not allow the non-friend key KN to be registered in the non-friend device 52, the execution device 36N does not store the non-friend key information DKN. Therefore, the non-friend device 52 can remain in a state where the non-friend key KN cannot be used.

[0188] Fourth Embodiment The management system 10 according to the fourth embodiment will be described below with reference to the drawings. The fourth embodiment differs from the first embodiment in that the friend device 51 includes a query unit 51CD and an execution unit 51RA. The following description will focus on the differences from the first embodiment, and descriptions of the same aspects will be simplified or omitted.

[0189] As shown in Figure 18, the storage device 37 of the friend device 51 stores the consent program PCA4 of the fourth embodiment. The consent program PCA4 is a program that causes the execution device 36 of the friend device 51, which is a computer, to function as an inquiry unit 51CD and an execution unit 51RA. Hereinafter, the execution device 36 of the friend device 51 will be referred to as the execution device 36F. The storage device 37 of the friend device 51 will be referred to as the storage device 37N.

[0190] 19, when the execution device 36N executes the consent program PCA4, the execution device 36F functions as an inquiry unit 51CD and an execution unit 51RA. Therefore, in the fourth embodiment, the friend device 51 has the inquiry unit 51CD and the execution unit 51RA.

[0191] The execution unit 35F starts execution of the consent program PCA4 when it detects that registration of a non-friend key KN has been requested in the management system 10. The execution unit 36F detects that a request for registration of a non-friend key KN has been made when an operation requesting registration of a non-friend key KN is executed in the friend device 51. That is, when the inquiry unit 51CD receives a registration request D31 for a non-friend key KN, it detects that registration of a non-friend key KN has been requested.

[0192] As shown in FIG. 20, when the execution unit 36F starts executing the consent program PCA4, the execution unit 36F first performs the processing of step S131. In step S131, the execution unit 37F identifies the owner device 40 to which the consent request CD is to be sent. In the fourth embodiment, information identifying the owner device 40 is added to the friend key information DKF. The execution unit 36F identifies the owner device 40 identified by the information identifying the owner device 40 as the owner device 40 to which the consent request CD is to be sent. The execution unit 36F then proceeds to step S132.

[0193] In step S132, the executing unit 36F transmits a consent request CD to the owner device 40. The executing unit 36F then proceeds to step S133. In step S133, the executing unit 36F determines whether consent information CI has been received from the owner device 40 within the specified period PP. Step S133 is the same as step S103 in the first embodiment, and therefore a detailed description thereof will be omitted.

[0194] When the executing unit 36F receives the consent information CI from the owner device 40 during the specified period PP (S133: YES), the executing unit 36F proceeds to step S134. In step S134, the executing unit 36F determines to allow registration of the non-friend key KN in the management system 10. Thereafter, the executing unit 36F proceeds to step S135.

[0195] In step S135, the execution device 36F allows the transmission of the invitation information IV2. That is, the execution device 36F allows the friend device 51 to register the non-friend key KN. As a result, the execution unit 51RA causes the non-friend device 52 to acquire the share information SH2 and perform the subsequent registration process. Thereafter, the execution device 36F ends this series of processes.

[0196] On the other hand, when the executing device 36F does not receive the consent information CI from the owner device 40 within the specified period PP (S133: NO), the executing device 36F proceeds to step S136.

[0197] In step S136, the execution unit 36F determines not to allow the management system 10 to register the non-friend key KN. After that, the execution unit 36F proceeds to step S137.

[0198] In step S137, the execution device 36F rejects the transmission of the invitation information IV2. That is, the execution device 36F does not allow the friend device 51 to register the non-friend key KN. Specifically, even if the execution device 36F has acquired the invitation information IV2, the execution device 36F does not allow the invitation information IV2 to be transmitted. As a result, the execution device 36F does not allow the non-friend device 52 to acquire the share information SH2. Since the non-friend device 52 does not acquire the share information SH2, the management system 10 does not perform the processes from step S43 onwards in the registration process of the non-friend key KN. Thereafter, the execution device 36F ends this series of processes.

[0199] <Functions and Effects of Fourth Embodiment> According to the fourth embodiment, in addition to the effect (1-1) of the first embodiment, the following effect can be achieved.

[0200] (4-1) In the fourth embodiment, the friend device 51 includes an inquiry unit 51CD and an execution unit 51RA. Therefore, the inquiry unit 51CD and the execution unit 51RA can use information acquired by the friend device 51. The execution unit 51RA can easily control the processing performed by the friend device 51.

[0201] (4-2) When the inquiry unit 51CD acquires the non-friend key information DKN, the inquiry unit 51CD detects that there is a request to register the non-friend key KN. Therefore, when the friend device 51 accepts the registration request D31 of the non-friend key KN in the series of processes shown in FIG. 7 , the inquiry unit 51CD transmits an acceptance request CD to the owner device 40.

[0202] (Other Embodiments) The above-described embodiments can be modified as follows: The above-described embodiments and the following modifications can be combined with each other to the extent that no technical contradiction occurs.

[0203] The vehicle 20 does not need to have some of the BLE module 23, the UWB module 24, and the NFC module 25. As long as the vehicle 20 has at least one of these modules, it can perform short-range wireless communication with the device 30. The vehicle 20 is not limited to these modules, and it is sufficient that the vehicle 20 has a module that performs short-range wireless communication with the device 30.

[0204] The digital key-related matters in the above embodiments do not have to comply with the CCC. The vehicle management device 26 is not limited to a digital key ECU. For example, the vehicle management device 26 may be a central ECU that manages multiple ECUs in the vehicle 20.

[0205] In each of the above embodiments, the management server 70 includes an execution device 71, which is a processing circuit including one or more processors that execute various processes according to a computer program (software). However, the management server 70 may also include a processing circuit including one or more dedicated hardware circuits, such as an application-specific integrated circuit (ASIC), that executes at least some of the various processes. Alternatively, the management server 70 may include a processing circuit including a combination of one or more processors and one or more dedicated hardware circuits. The processor includes a CPU and memory, such as RAM and ROM. The memory stores program code or instructions configured to cause the CPU to execute processes. The memory, i.e., computer-readable medium, includes any available medium accessible by a general-purpose or dedicated computer. The same applies to the device 30 and the vehicle management device 26.

[0206] The device 30 is not limited to a smartphone. The device 30 may be a smartwatch. The device 30 may be a predetermined server. In this case, the predetermined server may include the device 30. For example, if a rental business operator or a sharing business operator is the owner of the vehicle 20, the owner device 40 may be included in the predetermined server. For example, the friend device 51 may be included in the predetermined server.

[0207] In each of the above embodiments, digital keys are arranged in a hierarchy of owner keys KO, friend keys KF, and non-friend keys KN, with the higher the hierarchy, the greater the authority assigned to the digital key. Digital keys do not necessarily have to be set so that the higher the hierarchy, the greater the authority assigned to the key. For example, the same authority may be assigned to the three hierarchical levels of the owner keys KO, friend keys KF, and non-friend keys KN.

[0208] The device server 60 does not have to be provided for each type of device 30. It is sufficient that multiple devices 30 and the management server 70 are capable of wireless communication. The device server 60 may be omitted. It is sufficient that multiple devices 30 and the management server 70 are capable of direct wireless communication.

[0209] The management server 70 may be configured with multiple servers. For example, the management server 70 may be configured with a server that stores the database DB and a server that executes the server program PS. For example, the management server 70 may be configured with a server that communicates with the vehicle 20 and a server that communicates with the device server 60, and these servers may be able to communicate with each other.

[0210] The management server 70 does not need to store the database DB. The management server 70 only needs to manage at least one digital key in the management system 10.

[0211] The share device 50 has a function to receive the share key KS as in the above embodiment. A device 30 having a function to receive a digital key, such as the share device 50, is sometimes called a receiver device.

[0212] The non-friend device 52 may be able to transmit a request to register a new non-friend key KN. In other words, the share device 50 may transmit a request to register a new non-friend key KN regardless of whether it is a friend device 51 or a non-friend device 52. In this case, the management system 10 may register the new non-friend key KN by the series of processes shown in FIG. 7 .

[0213] In each of the above embodiments, the first device corresponds to the owner device 40, the second device corresponds to the friend device 51, and the third device corresponds to the non-friend device 52. The first digital key corresponds to the owner key KO, the second digital key corresponds to the friend key KF, and the third digital key corresponds to the non-friend key KN.

[0214] As in the above modified example, assume that a new non-friend key KN is registered based on a registration request from the non-friend device 52. In this case, there is a new non-friend device 52 that stores non-friend key information DKN indicating the new non-friend key KN. In this modified example, the first device may correspond to the friend device 51, the second device may correspond to the non-friend device 52, and the third device may correspond to the new non-friend device 52. The first digital key may correspond to the friend key KF, the second digital key may correspond to the non-friend key KN, and the third digital key may correspond to the new non-friend key KN.

[0215] In the first embodiment, the inquiry unit 70CD may detect that a request for registration of a non-friend key KN has been made, regardless of whether or not the key track request D33 has been received. For example, the inquiry unit 70CD may detect that a request for registration of a non-friend key KN has been made by separately acquiring a signal indicating that registration has been requested from the friend device 51 or the third device 30C.

[0216] In the first embodiment, when the execution unit 70RA does not allow the management server 70 to register the non-friend key KN, the management server 70 may store information indicating the shared device 50 that indicates the non-friend key KN in the database DB. In this case, after detecting a state in which the authentication information AT of the non-friend key KN is not stored in the vehicle 20, the management server 70 may delete the information indicating the shared device 50 that indicates the non-friend key KN from the database DB.

[0217] In the first embodiment, when the execution unit 70RA does not allow the management server 70 to register the non-friend key KN, the management server 70 may send a storage request D34 to the vehicle 20. In this case, the management server 70 may send a request to the vehicle 20 to delete the authentication information AT stored by the storage request D34. The management server 70 may cause the vehicle management device 26 to eliminate the state in which the authentication information AT of the target non-friend key KN is stored.

[0218] When the execution unit 70RA allows the management server 70 to register a non-friend key KN, the management server 70 does not need to store information indicating the shared device 50 that indicates the non-friend key KN that has been permitted to be registered in the database DB. Even in this case, if the vehicle management device 26 stores the authentication information AT of the non-friend key KN and the non-friend device 52 stores the non-friend key information DKN, the non-friend key KN is in a usable state.

[0219] The processing performed by the execution unit 70RA when not allowing registration of a non-friend key KN is not limited to the example in the first embodiment. For example, when the execution unit 70RA does not allow registration of a non-friend key KN, the execution unit 70RA may send a request to the vehicle 20 to delete the authentication information AT that was once stored. In this case, when the execution unit 70RA allows registration of a non-friend key KN, the execution unit 70RA does not need to send a request to the vehicle 20 to delete the authentication information AT that was once stored.

[0220] The execution unit 70RA may allow the registration of the non-friend key KN after transmitting the storage request D34. In this case, the execution unit 70RA does not need to transmit the storage request D34 when the registration of the non-friend key KN is allowed.

[0221] In the second embodiment, the inquiry unit 20CD may detect that a request for registration of the non-friend key KN has been made without receiving the storage request D34. For example, the inquiry unit 20CD may detect that a request for registration of the non-friend key KN has been made by separately acquiring a signal indicating that registration has been requested from the friend device 51 or the third device 30C.

[0222] The processing performed by the execution unit 20RA when not allowing registration of a non-friend key KN is not limited to the example of the second embodiment. For example, when the execution unit 20RA does not allow registration of a non-friend key KN, the execution unit 20RA may delete the authentication information AT that was once stored. In this case, when the execution unit 20RA allows registration of a non-friend key KN, the execution unit 20RA does not need to delete the authentication information AT that was once stored.

[0223] The execution unit 20RA may allow the registration of the non-friend key KN after receiving the storage request D34. In this case, when the execution unit 20RA allows the registration of the non-friend key KN in the vehicle 20, the vehicle management device 26 does not need to store the authentication information AT again in accordance with the storage request D34.

[0224] When the execution unit 20RA does not allow the registration of the non-friend key KN to the vehicle 20, the vehicle management device 26 may store the authentication information AT of the non-friend key KN if it has received the storage request D34. In this case, when the execution unit 20RA does not allow the registration of the non-friend key KN, it simply causes the vehicle management device 26 to delete the authentication information AT of the target non-friend key KN.

[0225] In the third embodiment, the owner device 40 may have the inquiry unit 30CD and the execution unit 30RA. For example, when the friend device 51 has the inquiry unit 30CD, the inquiry unit 30CD may detect that there is a request to register the non-friend key KN when generating the non-friend key information DKN.

[0226] In the third embodiment, the inquiry unit 30CD may detect that a request for registration of the non-friend key KN has been made without acquiring the non-friend key information DKN. For example, the inquiry unit 30CD may detect that a request for registration of the non-friend key KN has been made by separately acquiring a signal indicating that registration has been requested from the friend device 51, etc. For example, the inquiry unit 30CD may detect that a request for registration of the non-friend key KN has been made by acquiring the invitation information IV2.

[0227] The processing performed by the execution unit 30RA when not allowing registration of a non-friend key KN is not limited to the example of the third embodiment. For example, when the execution unit 30RA does not allow registration of a non-friend key KN, the execution unit 30RA may delete the non-friend key information DKN that was once stored. In this case, when the execution unit 30RA allows registration of a non-friend key KN, the execution unit 30RA does not need to delete the non-friend key information DKN that was once stored.

[0228] When the execution unit 30RA allows the non-friend device 52 to register the non-friend key KN, the non-friend device 52 does not need to send the key track request D33 to the management server 70. In this case, the non-friend device 52 only needs to store the authentication information AT by receiving the storage request D34 from the vehicle 20. For example, the non-friend device 52 may separately send the authentication package ATP and the storage request D34 to the vehicle 20.

[0229] When the execution unit 30RA does not allow the non-friend device 52 to register the non-friend key KN, the non-friend device 52 may send a key track request D33 to the management server 70. In this case, the execution unit 30RA may delete the non-friend key information DKN. The execution unit 30RA may send a completion notification M51 indicating that the deletion of the non-friend key information DKN has been completed.

[0230] In each of the above embodiments, the execution unit does not need to store the third digital key and the third device 30C in association with each other in the database DB during the registration process. In other words, the execution unit does not need to update the database DB.

[0231] In the second embodiment, a device included in the vehicle 20 other than the vehicle management device 26 may have the query unit and the execution unit. In the second embodiment, it is sufficient that the vehicle 20 has the query unit and the execution unit.

[0232] The timing at which the inquiry unit inquires of the first device 30A about whether to accept the registration of the third digital key is not limited to the examples in the above embodiments. The inquiry unit may make the inquiry when a new third digital key is to be registered.

[0233] The method by which the inquiry unit inquires of the first device 30A about whether to accept the registration of the third digital key is not limited to sending the consent request CD in the above embodiments. The inquiry unit may make the inquiry by sending a predetermined message.

[0234] In each of the above embodiments, the query unit and the execution unit do not have to be included in the same device. For example, the management server 70 may include the query unit 70CD, and the vehicle management device 26 may include the execution unit 70RA.

[0235] The query unit and the execution unit may be included in a device different from the management server 70, the vehicle management device 26, and the shared device 50. For example, in the first embodiment, the external server is the management server 70, but the external server may be a server different from the management server 70.

[0236] The memory unit 70M that stores the database DB does not have to be provided in the management server 70. If the management system 10 has the memory unit 70M, for example, the vehicle management device 26 or the device 30 may have the memory unit 70M.

[0237] The management system 10 does not need to have other functional units as long as it includes at least an inquiry unit and an execution unit. The management system 10 is not limited to a system including the vehicle 20, the device 30, and the management server 70. For example, the system may be a computer including an inquiry unit and an execution unit.

Claims

1. A system for managing multiple digital keys that can be used for a vehicle, wherein the multiple digital keys include a first digital key registered in a first device, a second digital key registered in a second device based on a request from the first device, and a third digital key; the system comprises: an inquiry unit configured to, when the second device newly registers the third digital key, inquire of the first device as to whether or not to accept the registration of the third digital key; and an execution unit configured to execute registration processing for the third digital key if acceptance information indicating acceptance of the registration of the third digital key is received, and not execute the registration processing if the acceptance information is not received.

2. The system described in claim 1, wherein the vehicle has a storage unit configured to store authentication information for authenticating the third digital key when the third digital key is used, and the execution unit is configured to send a storage request to the vehicle to request storage of the authentication information during the registration process.

3. The system according to claim 1, further comprising a storage unit configured to store a database in which the vehicle and a device to which each of the plurality of digital keys is registered are associated, and the execution unit is configured to store the third digital key and the third device to which the third digital key is registered in the database in association with each other during the registration process.

4. The system described in claim 3, wherein the inquiry unit is configured to, when receiving a key track request from the second device requesting an update of the database, inquire of the first device as to whether or not to approve the registration of the third digital key.

5. The system according to any one of claims 1 to 4, wherein an external server located outside the vehicle comprises the query unit and the execution unit.

6. The system described in any one of claims 1 to 3, wherein the vehicle comprises: a storage unit configured to store authentication information for authenticating the third digital key when the third digital key is used; and a receiving unit configured to receive a storage request requesting storage of the authentication information; and the inquiry unit configured, when the receiving unit receives the storage request, to inquire of the first device whether or not to approve registration of the third digital key.

7. The system according to claim 6, wherein the execution unit is provided in the vehicle, and the execution unit is configured to store the authentication information in the storage unit in accordance with the storage request when the execution unit receives the consent information.

8. The system according to claim 7, wherein the execution unit is configured to, if the consent information is not received, not store the authentication information in the storage unit even if the storage request is received.

9. The system according to any one of claims 1 to 3, wherein the second device comprises the query unit and the execution unit.

10. The system according to claim 9, wherein when the second device accepts a request to register the third digital key, the inquiry unit is configured to inquire of the first device whether or not to approve the registration of the third digital key.

11. A management server that manages multiple digital keys that can be used for a vehicle, the multiple digital keys including a first digital key registered in a first device, a second digital key registered in a second device based on a request from the first device, and a third digital key; the management server comprising: an inquiry unit configured to, when the second device newly registers the third digital key, inquire of the first device as to whether or not to accept the registration of the third digital key; and an execution unit configured to execute registration processing for the third digital key if acceptance information indicating acceptance of the registration of the third digital key is received, and not execute the registration processing if the acceptance information is not received.

12. A vehicle management device that manages multiple digital keys that can be used for a vehicle, wherein the multiple digital keys include a first digital key registered in a first device, a second digital key registered in a second device based on a request from the first device, and a third digital key; the vehicle management device comprising: an inquiry unit configured to, when the second device newly registers the third digital key, inquire of the first device as to whether or not to accept the registration of the third digital key; and an execution unit configured to execute registration processing for the third digital key if acceptance information indicating acceptance of the registration of the third digital key is received, and not execute the registration processing if the acceptance information is not received.

13. A management method performed by a system configured to manage multiple digital keys available for a vehicle, wherein the multiple digital keys include a first digital key registered in a first device, a second digital key registered in a second device based on a request from the first device, and a third digital key, the management method including the steps of: when the second device newly registers the third digital key, inquiring of the first device as to whether or not to accept the registration of the third digital key; executing registration processing for the third digital key if acceptance information indicating acceptance of the registration of the third digital key is received; and not executing the registration processing if the acceptance information is not received.

14. A program executed by a computer configured to manage multiple digital keys available for a vehicle, the multiple digital keys including a first digital key registered in a first device, a second digital key registered in a second device based on a request from the first device, and a third digital key, the program causing the computer to: when the second device newly registers the third digital key, inquire of the first device as to whether or not to accept the registration of the third digital key; execute registration processing for the third digital key if consent information indicating consent to the registration of the third digital key is received; and not execute the registration processing if the consent information is not received.

Images