Server, device, system, server management method, server program, device management method, and device program

Abstract

Digital keys which can be registered from now on are previously limited.SOLUTION: The management server 70 manages a plurality of digital keys that can be used for vehicles. The management server 70 includes a transmitting unit 70S. When the second digital key is generated on the basis of the first digital key, the transmission part 70S transmits restriction information RI of a third digital key generated on the basis of the second digital key to devices 30 in which the second digital key is registered.SELECTED DRAWING: Figure 10

Description

[Technical Field]

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

[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 of which only one can exist per vehicle. The shared device registers a shared key. A single shared key is a digital key of which multiple can exist per vehicle.

[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. [Prior art documents] [Patent documents]

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

[0005] In a management system such as that described in Patent Document 1, it is conceivable that a share device may register a share key to another share device by making a further registration request. In such a case, there is a demand for imposing restrictions on the other share keys that will be registered by the share device, such as a restriction on the number of registrations. [Means for solving the problem]

[0006] In order to solve the above problem, the server is a server that manages multiple digital keys that can be used for a vehicle, and is equipped with a transmission unit that, when a second digital key is generated based on a first digital key, transmits restriction information for a third digital key generated based on the second digital key to a device to which the second digital key is registered.

[0007] In order to solve the above problem, the server is a device in which a second digital key generated based on a first digital key is registered, and is equipped with a receiving unit that receives, from the server, restriction information for a third digital key generated based on the second digital key, and an executing unit that restricts the registration of the third digital key based on the restriction information.

[0008] In order to solve the above problem, the system includes a server that manages multiple digital keys that can be used for a vehicle, and a device to which a second digital key generated based on a first digital key is registered, wherein the server includes a transmitter that transmits restriction information for a third digital key generated based on the second digital key to the device when the second digital key is generated based on the first digital key, and the device includes a receiver that receives the restriction information transmitted by the transmitter, and an execution unit that imposes at least one of the restrictions on the registration of the third digital key based on the restriction information.

[0009] In order to solve the above problem, the server management method is a management method performed by a server that manages multiple digital keys that can be used for a vehicle, and when a second digital key is generated based on a first digital key, the server transmits restriction information for a third digital key generated based on the second digital key to a device to which the third digital key is registered.

[0010] To solve the above problem, the server program causes the server, which manages multiple digital keys that can be used for a vehicle, to function as a transmitter that, when a second digital key is generated based on a first digital key, transmits restriction information for a third digital key generated based on the second digital key to a device to which the second digital key is registered.

[0011] In order to solve the above problem, the device management method is a management method performed by a device to which a second digital key generated based on a first digital key is registered, in which the device receives restriction information for a third digital key generated based on the second digital key from a server, and performs at least one of restricting vehicle control when the third digital key is used and restricting registration of the third digital key based on the restriction information.

[0012] In order to solve the above problem, the device program causes a device in which a second digital key generated based on a first digital key is registered to function as: a receiving unit that receives, from a server, restriction information for a third digital key generated based on the second digital key; and an executing unit that, based on the restriction information, imposes at least one of restrictions on vehicle control when the third digital key is used and restrictions on registering the third digital key. [Effects of the Invention]

[0013] Each of the above configurations can set restrictions in advance on the digital keys that can be registered in the future. [Brief explanation of the drawings]

[0014] [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 according to the embodiment. [Figure 3] FIG. 3 is a schematic diagram showing the share key information of the embodiment. [Figure 4] FIG. 4 is a schematic diagram showing data in the database of the embodiment. [Figure 5] FIG. 5 is an explanatory diagram showing a series of processes performed by the management system when registering an owner key according to the embodiment. [Figure 6] FIG. 6 is an explanatory diagram showing a series of processes performed by the management system when a friend key is registered in the embodiment. [Figure 7] FIG. 7 is an explanatory diagram showing a series of processes performed by the management system when a non-friend key is registered in the embodiment. [Figure 8] FIG. 8 is an explanatory diagram showing a series of processes performed by the management system when a non-friend key is deleted in response to a request from a friend device according to the embodiment. [Figure 9] FIG. 9 is an explanatory diagram showing a series of processes performed by the management system when a non-friend key is deleted in response to a request from a non-friend device in the embodiment. [Figure 10] FIG. 10 is a schematic diagram showing the functional units of the management system of the embodiment. [Figure 11] FIG. 11 is a schematic diagram showing constraint information according to the embodiment. [Figure 12] FIG. 12 is a flowchart showing a series of processes related to the transmission of restriction information performed by the management server of the embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0015] (One embodiment) A management system 10 according to an embodiment will be described below with reference to the drawings. <Outline of the management system> 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0031] 1, the shared device 50 stores shared key information DKS indicating a shared key KS as key information DK. A 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.

[0032] 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 direct registration request D21 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 registered based on an indirect registration request from a shared device 50, which is a device 30 different from the owner device 40.

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

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

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

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

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

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

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

[0040] <Administration Server> The management server 70 manages multiple digital keys that can be used for the vehicle 20. The digital key is used by the user, and the digital key is then used in the management system 10. 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.

[0041] The storage device 72 stores a server program PS, a monitoring program PM, and a database DB. The server program PS, when executed by the execution device 71, causes the execution device 71 to register a digital key in the database DB and delete a digital key from the database DB. Details of the monitoring program PM will be described later.

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

[0043] As shown in Figure 4, data DA for one vehicle 20 includes the types of digital keys registered to the vehicle 20, the registered devices 30, the relationships between the registered devices 30, and restriction information RI for each type of digital key. 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.

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

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

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

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

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

[0049] 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 third device 30C, the fourth device 30D, the sixth device 30F, and the seventh device 30G are non-friend devices 52.

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

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

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

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

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

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

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

[0057] In addition, in the data DA, restriction information RI is defined for each type of digital key. In the data DA, the restriction information RI of the owner key KO is defined as no restriction. Therefore, no restriction is imposed on the owner device 40. In the data DA, the restriction information RI of the friend key KF is defined as first restriction information RI1. Therefore, the restriction indicated by the first restriction information RI1 is imposed on the friend device 51. In the data DA, the restriction information RI of the non-friend key KN is defined as second restriction information RI2. Therefore, the restriction indicated by the second restriction information RI2 is imposed on the non-friend device 52. The restriction information RI will be described in detail later.

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

[0059] <Registering the owner key> 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0086] After completing the registration management, the management server 70 transmits a key track completion notification M23 and first constraint information RI1 associated with the execution of a constraint program PC, which will be described later, to the second device 30B.

