Management server, management method, management program, and management system

Abstract

To suppress the occurrence of an event that a digital key cannot be registered when an owner tries to register the digital key.SOLUTION: The management server 70 is capable of communicating with the vehicle 20 storing information related to the digital key and with the plurality of devices storing information related to the digital key registered for the vehicle 20, and manages registration of the digital key. The management server 70 transmits information related to the digital key to the vehicle 20 when registration of a new digital key is requested from a share device, which is a device different from the device belonging to the owner of the vehicle 20, among the plurality of devices. When the difference DF between the maximum number of digital keys that can be registered for the vehicle 20 and the number of pieces of information related to the digital key stored by the vehicle 20 is equal to or less than the predetermined number PN, the management server 70 does not transmit information related to the digital key to the vehicle 20 even if registration of a new digital key is requested from the share device.SELECTED DRAWING: Figure 8

Description

[Technical Field]

[0001] The present invention relates to a management server, a management method, a management program, and a management system. [Background technology]

[0002] Patent Document 1 describes a management system. The management system includes a vehicle, multiple devices, and a management server. The vehicle stores authentication information for authenticating a digital key. The device stores key information indicating the digital key. The management server is capable of communicating with the devices and the vehicle and manages the registration of the digital key. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Publication No. 2024-1720 Summary of the Invention [Problem to be solved by the invention]

[0004] There are two types of digital keys that can be registered to a device. The first is an owner key, which is registered to an owner device belonging to the vehicle owner. The second is a shared key, which is registered to a device other than the owner device upon request from a device on the management system that includes the owner device. In the management system, the owner device and a shared device that stores the key information of the shared key can request the registration of a new shared key.

[0005] In the management system, there is a limit to the amount of authentication information that a vehicle can store. As mentioned above, the shared key can be registered not only by the owner device but also by request from the shared device. Therefore, even if the owner tries to register a digital key, there is a risk that registration will not be possible. [Means for solving the problem]

[0006] A management server that solves the above problems is capable of communicating with a vehicle that stores information about digital keys and with multiple devices that store information about the digital keys registered to the vehicle, and manages the registration of the digital keys. The management server includes an execution device and a communication module. When a request for registration of a new digital key is received from a shared device that is one of the multiple devices and is different from a device belonging to the vehicle's owner, the execution device controls the communication module to send information about the digital key to the vehicle. When the difference between the maximum number of digital keys that can be registered for the vehicle and the amount of information about the digital keys stored in the vehicle is equal to or less than a predetermined number, the management server controls the communication module so that the execution device does not send information about the digital key to the vehicle, even if a request for registration of a new digital key is received from the shared device.

[0007] A management method for solving the above problem is a management method that manages information transmitted by a management server that is capable of communicating with a vehicle that stores information about the digital keys and with multiple devices that store information about the digital keys registered to the vehicle, and that transmits information about the digital keys to the vehicle when registration of a new digital key is requested from a shared device among the multiple devices that is different from the device belonging to the vehicle owner.This management method includes a step of controlling the management server not to transmit information about the digital keys when a difference between the maximum number of digital keys that can be registered for the vehicle and the amount of information about the digital keys stored in the vehicle is equal to or less than a predetermined number, even if registration of a new digital key is requested from the shared device.

[0008] The management program for solving the above problem is executed by a management server that can communicate with a vehicle that stores information about digital keys and with multiple devices that store information about the digital keys registered for the vehicle, and that transmits information about the digital keys to the vehicle when registration of a new digital key is requested from a shared device that is one of the multiple devices and is different from the device belonging to the vehicle owner.This management program causes the management server to not transmit information about the digital keys even when registration of a new digital key is requested from the shared device when the difference between the maximum number of digital keys that can be registered for the vehicle and the amount of information about the digital keys stored in the vehicle is equal to or less than a predetermined number.

[0009] A management system for solving the above problems includes a vehicle that stores information about digital keys, multiple devices that store information about the digital keys registered to the vehicle, and a management server that can communicate with the vehicle and the multiple devices and manages the registration of the digital keys. In this management system, the management server transmits information about the digital key to the vehicle when a request for registration of a new digital key is received from a shared device that is one of the multiple devices and is different from the device belonging to the vehicle's owner. In this management system, when the difference between the maximum number of digital keys that can be registered to the vehicle and the amount of information about the digital keys stored in the vehicle is equal to or less than a predetermined number, the management server does not transmit information about the digital key to the vehicle even when a request for registration of a new digital key is received from the shared device. [Effects of the Invention]

[0010] The above-described management server, management method, management program, and management system can prevent an event from occurring in which an owner is unable to register a digital key when attempting to do so. [Brief explanation of the drawings]

[0011] [Figure 1] FIG. 1 is a schematic diagram illustrating a management system according to an embodiment. [Figure 2] FIG. 2 is a schematic diagram showing owner key information in the management system of FIG. [Figure 3] FIG. 3 is a schematic diagram showing shared key information in the management system of FIG. [Figure 4] FIG. 4 is a schematic diagram showing data in a database in the management system of FIG. [Figure 5] 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. [Figure 6] 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. [Figure 7] FIG. 7 is an explanatory diagram showing a series of processes performed by the management system of FIG. 1 when a request for registration of a non-friend key is made. [Figure 8] FIG. 8 is an explanatory diagram showing a series of processes that the management system of FIG. 1 performs after a request for registration of a non-friend key is made. [Figure 9] FIG. 9 is an image showing that a digital key cannot be registered and the reason why it cannot be registered. DETAILED DESCRIPTION OF THE INVENTION

[0012] An embodiment of a management system will be described below with reference to the drawings. <Outline of Management System 10> As shown in FIG. 1, a 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. There is a standard for digital keys, 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 has 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 communication with the device 30 using BLE communication. The UWB module 24 communicates with the device 30 using UWB communication. The UWB module 24 measures the distance between the device 30 and the vehicle 20. The NFC module 25 performs short-range communication with the device 30 using 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 and a storage device 28. The storage device 28 stores a vehicle program PV and authentication information AT. The vehicle program PV is executed by the execution device 27, 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 processing related to the storage and deletion of the authentication information AT.

