server

Abstract

To provide a server capable of allowing a user of a device storing information on another digital key associated with a digital key to grasp a use state of a vehicle by a user of a device storing information on the digital key.SOLUTION: The management server 70 is a server that manages a plurality of digital keys that can be used for the vehicle 20. The plurality of digital keys includes a first digital key and a plurality of digital keys associated with the first digital key. The management server 70 transmits an acknowledgement 30C to the owner devices 40, which are at least one of the devices storing information relating to a digital key associated with the first digital key, when a user of the third devices ATP7 storing information relating to the first digital key performs an operation A that is not included in the authority information M62, which is the range of functions that the first digital key can execute.SELECTED DRAWING: Figure 10

Description

[Technical Field]

[0001] The present invention relates to a server. [Background technology]

[0002] Patent Document 1 discloses a digital key system technology that uses a device such as a smartphone as a vehicle key. The digital key system stores information about the digital key in the vehicle. The digital key system also stores information about the digital key in a device. This allows the vehicle to be used using the device registered as a digital key without the need for a physical key. Furthermore, the digital key system issues a registration request to enable another person's device to function as a digital key through communication between the device storing information about the digital key and the other person's device. This allows the other person's device to be registered as a digital key to the vehicle. In other words, the digital key can generate a new digital key. The digital key system also allows the vehicle to be loaned to another person without the need to exchange a physical key. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Laid-Open No. 2023-184349 Summary of the Invention [Problem to be solved by the invention]

[0004] Among the devices that function as a digital key for a vehicle, there are devices that store information about the digital key for the vehicle that was generated when the owner of the vehicle made a registration request. Other devices store information about the digital key for the vehicle that was generated when a person other than the owner of the vehicle made a registration request. The owner of the vehicle and the user of the device that stores information about the digital key for the vehicle that was generated when a person other than the owner of the vehicle made a registration request may not know each other.

[0005] Regardless of whether they are the owner of a vehicle, a user who has newly generated a digital key for that vehicle wants to know the vehicle usage information of the user of the device that stores information about the newly generated digital key for that vehicle. [Means for solving the problem]

[0006] The server for solving the above problem is a server that manages multiple digital keys that can be used for a vehicle. The multiple digital keys include a first digital key and multiple digital keys associated with the first digital key. When an operation that is not included in the range of functions that the first digital key can perform is performed, the server transmits a confirmation notification to at least one device that stores information about the digital key associated with the first digital key. [Effects of the Invention]

[0007] The server allows a user of a device that stores information about another digital key associated with the digital key to understand how the user of the device that stores information about the digital key is using the vehicle. [Brief explanation of the drawings]

[0008] [Figure 1] FIG. 1 is a schematic diagram showing a management system. [Figure 2] FIG. 2 is a schematic diagram showing owner key information. [Figure 3] FIG. 3 is a schematic diagram showing the share key information. [Figure 4] FIG. 4 is a schematic diagram showing data in the database of the management server. [Figure 5] FIG. 5 is an explanatory diagram showing a series of processes performed by the management server when an owner key is registered. [Figure 6] FIG. 6 is an explanatory diagram showing a series of processes performed by the management server when a friend key is registered. [Figure 7] FIG. 7 is an explanatory diagram showing a series of processes performed by the management server when a non-friend key is registered. [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. [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. [Figure 10] FIG. 10 is an explanatory diagram showing a series of processes performed by a management system including a management server according to the first embodiment. [Figure 11] FIG. 11 is an explanatory diagram showing the continuation of the processing in FIG. 10 when the owner of the vehicle 20 permits operation A, which is not included in the authority information of the non-friend key. [Figure 12] FIG. 12 is an explanatory diagram showing the continuation of the processing in the case where the owner of the vehicle 20 rejects operation A that is not included in the authority information of the non-friend key in the processing in FIG. [Figure 13] FIG. 13 is a diagram showing an example of a display image presented to the user of the owner device to select whether or not to permit operations not included in the authority information of the non-friend key. [Figure 14] FIG. 14 is a diagram showing an example of a display image presented to the user of the owner device to allow the user to select whether or not to set an end condition. [Figure 15]FIG. 15 is an explanatory diagram showing a series of processes performed by a management system including a management server according to the second embodiment. [Figure 16] FIG. 16 is an explanatory diagram showing the continuation of the processing in the case where the owner of the vehicle 20 permits operation A, which is not included in the authority information of the non-friend key, in the processing in FIG. [Figure 17] FIG. 17 is an explanatory diagram showing the continuation of the processing in the case where the owner of the vehicle 20 rejects operation A that is not included in the authority information of the non-friend key in the processing in FIG. [Figure 18] FIG. 18 is an explanatory diagram showing a series of processes performed by a management system including a management server according to the third embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0009] (First embodiment) A first embodiment of the management server will be described below with reference to FIGS. <Outline of Management System 10> As shown in FIG. 1, the management server 70 is one of the devices that make up the management system 10. The management system 10 includes a vehicle 20, a plurality of devices 30, a device server 60, and a management server 70. The management server 70 is a server that manages a plurality of digital keys that can be used for the vehicle 20. There is a standard for digital keys, the Car Connectivity Consortium (CCC). Matters related to the digital key in this embodiment comply with the CCC.

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

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

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

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

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

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

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

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

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

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

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

[0021] 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 includes certificate information ST5, device public key information ST6, vehicle public key information ST7, permission public key information ST8, and authority information ST9.

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

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

[0024] 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 a vehicle public key PKV that has already been authorized. Authorization information ST9 is information that indicates the range of functions that can be performed by the device 30 that stores the authorization information ST9. The range of functions that can be performed will be described later.

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

[0026] The multiple share devices 50 include a friend device 51 and a non-friend device 52. The friend device 51 stores friend key information DKF indicating a friend key KF as the share key information DKS. The non-friend device 52 stores non-friend key information DKN indicating a non-friend key KN as the share key information DKS. In other words, the types of share keys KS include a friend key KF and a non-friend key KN.

[0027] The friend key KF is a shared key KS registered based on a registration request D21 directly from the owner device 40, as will be described later. The friend key information DKF is key information DK indicating the friend key KF. The friend device 51 is the device 30 that stores the friend key information DKF.

[0028] The non-friend key KN is a shared key KS registered based on an indirect registration request D31 from a friend device 51, as will be described later. The non-friend key information DKN is key information DK indicating the non-friend key KN. The non-friend device 52 is a device 30 that stores the non-friend key information DKN. 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. In other words, the registration request D31 is a request to have the device 30 store the non-friend key information DKN, which is key information DK.

[0029] Note that when a digital key is registered, the digital key is usable. That is, when a digital key is registered, the vehicle 20 stores authentication information AT, and the device 30 stores key information DK. The authentication information AT is information related to the digital key. That is, when a digital key is registered, the vehicle 20 stores information related to the digital key. The key information DK is information related to the digital key. That is, when a digital key is registered, the device 30 stores information related to the digital key.

[0030] 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, intra-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 and authority information ST9 from the owner key structure information STO.

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

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

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

[0034] The authority information ATP7 is information indicating the range of functions that the digital key can perform. The range of functions of the vehicle 20 that can be performed includes, 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 performed by authenticating the digital key, etc. The range of functions of the vehicle 20 that can be performed indicates, for example, the possible controls among starting the engine of the vehicle 20, turning on the power of the vehicle 20, and unlocking and locking the doors of the vehicle 20. For example, if the range of functions of the vehicle 20 that can be performed includes the above-mentioned three controls, the range of functions of the vehicle 20 that can be performed is wider than if the range of functions of the vehicle 20 that can be performed is only unlocking and locking the doors of the vehicle 20. More specifically, the range of functions of the vehicle 20 that can be performed by the friend key KF includes the above-mentioned three controls, while the range of functions of the vehicle 20 that can be performed by the non-friend key KN includes turning on the power of the vehicle 20 and unlocking and locking the doors of the vehicle 20.

[0035] In the first embodiment, the range of vehicle 20 functions that can be performed by the digital key is determined by the authority information ATP7 stored in the vehicle 20. The following describes a case where the authority information ATP7 stored in the device 30 that stores key information DK indicating the digital key is power-on control and door unlock and lock control. In this case, if the authority information ATP7 of the digital key stored in the vehicle 20 to which the digital key is registered is door unlock and lock control, the digital key can perform door unlock and lock control for the vehicle 20. If the authority information ATP7 of the digital key stored in the vehicle 20 to which the digital key is registered is power-on control and door unlock and lock control, the digital key can perform power-on control and door unlock and lock control for the vehicle 20. If the authority information ATP7 of the digital key stored in the vehicle 20 to which the digital key is registered includes control of starting the vehicle's 20 engine, turning on the power, and unlocking and locking the doors, the digital key can perform control of starting the vehicle's 20 engine, turning on the power, and unlocking and locking the doors on the vehicle 20.

[0036] As shown in FIG. 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. Each device server 60 relays communication with the management server 70, so that devices 30 of different types can communicate with the management server 70 via the device server 60. Note that FIG. 1 illustrates only one device server 60.

[0037] <Administration Server 70> The management server 70 is capable of communicating with the vehicle 20 and the multiple devices 30. The management server 70 includes an execution device 71, a storage device 72, and a communication module 73. The communication module 73 communicates with the device server 60 via a wireless communication line. The communication module 73 is also capable of wireless communication with the communication module 21 of the vehicle 20. The storage device 72 stores a server program PS, a confirmation program PM, and a database DB. When executed by the execution device 71, the server program PS 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 confirmation program PM will be described later.

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

[0039] As shown in Figure 4, the data DA for one vehicle 20 includes the type of digital key registered to the vehicle 20, the registered devices 30, and the relationships between the registered devices 30. The hierarchy is determined by 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.

[0040] 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, a second device 30B, a third device 30C, a fourth device 30D, a fifth device 30E, a sixth device 30F, and a seventh device 30G.

[0041] In the data DA, the device 30 whose type of digital key is registered as the owner key KO is the first device 30A. In other words, the first device 30A is the owner device 40.

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

[0043] More specifically, in the data DA, the devices 30 whose digital key type is registered as the 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.

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

[0045] In the data DA, the relationship between the second device 30B and the first device 30A is such that a friend key KF is registered in the second device 30B based on a registration request from the first device 30A. In the data DA, the relationship between the fifth device 30E and the first device 30A is such that a friend key KF is registered in the fifth device 30E based on a registration request from the first device 30A.

[0046] In the data DA, the relationship between the third device 30C and the second device 30B is such that a non-friend key KN is registered in the third device 30C based on a registration request from the second device 30B. In the data DA, the relationship between the fourth device 30D and the second device 30B is such that a non-friend key KN is registered in the fourth device 30D based on a registration request from the second device 30B.

[0047] In the data DA, the relationship between the sixth device 30F and the fifth device 30E is such that a non-friend key KN is registered in the sixth device 30F based on a registration request from the fifth device 30E. In the data DA, the relationship between the seventh device 30G and the fifth device 30E is such that a non-friend key KN is registered in the seventh device 30G based on a registration request from the fifth device 30E.

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

[0049] <About the associated digital key> In the embodiment, a first digital key is registered as a non-friend key KN in the third device 30C, a second digital key is registered as a friend key KF in the second device 30B, and a third digital key is registered as an owner key KO in the first device 30A.

[0050] The relationship between the third device 30C and the second device 30B is such that the first digital key is registered in the third device 30C based on a registration request from the second device 30B in which the second digital key is registered. The second digital key is the digital key that generated the first digital key. In other words, the second digital key is a digital key one generation older than the first digital key.

[0051] The relationship between the second device 30B and the first device 30A is such that the second digital key is registered in the second device 30B based on a registration request from the first device 30A in which the third digital key is registered. The third digital key is the digital key that generated the second digital key. In other words, the third digital key is a digital key one generation older than the second digital key.

[0052] The second digital key that generated the first digital key is a digital key associated with the first digital key. The third digital key that generated the second digital key is a digital key associated with the second digital key. The third digital key that generated the second digital key that is associated with the first digital key is also a digital key associated with the first digital key. In other words, the third digital key is a digital key two generations older than the first digital key.

[0053] When a digital key generates a new digital key, the new digital key is associated with the digital key that generated the new digital key and the digital keys associated with the digital key that generated the new digital key. For example, when a first digital key generates a new digital key, the first digital key, the second digital key, and the third digital key are all digital keys associated with the digital key newly generated by the first digital key. In other words, all digital keys one or more generations before the digital key newly generated by the first digital key are digital keys associated with the digital key newly generated by the first digital key. In other words, in the relationship diagram shown in FIG. 4, digital keys one or more generations before that that are in a direct lineage relationship are digital keys associated with the newly generated digital key.

[0054] A fourth digital key is registered in the fourth device 30D. The relationship between the fourth device 30D and the second device 30B is such that the fourth digital key is registered in the fourth device 30D based on a registration request from the second device 30B in which the second digital key is registered. The second digital key is the digital key that generated the fourth digital key. In other words, the second digital key is a digital key one generation older than the fourth digital key.

[0055] There is no relationship between the third device 30C and the fourth device 30D in which a digital key has been registered based on a registration request. The first digital key has not generated a second digital key associated with the fourth digital key. The fourth digital key has not generated a second digital key associated with the first digital key. Therefore, the first digital key and the fourth digital key are digital keys that are not associated with each other.

[0056] Similarly, the first digital key registered in the third device 30C and the digital key registered in the fifth device 30E are digital keys that are not associated with each other. The first digital key registered in the third device 30C and the digital key registered in the sixth device 30F are digital keys that are not associated with each other. The first digital key registered in the third device 30C and the digital key registered in the seventh device 30G are digital keys that are not associated with each other.

[0057] <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 explanation, the process executed by the execution device 27 of the vehicle management device 26 will be described as the process executed by the vehicle 20. In the following explanation, the process executed by the execution device 36 will be described as the process executed by the device 30. In the following explanation, the process executed by the execution device 71 will be described as the process executed by the management server 70.

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

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

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

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

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

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

[0064] 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. That is, the registration request D11 is a request to store the owner key information DKO, which is the key information DK, in the device 30. 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0080] Thereafter, when the management server 70 receives a key track request D23 for the friend key KF, the management server 70 performs processing in step S29. In step S29, the management server 70 performs registration management of the friend key KF. The key track request D23 is a request to store new authentication information AT in the vehicle 20.

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

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

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

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

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