[0087] 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 end the series of processes for registering the friend key KF.

[0088] <Registering a non-friend key> 7, 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 designated as a third device 30C.

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

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

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

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

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

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

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

[0096] 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. The friend device 51 then transmits to the third device 30C a completion notification M32 indicating that the completed non-friend key information DKN has been uploaded to the URL link, and information indicating usage restrictions UM, which will be described later.

[0097] 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 S47.

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

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

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

[0101] 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 second device 30B.

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

[0103] Thereafter, when the vehicle 20 receives the authentication package ATP and the storage request D34, it performs the process of step S50. In step S50, 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.

[0104] After completing the registration management, the management server 70 transmits a key track completion notification M33 and second constraint information RI2 associated with the execution of a constraint program PC, which will be described later, to the second device 30B.

[0105] Thereafter, upon receiving the key track completion notification M33, the second device 30B performs the process of step S51. In the process 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 end the series of processes for registering the non-friend key KN.

[0106] <Delete non-friend keys> 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, and the process executed by the execution unit 71 will be described as a process executed by the management server 70.

[0107] <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 the non-friend key KN based on a reservation deletion request D41 from the friend device 51.

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

[0109] 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 the specified condition RC. The specified condition RC is a condition required to start deletion after receiving the reservation deletion request D41. The specified condition RC is predetermined. For example, the specified condition RC is that a predetermined fade-out period has elapsed since receiving the reservation deletion request D41. Then, the friend device 51 transmits the reservation deletion request D41 for the non-friend key KN to the management server 70.