[0017] Note that authenticating a digital key means enabling the vehicle 20 to be controlled by the digital key. For example, when the vehicle management device 26 authenticates the digital key, the vehicle management device 26 enables the vehicle 20 to be unlocked. Also, for example, when the vehicle management device 26 authenticates the digital key, the vehicle management device 26 enables 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, 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 communication with the vehicle 20 by BLE communication. The UWB module 34 performs short-range communication with the vehicle 20 by UWB communication. The NFC module 35 performs short-range communication with the vehicle 20 by 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 the functions of 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 the storage and deletion of 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. The owner device 40 belongs to the owner of the vehicle 20.

[0024] 2, the owner key information DKO has 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, the ID of the vehicle 20. The intra-device key identification information ST2 is used to manage the digital key within the device 30. The intra-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, which is the public key of the device 30. Note that 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, which is the public key of the vehicle 20. Authorization public key information ST8 indicates an already authorized vehicle public key PKV.

[0028] As shown in Fig. 1, the shared device 50 stores shared key information DKS indicating a shared key KS as key information DK. The shared device 50 is a device 30 separate from the owner device 40. The shared key KS is a digital key that can be registered in multiple numbers for one vehicle 20 when registering the digital key to enable use of the digital key. In other words, multiple shared keys KS can exist for one vehicle 20.

[0029] The multiple shared devices 50 include a friend device 51 and a non-friend device 52. The friend device 51 stores, as the shared key information DKS, friend key information DKF indicating a friend key KF. The non-friend device 52 stores, as the shared key information DKS, non-friend key information DKN indicating a non-friend key KN. In other words, the types of shared keys KS include a friend key KF and a non-friend key KN. The friend key KF is a shared key KS registered based on a registration request D21 directly from the owner device 40, as will be described later. The non-friend key KN is a shared key KS registered based on a registration request D31 from the friend device 51, as will be described later. In other words, the non-friend key KN is a shared key KS that is not a friend key KF, among the shared keys KS.

[0030] The state in which the digital key is registered means that the digital key is usable, i.e., the vehicle 20 stores the authentication information AT and the device 30 stores the key information DK.

[0031] There is an upper limit to the number of pieces of authentication information AT that can be stored in the vehicle 20. Therefore, there is a maximum number of digital keys that can be registered for the vehicle 20 in the management system 10.

[0032] As shown in Fig. 3, the shared key information DKS has 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 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 information obtained by excluding device public key information ST6 from the owner key structure information STO.

[0033] 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.

[0034] The signature information ATP1 indicates that the shared device 50 is a legitimate party with which the digital key is shared. For example, in the case of the friend device 51, it indicates a signature by the owner device 40. The owner signature information indicates that the owner device 40 has signed the device public key PKD of the friend device 51, which is indicated by the device public key information ATP6. Also, for example, in the case of the non-friend device 52, it indicates a signature by the friend device 51. The friend signature information indicates that the friend device 51 has signed the device public key PKD of the non-friend device 52, which is indicated by the device public key information ATP6.

[0035] 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. For example, it is set as an identifiable name for each shared device 50 by operation from the owner device 40.

[0036] 1, the device server 60 relays communication between the devices 30 and the management server 70. A device server 60 is provided for each type of device 30. That is, the device server 60 with which a first type of device 30 communicates is 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.

[0037] Any of the device servers 60 relays communication with the management server 70, so that different types of devices 30 can communicate with the management server 70 via the device servers 60. Note that only one device server 60 is shown in FIG.

[0038] <Administration Server 70> The management server 70 manages the registration of 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, 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. The execution device 71 controls the communication module 73.

[0039] The storage device 72 stores a server program PS, a count program PC, and a database DB. When the server program PS is executed by the execution device 71, the execution device 71 registers a digital key in the database DB and deletes a digital key from the database DB.

[0040] The count program PC is executed by the execution device 71 to cause the execution device 71 to count the number of pieces of authentication information AT stored in the vehicle 20 and to perform control according to the number. In the database DB, for each of a plurality of digital keys, the corresponding vehicle 20 and the registered device 30 are associated with each other. In the database DB, data DA 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 key information DK indicating the digital key. The management server 70 manages the digital keys by saving the data DA in the database DB.

[0041] As shown in Figure 4, the data DA for one vehicle 20 includes the type of digital key registered to the vehicle 20, the registered devices 30, and the relationships between the registered devices 30. Hierarchical rankings are determined based on the type of digital key. From top to bottom, the hierarchy is arranged as follows: owner key KO, friend key KF, and non-friend key KN. The higher the hierarchy, the greater the authority set.

[0042] 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 hierarchy, the greater the authority, and therefore, for example, 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.

[0043] Furthermore, for example, the higher the hierarchy, the greater the authority, and therefore the wider the controllable range of the vehicle 20. The controllable range of the vehicle 20 indicates, for example, the possible controls among the engine start control of the vehicle 20, the power on control of the vehicle 20, and the unlocking and locking control of 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 the unlocking and locking control of the doors of the vehicle 20. More specifically, the controllable range of the vehicle 20 that the friend key KF can control is the above-mentioned three controls, whereas the controllable range of the vehicle 20 that the non-friend key KN can control is only the unlocking and locking control of the doors of the vehicle 20.

[0044] The following describes a state 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, respectively, are referred to as a first digital key to a seventh digital key.

[0045] In the data DA, the device 30 whose type of digital key is registered as the owner key KO 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.

[0046] In the data DA, the devices 30 whose digital key type is registered as a shared key KS 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.

[0047] More specifically, in the data DA, the devices 30 whose digital key type is registered as a friend key KF 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. In the data DA, the devices 30 whose digital key type is registered as a non-friend key KN are the third device 30C, the fourth device 30D, the sixth device 30F, and the seventh device 30G. That is, the fourth device 30D, the fifth device 30E, the sixth device 30F, and the seventh device 30G are non-friend devices 52.