[0086] <Registering a non-friend key KN> 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.

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

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

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

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

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

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

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

[0094] In step S46, the friend device 51 adds the signature information ATP1 to the unsigned non-friend key information DKNN. As a result, the friend device 51 generates non-friend key information DKN. Thereafter, the friend device 51 uploads the generated non-friend key information DKN to the URL link, which is the invitation information IV2. Then, the friend device 51 transmits a completion notification M32 to the third device 30C indicating that the completed non-friend key information DKN has been uploaded to the URL link.

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

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

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

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

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

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

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

[0102] After completing the registration management, the management server 70 transmits a key track completion notification M33 to the second device 30B. 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.

[0103] <Delete non-friend key KN> 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.

[0104] <Deletion of non-friend key KN from friend device 51 by deletion reservation D41> As shown in FIG. 8, the management system 10 performs a series of processes to delete the non-friend key KN from the friend device 51 based on the deletion reservation D41.

[0105] 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 deletion reservation D41 for the non-friend key KN is generated. The deletion reservation D41 is a command to reserve the deletion of the non-friend key KN.

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

[0107] Thereafter, when the management server 70 receives the deletion reservation D41 of the non-friend key KN, it performs the process of step S62. In step S62, the management server 70 generates a pending notification M41 indicating that the deletion reservation is pending in accordance with the deletion reservation D41. Then, the management server 70 transmits the pending notification M41 to the friend device 51.

[0108] Thereafter, when the friend device 51 receives the pending notification M41, the friend device 51 performs the process of step S63. In step S63, the friend device 51 displays, on the HMI 32, information indicating that the deletion of the non-friend key KN that is the target of the deletion reservation D41 is pending.

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

[0110] In step S65, the management server 70 confirms that the predetermined condition RC is satisfied. If the management server 70 confirms that the predetermined condition RC is satisfied, the management server 70 advances the process to step S66.

[0111] 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 deletion reservation D41. Then, the management server 70 transmits the deletion request D42 to the non-friend device 52.

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

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

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

[0115] 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 target of the deletion reservation 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.

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

[0117] 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 deletion reservation D41 has been completed.

[0118] 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 target of the deletion reservation 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.

[0119] <Deletion of non-friend key KN due to deletion in non-friend device 52> 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.

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

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

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

[0123] 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 that was deleted in step S81. Then, the management server 70 transmits the deletion request D51 to the vehicle 20.

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

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

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

[0127] <Generation of confirmation notification M62 by management server 70 in the first embodiment> Depending on the user of the non-friend device 52, it is possible that an operation A not included in the authority information ATP7 stored in the non-friend device 52 may be performed on the vehicle 20. In the embodiment, the range of functions of the vehicle 20 that the non-friend device 52 can perform as the non-friend key KN, which are included in the authority information ATP7 in the non-friend key KN, is control of turning on the power to the vehicle 20 and control of unlocking and locking the doors of the vehicle 20. For example, control of starting the engine of the vehicle 20 is operation A not included in the authority information ATP7 stored in the non-friend device 52.

[0128] 10 is an explanatory diagram showing the flow of a series of processes executed by the management server 70 in the management system 10 when a user of the third device 30C, which is a non-friend device 52, performs an operation A on the vehicle 20 that is not included in the authority information ATP7 in the non-friend key KN. As shown in FIG. 1, in the management server 70, the storage device 72 stores a confirmation program PM. The execution device 71 executes the confirmation program PM stored in the storage device 72. As a result, the management server 70 executes a series of processes.