[0110] Thereafter, upon receiving the reservation deletion request D41 for the non-friend key KN, the management server 70 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.

[0111] Thereafter, when the friend device 51 receives the deletion in progress 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.

[0112] 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 in the database DB as a fade-out state. The fade-out state is a state in which the reservation deletion request D41 has been received but the execution of deletion is still pending. Thereafter, the management server 70 proceeds to the process of step S65.

[0113] 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 advances the process to step S66.

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

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

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

[0117] 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 subject of the reservation deletion request D41. The management server 70 then transmits the deletion request D43 to the vehicle 20.

[0118] Thereafter, when the vehicle 20 receives the deletion request D43, the vehicle 20 performs 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 deletion 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.

[0119] 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 the process of step S72.

[0120] 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 deletion 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.

[0121] 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, to the HMI 32, information indicating that the deletion of the non-friend key KN that is the subject of the reservation deletion request D41 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. Thereafter, the management system 10 ends the series of processes for the deletion of this non-friend key KN.

[0122] <Deletion of non-friend keys due to deletion on non-friend devices> As shown in FIG. 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 in the non-friend device 52.

[0123] 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 deletion completion notification M51 to the management server 70 indicating that the non-friend key information DKN has been deleted.

[0124] 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 deletion completion notification M52 to the friend device 51, indicating that the non-friend key information DKN has been deleted.

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

[0126] After processing step S82, the management server 70 performs processing 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. Then, the management server 70 transmits the deletion request D51 to the vehicle 20.

[0127] 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 that was deleted in step S81 in accordance with the deletion request D51. The vehicle 20 then transmits a completion notification M53 to the management server 70 indicating that the deletion of the authentication information AT in accordance with the deletion request D51 has been completed.

[0128] 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 that was completely deleted in step S81. Thereafter, the management server 70 proceeds to the process of step S87.

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

[0130] <Each functional part of the management system> Next, each functional unit of the management system 10 will be described. 10, in the management system 10, the management server 70 has a transmission unit 70S, a memory unit 70M, and a reception unit 70R. A storage device 72 functions as the memory unit 70M. The memory unit 70M stores a database DB.

[0131] The execution device 71 functions as a receiving unit 70R. The receiving unit 70R receives a key track request from the device 30 via the communication module 73. The execution device 71 functions as a transmitting unit 70S. When a second digital key is generated based on a first digital key, the transmitting unit 70S transmits restriction information RI of a third digital key generated based on the second digital key to the device 30 in which the second digital key is to be registered. In particular, in response to the receiving unit 70R receiving the key track request, the transmitting unit 70S transmits a completion notification of the key track request and the restriction information RI to the device 30. The restriction information RI includes information used to restrict the registration of the third digital key.

[0132] As shown in FIG. 1, in the management server 70, the storage device 72 stores a constraint program PC. When the execution device 71 receives any of the key track request D12, key track request D23, and key track request D33, it executes the constraint program PC. The constraint program PC is a program that causes the execution device 71 to function as a transmission unit 70S when executed by the execution device 71. The constraint program PC is a server program in this embodiment. Furthermore, when the management server 70 executes the constraint program PC, the management server 70 performs a server management method.

[0133] 10, in the management system 10, a shared device 50, which is a device 30 to which a second digital key is registered, has a receiving unit 30R, a memory unit 30M, and an execution unit 30EX. A storage device 37 functions as the memory unit 30M. The memory unit 30M stores shared key information DKS.

[0134] The execution device 36 functions as the receiving unit 30R. The receiving unit 30R receives the constraint information RI from the management server 70 via the communication module 31. The execution device 36 functions as the execution unit 30EX.

[0135] As shown in FIG. 1 , in the vehicle 20, the storage device 37 stores a device program PD. The execution device 36 executes the device program PD to function as the receiving unit 30R and the execution unit 30EX. That is, the device program PD is a program that causes the execution device 36 to function as the receiving unit 30R and the execution unit 30EX. The execution unit 30EX restricts the registration of the third digital key based on the restriction information RI. In this embodiment, the device program PD is a program of the device 30. Furthermore, by the device 30 executing the device program PD, the device 30 performs a device 30 management method.