[0048] In the data DA, 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.

[0049] In the data DA, 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.

[0050] In the data DA, 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.

[0051] In the data DA, 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.

[0052] In the data DA, 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.

[0053] 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 based on a registration request from the fifth device 30E. In other words, the seventh digital key is registered based on the fifth digital key.

[0054] In this way, the data DA stores the devices 30 registered as digital keys. When the device 30 is registered, information indicating the device 30 that made the request that caused the registration is linked to the device 30. The data DA also includes information indicating which digital key each digital key is registered under.

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

[0056] <Registering the Owner Key KO> 5, the management system 10 performs a series of processes to register the owner key KO. Among the devices 30 that do not store the key information DK indicating the owner key KO, the device 30 that is to be set as the owner device 40 is referred to as the first device 30A.

[0057] In the management system 10, when the owner key KO is registered, key information DK indicating the owner key KO is stored in the first device 30A. In the management system 10, when the owner key KO is registered, authentication information AT for authenticating the owner key KO is stored in the vehicle 20. As a result, the first device 30A becomes the owner device 40. Note that when the owner key KO is registered, it is assumed that an application is installed in the first device 30A.

[0058] 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 the process of 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.

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

[0060] 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.

[0061] 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 a secure channel. The generation data DC includes vehicle identification information ST1 and vehicle public key information indicating the vehicle public key PKV. Then, the first device 30A receives the generation data DC. Then, the first device 30A proceeds to step S14.

[0062] In step S14, the first device 30A generates owner key information DKO indicating the owner key KO. After that, the first device 30A advances the process 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. Thereafter, 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.

[0063] 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.

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

[0065] 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. Then, the first device 30A transmits the key track request D12 for the owner key KO to the management server 70 via the device server 60.

[0066] Thereafter, upon receiving the key track request D12, the management server 70 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 the first device 30A as the device 30 registered as the owner key KO in the data DA of the vehicle 20 in the database DB. This causes the management system 10 to complete the series of processes for the owner key KO.

[0067] <Friend Key KF Registration> 6, the management system 10 performs a series of processes to register a friend key KF. Among the devices 30 that do not store friend key information DKF, the device 30 that is designated as a friend device 51 through the series of processes is referred to as a second device 30B.

[0068] 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). Thereafter, the owner device 40 proceeds to the process of step S22.

[0069] In step S22, the owner device 40 acquires 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.

[0070] 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.

[0071] 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. Note that the validity start time information ATP3, expiration date information ATP4, and name information ATP5 are set by the owner device 40. Thereafter, the second device 30B proceeds to step S24.

[0072] In step S24, the second device 30B uses the share information SH1 to generate unsigned friend key information DKFN. The unsigned friend key information DKFN is friend key information DKF that does not include signature information ATP1. Specifically, the second device 30B generates each piece of information included in the acquired share information SH1 as the unsigned friend key information DKFN. The second device 30B then transmits to the owner device 40 a completion notification M21 indicating that the generated unsigned friend key information DKFN has been uploaded to the URL link, and a signature request D22 requesting a signature.

[0073] Thereafter, the owner device 40 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.

[0074] In step S25, the owner device 40 generates signature information ATP1. Specifically, the owner device 40 causes the HMI 32 to present the acquired unsigned 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 the operation is performed, the owner device 40 acquires a signature based on the operation. Thereafter, the owner device 40 proceeds to step S26.

[0075] In step S26, the owner device 40 adds the signature information ATP1 to the unsigned friend key information DKFN. As a result, the owner device 40 generates 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.

[0076] Thereafter, the second device 30B receives the completion notification M22. Thereafter, the second device 30B 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 becomes a friend device 51. Thereafter, the second device 30B proceeds to the process of step S28.

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

[0078] 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.

[0079] Specifically, the management server 70 verifies 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 indicates shared keys KS that include friend keys KF and non-friend keys 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.

[0080] 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. In detail, the management server 70 stores the second device 30B as a device 30 registered as a friend device 51 in the data DA of the vehicle 20 in the database DB. 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.

[0081] Thereafter, the management server 70 transmits the authentication package ATP of 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 also notifies the vehicle 20 that the device public key PKD has been signed by the owner device 40.

[0082] Thereafter, when the vehicle 20 receives the storage request D24 and the authentication package ATP from the management server 70, it 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.

[0083] 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 process of step S31. In the process of step S31, the second device 30B presents information indicating the completion of the registration of the friend key KF on 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 end the series of processes for registering the friend key KF.

[0084] <Request to register non-friend key KN> 7 and 8, the management system 10 performs a series of processes to register the non-friend key KN. Among the devices 30 that do not store the non-friend key information DKN, the device 30 that is designated as a non-friend device 52 by the series of processes is referred to as a third device 30C.

[0085] The series of processes in Figure 7 and the series of processes in Figure 8 are executed consecutively. In Figure 7, the management system 10 requests the registration of a non-friend key KN. In Figure 8, after the request for registration of a non-friend key KN is made, the management system 10 determines whether or not to register the non-friend key KN based on the number of pieces of authentication information AT stored in the vehicle management device 26.

[0086] First, with reference to FIG. 7, a manner in which a request to register a non-friend key KN is made will be described. When an operation to request registration of a non-friend key KN is executed in 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). Thereafter, the friend device 51 proceeds to the process of step S42.

[0087] In step S42, the friend device 51 acquires 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.

[0088] 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 third device 30C downloads the share information SH2 from the URL link.

[0089] 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. Note that the validity start time information ATP3, expiration date information ATP4, and name information ATP5 are set by the friend device 51. Thereafter, the third device 30C proceeds to step S44.

[0090] 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 include the signature information ATP1. Specifically, the third device 30C generates each piece of information included in the acquired share information SH2 as each piece of information in the unsigned non-friend key information DKNN. The third device 30C then transmits to the friend device 51 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.

[0091] Thereafter, the friend device 51 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 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.