[0129] The owner device 40 is the first device 30A that stores key information DK indicating an owner key KO through the series of processes shown in FIG. 5. The owner key KO is registered in the first device 30A as a third digital key. The non-friend device 52 is the third device 30C that stores key information DK indicating a non-friend key KN through the series of processes shown in FIG. 7. The non-friend key KN is registered in the third device 30C as a first digital key. As described above, the third digital key is associated with the first digital key. In other words, the owner device 40 is a device 30 that stores information about a digital key associated with the first digital key.

[0130] When the user of the non-friend device 52 performs an operation A on the vehicle 20 that is not included in the authority information ATP7 in the non-friend key KN, the vehicle 20 performs processing in step S91. The following describes a case where the user of the non-friend device 52 performs engine start control on the vehicle 20 as an operation A that is not included in the authority information ATP7.

[0131] In step S91, the vehicle 20 generates a first request notification M61. The first request notification M61 is a notification requesting permission for operation A when operation A that is not included in the authority information ATP7 in the non-friend key KN of the third device 30C is performed on the vehicle 20. The vehicle 20 transmits the first request notification M61 to the management server 70.

[0132] The management server 70 is configured to be able to receive the first request notification M61 from the vehicle 20. Upon receiving the first request notification M61, the management server 70 performs processing of step S92. In step S92, the management server 70 generates a confirmation notification M62, which is a notification requesting permission for operation A not included in the authority information ATP7, in accordance with the first request notification M61. The confirmation notification M62 includes information for allowing the owner device 40 to set, through operation of the owner device 40, whether or not to allow operation A not included in the authority information ATP7 in the non-friend key KN. The confirmation notification M62 includes information for allowing the owner device 40 to set a predetermined termination condition EC, which will be described later, through operation of the owner device 40. The management server 70 transmits the confirmation notification M62 to the owner device 40.

[0133] <Processing performed by the owner device 40 after receiving the confirmation notification M62> The owner device 40 is configured to be able to receive the confirmation notification M62 from the management server 70. When the owner device 40 receives the confirmation notification M62, the owner device 40 performs the process of step S93. In step S93, the owner device 40 presents an image on the HMI 32 that prompts the user of the owner device 40 to set whether or not to permit operation A, which is not included in the authority information ATP7 in the non-friend key KN.

[0134] FIG. 13 is an example of an image presented on the HMI 32 of the owner device 40, which allows the user of the owner device 40 to set whether or not to permit operation A that is not included in the authority information ATP7 for the non-friend key KN.

[0135] The user of the owner device 40 follows the instructions presented on the HMI 32 and selects either "YES" or "NO" using the radio button for operation A, "engine start control of the vehicle 20."

[0136] <Step S93: YES> If the user of the owner device 40 selects "YES" using the radio button and then presses "OK" (step S93: YES), the owner device 40 performs the process of step S94 shown in Fig. 11. In the process of step S94, the owner device 40 presents an image on the HMI 32 that prompts the user to select whether or not to set a termination condition EC for permission of operation A.

[0137] <Present an image to select whether or not to set the termination condition EC> FIG. 14 is an example of an image presented on the HMI 32 of the owner device 40 in the process of step S94, which prompts the user of the owner device 40 to select whether or not to set an end condition EC for permission of operation A.

[0138] The user of the owner device 40 selects either "YES" or "NO" using the radio button as to whether or not to set the termination condition EC, following the guidance presented on the HMI 32. If the user of the owner device 40 selects "YES" using the radio button, the user of the owner device 40 can select the termination condition EC using the radio button.

[0139] When the user of the owner device 40 selects "Until the vehicle 20 is powered off" using the radio buttons and then presses "OK," "Until the vehicle 20 is powered off" is selected as the termination condition EC. When the user of the owner device 40 selects "Until YYYY / MM / DD" using the radio buttons, the user can input any date. When the user inputs any date in "Until YYYY / MM / DD" and then presses "OK," "Until YYYY / MM / DD" with the date input by the user is selected as the termination condition EC. When the user of the owner device 40 selects "Until X number of engine starts" using the radio buttons, the user can input any natural number into "X" in "Until X number of engine starts." When the user inputs any natural number into "X" in "Until X number of engine starts" and then presses "OK," "Until X number of engine starts" with the natural number input by the user is selected as the termination condition EC. If the user of the owner device 40 selects "NO" and then presses "OK", the termination condition EC is not set. Below, a case will be described in which the user of the owner device 40 selects "Until the power of the vehicle 20 is turned off" as the termination condition EC.

[0140] In step S94 shown in FIG. 11, the owner device 40 generates a permission notification M63. The permission notification M63 is a notification permitting operation A, which is not included in the authority information ATP7 in the non-friend key KN. The permission notification M63 includes "until the power of the vehicle 20 is turned off" as a default termination condition EC. If the termination condition EC is not set in the processing of step S94, the permission notification M63 does not include the termination condition EC. The owner device 40 transmits the permission notification M63 to the management server 70.

[0141] <Processing performed by the management server 70 after receiving the permission notification M63> When the management server 70 receives the permission notification M63, it performs processing in step S95. In step S95, the management server 70 generates a permission request D61. The permission request D61 includes a signal to add operation A, which is not included in the authority information ATP7 for the non-friend key KN, to the authority information ATP7. The permission request D61 includes a signal to delete operation A, which is not included in the authority information ATP7 for the non-friend key KN, from the authority information ATP7 when a predetermined termination condition EC included in the permission notification M63 is met. The management server 70 transmits the permission request D61 to the vehicle 20. That is, when the predetermined termination condition EC is met, the management server 70 transmits a signal to the vehicle 20 prohibiting operation A, which is not included in the authority information ATP7 for the non-friend key KN.

[0142] After transmitting the permission request D61 to the vehicle 20, the management server 70 performs processing in step S96. In step S96, the management server 70 generates a permission notification M64. The permission notification M64 includes information to be presented to the HMI 32 indicating that the owner device 40 has permitted operation A, which is not included in the authority information ATP7 in the non-friend key KN. The permission notification M64 includes information that causes the non-friend device 52 to present the default termination condition EC selected by the owner device 40 to the HMI 32. The management server 70 transmits the permission notification M64 to the non-friend device 52.

[0143] When the vehicle 20 receives the permission request D61, it performs processing in step S97. In step S97, the vehicle 20 changes the authority information ATP7 in the non-friend key KN stored in the vehicle 20. Before receiving the permission request D61, the vehicle 20 stored the authority information ATP7 in the non-friend key KN with the following operations: power-on control of the vehicle 20, and unlocking and locking control of the doors of the vehicle 20. When the vehicle 20 receives the permission request D61, the vehicle 20 adds operation A included in the permission request D61 to the authority information ATP7 in the non-friend key KN. In other words, the vehicle 20 adds engine start control of the vehicle 20 to the authority information ATP7 in the non-friend key KN. Through the processing in step S97, the authority information ATP7 in the non-friend key KN is changed to engine start control of the vehicle 20, power-on control of the vehicle 20, and unlocking and locking control of the doors of the vehicle 20. This allows the user of the non-friend device 52 to perform, on the vehicle 20, the operation A that is not included in the authority information ATP7 in the non-friend key KN at the start of this series of processes.

[0144] In the first embodiment, the vehicle 20 monitors whether or not the predetermined termination condition EC is satisfied. In step S97, the vehicle 20 starts monitoring whether or not the predetermined termination condition EC is satisfied.

[0145] When the non-friend device 52 receives the permission notification M64, it performs the process of step S98. In step S98, the non-friend device 52 presents to the HMI 32 a notification indicating that the owner device 40 has permitted operation A, which is not included in the authority information ATP7 in the non-friend key KN. The non-friend device 52 presents to the HMI 32 a predetermined termination condition EC.

[0146] <When the default termination condition EC is met> When the power of the vehicle 20 is turned off, the vehicle 20 determines that the predetermined termination condition EC is met. When the predetermined termination condition EC is met, the vehicle 20 performs processing of step S99. In step S99, the vehicle 20 performs processing to prohibit the user of the non-friend device 52 from performing operation A on the vehicle 20, and processing to generate a notification M65 of the prohibition.

[0147] The vehicle 20 changes the authority information ATP7 stored in the vehicle 20 as a process for prohibiting the user of the non-friend device 52 from performing operation A on the vehicle 20. Before the predetermined termination condition EC is satisfied, the vehicle 20 stores, as its authority information ATP7, the following operations: engine start control of the vehicle 20, power on control of the vehicle 20, and unlocking and locking control of the doors of the vehicle 20. When the predetermined termination condition EC is satisfied, the vehicle 20 deletes from the authority information ATP7 the operation A that was added to the authority information ATP7 based on the permission request D61 and that was not included in the authority information ATP7 of the non-friend key KN at the start of this series of processes. In other words, the vehicle 20 deletes the engine start control of the vehicle 20 from the authority information ATP7. By the process of step S99, the authority information ATP7 of the non-friend key KN is changed to power on control of the vehicle 20 and unlocking and locking control of the doors of the vehicle 20. As a result, the operation A that is not included in the authority information ATP7 in the non-friend key KN at the start of this series of processes is prohibited for the user of the non-friend device 52.