[0136] <Constraint information> 11, the restrictions indicated by the restriction information RI include registration restrictions EM and usage restrictions UM. The registration restrictions EM are restrictions imposed on the shared device 50 when registering the non-friend key KN. For example, the registration restrictions EM indicate restrictions imposed on the shared device 50 when sending a request for the non-friend key KN. The registration restrictions EM include registration prohibitions RME and registration allowances PME.

[0137] The registration prohibitions RME are prohibitions that the share device 50 must fulfill when registering a non-friend key KN based on a registration request from the share device 50. The registration prohibitions RME include registering more than the upper limit number LM of non-friend keys KN based on a registration request from the share device 50. The upper limit number LM is a value determined for each share device 50. For example, the upper limit number LM is determined as a predetermined value for each share device 50.

[0138] The registration acceptance items PME are items that the sharing device 50 is allowed to accept when registering a non-friend key KN based on a registration request from the sharing device 50. The registration acceptance items PME include that non-friend keys KN up to the upper limit number LM are registered based on a registration request from the sharing device 50.

[0139] The usage restrictions UM are restrictions imposed on the non-friend device 52 that stores the non-friend key information DKN indicating the non-friend key KN when using the non-friend key KN based on a registration request from the shared device 50. The usage restrictions UM include usage prohibitions RMU and usage permitted items PMU.

[0140] The prohibited items RMU during use are items that are prohibited by the non-friend device 52 that stores the non-friend key information DKN indicating the non-friend key KN when using the non-friend key KN based on a registration request from the shared device 50. The prohibited items RMU during use include the range of control of the vehicle 20 that cannot be permitted by the non-friend key KN. The range of control of the vehicle 20 that cannot be permitted by the non-friend key KN includes, for example, control of starting the engine of the vehicle 20, but does not include control of unlocking or locking the doors of the vehicle 20.

[0141] The usage permission items PMU are items that are permitted by the non-friend device 52 that stores the non-friend key information DKN indicating the non-friend key KN when using the non-friend key KN based on a registration request from the shared device 50. The usage permission items PMU include the range of control of the vehicle 20 that can be permitted by the non-friend key KN. The range of control of the vehicle 20 that can be permitted by the non-friend key KN includes, for example, unlocking and locking control of the doors of the vehicle 20, but does not include starting control of the engine of the vehicle 20.

[0142] <Send restriction information> Next, a series of processes relating to the restrictions on the friend key KF in the management system 10 will be described.

[0143] 12, when the execution device 71 starts executing the constraint program PC, the execution device 71 first performs the processing of step S101. In step S101, the execution device 71 identifies the device 30 that sent the received key track request. As a result, the execution device 71 identifies the device 30 that stores the key information DK indicating the digital key in a series of processes related to digital key registration that include the received key track request. After that, the execution device 71 proceeds to step S102.

[0144] In step S102, the execution device 71 determines whether the identified device 30 is a shared device 50. If the identified device 30 is a shared device 50 (S102: YES), the execution device 71 proceeds to step S103.

[0145] In step S103, the execution device 71 identifies the restriction information RI to be sent to the identified share device 50. For example, the execution device 71 first references the identified share device 50 and the database DB. Next, the execution device 71 identifies whether the identified share device 50 is a friend device 51 or a non-friend device 52. Then, the execution device 71 identifies the restriction information RI associated with the type of the identified device 30.

[0146] The executing device 71 then proceeds to step S104. In step S104, the executing device 71 transmits the identified restriction information RI along with a completion notification M23 to the identified shared device 50. Specifically, if the type of the identified device 30 is a friend device 51, the executing device 71 transmits first restriction information RI1 as the restriction information RI to the friend device 51. If the type of the identified device 30 is a non-friend device 52, the executing device 71 transmits second restriction information RI2 as the restriction information RI to the non-friend device 52. The executing device 71 then terminates this series of processes.