[0092] In step S45, the friend device 51 generates signature information ATP1. Specifically, the friend device 51 causes the HMI 32 to present the acquired unsigned 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 acquires a signature based on the operation. Thereafter, the friend device 51 proceeds to step S46.

[0093] In step S46, the friend device 51 adds the signature information ATP1 to the unsigned non-friend key information DKNN. As a result, the friend device 51 generates non-friend key information DKN. Thereafter, the friend device 51 uploads the generated non-friend key information DKN to the URL link, which is the invitation information IV2. Then, the friend device 51 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.

[0094] 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 becomes a non-friend device 52. The third device 30C then proceeds to the process of step S48.

[0095] 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. At this time, 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.

[0096] Through this series of processes, the management system 10 requests the management server 70 to register the non-friend key KN. In this way, in the management system 10, the registration of the non-friend key KN is requested starting from the registration request D31 from the friend device 51. In other words, the friend device 51 requests the management server 70 to register the non-friend key KN for the third device 30C.

[0097] Thereafter, the management system 10 executes a series of processes shown in Fig. 8. Below, referring to Fig. 8, we will explain the series of processes that the management system 10 executes after the management server 70 receives the non-friend key information DKN and the key track request D33 for the non-friend key KN.

[0098] <Counting by the management server 70> As mentioned above, there is an upper limit to the number of pieces of authentication information AT that the vehicle 20 can store. In Figure 8, when the management server 70 is requested to register a non-friend key KN, it checks the number of pieces of authentication information AT stored in the vehicle 20 based on the count program PC. Then, the management server 70 executes processing according to the number of pieces of authentication information AT stored in the vehicle 20 using the count program PC.

[0099] When the management server 70 receives the 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 checks the number of pieces of authentication information AT stored in the vehicle 20.

[0100] The management server 70 stores in data DA the types of digital keys registered to the vehicle 20, the registered devices 30, and the relationships between the registered devices 30. The number of pieces of authentication information AT stored in the vehicle 20 matches the number of digital keys registered to the vehicle 20. The number of pieces of authentication information AT stored in the vehicle 20 also matches the number of devices 30 that store key information DK. Therefore, the management server 70 can confirm the number of pieces of authentication information AT stored in the vehicle 20 by referring to the database DB.

[0101] After confirming the number of pieces of authentication information AT stored in the vehicle 20, the management server 70 executes the process of step S50. In the process of step S50, the management server 70 calculates the difference DF. The difference DF is the difference between the maximum number that can be registered for the vehicle 20 and the number of pieces of authentication information AT, which is information related to digital keys, stored in the vehicle 20.

[0102] <Registering a non-friend key KN> If the difference DF is greater than the predetermined number PN, the management system 10 performs the processes of steps S51 to S53. The predetermined number PN is a reference number for determining whether the number of pieces of authentication information AT stored in the vehicle 20 is approaching an upper limit. The predetermined number PN is determined in advance by the user of the owner device 40, who is the owner of the vehicle 20. For example, the owner of the vehicle 20 specifies the predetermined number PN through the owner device 40.

[0103] In step S51, the management server 70 performs registration management of the non-friend key KN. 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 reject list. If the non-friend key KN is on the reject list, the management server 70 sends a notification to the third device 30C that the key track request D33 cannot be fulfilled.

[0104] 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 subject of the key track request D33 in the database DB. Specifically, the management server 70 stores the third device 30C in the data DA of the vehicle 20 in the database DB as a 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 the third device 30C as a device 30 having the non-friend key KN registered in response to the registration request D31 from the friend device 51.

[0105] Thereafter, the management server 70 transmits the authentication package ATP of 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 also notifies the vehicle 20 that the device public key PKD is signed by the friend device 51.

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

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

[0108] <Send registration failure notification M41> If the difference DF is equal to or smaller than the predetermined number PN, the management system 10 performs the processes of steps S60 and S61.

[0109] If the difference DF is equal to or less than the predetermined number PN, the management server 70 transmits a registration failure notification M41 to the third device 30C. The registration failure notification M41 is a signal indicating that the non-friend key KN requested to be registered cannot be registered. The registration failure notification M41 also includes a notification that the non-friend key KN requested to be registered cannot be registered because the difference DF is equal to or less than the predetermined number PN. In other words, the registration failure notification M41 notifies the vehicle 20 that a new non-friend key KN cannot be registered due to the number of pieces of authentication information AT stored in the vehicle 20.

[0110] Upon receiving the registration failure notification M41, the third device 30C performs processing in step S60. In step S60, the third device 30C presents to the HMI 32 information indicating that the non-friend key KN is not registerable and the reason for the registration failure. For example, the third device 30C presents to the HMI 32 the image shown in FIG. 9 indicating that the non-friend key KN is not registerable and the reason for the registration failure. At this time, the third device 30C presents to the HMI 32 that the reason for the registration failure is the number of pieces of authentication information AT stored in the vehicle 20. In other words, the user of the third device 30C is notified that a large number of digital keys have been registered for the vehicle 20.

[0111] Furthermore, the management server 70 transmits a registration failure notification M41 to the friend device 51 if the difference DF is equal to or smaller than the predetermined number PN. Upon receiving the registration failure notification M41, the friend device 51 performs processing in step S61. In step S61, the friend device 51 presents to the HMI 32 information indicating that the non-friend key KN is not registerable and the reason for the registration failure. For example, the friend device 51 presents to the HMI 32 the image shown in FIG. 9 indicating that the non-friend key KN is not registerable and the reason for the registration failure. At this time, the friend device 51 presents to the HMI 32 that the reason for the registration failure is the number of pieces of authentication information AT stored in the vehicle 20. In other words, the user of the friend device 51 is notified that a large number of digital keys have been registered for the vehicle 20. In this way, the management system 10 ends the series of processes when the difference DF is equal to or less than the predetermined number PN.

[0112] In this way, when the management server 70 is requested to register a non-friend key KN, it checks the difference DF, and if the difference DF is less than or equal to a predetermined number PN, it does not send the authentication package ATP that the vehicle 20 stores as authentication information AT.