[0148] The establishment notification M65 includes information indicating that the vehicle 20 has prohibited the user of the non-friend device 52 from performing operation A, which is not included in the authority information ATP7, due to the establishment of the predetermined termination condition EC. The vehicle 20 transmits the establishment notification M65 to the management server 70.

[0149] When the management server 70 receives the establishment notification M65, it performs processing of step S100. In step S100, the management server 70 generates a prohibition notification M66. The prohibition notification M66 includes information indicating that the operation A, which is not included in the authority information ATP7 in the non-friend key KN, is prohibited from being performed on the vehicle 20 because the predetermined termination condition EC has been established. The management server 70 transmits the prohibition notification M66 to the non-friend device 52.

[0150] When the non-friend device 52 receives the prohibition notification M66, it performs processing in step S101. In step S101, the non-friend device 52 presents to the HMI 32 a notification indicating that the predetermined termination condition EC has been met and therefore the operation A, which is not included in the authority information ATP7 in the non-friend key KN, is prohibited from being performed on the vehicle 20. Thereafter, the management system 10 ends the series of processes.

[0151] <Step S93: NO> In step S93 shown in FIG. 10, if the user of the owner device 40 selects "NO" shown in FIG. 13 using the radio button and then presses "OK" (step S93: NO), the process continues to FIG.

[0152] 12, the owner device 40 generates a rejection notification M67. The rejection notification M67 is a notification to reject operation A, which is not included in the authority information ATP7 in the non-friend key KN. The owner device 40 transmits the rejection notification M67 to the management server 70.

[0153] <Processing performed by the management server 70 after receiving the rejection notification M67> When the management server 70 receives the rejection notification M67, it performs the process of step S102. In step S102, the management server 70 generates a rejection notification M68. The rejection notification M68 is a notification indicating that the owner device 40 has rejected operation A, which is not included in the authority information ATP7 in the non-friend key KN. The management server 70 transmits the rejection notification M68 to the non-friend device 52.

[0154] When the non-friend device 52 receives the rejection notification M68, it performs the process of step S103. In step S103, the non-friend device 52 presents to the HMI 32 a notification indicating that the owner device 40 has rejected operation A, which is not included in the authority information ATP7 in the non-friend key KN. Thereafter, the management system 10 ends the series of processes.

[0155] <Operation of the First Embodiment> The first digital key is registered as a non-friend key KN in the third device 30C, which is a non-friend device 52. The third device 30C is a device 30 that stores information about the first digital key.

[0156] A third digital key is registered as an owner key KO in the owner device 40. The third digital key is a digital key associated with the first digital key. In other words, the owner device 40 is a device 30 that stores information about the digital key associated with the first digital key.

[0157] When a user of the third device 30C to which the first digital key is registered performs an operation A on the vehicle 20 that is not included in the authority information ATP7 in the non-friend key KN, the management server 70 sends a confirmation notification M62 to the owner device 40.

[0158] <Effects of the first embodiment> (1-1) The management server 70 can allow the owner of the vehicle 20, who is the user of the owner device 40, to know how the vehicle 20 is being used by the user of the third device 30C to which the first digital key is registered.

[0159] Furthermore, the management server 70 can allow the owner of the vehicle 20 to permit or deny the user of the third device 30C to which the first digital key is registered from using functions of the vehicle 20. This allows the management server 70 to convey the intention of the owner of the vehicle 20 to the user of the third device 30C to which the first digital key is registered.

[0160] (1-2) The management server 70 is configured to receive, from the vehicle 20, a first request notification M61 requesting permission from the owner device 40 that stores information about the digital key associated with the first digital key when an operation A not included in the authority information ATP7 of the non-friend key KN is performed on the vehicle 20. When the management server 70 receives the first request notification M61, the management server 70 transmits a confirmation notification M62 to the owner device 40. This allows the management server 70 to inform the owner of the vehicle 20 that the user of the third device 30C to which the first digital key is registered has performed the operation A not included in the authority information ATP7 of the non-friend device 52. Furthermore, when the user of the third device 30C to which the first digital key is registered performs the operation A not included in the authority information ATP7, the management server 70 can allow the owner of the vehicle 20 to permit or deny the user of the third device 30C to which the first digital key is registered from using functions of the vehicle 20.

[0161] (1-3) Some owners of the vehicle 20 may permit a user of the third device 30C to which the first digital key is registered to use a function of the vehicle 20 and then prohibit that user from using the function. When the management server 70 receives a notification permitting operation A not included in the authority information ATP7 from the owner device 40 that stores information about the digital key associated with the first digital key, the management server 70 transmits a permission request D61 to the vehicle 20. The permission request D61 includes a signal to add operation A not included in the authority information ATP7 of the first digital key to the authority information ATP7. The permission request D61 includes a signal to delete operation A not included in the authority information ATP7 of the first digital key from the authority information ATP7 when a predetermined termination condition EC is met. As a result, the management server 70 prohibits operation A not included in the authority information ATP7 of the first digital key from being performed on the vehicle 20 when the predetermined termination condition EC is met. This allows the management server 70 to reassure the owner of the vehicle 20, who is the user of the owner device 40 that stores information about the digital key associated with the first digital key.

[0162] (1-4) The confirmation notification M62 sent by the management server 70 to the owner device 40 that stores information about the digital key associated with the first digital key includes information that allows the owner device 40 to set a predetermined termination condition EC through operation of the owner device 40.

[0163] The management server 70 sets the default termination condition EC in accordance with the information indicating the default termination condition EC received from the owner device 40. This allows the management server 70 to set the default termination condition EC in accordance with the intention of the owner of the vehicle 20 who has received the confirmation notification M62.

[0164] <Modification of the first embodiment> The first embodiment can be modified as follows: The first embodiment and the following modifications of the first embodiment can be combined with each other to the extent that they are not technically inconsistent.

[0165] The management server 70 may send a notification including information for causing the owner device 40 to set a predetermined termination condition EC, as a notification separate from the confirmation notification M62. The management server 70 may transmit, as the permission request D61, only a signal to the vehicle 20 to add the operation A that is not included in the authority information ATP7 in the non-friend key KN to the authority information ATP7. In this case, the management server 70 may transmit, as a request separate from the permission request D61, a signal to the vehicle 20 to delete the operation A that is not included in the authority information ATP7 in the non-friend key KN from the authority information ATP7 when a predetermined termination condition EC is met.

[0166] In step S98 shown in FIG. 11 , the non-friend device 52 may change the authority information ATP7 stored in the non-friend device 52 to the same extent as the authority information ATP7 stored in the vehicle 20 in step S97. In this case, in step S96, the management server 70 transmits a signal to the non-friend device 52 permitting operation A, which is not included in the authority information ATP7 of the non-friend key KN. When the non-friend device 52 receives the signal permitting operation A, which is not included in the authority information ATP7 of the non-friend key KN, it changes the authority information ATP7 stored in the non-friend device 52. Before receiving the signal, the non-friend device 52 stored the authority information ATP7 with the vehicle 20 power on control and the vehicle 20 door unlock control and vehicle 20 door lock control. When the non-friend device 52 receives the signal, it adds the vehicle 20 engine start control to the authority information ATP7 of the non-friend key KN. As a result, the authority information ATP7 stored in the non-friend device 52 is changed to include engine start control of the vehicle 20, power-on control of the vehicle 20, and door unlocking and locking control of the vehicle 20.

[0167] Below, we will explain the case where, in step S98, the management server 70 changes the authority information ATP7 stored in the non-friend device 52 to the same as the authority information ATP7 stored in the vehicle 20 in step S97. In this case, in step S101, the management server 70 changes the authority information ATP7 stored in the non-friend device 52 to the same as the authority information ATP7 stored in the vehicle 20 in step S99.

[0168] In step S95, the management server 70 may change the authority information ATP7 for the non-friend key KN stored in the database DB in the same way as the authority information ATP7 for the non-friend key KN stored by the vehicle 20 in step S97. In step S100, the management server 70 may change the authority information ATP7 for the non-friend key KN stored in the database DB in the same way as the authority information ATP7 for the non-friend key KN stored by the vehicle 20 in step S99.