[0147] If the identified device 30 is not a shared device 50 (S102: NO), the execution device 71 ends this series of processes. Therefore, if the type of the identified device 30 is the owner key KO, the execution device 71 does not transmit the constraint information RI to the owner device 40. Thereafter, the execution device 71 ends this series of processes.

[0148] Next, a process performed by the shared device 50 that has received the restriction information RI will be described. A case where the friend device 51 receives the restriction information RI will be described below. When the friend device 51 receives the restriction information RI, the friend device 51 restricts the transmission of a registration request D31 for a non-friend key KN based on the registration prohibitions RME. In this case, even if a predetermined operation is performed to register a non-friend key KN, the friend device 51 prohibits the registration of the non-friend key KN. That is, the execution unit 30EX prohibits the registration of a third digital key even if the registration of the third digital key is attempted. Specifically, the friend device 51 prohibits the transmission of a registration request D31 for a non-friend key KN that exceeds the upper limit number LM. That is, the execution unit 30EX prohibits the transmission of a request to register a number of digital keys that exceeds the upper limit number LM.

[0149] Furthermore, when the friend device 51 transmits the completion notification M32 after step S46 in the series of processes related to the registration of the non-friend key KN shown in FIG. 7, the friend device 51 adds information indicating the prohibited items RMU during use.

[0150] The non-friend device 52 that receives the usage prohibition item RMU prohibits the restricted control based on the usage prohibition item RMU. Specifically, the non-friend device 52 prohibits a request for engine start control of the vehicle 20. For example, the non-friend device 52 displays on the HMI 32 that the operation switch for requesting engine start control of the vehicle 20 cannot be operated.

[0151] 4, specifically, when the type of the identified device 30 is a friend device 51, the execution device 71 identifies that the constraint information RI is the first constraint information RI1. When the type of the identified device 30 is a non-friend device 52, the execution device 71 identifies that the constraint information RI is the second constraint information RI2. The items restricted by the second constraint information RI2 are broader than the items restricted by the first constraint information RI1. For example, the upper limit number LM limited by the registration prohibition items RME of the second constraint information RI2 is smaller than the upper limit number LM limited by the registration prohibition items RME of the first constraint information RI1. In other words, the number of times that the non-friend device 52 can transmit a request to register a further non-friend key KN is smaller than the number of times that the friend device 51 can transmit a registration request D31.

[0152] <Operation of one embodiment> According to the above embodiment, when registering a shared key KS, which is a third digital key, the transmission unit 70S of the management server 70 transmits restriction information RI to the second device 30B that stores the second digital key. The shared device 50, which is the second device 30B that has received the restriction information RI, restricts the transmission of a request to register a non-friend key KN, which is a third digital key, based on the restriction information RI.

[0153] <Effects of one embodiment> (1) According to the above embodiment, the transmission unit 70S transmits the restriction information RI of the third digital key to the device 30 to which the second digital key is to be registered, thereby making it possible to set restrictions in advance on the third digital key that may be registered in the future.

[0154] (2) According to the above embodiment, the restriction information RI is used to restrict the registration of the third digital key. Therefore, the device 30 to which the second digital key is registered can restrict the registration of the third digital key that may be registered in the future.

[0155] (3) According to the above embodiment, in response to the reception of the key track request by the reception unit 70R, the transmission unit 70S transmits a completion notification of the key track request and the restriction information RI to the device 30 in which the second digital key is registered. Therefore, the transmission unit 70S can transmit the restriction information RI in accordance with the series of registration processes for the second digital key.

[0156] (4) According to the above embodiment, the transmitter 70S transmits the restriction information RI together with a completion notification indicating that the key track request has been responded to. Therefore, the share device 50, which is the device 30 in which the second digital key is registered, can obtain the restriction information RI when the series of registration processes for the share key KS indicated by the share key information DKS stored in the share device 50 is completed.

[0157] (5) By restricting the share device 50 from sending a request to register a non-friend key KN based on the restriction information RI, the management system 10 can prevent excessive registration of non-friend keys KN.