[0113] <Operation of this embodiment> If the difference DF is equal to or less than the predetermined number PN, the execution device 71 of the management server 70 will not transmit the authentication information AT for the new shared key KS to the communication module 73 even if the shared device 50 requests registration of the new shared key KS. In other words, when the number of pieces of authentication information AT stored in the vehicle 20 is large, the management server 70 will not allow a new shared key KS to be registered in response to a request from the shared device 50.

[0114] <Effects of this embodiment> (1) The management server 70 prevents the number of pieces of authentication information AT stored in the vehicle 20 from reaching the upper limit without the owner's knowledge. As a result, the management server 70 can prevent the owner from being unable to register a digital key when attempting to do so.

[0115] (2) The execution device 71 of the management server 70 controls the communication module 73 to transmit authentication information AT, which is used by the vehicle 20 to authenticate the digital key, to the vehicle 20 as information related to the digital key. In this way, the management server 70 prevents the number of pieces of authentication information AT stored in the vehicle 20 from reaching the upper limit without the owner realizing it.

[0116] (3) The predetermined number PN can be set by the owner. As a result, the management server 70 can prevent new shared keys KS from being registered once the number of pieces of authentication information AT stored in the vehicle 20 reaches the number set by the owner.

[0117] (4) The management server 70 checks the difference DF when the shared device 50 requests registration of a new digital key. When the difference DF is equal to or less than a predetermined number PN, the execution device 71 of the management server 70 controls the communication module 73 so as not to transmit information related to the digital key.

[0118] When the management server 70 receives a request from the shared device 50 to register a new shared key KS, the management server 70 checks the difference DF and determines whether or not to transmit the authentication information AT. This allows the management server 70 to prevent the registration of a new shared key KS according to the number of pieces of authentication information AT stored in the vehicle 20.

[0119] (5) When the shared device 50 requests the registration of a new digital key for another device 30 and does not transmit information regarding the digital key, the execution unit 71 of the management server 70 controls the communication module 73 to transmit a notification to the other device 30 that the new digital key will not be registered.

[0120] The management server 70 does not transmit the authentication information AT to the vehicle 20, but instead transmits a notification to the other device 30 that the shared key KS will not be registered. This enables the management server 70 to notify the user of the other device 30 that the shared key KS cannot be registered.

[0121] (6) When sending a notification to another device 30 that the new digital key will not be registered, the execution unit 71 of the management server 70 controls the communication module 73 to send a notification to the other device 30 that the reason the new digital key will not be registered is the number of pieces of information about the digital key stored in the vehicle 20.

[0122] The management server 70 notifies the other devices 30 that the reason a new shared key KS cannot be registered is that the amount of authentication information AT stored in the vehicle 20 is increasing. This allows the management server 70 to notify the users of the other devices 30 of the reason why a new shared key KS cannot be registered, and to urge them to reduce the number of digital keys on the management system 10 by, for example, contacting the owner of the vehicle 20.

[0123] (7) When a shared device 50 requests the registration of a new digital key for another device 30 but does not send information about the digital key, the execution unit 71 of the management server 70 controls the communication module 73 to send a notification to the shared device 50 that requested the registration of a new digital key that the new digital key will not be registered.

[0124] The management server 70 does not transmit the authentication information AT to the vehicle 20, but instead transmits a notification to the share device 50 that requested registration of the share key KS that the share key KS will not be registered. This allows the management server 70 to notify the user of the share device 50 that requested registration of the share key KS that the share key KS cannot be registered.

[0125] (8) When sending a notification to the shared device 50 that has requested the registration of a new digital key that the new digital key will not be registered, the execution unit 71 of the management server 70 controls the communication module 73 to send a notification to the shared device 50 that the reason the new digital key will not be registered is the number of pieces of information about the digital key stored in the vehicle 20.

[0126] The management server 70 notifies the share device 50 that requested the registration of a new share key KS that the reason it cannot register a new share key KS is that the amount of authentication information AT stored in the vehicle 20 has increased. This enables the management server 70 to notify the user of the share device 50 of the reason why it cannot register a new share key KS, and to urge the user to reduce the number of digital keys on the management system 10 by, for example, contacting the owner of the vehicle 20.

[0127] (9) When the difference DF is equal to or less than the predetermined number PN, even if the shared device 50 requests registration of a new shared key KS, the management method does not transmit the authentication information AT for that shared key KS to the management server 70 (see FIG. 8). This prevents the number of pieces of authentication information AT stored in the vehicle 20 from reaching the upper limit without the owner realizing it. This makes it possible to prevent the occurrence of an event in which the owner is unable to register a digital key when attempting to do so.

[0128] (10) If the difference DF is equal to or less than the predetermined number PN, the count program PC, which is a management program, does not transmit the authentication information AT for the new shared key KS to the management server 70 even if the shared device 50 requests registration of the new shared key KS. This prevents the number of pieces of authentication information AT stored in the vehicle 20 from reaching the upper limit without the owner realizing it. This makes it possible to prevent the occurrence of an event in which the owner is unable to register a digital key when attempting to do so.

[0129] (11) If the difference DF is equal to or less than the predetermined number PN, the management system 10 does not transmit the authentication information AT for the new shared key KS to the management server 70 even if the shared device 50 requests registration of the new shared key KS. This prevents the number of pieces of authentication information AT stored in the vehicle 20 from reaching the upper limit without the owner realizing it. This makes it possible for the management system 10 to prevent the occurrence of an event in which the owner is unable to register a digital key when attempting to do so.

[0130] (12) In the management system 10, when the management server 70 receives a request from the shared device 50 to register a new digital key for another device 30 and does not transmit information about the digital key, the management server 70 transmits a notification to the other device 30 that the new digital key will not be registered. In the management system 10, the other device 30 displays a message that the new digital key will not be registered.

[0131] In the management system 10, the management server 70 does not send authentication information AT of the new shared key KS to the vehicle 20, but instead sends a notification to the other device 30 that the shared key KS will not be registered. Then, in the management system 10, the other device 30 displays a message that the shared key KS will not be registered. This allows the management system 10 to notify the user of the other device 30 that the shared key KS cannot be registered.