[0169] In addition to the permission request D61, the management server 70 may send to the vehicle 20 a signal to store the state of the non-friend key KN as a fade-out state when a predetermined termination condition EC is met. In this case, in step S99, the vehicle 20 performs a process of prohibiting operation A not included in the authority information ATP7 and a process of generating a notification of establishment M65 after a predetermined fade-out period has elapsed. The case where the predetermined termination condition EC is met is not limited to the case where a predetermined fade-out period has elapsed. For example, the predetermined termination condition EC may be when the vehicle 20 is located at a predetermined location. In this case, in step S99, the vehicle 20 performs a process of prohibiting operation A on the vehicle 20 by the user of the non-friend device 52 and a process of generating a notification of establishment M65 after the vehicle 20 is located at the predetermined location. The predetermined location is, for example, a predetermined parking lot.

[0170] (Second embodiment) The management server 70 according to the second embodiment will be described below with reference to Figures 1, 5, 7, and 13 to 17. The second embodiment will be described mainly focusing on the differences from the first embodiment. The management server 70 in the second embodiment is configured to be able to receive a second request notification M71 from a third device 30C, which is a non-friend device 52. The second request notification M71 will be described later.

[0171] <Generation of confirmation notification M72 by management server 70 in the second embodiment> 15 is an explanatory diagram showing the flow of a series of processes executed by the management server 70 in the management system 10 of the second embodiment. As shown in FIG. 1, in the management server 70, the storage device 72 stores a confirmation program PM. The execution device 71 executes the confirmation program PM stored in the storage device 72. This causes the management server 70 to execute a series of processes.

[0172] The owner device 40 is the first device 30A that stores key information DK indicating an owner key KO through the series of processes shown in FIG. 5. The owner key KO is registered in the first device 30A as a third digital key. The non-friend device 52 is the third device 30C that stores key information DK indicating a non-friend key KN through the series of processes shown in FIG. 7. The non-friend key KN is registered in the third device 30C as a first digital key. As described above, the third digital key is associated with the first digital key. In other words, the owner device 40 is a device 30 that stores information about a digital key associated with the first digital key.

[0173] The following describes a case in which the non-friend device 52 executes an operation to request permission from the owner device 40 to perform operation A that is not included in the authority information ATP7 stored in the non-friend device 52. In this case, the non-friend device 52 performs the process of step S201 shown in FIG. 15 . In step S201, the non-friend device 52 generates a second request notification M71. The second request notification M71 is a notification requesting permission for operation A that is not included in the authority information ATP7 stored in the non-friend device 52. The following describes a case in which the user of the non-friend device 52 requests permission from the owner device 40 to control the start of the engine of the vehicle 20 as operation A that is not included in the authority information ATP7. The non-friend device 52 transmits the second request notification M71 to the management server 70.

[0174] Upon receiving the second request notification M71, the management server 70 performs processing in step S202. In step S202, the management server 70 generates a confirmation notification M72, which is a notification requesting permission to perform operation A not included in the authority information ATP7, in accordance with the second request notification M71. The confirmation notification M72 includes information for allowing the owner device 40 to set, through operation of the owner device 40, whether or not to permit operation A not included in the authority information ATP7 in the non-friend key KN. The confirmation notification M72 includes information for allowing the owner device 40 to set a predetermined termination condition EC, which will be described later, through operation of the owner device 40. The management server 70 transmits the confirmation notification M72 to the owner device 40.

[0175] <Processing Performed by the Owner Device 40 After Receiving the Confirmation Notification M72> The owner device 40 is configured to be able to receive the confirmation notification M72 from the management server 70. When the owner device 40 receives the confirmation notification M72, the owner device 40 performs the process of step S203. In step S203, similar to the process of step S93 in the first embodiment, the owner device 40 displays on the HMI 32 the image shown in FIG. 13 that prompts the user to set whether or not to permit operation A that is not included in the authority information ATP7 in the non-friend key KN.

[0176] The user of the owner device 40 selects either "YES" or "NO" for operation A using the radio button in accordance with the guidance shown in FIG. 13 presented on the HMI 32.

[0177] <Step S203: YES> If the user of the owner device 40 selects "YES" (step S203: YES), the owner device 40 performs the process of step S204 shown in Fig. 16. In the process of step S204, similar to the process of step S94 in the first embodiment, the owner device 40 presents on the HMI 32 an image shown in Fig. 14 that prompts the user to select whether or not to set an end condition EC for permission of operation A. The user of the owner device 40 selects either "YES" or "NO" as to whether or not to set an end condition EC, following the guidance shown in Fig. 14 presented on the HMI 32.

[0178] In step S204, the owner device 40 generates a permission notification M73. The permission notification M73 is a notification permitting operation A, which is not included in the authority information ATP7 in the non-friend key KN. If the user of the owner device 40 selects "YES" as to whether to set an end condition EC according to the guidance of FIG. 14 presented on the HMI 32, the permission notification M73 includes the default end condition EC selected by the user of the owner device 40. If the user of the owner device 40 selects "NO" as to whether to set an end condition EC according to the guidance of FIG. 14 presented on the HMI 32, the permission notification M73 does not include the default end condition EC. The owner device 40 transmits the permission notification M73 to the management server 70.

[0179] <Processing performed by the management server 70 after receiving the permission notification M73> When the management server 70 receives the permission notification M73, it performs the process of step S205 shown in FIG. 16. In step S205, the management server 70 generates a permission request D71. The permission request D71 includes a signal for adding operation A, which is not included in the authority information ATP7 in the non-friend key KN, to the authority information ATP7. The management server 70 transmits the permission request D71 to the vehicle 20.

[0180] In the second embodiment, the management server 70 monitors whether or not the predetermined termination condition EC is met. In step S205, the management server 70 starts monitoring whether or not the predetermined termination condition EC is met.

[0181] After transmitting the permission request D71 to the vehicle 20, the management server 70 performs processing in step S206. In step S206, the management server 70 generates a permission notification M74. The permission notification M74 includes information for causing the HMI 32 of the non-friend device 52 to display that operation A, which is not included in the authority information ATP7 in the non-friend key KN, has been permitted by the owner device 40. The permission notification M74 includes information for causing the HMI 32 of the non-friend device 52 to display the default termination condition EC selected by the owner device 40. The management server 70 transmits the permission notification M74 to the non-friend device 52.

[0182] When the vehicle 20 receives the permission request D71, it performs processing in step S207. In step S207, the vehicle 20 changes the authority information ATP7 in the non-friend key KN stored in the vehicle 20. Before receiving the permission request D71, the vehicle 20 stored the authority information ATP7 in the non-friend key KN with the following operations: power on control for the vehicle 20, and unlocking and locking control of the doors of the vehicle 20. When the vehicle 20 receives the permission request D71, the vehicle 20 adds operation A included in the permission request D71 to the authority information ATP7 in the non-friend key KN. In other words, the vehicle 20 adds engine start control for the vehicle 20 to the authority information ATP7 in the non-friend key KN. Through the processing in step S207, the authority information ATP7 in the non-friend key KN is changed to engine start control for the vehicle 20, power on control for the vehicle 20, and unlocking and locking control of the doors of the vehicle 20. This allows the user of the non-friend device 52 to perform, on the vehicle 20, the operation A that is not included in the authority information ATP7 in the non-friend key KN at the start of this series of processes.

[0183] When the non-friend device 52 receives the permission notification M74, it performs the process of step S208. In step S208, the non-friend device 52 presents to the HMI 32 a notification indicating that the owner device 40 has permitted operation A, which is not included in the authority information ATP7 in the non-friend key KN. The non-friend device 52 presents to the HMI 32 a predetermined termination condition EC.

[0184] <When the default termination condition EC is met> In the second embodiment, the management server 70 monitors whether a predetermined termination condition EC is satisfied. When the predetermined termination condition EC is satisfied, the management server 70 performs processing in step S209. In step S209, the management server 70 generates a prohibition request D72 and a prohibition notification M75. The prohibition request D72 includes a signal to delete from the authority information ATP7 an operation A that was added to the authority information ATP7 due to the permission request D71 and is not included in the authority information ATP7 in the non-friend key KN at the start of this series of processes. The management server 70 transmits the prohibition request D72 to the vehicle 20. That is, when the predetermined termination condition EC is satisfied, the management server 70 transmits to the vehicle 20 a signal to prohibit the operation A that is not included in the authority information ATP7 in the non-friend key KN at the start of this series of processes.

[0185] The prohibition notification M75 includes information indicating that, when the predetermined termination condition EC is met, the management server 70 prohibits the operation A, which is not included in the authority information ATP7 in the non-friend key KN at the start of this series of processes, from being performed on the vehicle 20. The management server 70 transmits the prohibition notification M75 to the non-friend device 52.

[0186] When the vehicle 20 receives the prohibition request D72, it performs processing in step S210. In the processing in step S210, the vehicle 20 modifies the authority information ATP7 stored in the vehicle 20 as processing for prohibiting operation A on the vehicle 20 by the user of the non-friend device 52. Before the predetermined termination condition EC is satisfied, the vehicle 20 stores, as the authority information ATP7, engine start control of the vehicle 20, power on control of the vehicle 20, and unlocking and locking control of the doors of the vehicle 20. When the vehicle 20 receives the prohibition request D72, it deletes the operation A added based on the permission request D71 from the authority information ATP7. In other words, the vehicle 20 deletes the engine start control of the vehicle 20 from the authority information ATP7. Through the processing in step S210, the authority information ATP7 is changed to power on control of the vehicle 20 and unlocking and locking control of the doors of the vehicle 20. As a result, the operation A that is not included in the authority information ATP7 in the non-friend key KN at the start of this series of processes is prohibited for the user of the non-friend device 52.