[0158] (6) According to the above embodiment, the restriction information RI includes the registration prohibitions RME. The share device 50 that receives the restriction information RI prohibits the control indicated in the registration prohibitions RME. Therefore, the management system 10 can prevent the share device 50 from performing the control indicated in the registration prohibitions RME.

[0159] (7) According to the above embodiment, the registration prohibitions RME include sending a request to register a non-friend key KN that exceeds the upper limit LM of the number of non-friend keys KN that can be registered. The share device 50 that receives the restriction information RI is prohibited from sending a request to register a non-friend key KN that exceeds the upper limit LM. Therefore, the management system 10 can prevent the share device 50 from sending a request to register a number of non-friend keys KN that exceeds the upper limit LM.

[0160] (8) According to the above embodiment, the restriction information RI includes the permitted items at registration PME. The share device 50 that receives the restriction information RI allows the control indicated in the permitted items at registration PME. Therefore, the management system 10 can prevent the share device 50 from being unable to perform the control indicated in the permitted items at registration PME.

[0161] (9) According to the above embodiment, the registration permission items PME include the transmission of a request to register non-friend keys KN up to the upper limit number LM. Then, the share device 50 that has received the restriction information RI is permitted to transmit a request to register non-friend keys KN up to the upper limit number LM. Therefore, the management system 10 can prevent the share device 50 from restricting the transmission of a request to register non-friend keys KN up to the upper limit number LM.

[0162] (10) According to the above embodiment, the restriction information RI includes usage restrictions UM. The usage restrictions UM are items that are added to the non-friend device 52 that stores the non-friend key information DKN indicating the non-friend key KN when using the non-friend key KN registered based on a request from the shared device 50 to which the restriction information RI is sent. The shared device 50 that has acquired the usage restrictions UM can display an image indicating the usage restrictions UM on the HMI 32 before sending a request to register the non-friend key KN. This allows the user of the shared device 50 to know the usage restrictions UM before registering the non-friend key KN and then send a request to register the non-friend key KN.

[0163] (11) According to the above embodiment, the non-friend device 52, which stores non-friend key information DKN indicating the non-friend key KN registered in response to a request from the shared device 50, acquires information indicating the usage restrictions UM. The non-friend device 52 then restricts control using the non-friend key KN based on the usage restrictions UM. Therefore, the management server 70 can prevent the non-friend device 52 from being excessively permitted to control the vehicle 20 using the non-friend key KN.

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

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

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

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

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

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

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

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

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

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

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

[0175] <Restrictions on use> The usage restrictions are not limited to those described in the above embodiment. For example, the maximum speed that the vehicle 20 can output may be limited. Also, for example, the power, such as torque or acceleration, that the vehicle 20 can output may be limited. Also, for example, the audio volume that the vehicle 20 can output may be limited. Furthermore, the usage restrictions may include restrictions on the geographical area in which the vehicle 20 can be used, restrictions on available multimedia functions, restrictions on communication, such as the amount and speed of communication by the communication module 21, restrictions on disabling various safety functions of the vehicle 20, and restrictions on disabling the rear doors and trunk of the vehicle 20.

[0176] The prohibited actions of the RMU are not limited to those described in the above embodiment. For example, the prohibited actions may include control of the air conditioner of the vehicle 20, control of charging the battery of the vehicle 20, and control of opening and closing the power windows of the vehicle 20.

[0177] The PMU's usage permissions are not limited to the examples in the above embodiment. For example, they may include control of the air conditioning system of the vehicle 20, control of charging the battery of the vehicle 20, and control of opening and closing the power windows of the vehicle 20.

[0178] The usage restrictions UM may include only either the usage prohibitions RMU or the usage allowances PMU. For example, if the usage restrictions UM includes only the usage prohibitions RMU, it may be specified that all items not included in the usage prohibitions RMU are allowed.

[0179] The registration constraint EM is not limited to sending a request to register non-friend keys KN up to the upper limit LM. The registration prohibitions RME are not limited to the examples of the above embodiment. For example, the registration permits PME may include a prohibition that prohibits storing non-friend key information DKN indicating a non-friend key KN intended for a specific device 30 unless a predetermined condition is met. For example, the condition may be that the specific device 30 must be registered in a predetermined server in advance.