[0132] (13) In the management system 10, the management server 70 sends a notification to the other devices 30 that the reason for not registering a new digital key is the number of pieces of information related to the digital key stored in the vehicle 20. In the management system 10, the other devices 30 display a message that the reason for not registering a new digital key is the number of pieces of information related to the digital key stored in the vehicle 20.

[0133] The management system 10 notifies the user of the other device 30 that the reason a new shared key KS cannot be registered is that the amount of authentication information AT stored in the vehicle 20 is increasing. This allows the management system 10 to notify the user of the other device 30 of the reason a new shared key KS cannot be registered, and to urge the user to reduce the number of digital keys on the management system 10 by, for example, contacting the owner of the vehicle 20.

[0134] (14) In the management system 10, when the management server 70 receives a request from a shared device 50 to register a new digital key for another device 30 but does not transmit information about the digital key, the management server 70 sends a notification to the shared device 50 that requested registration of the new digital key that the new digital key will not be registered. In the management system 10, the shared device 50 that requested registration of the new digital key displays a message that the new digital key will not be registered.

[0135] In the management system 10, the management server 70 does not send authentication information AT of the new share key KS to the vehicle 20, but instead sends a notification to the share device 50 that requested registration of the new share key KS that the share key KS will not be registered. Then, in the management system 10, the share device 50 that requested registration of the share key KS displays that the share key KS will not be registered. This allows the management system 10 to notify the user who requested registration of the new share key KS that the share key KS cannot be registered.

[0136] (15) In the management system 10, the management server 70 sends a notification to the shared device 50 that has requested registration of a new digital key, indicating that the reason the new digital key has not been registered is because of the number of pieces of information related to the digital key stored in the vehicle 20. In the management system 10, the shared device 50 that has requested registration of a new digital key displays a message indicating that the reason the new digital key has not been registered is because of the number of pieces of information related to the digital key stored in the vehicle 20.

[0137] The management system 10 notifies the user who requested registration of the shared key KS that the reason the new shared key KS cannot be registered is that the amount of authentication information AT stored in the vehicle 20 is increasing. This allows the management system 10 to notify the user who requested registration of the reason the new shared key KS cannot be registered, and to urge the user to reduce the number of digital keys on the management system 10 by contacting the owner of the vehicle 20, for example.

[0138] (Other embodiments) This embodiment can be modified as follows: Each embodiment and the following modifications can be combined with each other within the scope of technical compatibility.

[0139] <Management System 10> The vehicle 20 may not have all of the BLE module 23, the UWB module 24, and the NFC module 25. As long as the vehicle 20 has at least one module, it can perform short-range communication with the device 30. Furthermore, the vehicle 20 is not limited to these modules, and may have any module that performs short-range communication with the device 30.

[0140] 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, it may be a central ECU that manages multiple ECUs in the vehicle 20.

[0141] The vehicle management device 26 may be configured as a circuit including one or more processors that execute various processes according to a computer program (software). The vehicle management device 26 may also be configured as a circuit including one or more dedicated hardware circuits, such as an application-specific integrated circuit (ASIC), that execute at least some of the various processes, or a combination thereof. 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 the processes. The memory, i.e., computer-readable medium, includes any available medium that can be accessed by a general-purpose or dedicated computer. The same applies to the device 30 and the management server 70.

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

[0143] 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.

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

[0145] 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.

[0146] The management server 70 may be configured with multiple servers. For example, it may be configured with a server that stores the database DB and a server that executes the server program PS. Alternatively, it 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.

[0147] The management server 70 does not need to store the database DB. The management server 70 only needs to manage, for at least one digital key in the management system 10, a combination of the key information DK of the device 30 and the authentication information AT of the vehicle management device 26.

[0148] <Various information> The information related to the digital key stored in the vehicle 20 is not limited to the authentication information AT. The authentication information AT is not limited to the examples of the above embodiments, as long as it is information for authenticating the digital key when using the digital key. For example, the authentication information AT may be a common key shared by the vehicle management device 26 and the device 30. Also, for example, the authentication information AT may be a common secret key.

[0149] The configuration of the information included in the key information DK is not limited to the example in the above embodiment. For example, the owner key information DKO does not have to include the slot identification information ST4. Also, for example, the key information DK may include information indicating the type of digital key. The type of digital key is, for example, information indicating one of the owner key KO, friend key KF, and non-friend key KN.

[0150] The database DB may include information indicating the type of the device 30. The type of the device 30 is information indicating, for example, a smartphone, a smartwatch, or a predetermined server as in the above-described modified example.

[0151] The structure of the data DA in the database DB is not limited to the examples in the above embodiments, as long as the database DB contains the information necessary for the management server 70 in the management system 10 to manage it.

[0152] In the database DB, the authority may be set for each digital key, rather than being uniformly determined according to the type of digital key. Also, the authority may not be determined in the database DB.

[0153] <The process for registering a digital key> The series of processes for registering the owner key KO is not limited to the examples in the above embodiments. For example, the owner device 40 may store the owner key information DKO by transmitting and receiving information such as the generated data DC between the vehicle 20 and the first device 30A via the management server 70, even if pairing is not performed by the process of step S12. The series of processes for registering the owner key KO may be modified as appropriate to suit the structure of the information included in the owner key information DKO and the structure of the information included in the authentication information AT.

[0154] The series of processes for registering the friend key KF is not limited to the examples in the above embodiments. For example, the management server 70 may update the database DB by processing in step S29 after transmitting the authentication package ATP and the storage request D24 to the vehicle 20. The series of processes for registering the friend key KF may be modified as appropriate to suit the structure of the information contained in the friend key information DKF and the structure of the information contained in the authentication information AT.

[0155] The series of processes for registering a non-friend key KN is not limited to the examples in the above embodiments. The order of the processes for registering a friend key KF may be different. The series of processes for registering a non-friend key KN may be modified as appropriate to suit the structure of the information contained in the non-friend key information DKN and the structure of the information contained in the authentication information AT.