[0187] When the non-friend device 52 receives the prohibition notification M75, it performs the process of step S211. In step S211, the non-friend device 52 presents to the HMI 32 a notification indicating that operation A, which is not included in the authority information ATP7 at the start of this series of processes, has been prohibited because the predetermined termination condition EC has been met. Thereafter, the management system 10 ends the series of processes.

[0188] <Step S203: NO> In step S203, if the user of the owner device 40 selects "NO" shown in FIG. 13 using the radio button and then presses "OK" (step S203: NO), the owner device 40 generates a rejection notification M76 shown in FIG. 17. The rejection notification M76 is a notification rejecting operation A that is not included in the authority information ATP7 in the non-friend key KN. The owner device 40 transmits the rejection notification M76 to the management server 70.

[0189] <Processing Performed by the Management Server 70 After Receiving the Rejection Notification M76> When the management server 70 receives the rejection notification M76, it performs the process of step S212. In step S212, the management server 70 generates a rejection notification M77. The rejection notification M77 is a notification indicating that the owner device 40 has rejected operation A, which is not included in the authority information ATP7 in the non-friend key KN. The management server 70 transmits the rejection notification M77 to the non-friend device 52.

[0190] When the non-friend device 52 receives the rejection notification M77, it performs the process of step S213. In step S213, the non-friend device 52 presents to the HMI 32 a notification indicating that the owner device 40 has rejected the operation A, which is not included in the authority information ATP7 in the non-friend key KN. Thereafter, the management system 10 ends the series of processes.

[0191] <Operation of the Second Embodiment> There is a possibility that the owner of the vehicle 20 and the user of the non-friend device 52 do not know each other. Therefore, there is a possibility that the user of the non-friend device 52 is unable to contact the owner of the vehicle 20.

[0192] The first digital key is registered as a non-friend key KN in the third device 30C, which is a non-friend device 52. The third device 30C is a device 30 that stores information about the first digital key.

[0193] A third digital key is registered as an owner key KO in the owner device 40. The third digital key is a digital key associated with the first digital key. In other words, the owner device 40 is a device 30 that stores information about the digital key associated with the first digital key.

[0194] The third device 30C, in which the first digital key is registered, transmits a second request notification M71 to the management server 70. Upon receiving the second request notification M71, the management server 70 transmits a confirmation notification M72 to the owner device 40.

[0195] <Effects of the second embodiment> (2-1) Even when the user of the third device 30C to which the first digital key is registered is not operating the vehicle 20, the management server 70 can allow the owner of the vehicle 20, who is the user of the owner device 40, to permit or deny operation A, which is not included in the authority information ATP7 of the non-friend device 52, performed by the user of the third device 30C to which the first digital key is registered. This improves convenience for the user of the third device 30C to which the first digital key is registered.

[0196] <Modification of the second embodiment> The second embodiment can be modified as follows: The second embodiment described above and the following modifications of the second embodiment can be combined and implemented as long as they are not technically inconsistent.

[0197] The management server 70 may send a notification including information for causing the owner device 40 to set a predetermined termination condition EC, as a notification separate from the confirmation notification M72. The range of vehicle 20 functions that a digital key can perform may be determined by the authority information ATP7 stored in the device 30 that stores key information DK indicating the digital key. The following describes a case where the authority information ATP7 of the digital key stored in the vehicle 20 to which the digital key is registered is power-on control and door unlock and lock control. In this case, if the authority information ATP7 stored in the device 30 that stores the key information DK indicating the digital key is door unlock and lock control, the digital key can perform door unlock and lock control for the vehicle 20. If the authority information ATP7 stored in the device 30 that stores the key information DK indicating the digital key is power-on control and door unlock and lock control, the digital key can perform power-on control and door unlock and lock control for the vehicle 20. If the authority information ATP7 stored in the device 30 that stores the key information DK indicating the digital key is for controlling the engine start of the vehicle 20, turning on the power, and unlocking and locking the doors, the digital key can perform the engine start control of the vehicle 20, turning on the power, and unlocking and locking the doors of the vehicle 20.

[0198] The following describes a case where the range of vehicle 20 functions that can be performed by a digital key is determined by the authority information ATP7 stored in the device 30 that stores the key information DK representing the digital key. In this case, in step S206 shown in FIG. 16 , the management server 70 transmits a permission request D71, which is a signal permitting operation A not included in the authority information ATP7 for the non-friend key KN, to the non-friend device 52, which is the third device 30C to which the first digital key is registered. Upon receiving the signal permitting operation A not included in the authority information ATP7 for the non-friend key KN, the non-friend device 52 changes the authority information ATP7 for the non-friend key KN stored in the non-friend device 52. Before receiving the signal, the non-friend device 52 stored the authority information ATP7 for the non-friend key KN with the following permissions: power on control for the vehicle 20, and lock and unlock control for the doors of the vehicle 20. Upon receiving the signal, the non-friend device 52 adds engine start control for the vehicle 20 to the authority information ATP7 for the non-friend key KN. As a result, the authority information ATP7 for the non-friend key KN stored in the non-friend device 52 is changed to include engine start control of the vehicle 20, power-on control of the vehicle 20, and door unlock and lock control of the vehicle 20. In this case, the management server 70 does not need to send the permission request D71 to the vehicle 20. Below, a case will be described in which the management server 70 sends the permission request D71 to the non-friend device 52 in step S206. In this case, the management server 70 sends a prohibition request D72 to the non-friend device 52 in step S209. As a result, in step S211, the non-friend device 52 changes the authority information ATP7 stored therein, similar to the vehicle 20 in step S210 in the second embodiment. That is, the non-friend device 52 deletes the engine start control of the vehicle 20 from the authority information ATP7 stored therein.As a result, when the predetermined termination condition EC is met, the management server 70 prohibits the operation A that is not included in the authority information ATP7 in the non-friend key KN from being performed on the vehicle 20. This allows the management server 70 to reassure the owner of the vehicle 20, who is the user of the owner device 40 that stores information about the digital key associated with the first digital key.

[0199] In step S205, the management server 70 may change the authority information ATP7 for the non-friend key KN stored in the database DB in the same way as the authority information ATP7 for the non-friend key KN stored by the vehicle 20 in step S207. In step S209, the management server 70 may change the authority information ATP7 for the non-friend key KN stored in the database DB in the same way as the authority information ATP7 for the non-friend key KN stored by the vehicle 20 in step S210.

[0200] When a predetermined termination condition EC is satisfied, the management server 70 may store the state of the non-friend key KN as the fade-out state. In this case, in step S209, the management server 70 generates the prohibition request D72 and the prohibition notification M75 after a predetermined fade-out period has elapsed. The case where the predetermined termination condition EC is satisfied is not limited to the case where a predetermined fade-out period has elapsed. For example, the predetermined termination condition EC may be the case where the vehicle 20 is located at a predetermined location. In this case, in step S99, the vehicle 20 generates the prohibition request D72 and the prohibition notification M75 after being located at the predetermined location. The predetermined location is, for example, a predetermined parking lot.

[0201] (Third embodiment) The management server 70 according to the third embodiment will be described below with reference to Figs. 11 to 14 and 18. The third embodiment will be described mainly focusing on the differences from the first embodiment. The management server 70 in the third embodiment is configured to be able to transmit a confirmation notification M300 to the second device 30B, which is the friend device 51. The confirmation notification M300 will be described later.

[0202] <Generation of confirmation notification M300 by management server 70 in the third embodiment> 18 is an explanatory diagram showing the flow of a series of processes executed by the management server 70 in the management system 10 of the third embodiment. As shown in FIG. 1, in the management server 70, the storage device 72 stores a confirmation program PM. The execution device 71 executes the confirmation program PM stored in the storage device 72. This causes the management server 70 to execute a series of processes.

[0203] The friend device 51 is a second device 30B that stores key information DK indicating a friend key KF through the series of processes shown in FIG. 6. The friend key KF is registered in the second device 30B as a second digital key. The non-friend device 52 is a third device 30C that stores key information DK indicating a non-friend key KN through the series of processes shown in FIG. 7. The non-friend key KN is registered in the third device 30C as a first digital key. The second digital key is a digital key that generated the first digital key. In other words, the second digital key is a digital key associated with the first digital key. The second device 30B is a device 30 that stores information about a digital key associated with the first digital key.

[0204] As shown in FIG. 18, when a user of the third device 30C, which is a non-friend device, performs an operation A on the vehicle 20 that is not included in the authority information ATP7 in the non-friend key KN, the vehicle 20 performs the process of step S91.