[0180] For example, the condition may be that the owner device 40 stores contact information such as the phone number of the specific device 30X. The registration prohibition items RME may include an item indicating that setting a period exceeding the upper limit of the validity period of the shared key KS is prohibited. For example, setting a third digital key, that is, the shared key KS, beyond a predetermined period or expiration date may be prohibited.

[0181] The registration permitted items PME are not limited to the examples in the above embodiment. The registration permitted items PME may include only items that are not included in the registration prohibited items RME. For example, in accordance with the modified example of the registration prohibited items RME, the registration permitted items PME may include an item that allows storage of non-friend key information DKN indicating a non-friend key KN intended for a specific device 30 when predetermined conditions are met.

[0182] The registration constraints EM may include only the items of the registration prohibitions RME and the registration allowances PME. For example, if the registration constraints EM include only the use prohibitions RMU, it may be specified that all items not included in the use prohibitions RMU are allowed.

[0183] <Constraint information> The management server 70 may transmit the restriction information RI to the shared device 50 at a different timing from the timing of the completion notification indicating that the key track request has been responded to. For example, the management server 70 may transmit the restriction information RI after transmitting the completion notification M23. Alternatively, for example, the management server 70 may transmit the restriction information RI to the friend device 51 before transmitting the completion notification M23. In this case, the management server 70 may transmit the completion notification M23 to the friend device 51 after receiving a notification from the friend device 51 that the restriction information RI has been received.

[0184] The non-friend device 52 may not be able to send a request to register a new non-friend key KN. In this case, the management server 70 may not store the second constraint information RI2, and the management server 70 may not send the constraint information RI to the non-friend device 52. In other words, the shared device 50 to which the management server 70 sends the constraint information RI may be only the friend device 51.

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

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

[0187] Furthermore, the management server 70 may store information including information indicating only permitted items without prohibited items as the restriction information RI for the owner device 40. In this case, the management server 70 may transmit the restriction information RI to the owner device 40 after the processing of step S19.

[0188] In the above embodiment, the restriction information RI differed depending on the type of shared key KS, but the restriction information RI may be the same regardless of the type of shared key KS. Also, the restriction information RI may differ for each shared key KS regardless of the type of shared key KS. For example, the restriction information RI may be set in advance for each shared key KS by the owner device 40.

[0189] The non-friend device 52 may acquire information indicated by the usage constraints UM from the management server 70. For example, after storing the non-friend key information DKN by the processing of step S47, the non-friend device 52 may acquire information indicating the usage constraints UM from the management server 70 when receiving the completion notification M33. In this case, the management server 70 may select the usage constraints UM to be transmitted to the non-friend device 52 from the database DB when registering and managing the non-friend key KN by the processing of step S49. Thereafter, the management server 70 may transmit the selected usage constraints UM to the non-friend device 52.

[0190] The constraint information RI may be information indicating the constraints of the non-friend key KN to be registered based on a request to register the target shared device. For example, the constraint information RI may include information indicating at least one of the registration constraints EM, the usage constraints UM, and the deletion constraints of the modified example described above.

[0191] The restriction information RI may include deletion restrictions. The deletion restrictions are restrictions that, when deleting a non-friend key KN based on a registration request from a sharing device 50, restrict the sharing device 50 and the non-friend device 52 that stores the non-friend key information DKN indicating the non-friend key KN. For example, the deletion restrictions may include a restriction indicating that deletion is permitted even if the specified condition RC is not met when a deletion request is made from the sharing device 50 that requested registration. This restriction is a restriction on a reservation deletion request D41 from the sharing device 50. Also, for example, the deletion restrictions may include a restriction that prohibits a deletion request from the non-friend device 52 that stores the non-friend key information DKN. This restriction is a restriction on deletion by the non-friend device itself.

[0192] The restriction information RI may not include the usage restrictions UM. In this case, the non-friend device 52 may not restrict the control using the non-friend key KN based on the usage restrictions UM.