[0156] The types of digital keys do not have to include non-friend keys KN. In other words, in the management system 10, the shared keys KS may only be friend keys KF. The non-friend device 52 may be able to send a request to register a new non-friend key KN. That is, the sharing device 50 may send 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.

[0157] In this case, after the non-friend device 52 requests registration, the management server 70 checks the number of pieces of authentication information AT stored in the vehicle management device 26, as in Fig. 8. Then, the management server 70 executes processing based on the number of pieces of authentication information AT stored, based on the count program PC, as in Fig. 8. At this time, if the management server 70 sends a registration failure notification M41, it sends it to the third device 30C and the non-friend device 52 that requested registration of the non-friend key KN for the third device 30C.

[0158] <Counted by management server 70> In the above embodiment, the predetermined number PN is determined in advance by the owner of the vehicle 20. In the above embodiment, the owner of the vehicle 20 refers to the user of the owner device 40. The owner of the vehicle 20 is not limited to the user of the owner device 40. For example, a user of a shared device 50 who has been granted the same authority as the owner device 40 may determine the predetermined number PN as the owner of the vehicle 20.

[0159] Furthermore, the predetermined number PN does not have to be determined by the owner of the vehicle 20. For example, the predetermined number PN may be determined in advance by the user of the shared device 50, rather than by the owner of the vehicle 20. Furthermore, for example, the predetermined number PN may be determined in advance by the provider of the vehicle 20 or the management server 70.

[0160] In the above embodiment, the management server 70 checks the differential DF when a request to register a non-friend key KN is received. The timing at which the management server 70 checks the differential DF is not limited to the above embodiment.

[0161] For example, the management server 70 may check the difference DF after the digital key is registered in the management system 10. Alternatively, the management server 70 may check the difference DF periodically, regardless of whether the digital key has been registered. In these cases, if the difference DF is equal to or less than a predetermined number PN, the management server 70 will not transmit the authentication information AT thereafter, even if the shared device 50 requests registration of the shared key KS.

[0162] In the above embodiment, the management server 70 transmits a registration impossible notification M41 to the third device 30C when the management server 70 does not transmit the authentication information AT to the vehicle 20. The management server 70 does not have to transmit the registration impossible notification M41 to the third device 30C.

[0163] Furthermore, the registration failure notification M41 does not have to include information indicating the reason why the non-friend key KN cannot be registered, in which case the third device 30C does not display the reason why the registration cannot be performed. In the above embodiment, when the management server 70 does not transmit the authentication information AT to the vehicle 20, the management server 70 transmits the registration impossible notification M41 to the friend device 51. The management server 70 does not have to transmit the registration impossible notification M41 to the friend device 51.

[0164] The registration failure notification M41 does not have to include information indicating the reason why the non-friend key KN cannot be registered. In this case, the friend device 51 does not display the reason why the registration cannot be performed.

[0165] In the above embodiment, the management server 70 checks the differential DF when a request to register a new shared key KS is received from the shared device 50. Then, if the differential DF is equal to or less than a predetermined number PN, the management server 70 does not send the authentication package ATP.

[0166] On the other hand, when requested to register a new shared key KS, the management server 70 may transmit the authentication package ATP and check the difference DF after transmitting the authentication package ATP. In this case, when the difference DF is equal to or less than the predetermined number PN minus 1, the management server 70 requests the vehicle 20 to delete the stored authentication package ATP, and then transmits a registration failure notification M41 to the third device 30C and the friend device 51.

[0167] In this case as well, a configuration can be realized in which the management server 70 does not transmit authentication information AT for a new shared key KS when the difference DF is equal to or less than a predetermined number PN. When the management server 70 is requested to register a new shared key KS, it may check the difference DF before transmitting the authentication information AT. When the difference DF is equal to or less than a predetermined number PN, the management server 70 may first transmit authentication information AT for the new shared key KS and then request that the transmitted authentication information AT be deleted.

[0168] <Additional Notes> The technical ideas that can be understood from the above-described embodiment and modified examples will be described. [Appendix 1] A management server that can communicate with a vehicle that stores information about digital keys and with multiple devices that store information about the digital keys registered for the vehicle and manages the registration of the digital keys, comprising a communication module and an execution device, wherein when registration of a new digital key is requested from a shared device that is one of the multiple devices and is different from a device belonging to the owner of the vehicle, the execution device controls the communication module to send information about the digital key to the vehicle, and when the difference between the maximum number of digital keys that can be registered for the vehicle and the amount of information about the digital keys stored in the vehicle is less than a predetermined number, the management server controls the communication module so that the execution device does not send information about the digital key to the vehicle even if registration of a new digital key is requested from the shared device.

[0169] [Appendix 2] The management server described in Appendix 1, in which the execution device controls the communication module to transmit authentication information used by the vehicle to authenticate the digital key as information regarding the digital key to the vehicle.

[0170] [Supplementary Note 3] The management server according to Supplementary Note 1 or Supplementary Note 2, wherein the predetermined number can be set by the owner. [Appendix 4] A management server according to any one of Appendices 1 to 3, which, when requested by the shared device to register a new digital key, checks the difference, and when the difference is less than a predetermined number, the execution device controls the communication module so as not to send information about the digital key.

[0171] [Appendix 5] The management server according to any one of Appendices 1 to 4, wherein when the shared device requests the registration of a new digital key for another device and information regarding the digital key is not sent, the execution device controls the communication module to send a notification to the other device that the new digital key will not be registered.

[0172] [Appendix 6] The management server described in Appendix 5, wherein when sending a notification to the other device that the new digital key will not be registered, the execution device controls the communication module to send a notification to the other device that the reason the new digital key will not be registered is the number of pieces of information about the digital key stored in the vehicle.

[0173] [Appendix 7] The management server according to any one of Appendices 1 to 6, wherein when the shared device requests the registration of a new digital key for another device and does not send information about the digital key, the execution device controls the communication module to send a notification to the shared device that requested the registration of the new digital key that the new digital key will not be registered.