[0205] In step S91, the vehicle 20 generates a first request notification M61. The first request notification M61 is a notification requesting permission for operation A when operation A that is not included in the authority information ATP7 in the non-friend key KN registered in the third device 30C is performed on the vehicle 20. The vehicle 20 transmits the first request notification M61 to the management server 70.

[0206] The management server 70 is configured to be able to receive the first request notification M61 from the vehicle 20. Upon receiving the first request notification M61, the management server 70 performs processing of step S300. In step S300, the management server 70 generates a confirmation notification M300, which is a notification requesting permission for operation A not included in the authority information ATP7, in accordance with the first request notification M61. The confirmation notification M300 includes information for setting, through the operation of the second device 30B, whether or not to permit operation A not included in the authority information ATP7 in the non-friend key KN. The management server 70 transmits the confirmation notification M300 to the second device 30B. That is, the management server 70 transmits the confirmation notification M300 to the second device 30B.

[0207] <Processing performed by the friend device 51 after receiving the confirmation notification M300> The second device 30B is configured to be able to receive a confirmation notification M300 from the management server 70. When the second device 30B receives the confirmation notification M300, the second device 30B performs the process of step S301. In step S301, the second device 30B presents on the HMI 32 an image that prompts the user of the second device 30B to set whether or not to permit operation A, which is not included in the authority information ATP7 in the non-friend key KN.

[0208] Figure 13 is an example of an image presented on the HMI 32 of the second device 30B, which allows the user of the second device 30B to set whether or not to allow operation A, which is not included in the authority information ATP7 for the non-friend key KN.

[0209] The user of the second device 30B follows the guidance presented on the HMI 32 and selects either "YES" or "NO" using the radio button for operation A, "engine start control of the vehicle 20."

[0210] <Step S301: YES> If the user of the second device 30B selects "YES" using the radio button and then presses "OK" (step S301: YES), the second device 30B performs the process of step S94 shown in Fig. 11, similar to the owner device 40 in the first embodiment. In the process of step S94, the second device 30B presents on the HMI 32 an image that prompts the user to select whether or not to set a termination condition EC for permission of operation A.

[0211] FIG. 14 is an example of an image presented on the HMI 32 of the second device 30B in the process of step S94, which prompts the user of the second device 30B to select whether or not to set an end condition EC for permission of operation A.

[0212] The user of the second device 30B selects either "YES" or "NO" using the radio button as to whether or not to set the termination condition EC, following the guidance presented on the HMI 32. If the user of the second device 30B selects "YES" using the radio button, the user of the second device 30B can select the termination condition EC using the radio button.

[0213] In step S94 shown in FIG. 11, the second device 30B generates a permission notification M63. The permission notification M63 is a notification permitting operation A, which is not included in the authority information ATP7 in the non-friend key KN. The permission notification M63 includes "until the power of the vehicle 20 is turned off" as a default termination condition EC. If the termination condition EC is not set in the processing of step S94, the permission notification M63 does not include the termination condition EC. The second device 30B transmits the permission notification M63 to the management server 70. Thereafter, the management system 10 performs a series of processes shown in FIG. 11.

[0214] <Step S301: If NO> In step S301 shown in FIG. 18, if the user of the second device 30B selects "NO" shown in FIG. 13 using the radio button and then presses "OK" (step S301: NO), the process continues to FIG.

[0215] 12, the second device 30B generates a rejection notification M67, similar to the owner device 40 in the first embodiment. The rejection notification M67 is a notification to reject operation A, which is not included in the authority information ATP7 in the non-friend key KN. The second device 30B transmits the rejection notification M67 to the management server 70. Thereafter, the management system 10 performs a series of processes shown in FIG.

[0216] <Operation of the Third Embodiment> The first digital key is registered as a non-friend key KN in the third device 30C, which is a non-friend device 52. The third device 30C is a device 30 that stores information about the first digital key.

[0217] A second digital key is registered as a friend key KF in the second device 30B, which is the friend device 51. The second digital key is a digital key that generated the first digital key. In other words, the second digital key is a digital key associated with the first digital key. The second device 30B is a device 30 that stores information about the digital key associated with the first digital key.

[0218] When a user of the third device 30C to which the first digital key is registered performs an operation A on the vehicle 20 that is not included in the authority information ATP7 in the non-friend key KN, the management server 70 sends a confirmation notification M300 to the second device 30B.

[0219] <Effects of the third embodiment> The management server 70 allows the user of the second device 30B, which stores information about the second digital key that generated the first digital key, to understand the usage status of the vehicle 20 by the user of the third device 30C, to which the first digital key is registered.

[0220] Furthermore, the management server 70 can allow the user of the second device 30B to permit or deny the user of the third device 30C to which the first digital key is registered from using functions of the vehicle 20. This allows the management server 70 to convey the intention of the user of the device 30 that stores information about the second digital key that generated the first digital key to the third device 30C to which the first digital key is registered.

[0221] <Modification of the third embodiment> The third embodiment can be modified as follows: The third embodiment described above and the following modifications of the third embodiment can be combined and implemented within the scope of technical compatibility.

[0222] The third embodiment is suitable for a case where the user who primarily drives the vehicle 20 is the user of the friend device 51. For example, if the owner of the vehicle 20 is a rental business or a sharing business, the user who primarily drives the vehicle 20 is the user of the friend device 51 to which the friend key KF is registered based on a registration request from the device 30 belonging to the owner of the vehicle 20. In this case, even if the user of a non-friend device 52 registered based on the registration request from the friend device 51 requests permission to use functions of the vehicle 20 from the owner of the vehicle 20, the request cannot reflect the intention of the user of the friend device 51 who primarily drives the vehicle 20. The management server 70 can allow the user of the friend device 51 who primarily drives the vehicle 20 to permit or deny the user of the non-friend device 52 from using functions of the vehicle 20. This allows the management server 70 to convey the intention of the user of the friend device 51 who primarily drives the vehicle 20 to the user of the non-friend device 52.

[0223] As long as the management server 70 can send the confirmation notification M300 to at least one device 30 that stores information about the digital key associated with the first digital key, the management server 70 does not need to send the confirmation notification M300 to the second device 30B that stores information about the second digital key that generated the first digital key.

[0224] The management server 70 may transmit a confirmation notification to two or more devices 30 that store information about the digital key associated with the first digital key. For example, when the management server 70 receives a first request notification M60 from a non-friend device 52 to which the first digital key is registered, the management server 70 may transmit a confirmation notification to multiple devices 30 that store information about the digital key associated with the first digital key. The multiple devices 30 may be, for example, the second device 30B, which is the friend device 51, and the first device 30A, which is the owner device 40.

[0225] <Other change examples> Other elements that can be modified in common to the above embodiments include the following: The following modifications can be implemented in combination with each other to the extent that they are not technically inconsistent.

[0226] The digital key-related matters in the above embodiments do not have to comply with the CCC. The default termination condition EC does not have to be selectable by the owner device 40. For example, the management server 70 may be configured to set a specific condition as the default termination condition EC. In this case, the management server 70 may transmit a notification to the owner device 40 that, when the default termination condition EC is met, prompts the owner device 40 to select only whether or not to prohibit operation A that is not included in the authority information ATP7 in the non-friend key KN.

[0227] The management server 70 does not have to be configured to be able to set the default termination condition EC. If the vehicle 20 stores the authority information ATP7, the management server 70 does not need to store the authority information ATP7 in the non-friend device 52.

[0228] If the non-friend device 52 stores the authority information ATP7, the management server 70 does not need to store the authority information ATP7 in the vehicle 20. The range of vehicle 20 functions that the device 30 can perform, as indicated in the authority information ATP7, is not limited to the functions described in the embodiment. For example, the authority information ATP7 may include functions that only permit unlocking and locking of the trunk box in the vehicle 20.

[0229] The management system 10 may be configured so that the authority information ATP7 stored in the device 30 that stores the key information DK indicating the digital key matches the authority information ATP7 of the digital key stored in the vehicle 20.

[0230] 11, the management server 70 may transmit a permission request D61 to the vehicle 20 and the non-friend device 52. In this case, the management server 70 transmits a signal to the non-friend device 52 to delete the operation A added to the authority information ATP7 of the non-friend device 52 in step S101 shown in FIG.

[0231] 16, the management server 70 may transmit a permission request D71 to the vehicle 20 and the non-friend device 52. In this case, the management server 70 transmits a prohibition request D72 to the vehicle 20 and the non-friend device 52 in step S209 shown in FIG.

[0232] <Registration of a new non-friend key KN by the non-friend device 52> 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 storing the share key KS 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.

[0233] 4, the third device 30C, which is a non-friend device 52 that stores key information DK indicating the non-friend key KN of the vehicle 20, may transmit a request to register a new non-friend key KN of the vehicle 20. As a result, the new device 30 that stores the key information DK of the new non-friend key KN of the vehicle 20 is registered as the non-friend device 52.