[0193] The restriction information RI may not include the registration restriction EM. In this case, the non-friend device 52 may not restrict the registration of the non-friend key KN based on the registration restriction EM. [Explanation of symbols]

[0194] 10...Management system 20...Vehicle 26...Vehicle management device 30…Devices 30EX…Executive Department 30M…Storage section 30R...Receiver 30S…Executive Department 40...Owner device 50...Shared devices 51...Friend Device 52...Non-Friendly Device 60...Device Server 70...Administration server 70M…Storage section 70R...Receiver 70S...Transmitter 71...Execution device 72...Storage device AT…Authentication information DB...database DK...Key information DKN...Non-Friend Key Information DKS…Share Key Information EM…Registration Restrictions KN...Non-Friend Key KS...Share Key LM...Maximum number PME…Acceptable matters at the time of registration PMU...Permissible conditions for use RI…Restriction information RME…Prohibited items when registering RMU…Prohibitions when using UM…Restrictions when using

Claims

1. A server that manages a plurality of digital keys that can be used for a vehicle, a transmitting unit that, when a second digital key is generated based on the first digital key, transmits restriction information for a third digital key generated based on the second digital key to a device in which the second digital key is registered. server.

2. The restriction information is used to restrict registration of the third digital key. The server of claim 1 .

3. a storage unit that stores a database in which the corresponding vehicle and the registered device are associated with each of the plurality of digital keys; a receiving unit that receives a key track request that requests updating of the database; The transmitting unit transmits a completion notification of the key track request and the constraint information to the device in response to the receiving unit receiving the key track request. The server according to claim 1 or 2.

4. The transmission unit transmits the constraint information together with the completion notification to the device. The server of claim 3.

5. A device in which a second digital key generated based on a first digital key is registered, a receiving unit that receives, from a server, restriction information for a third digital key generated based on the second digital key; an execution unit that restricts registration of the third digital key based on the restriction information. device.

6. If the restriction information includes a registration prohibition that prohibits registration of the third digital key, The execution unit prohibits registration of the third digital key even if registration of the third digital key is enforced. The device of claim 5.

7. a storage unit for storing key information indicating a digital key; The restriction information includes information regarding an upper limit number of the digital keys that can be registered to a vehicle, When the receiving unit receives the restriction information, the receiving unit prohibits transmission of a request to register the number of the digital keys that exceeds the upper limit number.

7. A device according to claim 5 or claim 6.

8. A system comprising: a server that manages a plurality of digital keys that can be used for a vehicle; and a device in which a second digital key generated based on a first digital key is registered, The server a transmitting unit configured to transmit, when the second digital key is generated based on the first digital key, restriction information of a third digital key generated based on the second digital key to the device; The device comprises: a receiving unit that receives the constraint information transmitted by the transmitting unit; an enforcement unit that enforces at least one of the restrictions on registration of the third digital key based on the restriction information. system.

9. A management method performed by a server that manages a plurality of digital keys that can be used for a vehicle, comprising: When a second digital key is generated based on a first digital key, the server transmits restriction information for a third digital key generated based on the second digital key to a device to which the third digital key is to be registered. How to manage your server.

10. A server that manages multiple digital keys that can be used for a vehicle, When a second digital key is generated based on a first digital key, the device functions as a transmitter that transmits restriction information of a third digital key generated based on the second digital key to a device in which the second digital key is registered. Server program.

11. A management method performed by a device in which a second digital key generated based on a first digital key is registered, comprising: the device comprising: receiving, from a server, restriction information for a third digital key generated based on the second digital key; and performing at least one of restricting vehicle control when the third digital key is used and restricting registration of the third digital key based on the restriction information. How to manage your devices.

12. a device to which a second digital key generated based on the first digital key is registered; a receiving unit that receives, from a server, restriction information for a third digital key generated based on the second digital key; and an execution unit that performs at least one of restricting vehicle control when the third digital key is used and restricting registration of the third digital key based on the restriction information. Program the device.

Images