[0174] [Appendix 8] The management server described in Appendix 7, wherein when sending a notification to the shared device that requested registration of the new digital key that the new digital key will not be registered, the execution device controls the communication module to send a notification to the shared device that the reason the new digital key will not be registered is the number of pieces of information about the digital key stored in the vehicle. [Explanation of symbols]

[0175] 10...Management system 20...Vehicle 21...Communication module 26...Vehicle management device 27...Execution device 28…Storage device 30…Devices 31...Communication module 36...Execution device 37…Storage device 40...Owner device 50...Shared devices 51...Friend Device 52...Non-Friendly Device 60...Device Server 70...Administration server 71...Execution device 72...Storage device 73...Communication module AT…Authentication information DF…Difference DK...Key information DKO…Owner key information DKS…Share Key Information KF...Friend Key KN...Non-Friend Key KO…Owner key KS...Share Key PC: Counting program PN...predetermined number

Claims

1. a management server that can communicate with a vehicle that stores information about a digital key and with a plurality of devices that store information about the digital key registered for the vehicle, and that manages registration of the digital key; a communication module; an execution device; When a request for registration of a new digital key is received from a shared device among the plurality of devices that is different from a device belonging to the owner of the vehicle, the execution device controls the communication module to transmit information about the digital key to the vehicle; When the difference between the maximum number of the digital keys that can be registered for the vehicle and the amount of information related to the digital keys stored in the vehicle is equal to or less than a predetermined number, even if a request to register a new digital key is received from the sharing device, the execution device controls the communication module not to transmit information related to the digital keys to the vehicle. Management server.

2. The execution device controls the communication module to transmit, to the vehicle, authentication information used by the vehicle to authenticate the digital key as information related to the digital key. The management server according to claim 1 .

3. The predetermined number is configurable by the owner. The management server according to claim 1 .

4. When a request for registration of a new digital key is received from the shared device, the difference is confirmed; The execution device controls the communication module so as not to transmit information related to the digital key when the difference is equal to or smaller than a predetermined number. The management server according to claim 1 .

5. When the shared device requests registration of a new digital key for another device and information about the digital key is not transmitted, the execution device controls the communication module to transmit a notification to the other device that the new digital key will not be registered. The management server according to claim 1 .

6. When transmitting a notification to the other device that the new digital key will not be registered, the execution device controls the communication module to transmit a notification to the other device that the reason the new digital key will not be registered is the number of pieces of information related to the digital key stored in the vehicle. The management server according to claim 5 .

7. When the sharing device requests registration of a new digital key for another device and does not transmit information about the digital key, the execution device controls the communication module to transmit a notification to the sharing device that requested registration of the new digital key that the new digital key will not be registered. The management server according to claim 1 .

8. When transmitting a notification to the sharing device that requested registration of the new digital key that the new digital key will not be registered, the execution device controls the communication module to transmit a notification to the sharing device that the reason the new digital key will not be registered is the number of pieces of information related to the digital key stored in the vehicle. The management server according to claim 7.

9. A management method for managing information transmitted by a management server that is capable of communicating with a vehicle that stores information about a digital key and with a plurality of devices that store information about the digital key registered for the vehicle, and that transmits information about the digital key to the vehicle when a request for registration of a new digital key is received from a shared device among the plurality of devices that is different from a device belonging to the owner of the vehicle, and when a difference between the maximum number of the digital keys that can be registered for the vehicle and the amount of information related to the digital keys stored in the vehicle is equal to or less than a predetermined number, controlling the management server not to transmit information related to the digital keys to the vehicle even if registration of a new digital key is requested from the sharing device. Management method.

10. a management program executed by a management server that is capable of communicating with a vehicle that stores information about a digital key and with a plurality of devices that store information about the digital key registered for the vehicle, and that transmits information about the digital key to the vehicle when a request for registration of a new digital key is received from a shared device among the plurality of devices that is different from a device belonging to the owner of the vehicle; When a difference between the maximum number of the digital keys that can be registered for the vehicle and the amount of information related to the digital keys stored in the vehicle is equal to or less than a predetermined number, the management server does not transmit information about the digital keys even if a request to register a new digital key is received from the shared device. Management program.

11. a vehicle that stores information about a digital key; a plurality of devices that store information about the digital keys registered for the vehicle; a management system including: a management server capable of communicating with the vehicle and the plurality of devices and managing registration of the digital key; The management server When a request for registration of a new digital key is received from a shared device among the plurality of devices that is different from a device belonging to the owner of the vehicle, information about the digital key is transmitted to the vehicle; When the difference between the maximum number of the digital keys that can be registered for the vehicle and the amount of information related to the digital keys stored in the vehicle is equal to or less than a predetermined number, even if registration of a new digital key is requested from the sharing device, information related to the digital key is not transmitted to the vehicle. Management system.

12. When the management server is requested by the shared device to register a new digital key for another device and does not transmit information about the digital key, the management server transmits a notification to the other device that the new digital key will not be registered; The other device displays a message indicating that the new digital key will not be registered. The management system according to claim 11.

13. the management server transmits a notification to the other device indicating that the reason for the failure to register the new digital key is the number of pieces of information related to the digital key stored in the vehicle; The other device displays a message that the reason the new digital key cannot be registered is the number of pieces of information about the digital key stored in the vehicle. The management system of claim 12.

14. When the management server is requested by the shared device to register a new digital key for another device and does not transmit information about the digital key, the management server transmits a notification to the shared device that requested the registration of the new digital key that the new digital key will not be registered; The shared device that requested the registration of the new digital key displays a message indicating that the new digital key will not be registered. The management system according to any one of claims 11 to 13.

15. the management server transmits a notification to the shared device that has requested registration of the new digital key that the reason for the failure to register the new digital key is the number of pieces of information related to the digital key stored in the vehicle; The shared device that requested the registration of the new digital key displays a message that the reason the new digital key could not be registered is due to the number of pieces of information about the digital key stored in the vehicle. The management system of claim 14.

Images