[0234] If the digital key registered in the new device 30 is considered to be the first digital key, the third device 30C is the device 30 in which the second digital key is registered. In this case, the second device 30B is the device 30 in which the third digital key is registered.

[0235] The management server 70 may send a notification to the second device 30B requesting permission for operation A, which is not included in the range of functions that the new device 30 can perform as the non-friend key KN of the vehicle 20. This allows the user of the second device 30B, which stores information about the digital key associated with the first digital key, to understand how the user of the new device 30, to which the first digital key is registered, is using the vehicle 20. Furthermore, the management server 70 allows the user of the second device 30B, which stores information about the digital key associated with the first digital key, to permit or deny the user of the new device 30 from using functions of the vehicle 20. This allows the management server 70 to convey the intention of the user of the second device 30B, which stores information about the digital key associated with the first digital key, to the user of the new device 30, to which the first digital key is registered.

[0236] The management server 70 may send a notification to the third device 30C requesting permission for operation A, which is not included in the range of functions that the new device 30 can perform as the non-friend key KN of the vehicle 20. This allows the user of the third device 30C, which stores information about the digital key associated with the first digital key, to understand the usage status of the vehicle 20 by the user of the new device 30 to which the first digital key is registered. Furthermore, the management server 70 allows the user of the third device 30C, which stores information about the digital key associated with the first digital key, to permit or deny the user of the new device 30 to use functions of the vehicle 20. This allows the management server 70 to convey the intention of the user of the third device 30C, which stores information about the digital key associated with the first digital key, to the user of the new device 30 to which the first digital key is registered.

[0237] The management server 70 may send a notification to the first device 30A, which is the owner device 40, requesting permission for operation A, which is not included in the range of functions that the new device 30 can perform as the non-friend key KN of the vehicle 20. This allows the user of the first device 30A, which stores information about the digital key associated with the first digital key, to understand the usage status of the vehicle 20 by the user of the new device 30 to which the first digital key is registered. Furthermore, the management server 70 allows the user of the first device 30A, which stores information about the digital key associated with the first digital key, to permit or deny the user of the new device 30 to use functions of the vehicle 20. This allows the management server 70 to convey the intention of the user of the first device 30A, which stores information about the digital key associated with the first digital key, to the user of the new device 30 to which the first digital key is registered.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0253] The types of digital keys do not have to include non-friend keys KN. In other words, in the management system 10, the shared keys KS may only be friend keys KF. <The process for deleting a digital key> In the above embodiments, the friend device 51 transmits the deletion reservation D41 to the management server 70 when deleting the non-friend key KN, but this does not have to be a reservation request. That is, the friend device 51 may transmit a request to delete the non-friend key KN to the management server 70 regardless of the predetermined condition RC. Furthermore, the management server 70 may proceed with the processing from step S62 onwards in response to a request to delete the non-friend key KN not only from the friend device 51 but also from the owner device 40.

[0254] The following describes a case where an operation to request deletion of a non-friend key KN is executed in the non-friend device 52. In this case, instead of the process in step S81 of FIG. 9, the non-friend device 52 may send a request to delete the non-friend key KN registered in the non-friend device 52 to the management server 70. Upon receiving the request, the management server 70 generates a request to delete the non-friend key information DKN, similar to step S66 shown in FIG. 8. The management server 70 then sends a request to delete the non-friend key information DKN to the non-friend device 52. Having received the request to delete the non-friend key information DKN, the non-friend device 52 deletes the non-friend key information DKN, similar to step S67 shown in FIG. 8. The non-friend device 52 then transmits a notification to the management server 70 indicating that the non-friend key information DKN has been deleted. After receiving the notification indicating that the non-friend device 52 has deleted the non-friend key information DKN, the management server 70 proceeds with the process from step S82 onwards shown in FIG. 9. The non-friend device 52 does not need to send a notification indicating that the non-friend key information DKN has been deleted to the management server 70. In this case, the management server 70 sends a request to the non-friend device 52 to delete the non-friend key information DKN, and then proceeds with the processing from step S82 onwards shown in Figure 9.

[0255] In both cases where a non-friend key KN is deleted due to operation of the friend device 51 and where a non-friend key KN is deleted due to operation of the non-friend device 52, a reservation for deletion may be requested from the management server 70.

[0256] The owner device 40 and the vehicle 20 may request the deletion of the non-friend key KN. Alternatively, for example, the management server 70 may generate a request to delete the non-friend key KN when a predetermined condition is satisfied.

[0257] <Additional Notes> The technical ideas that can be understood from the above-described embodiment and modified examples will be described. [Appendix 1] A server that manages multiple digital keys that can be used for a vehicle, the multiple digital keys including a first digital key and multiple digital keys associated with the first digital key, and when an operation that is not included in the range of functions that the first digital key can perform is performed, the server sends a confirmation notification to at least one device that stores information about the digital key associated with the first digital key.

[0258] [Appendix 2] The server of Appendix 1, which upon receiving a request notification, sends the confirmation notification to at least one device that stores information about a digital key associated with the first digital key.

[0259] [Appendix 3] The server described in Appendix 2, which, upon receiving the request notification from the vehicle, sends the confirmation notification to at least one device that stores information about a digital key associated with the first digital key.

[0260] [Appendix 4] A server as described in Appendix 2 or Appendix 3, which, when receiving the request notification from a device that stores information about the first digital key, sends the confirmation notification to at least one device that stores information about a digital key associated with the first digital key.

[0261] [Appendix 5] A server according to any one of Appendices 1 to 4, which, when receiving a notification permitting the operation from at least one device that stores information about the digital key associated with the first digital key, sends a permission request to add the operation to the range of functions that can be performed by the first digital key, and when a predetermined termination condition is met, sends a prohibition request to remove the operation from the range of functions that can be performed by the first digital key.

[0262] [Supplementary Note 6] The server according to Supplementary Note 6, which transmits the permission request and the prohibition request to the vehicle. [Supplementary Note 7] The server according to Supplementary Note 5 or Supplementary Note 6, which transmits the permission request and the prohibition request to a device that stores information about the first digital key.

[0263] [Appendix 8] A server as described in Appendices 5 to 7, which sets the default termination condition according to information indicating the default termination condition received from at least one device that stores information about a digital key associated with the first digital key.

[0264] [Appendix 9] The server according to any one of Appendices 1 to 8, wherein the plurality of digital keys associated with the first digital key include the digital key that generated the first digital key, and the server sends the confirmation notification to a device that stores information about the digital key that generated the first digital key.

[0265] [Appendix 10] The server according to any one of Appendices 1 to 9, wherein the plurality of digital keys associated with the first digital key include an owner key, only one of which can be registered to the vehicle, and the server transmits the confirmation notification to a device storing information about the owner key. [Explanation of symbols]

[0266] A…Operation ATP7...Authority Information D61, D71…Permission request D72…Prohibition request EC…Termination conditions KO…Owner key M62, M72, M300…Confirmation notification 20...Vehicle 30…Devices 30A...First device 30B...Second device 30C...Third device

Claims

1. a server that manages multiple digital keys that can be used for a vehicle; the plurality of digital keys includes a first digital key and a plurality of digital keys associated with the first digital key; When an operation that is not included in the range of functions that the first digital key can perform is performed, a confirmation notification is sent to at least one device that stores information about a digital key associated with the first digital key. server.

2. Upon receiving the request notification, transmitting the confirmation notification to at least one device that stores information about a digital key associated with the first digital key. The server of claim 1 .

3. When the request notification is received from the vehicle, the confirmation notification is sent to at least one device that stores information about a digital key associated with the first digital key. The server of claim 2.

4. When the request notification is received from a device that stores information about the first digital key, the confirmation notification is sent to at least one device that stores information about a digital key associated with the first digital key. The server according to claim 2 or claim 3.

5. transmitting a permission request for adding the operation to a range of functions that can be performed by the first digital key when a notification permitting the operation is received from at least one device that stores information about the digital key associated with the first digital key; When a predetermined termination condition is met, a prohibition request is sent to remove the operation from the range of functions that can be performed by the first digital key. The server of claim 1 .

6. Transmitting the permission request and the prohibition request to the vehicle. The server of claim 5.

7. The permission request and the prohibition request are transmitted to a device that stores information about the first digital key.

7. The server according to claim 5 or claim 6.

8. setting the predetermined termination condition according to information indicating the predetermined termination condition received from at least one device that stores information about a digital key associated with the first digital key; The server of claim 5.

9. the plurality of digital keys associated with the first digital key include the digital key that generated the first digital key; Sending the confirmation notification to a device that stores information about the digital key that generated the first digital key. The server of claim 1 .

10. The plurality of digital keys associated with the first digital key include an owner key that can be registered only once to the vehicle; The confirmation notification is sent to a device that stores information about the owner key. The server of claim 1 .

Images